Staying Technical as a Tech Manager: A Practical Guide

A few months into my first management role, I counted my week. Forty hours, and I’d opened an IDE exactly once. That was to approve a PR I barely had time to read. Nothing dramatic had happened that week. No crisis, no urgent launch. The time had just quietly disappeared into things that were all individually reasonable: 1:1s, content reviews, planning docs, a strategy meeting or two.That’s the drift. It doesn’t happen in one big shove. It happens one reasonable Thursday at a time.The standard advice is to block time for code and protect it. In my experience, that doesn’t survive contact with a normal week. Protected time gets colonized. The meeting you couldn’t say no to lands on your blocked afternoon, and the precedent is set. Three weeks later, you’ve written zero code.Staying technical needs to be built into the structure of the role, not carved out of what’s left over. And the goal isn’t to match your engineers on depth. You won’t, and you shouldn’t try. The goal is to stay…