Systemic Apprenticeship & Skill Transmission

Deliberately engineering apprenticeship into everyday work — senior-as-teacher role expectations, deliberate exposure to higher-stakes decisions, systematic (not personality-dependent) mentorship — as the mechanism by which junior/emerging talent acquires craft, distinct from episodic training programs.

Also known as: apprenticeship, apprenticeship pipeline, junior development, skill transmission, craft transmission, teaching in the flow of work, development happens in the work

Documents (22)

• Redefining the Software Engineering Profession for AI Mark Russinovich and Scott Hanselman · 2026-10-08 source ↗ Reader 🖥️
  Because generative AI amplifies senior engineering judgment while penalizing early-in-career developers, organizations must deliberately keep hiring and investing in EiC engineers through a structured 'preceptorship at scale' system -- senior mentors paired with AI tooling designed to teach, not just produce -- or the profession's talent pipeline will collapse.
• 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.'
• Andrew Kelley Interview: Why He Built Zig, Banned AI Contributions, and Moved Zig off GitHub Bruno Couriol · 2026-09 Reader 🖥️
  Because AI-generated open-source contributions are reliably low-quality and net-negative once maintainer review time is counted, and because code review is really an investment in cultivating future human core contributors rather than a pure quality filter, healthy open-source governance requires categorically banning AI-assisted contributions and preferring infrastructure (Codeberg over GitHub) whose institutional incentives favor long-term stability over corporate growth pressure.
• Agentic Skill Decay AddyOsmani.com · 2026-08-31 source ↗ Reader 🖥️
  Agentic coding collapses the loop from problem to working patch so fast that it strips out the incidental struggle (debugging, reading diffs, forming and testing hypotheses) that used to build engineering expertise as a side effect of the work itself — so practitioners must now deliberately reinsert that practice, because the very expertise agents make optional is what increasingly determines whether you can verify and direct what an agent produces.
• LIVE: Uncle Bob on Software Fundamentals in the Age of AI Matt Pocock (host) with Robert C. Martin ('Uncle Bob') · 2026-08-19 source ↗ Reader 🖥️
  Software fundamentals (clean, well-partitioned, deeply-structured, well-tested code) matter just as much in the agentic era as before — not despite AI's speed but because of it — because agents hit the same complexity wall humans always have, just at a different threshold; the right response is not to impose human disciplines (like strict line-by-line TDD or heavyweight upfront specs) on agents, but to encode human values as deterministic, automated gauntlets (crap scores, mutation testing, dependency rules) that agents must pass through, while reserving strategic judgment — architecture, module boundaries, what's worth building — for humans who must now learn that judgment by experiencing the agents' own tactical gauntlet.
• Can an AI-Powered Scribe Curb Physician Burnout? HBR.org · 2026-08-18 source ↗ Reader 🖥️
  An AI ambient scribe can measurably reduce clinician burnout by removing documentation burden and restoring undivided attention to patients, but the benefit is fragile — it depends on the organization deliberately protecting the freed-up time, resolving physicians' loss of authorship/identity over their own notes, earning genuine patient and physician trust in a black-box system, and confronting (without yet answering) what happens to the training of clinicians whose on-ramp task is being automated.
• Teaching Coding When AI Can Write the Code Eric Freeman · 2026-07-28 Reader 🖥️
  Because AI has severed the link between a finished piece of code and evidence of the student's understanding, coding education must shift its center of gravity from grading the finished artifact to making the process of thinking — explained, revised, and performed in public — the thing that is observed and assessed.
• What Makes Chinese Companies So Competitive? HBR IdeaCast (hosts Alison Beard and Adi Ignatius, guest researcher Dan Wang) · 2026-07-28 Reader 🖥️
  China's competitiveness comes not primarily from cheap labor, IP theft, or subsidies but from operating as an 'engineering state' that has preserved a dense, tacit 'process knowledge' industrial ecosystem the US allowed to atrophy — a real technocratic strength that coexists with, and does not translate into, either political predictability for entrepreneurs or a better quality of life for ordinary Chinese workers.
• Why Mentoring Matters More in the AI Era Marlo Lyons · 2026-07-24 Reader 🖥️
  Because AI is automating the routine work that once built professional judgment and pattern recognition through repetition, organizations must replace that lost experiential foundation with deliberately engineered, intentional mentoring — not the ad hoc, exposure-dependent mentoring models that assumed hands-on learning was already happening.
