I’ve worked a lot in both, and generally this captures my feelings about the situation.

Now I’m pretty much fully into OCaml via F#. F# hits a pretty perfect sweet spot with lots of great libraries and access to a fantastic language.

I suppose this is a hot take, but I’d never intentionally select a closed source paid database or programming language. Your data is the most valuable thing you have. The idea that you’d lock yourself into a contract with a third party is extremely risky.

For example, I’ve never seen a product on Oracle that didn’t want to migrate off, but every one has tightly coupled everything Oracle so it’s nearly impossible. Why start with Oracle in the first place? Just stay away from paid databases, they are always the wrong decision. It’s a tax on people who think they need something special, when at most they just need to hire experts in an open source database. It’ll be much much cheaper to just hire talent.

Meanwhile I’ve done two major database shifts in my career, and you are correct, keeping to ANSI standard SQL is extremely important. If you’re on a project that isn’t disciplined about that, chances are they are undisciplined about so many other things the whole project is a mess that’ll be gone in ten years anyway. I know so few projects that have survived more than fifteen years without calls for a “rewrite”. Those few projects have been extremely disciplined about 50% of all effort is tech debt repayment, open source everything, and continuous modernization.

I don’t think it’s going away until ECMA supports native types. Until then it’s the best game in town.

If a team decides to move away from it, it’s only few hours work to entirely remove. So even if it’s going away, it’s risk free until then.

But I cannot imagine why any team would elect to remove Typescript without moving to something else similar. Unless it’s just a personal preference by the developers who aren’t willing to learn it. It removes so many issues and bugs. It makes refactoring possible again. I think teams that want to remove all types are nostalgic, like a woodworker who wants to use hand tools instead of power tools. It’s perfectly fine, and for some jobs it’s better. But it’s not the most efficient use of a team to build a house.

“You’re going the wrong way!!”

“How does he know where we’re going?”

“Oh yeah”

Bashir realizes they are going to crash into two other ships

“AHHHHHHH”

ship shudders as it scrapes between the two incoming ships. Sparks fly dramatically, and Bashir looks over to see O’Brien dressed in a devil costume laughing maniacally

Who’s cutting onions in here

You definitely described it perfectly: total chaos.

Titles are just “how valuable you are to that team”.

Every team has different needs, so a senior engineer in one team might be a junior on another team that has a totally different set of needs. There is also no standardized titles, so it mostly is just “whatever they want to call it”.

Stamets you brighten my day and I only have upvotes to give back

This is absolutely cursed and brilliant. Bravo!

Now I just need to find a place to use it.

Ah this story resonates with me so hard. I similarly do this all the time.

Wow that’s pretty epic. Did you have to do anything unusual to get it to work?

I suppose it doesn’t roll away and is easier to stow but the ergonomics on that Starfleet Glo-CubeXtreme 2 seem dubious at best

“Why don’t you step outside an airlock Spez?” - Kira (probably)

Card games that aren’t too hard to learn:

• Star Realms / Hero Realms
• Yomi
• Ascension
• Keyforge
• Love letter
• One Night (needs a phone app)