> If you work in a project with automated tests that do not have sufficient coverage, this is just a spectacular way of blowing up production. Great, I'd rathe

> If you work in a project with automated tests that do not have sufficient coverage, this is just a spectacular way of blowing up production. Great, I'd rather have this error cause a loud and obvious failure that can be easily hotfixed, than have it lead to subtly incorrect behavior that goes unnoticed for days and takes another day to debug.