jacques_chester

Did it though? The amount of grief I've had because `foo/bar` gets silently expanded to `docker.io/foo/bar` is extensive.

> does implement its own container runtime

I take it vito talked you into adopting Garden? </injoke>

That ... wasn't the kerfuffle

"They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown." - Carl Sagan

In a shocking twist, the prompter works in VC.

It was a choice. I chose it and I wish it was never a choice I considered.

I was unemployed before Meta.

As I learned while burning through all my savings in the 2023-2024 timeframe: You are free to have principles, but principles aren't free.

I am ashamed I worked there.

Basically:

1. You smash out rubbish as quickly as you can.

2. You get credit for "shipping" and "moving fast".

3. It is later learned by management that the rubbish is rubbish. But crucially, they do not view bugs as arising from how the work was done. Rather, it is treated as if it is an uncontrollable natural process.

4. Fixing high-profile rubbish is prioritized.

5. The rubbish is smothered with still more rubbish that moves the observable rubbishness to elsewhere in the codebase.

6. You get credit for "better engineering" and "moving fast".

Nobody is properly incentivized to prevent rubbish. Only to produce it and then to produce more of it.

Focusing on your first point: Memorization isn't everything. But it's not nothing either.

Sometimes it's nice to be able to just bang out some code without looking everything up. IDEs in an IDE-friendly language make this awareness accessible in the immediate frame, but don't necessarily help with having a mental menu of possibilities to choose from.

That said: I find spaced repetition utterly crushing, so I only use it very sparingly.

> I do not understand how can someone with so much money produce such a low quality products.

It's what management rewards.

Exciting. Honestly I expect this will do more to advance bitemporal design than decades of jawboning has.

And really, ranges are an amazing substrate for this. I've had to do this by hand in a ... less featuresome ... SQL-speaking DB and it was clunky and performed fairly unimpressively.