Jakub Nabrdalik

A software developer with 10+ years of professional experience in IT,
as an architect, programmer, designer, analyst, project leader,
project manager, and lately as a Head of Software Development. WJUG
and WGUG leader. Software Craftsman, practicing TDD/BDD/DDD in
Java/Groovy/C#/PHP. Microservices enthusiast. More at:


In English Game of throneware, or how not to get killed, when a developer becomes a manager

You are a good developer, each year you learn more, each year you earn more. You become senior, you become architect, chief architect, chief principal officer architect, and, one day, you are at the top-payroll level, and there is no place to go. You are happy with what you do, but your wife/husband/bank keeps asking for more. What do you do? You go to middle management.

Or perhaps you are a shitty programmer, you really suck at your work, but thanks to your soft skills, drinking vodka with proper people, you still keep your job. And then, one day, due to Dilbert Principle ("companies tend to systematically promote their least-competent employees to management, in order to limit the amount of damage they are capable of doing"), they make you a manager.

Or maybe nothing like that applies to you. And they still make you a manager.

What happens, when you become a manager? How do you organize teams, workspace? How do you help people? How do you deal with politics, communication? What has the position of your desk to do with the architecture of your systems? How do you make decisions? How do you keep doing the boring stuff, while everyone around is hacking? How do you deal with salaries, outsourcing, investors, and Ivory-tower architects. How do you keep your hair from going pointy? And what do you do with all the insanity?

This isn’t a tutorial. This is a case study, of all the funny things that happens, when a developer becomes a manager. A story written from an engineer perspective.