# Engineering Managers Are Back in the Codebase (LeadDev) > [!info] Machine-mediated deep-read — not the author's words except inside quote blocks. > Ported from an existing Readwise deep-read for doc `01kzp1fsk531rcm6jkm7p95sr3`. A Permanent note from this exact source already exists in the vault ([[3. Resources/Permanent Notes/Managers Should Code Off the Critical Path]]) — this Literature Note fills the missing intake step, not a new claim. > [!question] Lingering Questions > - What counts as "hands-on technical work" in the Engineering Leadership Report 2026 — commits, code review, architecture docs, pairing? The article never defines it. > - Is the EM coding increase concentrated in AI-native startups, or broad-based across enterprise/legacy orgs too? > - Does AI-assisted EM code get the same review scrutiny as IC code, or does manager authority create a review-rigor gap? > [!tip] Article Ideas > - None distinct from the already-captured claim; see the existing Permanent note. > [!link] Cross Reference > - [[3. Resources/Permanent Notes/Managers Should Code Off the Critical Path]] — the claim this source already generated > - [[3. Resources/MOCs/Product & Startup Instincts MOC]] > [!quote] Vocabulary > - *player-coach* — a manager who both codes ("plays") and leads people ("coaches"); term from Gergely Orosz's 2024 Pragmatic Engineer prediction, now measured as a 2026 statistical pattern ## Metadata - Source: [[3. Resources/Readwise/Articles/Engineering Managers Are Back in the Codebase]] ## Author's thesis LeadDev's 2026 survey shows engineering-manager hands-on coding time rose from 20% to 35% year-over-year (with increases across every leadership tier), attributed to AI coding tools lowering the skill/time cost of producing working software — but practitioners quoted warn the healthy version of this trend stays bounded to non-critical-path, unblocking work rather than reverting managers to IC output. ## Key arguments (≤3) 1. **The statistical pattern is the strongest evidence, not the celebrity anecdotes** — convergent increases across tech leads (41%), managers of engineers (31%), managers of managers (30%), and CTOs (44%) make a single-cause explanation more plausible than the Zuckerberg/Brin anecdotes alone, which are flagged as survivorship-biased illustrations. 2. **The causal mechanism is asserted, not demonstrated**: the article never discloses survey methodology (sample size, selection, operational definition of "hands-on technical work"), so the AI-adoption-causes-EM-coding link is plausible but unverified. 3. **The guardrail is operational, not just aspirational**: Williams' "non-critical-path work" filter gives a concrete boundary — code to unblock, not to gate the roadmap. ## Claim atoms ### EM hands-on coding jumps from 20% to 35% in a year > [!quote] ID:rw_01kzp1fsk531rcm6jkm7p95sr3-h1 > Among engineering managers specifically, the share rose from 20% in 2025 to 35% in 2026. **Context & use**: The central statistic supporting the whole piece's thesis; anchor for the "player-coach becomes reality" claim. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> ### AI lowers the barrier from idea to working software > [!quote] ID:rw_01kzp1fsk531rcm6jkm7p95sr3-h3 > AI has drastically lowered the barrier to entry for turning an idea into working software **Context & use**: Emma Bostian (Spotify EM) — the article's stated causal mechanism for the coding-time increase. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> ### EM's core job is vision, not code output > [!quote] ID:rw_01kzp1fsk531rcm6jkm7p95sr3-h4 > the primary role of the engineering manager is to set the vision, work with stakeholders to define the requirements, be responsible for gaining consensus around nuanced decisions **Context & use**: Paul Williams (Bloomberg) — the article's counterweight/guardrail claim, and the source of the already-captured Permanent note's evidence. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> ## Permanent candidates - **Already captured**: [[3. Resources/Permanent Notes/Managers Should Code Off the Critical Path]] — this is the source's central actionable claim, already a Permanent note in the vault. Not re-created. ## Processing checklist - [ ] Check LeadDev's Engineering Leadership Report 2026 methodology before citing the 20%→35% stat elsewhere - [x] Connect into the relevant MOC — [[3. Resources/MOCs/Product & Startup Instincts MOC]] - [x] Confirmed existing Permanent note already covers the central claim — no duplicate created ## Links - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — engineering-management trend data - [[3. Resources/Permanent Notes/Managers Should Code Off the Critical Path]] — because evidence-for: this note's own Evidence section already cites this exact source