Software engineers are putting down their hammers

Civil and chemical engineers don’t build what they engineer, but software engineers always have, and now agents are taking that part over.
What’s left of our job is what other engineers have always done. Agents will aid many of those remaining responsibilities, not replace them.
This is for software engineers like me who lose sleep over AI-driven job loss. It covers what changed in my own work, why our careers might be okay, and what I’m doing about it.
This idea started on Slack
A coworker and I were trading jokes about not having careers much longer. I said I worried about it too. Then I kept typing, and the idea for this post came out in one long message.
My point was that software has been an odd branch of engineering. Civil engineers design bridges, dams, and buildings, but they aren’t the ones swinging the hammers or laying the concrete. Until recently, by writing the code by hand, we were. I put it this way that day:
SWE has been a blended role where we’re both the system designers, managers, and the “construction workers.”
Most of our days went to the construction part, and agents do a lot of it now. I continued, “Now a lot of that ‘construction work’ is agents, but the rest of the role still remains.”
I stand by that.
My other engineer friends already don’t “swing the hammers”
Two friends I went to engineering school with took the paths I was thinking of that day.
One studied civil engineering and went into construction. He’s now a project manager at a construction company near Detroit.
When I got into real estate investing and started having issues with permits, he understood right away. Planning, permits, and building codes are a big part of his job.
He’s responsible for the higher-level outcomes of construction sites. And while he’s sometimes on-site wearing a safety helmet, he’s never been the one who’s literally swinging the hammer to get the jobs done.
My other friend studied chemical engineering and became a process engineer at a plant for a household-name consumer goods company.
His work was designing, monitoring, and troubleshooting the processes that make the product, which for a while meant toothbrushes. School had him expecting a more hands-on job, and over time he learned what the job really was. He’d often be on the assembly line, but he wasn’t ever the one operating it.
Whether they design the building or run the job site, neither of my friends has been the one actively producing the outputs of their craft. They decide what gets built, decide how things should work, and then they answer for it.
So if we think of software as a unique field of engineering where we were actively producing the outputs, and now suddenly an alien species known as AI can produce them, it’s natural to panic a bit. Or a lot.
But the code itself was always just part of the job, and I think we can take comfort in looking to other engineering disciplines as a model for where our field is going.
From 100 lines at a time to whole stacks of PRs
This became my reality this summer, while doing a refactor at work.
Our map screen had a view controller and a view model that were incredibly tightly coupled. Thousands of lines of anti-patterns, spaghetti code, no tests -- I mean, you name it.
I’d wanted to fix it for three years, and I finally got the go-ahead to spend two weeks on it.
Earlier this year, when I was chipping away at similarly shaped tech debt with agents, I reviewed their output in 100- to 200-line chunks and steered every step. I’d still catch mistakes.
This time, AI could work with me on a much more detailed plan: the ideal end state, then about 11 PRs of roughly 300 lines of core logic each. Each PR would include “load-bearing tests.”
An agent worked through it one PR at a time. The scope roughly doubled once I saw the SwiftUI map view was both massive and acting as a view controller too, and the stack grew to about 15-25 PRs.
Each PR came back done to spec, close enough to how I would have done it. I fell into a funny loop, planning a couple of PRs ahead and reviewing a couple behind while the stack kept growing. By the end, I was reading whole stacks at once and sending a single round of feedback for all of them.
I had even stopped needing to read every line, focusing on the higher-level feedback instead.
The stack merged the following week. I still caught some minor issues during manual app runs along the way, but I mostly focused on the outputs, the testing strategy, the system design, and the process.
I hadn’t written a single line of code by hand, but there was plenty of work beyond that “hammer swinging” of writing code and reading every single line. Being able to focus on that work was liberating.
What’s left for software engineers
What I checked during that refactor was mostly the tests, aiming for 90% coverage or better, plus the shape of each PR.
I made decisions like where to carve out a helper object so it could be tested. I decided whether a stop-gap protocol was enough to keep the scope on one subsystem, or whether the fix had to work for the whole app. I also judged whether the separation of concerns and data flows were right.
Those calls came from ten years in the industry, six years of working at my company, and three years in my area of the product. An agent can read a skill file, but it doesn’t have my gut reaction to a requirement or my sense of where the platform is headed. That judgment is the part of the job I expect to stay ours.
Trusting agents this much takes an environment built for it, so you start working on the loop instead of within it.
My civil engineering friend has building codes; as software engineers, we often have loose product specs but still write our own constraints. Ours start with unit tests at the seams, then maybe higher-level tests like snapshot, integration, and flow tests. Eventually we build toward agents that test their own work before a human sees it.
The work is shifting, not evaporating.
A fair objection is that agents owning judgment is next. They’re already getting better at planning work like my 11-PR plan, and I can’t promise the gap between AI plans and my gut judgment stays forever.
What I’m counting on, though, is that the context behind a decision, from years in the industry or from working on a specific product, is the last shoe to drop. And hopefully not anytime soon.
Don’t get me wrong. I loved the flow state of writing code for hours with Slack turned off, and I do certainly mourn losing it. But I’m also a builder, and I can build far more now.
Great software engineering was never just the code. So much interesting work remains beyond written syntax and markdown plans -- arguably the most interesting work, and almost certainly the most impactful.
But will there be fewer of us?
The US has about 22k chemical engineering jobs and 380k civil engineering jobs, against about 1.9M Software Developers, Quality Assurance Analysts, and Testers. If our jobs become more like theirs, does that mean a much smaller profession? Does it become fewer people, managing more work?
Even from the BLS, the signals are mixed: programmers, a different BLS cut of our industry sized around 110k, are projected to shrink 7% over the next decade. Meanwhile, Software Developers, Quality Assurance Analysts, and Testers are projected to grow 10%.
Bet on Jevons paradox
Personally, I’m betting that the demand for software grows faster than agents shrink each software team.
It’s the Jevons paradox, and I’m already seeing it firsthand.
The owner of my Krav Maga studio vibe-coded a replacement for the gym software he paid about $200 a month per location for.
His version is purpose-built for his curriculum, tracks student progression down to specific movements, and adapts the lesson plans for each class to focus on what those specific students need for their next belt test. No way he could buy that, and it’s cheaper than his old software. But he’s a smart guy, and he also told me he expects he’ll need to call “an expert” like me someday when he hits a wall.
So extrapolating from that concrete example, my logic roughly goes like this:
Take the expensive, full software teams we’re used to. Let’s say that such a team requires a business opportunity worth $10M+ a year to exist.
As the costs to build and maintain software drop, and leaner teams can create solutions that would’ve needed a much larger team before, we’ll see that dollar line keep falling.
First to the single-digit millions, and then maybe even all the way down to the $100k side business that solves a niche problem incredibly well and at a fantastic value. I know my friend with a landscaping business would love a business management and billing solution dedicated to landscapers if the cost were right.
Someone will still have to maintain all of this, too.
I expect today’s massive software teams to get smaller, with people flowing toward many more small teams. Maybe more solopreneur businesses, or more software agencies dedicated to the vibe-coders.
I’m betting that adds up to more engineering jobs than we have today, and many new roles we can’t even imagine yet.
What the layoff numbers show

