Reading
Books I finished and keep recommending, with one line each on why. No ratings and no reading tracker — this is a shelf, not a diary.
15 books. Last edit 2026-11-18.
- Guns, Germs, and Steel — Jared Diamond
The best argument I know that geography, not talent, decided which societies ended up with steel. - The Prince — Niccolò Machiavelli
A short, cold manual on power that is still uncomfortable because it is still accurate. - The Socrates Express — Eric Weiner
Philosophy as a travel book. The chapter on walking is the one I keep coming back to. - The Psychology of Money — Morgan Housel
About behaviour more than money. Being rich and being wealthy turn out to be different problems. - Visual MBA — Jason Barron
Two years of business school drawn by hand in an afternoon. Useful when you have to argue with product. - Collapse — Jared Diamond
How societies talk themselves out of the evidence in front of them. Gets less comfortable every year. - Negeri di Ujung Tanduk — Tere Liye
A Jakarta thriller about money and politics that gets the arithmetic of power right. - A Brief History of Time — Stephen Hawking
The first book that made the universe feel like a system with mechanics instead of a mystery. - Teh dan Pengkhianat — Iksaka Banu
Short stories from the colonial Indies, unsentimental, and a sharper history lesson than most history books. - A Philosophy of Software Design — John Ousterhout
The best short book on why code gets hard to change. Deep modules, narrow interfaces, delete more. - Designing Data-Intensive Applications — Martin Kleppmann
The book I keep within reach. Every distributed system failure I have seen is in here somewhere. - The Pragmatic Programmer — Andrew Hunt & David Thomas
Advice from 1999 that has aged better than most advice from last year. - Clean Architecture — Robert C. Martin
Read it for the dependency rule and the boundary chapter, then argue with the rest. - The Phoenix Project — Gene Kim, Kevin Behr & George Spafford
A novel about deploys and incident response, and still the most accurate description of an on-call week. - Algorithms to Live By — Brian Christian & Tom Griffiths
Computer science as a way to decide when to stop looking, when to settle, and when to commit.
The Indonesian titles are here because they are the ones I lend out.