Join 📚 Josh Beckman's Highlights
A batch of the best highlights from what Josh's read, .
You owe it to yourself and your team to work on keeping your capacity high. The more capacity you have, the better work that you do, the less reactive that you are, and, fundamentally, the more output you produce.
Manage Your Capacity, Not Your Time
James Stanier
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
My general reaction to flag arguments is to avoid them. Rather than use a flag argument, I prefer to define separate methods.
class Concert...
public Booking regularBook(Customer aCustomer) {...}
public Booking premiumBook(Customer aCustomer) {...}
My reasoning here is that the separate methods communicate more clearly what my intention is when I make the call.
FlagArgument
Martin Fowler
...catch up on these, and many more highlights
Readwise