When systems get complex, someone needs to know them and know where to burn the tokens. You need to know what events need to be produced because you have specific consumers. You need to know your business invariants and why.
If you’re working on something that isn’t complex, yeah I can see why you’d think you can be replaced. If it’s just a front end? Yeah I can see that. A basic CRUD service? Sure. A business critical domain service with events, data migrations, complex business logic? I don’t see it.
However it will be similar to cybersecurity in that there will be no 'entry level' product engineer. It will probably have requirements having worked in customer service or finance or some other adjacent field to get a larger picture of what you are delivering. You will also not need 3000 of these individuals anymore (did we ever really??)
I can see a world where you go from "AI Shepard Customer Success rep" -> some middle role with increasing 'product' responsibilities -> Product Engineer.
The new roles will also probably be more generic - instead of backend and frontend you have 'Backend' (Infra + API) and 'Frontend' (Frontend + Design) and both of these roles will require genuine product thinking
No, and it's the same with leads, they can be given a system they understand but need to reference it.
I'm very certain these are people brushing up against their lack of processes, workflows, or engineering practices.
The context are large enough. You do not need to understand the world to build a chair.
I see the very opposite in many different domains happening now, and some codebases are monsterous. They are figuring out ways that do indeed work well.
The engineers that are figuring out these problems when working with a new tool, will have jobs.
Those who continue to doubt, and distance themselves are the ones that will be behind.
currently working on an initial product for a startup and while I'm substantially further along that I would be without LLMs, I'm at the point where the LLMs are now randomly breaking things.
It's not that I don't think those skills are important, but they betray a fundamental misunderstanding of what SWE is, which is about managing systems, juggling complexity, and having some wisdom about how those things should fit together.
Hopefully we start to better formalize some more of that now that the grunt work can be taken out of the equation a bit. And teach it in schools, find ways to measure it in interviews. etc
What we the people need to do is gain control and hold all the power of AI in our hands - not the filthy rich's hands! Devise systems that flip the power into our hands and create economies and jobs around it (i have ideas and surely 1000s to more do to around this).