Home

You Should be Embarrassed by Old Code

Looking at old code can be an uncomfortable, embarrassing, or infuriating experience. And that's a good thing.

If you've been writing code long enough, you know the feeling of looking at old code. It's embarrassing.

(I wrapped a 20-line method in an if statement instead of using an exit clause? WTF!? What a loser!)

This feeling of embarrassment of old cold—of frustration with your past self for the decisions you made—is absolutely crucial to your development as a developer. The uncomfortable feeling that comes with looking at old code—or, worse, having to work with it—means you're getting better at writing code.

With a little help from my friend, the transitive property, that means that if you look at old code and you don't mind it—or worse, you think it's good—one of these conditions must be true:

  1. You are amazing. You can't get any better.
  2. You had a moment of brilliance and wrote better code than you were accustomed to writing at that particular time.
  3. You haven't written much code since that time, or took a big break somewhere in there and lost steam in getting better.
  4. You aren't getting any better.

In reality, there's always room to be a better developer if you give it the time and attention it requires.

So, take comfort in the uncomfortable feeling of looking at old code. It means the code you're writing today is better.

Let's Connect

Keep Reading

Change Back to Previous Directory

Navigate to the directory you visited previously without the need of remembering or typing the name.

Jul 23, 2022

Why are security questions still a thing?

The motivation to provide an additional layer of security beyond an email-password combination is a noble one, but ...

Mar 03, 2017

Inherited Class-Level Utilities in Ruby

The difference between Ruby's class and class instance variables, and how you can use them to abstract functionality from inherited classes.

Jan 14, 2017