Throwback Thursday: April 23, 2026
Today's edition of Throwback Thursday revisits the pitfalls of leaving old code and database fields around and answers the question, "What could it hurt?"
With over a million words scattered across more than 1,500 articles on this blog, you've probably missed a few things here.
That’s why each week in "Throwback Thursday," we’ll revisit some standout posts. Expect a blend of my personal favorites, insightful articles from other great minds, and a touch of coding humor to keep things light.
Highlights from NoLongerSet.com
Cruft Sale!
Everything must go!!! Dead code, obsolete reports, and bunches of binary backups! No offer too big or too small!
Mike Wolfe
Old Code Left in Place
What’s the harm in leaving old code in place? It’s not like it costs us anything. ... Or does it?
Mike Wolfe
Old Fields Left in Place
Leaving old fields in place is even worse than leaving old code. Instead of runtime errors, you’ll end up with harder-to-detect data errors.
Mike Wolfe
Developer Humor
Code Lifespan
Cover image generated by Ideogram
