“I am not a developer anymore” – Me, last night
This (probably not so) startling statement was made by me at yesterdays Norfolk Developers meeting as part of a discussion about the Developer to QA ratio in my team. Actually, the statement is probably more accurate if you change it to “I am not a professional developer anymore“. The reality is I’ve not done any real development at work for about a month now. I’m a manager. I don’t code, I… well, that’s the thing. I’m not so sure what I do any more.
“Developers make the worst managers” – Me, c.2003
History has taught me that developers are not good at management. Don’t ask my why this is1, it’s just something I’ve observed during my career. It’s by no means a hard and fast rule, but there is a strong correlation there.
This doesn’t bode well for me. If you’ll excuse the WoW2 analogy: I feel like I’ve gone from being a level 60 Developer with Epic gear to being a level 1 Manager with noobie kit. Oh, everyone says I’m doing a wonderful job, but this is still the honeymoon period and I’ve yet to cock anything up.
“Yesterday I… erm…” – Me, 9:00am most mornings during the standup meeting
Part (most?) of my problem revolves round the fact that I no longer produce anything. As a developer I can point to a list of git commits and say “I wrote this code“; I can point to a feature and say “I implemented this“; I can point to a bug report and say “I fixed this“. My job is now meta. I liaise, guide, advise and facilitate while others do the actual work. Hopefully while doing this I add value.
For a long time now I’ve kept a private work journal detailing what I’ve done during the day. It’s proven to be useful on more than one occasion and now my job is much less tangible it helps keep track of what it is I actually do. There is a blissful irony here though: I’m now so busy doing… whatever it is I do during my day, that I don’t always have time to note it down at the end of the day.
“Have you tried pairing a QA and a developer together?” – Chris Oldwood, last night, 21:00
One thing I learned being a developer is that peer review is A Good Thing™, and that you can learn new things from the most unlikely places. It’s part of the reason why I am so candid about our development processes at things like nor(DEV): and SyncNorwich, warts and all; the feedback you get is invaluable.
The discussion that ensued after Cat Landin‘s talk last night on why developers are so bad at testing gave some really valuable insight into fixing some of the problems we have in our team. Sometimes all it takes is someone unencumbered by the politics, culture and mindset of an organisation to point out simple, but effective fixes.
After last night I have a number of “bug fixes” for our processes. Lets hope they’re as easy to refactor as code.
1Trust me, if I knew I’d be cashing in on “How to go from Developer to Manager” courses and books.
2World of Warcraft – and also from 5+ years ago, I’ve been clean a while now.