[ChrisMarshallNY]

Good list, but...

> Can do your job if you end up rage quitting, getting sick or just needing a day off and there's an emergency.

I'm not sure that we really want our managers getting into our code.

At my company, the company actively worked against managers, being technical. I had to "sneak" my tech, by doing open-source projects, on the side (no I didn't have a "shower clause" in my employment contract).

I'd say that it's a better bet that the manager knows who to grab, and stick on your project, until the leaks get caulked.

[zer00eyz]

I agree! As a manager you should probably not be coding (depends on org size). A manager doing a lot of coding is a good way to commit the sin of "making your team manage up".

However: as a manager if you can't do your staffs job you should not be managing that team. You would be unable to settle technical disputes, or properly assess your staff. You would not know who to grab and shove in the void.

So I'll restate it as such:

Can do your job if you end up rage quitting, getting sick or just needing a day off and there's an emergency. Knows enough NOT to make their team manage them.

[hiatus]

I'd say the difference between knowing who to grab and getting your hands dirty as a manager tends to be a function of company size, with the latter being more likely the smaller the company.