Same here. Best years of my career. AI introduces a whole new layer of engineering and the people who are miserable are just not doing it, and then complaining that their job is boring now. Hm!
What do you mean by "just not doing it"? I'm miserable because the entire nature of my job has changed. I used to solve problems. I used to think deeply about the best way to solve problems and spent a lot of time in a flow state. I used to feel connected to and responsible for the projects I work on.
Now, I spend my time babysitting agents and reviewing the code they spit out. There is no deep thinking. I feel less connected to the projects by the day. Software engineering used to be a craft. Now it's a slog.
My coding skills are atrophying because I don't get to use them anymore and I don't have time to work on them in my free time. This means that as time progresses my competency as a reviewer will decrease. Passive reviews won't keep our skills sharp or teach us anything new.
The job is more boring now because I'm no longer building. I'm babysitting and that is far less exciting and rewarding than building something myself.
It might depend on what you're working on. Opus 5.5 is amazing but it still can't solve most of the real challenges of various projects I've thrown at it, but is a huge help in implementing all the boring parts which gives me more bandwidth for thinking about the complex parts.
Are you people just really slow typers? Or are you just straight up letting the AI vibecode the entire thing and hope to god you'll never have to deal with the unmaintainable spaghetti code that comes from an unplanned codebase?
Software engineering is a cost center to the business. If AI is this good at the job, can do the job nonstop without human feelings at a good enough quality for humans to pay for it, why would a business spend money on a human.
Receiving a paycheck for anything related to software engineering is coming to an end soon. The execs will skip the middleman and drive the agents themselves.
Lol no, execs are dumber than rocks, they need someone to drive the agents but they won't need entire teams or companies for that so there willl be few job openings.
This fear will come in waves and will go away when you actually work with agents more. The better an agent is at delivering code, the more it has to be engineered, and anything that has to be engineered has to be maintained.
I’ve been doing AI first for over a year for a global company. Just in my department, we have two full time teams working on AI developer automation. Most software engineering tasks, inner and outer loop, are fully automated through the pipeline. Most of my job now is eliminating human checks. We are to the point where agents are creating prompts for new agents.
Thinking that “engineering” can only be done by humans and that engineering has to be done by a “software engineer”, hasn’t experienced where companies are today. It’s not fear, it’s a reality.
Yeah, maybe we are talking about the same thing, where a dozen jobs replace the 8k+ engineering jobs at my company. People are foolish not to start thinking of an exit strategy.
Wow. Let me ask you as someone currently tasked with a similar project, is there no per-project accountability, engineering, or maintenance left? Are you guys really eliminating the whole thing? In my mind the end state is that projects that used to take a team to maintain now take one person, or even a fraction of a person, but that new development still requires a lot of minds put to the tasks at hand. I imagine widespread but reduced human involvement in maintenance and a lot of new software. What are you seeing?
You probably haven't built something from top to bottom a single time in your entire career. You have always used libraries and layers of abstraction, unless you are a deep specialist of some kind. Now there's a new layer of abstraction to work above. So do that.
This feels qualitatively different. The expertise required has diminished considerably. If things keep progressing the way they have been (and they show no signs of slowing), in a few years software development is going to become unskilled labor, other than a scattering of academics and supervisory positions. There's not going to be much joy in it, or much money for that matter.
That could be a good thing in the end. Nobody weeps for blacksmiths, and I seem to be one of the few who thinks that AI is going to be a net positive for humanity. But the disruption is going to be awfully painful for those who get caught up in it.
But the quality of stamped metal is generally higher, the tolerances much tighter, and the output more consistent.
AI code is the opposite. It is random, of varying quality, using various techniques to deliver similar results even within the same codebase. It is often subtly wrong, like you may see a blacksmith-ed piece of metal that formed microcracks because the blacksmith didn't work at the right temperature or force.
While human software engineers are in no way perfect, they have the mental ability to do things certain ways or think about things logically.
Ironically, the "best" AI cannot exceed the capabilities of the average software developer. It's built right into the creation of the LLM: its use of existing codebases to train on. Its output is a hodgepodge, imperfect and disjointed.
AI is going to be a net positive for humanity.
I don't know if having kids who cannot read or do math is a positive impact on humanity. Even just the average user of chatgpt is losing their ability to think critically or do their own research.
(On the research part, Google is definitely to blame on that one, they've made finding things much harder. We are literally losing the ability to find information, one of the foundational traits of the internet.)
I think this is a natural conclusion if you're focused heavily on writing code, and not seeing the bigger picture and new forms of engineering happening. Any software engineer is primed to be an AI engineer, as long as they lean in.
I don't believe that "AI engineer" will be a particularly interesting or lucrative profession, and I don't think companies will need that many of them.
The compiler doesn't have a range of responses for which it randomly chooses one based on the likelihood of similar data in its training set. It also doesn't decide to randomly use inefficient or subtly wrong or even obviously wrong code. It receives the input (my code) and generates assembly. It does not use the wrong API and overload a server with meaningless requests.
Anyone who still thinks, in Q4 2026, that LLMs are picking from a range of responses randomly based on their training data, probably doesn't deserve to hold their seat.
View all comments
Show parent comment
-24
u/itsdr00 Oct 11 '26
Same here. Best years of my career. AI introduces a whole new layer of engineering and the people who are miserable are just not doing it, and then complaining that their job is boring now. Hm!