I also suspect that the claims of layoffs driven entirely by AI are overblown. Layoffs.fyi has some great tracking on this, as seen in the drawing. The number of layoffs has been fairly consistent since the COVID hiring craze, and what’s changed is the explanations for them.
The way I see this? Follow the incentives.
A CEO cutting a thousand jobs could give any number of reasonable explanations: the company overhired during COVID, high interest rates remain a business headwind for the foreseeable future, the business simply isn’t performing to expectations and needs to pull back, etc.
Or, they could say that a new technology will make the business so much more efficient that it can achieve the same or better results with fewer expenses (people).
The outcome of one thousand layoffs is the same either way, but the narrative is very different.
Which narrative would you choose as a CEO? Which company would you rather back as an investor?
I’m choosing to believe something good
Nobody really knows what happens next, me included. But I’d rather plan on the good outcome than the bad one.
Hope for the best, prepare for the worst, right?
Whatever happens, the outcome at an industry level will be the same either way. But if we can stay level-headed during this transition, the journey will be much smoother.
The folks who come out on the other end of this transformation somewhere successful are going to be the ones who don’t succumb to the doom and gloom, because a person has to believe there can be a sunny day to build for it.
So while I’m stashing as much of my income as I reasonably can into savings and investments to prepare for the worst, I’m also doing everything I can to mentally position myself as the person building toward our future.
If you owned a business or managed a team, which person would you rather have on your team?
My antidote to anxiety is action
The anxiety, stress, and worry that so many in our industry are feeling today are completely valid. And boy, do I feel it too.
What’s helping me is acting on what I control.
Personal finances? I can control that. I’ve upped my savings rate over the past two years, and I dream of reaching financial independence through frugal-ish living.
Information diet? I can control that. Every day I decide to skip Reddit doomscrolling and learn from folks actively working out how our industry’s transformation is happening is a win. The Pragmatic Engineer is my latest favorite.
Skills? I can control that, too. I build with agents every working day, embracing them as a mech suit that helps me go further and faster than ever before. I also choose to invest some of my free time outside of work to develop my skills further, and I’ve already seen the dividends at work.
If you’re losing sleep too, start with one thing you can control, and let’s get through this crazy time together.
Drafted from my dictation with an agent, then edited by me.