For a dev-PM - how do you decide how deep to go into a topic?

1 min read

bike balance

This situation just came up in one of our teams. We just promoted a developer to do management tasks and slowly become a technical PM.

He started going less deep into topics and tried to get more of an overview on things.

One question came up:

How do I balance development with management work?

Are there any best practices on it?

My first take was this:

Things not to do

No algorithmic work that needs deep focus for hours on end.

No critical work, which has a tight deadline.

Things to do

Pair programming under the lead of a coworker.

Smaller tickets that don’t require much time, but would not be fun for a full developer to do. Examples: I18n

Till Carlos

I'm Till, a senior developer who started a software company. I explain software concepts for people in supervising / leading roles.