# Managers Should Code Off the Critical Path ## Claim An engineering manager's hands-on coding should improve technical awareness without putting delivery on the critical path. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - This holds when coding helps a manager test assumptions, build a proof of concept, or unblock work without taking ownership away from the team. - It fails when the manager becomes another individual contributor whose availability gates a release or whose commits escape normal review. - The source reports a rise in managers doing hands-on technical work, but it doesn't establish that AI caused the increase; that causal claim remains provisional. ## Evidence [[3. Resources/Readwise/Articles/Engineering Managers Are Back in the Codebase]] reports that engineering managers doing hands-on work rose from 20% in 2025 to 35% in 2026. The practitioners quoted keep the manager's primary responsibility on vision, stakeholder alignment, consensus, and team growth, with coding used for non-critical-path work. ## Links - [[The Bottleneck Moved From Code Generation to Review and Judgment]] — applies-in: manager code that adds review load or becomes release-critical worsens the scarce part of AI-assisted delivery. - [[Code Review Is a Human Knowledge-Transfer Ritual Not Just a Quality Gate]] — because a coding manager should participate in the team's review and learning system rather than bypass it through authority. - [[AI Tools Don't Eliminate the Apprenticeship Layer They Relocate Its Cost]] — because managers staying technically credible can support formation only when their coding leaves room for engineers to own consequential work. - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — applies-in: the MOC lists this note under Judgment, review, and taste as the new bottleneck. - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — applies-in: the MOC lists this note under Synthesis additions (2026-08-16 — ownership & delegation).