✳flâneur — a map of the web's best reading
10 Papers Every Developer Should Read
michaelfeathers.silvrback.com · 1,763 words · saved by 2 readers
10 Papers Every Developer Should Read - (At Least Twice)
10 Papers Every Developer Should Read (At Least Twice) Michael Feathers November 15, 2017 (This is a requested repost of a lost blog I wrote in 2009. I'd change a few things, but not many) I spent most of yesterday afternoon working on a paper I’m co-writing. It was one of those days when the writing came easy. I was moving from topic to topic, but then I realized that I was reaching too far backward – I was explaining things which I shouldn’t have had to explain to the audience I was trying to reach. When I first started writing, one of the pieces of advice that I heard was that you should al
Explore this link on the map →saved by
related reading
- What every computer science major should knowmatt.might.net
- Teach Yourself Computer Scienceteachyourselfcs.com
- Computers can be understood - Made of Bugsblog.nelhage.com
- Classic Systems Papers – Mark's Musingsverber.com
- Recommended Reading for Developersblog.codinghorror.com
- Things unlearnedscattered-thoughts.net
- Things You Should Never Do, Part I – Joel on Softwarejoelonsoftware.com
- how I think when I think about programming - alice mazalicemaz.com
- Teach Yourself Programming in Ten Yearsnorvig.com
- Loper OS >> The Wisdom of Erik Naggumloper-os.org
- notes/books/pragmatic-programmer.md at master · pkardas/notes · GitHubgithub.com
- Advice for new software devs who've read all those other advice essays • Buttondownbuttondown.email