AI Labor Disruption

How AI reshapes jobs, careers and the developer pipeline — exposure versus replacement, winner-take-most dynamics, and the broken junior on-ramp.

Also known as: exposure vs. replacement, white-collar labor disruption, hvitsnippyrker (white-collar professions), vinnere og tapere (winners and losers), job displacement, AI job doom, vibeshift, AI-junior (AI as junior developer), graybeard engineers, AI alibi, broken promise, the middle, re-soloing of programming

How authors use it

Oldest first (extraction date when no publication date is known).

Documents (61)

• Presentation: A Few Predicted Talks From QConAI 2030 Meryem Arik · 2026-09-14 source ↗ Reader 🖥️
  As falling per-unit token costs and near-zero-cost software collide with rising use-case demand, non-technical builders, and parallel agent architectures, the decisive challenge for software organizations through 2030 shifts from producing more code to governing who builds it, what it costs, and how humans supervise it -- a shift that will also redefine what makes a good software engineer and, as public backlash grows, force new AI regulation.
• Podcast: How Will We Train Developers If AI Does the Routine Work: A Conversation with Scott Hanselman Michael Stiefel (host) with Scott Hanselman (guest, VP, Microsoft/GitHub) · 2026-09-14 Reader 🖥️
  The software industry must institutionalize a formal, metriced 'preceptor' role -- modeled on nursing's dedicated teaching-nurse system -- whose explicit job is to grow junior engineers into seniors, because AI has absorbed the routine, low-stakes toil junior developers used to learn from, and without deliberate, funded intervention the industry's short-term hyper-optimization will hollow out the senior-engineer pipeline within a generation.
• When AI can do more than we can check Christian Catalini · 2026-09-08 Reader 🖥️
  As AI collapses the cost of producing plausible-looking output while the cost of verifying that output stays tied to human time, expertise, and slow real-world feedback, verification — not generation or intelligence — becomes the scarce, binding resource that reshapes careers, companies, investment, and policy, and whoever builds the durable capacity to verify, insure, and correct AI captures the value while everyone else risks sliding into a 'Hollow Economy.'
• How to Respond to the Coming AI Cost Shock Stacia Garr · 2026-08-17 source ↗ Reader 🖥️
  As enterprise software vendors end subsidized AI pricing in favor of unpredictable usage-based billing, leaders must stop treating AI adoption as a software procurement decision and instead manage it as an organizational-design decision — modeling true cost elasticity, protecting core institutional capabilities against AI dependency, and integrating token budgets into workforce planning.
• How Organizations Use AI: Evidence From ChatGPT Aaron Chatterji, David Holtz, Neel Rakholia, Prasanna Tambe, Gawesha Weeratunga · 2026-08-11 Reader 🖥️
  Enterprise ChatGPT adoption and use, measured through OpenAI's own product telemetry across 1,500+ organizations and 17M+ messages, is a broad but highly uneven organizational phenomenon — concentrated among larger, more valuable, more intangible-capital-intensive firms, and diffusing unevenly across job functions, seniority levels and tasks within adopting firms — showing that organizations are still in an early, open-ended process of learning where generative AI belongs in their workflows rather than having already converted access into uniform deployment.
• Presentation: The Free-Lunch Guide to Idea Circularity Holly Cummins · 2026-07-31 source ↗ Reader 🖥️
  Ideas in technology that look genuinely new are almost always old tradeoffs returning because the surrounding environment has re-tilted the balance, not novelties or evidence of forgetting -- and the same 'debt is a tradeoff with the future' logic that explains financial debt also explains technical, epistemic, ecological, and sleep debt, so recognizing which tradeoff underlies a current design is the transferable skill for spotting when a discarded old idea is about to become valuable again.
• This AI notetaker won't sell surveillance to your boss Casey Newton · 2026-07-30 Reader 🖥️
  As AI notetakers make transcription of work meetings the default rather than the exception, the decisive ethical and competitive question is not whether everything gets recorded but who gets to see it afterward — and Granola's bet, per its CEO, is that keeping transcripts private-by-default and refusing employer backdoor access is both the right design choice and the way to build a durable moat in the coming fight over who owns the AI interface layer.
• Sorry, Sam and Elon, we have not reached the Singularity Gary Marcus · 2026-07-28 source ↗ Reader 🖥️
  Sam Altman and Elon Musk's recent claims that we have reached (or are reaching) 'the Singularity' should not be taken seriously, because neither they nor anyone else invoking the term has actually defined it, and under every established definition of the term Marcus can find — I.F. Good's ultraintelligent machine triggering an intelligence explosion, Kurzweil's brain-computer merge, technological growth accelerating beyond human control, or an AI-driven 'age of abundance' — the available evidence (quiet AI-driven layoffs turning into rehiring, a human-caused and containable security incident, and current AI still failing most of a ten-item AGI benchmark) shows plainly that we have not.
• How Gemini Flash agents are helping a Michigan dairy farmer News from Google Team · 2026-07-28 source ↗ Reader 🖥️
  A single motivated farmer can replace hours of daily manual data-reconciliation with a local, privacy-conscious multi-agent AI workflow built on Gemini 3.6 Flash, because that model's lower per-token cost is what newly makes continuous, tool-using 'agentic loops' affordable for small independent operators who couldn't previously justify them.
• Stranded in the Slow Zone Tim O'Reilly · 2026-07-24 source ↗ Reader 🖥️
  Frontier AI agents now let individual builders create personal systems with the complexity and fragility of enterprise software, so the DevOps discipline that once belonged only to large organizations — documentation that outlives any one model, and tool portability rather than model-agnostic architecture or self-hosting — has become a personal survival skill, even as the same shift turns engineers into managers of AI 'bots' and raises the same craft-versus-slop question for writing that it already raised for code.
• Managers Are Not Overhead: They Are Infrastructure David Michelson · 2026-07-22 source ↗ Reader 🖥️
  Organizations flattening management layers on the assumption that AI has absorbed most of what managers used to do are making an unsupported productivity bet, because converging survey evidence shows managers have become the critical infrastructure layer that translates AI investment into realized team-level value, not a layer of overhead AI is now positioned to eliminate.
• The case for making your own apps Casey Newton · 2026-07-22 source ↗ Reader 🖥️
  As AI collapses the cost of building software toward zero, a large and growing share of the software people use — within a few years, plausibly a third to half of it — will be hyper-personalized, disposable software they (or their friends and colleagues) make themselves, which will hollow out commercial SaaS products whose value was mainly a mediocre one-size-fits-all UI while sparing those that hold irreplaceable data or can operate headlessly.
• You won’t get replaced. You’ll get skipped. Ernie Svenson · 2026-07-21 Reader 🖥️
  The right question about AI and law isn't whether AI will replace lawyers but whether AI erodes lawyers' jurisdiction — their claim over work, contested in three arenas (licensing law, public belief, and daily practice) per sociologist Andrew Abbott's 1988 framework — and because daily practice is the arena moving fastest, a solo or small-firm lawyer's best move is to proactively claim new jurisdictional ground with AI rather than defend the old ground with rules alone.
• The New Rules for Becoming an Enterprise Leader HBR.org · 2026-07-14 source ↗ Reader 🖥️
  Three converging forces — pervasive personal/organizational use of AI, geopolitical turbulence, and compressed leadership pipelines — have made every one of the seven classic functional-to-enterprise leadership transitions harder and faster than before, so organizations must replace 'ready now' succession planning with a 'ready enough plus support' model that deliberately builds both outer leader skills (strategic thinking, decision architecture, stakeholder navigation) and inner leader skills (polarity tolerance, emotional regulation, real-time self-awareness) earlier in careers, through curated crucible experiences rather than credentialing.
• The loudest warning about AI and jobs yet Casey Newton · 2026-07-14 source ↗ Reader 🖥️
  Although there is no full-blown AI jobs crisis yet, entry-level employment is already showing measurable erosion, and the cohering consensus among economists (crystallized in the 'We Must Act Now' statement) means governments and labs should build data, incentives, and safety-net institutions now, before the disruption becomes undeniable.
• Travel Through the Lens of AI with Booking.com CEO Glenn Fogel Glenn Fogel (guest); No Priors / Sarah Guo (host) · 2026-07-11 Reader 🖥️
  Because no competitive advantage is a permanent moat in the AI era, an incumbent like Booking Holdings can win only by relentlessly rebuilding itself—deploying AI as a tool to serve travelers and partners better, above all through a personalized agentic travel assistant—while its real but always-assailable edge lies in the operational, supply-side and regulatory complexity that outsiders consistently underestimate.
• Adam Mosseri: AI is a tailwind for authenticity Adam Mosseri (guest); Lenny Rachitsky (host) · 2026-07-11 Reader 🖥️
  Because AI makes creation nearly free and floods the world with synthetic content, the scarce and durable human advantages become taste, judgment and authenticity — which Mosseri argues is a tailwind rather than a headwind for Instagram (audiences will seek out real people and creators, not less), and which in turn reshapes how work is organized: teams compress into small generalist 'pods' led by a new 'product staff' role, while hiring rewards curiosity, grit and a willingness to try over deep specialization.
• Who cleans up after the vibe-coding party? Sam Learner · 2026-07-11 Reader 🖥️
  AI coding tools have made producing an open-source contribution nearly free while leaving the cost of reviewing, verifying and maintaining it entirely on human maintainers -- degrading the reputational and communal incentives that sustained volunteer contribution and pushing individual maintainers toward uncoordinated, defensive responses (ending bug bounties, banning AI submissions outright) in the absence of any systemic rebalancing of who does software's unglamorous, chronically undervalued maintenance work.
• Lenny Rachitsky's Post Lenny Rachitsky · 2026-07-10 source ↗ Reader 🖥️
  The question that best predicts how a tech worker feels about their work in 2026 is no longer their role or employer but what AI has done to their sense of professional identity — and workers sort into four distinct emotional archetypes (Energized, Conflicted, Disoriented, Resentful) that form a spectrum from optimism to resistance.
• Det skal være vanskelig Erik Børve Rasmussen · 2026-07-10 source ↗ Reader 🖥️
  Difficulty is the mechanism of learning, not a defect in it, so AI — a machine for removing difficulty — destroys learning wherever the process rather than the product was the whole point (school, unlike work); the remedy is therefore to redesign AI and assessment as skill-forcing 'simulators' rather than to ban them.
• How the 4 New AI Models Change How You Work AI Daily Brief · 2026-07-10 Reader 🖥️
  A backlogged wave of AI models arriving at once shows the frontier shifting from raw capability to division of labor — orchestrator models directing cheaper, faster, specialized models (voice front-ends, implementation coders) — so working well now means matching each task to the right model rather than always reaching for the smartest one.
• Lawyers are quietly becoming builders Ernie Svenson · 2026-07-10 source ↗ Reader 🖥️
  AI has redefined 'building' from writing software to iteratively correcting and reusing AI workflows for repeatable tasks, so any lawyer — not just a technical few — can and should become a builder without learning to code.
• SWLW #711: The laws of this world (game theory), Should you still become a Software Engineer in 2026, and more. Oren Ellenbogen · 2026-07-10 Reader 🖥️
  As AI compresses both the cost of writing code and the reliability of the signals people and organizations have used to judge value (interviews, hours logged, raw effort), this issue's throughline is that the decisive differentiators shift to what resists commoditization: disciplined distrust toward AI output, deliberate positioning/leverage over sheer effort, and self-directed habits (monthly growth checks, daily writing) that build judgment rather than borrow it.
• 3 ways this coffee shop is growing with Gemini Sarah Armstrong · 2026-07-08 source ↗ Reader 🖥️
  A small-business owner can reclaim time and grow his business by using Gemini as a flexible, no-code assistant for data tracking, creative/design work, and marketing content, because growth comes from better tools rather than more hours worked.
• The "funhouse mirror": How AI reflects the hidden truths of your software pipeline Rachel Laycock (interviewed by The New Stack) · 2026-07-07 source ↗ Reader 🖥️
  AI is not a disruptor but an amplifier of your existing pipeline, so because writing code was never the bottleneck, its coding speed turns a velocity multiplier into a debt accelerator wherever software-delivery fundamentals, guardrails, and stewardship of newcomers are not already in place.
• Arvind Narayanan on Why AI Isn't All That Revolutionary Yascha Mounk · 2026-07-07 source ↗ Reader 🖥️
  AI will be a transformation on the scale of electricity, but because most cognitive work resists full automation — only its 'execute' layer, not its 'decide' or 'deliver/accountability' layers, is what AI is actually replacing — and because economic value structurally migrates to whatever remains scarce (human time and judgment), the transformation will unfold over decades rather than years, leaving society real collective agency to choose how it is governed rather than forcing a choice between technological utopia and catastrophe.
• Are We Entering a New Age of Creativity with the Help of AI? Harvard Business Review · 2026-07-07 source ↗ Reader 🖥️
  Laurene Powell Jobs's Atlantic-OpenAI content-licensing deal exemplifies the correct strategic response to generative AI for creative institutions: treat AI licensing as a short-term revenue and access play while doubling down on human-curated 'meaning' and top-tier creative talent, because genuine creativity — unlike AI's pattern recognition — remains scarce and is what audiences will still pay for.
• We've Stopped Arguing About Whether AI Changes Software Greg Herlein · 2026-07-07 source ↗ Reader 🖥️
  The debate over whether agentic AI transforms software engineering is settled; the transformation is a shift in the center of gravity of the work — from writing code to specifying, verifying, and curating knowledge.
• How tech workers are feeling in 2026: a workforce splitting in two Lenny's Newsletter (Noam Segal) · 2026-07-07 Reader 🖥️
  In 2026, whether AI has left a tech worker feeling amplified or destabilized in their sense of professional identity — not their role, company, or seniority — is now the single strongest predictor of how they feel about work, producing a workforce that is simultaneously more burned out, less optimistic about the field, and yet individually more productive and often still finding real value in the tools.
• AI productivity is burning out your best engineers Sreenivasa Reddy · 2026-07-06 source ↗ Reader 🖥️
  AI coding tools quietly transfer the uncredited work of validating and fixing AI output onto mid-level engineers -- the 'invisible validator' burden -- burning out the exact cohort an organization can least afford to lose, and the remedy is structural rather than personal: leaders must make oversight explicit, measured, and rotated so the hidden cost stops falling silently on the middle.
• Why did Martin Fowler invite 60 engineers to a ski resort? Ivett Ördög · 2026-07-05 source ↗ Reader 🖥️
  The turn to AI-built software has reopened rather than resolved the foundational questions of the craft — should humans still read code, how do we know it works, does code quality still matter, and how do we manage newly-empowered citizen developers — and the author's connective throughline is an optimistic one: AI democratizes building while the disciplines that make code good for humans remain exactly the ones that make it good for AI.
• AI Companies Are Hiring More AI Daily Brief (Nathaniel Whittemore) · 2026-07-02 Reader 🖥️
  The author argues that the dominant 'AI is destroying jobs' narrative is oversimplified: even as AI-exposed sectors shed jobs, the firms adopting AI most aggressively are the ones growing headcount fastest, so exposure to AI is not the same as replacement, and markets and courts are already correcting AI's overreach.
• Research: Why Some Junior Employees Work Well with AI—and Others Don’t Ashish Agarwal, Anitesh Barua, Anu Puvvada, Fangchen Song, Wen Wen · 2026-07 source ↗ Reader 🖥️
  What separates early-career employees who create value beyond an AI baseline from those who merely match or fall below it is not their foundational skills (critical thinking, domain knowledge, AI literacy) but how they behave while working with AI — orchestrating, interrogating, and refining its output — so organizations should redesign entry-level training and performance assessment around that interaction behavior rather than around screening or upskilling foundational skills alone.
• 46 thoughts on the near future bayes · 2026-06-30 Reader 🖥️
  The near future is defined by an already-underway, multi-order-of-magnitude 'algorithmic takeoff' in AI capability — extending from software into robotics, science, and physical production — that will compress vast economic and institutional change into a short, poorly governed window, producing genuine winners and losers, real risks to human agency and strategic stability, and no consensus (including from the author) on how to manage any of it responsibly.
• What is the harder human-capital problem beneath token capital? Turing Post · 2026-06-15 Reader 🖥️
  Beneath Nadella's visible 'token capital vs. human capital' story lies a harder problem — the human capital big firms manufacture best (senior, politically-fluent ladder-climbers) is exactly the kind that wastes token capital, while the frontier-moving talent that would use it well is what corporate structure selects against — so the scarcest capital in the AI age is neither human nor machine but an organizational structure porous enough to hold uncorporate talent and corporate-scale compute together without flattening either.
• The engineering manager role is splitting in two Stephane Moreau · 2026-06-09 source ↗ Reader 🖥️
  The engineering-manager role is fracturing into two divergent futures — the code-adjacent tech lead manager and the non-technical multi-team EM — and because AI-shrunk teams are driving the split as an unplanned byproduct of flattening, engineers on the management path must diagnose which future their company is building and prepare accordingly rather than aiming at a single 'EM' destination.
• You Don't Get to Create Anything (Still Burning: Beck + Randy Shoup on Jevons paradox and distributed systems under AI) Kent Beck — Still Burning Podcast · 2026-06-03 Reader 🖥️
  Cognition is becoming near-free, and per Jevons paradox that will produce more cognitive work and more engineers, not fewer — but the people best prepared for this regime are exactly the ones who already lived through writing the distributed-systems playbook, because they know two things the panicking crowd forgets: that a playbook is hard-won and not obvious until written, and that the human compulsion underneath all of this is the maker's need to create the thing rather than merely transcribe it (the 'you don't get to create anything' moment that drives Shoup out of patent law and back into engineering); accordingly the right posture is calm, perspective-keeping, deductive engagement with the new regime — bounding the genie with specs/evals, making good practices easier rather than shaming the bad, and treating this as another wave of physics-discovery rather than a hype cycle or an apocalypse.
• The Last Technical Interview Steve Yegge · 2026-05-29 source ↗ Reader 🖥️
  The traditional one-or-two-round technical interview has always been a statistically unreliable simulation of real work, and a combination of AI-driven strain (résumé floods, AI-assisted cheating, fraudulent applicants) and a growing supply of available senior talent is finally forcing the industry to replace it with paid, real-work trials — provisional employment models like internships, co-ops, and Yegge's proposed 'campfire' — whose results are made portable and reusable as a permanent candidate credential.
• Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) Kent Beck — Still Burning Podcast · 2026-05-20 Reader 🖥️
  We are not in another technology hype wave but in a step-function transformation: the marginal cost of producing software is collapsing toward zero, large incumbents are adopting AI faster than any prior shift, and the whole ecosystem — not just the AI labs — is accelerating; in this 'Red Queen' regime, profit and productivity may not visibly improve because every competitor is running at the new tempo, so the only sane response is to paddle straight into the wave by sustaining the maker's compulsion (the 'itchy brain'), reshaping engineering leadership toward hands-on impact, and accepting that software engineering as a profession will resemble medicine or law more than the unique 2010s template that minted six-figure undergrads.
• Who Cares About Consumer AI? AI Daily Brief · 2026-05-06 Reader 🖥️
  Consumer AI is growing faster than any technology in history but faces a structural economic disadvantage against enterprise AI: per-user token economics favor enterprise by roughly 100x, making advertising — not subscriptions — the only viable path to consumer-scale revenue.
