Throwback Thursday: December 26, 2024
In today's edition of Throwback Thursday, we tackle every programmer's favorite topic: Technical Debt.
With over a million words scattered across more than 1,300 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
Sources of Technical Debt
Dealing with technical debt is no fun. It’s better to avoid it in the first place. To help with that, here’s a list of common sources of technical debt.
Mike Wolfe
Cruft Sale!
Everything must go!!! Dead code, obsolete reports, and bunches of binary backups! No offer too big or too small!
Mike Wolfe
Storing Local Table Data in a Front-End Access Application
If you’re thinking about storing local data in your front-end Access application, make sure it follows these 4 ground rules.
Mike Wolfe
Wisdom from Around the Web
Technical Debt Isn’t Just Technical
As a company that specializes in working with legacy code, we’ve run into our fair share of technical debt over the years. Many teams have deferred their maintenance for so long that any tiny change to the code takes forever to get out the door. But there are other things that contribute to technical debt that you won’t find in the codebase.
Not Another Technical Debt Article
Jimmy MillerDon’t fix it just because it’s technical debt.
Why should we only spend part of our time doing work that maximizes value, and the rest of our time doing other, less optimal work?
Dan Slimmon
Developer Humor
Technical Debt
Cover image generated by Ideogram
