Engineering Book Club

We are in Discord now! discord.gg/pc2pqxwtHV

Reading is not enough. The real learning happens when you write notes, apply what you read, and discuss it with others. Here is how to make engineering books stick. engineeringbookclub.com/resources/how-…

You do not need to read every word from cover to cover. With the right strategy, you can get through most technical books in about a week and retain what matters. engineeringbookclub.com/resources/how-…

New section on our website: Currently reading and what's coming next. engineeringbookclub.com/currently-read…

Blog posts and videos are great for getting started. But when you want depth, structure, and ideas that stick, nothing beats a well-written engineering book. engineeringbookclub.com/resources/why-…

Over the years, a handful of books completely changed how I think about writing software. Here are the five that had the biggest impact on my day-to-day work. engineeringbookclub.com/resources/five…

Tutorials teach you how. Books teach you why. If you want to escape tutorial hell and build real understanding, start reading engineering books. engineeringbookclub.com/resources/from…

In "Coders at Work," Seibel interviews 15 famous programmers. Common thread: They all read code constantly. Reading others' code teaches you patterns, anti-patterns, and different thinking styles. You can't learn to write well without reading widely.

"Building Microservices" explains that the hardest part isn't the code, it's the data. When you split services, you split databases. Now you have eventual consistency, distributed transactions, and data synchronization problems. Microservices create data problems.

"Domain Driven Design Distilled" is Vaughn Vernon's shorter introduction to DDD. It covers bounded contexts, aggregates, and domain events in 150 pages instead of 500. Sometimes you need the condensed version first to know if you want the deep dive.

"Agile Estimating and Planning" by Mike Cohn teaches that estimates are about conversations, not precision. Story points work because they force discussion about complexity and unknowns. The conversation is more valuable than the number.

In "Implementing Lean Software Development," the Poppendiecks adapt Toyota's manufacturing principles to software. Key insight: Inventory in software is partially done work. Every feature branch, undeployed code, or unvalidated assumption is inventory that costs you.

"The Mythical Man-Month" explains that perfect software is impossible because specifications themselves change during development. You're not building to a fixed spec, you're learning what to build while building it. Accept this reality, plan for it.

Currently reading: Tidy First by Kent Beck.

"Clean Craftsmanship" by Robert Martin argues that professionalism in software means discipline. Write tests first. Refactor constantly. Communicate clearly. These aren't optional nice-to-haves, they're minimum standards for professional work.

"Software Architecture: The Hard Parts" addresses the hardest question: When should you break apart a system? The book provides decision frameworks for granularity, data ownership, and workflow management. Split too early or too late, both hurt.

In "The Art of Capacity Planning," Allspaw teaches that capacity planning isn't about servers, it's about headroom. You need buffer between normal load and system limits. Running at 90% utilization means small traffic spikes cause outages.

"Patterns of Enterprise Application Architecture" by Martin Fowler catalogs patterns like Repository, Unit of Work, and Service Layer. These patterns aren't trendy, but they solve real problems in business applications. Understanding them prevents reinventing wheels poorly.

"Implementing Service Level Objectives" teaches that 100% uptime is impossible and expensive. Choose meaningful SLOs (like 99.9%) and use error budgets to balance reliability with feature velocity. Perfect is the enemy of shipped.