• Is AI Doom Going Out of Style? AI Daily Brief · 2026-05-05 Reader 🖥️
  The AI job-doom narrative is losing its grip because intellectual pushback (Jevons' Paradox reaching mainstream audiences via Klein/Imas) and market validation (agentic revenue explosion, rising software job postings) are converging simultaneously — though the authors acknowledge the shift rests on thin evidence and public sentiment remains deeply negative.
• Supporting Your Employees' Career Growth When Everyone Is Overwhelmed Rebecca Knight · 2026-05 source ↗ Reader 🖥️
  When workloads and AI/economic uncertainty crowd out career thinking, managers should reframe development away from long-horizon ladder-climbing toward near-term, broad, learning embedded inside the existing flow of work — and lead it by visibly doing it themselves.
• The AI paradox: More automation, more humans, more work | Dan Shipper Lenny Rachitsky (host); Dan Shipper (guest, CEO Every) · 2026-05 Reader 🖥️
  Despite radically improving model capabilities, the agentic era will paradoxically generate more work for more humans — because every agent needs a human gardener, SaaS persists (with users bringing their own tokens via Codex/Claude Code), and progress merely commoditizes yesterday's competence and pushes humans further up the value chain to define what is worth doing next.
• KI tar ikke jobbene, men inngangsporten Lasse Maugesten · 2026-04-17 source ↗ Reader 🖥️
  AI is not reducing overall employment, but it is closing the entry-level pathway into careers by automating the routine, book-knowledge tasks junior employees used to learn from — so unless this is addressed, today's shrinking junior intake will become tomorrow's shortage of experienced workers, in Norway as elsewhere.
• Hard truths about building in the AI era | Keith Rabois (Khosla Ventures) Lenny Rachitsky, Keith Rabois · 2026-04-12 source ↗ Reader 🖥️
  Building a world-class company requires ruthless talent identification and density above all else, and in the AI era this means fewer but more capable people operating at extreme speed with business acumen replacing traditional role specialization.
• Hard truths about building in the AI era | Keith Rabois (Khosla Ventures) Lenny's Newsletter · 2026-04-12 source ↗ Reader 🖥️
  The AI era demands a return to opinionated, founder-led product building with radically smaller teams, where traditional organizational roles like PM are collapsing, hiring 'barrels' (people who can ship end-to-end) matters more than ever, and the biggest consumer of AI tokens will be marketing, not engineering.
• – Dette vil skape vinnere og tapere i rekordfart tekna.no (Hans K. Hvide) · 2026-04-11 source ↗ Reader 🖥️
  AI will create a winner-take-most dynamic among Norwegian white-collar professionals — favoring the most skilled and making entrepreneurship more accessible — and engineers should position themselves by integrating AI into whatever they do and considering starting their own ventures.
• Why Enterprise AI Has a Leadership Problem AI Daily Brief · 2026-04-10 Reader 🖥️
  Enterprise AI adoption is surging in investment and tooling but failing organizationally because leaders are spending almost exclusively on infrastructure and models while neglecting the human, cultural, and structural changes required for adoption — making AI success a leadership problem, not a technology problem.
• SMOC.AI's Post — 5 Minutter: AI og utviklere Kristoffer Kvam · 2026-04-10 source ↗ Reader 🖥️
  AI amplifies senior developers' effectiveness but breaks the traditional junior developer training pipeline, because the simple tasks that served as the learning on-ramp are being automated away — and juniors guiding AI-juniors compound weaknesses rather than building competence.
• Martin Fowler & Kent Beck: Frameworks for reinventing software, again and again The Pragmatic Engineer · 2026-04-07 Reader 🖥️
  In a period of unprecedented technological disruption, the same meta-skills that mattered before — disciplined skepticism tempered by curiosity, small experiments to validate claims, and mastery of craft fundamentals — remain the primary differentiators, but practitioners must shift their satisfaction from writing perfect code to understanding domains and systems at a higher level of abstraction.
• Fragments: February 18 Martin Fowler · 2026-02-18 source ↗ Reader 🖥️
  AI-assisted software development is best understood as an amplifier of a team's existing practices rather than a disruptive break, so the field's real work is rebuilding the human-era practices that are predictably breaking—through emerging disciplines like the supervisory middle loop, risk tiering, TDD-as-prompt-engineering, and platform 'bullet trains'—amid far more shared uncertainty than settled answers.
• Fragments: February 13 Martin Fowler · 2026-02-13 source ↗ Reader 🖥️
  As LLMs become established coding collaborators, software development is reorganizing around 'supervisory programming' in which developers herd fleets of agents — a shift that recasts the profession's central challenges as preserving a team's shared understanding of the system (cognitive debt), sustaining a developer experience that is effectively identical to agent experience, and containing the work-intensification and context-switching that driving many agents creates.
• 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.
• The Future Of Software Engineering Thoughtworks · 2026-02 Reader 🖥️
  As AI takes over code production, engineering rigor does not disappear but migrates to specifications, tests, constraints, risk management, and a new 'middle loop' of supervisory work — and organizations that fail to deliberately rebuild their practices, roles, and governance around these new destinations will suffer compounding losses in quality, comprehension, and stability.
• Automatisert KI-koding vil endre alt ("Automated AI coding will change everything") Henning Meese · 2026-01-09 source ↗ Reader 🖥️
  AI's eventual takeover of most coding work is near-certain and the industry is already betting on it ('all in'), but the specific timeline keeps sliding later than predicted — illustrated by LessWrong's own 'superhuman coder' threshold estimate being pushed back 3.5 to 5 years in a single revision — so human developers are not about to become unemployed en masse in the near term, even though what role they will play once that threshold does arrive remains genuinely open.
• When AI Writes Almost All Code, What Happens To Software Engineering? Gergely Orosz · 2026-01-06 Reader 🖥️
  As AI crosses a real capability threshold and starts writing the large majority of code for many developers and teams, the part of software engineering that was always about judgment, verification, architecture, and accountability — not typing syntax — becomes more valuable, not less, while the raw ability to write code in a given language stops being a differentiator at all.
• Linear’s CEO just described the biggest shift in product team... Aakash Gupta · 2026-01-04 source ↗ Reader 🖥️
  As coding agents collapse the 'middle' translation step between product intent and working code, leverage shifts to the two points that don't automate away — forming and externalizing clear intent before execution, and reviewing agent output after it — so the teams that build structured, context-rich systems usable by both humans and agents will gain a durable structural advantage.
• The Tidy House Tim O'Reilly (with DJ Patil) · 2026 Reader 🖥️
  AI's bottleneck is no longer the technology but the unprepared organizations and economic mechanisms around it; the winners — and the social contract — will be saved by the unglamorous work of 'tidying the house' (clean data, redesigned institutional processes, mechanism design that distributes value) rather than by waiting for an intelligence explosion.
• Simon Wardley's Post — Industrialisation of ML: nine notes on what to expect Simon Wardley · 2025-12 Reader 🖥️
  What is happening with AI is the industrialisation of machine learning — a one-way evolutionary shift to commodity/utility — and the right posture toward it is neither resistance nor hype but disciplined adaptation through the predictable 5-8 year co-evolution of practices, with explicit attention to where bottlenecks, supply-chain power, and inequality will actually land.
• How soon AI will start firing programmers? Yegor Bugayenko · 2023-09-04 source ↗ Reader 🖥️
  Writing in September 2023, weeks into the ChatGPT era and before any coding agent existed, Bugayenko predicts that AI 'robots' will progressively absorb a widening list of software-engineering tasks — starting with low-stakes, assistive work (bug reporting, pull-request review, refactoring, documentation, backlog grooming) and ending, as the furthest-off and most consequential item, with AI monitoring individual programmers' activity to appraise their productivity and determine 'which human contributors are most valuable to their projects' — so that the title's question about firing programmers is answered not by a date but by a position in the list: last.
• How AI coding companions will change the way developers work Dr Werner Vogels (interviewing Doug Seven and Sandeep Pokkunuri, Amazon CodeWhisperer) · 2023-04-27 source ↗ Reader 🖥️
  AI coding companions (as embodied by Amazon CodeWhisperer in 2023) remove the 'undifferentiated heavy lifting' of programming — boilerplate, documentation lookup, unfamiliar-API scaffolding — without replacing developer expertise or control, returning developers' time to the creative, higher-value parts of the job (problem framing, design, customer value) while keeping them fully responsible for reviewing, verifying, and shipping whatever the tool suggests.

Propositions touching this concept (15)

By publication month, oldest first (extraction month when no publication date is known).

2024-11

• explicitBecause people already tend to use AI to replace rather than enhance their own creative skills, overreliance risks a 'crisis of meaning' in creative work — not just job displacement, but the erosion of the sense of purpose traditionally tied to the time and dedication creative work required.
  Co-Intelligence, by Ethan Mollick: a Summary · p7

2025-10

• explicitModern leadership happens 'from the middle of the organisation, not from the top' — mobilising delivery is positional, not just communicative.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs · p8

2026-01

• explicitAs the middle produces more output with less direct supervision, pressure shifts downstream onto reviewing, testing, and releasing code; the tooling for that stage needs to evolve and ideally blend into the overall process rather than remain a late-stage stopgap.
  Linear’s CEO just described the biggest shift in product team... · p6

2026-04

• explicitcorroboratedThe population most vulnerable to AI displacement is 'the middle' — people who entered programming primarily for economic opportunity rather than intrinsic motivation.
  Martin Fowler & Kent Beck: Frameworks for reinventing software, again and again · p6

2026-05

• explicitThe AI job-doom narrative is undergoing a meaningful cultural vibeshift driven by convergence of intellectual pushback and market signals.
  Is AI Doom Going Out of Style? · p1
• explicitdevelopedThe vibeshift evidence is thin — built on a few market signals and one prominent essay — while polls show bipartisan public worry about AI remains strong.
  Is AI Doom Going Out of Style? · p10

2026-06

• explicitContext Rot and 'Lost in the Middle' research (across 18 frontier models) shows every model's performance degrades as input grows — even holding task difficulty constant — so a model's raw context-window capacity is the wrong metric for how much can safely be loaded; active context must be treated as a deliberately allocated budget, the way infra teams treat memory.
  Agent Skills · p11

2026-07

• explicitcontestedThe burden falls on mid-level engineers specifically because they are experienced enough to spot what is wrong but not senior enough to push the work elsewhere: juniors gain leverage from AI and seniors are unblocked by it, while the middle absorbs the validation overhead of both without recognition or the seniority to offload it.
  AI productivity is burning out your best engineers · p2
• explicitestablishedContext management is where agents fail silently: context rot degrades performance 30%+ when key content sits in mid-window positions (Chroma; Stanford 'Lost in the Middle'), even in million-token windows; the fix is not a bigger window but keeping the smallest set of high-signal tokens via compaction, observation masking, just-in-time retrieval, and subagent delegation.
  The Anatomy of an Agent Harness · p5
• explicitGovernments and institutions should build economic safety nets and incentive structures now — a possible AI-funded sovereign wealth fund, unemployment-insurance overhaul, funded worker relocation, wage insurance, and employer incentives to hire younger workers — before AI-driven job displacement becomes undeniable.
  The loudest warning about AI and jobs yet · p9
• explicitIn the three-layer AI supply chain, the middle-layer enterprise that integrates and deploys AI bears legal and reputational accountability when the system harms end users — even for a model it neither built nor trained — because regulators and plaintiffs look first to the organization closest to the affected person.
  You Outsourced the AI—but You Still Own the Risk · p1
• explicitAnthropic's Fable 5 model was shut down by a US government export control order in the middle of a running agent session, roughly eight days earlier than the ten-day warning Gene had received implied.
  Stranded in the Slow Zone · p1

2026-08

• explicitLong prose rulebooks (steering documents of five-to-ten pages, or an entire book, fed into an agent) are treated by models as soft guidelines rather than hard rules, because of a 'lost in the middle' effect where content in the middle of a growing context window loses salience relative to content near the start or end.
  LIVE: Uncle Bob on Software Fundamentals in the Age of AI · p4
• explicitMultiple narrowly-focused, single-task agents keep each agent's own context window under control (reducing the 'lost in the middle' problem for that agent) and allow parallel execution, at the cost of per-agent startup latency and context-rebuilding overhead.
  LIVE: Uncle Bob on Software Fundamentals in the Age of AI · p7

2026-09

• explicitGuardrails alone are insufficient; platform teams must also make clear what 'the middle of the road' is — the architecture and principles a team should aim for — not only the boundary constraints that stop them from going too far wrong.
  Presentation: Platform Engineering in the Age of AI · p25

Tensions

Open gaps (125)

• incompleteThe job-survival heuristic (disintermediation/outcompetition/fungibility) — despite the author's own admission that 'this analysis is quite subtle and this paragraph is not going to do it justice' — is tested against only three anecdotal examples (TikTok influencer, doctor, factory worker) with no reference to labor-economics literature on historical automation waves (e.g., agriculture's employment share falling from roughly 40% to 2% of the US workforce over a century, or manufacturing employment trends since the 1970s) that would let a reader calibrate plausible timeframes or magnitudes for AI-specific labor disruption. This corpus's own extract-arvind-narayanan-ai-isnt-all-that-revolutionary reaches a more developed (though still incomplete, per an existing open gap) decide/execute/deliver decomposition of the same problem; bayes doesn't reach that level of mechanism, let alone cite data.
  46 thoughts on the near future — read next: Compare against extract-arvind-narayanan-ai-isnt-all-that-revolutionary#p4 and #p14, and the existing corpus gap noting Narayanan himself doesn't explain the wage mechanism by which scarce human time would command a livable wage.
• incompleteThought 4 in Culture and Psychology diagnoses a wealth 'doublespeak' (people who say AI benefits everyone but wouldn't trade their own position for a random person's) and unusually applies this critique to the author himself. But the same reflexive scrutiny is not extended to the piece's own epistemics: nearly every uncertain judgment call across the other 45 points (how many OOMs remain, how fast robots scale, whether a pause is wise, whether nationalization happens) resolves toward 'faster/bigger/more capable than consensus expects' — also the reading most flattering to, and most aligned with the visible incentives of, someone with insider familiarity with frontier AI (the piece name-drops GB300s, Anthropic, GLM5.2, Fable, and 'Mythos 2' with specificity). The self-awareness about wealth-doublespeak is not turned on the analogous possibility that consistently forecasting acceleration is itself a predictable output of the author's own position and incentives.
  46 thoughts on the near future — read next: No direct corpus parallel exists; flag as a standalone critical gap about author-incentive disclosure in AI-maximalist forecasting content generally.
• incompleteThe Ramp headcount finding — the argument's strongest evidence — is correlational and self-selected (fast-growing firms are likelier to buy AI). The author flags this and cites matched-firm controls and a 6-12 month lag, but the core causal question (does AI adoption *cause* hiring, or do growing firms simply adopt AI?) is not settled.
  AI Companies Are Hiring More — read next: Read the Ramp/Revelio methodology and its matched-firm controls directly; then Acemoglu & Autor / Autor on automation and labor demand for causal-inference framing on technology adoption and employment.
