Build

This book feels like advice from someone who has the scar tissue to be blunt. It's opinionated, practical, and much more useful when read as pattern recognition than as a universal playbook.

The sections on product taste and team standards are the ones I keep coming back to. Fadell is good at connecting tiny execution details to the larger question: does this thing actually deserve to exist?