4 ms·
I was a long time developer who became a manager. I chose to become a manager because I enjoy the people aspect of it. I see my primary responsibility to help m
by helmsb 6y ago
I was a long time developer who became a manager. I chose to become a manager because I enjoy the people aspect of it. I see my primary responsibility to help my teammates be successful and deliver high quality products.
I considered taking a path through architecture but chose management because I felt like I could have a larger positive influence. As an architect I could design a few good software solutions but as a manager I can help coach a group of people who each go on to make great designs.
I do miss coding but I try and make up for it by setting aside time to pair program with teammates and perform “shadow PRs” (PRs that I review but don’t approve that I follow up with to see if there are things I missed that the team picked up on or vice-versa. I also set aside 2-4 hour per week of personal time to keep my skills sharp. I’m a firm believer that a software development manager should retain some technical chops.
Here are the values I try and live by as a manager:
1. Take less than your fair share of the credit and more than your fair share of the blame.
2. Commit yourself to the success of your team and your own success will follow.
3. Be transparent and honest.
4. Don’t be afraid to admit when you’re wrong.
5. Be decisive.
- jy2947 6y agoThanks, agree to every word.
- bladelessninja2 6y agoI've never really understood the "architect" role, maybe because I've always stumbled across poor architects, but I generally don't agree it is a good practice for someone to make decisions (architecture) and not deal with consequences (actually code within this architecture). Those decisions should be left for team to make and, yes, opinion of more experienced devs should be weighted more, but everyone should have a right to speak. Something that connects with above statement: most architects are involved only at the beginning, which is so unimaginably stupid considering the fundamental truth about software development which is: "requirements will change". Personally, if I hear from recruiter that they havea an architect in team I always say "thank you, but no thank you".