Throwback Thursday: February 13, 2025

In today's edition of Throwback Thursday, we explore the greatest gift we can give to future programmers: writing readable code.

Throwback Thursday: February 13, 2025

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

Code is WORM: Act Accordingly
Write Once. Read Many. The cost of avoiding shortcuts when writing code is far exceeded by the benefits you’ll get when reading it.
Don’t Write Clever Code
There are two problems with clever code. 1) The next person might not know what you were doing. 2) They might not know if *you* knew what you were doing.
Avoid Context Switching for More Readable Code
Writing code is like juggling. But mixing code, queries, and global state is like juggling balls, bowling pins, and running chainsaws.
“I’m Not Touching That!”
Hey, who wants to maintain this legacy code? Beuller? Beuller?

Developer Humor

Arcane Bullshit

Learning arcane bullshit from the 80s can break your computer, but if you're willing to wade through arcane bullshit from programmers in the 90s and 2000s, you can break everyone else's computers, too.

Cover image generated by Ideogram

All original code samples by Mike Wolfe are licensed under CC BY 4.0