[s1ngular1ties]

Yeah I’ve experienced much the same as you. Like it’s overwhelmingly clear from everything it’s enabled for us that we’re going far, far faster than we ever have, and the guardrails we have in play have helped guard the architecture and make it even harder to commit a bad PR. Sometimes in reading these comments I’m left wondering what sorts of experiences people are having elsewhere that’s left them this soured on its usage in business.

[ryandrake]

Everyone is replying but nobody is reading.

Moving faster doesn’t necessarily mean delivering business value faster. You may be moving faster in the wrong direction.

More code doesn’t necessarily mean delivering more business value. You’re piling on debt and if that debt is growing faster than the value of the code, you’re actually losing.

And even if you somehow are delivering more, better code, faster, and without building technical debt: writing code is somewhere around 1-5% of the actual work and time that it takes to deliver a software product. At least in all the places I’ve ever worked. You are optimizing the wrong thing.

[s1ngular1ties]

You might want to read my earlier comment in the overall thread re: delivering business value and moving the needle features while still building with solid architectural principles. As I mentioned above, the AI stuff - with the rails I’ve put in to guide it - has actually lessened tech debt introduced, not made it worse.

I’m well aware of what you’re saying, but we are definitively moving faster in the correct direction. If this hasn’t been the case for where you’ve worked, my sympathies!