If AI-generated code is changing the role of developers, if Agile improved speed and flexibility, then <a href="https://medium.com/@craig_32726/agile-is-out-architecture-is-back-7586910ab810" target="_blank" rel="noopener nofollow">the next challenge</a> is cohesive long-term structure and understanding - processes and frameworks that guide developers and their AI assistants, to avoid technical debt and ensure long-term maintainability.

This squad was established to be able to share anything about development. Post, Comment, and Upvote!

Dev World

As AI-generated code transforms development workflows, the industry faces a new challenge: maintaining cohesive long-term structure. While Agile methodologies improved speed and flexibility, the focus is shifting back to architectural frameworks and processes that guide both developers and AI assistants to prevent technical debt and ensure maintainability over time.

Agile is Out, Architecture is Back!

The person with knowledge in system design and architecture will always have a place in a company

AI just exaggerated the problem with Agile. Agile has always been about shitcode. It’s only suitable for businesses created to sell. Fast money for investors. You can not create good product with Agile. Never.
Agile === huge cost of maintain in future.
Look at Telegram—9 developers and no Agile. Wanna do the same - ask me how.

The manifesto for agile software development doesn’t say “No architecture”. Companies like to buy into Agile… which most of the time means they buy into someone else’s product that they want to sell and forget to have first principles. The real problem, as the article almost passes over, was “shipping fast”. Companies bought into the idea of Agile because they thought they’d get a speed up. And they do see a time-to-first-value (a la time to first packet in HTTP). That doesn’t mean software, on the whole, is built faster, ostensibly it might even be slower. But that first functional piece come out front-loaded and value is refined by fit over plan. In fact… the manifesto actually states in it’s 12 principles “Continuous attention to technical excellence and good design enhances agility.” So the article, while speaking about a reality we face, isn’t really technically correct.