Join 📚 Josh Beckman's Highlights
A batch of the best highlights from what Josh's read, .
When fewer than 5,000 programmers existed, they built [Lisp](https://en.wikipedia.org/wiki/Lisp_%28programming_language%29) (1960) and [APL](https://en.wikipedia.org/wiki/APL_%28programming_language%29) (1966) and [sketchpad](https://en.wikipedia.org/wiki/Sketchpad) (1963). With over 5 million programmers today, the best we can do is Rust and React.
I Hereby Pardon All Junior Engineers
Taylor Troesh
It is also notable that the Feynman lectures (3 volumes) write about all of physics in 1800 pages, using only 2 levels of hierarchical headings: chapters and A-level heads in the text.
It also uses the methodology of *sentences* which then cumulate sequentially into *paragraphs*, rather than the grunts of bullet points. Undergraduate Caltech physics is very complicated material, but it didn't require an elaborate hierarchy to organize.
A useful decision rule in thinking and showing is "What would Feynman do?"
Book design: advice and examples
edwardtufte.com
Now the real advantage of tracing to me is it comes out of the box with the idea of sampling. It is a debugging and troubleshooting tool, not something with compliance or business uses. Therefore it hasn't become completely mucked up with people jamming all sorts of weird requirements in there over time. You can very safely sample because its only for developer troubleshooting.
Monitoring Is a Pain
Mathew Duggan
...catch up on these, and many more highlights
Readwise