3 ms·

First, you need to learn the skills and work of managing a software team. I just wrote about it here: https://www.linkedin.com/pulse/real-work-management-marc

First, you need to learn the skills and work of managing a software team. I just wrote about it here: https://www.linkedin.com/pulse/real-work-management-marcus-blankenship?trk=pulse_spock-articles https://www.linkedin.com/pulse/real-work-management-marcus-b... Second, the best thing you can do for your career is the hard work of turning your team of "mediocre programmers with broken culture" into something great. It's hard work, but it can be done, I promise. I write more about this as well at.. http://marcusblankenship.com/become-a-great-manager/ http://marcusblankenship.com/become-a-great-manager/ Not trying to toot my own horn here, but it is completely achievable.

sheepmullet 11y ago
Thanks for the article. I agreed with a lot of it. A few thoughts: > Your work is MORE important than any individual programmer because you are a force multiplier. I disagree. Your senior developers should all be force multipliers and it isn't about more vs less important. They are simply different roles. In the short term (1-2years) a great manager is the easiest person to replace in a team because a great manager focuses more on strategy than tactics - although there is always a bit of both. > You are unique in your group; you are their manager and leader. All the great managers I've worked with had one thing in common: they weren't managers or leaders in any day to day traditional sense. I don't want my manager to be the main person talking to our customers or trying to prioritise work. Etc etc. I want them to fix/improve the culture. E.g. > Ensuring the team has the best tools possible. This doesn't mean the manager should be picking the tools. It also doesn't mean the manager should be getting particular tools authorised/purchased. I can write a better business case than my manager for any particular tool I need. A great manager might instead create a culture where no business case is required for tool purchases under $500. My last manager actually put any tool purchases we wanted on his personal credit card, no questions asked, because he couldn't get any organisational support. He then did all the legwork to get reimbursed. And that is clearly leadership. But its not leadership in a day to day sense. It did however help create a really good atmosphere and we were incredibly productive as a team.
vcald64 11y ago
Thanks for the articles Marcus, they gave me some valuable insights!

sheepmullet 11y ago

Thanks for the article. I agreed with a lot of it. A few thoughts: > Your work is MORE important than any individual programmer because you are a force multiplier. I disagree. Your senior developers should all be force multipliers and it isn't about more vs less important. They are simply different roles. In the short term (1-2years) a great manager is the easiest person to replace in a team because a great manager focuses more on strategy than tactics - although there is always a bit of both. > You are unique in your group; you are their manager and leader. All the great managers I've worked with had one thing in common: they weren't managers or leaders in any day to day traditional sense. I don't want my manager to be the main person talking to our customers or trying to prioritise work. Etc etc. I want them to fix/improve the culture. E.g. > Ensuring the team has the best tools possible. This doesn't mean the manager should be picking the tools. It also doesn't mean the manager should be getting particular tools authorised/purchased. I can write a better business case than my manager for any particular tool I need. A great manager might instead create a culture where no business case is required for tool purchases under $500. My last manager actually put any tool purchases we wanted on his personal credit card, no questions asked, because he couldn't get any organisational support. He then did all the legwork to get reimbursed. And that is clearly leadership. But its not leadership in a day to day sense. It did however help create a really good atmosphere and we were incredibly productive as a team.

vcald64 11y ago

Thanks for the articles Marcus, they gave me some valuable insights!