Technical Papers Every Programmer Should Read (At Least Twice)
1–10 of 61 posts
Re: Technical Papers Every Programmer Should Read (At Least Twice)
#2Re: Technical Papers Every Programmer Should Read (At Least Twice)
#3Why not have links to each one?
Re: Technical Papers Every Programmer Should Read (At Least Twice)
#4Is this title still referring to the object mentor essays that were posted a couple weeks ago?
Re: Technical Papers Every Programmer Should Read (At Least Twice)
#5"All papers are freely available online" Why not have links to each one?
Re: Technical Papers Every Programmer Should Read (At Least Twice)
#6Is this title still referring to the object mentor essays that were posted a couple weeks ago?
Re: Technical Papers Every Programmer Should Read (At Least Twice)
#7Leslie Lamport, "Braid Theory": http://research.microsoft.com/en-us/um/people/lamport/pubs/b...
Don Knuth, "The Potrzebie System of Weights and Measures", Mad Magazine: http://upload.wikimedia.org/wikipedia/en/5/52/Potrzeb.jpg
Re: Technical Papers Every Programmer Should Read (At Least Twice)
#8Flapjax: A Programming Language for Ajax Applications:
http://www.cs.brown.edu/~sk/Publications/Papers/Published/mg...
Embedded probabalistic programming:
http://okmij.org/ftp/kakuritu/dsl-paper.pdf
Memoization of Top-down Parsing:
Re: Technical Papers Every Programmer Should Read (At Least Twice)
#9"All papers are freely available online" Why not have links to each one?
Sorry. My Markdown syntax was bad. There are now links to the articles marked by ↗.
Re: Technical Papers Every Programmer Should Read (At Least Twice)
#10Earlier quoted context omitted.
Sorry. My Markdown syntax was bad. There are now links to the articles marked by ↗.
Can't find the link for "Organizing Programs Without Classes". The Oracle site says "click here to download", but there is nothing to click?