Skip to content

Instantly share code, notes, and snippets.

@cchandler
Created November 25, 2015 00:24
Show Gist options
  • Save cchandler/9fe9dd6163711a53600c to your computer and use it in GitHub Desktop.
Save cchandler/9fe9dd6163711a53600c to your computer and use it in GitHub Desktop.
If I were going to expand on the point, it's not that testing in production is good or desirable, but rather that
the long-tail of eventualities+inputs real-world code will face over time is not "testable" in the classic sense.
There's no unit/integration test for "a chiller failed in the datacenter and half my servers are exhibiting heat-related failure"
or "this particular version of linux in production has a probabilistic XFS locking bug that kills my thread"
To be crystal clear, I am in no way advocating _against_ unit or integration testing. I think both are critical. I am just also
cognizant of how complex things breakdown over time. I'm thinking of operational maturity as how well an organization writes
software to embrace the certainty of failure and improve telemetry/introspectibility to deal with said disaster.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment