Re:Technical Papers Every Programmer Should Read (At Least T...
by fogus on Friday September 09, 2011 @03:51PM
(#2979569)
Sorry. My Markdown syntax was bad. There are now links to the articles marked by ↗.
Re:Technical Papers Every Programmer Should Read (At Least T...
by pjscott on Friday September 09, 2011 @05:33PM
(#2979954)
This is a great collection of papers, and I don't mean to downplay how happy I am to find it, but you might want to use a linking method that's more obvious, like having relevant text be blue and underlined. The principle of least surprise is important, usually more important than cleverness in design.
(Now I'm going to go off and read that Lamport paper.)
[deleted]
Re:Technical Papers Every Programmer Should Read (At Least T...
by njharman on Friday September 09, 2011 @08:53PM
(#2980395)
"link to paper" comes to mind...
Re:Technical Papers Every Programmer Should Read (At Least T...
by Tichy on Friday September 09, 2011 @04:35PM
(#2979729)
Can't find the link for "Organizing Programs Without Classes". The Oracle site says "click here to download", but there is nothing to click?
Re:Technical Papers Every Programmer Should Read (At Least T...
by patrickyeon on Friday September 09, 2011 @04:41PM
(#2979752)
I see a postscript version here: http://www.cs.ucsb.edu/~urs/oocsb/self/papers/organizing-pro...
Re:Technical Papers Every Programmer Should Read (At Least T...
by Tichy on Friday September 09, 2011 @05:37PM
(#2979968)
Thanks!
Re:Technical Papers Every Programmer Should Read (At Least T...
by lelf on Friday September 09, 2011 @08:11PM
(#2980307)
here is link to ps.gz.
And you can find PDF at http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.127.5...
Re:Technical Papers Every Programmer Should Read (At Least T...
by russellallen on Friday September 09, 2011 @08:08PM
(#2980303)
Why not have links to each one?