• incompleteThe 'tributary capitalism' framing reports that OpenAI offers 5% to 'ease Washington pressure' but never examines what the labs receive (regulatory relief? antitrust forbearance? procurement priority?) or the conflicts created when the state holds equity in firms it also regulates and funds.
  AI Companies Are Hiring More — read next: Sovereign-wealth-fund governance (Alaska Permanent Fund; Norway's Government Pension Fund Global) and the state-ownership / regulatory-capture literature; commentary on antitrust and competitive-neutrality implications of government equity in frontier labs.
• incompleteThe Anthropic episode is used as evidence of labs' surveillance-grade visibility into user systems, but the enterprise trust and data-governance implications — for organizations that route proprietary code through frontier coding agents — are left dangling.
  AI Companies Are Hiring More — read next: Enterprise data-governance and confidentiality terms for frontier-lab coding agents (Claude Code, etc.); prior reporting on provider telemetry and account-abuse monitoring.
• incompleteThe essay attributes the mid-level squeeze specifically to AI-generated code, but the mechanism it describes -- experienced-but-not-senior engineers silently absorbing uncredited context and cleanup work -- is a long-standing feature of the middle of the org chart. It never isolates how much of the burnout is genuinely AI-induced versus AI accelerating a pre-existing structural overload.
  AI productivity is burning out your best engineers — read next: extract-burnout-across-org-chart on manager/mid-career 'compression' as a pre-AI structural pattern; measurement that separates AI-attributable review/cleanup load from baseline validation work.
• illogicalThe speaker states up front that she personally tends to overestimate how quickly enterprises change, but does not apply that self-flagged bias when she reaches her most enterprise-speed-dependent predictions -- 'IT manages thousands of apps by 2030' and 'no more separate QCon AI by 2030' both assume fast, broad enterprise organizational change, without her flagging the tension with her own stated error direction.
  Presentation: A Few Predicted Talks From QConAI 2030 — read next: Re-read the talk's specific 2030 timelines discounted for the overestimation bias she herself names, to see which predictions would more plausibly land closer to 2032-2035.
• incompleteThe 'decide, execute, deliver' sandwich is asserted with a confident 'roughly a third each' split but no measurement, citation, or task-level data is offered — for software engineering or for the law/research professions it's casually generalized to.
  Arvind Narayanan on Why AI Isn't All That Revolutionary — read next: Task-decomposition and time-and-motion studies of knowledge work (e.g. O*NET task analyses, McKinsey/consultancy automation-exposure studies) that could empirically test or refute the roughly-equal-thirds claim.
• incompleteThe distributional mechanism by which wealth generated in an AI-dominated economy would flow to pay well for 'scarce human time' services (elder care, companionship, coaching) is explicitly acknowledged by Narayanan as unresolved ('it won't automatically happen... that's the distributional question that is unclear'). The conversation ends on this open question rather than resolving it; the remaining discussion (AI and warfare, and presumably more on this point) is paywalled and unavailable in this extraction.
  Arvind Narayanan on Why AI Isn't All That Revolutionary — read next: Work on post-scarcity/automation distribution mechanisms — UBI design proposals, wealth-tax and sovereign-wealth-fund models for AI-era redistribution, and critiques of 'trickle-down automation' assumptions.
• incompleteNarayanan predicts jobs will persist because 'human time is scarce' and firms will compete on what's scarce, but doesn't explain the mechanism by which scarce human time would command wages sufficient to sustain a middle-class standard of living, rather than collapsing toward subsistence-level 'artificial job' wages, especially given his own ambivalence about UBI as the redistribution backstop.
  Arvind Narayanan on Why AI Isn't All That Revolutionary — read next: Labor economics on wage formation under monopsony/oversupply conditions for 'artificial' service jobs; comparative history of how displaced-labor wages actually behaved during the Industrial Revolution before compensating institutions (unions, minimum wage, welfare state) were built.
• incompleteFogel names the labor speed-mismatch and the non-retrainable worker as the central problem but offers no mechanism beyond corporate upskilling—while conceding that fifty years of government retraining has largely failed—so the policy and social response is left open.
  Travel Through the Lens of AI with Booking.com CEO Glenn Fogel — read next: Read ai-labor-disruption and ai-regulation material on displaced-worker transitions, safety nets and the political economy of dislocation.
• incompleteThe article never specifies what criterion separates a 'nearer-term' prediction from a 'further-off' one — is it required context window, required access to organizational/behavioral data, required trust from humans, or something else? Without a stated criterion, the ordering reads as intuition rather than a model, and it is impossible to tell whether Performance Appraisal is placed last because it is technically harder or because it is more consequential and uncomfortable to automate.
  How soon AI will start firing programmers? — read next: This corpus's material on AI-as-amplifier and AI-labor-disruption, for frameworks that do distinguish technical-capability constraints from organizational/social-adoption constraints on which AI capabilities actually get deployed.
• incompletePerformance Appraisal is described purely as a measurement-and-ranking capability ('determine which human contributors are most valuable') with no engagement with whether the underlying metrics (activity volume, comment sentiment, CI/CD failure correlation) would be a reliable basis for that determination — the article treats measurability as equivalent to validity.
  How soon AI will start firing programmers? — read next: extract-lenny-forsgren-measure-ai-developer-productivity, which argues at length that individual productivity metrics are easily gamed and often misleading in the AI era — directly undercutting the premise that an AI monitoring 'each programmer's activity' would produce a trustworthy appraisal.
• uninformedWritten before any agentic coding tool existed (ChatGPT 3.5 only, no tool use, no autonomous execution loop), the article has no way to anticipate that several of its 'assistive' predictions (PR review, bug fixing) would later be delivered not by discrete bot contributions to a repo but by persistent, scheduled, multi-run agent loops — a structural form this corpus's loop-engineering material shows is now central to how such capabilities are actually deployed.
  How soon AI will start firing programmers? — read next: extract-lulla-loop-engineering-building-blocks-adoption-impact and extract-osmani-loop-engineering, for how 'AI does code review' or 'AI fixes bugs' predictions cashed out structurally three years later.
• incompleteCummins argues the current tech job downturn is mostly interest-rate-driven (ZIRP ending) rather than AI-driven, using a single aggregate vacancy-timing correlation as her main evidence. She does not address the disaggregated finding, present elsewhere in this corpus, that AI is already measurably eroding entry-level/early-career roles specifically even while aggregate figures look stable -- a granular pattern her aggregate graph would not detect.
  Presentation: The Free-Lunch Guide to Idea Circularity — read next: extract-loudest-warning-ai-jobs, for the disaggregated (by seniority/AI-exposure) labor data that complicates the pure interest-rate explanation.
• incompleteThe essay addresses leaders and the front lines but is silent on the middle layer — the fief-leaders themselves as actors who must decide whether to dissolve their own kingdoms. Their incentive structure is sketched (self-interest) but not engaged as a design problem.
  AI Won't Save the Kingdoms We Built — read next: Schein on organizational culture and middle-management as load-bearing; classic literature on 'turkey voting for Thanksgiving' problems in restructurings.
• incompleteThe article never addresses the tension between Hvide's entrepreneurship advice and Tekna's institutional role as a union. If the answer to underpayment is 'start your own company,' what is the union for? This is a significant omission in an article published by the union's own magazine.
  – Dette vil skape vinnere og tapere i rekordfart — read next: Literature on how professional unions adapt to platform/gig economies; Scandinavian labor model under pressure from tech
• misinformedThe claim that AI favors the most skilled is presented as obvious, but recent research (e.g., Erik Brynjolfsson et al.) suggests AI tools disproportionately help lower-skilled workers by raising their floor. The winner-take-most thesis may be exactly backwards for many tasks. Hvide cites no evidence for his distributional claim.
  – Dette vil skape vinnere og tapere i rekordfart — read next: Brynjolfsson, Li & Raymond (2023) 'Generative AI at Work'; Mollick & Mollick on AI and skill compression; DORA 2025 on AI and developer productivity
• incompleteNo discussion of what 'integrating AI' actually means in practice beyond vague advice. The article offers no concrete guidance on what skills, tools, or practices engineers should develop.
  – Dette vil skape vinnere og tapere i rekordfart — read next: Practical AI integration frameworks; Claude Code/agentic workflow literature; Kent Beck on AI-assisted design
• incompleteThe compressed Norwegian wage structure is presented as a problem (engineers are underpaid) without acknowledging that it is a feature of the social democratic model that provides other benefits (equality, social stability, public services). The article implicitly frames American-style compensation as the benchmark without examining the tradeoffs.
  – Dette vil skape vinnere og tapere i rekordfart — read next: Nordic labor economics; the 'flexicurity' model; comparative innovation systems literature
• selection_biasAll four cited studies are sponsored by companies selling enterprise AI tools or services (A16Z, KPMG, Writer, WalkMe/SAP). Each has an incentive to frame AI adoption as important-but-broken, positioning their product category as the solution. The article does not acknowledge this.
  Why Enterprise AI Has a Leadership Problem — read next: Cross-reference with independent academic studies or government statistics on enterprise AI adoption and ROI.
• unaddressed_questionThe article notes 29% of employees are 'actively sabotaging' AI strategy but does not explore whether any of that sabotage is rational — e.g., resisting genuinely harmful implementations, protecting data privacy, or pushing back on poorly designed mandates.
  Why Enterprise AI Has a Leadership Problem — read next: Organizational resistance literature; look at whether 'sabotage' might be better understood as feedback on implementation quality.
• unaddressed_questionThe two-tier workforce thesis (AI super-users vs. everyone else) is stated but its labor market and equity implications are not explored — particularly whether it will deepen existing demographic and socioeconomic divides.
  Why Enterprise AI Has a Leadership Problem — read next: Labor economics research on skill-biased technological change; Autor, Acemoglu on AI and inequality.
• incompleteAs a fragments collection the post names many open questions (token economics, specialists vs Expert Generalists, specs-vs-waterfall, AI-vendor responsibility) but supplies little evidence or method to answer them—it maps the questions rather than resolving them.
  Fragments: February 18 — read next: Read the 17-page Thoughtworks 'key takeaways' PDF and Fowler's linked 'Expert Generalist' article for the underlying reasoning.
• illogicalMarcus's headline rhetorical move — demanding a definition and treating its absence as near-decisive evidence the claim is empty — risks being a debate-winning gotcha rather than genuine engagement. He never considers that Altman/Musk might be using 'Singularity' as a loose metaphor for 'we've crossed into a period of rapid, hard-to-predict change,' which wouldn't require the technical precision Marcus demands to carry some (weaker) meaning. The strength of the piece actually comes from testing several *established* rigorous definitions against evidence and finding each wanting — that part of the argument doesn't need the 'nobody defined it' framing to work, and arguably the framing weakens the piece by putting a shakier argument in the most prominent position (the title and opening).
  Sorry, Sam and Elon, we have not reached the Singularity — read next: Altman's original 'self-contradictory' blog post that Marcus links to but doesn't quote or analyze — reading the actual source would let one assess Marcus's 'self-contradictory' and 'never defines the term' charges directly rather than taking them on faith.
• incompleteMarcus links to but never quotes or walks through Altman's 'self-contradictory' blog post on the Singularity, so the specific charge of self-contradiction is asserted, not demonstrated within this piece.
  Sorry, Sam and Elon, we have not reached the Singularity — read next: Read Altman's original blog post directly and check whether it actually contradicts itself, and whether it offers even an informal working definition Marcus is eliding.
• incompleteThe piece treats three quite different technical usages of 'the Singularity' (Good's intelligence explosion, Kurzweil's brain-computer merge, and a popular 'growth beyond human control' framing) somewhat interchangeably in a single takedown, without ever stating explicitly that these are actually distinct, sometimes incompatible concepts in the singularity literature (Vinge's original technological-singularity sense differs from both). Making that distinction explicit would have made the multi-front rebuttal more rigorous rather than just serially plausible.
  Sorry, Sam and Elon, we have not reached the Singularity — read next: Vernor Vinge's original 1993 essay on the technological singularity, to compare his definition against Good's and Kurzweil's and see how much daylight exists between the senses Marcus treats as roughly equivalent.
• incompleteThe headline '95% faster' asset-creation statistic is asserted with no disclosed methodology, sample size, or baseline definition of the prior process it's being compared against.
  3 ways this coffee shop is growing with Gemini — read next: Look for independently conducted (non-vendor) studies or benchmarks comparing AI-assisted design workflows to baseline design-tool workflows, with disclosed methodology.
• uninformedNo discussion of failure modes or verification: the article never describes how Hrag checks whether the sales forecaster's numbers are correct, or whether Gemini's synthesized newsletter content accurately represents its source articles. For a rigorous adopter, the interesting engineering question — how do you validate output from a system you didn't build and can't fully inspect — goes unaddressed.
  3 ways this coffee shop is growing with Gemini — read next: Seek practitioner (non-vendor) accounts of validating LLM-generated code, data pipelines, or summaries in small-business or non-expert-user contexts.
• incompleteCost is essentially absent from a story framed as nearly effortless ('an hour', '20 minutes'): no mention of Gemini's subscription price for the described use cases (only the news-digest feature notes it needs 'Pro and Ultra'), nor of the time investment required to become effective at prompting and iterating.
  3 ways this coffee shop is growing with Gemini — read next: Compare against Google's published Gemini pricing tiers and independent small-business cost/ROI reporting on AI-tool adoption.
• incompleteThis is a single-business testimonial published on Google's own blog by a Google-affiliated author, with no independent journalism, corroborating sources, or disclosed selection process (why this business, out of presumably many Gemini-using small businesses) — the leap from 'one coffee shop' to the closing claim about 'small business owners' generally is asserted, not demonstrated.
  3 ways this coffee shop is growing with Gemini — read next: Look for third-party surveys or independently reported case studies of AI-tool adoption outcomes across a sample of small businesses, to weigh against this single anecdote.
• uninformedNo discussion of failure modes or verification: the article never describes how Paul checks whether the SVM calculations or their causal attributions (e.g., 'humidity reduced feed intake') are actually correct, and the one detailed walkthrough is introduced as a 'for example,' leaving unclear whether it reflects a real reported day at all.
  How Gemini Flash agents are helping a Michigan dairy farmer — read next: Seek practitioner (non-vendor) accounts of validating LLM-generated financial or operational calculations in small-business or non-expert-user contexts, especially where the same person built, runs, and evaluates the system.
• incompleteThe article does not report what happened to the analysts whose mechanical workload disappeared — whether headcount shrank, roles were redefined toward the 'deeper analysis' the piece gestures at, or attrition/reassignment occurred. Prabhakar's quoted question ('what does an analyst do...') is presented as still open, which means the piece describes an unresolved organizational consequence of its own headline result.
  Grab Cuts Mechanical Analytics Work From 44% to 30% with AI Agents — read next: Follow-up reporting on Grab's analytics team structure or headcount over the same period; broader literature on professional jurisdiction erosion when routine work is automated.
• illogicalHanselman argues both that AI is centrally responsible for eliminating the junior-training on-ramp (the entire premise motivating the preceptor proposal) and that 'AI is not going to take your job -- the hyperoptimization of some C-suite executive is going to take your job,' attributing the pipeline collapse mainly to short-termism rather than AI. These two framings are never reconciled: is AI the proximate mechanism, or merely the current instrument of a short-termism that predates it? The conversation never specifies what a hyperoptimizing company without AI would have done to the junior pipeline, so the counterfactual attribution is left unexamined.
  Podcast: How Will We Train Developers If AI Does the Routine Work: A Conversation with Scott Hanselman — read next: Look for empirical work separating pre-2017 entry-level hiring decline trends from the post-ChatGPT AI-coding-adoption period, to test whether AI is additive to or merely relabeling a pre-existing trend.
• incompleteNo engagement with organizations that lack Microsoft's scale, cash, or executive sponsorship -- a resource-constrained startup, a non-tech company's small engineering team, or a highly outsourced/offshore engineering org has no obvious path to implementing preceptorship as described (400-500 person 'shards,' formal cohorts, explicit executive buy-in).
  Podcast: How Will We Train Developers If AI Does the Routine Work: A Conversation with Scott Hanselman
• incompleteThe 'third place' collapse and anthropomorphization-of-AI risks are raised as real sociological costs, but Hanselman offers no organizational remedy beyond his own personal practice (periodic travel to Seattle); there is no discussion of what fully distributed, no-office companies could do instead, nor any engagement with whether his prescription (in-person contact) is feasible for organizations that chose remote-first specifically to access geographically dispersed talent.
  Podcast: How Will We Train Developers If AI Does the Routine Work: A Conversation with Scott Hanselman
• incompleteTreats overload as a permanent atmospheric condition rather than a designed outcome. The article tells overwhelmed managers how to coach overwhelmed reports about growth, but never asks why aggregate work has expanded or whether it should be cut. The one-sentence 'lighten their load' is the closest it comes — it is not developed and not staffed with examples.
  Supporting Your Employees' Career Growth When Everyone Is Overwhelmed — read next: John Cutler's 'institutionalized overload' (TBM 412 and related) treats overload as a systems problem with feedback loops and organizational levers — read this against Knight's piece to see what's missing when the manager is the only actor in the frame.
• incompleteThe organization as a unit of analysis is absent. No discussion of role architecture, promotion criteria, learning budgets, internal mobility programs, or HR systems. The implicit model is: each manager improvises a development culture inside their span of control, regardless of structure.
  Supporting Your Employees' Career Growth When Everyone Is Overwhelmed — read next: Org-design literature on internal labor markets and skill architectures (e.g., Cappelli on talent on demand) — or Cutler on org operating systems — would supply the missing layer.
• incompleteRisk and accountability are silently transferred to the individual. Career uncertainty caused by employer decisions (layoffs, restructurings, AI deployment) becomes a personal learnability problem. There is no symmetric obligation on the employer.
  Supporting Your Employees' Career Growth When Everyone Is Overwhelmed — read next: Critical management scholarship on the 'enterprising self' and responsibilization (e.g., du Gay, Fleming) — and any HBR-adjacent counterpoint arguing for employer-side commitments.
• illogical'Show your own work' is positioned as the bridge between asking impossible things and maintaining credibility. But if the targets are genuinely impossible (Bidwell's own framing), no amount of leader transparency repairs that; transparency without target reduction is theater. The argument elides the difference.
  Supporting Your Employees' Career Growth When Everyone Is Overwhelmed — read next: Anything on psychological safety as a precondition for honest upward escalation (Edmondson) — to see what 'showing your own work' would need to do to actually change the work, not just narrate it.
• uninformedNo acknowledgment that 'permission to learn' presumes a manager with real slack and political cover to grant time for non-job-essential study. In overloaded, deliverable-tracked teams, that permission is often not in the manager's actual gift — the article assumes managerial discretion that may not exist.
  Supporting Your Employees' Career Growth When Everyone Is Overwhelmed — read next: Cutler on power and space in organizations; flow accounting / slack theory (Tom DeMarco).
• illogicalConflates two distinct claims under the 'rewiring the smiling curve' phrase: (1) the acquirer creates value at all three nodes, and (2) value at the middle (manufacturing) is no longer low-margin. Only the first is argued; the second is suggested rhetorically.
  How Chinese Firms Are Saving Western Brands — read next: Stan Shih's original smiling-curve papers; recent revisions by Mudambi on geography of value.
• incompleteThe interview never follows up on what happens to the writers and journalists who are not top-tier creative talent and are being 'weeded out' as legacy outlets like the Atlantic double down on a smaller roster of highly paid stars. Elkins states plainly that Powell Jobs 'is weeding folks out' and that the publishing 'funnel... is getting more and more narrow,' but the whole argument stays optimistic about the shrinking population of winners without examining the losers' fate, alternative markets, or what this means for journalism's overall labor market and coverage breadth (e.g., local news, beat reporting). This is the sharpest gap: an argument about creative-industry winners built on an unexamined and possibly large population of creative-industry losers.
  Are We Entering a New Age of Creativity with the Help of AI? — read next: Labor-economics and media-industry literature on winner-take-most/superstar dynamics in creative markets, and reporting on the collapse of local and freelance journalism under both the advertising-model crisis and AI displacement.
• illogicalThe central 'meaning cannot be commodified out' argument rests on one negative case (Buzzfeed's failure) and one still-unresolved positive case (the Atlantic, whose own outcome Elkins repeatedly disclaims — 'we'll see where it goes... I have no crystal ball'). No comparative base rate of publisher-AI licensing deals succeeding versus failing is offered, so the argument's generalizability is asserted rather than demonstrated.
  Are We Entering a New Age of Creativity with the Help of AI? — read next: Longitudinal tracking of publisher-AI deal outcomes (traffic, revenue, subscriber retention) as more of the '70+' deals mature past their first year or two.
• uninformedThe claim that AI is 'increasingly eliminating entry-level positions' is asserted without data in this conversation — unlike the planning-cycle-speed claim, where Watkins cites his own survey (~75%). The corpus's own labor-economics coverage treats the entry-level/AI relationship as mechanism-unclear (the aggregate productivity data doesn't yet obviously support the displacement story), so Watkins's confident causal framing may be running ahead of the evidence.
  The New Rules for Becoming an Enterprise Leader — read next: extract-loudest-warning-ai-jobs and extract-stopped-arguing-whether-ai-changes-software for the primary-source debate on whether and how AI is actually displacing entry-level hiring.
• incompleteThe three-forces/seven-transitions framework is presented as applying to 'virtually every leader' and organization, but every illustrative example in the conversation (the food-products company, generic references to 'very large organizations') is a large, AI-adopting, multi-divisional global corporation. There is no engagement with how the framework applies, or fails to apply, to smaller organizations, non-profits, public-sector bodies, or firms in AI-cautious or resource-constrained settings.
  The New Rules for Becoming an Enterprise Leader
• incompleteThe 'T-ledelse' reframe of the hosts' heis-fører concept is elegant, but the question of where T-ledelse fits in a 22,000-person organisation with multiple levels — and whether T-ledelse from the very top can substitute for translation roles at the middle — is not resolved. The hosts' own concept (heis-fører at middle levels) and Holte's reframe (T-ledelse from the top) may not be alternatives at all; the conversation does not address whether both are needed.
  2) Hans Christian Holte dusjer i informasjon
• incompleteThe paper documents that early-career workers are the most intensive per-user users of ChatGPT Enterprise, but does not connect this to the parallel, more alarming finding elsewhere in the literature it cites (Brynjolfsson et al. 2025a) that early-career/entry-level employment itself may be shrinking under AI exposure. It leaves entirely open whether heavy per-user usage among the early-career workers who remain employed reflects healthy skill-building and agent-native fluency, or reflects AI absorbing exactly the repetitive, information-synthesis tasks that used to be assigned to juniors — accelerating headcount reduction at that level even as remaining juniors use the tool the most.
  How Organizations Use AI: Evidence From ChatGPT — read next: Read this paper's task taxonomy alongside labor-market studies of AI-exposed entry-level employment (e.g., this corpus's extract-loudest-warning-ai-jobs, and the underlying Brynjolfsson et al. 2025a paper) to test whether the task categories where early-career workers are heaviest users are the same categories associated with entry-level job losses.
