The Art of Doing Science and Engineering: Learning to Learn
Source: https://press.stripe.com/the-art-of-doing-science-and-engineering ↗
Hamming's final lectures at the Naval Postgraduate School, delivered over many years and published here in the Stripe Press edition that brought the book to a new generation.
These are not technical lectures but a master class in thinking about thinking — how to choose problems worth working on, how to recognise when you are avoiding the important work, how to position yourself for luck, and why most capable people fail to do first-rate work.
The chapter "You and Your Research" is one of the best essays on intellectual ambition ever written and has been passed from hand to hand in research labs and engineering teams for decades.
Hamming's core question — "What are the important problems in your field, and why aren't you working on them?" — is as uncomfortable for a product director as it is for a scientist.
The book is simultaneously practical and philosophical, and it rewards rereading at different stages of a career because the same passages acquire different meanings as your context changes.
Central argument
Hamming argues that doing first-rate work is less a matter of raw talent than of conscious choices about how you think and what you work on — specifically, that most capable people fail not from lack of ability but from avoiding the problems that actually matter. His central claim is that intellectual courage, the willingness to ask 'what are the important problems in my field and why am I not working on them?', is the distinguishing habit of those who produce lasting contributions. He further argues that luck is not random but can be cultivated by positioning yourself at the intersection of knowledge, open doors, and prepared attention.
Critique
Hamming's framework is built almost entirely from the vantage point of an elite researcher at Bell Labs — an institutional environment so exceptional in its resourcing, freedom, and peer density that his prescriptions for choosing important problems presuppose a degree of autonomy that most practitioners simply do not have. The argument quietly conflates individual intellectual agency with structural privilege, making it difficult to distinguish whether the lesson is 'think more ambitiously' or 'get yourself into a better institution first'. A thoughtful reader might also note that his framing of first-rate work is implicitly individualist, offering little account of how collaborative or organizationally constrained contexts change what it means to work on the right problem.
Why it matters for product
The question Hamming forces — why are you not working on the important problems? — cuts directly at a failure mode common in product leadership: spending the majority of strategic attention on problems that are urgent, visible, or politically safe rather than on the ones that would actually change the trajectory of the product or company. For a CPO, this reframes roadmap prioritization and discovery investment not as resource allocation problems but as tests of intellectual honesty about what the team is collectively avoiding. His point about positioning for luck also has direct organizational design implications: the structures that allow weak-signal insight to surface — cross-functional exposure, protected exploration time, access to adjacent domains — are not overhead but the conditions under which important problems become visible.