Weekly Reflection #32 - Fear is a Diagnostic Signal


This week on Book Overflow, Pramod Sadalage came on to reflect on Software Architecture: The Hard Parts. He co-wrote it, along with Building Evolutionary Architectures, the book behind Weekly Reflection #19 - Design for Evolution. In our most recent interview, he described a SQL Server database with 287,000 tables. Nobody wanted to touch it, because any change might break something no one knew was connected. Pramod treats that fear as a measurement. It marks where the coupling is hidden. So he goes looking for it. He instruments the system to see what talks to what, adds indirection, and replaces direct access with real boundaries. Once the dependencies are visible, the system can change again.

The same holds outside of code. The part of your work or life you are most afraid to change often has the most hidden coupling. Fear is a diagnostic signal. Follow it.


Wisdom

Problems that remain persistently insoluble should always be suspected as questions asked in the wrong way.

Reflection

What are you afraid to touch, and what is that fear trying to show you?


Lagniappe

  • This week on Book Overflow, Pramod Sadalage joined us to reflect on Software Architecture: The Hard Parts. He's such a wealth of knowledge on the tradeoffs and complexities of designing systems with data.
  • I've been exploring Penrose tilings, patterns that never repeat. I built a small interactive one you can try: Penrose Tiles.
  • As always, I'd love to hear your thoughts. Reply and let me know what resonates.

Weekly Reflections Newsletter

Practical insights on platform engineering, developer experience, and building teams that ship. Each issue is written to be useful, actionable, and applicable. No filler, no promotions-only emails. Enter your email and sign up for free right now.

Read more from Weekly Reflections Newsletter

Each week, I share one insight. One piece of wisdom. One question to reflect on. (and a little Lagniappe) Insight I've been working with someone recently, migrating a manual, multi-step process out of Excel and into a Python workflow. It requires significant upfront work. You have to understand the task before you can automate it. But when you find the right solution, the whole thing runs without you. It's a thing of beauty. Effective automation drives the toil of a task toward zero. Wisdom...

Each week, I share one insight. One piece of wisdom. One question to reflect on. (and a little Lagniappe) Insight At PlatformCon 2026, Kelsey Hightower gave a talk titled ZTA: Zero Token Architecture (a name he admits isn't really a thing, but it sort of is now, isn't it?). The whole idea comes down to: don't outsource your ability to think, just because these tools exist. One of his examples involves working with database tables. Someone teaches an AI agent to build one, then asks it to...

Each week, I share one insight. One piece of wisdom. One question to reflect on. (and a little Lagniappe) Insight Years ago, I was working at a company that cut head count. My team worried about how we would keep up with the same work. Our manager stopped us and said, "No, we'll do less with less. The company made this decision, and now we will prioritize accordingly." Wisdom There is nothing so useless as doing efficiently that which should not be done at all. Peter Drucker, The Effective...