Right? Well, that's the image. The problem with this image is that a couple of those who think or would like to think they are Code Monkeys are actually Code Donkeys - intendedly or accidentally, and the difference is a little bit more than just one letter and biological species.
Let me give you a couple of very different technical and psychological examples of what I mean is a Code Donkey:
- Breaks the builds - sometimes or often
- Uses VCS as code backup system
- Suffers from Goodnight-Commit syndrome
- Suffers from Superhero syndrome overestimating his own capabilities and thus quickly becoming unreliable
- Never blames himself for a failure, blames all the others for everything he did wrong
- Just randomly doesn't answer to emails or questions
- Hunts every new technology hype, screwing it into the current solution, no matter if it fits there or not
- Knows everything better and ignores best practices or suggestions from the others
- Doesn't share knowledge, i.e. doesn't mentor juniors
- Doesn't document and comment his code well
- Prefers talking over listening in meetings or in other gatherings
- Criticizes formalism of non-startups showing how "easy" it is to just peg down the code without all those layers, abstractions etc.
It's not the speed of your typing or the amount of yout tweets and thus the alledged coolness. It's how you act. And to be a guru, you need to act professionally.
No comments:
Post a Comment