Michael Fogus personal blog
Technical Papers Every Programmer Should Read (At Least Twice)
Let me preface this post by saying that no programmer should feel compelled to read any of these papers. I list them because I think that they provide a breadth of information that is generally useful and interesting from a computer science perspective. What you do with that information is your prerogative, including…
- Points
- 467
- HN comments
- 159
- Submissions
- 4
- Cited by
- 5 commenters
Software EngineeringLife, Learning & Writing2011
On Hacker News
| Submitted | Title on HN | Points | Comments |
|---|---|---|---|
| Sep 9, 2011 | Technical Papers Every Programmer Should Read (At Least Twice) by icey | 467 | 57 |
| Dec 20, 2014 | Technical Papers Every Programmer Should Read at Least Twice (2011) by altern8 | 366 | 66 |
| Dec 22, 2011 | Technical Papers Every Programmer Should Read (At Least Twice) by llambda | 198 | 30 |
| Dec 1, 2016 | Technical Papers Every Programmer Should Read (2011) by tosh | 66 | 6 |
Cited in comments
Linked from 6 Hacker News comments by 5 different people, from Jun 2013 to May 2017.
Most recent:
- WalterSear · May 29, 2017
- swah · Feb 24, 2015
- ColinWright · Dec 24, 2013
- vowelless · Nov 3, 2013
- vowelless · Sep 7, 2013
- gtani · Jun 29, 2013
