Hacker News new | ask | show | jobs
by machinagod 4747 days ago
The point about prioritizing clearing road-blocks for your team cannot be underestimated, but, in my experience, with a serious caveat:

- Unless your SURE you have the time, do not put the technical task onto yourself, try to redirect.

I've made that blunder over and over again: saying "heh, I'll hack this little bit up tomorrow", and in the middle of planning, helping other people and so forth you postpone, losing the blocked developers attention and focus.

Other than that, great write-up on my job description :)

2 comments

I can't upvote you more than once, so I'll add an "amen" and a personal experience.

A while back a company where I'd been doing contract web dev work had a dual account/project management role come open and offered it to me. I'd done some client-facing work for them before and freelancing on my own, so I thought "How hard could it be?"

Two things I didn't know when I said yes:

* how much work there was for the small team in place -- and because I wasn't replaced as a technical resource, the team had just gotten smaller

* how different development and management work are in terms of headspace. It's very hard to do both simultaneously, because one job requires a lot of immersive concentration, and the other requires near continuous back-and-forth to discuss, track, and push a lot little pieces of information where they need to go.

So... I'd end up having to find non-office hours to do development work, but still had to be "on" and available during normal office hours.

I managed to keep it up for about six months. Kindof. Wouldn't recommend it, though.

Pg referred to this as Maker schedule and manager schedule

http://www.paulgraham.com/makersschedule.html

It's true all over

Yes - always good advice for Project Managers as well. Never put yourself on the critical path.