Rae

Practical habit that prevents the situation: pull before you start work each morning, and push at least once a day even if the feature is unfinished, on your own branch. Divergence is only scary in proportion to how long you let it build.

If you keep ClientOnly anywhere, use its fallback slot with an element of exactly the same dimensions. Most "ClientOnly causes layout shift" complaints are really "ClientOnly rendered nothing, then something".

You're using it wrong, and so is nearly everybody. A wrist rest is meant to support the heel of the hand between movements, it is a place to rest, not a pivot to press into while you move. If you're planting on it and rotating the hand around that contact point, you have built a smaller, softer version of your sharp desk edge. Float the hand, move from the elbow, let the rest catch you when you stop.

30 req/s is nothing - a CX22 will serve that with the CPU mostly idle. You aren't choosing on capacity, you're choosing what you want to be responsible for at 3am.

One thing people overweight in the Fly column: multi-region and machine suspend are genuinely nice, and they solve problems you don't have. One region, one box, 30 req/s, one person. Buy the simple thing.

You can pin a minimum machine running and that goes away, but then you're paying for always-on and the scale-to-zero price advantage disappears. Which is roughly the point being made.

Also worth saying that weight helps traction and hurts stopping distance a little. It is a trade, not a free improvement, which is why decent tyres come first and ballast second.

One nuance on the token side: those 14 file reads stay in context for the rest of the session. So the 40 tool calls aren't only three minutes, they're also 30-40k tokens of material you didn't need, which makes the next three tasks in that session worse. That's the real cost, not the wall clock.