Project Hail Mary

A novel, and an easy recommendation for engineers.

What it's about

A man wakes up alone on a spacecraft with no memory of who he is or why he is there. As his memory returns in pieces, he learns that the Sun is dimming, Earth is in trouble, and he may be the last chance to find out why. I will stop there, because the best parts of the book are the ones you should meet cold.

What stuck

It is a debugging story. Almost every chapter is a hypothesis, a cheap experiment, a surprising result, and a revised model. The science is carefully worked through, and the fun is watching someone reason from first principles under pressure with limited tools.

Memory loss as a design device. Because the narrator rediscovers his own past, the book keeps asking how you trust knowledge you cannot remember acquiring. That is uncomfortably close to working in a codebase you inherited.

Collaboration without a shared language. Without spoiling anything: some of the best problem-solving in the book happens between minds that have to build a common vocabulary from nothing. It is the most optimistic take on cross-team communication I have read.

What I'd apply

• When stuck, shrink the experiment. The fastest progress in the book always comes from the smallest test that could change the model.
• Write down what you know and how you know it. Future you is often the amnesiac.