It's a shame because it takes away the choice of either seeing the real product, or imagining it - I'm left with this shitty generated impression of what the food won't look like.

The work can be done in future to migrate to using ConcurrentHashMap when the feature to add multithreading support is added. There's no sense to add groundwork for unplanned, unimplemented features - that is premature optimisation in a nutshell.

When wool gets warm it expands, which cools you slightly. It seems to have a much better range of temperatures you can be comfortable in.

Synthetic jumpers and sweaters get stuffy quickly and after a few washes can end up itchy.

And no, good cable knits from non designer brands go for $100-$200 and will last many, many years.

It's notably lacking newer models (4.5 Opus, 4.6 Sonnet) and models from Gemini.

LLMs appear to naturally progress in short leaps followed by longer plateaus, as breakthroughs are developed such as chain-of-thought, mixture-of-experts, sub-agents, etc.

A less rigid development branch allows feature branches to be smaller and easier to merge, and keeps developers working against more recent code.

A more locked-down, PR-only main branch enables proper testing before merging, and ensures that the feature and release branches stemming from it start in a cleaner state.

I've worked with both approaches and I'm firmly in the camp of keeping main stable, with a looser shared branch for the team to iterate on.

Devil's advocate, but it can't if it's in Starbucks ;)

There's far cheaper workstations out there than Macbooks, especially if you're running Linux on them.