Really? This is your solution? ‘He should have been more professional?’
‘Mad genious myth?’ Take a look at your phone. Is it Android? If it wasn’t for the Mad Genious of Linus Torvalds, it wouldn’t have existed. Ever heard of Bitcoin? Yes, another foul deed of the loner Mad Genius. I understand there are a lot of people who see programming as just another 9 to 5 — you just go there, do something trackable/auditable and go home. For me, programming is about creation, delivering value, creating something out of thin air, that solves people’s problems. Doing it in time and within budget is of great importance.
I take specific care to avoid being on the same team with people who couldn’t care less how the project is doing, are not nerdy, are not interested in novel ways to solve problems and are just interested in ‘not feeling bad’ while at work. I distance myself from people who lack passion, who don’t contribute enough, don’t listen enough, don’t think enough and don’t care enough. It is just another 9 to 5. Project lives or dies, they get their salaries. Why bother staying late or being passionate?
I am absolutely sure that Rick is not as smart as he thinks, because he should have forseen that skillgaps need to shrink, not rise, and if that’s not possible, quit the team.
Also sure Rick’s tale would be something completely different.
Something about a project failing and nobody caring.
Something about him having to spend his weekends at work because his colleagues are working 1/10th of the speed and quality that Rick is. Something a lot of tasks, that HE and ONLY HE is able to do, because of this skill gap?
Something about anything he does for 1 hour, he has to explain it for 6 hours to people, who are not very keen to listening or understanding novel new things? Something about not having the time for this, because of delivery pressure (hence working 12 hours a day 7d/w).
I hate the simplistic approach that that article was written. It is a very complex situation with faults in Rick, his colleagues, management. Yet the article is describing not how that was a f*cked up situation to arrive at, how to prevent such disdain, engagement and skill gaps within a team, but how, after the damage was being done for years, they fired the guy, (because that’s the choice they have, they simply can’t fire a team), cut off a lot of the team’s ambition in feature-set, delivered something and proclaimed it ‘the best decision ever’.