AI Pulse

AI makes coding faster, and some developers miss the struggle

AI News 364 min read

Faster is usually treated as unambiguously good. Developers interviewed by CNBC offer a different account: AI coding tools do make them quicker, but the job has stopped being fun.

The fact

CNBC reports that AI coding tools are making software engineers faster, but developers say the work has lost its "sense of joy and fun".

This is not an anti-AI piece. Nobody interviewed said they want to give the tools up. They said something narrower: it is faster, and something is missing.

What the speed is traded for

Code generation pushes the cost of writing close to zero. Engineers' time moves from typing to reading, editing and verifying. The total amount of work does not fall; its shape changes.

What gets removed, though, is the part with the tightest feedback loop. Writing a line, running it, seeing it work is a short-cycle reward. Reviewing code someone else — or a model — wrote is slower and far more ambiguous.

Where the fun actually went

  • The satisfaction of debugging: finding a bug by reasoning has become accepting a suggestion and then checking it
  • Craft: the code is no longer your work, it is your review queue
  • Rhythm: from think-then-write to generate-then-judge

Stack those three and you get an odd sensation: managing something you do not fully understand.

What it does to teams

The most fragile thing is the junior pipeline. Intuition used to be built by writing a lot of code; that practice is now delegated. Reading generated code does not build the same instinct.

Meanwhile the review burden rises. The more code is generated, the more judgement is required, and senior engineers become the bottleneck.

The other side: nostalgia follows every abstraction

Every layer of tooling produced the same complaint. Compilers, high-level languages, frameworks and cloud services were all accused of making programming stop being programming.

The real question is not whether the job is still enjoyable but whether output quality improved alongside speed. If velocity rose and defect rates did not, the trade was worth it — the task is redesigning where the sense of achievement comes from.

What to watch

  • Code review time and defect rates
  • Junior hiring volumes and how juniors are trained now
  • Whether teams redefine what counts as senior
  • Where engineers spend the hours they save

Nothing here is investment advice.

Source: CNBC

Related coverage