Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
Other teams, however, put off doing the unglamorous work of removing their dependencies and instrumenting their systems. Instead, they focused too soon on the flashier work of developing new features, which enabled them to make some satisfying early progress. Their dependencies remained, however, and the continuing drag soon became apparent as the teams lost momentum.
Working Backwards
Colin Bryar and Bill Carr
Anytime you’re building a new system, regardless of how technically complex it might be, testing the value of the idea is the best place to start. If no one wants it, it doesn’t matter how hard or easy it is to build it.
How I Break Down Hypotheses to Make Them Easier to Test
Jeff Gothelf
One bit of advice I give writers is to see each draft as a hypothesis or experiment: your job is to gather data to test that version of the manuscript and figure out what’s wrong with it. If it fails, it doesn’t mean that you have failed, but only that the current experiment has. So you redesign it. Shift your emphasis off the personal and back toward the product. Perspective is everything!
Write Useful Books
Rob Fitzpatrick und Adam Rosen
...catch up on these, and many more highlights
Readwise