Books that shaped how I think about engineering, systems, and craft.
The best book on software complexity I have read. Ousterhout argues that the primary goal of software design is to reduce complexity — and that most engineering decisions should be evaluated through that lens. The concept of deep vs. shallow modules alone is worth the read.
A timeless collection of principles that have aged remarkably well. The tracer bullet concept, DRY, orthogonality, and the broken windows theory of code quality — these ideas underpin how I approach every project. Required reading for engineers at any stage.
The definitive text on the systems that power modern software. Kleppmann covers databases, distributed systems, stream processing, and the fundamental trade-offs between consistency, availability, and partition tolerance with exceptional clarity. I return to this book regularly.