Ask HN: Are developers sad about AI writing more of their code?
12 JFerreol_J 17 7/31/2025, 12:13:54 PM
I’ve been chatting with a few dev friends and colleagues about Cursor, copilot etc
and what surprised me was that their biggest feeling about this was neither excitement nor concern, but sadness.
Sadness in the sense that they are afraid the “fun” parts of their job (thinking, building, solving) might slowly be taken away. That they’ll become bored reviewers.
It got me wondering if other devs feel this way?
Are we really on a path where engineering turns into a supervisory job? or is it just temporary until it shifts into something radically different?
Curious to hear from dev folks here !
When people start relying on the "I just want it to work this way" mentality and let AI take over, they can lose track of how things actually work under the hood. And that opens the door to a lot of problems — not just bugs, but blind trust in things they don't understand.
For me, the joy is in understanding. Understanding what each part does, how it all fits together. If that disappears, I think we lose something important along the way.
But that trust can be dangerous when we don’t even know what we’re trusting. And when something breaks, it can leave us completely blind.
I’m not saying everyone needs to go all the way down to the metal — but I do think it’s important to at least understand the boundaries. Know what’s underneath, even if you don’t touch it every day.
Otherwise, it’s not engineering anymore — it’s guessing.
And I’ve never been good at just “believing” things work. I need to poke around, break them, fix them. That’s how I learn. Maybe I’m just stubborn like that.
the paradigm is shifting from us not deciding how to do, but deciding what to do, maybe by writing requirements and constraints and letting AI figure out the details.
the skill will be in using specific language with AI to get the desired behavior, old code as we know it is garbage, new code is writing requirements and constraints
so in a sense we will not be reviewers, nor architects or designers, but writers of requirements and use cases in a specific LLM language, which will have its own but different challenges too
there might be still a place for cream of the crop mega talented people to solve new puzzles (still with AI assistance) in order to generate new input knowledge to train LLMs
So my worst-case scenario with LLMs in terms of my job is that they will make my job hard to tolerate. If that actually happens, I'll leave the field entirely as there would be no room for the likes of myself in it anymore.
No, I am not sad because I am in control. If there is something I want to take on as an intellectual challenge, I do it.
If it's just mechanical tasks or UI layout tweaking, AI is perfect. I can become the user who keeps asking for fine-tuning of corner radius. :-)
For things that keep me interested, I just won't use LLM features. Sometimes at the end I'll have it audit my code and sometimes it'll catch something that can be improved.
Also test cases. It's not perfect, but a large chunk of that being automated there is very nice.
I wouldn't normally post a link to my blog in the comments of another thread -- I'm really not trying to shamelessly plug here -- it's just _incredibly_ relevant, and I've already poured my heart and soul into writing out exactly what I think here, so I think it's germane:
https://prettygoodblog.com/p/the-big-secret-that-big-ai-does...
> I cannot write the necessary philosophical screed this deserves, but: there are things which make us human and in our individual humanity unique; these things are art and skill of any kind; and it so greatly behooves one to strive to master art in any and all its forms.
This being said it does get some uninteresting things done very fast so I’m not entirely sad
Hearing people say that code review/reading is the boring part makes me think maybe I should actually pursue this
I don’t think people who know how the computer and networking works are going anywhere any time soon. Or the people who actually made react or pydantic.