/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Developers on AI coding: many are enthusiastic and now feel more like architects than construction workers, some say software jobs openings may grow, and more

Lately, Manu Ebert has been trying to keep his A.I. from humiliating him.  —  I recently visited Ebert, a machine-learning engineer …

New York Times Clive Thompson

Context & Ripple Effects

Earlier coverage framed AI coding as an evolution in software work rather than an outright extinction event. This account adds a practitioner-level view of that transition: developers describe moving from direct implementation toward directing and reviewing machine-generated work.

The tension is that automation can raise experienced developers' output while reducing some junior-level tasks, as earlier reporting on productivity and entry-level work suggested. Recent Anthropic research also found its largest performance decline in debugging, making oversight—not merely code generation—a central issue.

First-order effects

  • Developers using AI coding tools spend more of their time specifying systems, judging outputs and correcting failures; the reported “architect” identity reflects a shift in day-to-day responsibility, not simply faster typing.
  • Unreliable or embarrassing model behavior keeps human review and debugging in the workflow, particularly where developers must validate generated changes.

Second-order effects

  • Teams may place greater value on system design, code review and debugging capability as routine implementation is automated; the reported debugging performance decline in an AI-coding experiment underscores that this is a skill risk as well as a productivity gain.
  • The debate over whether openings grow turns on how firms redeploy productivity gains: more capacity could support additional software projects, while reduced demand for routine tasks could narrow some entry paths.

Third-order effects

  • If this pattern persists, software careers are likely to be organized more around supervising AI-assisted production and owning technical decisions, with training and hiring adapting to emphasize judgment over repetitive implementation.
  • The labor-market outcome remains unsettled: AI coding can expand the volume of software work, but it can also change which experience levels and skills employers seek first.

The trend: AI coding is becoming a form of AI industrialization in which developers shift from producing every line to governing a faster, model-assisted software-production process.

Discussion

  • @davidcrespo @davidcrespo on bluesky
    good but almost disappointing in a way when the NYT feature gets it right in every detail. guess Clive Thompson (husband of Emily Nussbaum, TIL) knows his subjects. wonderful synopsis
  • @kottke@mastodon.social @kottke@mastodon.social on mastodon
    Clive Thompson wrote about coding with AI agents.  “Software developers point out that coding has a unique quality: They can tether their A.I.s to reality, because they can demand the agents test the code to see if it runs correctly.” https://www.nytimes.com/...
  • r/BetterOffline r on reddit
    A NYTimes Magazine article paints a mostly rosy picture of AI coding.
  • r/Longreads r on reddit
    Coding after coders: the end of computer programming as we know it