I am part-brogrammer
While some would say that brogrammers aren't real, I see a little bit of brogrammer in me. While I don't normally drink booze while I code nor do I make many sexist coments (as far as I know), I am guilty of suffering from one part of the brogrammer stereotype. And worse yet, I think I picked up one of the worst brogrammer characteristics. My attitude towards writing code is way too macho. I think this is one of the worst brogrammer traits, because it will eventually make your final product worse.
Macho brogramming leads to bad software
So why is macho programming bad? It leads to an over-estimation in a coder's ability. I often promise to deliver something, and find myself short on time. In order to finish on time, I'll have to work late and/or push out rushed code, which leads to buggy code.
Beyond the code you actually write, macho brogrammers like myself spend way too little time not writing code. I have come to realize that good software developers spend a lot of time reading, asking questions and planning. Writing code should come at the end of a lot of thought. If you begin writing too early, chances are you haven't found the ideal design and you will either have to re-write code or live with poor design choices.
Putting the Pro back into Programmer
I think the way to stop being a macho brogrammer is pretty simple. Here's what I came up with.
- Think first. Code later.
- Ask lots of questions.
No comments:
Post a Comment