Clean Code

A genuine classic, and one of those rare books that belongs on every engineer's shelf. It is a bit dated in places, but the fundamentals it teaches are timeless — this is a must-read.

What Martin gets right is that code is read far more often than it is written, so writing for the reader is the whole game:

Clean code reads like well-written prose.

The ideas that stuck with me:

• Meaningful names. A good name does the work a comment would otherwise have to — intention-revealing names let code read like prose.
• Small functions that do one thing. Tight, single-purpose functions you can hold in your head all at once.
• Code as documentation. A comment is often an apology for code that failed to explain itself; fix the code first.
• The Boy Scout Rule. "Leave the campground cleaner than you found it" — craftsmanship as a continuous habit, not a one-off cleanup.

Where I push back: the examples are very Java/OOP-centric and feel of their era, and some advice is taken as gospel. The push to split every function into tiny 1–2 line pieces, in particular, does not always hold up — sometimes it fragments the logic more than it clarifies it. Take the principles, not every rule literally.

Still, a fundamental and great read. A must-read for every engineer.