"It sounds a bit sadistic," he says. "But it's a really good exercise to do.""
Anyone else finding beauty in this?
The meticulous and tedious, often thankless nature of scientists and their work. Also a nice strategy to implement for some other projects/fields.
Once I write tests for all the things that could go wrong and verify the correct behavior, I feel a lot better than if I only test the happy path (when everything goes right).
I wish software developers would take more time to think about how things could go wrong.
I wish more PMs understood the need to spend developer hours on it.
Only when you've written them all down, do you have a list of things to actively expect to go wrong, and prevent or mitigate.
It is the difference in handling risk between using knowledge, skill, technology, and planning to manage risk, vs relying on Pure Dumb Luck and hoping to get away with something.