I wrote something similar in scope a while back. I think making agile processes useful and productive is something needed. https://www.linkedin.com/pulse/agile-principles-from-traditional-american-view-jeff-jones/ https://www.linkedin.com/pulse/rethinking-software-development-life-cycle-management-jeff-jones/

Juraj Malenica Coding can be automated to a degree. That has been going on for years with code generators and templates. But writing code for what is designed takes more than what a code generator or AI can do. There is a tendency among coders to find a "recipe" that somewhat fits an intended method to code, and force it in. But that ends up, in the aggregate, with buggy, unstable, and resource-hungry apps. Instead, coding a design sometimes requires thinking like an engineer and solving a coding problem for which there is no "recipe". The engineer has to create a new solution to a specific new problem. That cannot be automated.

Software engineers are in less demand, and coders are in higher demand as the number of non-technical project managers, scrum masters, and other non-technical managers with authority on a how a project is managed and executed, increases in proportion to the total team size. This brings an outsized emphasis on procedure over good engineering and an emphasis on hiring coders who can code from memory, rather than engineers that design first, choosing the best technology for the maximum value over the SDLC. The general result is getting something out the door quickly without appropriate attention given to quality, performance, reliability, scalability, or total life cycle cost. In the end, the projects often fail without having a correct assessment of why. The best way to avoid this without astronomical costs or great delays in deployment is to minimize or eliminate the non-technical software project team members. Use engineers instead of coders. Engineers learn any needed technology quickly so they can adapt to the changing landscape of technology. Many senior engineers are fully capable of remaining "hands on" while effectively managing the project and relating to non-technical stakeholders. In general, it takes fewer engineers to deliver a solution than coders and non-technical project team members combined, yet deliver a better product that has a lower SDLC cost.