Being Bad Sucks

You have to be bad before you can be good. Well, that sucks.

For programming, this means that most of what you’re writing now will be useless in a few years unless you make an effort to refactor your code regularly.

If you went to school for computer science, this will drive you mad because you were taught how important it is to write code that is generic.

So, we go through years of trying to write generic code, following all the guidelines OOP and software engineering, but we suck at it. It’s frustrating. I hope that most of you aren’t struggling with these kinds of things, but I have a hunch that it’s a widespread problem.

Instead of focusing on making things generic, let’s strive to solve the problem we’re actually working on. Don’t worry about hardening your code against future use. Most of what we write today will be garbage tomorrow.

Just write code that gets work done. Get good at getting things done.



Build a man a fire, and he'll be warm for a day. Set a man on fire, and he'll be warm for the rest of his life.