## The Tornado Test Adam Jacob (Chef's creator) opens with a thought experiment: a tornado destroys your datacenter cage mid-movie-night. Because the original infrastructure was built as code, recovery is just: sign up for a cloud provider, restore off-site backups, provision servers with roles, repoint DNS, restore data. "One hour and forty-five minutes later, you've gone from business-ending natural disaster to finishing your family movie night." ## The Defining Goal "Enable the reconstruction of the business from nothing but a source code repository, an application data backup, and bare metal resources." In a handcrafted-infrastructure world, the same disaster takes weeks or months — replacement hardware alone takes weeks, hand-building takes longer — and by the time you recover, "would anyone care anymore?" ## The Irreducible Constraint Ideally, the single largest constraint on reconstituting the business should be the time to **restore the application data** — the part with real business value. You can speed up acquiring raw resources and configuring them, but data restoration "takes as long as it takes." Contrast the slow rot of hand-managed systems: [[Configuration Drift]].