Technical Papers Every Programmer Should Read at Least Twice (2011)
There is very little all programmers should be required to have in common. The field is just that big now.<p>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 <i>was</i> required for 'all programmers' to read.  At least this list does seem more up to date and relevant.<p>I just wish we'd stop with 'all X should' titles.  Its demeaning and inaccurate.