> I think it's ultimately about finding the organization that fits the workflow you want.

This is a key point, and one that is rarely articulated.

The problem -- for me, anyway -- with the Current Era is specifically the workload, but the relentlessness.

I'm old enough to remember the Old Days of big release dates. You'd grind for a while, sometimes in a deathmarch, but after the release the organization would relax and there would be _some_ slack.

Now it's an endless river of prompts, push to prod, fix, repeat ad nauseam. Because implementation is now much cheaper but genuinely good ideas are as scarce as ever, companies are turning into a random walk optimizations weirdly mirroring training regimes. The idea apparently being that you make enough features/changes you'll eventually find the key to unlocking hyper-growth.

But unlike a training system, all these intermediate steps compound. Customers find their software mutating under them at an alarming rate. Maintainability becomes barely possible, even with Claude doing a ton of work. We're just creating technical debt we expect the future AI to fix, and getting no closer to the "revenue unlock."

Many are chained with fear to this dehumanizing and demoralizing system, and it sucks.