[apsurd]

> Philosophically, if you had one part of your work now practically free, you'd like to utilize that freedom to maximally cover for the other parts

I've been struggling to capture this sentiment for myself in a way that hits. If shipping code is a commodity then why is everyone's immediate priority seemingly to ship 10x more code. It just makes no sense. I can't seem to get off this hill. Company-wide AI mandates and 100 fleet Agent orchestration Rube Goldberg machines... it's getting wild out there.

Meanwhile my Claude Pro ($200/year) does force me to smooth out my usage and plan more (Sonnet/Opus advisor split). But other than that, I can't imagine what I'd be doing with 20x (200x?) the compute to code sling. I think I'd lose my mind.

[Aperocky]

Because code used to be correlated with progress, it became almost a measurement in lieu. But realistically, the code is meaningless if it doesn't accomplish something, and that should remain the true bar of progress.

For instance, if I churned out 20x more code, threw away 19x code with rewrites and reverts and discards and accomplished the same project to the same standard 70% faster, would I do it? Yes. The part that matter is not 20x code, it is 70% faster.

Code is both the final product, and a tool to achieve that. We used to have a much harder time to realize the "tool" part, but now we are here. This also means any measurement centered on code being the final product is going to cease being effective or realistic.

[apsurd]

You're right, my gripe is specifically with code slinging that hits production end users. My background is in product so to your point, it's very unnerving to see a straight line being enthusiastically optimized for developers -> customer facing product outcomes.

This is contentious because I'm not exactly advocating for arbitrary gate-keepers. The nuance is that building usable stuff is hard. And not a matter of shipping more code. I take your point to mean well it depends on what that code is doing. If 20x more code is in a meta-harness of simulation and such to arrive at the leading candidate for what hits production, well then you've got my attention there.

[trefoiled]

Forget about the danger of a dev to customer pipeline with no product people in between, some of us are living with the reality of product to customer pipeline with no developers in between, and that's much more disturbing. Our CEO is now the top contributor to our codebase, and he's completely non-technical.

[torben-friis]

>If shipping code is a commodity then why is everyone's immediate priority seemingly to ship 10x more code.

I wonder how much of current engineering practices can be traced to what's pushed to company leaders on LinkedIn.

Every company is shitting bricks pushing for faster development and speed, gotta go fast to nowhere in particular, and I'm convinced it's tied to constant bombardment of the idea that they're doing to be left out or obsolete if they don't get in the ship NOW.