Papers Every Programmer Should Read (At Least Twice)
Report a link problem
The originally submitted URL now redirects to the address above. Updating the destination does not change the item’s HN history, Hall membership, or rank.
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 orderA paper that would be on my personal list is "What Every Computer Scientist Should Know About Floating-Point Arithmetic" (Goldberg): http://download.oracle.com/docs/cd/E19957-01/806-3568/ncg_go...
I'm surprised he didn't add Fred Brooks's "No Silver Bullet". It and the essays in "The Mythical Man Month" should really be required reading for anyone working on large projects, imho. http://www.virtualschool.edu/mon/SoftwareEngineering/BrooksN... http://en.wikipedia.org/wiki/The_Mythical_Man-Month
He forgot: http://www.cs.utexas.edu/~shmat/courses/cs345/whyfp.pdf "Why functional programming matters" by John Hughes
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
- 574
- Total comments
- 41
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 |
|---|---|---|---|---|
| 2009-02-27 | Papers Every Programmer Should ReadFirst breakout | soundsop | 189 | 14 |
| 2011-06-09 | 10 Papers Every Programmer Should Read (At Least Twice) | shawndumas | 27 | 1 |
| 2011-08-24 | Papers Every Programmer Should Read (At Least Twice)Best thread · Latest 20+ point return | ColinWright | 358 | 26 |