News for hackers. Stuff that matters.
Re:Technical Papers Every Programmer Should Read at Least Tw... by frakkingcylons on Friday December 19, 2014 @09:58PM (#8775736)
I think Communicating Sequential Processes [0] by Hoare is another landmark paper that should be on this list for its perspective on organizing concurrent processes. This was actually required reading for the concurrency section of my undergrad operating systems course.

[0]: https://www.cs.cmu.edu/~crary/819-f09/Hoare78.pdf

Re:Technical Papers Every Programmer Should Read at Least Tw... by dvanduzer on Friday December 19, 2014 @10:11PM (#8775757)
"The practice of supplying proofs for nontrivial programs will not become widespread until considerably more powerful proof techniques become available, and even then will not be easy. But the practical advantages of program proving will eventually outweigh the difficulties, in view of the increasing costs of programming error."

The Hoare paper actually linked is hopelessly outdated, despite being an interesting historical artifact.

Re:Technical Papers Every Programmer Should Read at Least Tw... by ploxiln on Saturday December 20, 2014 @02:45AM (#8776101)
I might call it "sadly" outdated... not that I'm a fan of provably-correct programming (I've never done it, I just fix systems and networking software), but the seemingly modern comfort with buggyness and sloppy implementation... funny or sad, who knows