AMA: GitHub Senior Director of Product Management, Julian Dunn on Developer Product Management

Quite a lot. But one has to be cautious in this and have PM exercise oversight, because not all developers are alike. Your developers may not accurately represent develop...

We divide up the team by domain area and then map existing features and area-specific outcomes to them as much as possible. Obviously, it's not always possible to create ...

Lots of changes are happening, chiefly motivated by the end of free money (i.e. post-ZIRP era) and the rise of AI. I know everyone has probably heard these two themes a m...

Quite technical, because you cannot have the requisite level of empathy for the target user, not to mention be credible with your engineering team if you aren't. Now, I d...

It can vary from not-terribly-technical to quite technical. This depends on how complex your product is and how much the nuances of that complexity matter to the user's s...

"Push back" is a strong term. With developer tools, you can't just discount what your engineering team says out of the gate, since they already have a lot of built-in emp...

I have a lot of opinions about open-source business models, many of which I am sure are not popular, but let's jump in anyway. :-) First, let's start by acknowledging tha...