• incompleteThe lab-vs-enterprise conflation. The argument is strongest for frontier labs that BUILD token capital (models, evals, loops require irreverent frontier-movers) and weakest for the telco, bank or typical enterprise that BUYS and absorbs it. A firm that consumes AI rather than pushing the frontier may not need 'permission-averse, loudly-wrong' talent at all — for it the binding constraint is more likely absorption, integration and process legibility than porousness for mavericks. The essay treats the two as one problem and never tests whether its prescription even applies to the majority of the 54% of employment it invokes.
  What is the harder human-capital problem beneath token capital? — read next: Read against the enterprise-AI-adoption literature that separates building vs. buying/absorbing AI capability (e.g. forward-deployed-engineer and readiness models): does a token-capital consumer need frontier-mover porousness, or is its real obstacle organizational absorption, and would importing 'uncorporate' talent even help?
• incomplete'Porous structure' is named as the answer but never operationalized. The essay supplies no mechanism, org-design pattern, incentive structure, or worked example of what porousness looks like, nor how a firm hands 'corporate-scale compute + responsibility' to uncorporate people without recreating the committees and procurement logic that sand them down. The prescription is a direction, not a design.
  What is the harder human-capital problem beneath token capital? — read next: Read toward concrete structural patterns that could fill the mechanism — small-teams/tiny-core bets, autonomous-team designs, skunkworks and lab-within-a-company structures — and test which actually preserve irreverence at corporate scale.
• illogicalThe essay's own evidence strains against its thesis. Demis Hassabis built Gemini INSIDE Google, a corporate giant — 'in spite of' it, yes, but still inside it and still winning — which shows rigid incumbents CAN produce frontier results, cutting against the flat claim that structure 'selects frontier talent out.' By naming only the winning obsessives (Hassabis, Dean, Liang Wenfeng) it also survivorship-selects, saying nothing about the uncorporate people who were in fact crushed. So 'structure selects them out' is asserted more strongly than the evidence, which really shows 'structure taxes them, but some still win.'
  What is the harder human-capital problem beneath token capital? — read next: Read comparatively for cases where incumbents DID retain and productively hold frontier talent, to separate the strong claim ('structure filters them out') from the weaker, better-supported one ('structure imposes a heavy tax they sometimes overcome').
• tensionConflates elite commentary vibeshift with actual public narrative change. The piece acknowledges polls remain negative but does not reconcile this with its thesis that a meaningful shift is underway.
  Is AI Doom Going Out of Style?
