3 ms·
My understanding of what a good manager's job is consists of largely managing the interface between the team doing the tech work, and the rest of the company: e
by pavel_lishin 8y ago
My understanding of what a good manager's job is consists of largely managing the interface between the team doing the tech work, and the rest of the company: ensuring there's no external blockers, making sure that requirements are accurate, that realistic expectations are being communicated in both directions, etc.
I don't imagine it as someone whose job it is to ask me once an hour, "so how's it going, can you code any faster?"
- DanielBMarkham 8y agoYep. Clearing obstacles and managing externals -- although once you give somebody the title there seems to be a lot more involved. The good managers I've seen don't talk a lot. The best managers are developers who have a natural skill for the work and got voted into the job, They do that obstacle-clearing and coordination on an as-needed basis, working alongside everyone else the rest of the time. The core of the problem is that tech development involves way more skills than there are people, no matter how you want to slice them. When you go for training or start putting folks in roles, the assumption is that your role is at the center of the org. Not the value creation stream. There's an oversimplification and false focus that occurs that's antithetical to getting things done. So yes, that's the manager's job. But it rarely stays like that.