Books
Books that actually changed how I work, as opposed to books that were pleasant to read — the overlap is small.
I read slowly, and I reread more than I read.
These are not the best books I know of. They are the ones I actually cite — while writing code, while deciding things, while arguing with people.
-
The Pragmatic Programmer
Andrew Hunt / David Thomas · 1999
Twenty-five years on, every specific technology in it has been replaced and not one of the judgement calls has expired. That says something on its own.
-
Thinking, Fast and Slow
Daniel Kahneman · 2011
It will not stop you making cognitive errors. It will let you recognise them afterwards, which turns out to be worth plenty.
-
1587, a Year of No Significance
Ray Huang · 1981
Uses one uneventful year to show exactly how an institution stops working. Anyone who writes about technical debt should read it.
-
Structure and Interpretation of Computer Programs
Abelson / Sussman · 1985
Took three attempts to finish. The first two failed not because it was hard but because I had not yet hit the problems it solves.
-
The Design of Everyday Things
Don Norman · 1988
I have never since been able to push a door that should be pulled without noticing. The cost is permanent.
-
Siddhartha
Hermann Hesse · 1922
Just over a hundred pages, and I reread it every few years. I underline something different every time.