Sources & Research

Academic Research

• GitHub Copilot Impact Study (2024) (dl.acm.org): Found productivity gains but identified skill atrophy risks in junior developers
• Student Dependency Patterns in AI-Assisted Learning (IACIS 2024): Documented "learned helplessness" in students over-reliant on AI
• Junior Developer Career Trajectories with AI Tools (Software Engineering Institute): 3-year longitudinal study on skill development
• AI Impacts on Skill Formation (Shen & Tamkin, 2026) (arXiv:2601.20245): Anthropic Fellows RCT (52 devs learning Python Trio with/without GPT-4o): AI group scored 17% lower on skills quiz (Cohen's d=0.738, p=0.01) with no significant speed gain. Identified 6 interaction patterns, 3 preserving learning (conceptual inquiry, hybrid explanation, generation-then-comprehension) via active cognitive engagement.

Industry Reports

• Stack Overflow Developer Survey 2025: AI tool adoption and perceived impact on learning
• State of Developer Ecosystem 2025 (JetBrains): AI usage patterns by experience level
• GitHub Octoverse 2025: Code generation adoption rates and practices

Productivity Research

Sources for §3 The Reality of AI Productivity:

• GitHub Copilot Productivity Study (2024) (GitHub Blog): Enterprise productivity measurements with Accenture
• McKinsey Developer Productivity Report (2024) (mckinsey.com): Comprehensive analysis of AI impact across dev workflows
• Stack Overflow 2024: AI Sentiment (stackoverflow.co): Developer attitudes toward AI tools, productivity perceptions
• Uplevel Engineering Intelligence (2024): Burnout and productivity metrics with AI coding tools
• METR Experienced Developer RCT (2025) (arXiv:2507.09089): Randomized controlled trial (16 experienced devs, 246 issues, repos 1M+ lines): AI tools made developers 19% slower on familiar codebases, despite perceiving themselves 20% faster (39-point perception gap). Strongest evidence for skill atrophy risk in experienced developers.
• Borg et al. "Echoes of AI" RCT (2025) (arXiv:2507.00788): 2-phase blind RCT (151 participants, 95% professional developers): AI users 30.7% faster (median), habitual users ~55.9% faster. Phase 2: downstream developers evolving AI-generated code showed no significant difference in evolution time or code quality vs. human-generated code. First RCT to explicitly target maintainability of AI-assisted code. Co-authored by Dave Farley ("Continuous Delivery"). Note: arXiv preprint (v2 Dec 2025), not yet published in peer-reviewed proceedings.
• DORA/Google DevOps Research (2024): AI tool adoption impact on team performance

Review Load, Cognition & Recovery

Sources for §14 The Attention Cost of the Review Shift:

• Cohen, "Best Kept Secrets of Peer Code Review" / Cisco case study (2006) (smartbear.co, PDF): 10 months, ~50 developers on Cisco MeetingPlace, ~2,500 reviews over 3.2M LOC, instrumented via Code Collaborator. Defect density drops sharply past 200 LOC (no review over 250 lines exceeded 37 defects/kLOC), best detection under 300 LOC/hour, detection collapses past 60-90 minutes of sustained review. Observational, single company, pre-AI.
• Siegmund et al., "Understanding Understanding Source Code with fMRI" (ICSE 2014) (cs.cmu.edu, PDF): program comprehension recruits working memory, attention and language regions.
• Floyd, Santander & Weimer (ICSE 2017) (DOI): code review carries a neural signature distinct from prose review, modulated by expertise.
• Peitek et al., code complexity metrics vs measured cognitive load (2021) (DOI): textual size and vocabulary size predict neural and subjective cognitive load during comprehension.
• Parasuraman & Riley, "Humans and Automation: Use, Misuse, Disuse, Abuse" (Human Factors, 1997) (sagepub.com): foundational taxonomy of automation bias and complacency.
• Goddard, Roudsari & Wyatt, automation bias systematic review (2011) (PMC3240751): erroneous decision-support advice raised incorrect-decision risk ~26% versus unaided decisions. Clinical domain, mechanism transfers to reviewing generated code.
• Lee, Sarkar et al., "The Impact of Generative AI on Critical Thinking" (CHI 2025) (microsoft.com): Microsoft Research and Carnegie Mellon, 319 knowledge workers, 936 first-hand examples. Confidence in GenAI predicts less critical thinking, self-confidence predicts more. Critical thinking migrates to verification, integration, task stewardship.
• DORA, Trust in AI (dora.dev): ~39% of developers outside Google trust generative AI output "a little" or "not at all".
• BCG & UC Riverside, "AI brain fry" (2026, n=1,488 US employees): 14% report mental fatigue from AI oversight beyond cognitive capacity, 18% among developers. Managing 3+ concurrent agents raises mental effort ~14% and fatigue ~12%. Same study found AI applied to genuinely repetitive tasks correlated with ~15% lower burnout. Self-reported survey.
• "Modeling Developer Burnout with GenAI Adoption" (arXiv:2510.07435): survey-based SEM on the JD-R model. Adoption raises burnout through increased job demands, mitigated by job resources and positive perception of the tool. Preprint.
• "At What Cost? Software Developers' Well-Being in the Age of AI" (arXiv:2605.22349): literature review noting that few studies explicitly measure burnout, stress or work-life balance in AI-assisted development. Useful as an honest statement of the evidence gap.
• Wendsche & Lohmann-Haislah, detachment meta-analysis (Frontiers in Psychology, 2017) (frontiersin.org): 86 publications, k=91 samples, N=38,124. Psychological detachment associated with lower exhaustion, better sleep, higher life satisfaction (r ≈ 0.30-0.36). Heavy work investment negatively related to detachment.
• Involvement profiles in knowledge workers (Frontiers in Psychology, 2020) (PMC7205444): two Norwegian samples. The high-involvement profile (low detachment plus high autonomous motivation) scored lower on emotional exhaustion than the higher-detachment group. Counterweight to reading low detachment as burnout on its own.
• Digital Applied Q1 2026 (n=2,847 developers): 11.4h/week reviewing AI-generated code versus 9.8h writing, +31% YoY, heavy agentic users at 14-16h. Vendor survey, self-reported hours. Also cited in ops/team-metrics.md.
• Sonar 2026 State of Code: 42% of committed code AI-generated, 24% of the work week spent checking and validating AI output, 96% do not fully trust it while 48% always verify. Vendor survey.

Junior Pipeline & Labour Market

Sources for §14 The Apprenticeship Ladder Ran Through the Writing Phase:

• Brynjolfsson, Chandar & Chen, "Canaries in the Coal Mine" (Stanford Digital Economy Lab, Nov 2025) (digitaleconomy.stanford.edu): ADP payroll records covering roughly 1 in 6 US workers across 285,000 firms. ~16% relative employment decline for ages 22-25 in the most AI-exposed occupations, driven by reduced hiring rather than termination, adjusting on headcount rather than wages. With firm-time fixed effects the signal begins in 2024.
• Westby, Sasser Modestino et al. (June 2025) (PDF): 1.5M+ software developer vacancies 2021-2023, difference-in-differences with month and location fixed effects. 16.3% drop in the junior share of postings after November 2022, larger than for other computer and mathematical occupations.
• Lichtinger & Hosseini Massoum (Harvard): LinkedIn and Revelio Labs data, ~62M workers across 285,000 firms, 2015-2025. Junior hiring falls in AI-adopting firms from Q1 2023 while senior headcount rises.

Team & Organizational Research

• Create Future: AI Training Impact on Junior Developers (2025): Structured AI training raises junior time savings from 14-42% (untrained) to 35-65% (trained) on key tasks. Source for §12 Onboarding Imperative.
• Stanford Digital Economy Study (2025): Software developer employment for ages 22-25 declined ~20% by July 2025. Context for the urgency of structured junior development. understandingai.org analysis. Note: this figure is software-developer-specific and comes from a secondary analysis of an earlier draft. The November 2025 published paper reports ~16% for ages 22-25 across all most-exposed occupations, cited in full under Junior Pipeline & Labour Market.
• LeadDev: Tech CEOs reckon with AI impact on junior developers (2025) (leaddev.com): Organizational perspectives from engineering leaders on structuring junior growth in AI-heavy teams.
• Stack Overflow: AI vs Gen Z (2025) (stackoverflow.blog): Career pathway shifts for junior developers with AI adoption data by experience level.

Practitioner Perspectives

• Anthropic Claude Code Best Practices (anthropic.com): Official guidance on effective usage
• ThoughtWorks Technology Radar: AI-assisted development maturity model
• Martin Fowler on AI Pair Programming: Patterns for effective human-AI collaboration
• OCTO Technology: Le développement à l'ère des agents IA (blog.octo.com): Organizational perspective on AI-augmented development: pairs as minimal team unit (bus factor), bottleneck shifts from technical to functional requirements, junior developer integration via pair programming and deliberate practice. Managerial focus, useful context for team leads.
• Matteo Collina: The Human in the Loop (adventures.nodeland.dev): Node.js TSC Chair on the bottleneck shift from coding to reviewing. Response to Arnaldi's "Death of Software Development." Key thesis: AI amplifies productivity, but judgment and accountability remain human responsibilities. Quote: "The human in the loop isn't a limitation. It's the point." See detailed analysis.

Educational Frameworks

• Méthode Aristote (methode-aristote.fr): Hybrid human+AI tutoring model
• Bloom's Taxonomy Applied to AI Learning: Cognitive levels in AI-assisted education
• Zone of Proximal Development with AI: Vygotsky's theory applied to AI scaffolding

Methodology References

See methodologies.md for:

• TDD with AI assistance
• Spec-Driven Development
• Eval-Driven Development for AI outputs

Community Experiences

Practitioner reports from real-world usage provide empirical validation of theoretical patterns. Croce (2025)[^croce2025] documents efficiency gains for isolated algorithmic tasks (90s vs 60min average on Advent of Code puzzles), but highlights collaboration trade-offs during solo challenges: decreased team engagement, fewer creative discussions, and reduced diverse approach sharing.

Caveat: These findings are based on N=1 self-reports in competitive programming contexts (Advent of Code), not peer-reviewed research or representative production environments. The collaboration cost observed may be specific to solo challenge contexts rather than team development workflows.

[^croce2025]: https://github.com/FlorianBruniaux/claude-code-ultimate-guide/blob/af05b84fb6e32432dae2114ee2a72c44ef3d29b1/guide/roles/Steve/README.md Croce, "What I Learned Challenging Claude to a Coding Competition", Anaconda Blog, Jan 16, 2026. Field CTO perspective from 12 days of Advent of Code competition (human vs Claude Code). Reported metrics: Claude 90s/puzzle average, human 60min/puzzle average, no debugging until day 6. Note: Single-participant study on algorithmic puzzles, not production development.