The Chimney Sweep's Warning: On the Soot That Cools the Hearth

There’s a piece of received wisdom in our world of small, reliable services that feels as comfortable as a well-worn flannel shirt: automate everything. It’s the mantra. We script our deployments, cron our backups, pipeline our tests, and wire our alerts to pager duty. The goal is a hands-off system, a silent, self-tending engine room where human intervention is a sign of failure. We are told to eliminate the toil, to build a chimney that never needs sweeping. But I’ve come to worry that in our zeal to automate the fire, we’ve forgotten the purpose of the soot.

The soot, here, is the minor friction, the tiny manual check, the occasional walk through the log files just because. It’s the process you haven’t yet—and perhaps never will—script away. The prevailing critique is that this is inefficiency, a relic of a less enlightened ops age. But I’ve watched systems where total automation became a form of insulation, a layer of abstraction so complete that it cooled our intuitive understanding of the hearth’s actual heat. When every alert is automated, you stop listening to the system. You only hear it scream.

Consider the backup. You have a script that runs, encrypts, and pushes to cold storage. A green checkmark appears in a dashboard. Received wisdom says this is a solved problem. Yet, the chimney sweep’s lesson is that you must still, occasionally, feel the draught with your hand. You must, once in a great while, attempt a restore on a throwaway volume not because the alert told you to, but because your gut—trained by past seasons—knows that seals degrade and formats drift. The automated verification is essential, but it verifies only what it is programmed to see. The human glance catches the anomaly it wasn’t told to look for: the logs that are too quiet, the file size that has subtly plateaued, the timestamp that feels off by a season.

This isn’t a call for busywork. It’s a defense of designed friction. A scheduled, deliberate, and yes, manual interaction with the machinery not as an operator, but as a caretaker. The gardener doesn’t automate the feeling of the soil between their fingers; it is the primary sensor. Our equivalent is tracing a request through three services by hand, not to fix anything, but to remember the path. It is writing a one-off query against the log aggregator just to see the shape of a normal Tuesday.

Automation promises freedom from the mundane, and it delivers. But it can also exile us from the mundane’s wisdom. The soot accumulation is data. It tells you about the fuel’s quality, the burn’s efficiency, the weather’s pull on the flue. Sweeping it away blindly every time, without a moment to note its texture, is to discard a system’s gentle, continuous confession. So, keep your brilliant automations. But leave one small, unswept corner. Schedule a quarterly “chimney feeling.” Go to the server room, open the terminal, and just… tend. The reliability you save may be your own.

Notes & further reading

A few pages I came back to while writing this: