跪拜 Guibai
← All articles
Backend

AI's Side Effects on a Veteran Developer: Faster Answers, Atrophied Instincts

By 自然吸气发动机 ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

Every engineer who leans on AI for daily work is trading manual reps for speed, and the loss shows up as weaker debugging intuition and a harder time proving that experience still matters. When the barrier to producing code drops to near zero, the people who profit are tool sellers, not the people who write code.

Summary

AI coding assistants have changed the daily work of a veteran backend developer, and the side effects are showing up in the skills he used to take for granted. The old production-debugging routine of reading logs, tracing source code, and drawing call chains is now a prompt-and-wait loop, with phone-scrolling filling the gap. The intuition that once came from hunting bugs by hand is atrophying, and new vocabulary like Harness, Agent, and Skill gets a quick demo before being filed under “understood.” On the company's internal tech forum, plain knowledge-sharing posts have faded because AI can write them better; posts about AI itself are what draw traffic, even when shallow.

Learning no longer feels like an accumulating asset. Around 2018, studying JVM internals and watching tutorials on weekends built a personal technical base; now a model that has read the internet makes that base hard to price, and a newcomer with AI looks close to the same capability. The reward for blogging is gone, and the profession itself looks precarious: the human is still in the saddle, but as agents improve, the horse is heading toward not needing a groom.

The popular story that an ordinary person with a great idea and AI can get rich is naive. The output has no technical barrier, so anyone with the same tools can reproduce it. The only moat is being first to think of the idea, and that advantage expires quickly in a fast information environment. The gold-rush analogy still applies: the shovel sellers make the money.

Takeaways
— The old production-debugging workflow of reading logs, tracing source code, and drawing call chains has been replaced by handing the problem to AI and waiting.
— The bug-hunting intuition was built by repeatedly digging through source code by hand, and skipping that path is what makes the skill fade.
— New AI terms like Harness, Agent, and Skill are being skimmed at the concept level and marked as known after a single demo.
— On a company internal tech forum, posts that share one ordinary knowledge point have become rare, while AI-topic posts get traffic even when shallow.
— Around 2018, studying JVM internals with books and weekend tutorials was treated as an investment that accumulated into personal technical assets.
— With AI present, individual knowledge breadth no longer differentiates a veteran from a newcomer, because a model can always be broader.
— The programmer's role is compared to riding a horse: the rider still gives commands, but better agents and foundation models point toward a future without a groom.
— An AI-made highlight has no technical barrier, so anyone can reproduce it; the only moat is being first to think of the idea, and that advantage decays fast.
— In the gold-rush analogy, the shovel sellers make the money, not the miners.
Conclusions

The “troubleshooting muscle” complaint is not nostalgia: pattern recognition in debugging comes from repeated trace-and-source sessions, and a tool that removes the intermediate steps also removes the training signal that creates the intuition.

The internal-forum observation describes a market distortion: once a model can write a better explanation of any settled topic, the only content that still earns attention is content about the model itself, which rewards shallowness.

The horse-and-groom metaphor is harsher than the usual “AI augments humans” line: it casts the programmer as a supervisor whose supervision is itself being automated away.

The “everyone can code” message hurts experienced engineers by changing how the market prices output: if a junior with AI can produce something that looks like a senior's work, the price of experience falls before any quality gap becomes visible.

Concepts & terms
Agent
An AI system that doesn't just answer a single prompt; it plans, calls tools, checks results, and loops until it completes a goal. Agent improvements are the main force shrinking the human role in software work.
Harness
The orchestration layer around an agent that runs its loop, manages tool calls and memory, and decides when to stop. It is one of the new AI terms that gets skimmed quickly rather than studied deeply.
Skill
A reusable capability an agent can invoke, often packaged as a prompt, a workflow, or a tool definition. It is one of the new AI terms that gets skimmed quickly rather than studied deeply.
From the discussion
Featured comments
tinnkaigou

It's already irreversible. The next step is that computer languages won't even be needed—just straight to binary.

自然吸气发动机

Indeed, it's irreversible. That's the general trend.

See top comments, translated →
Source: juejin.cn ↗ Google Translate ↗ Backup ↗