How to read a paper by S. Keshav, David R. Cheriton School of Computer Science, University of Waterloo
A few days back, Nandaja shared a link to a 2017 blog post by Michael Feathers titled 10 Papers Every Developer Should Read. It inspired me to start reading academic papers. So this is my attempt to form the habit of reading academic papers. I'll be starting with the ones listed in the above blog post. I'll also include the ones I read before. Let's hope it works.
In the future, I'll move most of the papers listed here to a more relevant page. Until then, this is the place for me to dump the reading notes, relevant links and files.
On the criteria to be used in decomposing systems into modules – David Parnas
A Note On Distributed Computing – Jim Waldo, Geoff Wyant, Ann Wollrath, Sam Kendall
The Next 700 Programming Languages – P. J. Landin
Can Programming Be Liberated from the von Neumann Style? – John Backus
Reflections on Trusting Trust – Ken Thompson
Lisp: Good News, Bad News, How to Win Big – Richard Gabriel
An experimental evaluation of the assumption of independence in multiversion programming – John Knight and Nancy Leveson
Arguments and Results – James Noble
A Laboratory For Teaching Object-Oriented Thinking – Kent Beck, Ward Cunningham
Programming as an Experience: the inspiration for Self – David Ungar, Randall B. Smith