Distributed Systems Classics (2017)
nvartolomei.com
Distributed Systems Classics (2017)
1–10 of 49 posts
Re: Distributed Systems Classics (2017)
#2Re: Distributed Systems Classics (2017)
#3As always, lists like these don’t include Joe Armstrong's PhD thesis “Making reliable distributed systems in the presence of software errors” - http://erlang.org/download/armstrong_thesis_2003.pdf
Re: Distributed Systems Classics (2017)
#4In addition to making LaTex which has almost nothing to do with it
Re: Distributed Systems Classics (2017)
#5As always, lists like these don’t include Joe Armstrong's PhD thesis “Making reliable distributed systems in the presence of software errors” - http://erlang.org/download/armstrong_thesis_2003.pdf
Re: Distributed Systems Classics (2017)
#6As always, lists like these don’t include Joe Armstrong's PhD thesis “Making reliable distributed systems in the presence of software errors” - http://erlang.org/download/armstrong_thesis_2003.pdf
No disrespect meant to Mr. Armstrong, but it's possible it's never listed because it's basically a textbook. It's 295 pages. The rough average of all papers in OP is like 15 pages.
Re: Distributed Systems Classics (2017)
#7Re: Distributed Systems Classics (2017)
#8As always, lists like these don’t include Joe Armstrong's PhD thesis “Making reliable distributed systems in the presence of software errors” - http://erlang.org/download/armstrong_thesis_2003.pdf
No disrespect meant to Mr. Armstrong, but it's possible it's never listed because it's basically a textbook. It's 295 pages. The rough average of all papers in OP is like 15 pages.
Just the first 2 chapters (~30p) + the Conclusion (~10p) contain a lot of useful food for thought.
Re: Distributed Systems Classics (2017)
#9Lamport is the author of more than half of these, it's crazy how influential he is in this space In addition to making LaTex which has almost nothing to do with it
It's not like they have light schedules - they do research, they have classes, they attendconference, and they have jobs, etc...
And some benefit from tenure, which give them time to deeply focus on some topics.
But I can't imagine how I would write tex in ten years in Pascal on archaic machines if I had all the time to myself.
Doing that in the middle of understanding more computer science than my eyes would ever read ?
What do they do with their time ? What do they don't do ? Are they able to skip the eating and pooping and sleeping and cleaning their house and picking up parcels at the post office and grocery shopping parts ?
Or a proto Unix being written in three weeks. Concretely, what are the days of those three weeks made of ? Especially since it's famously when the spouse was NOT there to handle the housekeeping...
I see not amount of "life hacks" and "atomic habits" and whatnot helping with that. But it's probably just as natural to them as biking - and you can't explain biking, I guess ?
Re: Distributed Systems Classics (2017)
#10As always, lists like these don’t include Joe Armstrong's PhD thesis “Making reliable distributed systems in the presence of software errors” - http://erlang.org/download/armstrong_thesis_2003.pdf