The most satisfying work I’ve done has been sweeping an empty room, turning off the lights, and closing the door. Because the work was done. Had come to an end. Fin. Entropy reduced to zero.
Having small children and other creatures living with me, it rarely happens that a task is completely done. There’s one more dish to wash, another sock to put in the laundry, more crumbs on the floor, another meal to make. The work is over when I die. For small portions of life, we can pretend that each beginning has an end. We empty one house before moving to another. What if there’s not? How burdensome!
I like to imagine a revolution, the world swept clean by fire before the dawning of a new age. There’s something so easy, so glamorous about a clean slate for starting over. It eliminates all concerns about the moment of transition.
And doesn’t exist.
The other day I watched a lovely little presentation on the benefits of treating infrastructure as code, and managing it holistically, as a software project. It’s a wonderful thought, and one I’ve been an advocate of since reading “Bootstrapping an Infrastructure” around the turn of the century. It’s nice to see the attitude gaining traction some some n years since virtualization made it possible for nearly everyone. But this is an attitude shift, a change in mindset rather than a drop-in replacement for whatever software ails you. What if one, unlike a fancy new software start-up, has existing infrastructure, policies, procedures, and people? How does one adapt to a new paradigm where computing resources aren’t expensive, and the most expensive cost is history and tradition?
Burning it all down is not an option.