Abstraction Shifts in Programming (History)
The recurring historical pattern in which programming moves up a level of abstraction (assembly → compiled languages → objects → platforms/systems → natural-language/agents), each shift declared 'the end of programming' yet expanding the profession — used to argue whether AI coding is continuity or rupture (Booch's golden ages, O'Reilly, Fowler's determinism break).
Also known as: golden age of software engineering, third golden age, end of programming, rising levels of abstraction, abstraction jump
Documents (3)
- The third golden age of software engineering – thanks to AI, with Grady Booch The Pragmatic Engineer (Gergely Orosz, host; Grady Booch, guest) · 2026-02-04 Reader 🖥️
Software engineering is entering a historically recurring pattern — a rise in the dominant level of abstraction — rather than being automated out of existence, because 'software engineering' has always meant balancing human, economic, legal, and ethical forces (not just writing code), and today's AI tools only automate the coding layer, which is itself bounded by the already-seen patterns they were trained on. - How AI will change software engineering – with Martin Fowler The Pragmatic Engineer · 2025-11-19 source ↗ Reader 🖥️
AI's defining change to software engineering is not primarily a jump in abstraction level but a shift from deterministic to non-deterministic systems — and the disciplines that make software durable and legible to teams over time (small reviewable steps, tests, refactoring, shared vocabulary, mentorship) matter more, not less, as a result, even as the field has not yet worked out how teams — as opposed to individuals — should operate with AI. - The End of Programming as We Know It Tim O'Reilly · 2025-02-04 source ↗ Reader 🖥️
AI will not end programming or cause mass programmer unemployment; it is the latest in a long series of abstraction shifts that each redefined what 'programming' means and historically increased, not decreased, the number of programmers and the scope of what gets built — provided organizations and individuals invest in the 'learning by doing' needed to convert raw AI capability into deployed productivity.
Propositions touching this concept (2)
By publication month, oldest first (extraction month when no publication date is known).
2025-02
- explicitEvery prior major programming-abstraction shift (assembly language, compiled languages, GUIs/OS driver encapsulation, the web, cloud/API economy) was popularly framed as 'the end of programming,' yet each one increased the total number of programmers and the scope of what got built, because falling cost of creation increased demand (elasticity of demand) faster than it eliminated roles.
2026-02
- explicitToday's AI coding assistants (Cursor, ChatGPT, Claude) are a continuation of the third golden age's abstraction-rising trend, not a break from it or the start of a new one — they exist to accelerate the use of the libraries and platforms that the third age already produced.
Open gaps (4)
- incompleteBooch never addresses what would mark the end of the third golden age or the start of a fourth, despite his own periodization implying golden ages are finite — leaving open whether the current AI-driven jump (natural language as programming interface) is a continuation of the third age, as he claims, or qualifies as a new, fourth golden age with its own characteristic crisis.The third golden age of software engineering – thanks to AI, with Grady Booch — read next: Look for a framework that defines golden-age boundaries by their crisis type (complexity crisis → software crisis → platform/trust crisis) and test whether AI coding constitutes a new crisis class rather than an extension of the third age's.
- illogicalThe claim that 'fundamentals survive every abstraction shift' is argued by induction from two prior cases (assembly→high-level languages, functions→objects), both of which stayed within formal, deterministic languages. Booch doesn't examine whether a shift to informal, ambiguous natural-language instruction plus probabilistic generation differs in kind, not just degree — which is the actual crux of disagreement with people who think 'this time is different.'The third golden age of software engineering – thanks to AI, with Grady Booch — read next: Pair with other corpus pieces that directly engage the 'is AI categorically different from prior automation' counter-argument, and with technical analyses of LLM capability trajectories beyond trained-pattern distributions.
- uninformedBooch dismisses Amodei's prediction partly on the basis that current models are trained only on previously-seen patterns, but doesn't engage with the trajectory argument — that model capability has been expanding beyond narrow CRUD patterns at a measurable rate — which is the actual empirical crux of near-term automation-timeline disagreements, rather than a settled historical analogy.The third golden age of software engineering – thanks to AI, with Grady Booch — read next: Pair with benchmark- or practitioner-report-driven pieces examining the rate of capability expansion across recent model releases, not just a snapshot of current limits.
- uninformedFowler attributes the current software-industry downturn and job losses primarily to the end of zero-interest-rate financing rather than AI, but does not engage with the counter-evidence elsewhere in the discourse that some of the layoff wave is genuine AI-driven restructuring (not merely macroeconomic or a cover story) — he states his view confidently without weighing the split causation other commentators report.How AI will change software engineering – with Martin Fowler — read next: Compare against corpus accounts that split the layoff wave into AI-washing/cover-story and genuinely AI-driven restructuring components.