• Leadership Summit 2026: Inspiring Grit and Growth Amid Unprecedented Change HBR.org · 2026-07-23 Reader 🖥️
  AI's effect on human skill and grit is not fixed by the technology itself but by whether people treat it as a coach to learn from (attending to and imitating its superior output) rather than a crutch to passively accept, and by whether they also deliberately design their surrounding situation — mentors, teams, culture — since grit (steadfast top-level goals, agile tactics) is necessary but not sufficient for excellence.
• How Do You Know That? Kent Beck — Still Burning Podcast · 2026-07-22 Reader 🖥️
  The skill that matters most — in engineering craft, in working with AI agents, and in locating accountability when automated systems act — isn't knowing the answer but asking 'how do you know that?': interrogating the actual reasons behind behavior, code, and systems, because that meta-intelligence diagnoses root causes invisible to observers of behavior alone, and because AI agents, having no drive or accountability of their own, can never do that interrogating or that owning on a human's behalf.
• 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.
• Should You Still Become a Software Engineer in 2026? GitHub VP Jean Lee (interviewer); Scott Hanselman (guest, VP & Member of Technical Staff, Microsoft/GitHub) · 2026-06-25 source ↗ Reader 🖥️
  AI coding agents are the latest in a recurring cycle of developer 'power tools' that change the tools but not the craft or its human accountability, so the real risk of the AI era is not that engineers become obsolete but that the profession fails to deliberately re-engineer its junior-to-senior training pipeline (via something like nursing's preceptor model) before AI hollows out the tasks juniors traditionally learned on.
• Engineering Leadership Report 2026 Postman · 2026-06-05 Reader 🖥️
  Engineering leadership is undergoing genuine, compounding transformation — organizational flattening (now reaching upper management), expanding technical-plus-managerial scope, and AI adoption that has outpaced governance and measurement — and the organizations that come out ahead in 2026 will not be the ones that adopted AI fastest but the ones that built the trust, clarity, and investment in people that let AI amplify rather than erode human capability.
• 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.
• How to Turn Individual Talent into Organizational Excellence Harvard Business Review · 2026-03-12 Reader 🖥️
  Sustained organizational excellence is produced not by individual talent, hiring, or motivation but by a deliberately designed system in which talent development, socially-enforced team standards, and disciplined recurring routines reinforce one another.
• 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.
• The Bet On Juniors Just Got Better Kent Beck (Software Design: Tidy First?) · 2025-12-12 Reader 🖥️
  Because AI coding assistants used as 'augmented coding' tools compress a junior developer's ramp-to-profitability and make it more likely they survive the unprofitable early period at all, hiring juniors is now a better economic bet than before -- not a worse one -- provided organizations deliberately manage them for learning rather than production.
• State Of AI-Assisted Software Development DORA · 2025-09-23 Reader 🖥️
  AI's effect on software delivery is not a property of the tool but of the organizational system it is embedded in: across nearly 5,000 developers, AI consistently amplified whatever team dynamics already existed — toward 'harmonious high-achievement' or toward a 'legacy bottleneck' — and organizations only convert individual AI-driven effectiveness gains into durable team, product, and organizational performance by deliberately building a cluster of systemic capabilities (AI-policy clarity, data health, version-control discipline, small batches, user-centricity, and platform quality) and treating AI adoption as a whole-system transformation rather than a tooling rollout.
• How AI will change software engineering Kari McMahon · 2025-04-14 source ↗ Reader 🖥️
  Generative AI is changing software engineering fast enough that confident predictions about the field's future are themselves unreliable, so engineers and organizations should focus less on forecasting the end-state and more on adapting skills, protecting junior pipelines, and treating the engineering team (not the individual) as the unit that has to stay productive.
• Generative AI Is Not Going To Build Your Engineering Team For You Charity Majors · 2024-06-10 source ↗ Reader 🖥️
  Generative AI accelerates the easy, narrow, disposable part of software engineering (writing code) but does nothing for the hard part (building and operating the sociotechnical systems code lives in), so it cannot substitute for hiring and apprenticing junior engineers — teams, not individuals, are the real unit of software ownership, and starving the junior pipeline is cannibalizing the industry's own future senior engineers.

Propositions touching this concept (5)

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

2024-06

• explicitcorroboratedThe 'generative AI is like an excitable junior engineer' analogy only holds for disposable, self-contained code never meant to be integrated into a larger body of work or maintained by others — which is a narrow and atypical case; for ordinary production code the analogy fails because AI provides no feedback loop, no apprenticeship relationship, and no contribution to team culture.
  Generative AI Is Not Going To Build Your Engineering Team For You · p4

2025-04

• explicitSoftware engineering is an apprenticeship industry where the team, not the individual, is the unit that has to be productive — optimizing for the cheapest individually-capable hires while ignoring the team as a system is short-sighted.
  How AI will change software engineering · p4
• implicitSenior developers are becoming more reluctant to mentor and oversee juniors on complex tasks now that AI tools are available as an alternative source of help, which further erodes the informal apprenticeship relationship juniors depend on.
  How AI will change software engineering · p7

2025-09

• explicitestablishedDefault AI usage patterns disrupt the traditional three-generation (junior/mid/senior) apprenticeship model, because experts can now self-serve answers from AI and therefore stop creating the hands-on, high-stakes opportunities junior engineers historically needed to develop tacit skill — a pattern Matt Beane has documented across more than 31 occupations and now sees emerging specifically in software engineering.
  State Of AI-Assisted Software Development · p9

2026-09

• explicitcorroboratedDeliberately engineered 'synthetic apprenticeship' — using AI to generate difficult cases and adversarial scenarios, committing to a decision before seeing the answer, recording reasoning, and studying errors — can rebuild the judgment-forming function of traditional apprenticeship faster than passive content consumption, provided the exercise preserves genuine uncertainty and requires independent thought first.
  When AI can do more than we can check · p13

Open gaps (34)

• illogicalThe author asserts "the return on expertise is going up" with near-certainty, then two paragraphs later states "I don't know how long code-level expertise will remain as valuable as it is today. Models are improving too quickly for much certainty." These two claims sit in tension without being reconciled — the confident framing needs a time-horizon qualifier the piece never supplies.
  Agentic Skill Decay
• incompleteThe entire argument depends on managers deliberately redirecting AI-freed time into learning rather than production, which the piece says 'doesn't happen automatically' and 'you have to actually do it' -- but gives no structural mechanism (incentive, metric, or process) for ensuring that happens, beyond exhortation.
  The Bet On Juniors Just Got Better — read next: extract-hanselman-training-developers-ai-routine-work proposes concrete mechanisms (preceptors evaluated on mentoring outcomes rather than own throughput, 'time-to-first-PR' as an explicit morale/growth metric) that would operationalize exactly the choice this piece leaves unenforced.
• incompleteThe article proposes 3:1-5:1 preceptor ratios, a preceptor-training subset of seniors, and chat-log review, but gives no account of how preceptor duties are resourced against individual performance metrics, promotion criteria, or the same AI-boosted throughput expectations now applied to seniors -- the exact incentive misalignment the article diagnoses as the cause of the junior-hiring collapse.
  Redefining the Software Engineering Profession for AI — read next: Hanselman's own earlier remarks (in extract-hanselman-training-developers-ai-routine-work) go further on this specific point -- proposing that preceptor performance be evaluated on how well they mint new seniors, not on their own output -- which this ACM piece doesn't restate.
• incompleteThe trainee/apprenticeship dilemma is named as genuinely open ('either way, you have to consider the pros and cons') but neither speaker proposes even a candidate resolution, a pilot program, or a way to test the two options empirically.
  Can an AI-Powered Scribe Curb Physician Burnout? — read next: Read extract-hbr-mentoring-matters-ai-era, which at least prescribes structured mentoring mechanisms (named competencies, protected time, narrated decision-making) as a partial answer to the same on-ramp problem in other knowledge-work professions.
• incompleteThe 'code review is overrated' claim is offered as a contrarian one-liner with no supporting evidence (defect rates, incident postmortems, comparative studies of eval-only versus human-reviewed pipelines), and does not address what happens to junior engineers' skill formation if review — historically a primary mechanism by which junior engineers learn to read and critique code — is deprioritized. This gap is made sharper by the episode's own timestamps listing a 'Junior engineers' segment (1:16:31) that this takeaways article does not summarize at all.
  Stop being skeptical about AI for development with Charity Majors — read next: The podcast's own 'Junior engineers' segment (unsummarized here); this corpus's systemic-apprenticeship material on skill transmission mechanisms.
• incompleteThe DORA AI Capabilities Model's seven capabilities — the report's headline, survey-validated deliverable — include no apprenticeship or skill-transmission capability, even though Matt Beane's own essay in the same report argues default AI use measurably erodes the junior-to-senior pipeline across many occupations and (early signs suggest) in software engineering too. The model and the warning sit side by side without being reconciled.
  State Of AI-Assisted Software Development — read next: Track whether DORA's next annual survey operationalizes a skill-development or apprenticeship-health measure as an eighth capability; read Matt Beane's ongoing SkillBench research directly for software-specific findings.
• incompleteThe post quotes all five Thoughtworks headline findings up front but only substantively elaborates two of them (the executive/engineer expectation gap, and — thinly — verification-as-bottleneck via the sensors/feedback theme). 'Harness engineering,' 'the apprenticeship crisis,' and 'legacy modernization' are named but never discussed anywhere in the body text that follows.
  Fragments: July 21 — read next: Read the full Thoughtworks PDF report directly for the elaboration this fragment post doesn't provide, and cross-reference this corpus's existing harness-engineering syntopical map and extract-fowler-fragments-july-6 for adjacent material from the same retreat series.
• 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.
• incompleteThe preceptor proposal is evaluated only on the promise that preceptors will be 'metriced' on 'how well they train people,' but no metric is actually specified beyond the anecdotal claim that Microsoft's 'first cohort of preceptors... has been very successful' and the qualitative 'engineering thrive'/time-to-first-PR framing, which is itself explicitly described as a morale signal, not a competency signal. There is no description of what a preceptor's performance review actually measures when it comes time to say a trainer 'shouldn't be a trainer.'
  Podcast: How Will We Train Developers If AI Does the Routine Work: A Conversation with Scott Hanselman — read next: extract-hbr-mentoring-matters-ai-era's more specified model (structured cadence, explicit competency goals, a written one-page agreement) offers a concrete alternative worth comparing against Hanselman's still-informal 'it's been very successful.'
• incompleteHanselman never addresses whether the preceptorship model as described (pairing, fellowship, code review) actually transmits architectural judgment -- the very skill he says AI cannot do -- or only reproduces the narrower skills the old toil-based system produced. If AI is already doing entry-level toil, and preceptors are pairing/reviewing rather than assigning toil, it is unclear preceptors reproduce the 'wax on, wax off' mechanism he says was essential; this is a gap between his own diagnosis (what created seniors before) and his own prescription (what he proposes now), which may be a different learning mechanism entirely.
  Podcast: How Will We Train Developers If AI Does the Routine Work: A Conversation with Scott Hanselman — read next: Look for accounts of what specifically preceptor/pairing sessions consist of at Microsoft's pilot -- do trainees do hands-on toil under supervision, or primarily observe and discuss AI-generated diffs?
• 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
• incompleteThe 'process knowledge' thesis — the claim that China's tacit industrial experience is what the US lacks and cannot quickly rebuild — rests entirely on Wang's qualitative fieldwork (conversations from 2017-2023) and a handful of named firms (BYD, Foxconn, Boeing, Intel, Detroit automakers). No comparative or quantitative measure of tacit-knowledge stock (e.g., manufacturing workforce tenure distributions, apprenticeship completion rates, factory yield/defect-rate curves) is offered to substantiate that China's advantage is systematic rather than a compelling but unverified narrative fitted to a few salient cases.
  What Makes Chinese Companies So Competitive? — read next: Industrial-economics literature on learning curves and tacit knowledge in manufacturing (e.g., aerospace and semiconductor yield-curve studies); cross-national productivity/quality benchmarking of factories; Polanyi's 'The Tacit Dimension' for the underlying epistemic claim.
• incompleteWang doesn't reconcile an internal tension: he argues prominent entrepreneurs are relocating abroad (Ma to Japan, Zhang Yiming to Singapore) to escape political risk, while also crediting China's dense, hyper-competitive ecosystem for its continued industrial dominance. He never addresses whether founder emigration is a leading indicator that erodes the same entrepreneurial/knowledge ecosystem he credits for competitiveness, or whether founders and the underlying industrial workforce are cleanly separable such that the departures don't matter.
  What Makes Chinese Companies So Competitive? — read next: Research on founder/entrepreneur emigration and its effect on domestic startup ecosystems; comparative cases (e.g., Russian tech emigration post-2022) on whether elite flight measurably weakens an economy's innovation base.
• uninformedThe entire conversation is framed as a US-China binary — 'engineering state' vs. 'lawyerly society' — with no consideration of a third model, such as European/Nordic coordinated-market economies that combine strong worker protections and rule-of-law transparency with selective industrial policy and high-quality infrastructure (e.g., Norway's state ownership stakes, German Mittelstand manufacturing). A listener outside the US is left without guidance on which elements of the 'engineering state' argument — if any — are adoptable inside a transparent, rights-based system, since Wang's framework treats the two poles as effectively exhaustive alternatives rather than a spectrum.
  What Makes Chinese Companies So Competitive? — read next: Comparative political-economy literature on coordinated market economies (Hall & Soskice's 'Varieties of Capitalism'); Norwegian/Nordic industrial-policy case studies (state ownership in Equinor, Norwegian sovereign wealth fund governance) as a test of whether infrastructure/manufacturing strength requires trading away legal transparency.
• incompleteNo measurement framework is proposed for whether the mentoring redesign is actually closing the judgment/pattern-recognition gap — the article's evidence for the six practices is experiential ('patterns I've observed'), not outcome data, despite judgment being explicitly framed as intangible and hard to assess.
  Why Mentoring Matters More in the AI Era — read next: Corpus material on AI-impact measurement discipline (e.g., extract-dx-measuring-ai-impact) applied to mentoring/development outcomes rather than coding-productivity outcomes.
• incompleteThe article calls for protected mentor time and more senior-leader involvement in daily narrated teaching, but doesn't engage the corpus's contemporaneous finding that organizations are simultaneously flattening management layers and pushing more hands-on technical work onto senior/advanced individuals — exactly the population this article expects to have spare capacity to mentor. The prescription and the structural trend may be in tension.
  Why Mentoring Matters More in the AI Era — read next: extract-postman-engineering-leadership-report-2026 (management-layer flattening + rising hands-on work among advanced/senior staff) and extract-you-dont-get-to-create-anything-beck-shoup#g4 (the apprenticeship channel under high manager-to-report ratios).
• uninformedThe prescriptions (real-time narration before/after meetings, 15-to-30-minute as-you-work reviews) implicitly assume synchronous, often co-located or at least highly available working relationships. There is no engagement with how this translates to distributed, asynchronous, or cross-timezone teams, where spontaneous narration is much harder to arrange.
  Why Mentoring Matters More in the AI Era — read next: Remote-work and asynchronous-collaboration literature; any corpus material on distributed team practices.
• incompleteThe article predicts disposable-code generation will become a general tech-literacy skill rather than a profession, with pay scales dropping accordingly, but doesn't address what happens to the career ladder into durable-code engineering if fewer people ever practice the 'easy' coding tasks that traditionally built early judgment (the same early-in-career/apprenticeship concern raised elsewhere in this corpus).
  Disposable Code Is Here to Stay, but Durable Code Is What Runs the World — read next: extract-cacm-redefining-software-engineering-profession-for-ai and extract-dora-2025-state-of-ai-assisted-software-development both address how removing hands-on, lower-stakes coding work affects the pipeline into senior/durable-code engineering.
• incompleteThe 'we're the kind of team that writes tests' plus code-review-reinforcement mechanism (takeaway 5) is described only from the leader's side, with no account of what happens when the identity claim fails to take hold — resistance, gaming (writing trivial tests just to pass review), attrition among people who don't buy in — or how dependent the tactic is on team size and existing culture.
  How Do You Know That? — read next: Change-management/golden-path literature on adoption mechanics and failure modes of intrinsic-motivation-based rollouts.
• incompleteThe article never quantifies what fraction of Zig's actual pull-request volume was AI-related before the ban, so the scale of the problem the policy was designed to solve is asserted, not measured.
  Andrew Kelley Interview: Why He Built Zig, Banned AI Contributions, and Moved Zig off GitHub — read next: Zig's own GitHub/Codeberg issue-tracker history or maintainer commentary quantifying pre-ban AI-contribution volume.
• incompleteThe specific question asked — how situational agency applies 'at scale across a big organization' and where the framework breaks down — is never actually answered; Duckworth reverts to the individual-level Phelps story rather than addressing organizational design, roles, or failure modes.
  Leadership Summit 2026: Inspiring Grit and Growth Amid Unprecedented Change — read next: Read the corpus's 'Individual Talent, Organizational Excellence' HBR piece for the systems-level, cross-role answer to this exact scaling question (talent + team + routine, with responsibility distributed by role).
• incompleteThe 'first job is murder' bottleneck is framed almost entirely through a US, Big-Tech-adjacent lens (top colleges, feeder systems, connections) without addressing how the dynamic plays out in different labor markets, education systems, or company sizes outside that frame — e.g. apprenticeship or vocational-training traditions in other countries that structure entry-level hiring differently.
  Generative AI Is Not Going To Build Your Engineering Team For You — read next: Look for comparative accounts of entry-level engineering hiring outside the US Big-Tech pipeline, or vocational/apprenticeship-model traditions (e.g. German Ausbildung, or Norwegian fagbrev-style models) applied to software.
• incompleteThe article diagnoses the problem sharply (entry gate closing, future senior shortage) but names no candidate response — no organizational redesign of junior work, no policy lever, no example of a company or sector doing this differently. It ends on the open question rather than any direction toward an answer.
  KI tar ikke jobbene, men inngangsporten — read next: Documents elsewhere in this corpus that propose concrete organizational responses to the same mechanism (e.g. protected mentor time, deliberately structured AI-free learning tasks, or redesigned internship programs) would be the natural next read.
• incompleteThe TRY examples (senior developer, strategist) are offered as illustrations of AI amplifying existing expertise, but the article doesn't explore whether an organization could deliberately engineer a substitute path to tacit knowledge once the traditional one (junior grunt work) is gone — e.g. simulation, shadowing, or AI-assisted mentorship designed specifically to transmit judgment rather than just output.
  KI tar ikke jobbene, men inngangsporten — read next: Look for proposals of a deliberately engineered 'synthetic apprenticeship' or structured AI-assisted mentorship model.
• incompleteThe article names the senior-hiring-only trend and the junior-pipeline risk as live concerns but never engages the obvious collective-action problem: if the pipeline is a shared industry resource that no single firm has an incentive to fund alone, what — beyond individual advocacy — would actually fix it? This is a question other documents in the corpus engage head-on (e.g. Majors's essay frames it as a professional-advocacy fight engineers must wage inside their own orgs).
  How AI will change software engineering — read next: Charity Majors's fuller essay, 'Generative AI Is Not Going To Build Your Engineering Team For You', develops exactly this argument with specific org-design prescriptions (team composition, ramp-cost accounting, who should and shouldn't hire juniors).
• 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.
• 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.
• incompleteThe article asserts that behavior-focused, workflow-embedded training builds 'amplifier' behaviors, citing KPMG's own program as a test case, but reports no before/after outcome data, control group, or effect size — only "early results suggest." The load-bearing premise underneath every prescription (that these behaviors are teachable and that training measurably shifts people between profiles) is asserted, not demonstrated.
  Research: Why Some Junior Employees Work Well with AI—and Others Don’t — read next: Longitudinal or intervention studies testing whether AI-collaboration training changes an individual's performance-profile classification over time; a follow-up KPMG/UT Austin publication with pre/post data.
• incompleteThe author notes it took him years of deliberate TDD practice to become good enough at software design for TDD to pay off. If agents now absorb the granular design decisions TDD used to force a developer to make, it's unclear how a less experienced engineer develops the same design judgment — the article doesn't engage with this skill-transmission question at all.
  Practices I Abandoned with Agents: An Ode to Test-Driven Development — read next: Look for work on how design judgment and apprenticeship transfer (or fail to transfer) when the granular, repetitive decisions that used to train that judgment are delegated to agents.
• incompleteThe 'treat the junior like an agent' training proposal is floated as a hypothesis with no account of retention, morale, or whether months of deliberate unproductivity is organizationally survivable at scale (cost, attrition risk, manager buy-in) — Martin does not address who absorbs that cost or how it differs from the kind of apprenticeship investment organizations are already (per other corpus material) struggling to fund even without an added 'treat them as an agent' framing.
  LIVE: Uncle Bob on Software Fundamentals in the Age of AI — read next: extract-hanselman-training-developers-ai-routine-work's preceptorship proposal and its explicit claim that preceptorship 'costs money and slows output in the short term' addresses exactly this gap with more institutional detail (named role, evaluation criteria, executive buy-in) — read together to see whether 'treat junior as agent' is a mechanism that could slot into a preceptor's toolkit.
• incompleteDirectors, underwriters, and meaning-makers are presented as durable emerging human roles, and 'synthetic apprenticeship' is proposed as the fix for the pipeline that used to produce such experts — but the essay frames this fix at the level of what organizations should build, not what an individual without organizational sponsorship (a self-taught engineer, a career-changer, someone at a firm that never rebuilds its junior loop) can do to acquire the same judgment. This access gap sits in real tension with the policy section's own later worry that augmentation available 'only to a narrow elite' could split the economy into leveraged centaurs and everyone else.
  When AI can do more than we can check — read next: Read on access and equity in AI-augmented skill formation — who gets structured simulation/apprenticeship opportunities and who is left to acquire judgment unaided.
• 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.