Coding at work (after a decade away)

Overview A senior engineering leader shares his experience of stepping back into code contributions after a decade of focusing on management. He examines why writing code as a manager can feel low-return, how it impacts decision-making, and the personal and team benefits of staying technically engaged.

Key Takeaways

• Writing code as a manager often yields lower business impact than hiring or planning, but it can improve personal insight and credibility.
• Small, focused coding tasks can be fit into limited time pockets without disrupting team rhythm.
• Understanding the codebase deeply helps make faster, higher-quality decisions.
• Balancing manager duties with occasional coding can mitigate burnout and keep technical skills sharp.

Who Would Benefit

• Engineering managers and directors contemplating coding work.
• Senior engineers transitioning to leadership roles.
• Leaders seeking strategies to maintain technical relevance.
• Teams looking to improve decision-making efficiency.

Frameworks and Methodologies

• Time-boxing technical work within manager schedules.
• Leveraging strong engineers for knowledge transfer.
• Prioritizing high-impact activities over low-return coding.