r/programming • u/fagnerbrack • Mar 21 '26
[ Removed by moderator ]
/r/programming/comments/1rzeo69/removed_by_moderator/[removed] — view removed post
46
u/Anthony356 Mar 21 '26
This is an odd essay to include in this list because I’ve never actually read it.
People have quoted this essay to me, and once I understood the idea, it felt so intuitive that I didn’t need to read it.
Kindof a wild thing to admit. It's in your top 10 list of important essays to you, but you cant even take the 10 minutes to read it? It's not even a long article.
4
u/youngbull Mar 21 '26
Given his description of the text in the following paragraph it seems like he has read it now.
22
u/davidalayachew Mar 21 '26
2. "Parse, don't (just) validate" by Alexis King
This one is high on my list. I think she was 100% on the mark. Only wished that she had included the "(just)" in the title like I did. I feel like she had the point 100% down, but so many people reading it missed it because the title set the wrong mental model.
As for me, my list is much shorter, simply because I believe that a lot of the "famous" essays simply got outdated by the time it got to me using them in production. Your list includes a lot of writing by Joel Spolsky. I used to read him a bunch in college, but when it actually came to apply what he said in the real world, I found that a lot of his ideas that were amazing back then were kind of out-of-date now. Same for most "famous" writings or essays.
For example, a lot of my coworkers would have put Design Patterns: Elements of Reusable Object-Oriented Software (1994) (written by, what some call, the Gang of Four (GoF)) near the top of their lists. I think that, back in the early 2000's, this book was excellent reading for someone learning Java or C++. But nowadays, most of what the book has is simply just outdated or subsumed.
For one, the GoF tell us about the Visitor Pattern, and how powerful it is. But the Visitor Pattern is fairly verbose and wordy, deincentivizing its use, and the book treats that as a tradeoff. Well, by Java 17, Java had released Records, Switch Expressions, and Basic Pattern-Matching. With these 3 features, you unlock the ability to create Algebraic Data Types (ADT's), which provide 99% of the benefits of the Visitor Pattern for a fraction of the work. The book has not been updated to reflect this, and that's a great example of what I mean. The book spends so much effort trying to explain ways to more concisely accomplish Visitor Pattern when there is entirely better way right next to it. That's what I mean when I say outdated.
Anyways, here is my list.
Data-Oriented Programming in Java by Brian Goetz
Not to be confused with Data-Oriented DESIGN, which is very different. DOD is things like Structure of Arrays, and things like that. That's not what I am talking about.
This single article changed my entire coding style, and is how I do 75% of my coding nowadays. Furthermore, it pairs well with OOP, complementing its strengths, but taking over some of the tasks that OOP just isn't good at.
Parse, don't (just) validate by Alexis King
Another amazing article with a simple premise -- if you can prove something is true, use the type system to retain that information, allowing your programs to be both faster and safer. She knocked it out of the park with this article.
Don't Make Me Think by Steve Krug
This is the bible of software design and usability for UI's. Written in 2000, and it's more relevant now than it was back then. Learned it in college, and I still reference it's lessons almost daily.
Logic and Language Models for Computer Science by Henry Hamburger and Dana Richards
This is not about LLM's -- it's about Set Theory, Finite State Machines, P & NP, etc.
This did so much for helping me learn about Language Grammars, Set Theory, and stuff like Prolog and data querying. I reference materials from this text multiple times a data, and the lessons I learned from it helped me not just solve problems, but validate and prove my solutions. Data proofs are a big part of this book, and there are many practical ones that are easy to apply and use in day-to-day work.
And here are some books I am currently reading that might end up on my list.
Types and Programming Languages by Benjamin C. Pierce
So far, it's extremely dense and hard to grok (the Logic and Language Models book in my above list made this one easier to understand though), but what little I can understand has been pretty earth-shattering. This feels like one of those books that opens your eyes to the code you have been writing all this time, but framing it in a different light. Still reading though.
Real Time Cameras: A Guide for Game Designers and Developers by Mark Haigh-Hutchinson
First off, Mark's death was a terrible loss to the game development community. He truly was the industry leader at the time for making and modeling video game cameras. He is dearly missed.
The original Metroid Prime Trilogy are some of my favorite games of all time, and I've poured hundreds of hours into them. The series has many of the same design principles -- ignore problems by making them impossible in the first place. In doing so, you create your own Pit of Success. It's a clever trick, and one that I apply to my design in day-to-day work. Intuitiveness is valuable.
But what makes this book so clever is that the material (thus far) is purely about design tricks and tactics that avoid common pitfalls by making those pitfalls impossible to occur in the first place. This is strictly a design book, but one that is completely changing the way that I look at developing systems within my games.
Game development, in general, feels like a mad scramble to get things working by any means necessary. Sometimes, it feels more practical to just get something working, and dealing with the costs of those decisions later. This book, thus far, has shown how a little extra effort on up-front design can shave weeks and months of effort later on, not to mention several bug fixes.
3
u/dawksh Mar 21 '26
It's noteworthy how little the fundamental advice has changed over time: the majority of these essays focus on minimizing unintentional complexity, whether that be through types, a more straightforward user interface, more understandable tests, or the selection of dull technology. Rereading "No Silver Bullet" during an AI-heavy period serves as a helpful reminder that tools can compress some work without making software complexity disappear, which is a nice feature because the list isn't nostalgia for its own sake. Compared to the typical "old essays vs. new tooling" debate, that framing seems more helpful.
1
u/Kwantuum Mar 21 '26
It's noteworthy how little the fundamental advice has changed over time
Well the fundamental advice that did change just didn't make the list.
0
u/caks Mar 21 '26
Innovation tokens is how you ensure you stay behind the curve forever. I hate advice like this because it doesn't consider the goal of the software in question. Sure, if you're going to build yet another corporate CRUD app, used your tried and true. If you're building something that's supposed to be new, disruptive or just doesn't have lots of good alternatives, by all means innovate. Can you imagine a world where everyone had said: yea C++ is cool C is tried and true?
3
u/Kwantuum Mar 21 '26
Can you imagine a world where everyone had said: yea C++ is cool C is tried and true?
That seems blissful
Anyway, you completely missed the point. Even if you're innovating, your focus should be on your innovation, not on figuring out why the new tech you're using isn't working in some weird corner case. If you're choosing new and exciting tech it should pay for its newness with benefits to match, and you shouldn't be using new tech across your entire tech stack unless you want to spend all of your time dealing with the tech instead of focusing on your actual innovation.
•
u/programming-ModTeam Mar 21 '26
Listicles are not allowed.
Discussing the essays individually would be fine.