It’s a common topic. Should an engineering manager keep writing code and stay hands-on technically once they take on a leadership role? There are countless articles out there on the subject.
But what is it that makes an engineer manager ask this question in the first place? Why is it even a thing? When your main goal is to lead a team and enable other engineers to be great, why focus on work that doesn’t have the biggest impact or add the most value to your team?
From my personal experience of going down this route and asking myself the same questions, I feel there are three main reasons that motivate someone to think this way.
Report Story
