Seems that hero coders are a breed not really respected by their peers, but pretty loved by the project managers... Why? Well, because they are the ones called to save the day when the s..t hits the fan but they are dark and grumpy with their colleagues(this is not always true... :) ).
We all want to be(come) those mythical geeks that by raising their eyebrows are inverting the bits create monumental masterpieces which makes the world tremble, but unfortunately hero coding is not the answer, at least not for me. Hero coding is more like a drug for programmers, which once tasted is hard to give up on, it's like a drug because we have our big egos and who doesn't want to feel irreplaceable and important to the people around them, to be the ones called to pull insane amount of time and work for that ugly feature never finished and always late?
As a geek wannabe, hero coding seems to be the answer for quickly becoming a good and respected developer but after doing it for a couple of months and being forced to stop for a couple of weeks, looking back at what I achieved in that time doesn't look too good, and this is not because programming 16 hours a day is not cool, but because hero coding favors an environment in which some important things are lost: code quality, self esteem, each short-cut looks appealing and you quickly forgot things which are important for you: sucking less each year , improve your skills and be near the ones you love.
Hero coding is followed by a pretty ugly burnout period, which is quite depressing...
By writing this, does it mean that I'm an uber geek programmer shouting his ego? No, it means that I acknowledge that I have a problem and I must get rid of it...
Until next time, be good...
P.S. "Hi, my name is Adrian and I'm a hero coding addict..."
No comments:
Post a Comment