|
@patrickc | |||||
|
I love the clarity, brevity, and simplicity of this memo about the design of the Alto's OS: microsoft.com/en-us/research….
What are similarly good examples of clear architectural writing for ambitious technical systems?
|
||||||
|
||||||
|
𝚄𝚍𝚊𝚢 𝚂𝚒𝚗𝚐𝚑
@udayrsingh
|
16. sij |
|
The Lisp 1 Programmer's Manual is quite clear: bitsavers.org/pdf/mit/rle_li…
|
||
|
|
||
|
Patrick Collison
@patrickc
|
16. sij |
|
That's a good suggestion!
|
||
|
|
||
|
Daniel Compton
@danielwithmusic
|
16. sij |
|
I imagine Stripe has a bunch that would be really interesting for non-Stripes to see?
|
||
|
|
||
|
Patrick Collison
@patrickc
|
16. sij |
|
Some day, perhaps!
|
||
|
|
||
|
Riva
@rivatez
|
16. sij |
|
anything by Seymour Cray:
ed-thelen.org/comp-hist/CRAY…
|
||
|
|
||
|
naveen
@naveen
|
16. sij |
|
i now want the original physical copy this Cray manual
|
||
|
|
||
|
Sriram Krishnan
@sriramk
|
16. sij |
|
Not sure if in public but some of the original design stuff for NT is amazing. @marklucovsky may know if any is public.
|
||
|
|
||
|
Steven Sinofsky
@stevesi
|
17. sij |
|
The NT docs were all 4” binders :)
|
||
|
|
||
|
Jason Crawford
@jasoncrawford
|
16. sij |
|
“The Log: What every software engineer should know about real-time data's unifying abstraction”, by @jaykreps, which turned into @apachekafka/@confluentinc engineering.linkedin.com/distributed-sy…
|
||
|
|
||
|
Victor Mota
@vimota
|
17. sij |
|
Maybe too obvious, but the Satoshi paper. Also @JeffDean's research.google.com/archive/mapred… and BigQuery's percursor static.googleusercontent.com/media/research…
|
||
|
|
||