A Difficult Software Developer so talented, so productive, so essential that if they were to leave, the entire project would collapse.
- Can mutate into: “The Hostage Taker” or “The Diva” Difficult Developer
- Dangerous when coupled with: “The Optimist” Difficult Project Manager
- Often confused with “The Assassin” Underappreciated Developer
- Likelihood of fixing: None
- Danger to project: Extremely High
In the software development industry, the term “Rockstar Developer” is often bandied about by recruiters attempting to attract developers by inflating their egos, i.e. “We are looking for a few Rockstar Developers.” True “Rockstar” developers are hard to find, as they are the perfect developer:
- There is no problem they cannot solve (and quickly).
- They work all hours of the night to make their deadlines.
- They have virtually no bugs, or any bugs are quickly resolved.
- They take on the most difficult parts of the project.
- They are generally well liked by the peers.
Unfortunately, once hired, they become indispensable to the project.
The Rockstar Developer is like a black hole of work: work spirals around them, and is eventually and inevitably sucked into them to be done. This can be as extreme as them taking work away from slower developers in order to meet a deadline – much to everyone’s relief. If the project is in a bind, they will bail it out. If something dramatic and unexpected happens, they will know what to do. They are truly remarkable – and every recruiter knows it.
The Rockstar Developer will receive several recruiter calls a day, every day. This is because their reputation precedes them. Companies are always looking to poach “Rockstars” because they know how valuable they are, and in many cases will do almost anything to get them. The situation, therefore, is someone indispensable to your project having just about every other company wanting to poach them from you. If they do, the project fails in a classic case of putting too many eggs in one basket.
There is no “solution” to The Rockstar Developer – indeed; you would be foolish to “fix” them as they are your most productive developer by far. All you can do is mitigate the damage from them leaving by building a team around them that can continue to be effective if The Rockstar were to leave. This will most likely mean that you will need several developers to replace the productivity of a single “Rockstar”, but at least you will be able to survive their departure.
To test how bad your situation is, pay close attention to developer productivity when they go on vacation. If, when The Rockstar goes away for a week, all development halts, then you need to redouble your efforts in getting other developers to a level whereby they can keep the project moving when The Rockstar is not in the office.
This can be challenging if the developers have become so accustomed to The Rockstar handling difficult problems that they have become lazy and complacent. There is a chance that with the sudden departure of The Rockstar, the other developers will spring into action, but more likely they are so fond of The Rockstar that they follow them out the door to work with them again at their new company.