Join 📚 Josh Beckman's Highlights
A batch of the best highlights from what Josh's read, .
It's easy to look at pregnancy (for example) as something which affects only 2% of your users. But it's really something that affects 40% of your users 5% of the time.
Dana Fried on Twitter: "This Is an Easy Statistical Mistake for Tech Companies to Make - And One We Try to Avoid in Chrome: It's Easy to Look at Pregnancy (For Example) as Something Which Affects Only 2% of Your Users. But It's Really Something That Affects 40% of Your Users 5% of the Time." / Twitter
twitter.com
RFCs are written and discussed, but there’s no mechanism by which they’re formally adopted or rejected. Organizations choose to implement them (or don’t); they become standards through widespread voluntary adoption.
This means that, if engineering organizations naively adopt an RFC process without bolting on some sort of explicit decision-making step, the process quickly breaks down. Without some sort of process to move towards a decision, **the default outcome of an RFC is “no”**
RFC processes are a poor fit for most organizations
jacobian.org
The single biggest thing Substack accomplished was *legitimizing* a Schelling point: interesting intellectuals can charge money for doing their thing and people who interested in the life of the mind should pay for their output. The Schelling point, the place at which these two groups would choose to meet without any coordination mechanism, was the writer’s Substack.
BAM Is Now Reader-Supported
Patrick McKenzie (patio11)
...catch up on these, and many more highlights
Readwise