10 Papers Every Programmer Should Read at Least Twice (with links!)

http://michaelfeathers.tumblr.com/post/81489281/10-papers-every-programmer-should-read-at-least-twice

by Michael Feathers

1. On the criteria to be used in decomposing systems into modules - David Parnas
   http://www.cs.umd.edu/class/spring2003/cmsc838p/Design/criteria.pdf

2. A Note On Distributed Computing - Jim Waldo, Geoff Wyant, Ann Wollrath, Sam Kendall
   http://labs.oracle.com/techrep/1994/smli_tr-94-29.pdf

3. The Next 700 Programming Languages - P. J. Landin
   http://www.thecorememory.com/Next_700.pdf

4. Can Programming Be Liberated from the von Neumann Style? - John Backus
   http://www.thocp.net/biographies/papers/backus_turingaward_lecture.pdf

5. Reflections on Trusting Trust - Ken Thompson
   http://www.ece.cmu.edu/~ganger/712.fall02/papers/p761-thompson.pdf

6. Lisp: Good News, Bad News, How to Win Big - Richard Gabriel
   http://www.dreamsongs.com/Files/LispGoodNewsBadNews.pdf

7. An experimental evaluation of the assumption of independence in multiversion programming - John Knight and Nancy Leveson
   http://sunnyday.mit.edu/papers/nver-tse.pdf

8. Arguments and Results - James Noble
   http://www.laputan.org/pub/patterns/noble/noble.pdf

9. A Laboratory For Teaching Object-Oriented Thinking - Kent Beck, Ward Cunningham
   http://www.inf.ufpr.br/andrey/ci221/docs/beckCunningham89.pdf

10. Programming as an Experience: the inspiration for Self - David Ungar, Randall B. Smith
    http://labs.oracle.com/features/tenyears/volcd/papers/6Ungar.pdf

*I stumbled across this list, but what good is it without links to read the papers? Hopefully, I can make a dent on this list soon.