I see a problem time and time again with programmers wasting an incredible amount of time writing “good code” when in reality sometimes that “good code” isn’t good at all. I fall prey to this as well, so I’m going to write up this post to put into words the code design decisions that I make subconsciously when trying to write “good code”. That way I can analyze it, and refine it in the future. This post is focused on the code itself, not whether or not the software product is of any use. At the end of the day the hardest thing to do is to create something that people want to use. That is a totally different topic.
What can I say? After 15 years of programming professionally, I’m a pretty confident coder. I work hard at it, and still find ways to improve everyday.
As Bradley Nowell so eloquently stated in “Love is What I got”….
“I can play the guitar like a mother f-in riot.” – Sublime
Well this is how I feel about code!
“I can rock the compiler like a mother f-in riot.” – Jon Kragh