• omissionThe Anthropic revenue numbers ($9B to $44B ARR) are presented without questioning sustainability or margin structure beyond the current moment. Revenue growth rate =/= sustainable business.
  Is AI Doom Going Out of Style?
• underdevelopedKlein's insight that 8 million displaced workers may be harder to help than 80 million is introduced but not developed. This is potentially the most important policy point in the piece and gets one sentence.
  Is AI Doom Going Out of Style?
• incompleteThe paradox is asserted but its mechanism is under-specified. Shipper offers 'every agent needs a human' (a maintenance claim), 'benchmarks miss prompting' (an attention claim), and 'models commoditize yesterday's competence' (a frontier claim). These are three different mechanisms doing different work, and Shipper conflates them. The maintenance claim is explicitly transient — he concedes personal agents return as models improve. The attention claim is partially circular — he will redesign his benchmark to zero out a saturated model. Only the frontier claim is structural, and it is the least developed. A serious version of the thesis needs to argue that the new frontier work is itself non-automatable and remunerated — neither is shown.
  The AI paradox: More automation, more humans, more work | Dan Shipper — read next: Acemoglu & Restrepo on task displacement and reinstatement; the 'augmentation vs. automation' literature (Brynjolfsson, Mitchell); recent econometric work on AI's effect on call-centre and software-engineering productivity (the GitHub Copilot RCT, Brynjolfsson-Li-Raymond on generative AI in customer support)
• incompleteThe 'humans-as-orchestrators' vision is unfalsifiable in this conversation. Shipper says explicitly that when models 'saturate' his senior-engineer benchmark, he will redesign it to zero out the current model. If the benchmark moves to wherever AI cannot yet go, the claim 'humans are still needed' is true by construction and tells the listener nothing about the actual trajectory of automatable knowledge work. A senior engineering leader needs a falsifiable formulation — what specifically would need to be true for Shipper to concede that the 'more humans' claim has expired? — and the conversation does not offer one.
  The AI paradox: More automation, more humans, more work | Dan Shipper — read next: Popper on falsifiability; Sutton's 'bitter lesson' as the counter-frame; the eval-design literature (HELM, MMLU saturations, the ARC-AGI debate); recent critiques of human-baseline benchmarks (Anthropic's METR work on long-horizon agentic tasks)
• incompleteSelection effects in the Every case are uninterrogated. Every is ~30 self-selected curious early adopters with pre-release model access, dual media-and-software business model, founder writer-CEO, no legacy systems, no regulated environment, no enterprise sales process longer than the model release cycle. Every assertion in the conversation is sourced from this one organization and projected onto knowledge work in general. For evaluating organizational impact in a Norwegian enterprise context (regulated industries, slower procurement, less English-language model access for non-English work, strong worker-council constraints), the generalization gap is large and unflagged.
  The AI paradox: More automation, more humans, more work | Dan Shipper — read next: Erik Brynjolfsson's recent work on cross-firm productivity dispersion in AI adoption; Wharton-led surveys on enterprise AI deployment; case studies from regulated EU firms (Klarna's published numbers and their later retraction); Norwegian-context: BI Handelshøyskolen / Sintef studies on AI adoption in Nordic enterprise (the 'forskning og digitalisering' extraction in this library)
• incompleteToken-economics assumption (SaaS users bring their own tokens via Codex) is treated as a stable equilibrium when it is more plausibly a transitional artifact. Once enterprise procurement notices that token spend is shifted to user-attached agent harnesses, three forces will push back: (a) per-call agent-tier pricing from SaaS vendors capturing the new volume, (b) enterprise consolidation of agent infrastructure (corporate-controlled Codex/Claude Code deployments), and (c) usage-based SaaS pricing emerging precisely to capture agent-driven volumes. Each of these inverts Shipper's 'buy SaaS stocks' conclusion. He does not engage any of them.
  The AI paradox: More automation, more humans, more work | Dan Shipper — read next: Tomasz Tunguz's recent essays on AI pricing; the cloud-pricing history (AWS's evolution from flat to consumption); Bessemer State of the Cloud reports on agent-driven pricing changes; OpenRouter / LLM-aggregator economics
• incompleteShipper's 'CEO must be personally AI-pilled' claim sits uncomfortably with his 'super-agent per company maintained by a forward-deployed engineer' claim. If the FDE is the load-bearing role and the per-company agent is the substrate, the CEO's personal model fluency is arguably the wrong variable to optimize — the firm needs FDE talent supply and an org design that protects FDE attention from the C-suite. The conversation never reconciles the personal-fluency prescription with the structural FDE prescription.
  The AI paradox: More automation, more humans, more work | Dan Shipper — read next: Karl Weick on 'sense-making' in organizations; recent CIO/CTO surveys on AI organizational placement (Gartner, MIT Sloan); the literature on 'two-pizza team' analogues for AI deployment
• incompleteNo engagement with worker-attention costs of the prescription. 'Ride the models' for every new release, 'try Codex in your off-hours if your employer blocks it', 'every agent needs a human gardener', 'inbox-zero for 10 straight days via Codex monologue' — collectively this is a maximally attentive lifestyle marketed as liberation. Shipper notes he 'works way more' and frames it as paradox-evidence, not as cost. For a senior engineering leader thinking about sustainable organizational design, the elision of attentional and psychological cost is significant.
  The AI paradox: More automation, more humans, more work | Dan Shipper — read next: The 'AI psychological costs' extraction in this library (extract-psychological-costs-of-ai-*); Cal Newport on attention residue and deep work; recent labour-economics work on AI-driven work intensification (LSE, Stanford); union/works-council positions on AI workload
• illogicalThere is internal tension between (a) 'CLIs are over, GUIs win' and (b) 'agents using SaaS via CLI is how SaaS survives'. If the user's primary surface is Codex/Co-work GUI and the agent talks to SaaS over CLI, then CLIs are precisely what is preserved — they are the agent-readable API layer, not the user surface. Shipper conflates the user-surface CLI claim with the agent-readable-API CLI claim. The two are different and have opposite trajectories: the first dies, the second flourishes. The conversation does not separate them.
  The AI paradox: More automation, more humans, more work | Dan Shipper
• incompleteLarson doesn't discuss what happens to engineers whose prior differentiated value was coding speed/skill now that 'first-pass code is nearly free' — his 'development harness' framing implies a shift in what's scarce (harness quality, judgment, domain context) but doesn't say what role, if any, the formerly-valuable 'fast coder' skill now plays, or how such engineers should re-skill.
  Revised rules of engineering leadership. — read next: Pair with pieces that directly address re-skilling and the changing value of coding speed as abstraction rises.
• incompleteThe article never explains the mechanism by which employers could already be cutting entry-level hiring for AI reasons if AI hasn't yet produced measurable aggregate productivity gains — an economically odd combination that the piece flags as 'mystifying' but does not resolve.
  The loudest warning about AI and jobs yet — read next: The delayed-electrification-productivity literature (technology adoption preceding measurable output gains by years, until work is reorganized around the new capability) offers a candidate mechanism: firms can substitute on cost/headcount grounds immediately while the reorganization needed to produce measurable output gains hasn't happened yet.
• survivorship bias in the 'craft transfers' argumentBoth speakers are masters of craft who naturally see craft as the durable skill. They do not seriously consider the possibility that AI could make some craft practices genuinely obsolete rather than merely shifting them upward. Beck comes closest with his admission of grief about losing zone-flow on code, but neither explores which specific practices may not transfer.
  Martin Fowler & Kent Beck: Frameworks for reinventing software, again and again — read next: Look for empirical studies or practitioner reports on which specific engineering practices AI makes less vs. more valuable.
• vague definition of 'the middle'Beck's claim about 'the middle' being most vulnerable is stated without clear criteria. How do you distinguish someone in 'the middle' from a competent professional who simply isn't a thought leader? The framing risks becoming a circular argument: those who thrive had intrinsic motivation; those who didn't were 'the middle.'
  Martin Fowler & Kent Beck: Frameworks for reinventing software, again and again — read next: Look for more rigorous analysis of which programmer skill profiles are most affected by AI tooling.
• absence of data on team-structure claimsThe argument that pairs-plus-agents beats solo-plus-agents is based on XP philosophy and Beck's personal experience, not comparative evidence. Given that this is arguably the most consequential organizational design question in software right now, the evidentiary basis is thin.
  Martin Fowler & Kent Beck: Frameworks for reinventing software, again and again — read next: Seek out early empirical comparisons of solo-plus-agent vs. pair-plus-agent productivity and quality outcomes.
