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
saved by
related reading
- Essays on programming I think about a lot | benkuhn.netbenkuhn.net
- Things unlearnedscattered-thoughts.net
- How to win a best paper award (or, an opinionated take on how to do important research)nicholas.carlini.com
- Reflections on 10,000 Hours of Programming | Matt Rickardmatt-rickard.com
- Cognitive load is what mattersminds.md
- Advice for new software devs who've read all those other advice essays • Buttondownbuttondown.email
- Recommended Reading for Developersblog.codinghorror.com
- Some thoughts on writingdanluu.com
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- how I think when I think about programming - alice mazalicemaz.com
- Readingcarlkolon.com
- Writing Toy Software Is A Joyblog.jsbarretto.com