4 ms·
> You can average it out at 30% of the time, but in a given week, you can't commit to it, because a greater responsibility of your job is being available to man
by jasonwocky 13y ago
> You can average it out at 30% of the time, but in a given week, you can't commit to it, because a greater responsibility of your job is being available to manage the unexpected
I'd argue that your job is to teach others how they can best manage the unexpected. Then you should only be involved in the really exceptional circumstances, allowing you more time to tend to your (metaphorical) garden at work. If writing code is part of that, so be it. But the bulk of time, I'd argue, ought to be in mentoring others.
The best managers I've worked with don't run around like chickens with their heads cut off, constantly responding to fires.
- gaius 13y agoDepends what you mean by "fires". If a customer comes along with a new requirement, how do you predict that? Then your job is figuring out if it can be done, the best way to do it, if you have people free to do it and test it, if doing this for customer A will have any impact on customers B-Z, if there are any currently in-progress features you could or should cut to work on this, whether to push back on the customer and say, not in this release and how to do that without disappointing them too much, etc etc etc. Basically a manager's role includes being the interface between his team and the outside world, and the outside world is by its very nature chaotic.