A few years ago, being the person who could turn a requirement into working code was a pretty valuable skill.
Now you can give an AI:
“Build me a REST API with authentication, tests and documentation.”
…and get something surprisingly usable in minutes.
So naturally, the uncomfortable question is:
If AI can write the code, what exactly are software engineers getting paid for?
Here's where it gets interesting.
Imagine an AI-generated feature gets merged.
The tests pass.
The deployment succeeds.
And two hours later, production starts throwing errors.
Now someone has to figure out:
Why only certain users are affected?
Why did latency suddenly spike?
Is the application broken, or is the database struggling?
Did the new code introduce a race condition?
Is the fix actually safe to deploy?
AI can help investigate all of this.
But somebody still has to understand the system well enough to know whether the answer makes sense.
And developers themselves seem to know this.
Stack Overflow's 2025 survey found that 84% of developers use or plan to use AI tools, yet 46% said they don't trust the accuracy of AI output. The biggest frustration? AI solutions that are almost right — with 45% saying debugging AI-generated code can take more time.
There's another interesting signal: developers are much less willing to hand AI high-responsibility work like deployment and monitoring.
Maybe that's the shift.
The valuable engineer isn't necessarily the person who can type the most code anymore.
It's the person who can:
understand the problem → design the system → use AI effectively → question its output → debug what breaks → make the right trade-off.
AI might be making code cheaper.
But good engineering judgment?
That's still expensive.
And maybe that's what we're actually getting paid for. 👀
Top comments (0)