Technical Papers Every Programmer Should Read (At Least Twice)
Report a link problem
Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderI read a random sampling paper recently which took a simple problem and approached it in ways that were much more elegant than I did. Its almost a toy problem but I found the paper really interesting: http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.138.7...
There is very little all programmers should be required to have in common. The field is just that big now. 9 times out of 10 a list like this includes a treatise on floating point number representation, which while useful, probably isn't of utmost importance in the 21st century, but hey, at one time folks thought that was required for 'all programmers' to read. At least this list does seem more up to date and relevant. I just wish we'd…
The name Luca Cardelli, one of the authors of one of the recommended papers, rings a bell: Modula 3 guy. https://en.wikipedia.org/wiki/Modula-3
Previous discussion: https://news.ycombinator.com/item?id=2979458
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 914
- Total comments
- 130
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2011-09-09 | Technical Papers Every Programmer Should Read (At Least Twice)First breakout · Best thread | icey | 467 | 57 |
| 2014-12-20 | Technical Papers Every Programmer Should Read at Least Twice (2011) | altern8 | 366 | 66 |
| 2016-08-01 | 10 Technical Papers Every Programmer Should Read (At Least Twice) (2011) | adamnemecek | 2 | 1 |
| 2016-09-24 | 10 Technical Papers Every Programmer Should Read | hackerkid | 4 | 0 |
| 2016-10-17 | 10 Technical Papers Every Programmer Should Read (At Least Twice)Hall induction | leksak | 8 | 0 |
| 2016-12-01 | Technical Papers Every Programmer Should Read (2011)Latest 20+ point return | tosh | 66 | 6 |
| 2021-07-22 | Technical Papers Every Programmer Should Read (At Least Twice) (2011) | codesections | 1 | 0 |