But even the good engineers should likely be a little worried.
is there something about planning that LLMs cannot do being your crux of the argument?
what do you believe about your jobs or function that you think will be immune from AI replacing you?
If anything it seems your role is not that dissimilar to those translating languages or business requirements.
I am struggling to see what it is about this planning you do that cannot be done by AI because it seems to me thats not where the moat is rather I find the middle man jobs to be the most vulnerable to AI immediately much more than people writing code.
Because at least someone is watching the outputs from AI and understands the code and can communicate it easily back to the stakeholders without the middle man gate keeping and applying their "taste".
I have a feeling that anyone in your shoes is going to be working with code soon or they won't have much to offer anymore to the business. A stakeholder could easily replace the middle layer with AI and even as a business owner myself I do not see any need to add any more humans at the layer anymore unless they write code.
I don't see how not writing code is being offered as a moat, it seems like that is just translating business/stakeholder requirements to architecture/biz processes which is exactly the type of low hanging fruit that AI will capture first
or was it your point that the position sits closer to the stakeholders (relatively compared to those lifting) thus immune from replacement by AI
or is your argument that your taste is exquisite that no AI will be able to match it like it already has with software so far and it will not improve beyond the current state
https://www.reddit.com/r/ProductManagement/comments/uy1ot1/w...
At least that's how it was for me, maybe other peoples' careers are different.
The "planning things out" has moved to another layer, called "architects"
If they're so good at banging out code now, they're coming for that too, you know.
That might happen, but I don't think it's implied, at least given literally every other bit of technology that has ever happened in history ever.
I am not assuming they'll continue indefinitely, but it's a small step from writing code to planning out the code to write, and another small step from planning a coding project to planning a software project, etc.
These are all small steps, and because the act of specification + planning paid less than specification + planning + programming, what reason do you have for thinking that specification + planning is valuable enough to keep the salaries the same as specification + planning + programming?
I dispute that the problem is fixed size. The people who are senior engineers now will learn how to think at a higher level with the AI models.
I think my argument is that, if they were going to do that, they would have done so by now - they already say that actual coding was only a small percentage of their work anyway.
Would you trust living in a high rise designed by AI?
Designing a system that survives production is the job.
As software engineers, our job will expand horizontally. We will shift left, and right. But that’s really fine, because I’ve found SWE can be really good at that.
They’re good at requirements engineering. They’re good at quality assurance. They’re good at technical support. So, why not pay a SWE to be that person?
Or, at least, some SWEs are good at that. The ones that aren’t will struggle I think.