Engineering Book Club
@TheEngBookClub
Followers
228
Following
53
Media
2
Statuses
156
An online community to read and discuss engineering books with other professionals. Account managed by @miguelbemartin
World
Joined February 2023
The CAP theorem (Consistency, Availability, Partition tolerance—pick 2) is everywhere in "Designing Data-Intensive Applications." But here's the nuance: You don't choose once. You choose differently for each subsystem based on business requirements. 🎯 #DistributedSystems
0
1
1
Eric Evans' "Domain-Driven Design" is dense (500+ pages), but the core insight is simple: Complex business logic belongs in the domain model, not scattered across controllers and services. Center the domain, everything else is infrastructure. 🎯 #DDD #SoftwareDesign
0
1
0
Eric Evans' "Domain-Driven Design" is dense (500+ pages), but the core insight is simple: Complex business logic belongs in the domain model, not scattered across controllers and services. Center the domain, everything else is infrastructure. 🎯 #DDD #SoftwareDesign
0
1
0
That's true!
@miguelbemartin @TheEngBookClub yeah this is real accountability changes how you process the ideas, not just whether you finish the book
0
0
0
@TheEngBookClub Plus, the 20th anniversary edition updates the technologies referenced and reexamines the assumptions behind the practices recommended in the light of an additional two decades worth of experience. https://t.co/k45lE1WdhJ
0
1
1
"Refactoring" by Martin Fowler isn't just about cleaning code. It's about building the discipline to improve code continuously rather than waiting for a "big rewrite." Small, safe steps compound over time. 🔄 #Refactoring #CodeQuality
0
1
1
The CAP theorem (Consistency, Availability, Partition tolerance—pick 2) is everywhere in "Designing Data-Intensive Applications." But here's the nuance: You don't choose once. You choose differently for each subsystem based on business requirements. 🎯 #DistributedSystems
0
1
1
Gene Kim's research for "The Unicorn Project" found that developers spend only 1-5 hours per week writing new code. The rest? Meetings, debugging, waiting for builds, navigating bureaucracy. Improving developer experience isn't luxury—it's leverage. ⏱️ #DeveloperExperience
0
1
1
"Refactoring" by Martin Fowler isn't just about cleaning code. It's about building the discipline to improve code continuously rather than waiting for a "big rewrite." Small, safe steps compound over time. 🔄 #Refactoring #CodeQuality
0
1
1
The SOLID principles from Uncle Bob's books aren't about making code "perfect." They're about making code flexible enough to survive requirement changes—because requirements always change. 🔧 #CleanCode #SOLID #SoftwareDesign
0
1
1
Gene Kim's research for "The Unicorn Project" found that developers spend only 1-5 hours per week writing new code. The rest? Meetings, debugging, waiting for builds, navigating bureaucracy. Improving developer experience isn't luxury—it's leverage. ⏱️ #DeveloperExperience
0
1
1
"Thinking in Systems" by Donella Meadows isn't a programming book, but it should be required reading for engineers. Software systems exhibit the same feedback loops, delays, and emergent behaviors as any complex system. 🔄 #SystemsThinking #SoftwareArchitecture
0
1
1
In "A Philosophy of Software Design," John Ousterhout argues that complexity is incremental. You don't build a complex system all at once—you add a "small" hack here, a "quick" fix there. Death by a thousand cuts. ⚔️ #SoftwareComplexity #SystemDesign
0
1
0
The SOLID principles from Uncle Bob's books aren't about making code "perfect." They're about making code flexible enough to survive requirement changes—because requirements always change. 🔧 #CleanCode #SOLID #SoftwareDesign
0
1
1
"Thinking in Systems" by Donella Meadows isn't a programming book, but it should be required reading for engineers. Software systems exhibit the same feedback loops, delays, and emergent behaviors as any complex system. 🔄 #SystemsThinking #SoftwareArchitecture
0
1
1
In "A Philosophy of Software Design," John Ousterhout argues that complexity is incremental. You don't build a complex system all at once—you add a "small" hack here, a "quick" fix there. Death by a thousand cuts. ⚔️ #SoftwareComplexity #SystemDesign
0
1
0
Join us tomorrow for an engaging session on the third part of Team Topologies! Don't miss it!
0
0
0
"The Phoenix Project" is technically fiction, but every engineer recognizes their own workplace in it. The book popularized DevOps principles by wrapping them in a story about a failing IT department. Sometimes narrative beats technical writing. 📖 #PhoenixProject #DevOps
0
1
0