• enterprise perspective is observation without prescriptionFowler reports 'large-scale confusion and panic' and security concerns at enterprises but offers no framework for how enterprises should approach AI adoption differently from startups. The advice is pitched at individual practitioners, not organizational leaders.
  Martin Fowler & Kent Beck: Frameworks for reinventing software, again and again — read next: Look for enterprise-specific AI adoption frameworks (e.g., ThoughtWorks Technology Radar, or Fowler's own martinfowler.com posts on the topic).
• the COBOL analogy cuts both waysBeck invokes the recurring 'eliminate the programmers' dream (COBOL, etc.) as historical context, then adds 'it behooves us as programmers to think about why they keep wanting to get rid of us.' This self-critical aside is dropped immediately without exploration. The uncomfortable possibility — that some of the desire to eliminate programmers reflects genuine organizational friction caused by programmers — is raised but not examined.
  Martin Fowler & Kent Beck: Frameworks for reinventing software, again and again — read next: Consider whether the 'eliminate programmers' impulse reflects legitimate frustration with the cost and difficulty of translating business intent into code, which AI might actually address.
• incompleteThe piece names what it calls the obvious security and emergency-preparedness (beredskap) risk of deploying systems that nobody but the AI that built them understands, then explicitly declines to pursue it ('det er ikke poenget her') — leaving the single most concrete, near-term organizational risk the article itself raises completely unexamined.
  Automatisert KI-koding vil endre alt ("Automated AI coding will change everything") — read next: Material specifically on accountability, on-call ownership, and incident response for AI-authored systems that no human on the team fully understands — e.g. extract-whats-an-orchestrator-why-software-needs-one.json's treatment of accountability-through-understanding-without-reading.
• uninformedPedregal asserts as settled historical fact that labor-saving technology (the computer) has never converted into more leisure time, only more work ('People thought when the computer came out, we'd have lots of leisure — and no, the opposite happened'), without engaging that actual working-hours effects have varied sharply by income/education level rather than moving uniformly upward — the claim is offered as a flat generalization rather than examined against the split it likely obscures.
  This AI notetaker won't sell surveillance to your boss — read next: Labor-economics literature on working-hours trends by income/education cohort since the mid-20th century (e.g. the divergence between overworked high earners and underemployed lower earners), and the classic Keynes 15-hour-week prediction debate.
• incompleteNo discussion of what happens to the humans who previously handled the '70%' of first-contact interactions AI now handles — whether headcount shrank, roles were redefined, or hiring simply slowed. The episode frames AI-first adoption entirely from the operator's efficiency/growth side, never from the displaced- or redefined-labor side.
  Building an Autonomous Enterprise for Real-World Services with Netic Founder Melisa Tokmak — read next: Read against the corpus's ai-labor-disruption material for how other sources handle (or fail to handle) the labor-impact side of 'AI-first' transitions in physical/blue-collar-adjacent service work.
• incompleteThe article doesn't engage with who bears the cost during the decades-long diffusion lag it describes approvingly — Bessen's own finding is that wages stayed flat or depressed for ~50 years during the first Industrial Revolution partly because factory owners hoarded productivity gains. The optimistic framing here ('learning by doing,' 'AI-literate workforce') elides the distributional question of whether today's equivalent of 19th-century factory workers (today's junior/mid-level programmers) will see their share of the eventual gains, or whether gains will again concentrate upward during the diffusion period.
  The End of Programming as We Know It — read next: Documents in this corpus on who captures AI productivity gains at the org level (e.g. Charity Majors on junior-hiring economics, or pieces on AI and wage distribution) would sharpen this.
• 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.
• incompleteBooch's re-skilling advice ('move up a level of abstraction, start worrying about systems') is pitched at the individual, not the organization — he never discusses who funds, structures, or sequences re-skilling for displaced infrastructure/delivery-pipeline engineers, or what happens to those who can't make that jump, a gap directly relevant to teams and orgs living through this transition.
  The third golden age of software engineering – thanks to AI, with Grady Booch — read next: Look for team/org-level AI-adoption frameworks that assign leadership responsibility for re-skilling, not just individual advice (e.g. phased adoption models with explicit organizational mandates).
• 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.
• incompleteThe article asserts that entry-level engineers will be expected to hit a baseline that used to be senior/staff-level, and separately floats rigorous CS education as a possible answer to 'how does anyone become qualified' — but never designs the actual apprenticeship mechanism: if juniors no longer spend years writing code by hand under senior mentorship, what specifically replaces that as the vehicle for developing judgment about verification, architecture, and knowing when AI output is wrong?
  When AI Writes Almost All Code, What Happens To Software Engineering? — read next: Material on deliberately engineered apprenticeship/mentorship models for an AI-saturated pipeline, as distinct from pre-AI, personality-dependent mentorship.
• illogicalThe article treats the PM/engineering convergence (Section 6) as a smooth, mutually beneficial blending for both roles, but its own earlier evidence (Section 5's work-life-boundary erosion, juniors being pushed to senior-level baselines) suggests convergence could instead mean each role simply absorbing more of the other's workload without a corresponding reduction in total work or headcount pressure — the article doesn't reconcile 'teams become smaller and more efficient' (good news, Section 6) with 'tougher work-life balance' (bad news, Section 5) even though both follow from the same underlying mechanism (fewer people doing more, faster).
  When AI Writes Almost All Code, What Happens To Software Engineering? — read next: Organizational-design material on whether role convergence under AI actually reduces total workload or just redistributes and intensifies it.
• incompleteThe claim that psychological safety is negatively correlated with success is stated as a blanket assertion without evidence beyond a sports analogy (Jordan Rules). No engagement with the substantial research literature on psychological safety in knowledge work, nor acknowledgment that survivorship bias may be at play (we see the winning teams that lacked it, not the many that failed).
  Hard truths about building in the AI era | Keith Rabois (Khosla Ventures)
• incompleteThe anti-customer-feedback position is argued entirely through consumer examples (Porsche, Airbnb, DoorDash) but then extended to SMB without distinguishing where on the consumer-to-enterprise spectrum the advice flips. The Porsche example proves that stated preferences diverge from revealed preferences, not that all consumer feedback is harmful.
  Hard truths about building in the AI era | Keith Rabois (Khosla Ventures)
• illogicalThe argument that public criticism optimizes for the system while private criticism optimizes for the individual assumes a binary choice. It does not address whether the information benefits of public criticism could be achieved through other means (e.g., transparent issue tracking, team retrospectives) without the potential costs of public shaming.
  Hard truths about building in the AI era | Keith Rabois (Khosla Ventures)
• uninformedThe claim that AI writing quality degrades with length due to 'token rationing' by LLMs optimizing economics is presented as a confident theory but reflects a misunderstanding of how inference works. Output quality degradation with length has more to do with attention mechanisms, context window limitations, and the difficulty of maintaining coherence over long sequences than with deliberate economic throttling.
  Hard truths about building in the AI era | Keith Rabois (Khosla Ventures)
• incompleteThe advice to skip senior hires and develop talent internally is supported by examples from companies that had extraordinary founding teams (Ramp, Trade Republic). The selection bias is unaddressed: these companies may have been able to develop internal talent precisely because their initial talent density was exceptional. The advice may not generalize to companies with weaker founding teams.
  Hard truths about building in the AI era | Keith Rabois (Khosla Ventures)
• incompleteThe existential question about whether foundation model labs will absorb all value from application-layer AI startups is raised but never addressed. Given that Rabois is actively investing in AI companies, this is a significant gap — he identifies the question but offers no framework for how startups should think about durability against improving foundation models.
  Hard truths about building in the AI era | Keith Rabois (Khosla Ventures)
• incompleteThe 'don't talk to customers' thesis ignores the distinction between different kinds of customer input: usability testing, behavioral data, Jobs-to-be-Done interviews, and direct feature requests are very different activities with different failure modes. Rabois appears to collapse them all into one category.
  Hard truths about building in the AI era | Keith Rabois (Khosla Ventures) — read next: Teresa Torres's 'Continuous Discovery Habits' for a rigorous framework on which kinds of customer input are valuable and when; Clayton Christensen's Jobs-to-be-Done theory for a middle path between 'ignore customers' and 'build what they ask for.'
• incompleteThe PM-is-dying thesis lacks a theory of what replaces PM functions beyond spec-writing: prioritization across competing initiatives, stakeholder alignment, go-to-market coordination, and cross-team dependency management. If AI handles translation, who handles these?
  Hard truths about building in the AI era | Keith Rabois (Khosla Ventures) — read next: Shreyas Doshi's writing on PM archetypes and which PM functions are strategic vs. tactical; Marty Cagan's 'Transformed' for a model of empowered product teams that might survive AI compression.
• uninformedThe claim that CMOs will be the #1 token consumers does not engage with the possibility that AI agents (not humans) will be the primary consumers of tokens — where the distinction between 'marketing tokens' and 'engineering tokens' becomes meaningless because agents operate across functions.
  Hard truths about building in the AI era | Keith Rabois (Khosla Ventures) — read next: Anthropic's and OpenAI's writing on agentic workflows; the emerging literature on AI-to-AI communication and multi-agent systems.
• incompleteThe 24.1/25.8/50.1 split and the amplifier/delegator/apprentice behaviors are derived from a single company (KPMG) on client-engagement-style professional-services tasks; the article never addresses whether these proportions or behaviors would replicate in other industries, task types (e.g., software engineering, where an adjacent 'AI as amplifier' literature already exists), or more senior career stages.
  Research: Why Some Junior Employees Work Well with AI—and Others Don’t — read next: Cross-industry or cross-domain replications of the typology, especially in software engineering where similar amplifier/dysfunction-multiplier framings and junior-pipeline concerns already circulate.
• illogicalThe China-dominance argument compresses 'supply chain understanding' into a near-sufficient condition for long-run dominance. Other variables (capital allocation efficiency, demographics, talent migration, capability of domestic models, export-control regimes, energy supply, civil-military fusion costs) are not weighed.
  Simon Wardley's Post — Industrialisation of ML: nine notes on what to expect — read next: Read against Dan Wang on Chinese tech policy, CSIS/RAND supply-chain analyses, and any sceptical takes on PRC industrial policy execution (e.g. semiconductor self-sufficiency progress vs targets).
• incompleteThe Jevons-paradox reframing (adjacent possibles becoming real) is asserted but the conditions under which adjacent possibles actually become real industries — vs stalling — are not specified. Sometimes the adjacent possible is real and stays small.
  Simon Wardley's Post — Industrialisation of ML: nine notes on what to expect — read next: Read against the slower-than-expected industrialisation histories — early electricity (the 40-year productivity paradox), enterprise software in the 1990s. Beck and Shoup on Jevons-in-coding is a sharper instantiation of this same claim worth juxtaposing.
• uninformed (mild)The post under-weights regulatory ratchets — particularly EU AI Act, sector-specific liability regimes, GDPR-style data sovereignty rules — as climatic variables that shape what 'industrialised ML' actually looks like in different jurisdictions. Wardley's mapping treats regulation as doctrine; this post treats it as background.
  Simon Wardley's Post — Industrialisation of ML: nine notes on what to expect — read next: Read alongside EU AI Act implementing acts, NSM/Datatilsynet guidance for the Norwegian context, and Frederiksen on Coop Bank sovereignty for how an enterprise actually reasons about regulatory ratchets as architectural constraint.
• incompleteThe post is silent on the cultural and organisational variation in how 'practice converges' over the 5-8 year window. Nordic public-sector institutions, Japanese manufacturers, and Silicon Valley startups will not converge to the same practice — but the post talks as if there is one convergence trajectory.
  Simon Wardley's Post — Industrialisation of ML: nine notes on what to expect — read next: Read against Cutler on organisational operating systems and the Heis stable's Norwegian-leader interviews — concrete evidence that practice-convergence is mediated by national culture and institutional shape, not just by elapsed years.
• illogicalThe 'AI as junior developer' metaphor contains a self-defeating dynamic the author doesn't notice: if AI eliminates junior training, and seniors are needed to guide AI, then the pipeline that produces seniors is broken. The metaphor predicts its own obsolescence — eventually there are no seniors left to guide the AI-junior. This is the most consequential implication of the post and it goes entirely unaddressed.
  SMOC.AI's Post — 5 Minutter: AI og utviklere — read next: Systems thinking (Meadows) on stocks and flows — the senior developer pool is a stock that requires inflow from the junior pipeline; cutting the inflow depletes the stock over time
• incompleteThe claim that AI code quality is 'often low' is stated but not analyzed. Low in what dimension? Maintainability? Correctness? Performance? Architecture? Different quality dimensions have different implications for when and how AI should be supervised.
  SMOC.AI's Post — 5 Minutter: AI og utviklere — read next: DORA 2025 findings on AI and code quality; empirical studies on AI-generated code defect rates
• incompleteVendor incentive distortion in the 'whole ecosystem is accelerating' claim
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: DORA 2025 and the Stanford/Microsoft developer-productivity studies on AI's actual code-quality effects; Gergely Orosz on enterprise sales-cycle compression; Marc Andreessen's classic 'why software is eating the world' for the prior pattern. For the contrarian counterweight: Gary Marcus and Ed Zitron on whether the AI productivity story is being narrated by the people selling it.
• incompleteThe marginal-cost claim is accounting-incomplete (Beck flags it; Grinich doesn't return)
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Anything in your Kent Beck file on TCR and scope-of-done (this is exactly the conversation about plausible deniability and shrinking scope); Lorin Hochstein on operational complexity; the Böckeler harness-engineering extraction in this repo (the 'gap between running system and trusted system' is the harness-engineering surface). The Adam Tooze / Brad DeLong line on 'productivity gains that don't show up in the statistics' is the macroeconomic complement.
• incompleteThe 'descaling of software' counter-trend is named by Beck and left hanging
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Steve Yegge on vibe coding; Gene Kim's vibe coding series; Simon Willison on the 'no-coder using LLMs to build real software' phenomenon; the Schoening agency-over-skills extraction in this repo (the agency thesis is the descaling-friendly side of this tug of war). Honest framing: Beck's craft instincts and Grinich's institutional instincts pull in opposite directions; you may have to choose.
• incompleteGrinich's 'industrialization phase' analogy launders externalities
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Tooze on energy transitions; the IEA's compute-electricity projections; the literature on whether the late-19th-century industrialization actually 'cleaned up' or just exported externalities. For Kjetil specifically: this is the systems-thinking lens — feedback loops, stocks/flows, who absorbs what — applied to the rhetoric of inevitability.
• incompleteWhat changes about Beck specifically — the craft thinker in this regime
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Beck's own recent Substack posts (Tidy First, the 'starving genies' piece, 'forest thinning'); your highlights on Beck for where he reframes craft for the agentic era; Hickey's 'Simple Made Easy' as the substrate craft argument; Ousterhout's complexity work. The persona-relevant cross-thread: this is where Kjetil's 'fragility of ideas' hidden layer touches the AI transition — if the craft of attentive code-reading is the protected attention surface, what protects it now?
• incompleteWhat does the 'itchy brain' protect against, exactly?
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Pressfield on Resistance; Cal Newport on deep work degradation under tool proliferation; the David Whyte/Maria Popova line on the difference between making and consuming; the persona's Bailey/Hyperfocus annotations on what attention needs in order to do anything. This is where the persona's hidden layer (fragility of ideas) and the episode's title concept (itchy brain) collide — and it is the most productive question the episode opens.
• incompleteThe digest repeats Bayes's 'where's your margin once knowledge work's human contribution goes to zero' provocation without connecting it back to its own earlier picks (Hanselman's human-in-the-loop review, Yegge's hiring-signal collapse) to ask what becomes of either practice if the premise is right.
  SWLW #711: The laws of this world (game theory), Should you still become a Software Engineer in 2026, and more. — read next: extract-46-thoughts-on-the-near-future's own propositions on labor displacement and permanent-underclass risk are the natural next read for this unexamined connection.
• incompleteThe document identifies the productivity/experience paradox but offers no framework for resolving it beyond the 'agent experience' reframe. How should organizations actually measure and invest in developer satisfaction when it is decoupled from output?
  The Future Of Software Engineering — read next: DORA team's ongoing research on developer experience metrics; Nicole Forsgren's work on SPACE framework
• incompleteThe batch-size regression is flagged as an 'active regression needing industry attention' but no countermeasures are proposed beyond general governance reform.
  The Future Of Software Engineering — read next: DORA State of DevOps reports; continuous delivery literature on changeset sizing with AI tools
• incompleteThe load-bearing implicit premise — that voluntary action by incumbents, labs, and self-starting individuals can deliver the mechanism design and tidying required — goes undefended. Government, regulators, and organized labor appear only as obstacles (DOGE as wrecking ball, Kaiser nurses as bargaining problem), never as design partners. This narrows the solution space to a Silicon Valley-friendly subset.
  The Tidy House — read next: Mariana Mazzucato on the entrepreneurial/mission-driven state; Daron Acemoglu & Simon Johnson 'Power and Progress' on who captures the surplus from general-purpose technologies; recent labor-side accounts of AI rollout (Wendy Liu, Brian Merchant).
• incompleteDevoted is used as the load-bearing exemplar without examining selection effects: it was founded by a chief-data-scientist-grade leader with capital, on a fresh codebase, in a payer model with strong economic incentives for clean data. The piece does not address how a 40-year-old hospital with EHR debt and 30% volume drops gets to the tidy house from here.
  The Tidy House — read next: Healthcare IT case studies on EHR modernization (e.g., Epic-on-FHIR transitions); writings on technical-debt-laden AI adoption (Will Larson, Charity Majors on infra readiness); McKinsey/Bain healthcare AI deployment reports for contrast.
• incompleteThe 'layers above the model' thesis is asserted as a strategic forecast but not differentiated from prior hype cycles (each platform era has claimed value would accrue above it). The conditions under which model-layer commoditization actually occurs in 2026 are not examined — particularly given vertical integration trends and shrinking margins above commodity inference.
  The Tidy House — read next: Recent writing on harness/orchestration economics (Simon Willison, Will Larson on platform engineering); Ben Thompson on aggregation vs. integration in AI; the Anthropic / OpenAI app-layer move (e.g., Skills, agents).
• incomplete'Mechanism design' is used loosely — slipping between an economist's formal sense (incentive-compatible institutions) and a technologist's informal sense ('design good defaults'). The article doesn't distinguish which kinds of failures voluntary mechanism design can solve and which require collective enforcement.
  The Tidy House — read next: Hurwicz/Myerson on mechanism design; Elinor Ostrom on commons governance; Lessig 'Code is Law' for the techno-determinist counterweight.
• incompleteLabor's role is undertheorized. Kaiser nurses appear as an example of resistance triggered by bad lab narrative — but unions could equally be co-designers of the 'use AI to remove BS, not workers' bargain the piece advocates. The asymmetry — labs need persuading via mechanism design, labor needs persuading via better narrative — is unexamined.
  The Tidy House — read next: Writers Guild AI agreement post-mortems; Daron Acemoglu interviews on shared prosperity; Aaron Benanav on automation discourse vs. labor reality.
• incompleteThe article names 'underwriters,' 'directors,' and organizational balance sheets as the abstractions that absorb verification's costs, but never addresses who actually performs day-to-day verification labor, how that labor is staffed and trained, what it costs relative to the generation it checks, or whether verification becomes a distinct new profession with its own training pipeline and wage floor. The individual-strategy section advises readers to become directors or underwriters, but doesn't address the (larger) population of people who will do verification work without occupying those elevated roles.
  When AI can do more than we can check — read next: Read labor-economics treatments of AI verification/oversight roles and wage-premium data for reviewers, auditors, and QA-adjacent professions under AI-driven volume increases.
• evidentiaryThe 100x token economics claim is asserted but not rigorously derived. Anthropic's revenue growth could reflect pricing strategy, API volume, or contract structure rather than inherent per-user value differences.
  Who Cares About Consumer AI?
• analyticalThe ads math assumes Google-level ad revenue per user is achievable for AI chat interfaces, but AI conversations are structurally different from search (fewer commercial-intent queries, different attention patterns). No evidence is given that AI ad inventory can match search ad inventory.
  Who Cares About Consumer AI?
• analyticalChesky's consumer renaissance prediction is presented without interrogation. The structural barriers he identifies (no business model, design gap, trend-following culture) are not shown to have a clear resolution mechanism within 12-24 months.
  Who Cares About Consumer AI?
• scopeNo discussion of non-US consumer AI markets, where ad economics differ radically and subscription willingness may be lower.
  Who Cares About Consumer AI?
• analyticalThe newsletter does not consider whether consumer AI could generate value through data/behavioral signals rather than direct monetization, which is Meta's actual historical model.
  Who Cares About Consumer AI?
• misinformedThe opening hook's claim that reading the article digitally (via a browser) necessarily means 'you have just used' cURL overstates cURL's role in that specific pathway -- most mainstream web browsers use their own networking stacks rather than libcurl to fetch web pages, even though cURL genuinely is extremely widely embedded elsewhere (package managers, command-line tools, embedded devices, app backends). The framing conflates cURL's real, vast reach with a specific, likely inaccurate claim about browser page-loading.
  Who cleans up after the vibe-coding party? — read next: cURL's own documentation on where libcurl is and isn't actually used (browsers vs. tooling vs. embedded systems) for a precise picture of its footprint.
• illogicalThe argument that reduced engineer hiring reflects democratization (optimistic read) rather than declining demand (pessimistic read) rests on Robert C. Martin's developer-doubling extrapolation, which is rhetorical and does not actually adjudicate between the two readings — the same hiring data is consistent with both.
  Why did Martin Fowler invite 60 engineers to a ski resort? — read next: Read labor-market analyses that separate 'demand for software' from 'demand for professional engineers' with evidence rather than extrapolation.
• incompleteThe 'you don't get to create anything' extension to AI is never made explicit
  You Don't Get to Create Anything (Still Burning: Beck + Randy Shoup on Jevons paradox and distributed systems under AI) — read next: Beck's own Substack on 'starving genies' and the human's relationship to the genie's outputs; Cal Newport's deep-work tradition on how the substitution of tool-mediated production changes the nature of the work; Pressfield on Resistance; and — the persona-relevant cross-thread — the 'fragility of ideas' hidden layer in Kjetil's reading: if the maker-compulsion is the durable substrate, what does it look like when the agent satisfies it without you having moved? This is the productive question the episode leaves on the table.
• incompleteThe Jevons-on-cognition forecast is asserted, not argued through to its qualitative differences
  You Don't Get to Create Anything (Still Burning: Beck + Randy Shoup on Jevons paradox and distributed systems under AI) — read next: Carl Benedikt Frey 'The Technology Trap' on the political economy of transitional displacement; Brad DeLong on what 'creating new categories of work' has actually looked like historically; Anton Korinek and Daron Acemoglu on AI-and-labor specifically. For the contrarian side: Erik Brynjolfsson on the J-curve (gains that show up late and unevenly); the Robin Hanson 'Age of Em' tradition for the qualitative-difference-of-cognition objection. Persona-relevant: DORA 2025 on AI's actual code-quality effects.
• incompleteThe playbook claim under-specifies the AI playbook's structure
  You Don't Get to Create Anything (Still Burning: Beck + Randy Shoup on Jevons paradox and distributed systems under AI) — read next: Hamel Husain on evals; Simon Willison on the working LLM-augmented practitioner's actual playbook; Addy Osmani and the Claude Code patterns crowd; the Bernhard / Bockeler / Thoughtworks harness-engineering thread already in this repo; the Heis ep 11 AI-special with Vilde Opsal and Anders Sveen for the Norwegian practitioner cut; the Heis ep 13 Torrissen for code-quality-under-AI. This is exactly where 'craft transmission for the next era' lives — and where the conversation is most incomplete.
• incompleteThe 'apprenticeship channel under 50:1 manager ratios' problem from the prior Still Burning episode is not picked up
  You Don't Get to Create Anything (Still Burning: Beck + Randy Shoup on Jevons paradox and distributed systems under AI) — read next: John Cutler on overload and DRI dynamics; Will Larson and Tanya Reilly on engineering-org structure; the Heis ep 13 Torrissen extraction for the Norwegian practitioner take on code-quality and craft transmission under AI. Persona-relevant: the 'fragility of ideas' layer — ideas die at the institutional adoption point if the apprenticeship channel is gone.
• incompleteShoup's 'make it easy, don't shame' principle is stated as climate policy and not applied to software craft
  You Don't Get to Create Anything (Still Burning: Beck + Randy Shoup on Jevons paradox and distributed systems under AI) — read next: Cutler on operating-system design and waste; Thaler and Sunstein on choice architecture for the foundational behavioral-economics text; Kniberg on Spotify's model as an example of friction-reduction at scale. Persona-relevant: this is exactly where Kjetil's leadership-vs-management orientation and his Cutler-deep reading already live.
• incompleteThe 'distributed-systems-playbook-writers as exemplars' framing implicitly leaves out the playbook that didn't get written
  You Don't Get to Create Anything (Still Burning: Beck + Randy Shoup on Jevons paradox and distributed systems under AI) — read next: Schneier on security (in Kjetil's RSS); the Ruined by Design / Mike Monteiro line on what professionals fail to write playbooks for; the Norwegian intelligence reports (NSM, PST) for the security-and-resilience perspective; recent regulatory writing on AI-and-governance for what is being written by non-engineers because engineers didn't write it.
• incompleteThe Beck-as-inductive vs. Shoup-as-deductive split is named but not connected to the playbook-writing claim
  You Don't Get to Create Anything (Still Burning: Beck + Randy Shoup on Jevons paradox and distributed systems under AI) — read next: Anything on creative-cognitive partnerships at scale: Brian Eno's 'scenius' concept, Anne Lamott on the writer-editor pairing, the literature on the pair-programming and mob-programming traditions in software. For the temperament-and-craft thread specifically: Beck's own writing on the craft of seeing simple design where others see complexity.
• incompleteNo evidence is offered within the piece for the central historical claim — 'professions that tried to hold their ground with rules alone usually lost it anyway; the ones that survived redrew their own claim.' No named case studies (from Abbott's actual book or elsewhere) are given; the generalization is asserted as a settled summary.
  You won’t get replaced. You’ll get skipped. — read next: Read Abbott's The System of Professions directly for the actual case studies (e.g., psychiatry vs. clinical psychology, or accountants vs. lawyers over tax work) to check whether 'redrawing jurisdiction' was really the differentiator between professions that held ground and those that didn't, or whether other factors (capital, state licensing power, timing) did the real work.
• illogicalThe advice to 'claim the new ground before someone else does' treats the three jurisdictional arenas as independently exploitable by an individual solo lawyer — but the piece's own framework says the arenas interact. Unauthorized-practice-of-law rules (the 'law' arena) may legally bar a solo lawyer from expanding into adjacent non-legal services even where public opinion and technical capability (the other two arenas) would support it; the practical advice doesn't reckon with this internal tension.
  You won’t get replaced. You’ll get skipped. — read next: State unauthorized-practice-of-law (UPL) statutes and recent UPL enforcement actions against AI-adjacent legal-services offerings, to see how binding the 'law' arena actually is against the kind of scope expansion this piece recommends.
• incompleteThe piece's own P.S. — plugging the paid 'Inner Circle' community that teaches 'which AI tools are worth your time' — is a live instance of exactly the thesis it just argued: an attempt to claim new jurisdiction (over 'how lawyers should adopt AI') before someone else does. The piece never flags this self-referential application of its own framework to its own business model.
  You won’t get replaced. You’ll get skipped. — read next: None needed — this is an internal-consistency observation about the piece itself rather than a topic requiring outside reading.