| This is categorically not true. For almost all of my 30 years it’s been 1. Talk to the business, solve XYProblems, deal with organization complexity, learn the business and there needs. 2. Design the architecture not just “the code”, the code has to run on something. 3. Get the design approve and agree on the holy trinity - time/cost/budget 4. Do the implementation 5. Test it for the known requirements 6. Get stakeholder approval or probably go back to #4 7. Move it into production 8. Maintenance. Out of all those, #4 is what I always considered the necessary grunt work and for the most part even before AI especially in enterprise development where most developers work has been being commoditized in over a decade. Even in BigTech and adjacent codez real gud will keep you as a mid level developer if you can’t handle the other steps and lead larger/more impactful/more ambiguous projects. As far as #5 much of that can and should be done with automated tests that can be written by AI and should be reviewed. Of course you need humans for UI and UX testing The LLMs can do a lot of the grunt work now. |
This all happens while we are at the implementation stage and impacts all other aspects of the whole thing. It is a grunt work, but we need elite grunts, who see more than just the minimal requirements.