3 ms·
They're not supposed to make technical decisions. What you're talking about is one person wearing multiple hats. Sure, some people can do that. But the end goal
by ilovecaching 8y ago
They're not supposed to make technical decisions. What you're talking about is one person wearing multiple hats. Sure, some people can do that. But the end goal is to have a manager that manages as his sole job. Getting your hands dirty is a bad thing. That means your spending that time doing technical work when you could be reducing friction for the team and promoting their work.
- icedchai 8y agoIf you go too far down that road, you wind up with Dilbert-style PHBs who know nothing about the work their team actually does. I'd rather someone who can get their hands dirty, help out the team if necessary.
- zeroxfe 8y agoSorry. I guess I straight up disagree with all of that. I also disagree with the notion of "sole job", which inevitably leads to "that's not my job", a common response at ossified organizations. IME, well-functioning companies are made up of flexible individuals with good judgement. Obviously, there must be a "main job" for every individual -- I think that's absolutely required. I really wish more managers would actually get their hands dirty.
- janee 8y agoImo getting your hands dirty is a prerequisite to understanding your team... and for me it's something you have to keep doing. I agree you shouldn't be the one making technical decisions, but wouldn't say DON'T get your hands dirty as a manager