/
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

A eulogy for coding, which has always felt like an endlessly deep and rich domain, after ChatGPT swallowed knowledge and skills that take lifetimes to master

Coding has always felt to me like an endlessly deep and rich domain.  Now I find myself wanting to write a eulogy for it.

New Yorker James Somers

Context & Ripple Effects

This is an early cultural diagnosis of generative AI’s effect on programming: the concern is not merely faster code production, but whether expertise once accumulated through long practice is being compressed into an interface. A contemporaneous counterpoint argued that chatbots can repackage existing ideas while lacking human lateral thinking, underscoring that the dispute was initially about the boundaries of machine assistance rather than a settled replacement story.

Later coverage makes the question more concrete. Reports of junior developers becoming dependent on coding copilots and of developers shifting toward an architect-like role show the debate moving from coding’s cultural status to how skills are learned and work is divided.

First-order effects

  • The article gives voice to programmers who experience ChatGPT as a challenge to the value and identity attached to mastering code, rather than simply another productivity tool.
  • It reframes coding knowledge as something users can increasingly access conversationally, raising the immediate premium on judgment about what to ask for and how to assess the result.

Second-order effects

  • If AI handles more routine implementation, teams can move human attention toward system design, review, and problem framing—the role shift later described as developers becoming more like architects.
  • Training becomes a pressure point: reliance on copilots can reduce opportunities to build foundations through hands-on implementation, as later concern over junior-developer dependence illustrates.

Third-order effects

  • Software work may stratify more sharply between people who can direct and validate AI-generated output and those whose value is tied primarily to producing routine code; the extent depends on whether validation skills remain broadly taught.
  • This is a step toward the assistant becoming the primary work surface for software creation, where accumulated technical knowledge is mediated through AI tools rather than accessed mainly through documentation, languages, and individual practice.

The trend: Generative AI is shifting programming from an implementation-centered craft toward AI-mediated specification, verification, and systems judgment.

Discussion

  • @craigmod@mastodon.social Craig Mod on mastodon
    Somer's excellent eulogy for coding:  —  “Programmers are people who can endure an endless parade of tedious obstacles.”  —  https://www.newyorker.com/...
  • @chrismaddern Chris Maddern on x
    wen mint @NewYorker? would make an amazing @ourZORA or @manifoldxyz open edition... https://www.newyorker.com/... [video]
  • @ldignan Larry Dignan on x
    “Programming by typing C++ or Python yourself might eventually seem as ridiculous as issuing instructions in binary onto a punch card...maybe the thing to teach isn't a skill but a spirit.” https://www.newyorker.com/...
  • @dannygroner Danny Groner on x
    “GPT-4 is impressive, but a layperson can't wield it the way a programmer can. I feel somewhat more secure than before. As software gets easier to make, it'll proliferate; programmers will be tasked with its design, its configuration, and its maintenance.” https://www.newyorker.c…
  • @diopfode Fodé Diop on x
    “But as I write this my wife is pregnant with our first child, due in about three weeks. I code professionally, but, by the time that child can type, coding as a valuable skill might have faded from the world.” https://www.newyorker.com/...
  • @pbwinston Philip Winston on x
    First-rate article on what AI might do to the professional programmer. One thing is sure: it will be interesting. https://www.newyorker.com/...
  • @thorstenball Thorsten Ball on x
    Attention: new James Somers is out! Not a drill! https://www.newyorker.com/... [image]
  • @ianpatterson99 Ian Patterson on x
    This New Yorker piece on the end of programming has been getting some traction via HN. Suspect the same would have been said at the end of previous phases of coding: the end of assembler, of punched cards, of Cobol, of Fortran,... https://www.newyorker.com/...
  • @cloudmarooned @cloudmarooned on x
    An excellent read.
  • r/MediaSynthesis r on reddit
    “A Coder Considers the Waning Days of the Craft: Coding has always felt to me like an endlessly deep and rich domain.  Now I find myself wanting to write a eulogy for it”