Essays on programming I think about a lot | benkuhn.net
Computers can be understood • Choose Boring Technology • The Wrong Abstraction • Falsehoods Programmers Believe About Names • The Hiring Post • The Product-Minded Engineer • Write code that is easy to delete, not easy to extend • The Law of Leaky Abstractions • Reflections on software performance • Notes on Distributed Systems for Young Bloods • End-to-End Arguments in System Design • Inventing on Principle
Every so often I read an essay that I end up thinking about, and citing in conversation, over and over again. Here's my index of all the ones of those I can remember! I'll try to keep it up to date as I think of more. There's a lot in here! If you'd like, I can email you one essay per week, so you have more time to digest each one: You have been subscribed! Nelson Elhage, Computers can be understood . The attitude embodied in this essay is one of the things that has made the biggest difference to my effectiveness as an engineer: I approach software with a deep-seated belief that computers and
Explore this link on the map →related reading
- The Law of Leaky Abstractions – Joel on Softwarejoelonsoftware.com
- how I think when I think about programming - alice mazalicemaz.com
- Computers can be understood - Made of Bugsblog.nelhage.com
- Choose Boring Technologyboringtechnology.club
- Michael Feathers - 10 Papers Every Developer Should Readmichaelfeathers.silvrback.com
- notes/books/pragmatic-programmer.md at master · pkardas/notes · GitHubgithub.com
- Thoughts on the software industry | linus.coffeelinus.coffee
- programming practices - How to comprehend abstraction in code? - Software Engineering Stack Exchangesoftwareengineering.stackexchange.com
- That's not an abstraction, that's just a layer of indirectionfhur.me
- In defense of blub studies | benkuhn.netbenkuhn.net
- Repeat yourself, do more than one thing, and... — programming is terribleprogrammingisterrible.com
- Abstraction (computer science) - Wikipediaen.wikipedia.org