Getting some AI related "the job of the software engineer is no longer to type code, it's intent, it's architecture, it's design" blather and... GODDAMN IT PEOPLE WHAT THE FUCK DO YOU THINK THE JOB HAS BEEN UNTIL NOW AND DON'T TELL ME WHY THIS IS DIFFERENT BECAUSE I WILL CHUCK CREAM PIES AT YOUR HEAD FOR YOUR PAST PROFESSIONAL NEGLIGENCE.
JFC, the job has *always* been design, intent, and architecture. That you think this is new speaks poorly of past-you, their decisions, and their judgement.
@wordshaper Absolutely; the main reason to focus on the code is as an introductory learning phase, like learning how to solder or the basics of a breadboard. Taking that step away makes the learning curve harder. Highlighting only that step shows a lack of understanding of what the point is (or avoiding/generating boilerplate because the system got mired down in old practices and stopped evolving).
The progression from Junior to Senior reflects that exact journey.
@zimzat This is true, but in all honesty I feel this is something people should be doing from almost the very beginning.
Unless you're a 12 year old kid blindly typing in program listings from a magazine, *all* of the work you do as a programmer should have intent, design, and architecture. *All* of it. You won't necessarily be very creative with it, or maybe even very good at it, but those are the foundational things the code is just layered on top of.
Dan Sugalski
Russell