Join 📚 Josh Beckman's Highlights
A batch of the best highlights from what Josh's read, .
I say the critical resource is not *developer time*, it’s *developer energy*. The “10x developer” may or may not be a myth, but it is no myth that I personally am 10x more productive on days when I am energized than on days when I am exhausted, distracted, and frustrated.
Take Your Pragmatism for a Unicycle Ride
Richard Marmorstein
At least sometimes, it seems, there is more demand for a very safe cash flow *plus* a very risky cash flow than there is for a single blended kinda-risky cash flow.
Money Stuff: Slicing Cash Flows for Better Ratings
Matt Levine
Programming languages evolve to replace the all-powerful "low-level" constructs with more limited constructs that reduce to the low-level ones. It's why you get things like [interfaces over inheritance](https://buttondown.email/hillelwayne/archive/if-inheritance-is-so-bad-why-does-everyone-use-it/).
The corollary of this is that if you use a powerful construct, it should be because the limited one *can't* do what you want. Don't force an infinite for-loop!
Some Notes on for Loops
buttondown.email
...catch up on these, and many more highlights
Readwise