Look Through Your Old, Active Code

Honestly, I don’t know if I’m talking to everyone or just myself. It doesn’t really matter, though. Every developer needs to go back and look at his or her old code if it’s still in use and supported.

I don’t know about you all but I code something every damn day. That means I learn something new every damn day. While not everything I learn requires a change in the way I do things, the culmination of things learned over time change the way I approach code.

I go back and look at some of my old code and have no choice but to switch it up a bit. It’s not only because I don’t like my old approaches, but also because I’m still supporting that old code.

Why create more work for myself in support? Why maintain funky knowledge when it can be a thing of the past? It just doesn’t make sense to ignore.

If your overall setup can afford to be updated without a bunch of customers protesting outside of your development shop, go back, look at your old code, and make sure it’s what you would have written today if you had the same tasks.

You’re only making things better for everyone and you’re getting more coding reps in.

Alright, back to work.

Author: Sean Davis

I'm a simple guy. I like to code and I like to workout. I'm all about growth and just about everything else is nonsense in my book.

Leave a Reply

Your email address will not be published. Required fields are marked *