rlander

This has been exactly my experience so far, regardless of the model. A developer knows when to stop and ask questions (colleagues or stakeholders). Claude just keeps going and doubles down on its own interpretation.

For me, the biggest benefit is being able to produce an initial POC that I can learn from before writing my own code. And, as you pointed out, it’s also brilliant for refactoring work.

Except const is not sufficient. It will prevent the reference from being reassigned but the const can still reference a mutable object.

Maybe you haven’t seen this yet, but there is a (recent) option to fork a conversation when you click on the thee dots of a reply.

True, but GDP is often a decent proxy for material living standards, especially across countries and over time (so long as we note what it leaves out).

That’s not a small cycle count for a normal household. 90 × 24 = 2,160 total hours.

I sous vide now and then, about twice a week for 6 hours each, so around 12 hours a week. That works out to roughly 15 years of usable machine time for the average person.

Not bad at all.

I feel like you missed the point of Imba. It's not solely focused on code compression (although that does appear to be a secondary objective). Instead, Imba is all about empowering developers to create declarative user interfaces without the typical complexities that often accompany such tasks, like dealing with reactivity, signals, custom directives, v-dom, and so on.

What an amazing story! I have to admit, I was a bit apprehensive while reading through it.

Does that apply to neutered males?