The Baker's Quiet Starter: On the Culture That Rises While the Oven Sleeps

There’s a rhythm to baking sourdough that feels deeply unnatural to the modern tech mindset. You can’t rush it. You mix flour and water, and you wait. For days, this seemingly inert paste, your "starter," does nothing you can easily measure. Then, almost imperceptibly, it begins to live. It bubbles, it rises, it develops a distinct personality. The baker’s primary job during this phase is not to *do*, but to *observe* and *maintain*. They feed it, they check its activity, they learn its tempo. This patient cultivation of a living culture, I’ve come to believe, holds a profound lesson for those of us tending to small services and systems.

In our world, we are obsessed with the bake—the deployment, the push to production, the moment the hot loaf comes out of the oven. We focus our monitoring on the critical minutes of a release, watching graphs for spikes in CPU or memory. But the baker knows that the quality of the bake is entirely dependent on the health of the starter, a health that was determined hours or even days before, during the quiet, unglamorous time when the oven was cold. Similarly, the real resilience of our systems is often built not during the frantic incident, but in the long, uneventful stretches between them.

Feeding the System's Culture

A neglected starter becomes acidic, weak, and eventually dies. It loses its ability to leaven bread. Our systems have a culture too—an operational culture comprised of backups, logs, and routine maintenance scripts. If we only attend to them during a crisis, we find they’ve gone flat. A backup schedule is not a set-and-forget solution; it is a living process that needs regular "feeding." We must test the restore process, verify the integrity of the archives, and prune old data. This is the equivalent of the baker discarding a portion of the starter and feeding it fresh flour and water. It’s a ritual that ensures vitality.

Logging, in this analogy, is the baker’s notebook. It’s not just for diagnosing a burnt loaf. It’s the daily record of ambient temperature, of how long the dough took to rise, of the look and smell of the starter. These seemingly mundane entries create a baseline of normalcy. When something subtle shifts—a process taking a few seconds longer, a small increase in warning-level messages—we can detect it. We can sense the change in the system’s "activity" long before it fails to rise altogether. This is the value of observability during peacetime; it’s how we learn the unique temperament of our services.

The parallel extends to our own habits. The baker’s quiet, daily interaction with their starter is a form of mindfulness. It forces a slowing down, a connection to the fundamentals. In the same way, the practice of reviewing quiet logs, of running a non-urgent backup drill, or of documenting a simple procedure grounds us in the reality of our systems. It builds a deep, intuitive understanding that no amount of frantic firefighting can provide. The goal is not just to have a system that works, but to nurture one that is alive, resilient, and whose health we understand so intimately that we can sense a problem long before the alarms scream. We must learn to value the time when the oven is off, for that is when the true strength of the system is built.

Notes & further reading

A few pages I came back to while writing this: