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
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.
There's typically a combination of issues that are occurring when the codebase goes off the rails.
One is that cruft builds up. Large vibecoded codebases need regular "review cleaning". Where you review the whole thing top down for hygiene, contradictions, bad comments, style, redundancy, design. It's a standard thing for me now. A full review and cleanup pass once every couple months.
The second thing that tends to go wrong is that after a certain complexity threshold, the models cannot keep track of the relevant details for a task very well. They lose sense of project directionality. Every task gets disconnected from other tasks and they start pulling the system apart at the seams, exacerbating the cruft issue above and accelerating collapse.
I've found that separating my documentation into three distinct lobes helps: goaling docs, guardrail docs, and implementation docs. Goaling docs describe in prose the goals of the project which includes scope, certain design targets, and other things that you are aiming towards. Guardrails are for design and implementation choices you have explicitly ruled out, the "what not to do" part. Impl docs describe the state of the system as it is.
The top-level agent documents refer to these and make their purpose explicit.
You'd think a ticketing system might capture this, but it doesn't really provide the richness of expression a collection of documents in a directory does.
These approaches aren't perfect. The process still has a tendency to wander off the rails, but it happens less often now and I catch it more quickly. Every session misses little bits of the goaling alignment, but they also find and address small issues missed by previous sessions. Overall it does a better job of keeping the codebase hovering around some threshold of coherency.
I'm having a lot of fun to be honest. Yes it's bizarre and nothing like what development used to be, but it finally feels like there's some new things to learn now.
These days they know how to handle their own context in review. So I will use that to find improvements too in retrospectivea and a small usage script hook it runs each push that alerts if high token usage. Hint the subagents are getting excessive context, which is also good hint of drift. So then I can measure when it starts happening typically via that script that Claude checks and readjusts when one goes over budget.
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
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).
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.
I think it is mastake to lay this completely at the feet of ICs. What you are describing is a form of engineering, and a lot of management feels that "engineering is solved" (not just "coding") and have no patience for these things. ICs are being forced into extremely naive and unsophisticated AI usage by managers with incorrect mental models. That's why so many ICs are cranky.
Its out there, it can do things, and it has its limitations. What it can do gets lot of light, and what it can't do well becomes a ICs 'skill issue'. Say with AI your velocity can go up by factor or X, but expectation is Y where Y >> X. This leads to lot AI-usage which is nothing close to "engineering". The whole idea that engineer should be able to defend what they build, while showing productivity gains that are factor Y can't be done without cutting corners, and it looks like leadership is mostly ok with it as long as it not immediately causing problems.
This is again not problem with AI essentially, but the overly optimistic expectations from it.
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.