Papers Every Programmer Should Read (At Least Twice)

papers.html

<ol>
  <li><a href="http://sunnyday.mit.edu/16.355/parnas-criteria.html">On the criteria to be used in decomposing systems into modules</a> – David Parnas</li>
  <li><a href="http://research.sun.com/techrep/1994/abstract-29.html">A Note On Distributed Computing</a> – Jim Waldo, Geoff Wyant, Ann Wollrath, Sam Kendall</li>
  <li><a href="http://portal.acm.org/citation.cfm?id=365257">The Next 700 Programming Languages</a> – P. J. Landin</li>
  <li><a href="http://portal.acm.org/citation.cfm?id=359579">Can Programming Be Liberated from the von Neumann Style?</a> – John Backus</li>
  <li><a href="http://cm.bell-labs.com/who/ken/trust.html">Reflections on Trusting Trust</a> – Ken Thompson</li>
  <li><a href="http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.50.6083">Lisp: Good News, Bad News, How to Win Big</a> – Richard Gabriel</li>
  <li><a href="http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.29.363">An experimental evaluation of the assumption of independence in multiversion programming</a> – John Knight and Nancy Leveson</li>
  <li><a href="http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.50.7565">Arguments and Results</a> – James Noble</li>
  <li><a href="http://c2.com/doc/oopsla89/paper.html">A Laboratory For Teaching Object-Oriented Thinking</a> – Kent Beck, Ward Cunningham</li>
  <li><a href="http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.31.562">Programming as an Experience: the inspiration for Self</a> – David Ungar, Randall B. Smith</li>
</ol>