Originally published at terminalblog.com.
Three days ago, a developer posted on Hacker News: "Man, AI is killing my brain."
The post hit 50 points and 24 comments in hours. It wasn't a product announcement or a benchmark. It was a confession.
"Almost one year later and I'm no longer sure I can write code any more. Hell, I'm even struggling to write this post because AI is very good at understanding wrongly spelled words, doesn't care about punctuation or capital letters. Every single thing that made me think, was taken away from me."
That thread, plus two other recent discussions — a principal engineer asking "how much longer are they going to keep me around?" after encoding his judgment into agent systems, and a practical thread on stopping agents from "acting out of line" — reveal what developers actually think when the marketing hype fades.
Here's what emerged.
What Happened: Three Conversations, One Underlying Anxiety
Thread 1: The Atrophy Confession (50 points, 24 comments)
The author, posting as fnoef, describes a year-long slide. Started with careful review of every AI-generated line. Then colleagues shipped 10x more by trusting the agent. Pressure mounted: "improve my productivity and be on par with my colleagues or my work will be at risk."
The descent: small features pushed straight to main → work trees with 4-5 parallel agents → juggling outputs until mental capacity broke → clicking "Recommended" without understanding → copying bug reports into Claude and letting it figure it out.
The result: "I no longer know the code, or how things work."
Thread 2: The Principal Engineer's Exit Question (4 points, deep discussion)
nharziro, a principal engineer with a decade on one codebase, built something different. Not just using agents — orchestrating them. Skills ($rest-api-design, $simplify), AGENTS.md files, MCP layers, automated ticket-to-deployment pipelines.
The harness now produces work "often very close to what I would have written myself."
His question: "If more and more of my knowledge, judgment, and way of working can be encoded into the systems around me, how much longer are they going to keep me around?"
Thread 3: The Control Problem (practical, 3 points)
vivekyyy asks a simpler question: how do you stop agents from violating protocol? Easy to block README writes. Hard to enforce "database migrations must be autogenerated and not handwritten" across Claude, Cursor, and Codex simultaneously.
The answers reveal the current state: provider-dependent configs, custom pre-tool plugins, no universal standard.
Developer Reactions: The Spectrum Is Wide
"I Feel the Same" — The Atrophy Camp
"Feel the same. Except that for me it's not 'after 10 hours...I no longer have the brain capacity'... it's more like 'it doesn't really matter anymore if I can write code or not. It means nothing.' Quite sad, indeed." —
missingpackage"AI atrophies the brain. If you don't use a muscle, it atrophies. You know the solution." —
chistev, linking to their own post "How AI Is Making Us Dumber""We used to joke about 'drinking from the fire hose' but these days it feels like we're heading towards sun bathing in the solar flare." —
MarkusQ
Several commenters drew parallels to the 2009 HN thread "The day I stopped coding" — same anxiety, new tool.
"It's a New Abstraction Level" — The Optimists
"I was lucky enough to have retired from coding as a career before I ever started using Claude Code. Now I write more code than I ever did but I'm less of a coder than I ever have been too. I'm still having fun, it's just a new abstraction level above the coding." —
spottedmarley"It energises me. Finally my ADHD brain has something faster than it to play with endlessly. Everything I make is now a glorious speedrun." —
brador"I look at it as handing it off to an intern to do the preliminary work. As long as I actually look at it for sanity's sake then I'm still in the loop." —
dkowalski
"Your Health Is Your Most Important Resource" — The Resisters
"As someone that is actually resisting the madness, I come to these threads with a feeling of 'I told you so' and pretty soon it turns into sadness for my fellow engineers... We are in a situation where execs are requiring us to do actions that reduce our market value, maybe permanently. It is in your best interest to resist as hard as you possibly can, to the point of insubordination." —
sph"It's as dire as if your employer required you to take mind altering drugs daily. You cannot accept this if you want to remain employable for the long term." —
sph(same comment)"I refused to use AI for mostly the OP's reason despite extreme pressure. I ended up quiet quitting until it was untenable and then found a new job in a regulated market; think fintech/healthtech type. That place is more careful about AI usage." —
eudamoniac
"Encoding Judgment Is the Real Product" — The Systems Builders
The nharziro thread sparked a deeper debate. One commenter argued: "I disagree with you encoding your judgement. You have your judgement from years of work and when you see something stupid I'm sure you stop it. So your judgement is the critical part and AI will not and should not have it outright."
nharziro pushed back: "These skills are themselves a form of judgment. The agent uses them to make decisions... Now, though, we are starting to leave behind much more of what made us capable of doing that job... The code is no longer the only artifact. We are also encoding parts of our decision-making process, standards, patterns, and judgment into the systems surrounding it."
The Real Insight: Three Tensions Nobody Talks About
1. The Productivity Trap Is a Collective Action Problem
Individual developers cannot opt out. The fnoef author resisted for a year — until management made it clear: match the AI-augmented output or risk your job.
Commenter polotics called the 15-parallel-agent workload a "humble brag" — but the reality is, if your peers ship 10x and you don't, you're not "crafting software." You're unemployed.
This isn't individual weakness. It's a prisoner's dilemma where the only winning move (for the individual) accelerates the collective erosion of deep understanding.
2. "Reviewing Code" Doesn't Scale — And Everyone Knows It
The standard advice: "Just review the PRs carefully."
Reality check from wuschel: "With an 10x amount of output you 10x the amount of failures at constant production quality. Did you put improved processes into place?"
From othmanosx: "Reviewing the code is that hard part, but what makes it stressful is GitHub's poor support for a good PR review experience, I ended up building my own solution."
The tooling for human-in-the-loop review hasn't caught up to agent-out-of-the-loop generation. Reviewing 15 agents' output isn't code review — it's triage.
3. The Senior/Junior Divide Is Widening Dangerously
"A senior engineer is only able to effectively delegate to interns because of years spent as that intern/junior engineer. If you're a junior engineer or an intern doing this, I think it might be harmful long-term." —
numeri
This is the sleeper issue. Seniors can vibe-code because they have the mental model to catch hallucinations. Juniors who skip the "painful bits" (hunting for answers, understanding why) never build that model.
As numeri put it: "Spending two hours hunting for an answer to something you don't understand increases your familiarity with the available resources, broadens your knowledge base, leads you to thinking of more questions... Shortcutting all of that with a quick answer from an LLM is not helpful long-term."
What It Means for You
If You're a Junior or Mid-Level Developer
Don't outsource the struggle. The two hours you spend debugging a weird TypeScript error is the career capital. The agent's instant fix is a loan against your future competence.
Practical rule: Write the first draft yourself. Use the agent for refactoring, tests, boilerplate, documentation — the things you already understand well enough to verify.
If You're a Senior/Staff Engineer
Your value is shifting from "writing code" to "encoding judgment." The nharziro model — skills, guardrails, AGENTS.md, automated review pipelines — is where leverage lives.
But: document what you encode. Every guardrail you write is a decision you won't have to make next time. That's leverage. It's also a trap if you stop understanding why the guardrail exists.
If You're a Manager/Exec
The "10x developer" metric is a trap. Measuring output (commits, PRs, features shipped) without measuring comprehension debt creates a time bomb.
Ask your teams: "Can you explain how this feature works without asking the agent?" If the answer is no, you're borrowing velocity from the future.
If You're Building Agent Tools
The control plane is the product. The vivekyyy thread proves it: developers need cross-tool protocol enforcement (migrations autogenerated, no README writes, security policies). Today it's provider-specific configs and custom plugins. Tomorrow it's a standard.
Whoever solves "express intent once, enforce everywhere" wins.
The Uncomfortable Truth
The HN discussions reveal something the press releases don't: developers are scared.
Not of AI taking their jobs — of themselves becoming the kind of developer who can't function without it. The fnoef author didn't fear replacement. They feared atrophy. The nharziro author didn't fear obsolescence — they feared successful obsolescence: encoding themselves so well the system no longer needs them.
The optimists (brador, spottedmarley) have one thing in common: they already paid the price of mastery. They can vibe-code because they know what good code looks like.
The warning isn't "don't use AI." It's "don't let AI skip the part where you become the person who can evaluate AI output."
What's Next
The threads are still evolving. The fnoef post got a new comment this morning: "When reading posts like this, I am really curious how organisations control for quality. With an 10x amount of output you 10x the amount of failures at constant production quality."
No answer yet.
But the fact that 200+ developers engaged with these three threads in 72 hours tells you everything: this isn't theoretical. It's the daily reality of the people building your software.
Related articles
- Claude Code Alternatives in 2026: 12 Options Compared
- Claude Code: Skills vs Subagents vs MCP — The 2026 Decision Guide
- Coding Agent Security Checklist 2026 — The Operators Hardening Guide
Want more grounded takes on AI coding agents? Subscribe to the terminalblog newsletter — no hype, just operator reality.
