3 ms·
> The pointy-haired boss is a manager who doesn't program. So > the surest way to avoid becoming him is to stay a programmer. I agree. One of the absolute wors
by breck 15y ago
> The pointy-haired boss is a manager who doesn't program. So > the surest way to avoid becoming him is to stay a programmer.
I agree. One of the absolute worst pieces of advice I got over and over again was "don't go into programming. It's all being outsourced overseas anyway. Just learn how to manage programmers." Luckily for some reason I finally decided to ignore that advice and strive to become a great programmer myself. One of the, if not the, best decisions in my entire life.
Even now, although I certainly could become more of a "manager", I choose to stay in the pit coding. Although I now do tasks that can be called "managing" such as helping out other coders with their bugs and problems, mentoring, communicating with people outside of engineering, recruiting and interviewing, the biggest chunk of my time is spent programming and working on my skills.
It's worked for PG. It's worked for Paul Farmer(replace "programming" with "doctoring"). I'd bet it's worked for nearly every master of their field. I think it's an essential rule to follow.
- kemiller 15y agoThose task are not just things that could be called "managing" they ARE managing. I think it's funny that programmers think of managing as this horrid thing outside their realm, but really, it's just the skill of working with others and extending your reach beyond your own fingers. To that end, I think PG is dead wrong. Programmers can make great managers, and find it very rewarding, even if they're not in code all day. There's as much variation in that end of the business as their is in the coding. Would you go into programming if you believed that ever job was a dead-end VB jockey? Of course not. The way to avoid being a PHB is to avoid behaving like a PHB.