9
I swore by running programs without a dry run, but one crash changed everything.
Now I always do a dry run first (even if it feels like a waste of time).
3 comments
Log in to join the discussion
Log In3 Comments
williamm823d ago
See, I get why @mason.brian says that, but I just learn better the hard way sometimes. That one big crash taught me more than a dozen careful dry runs ever could. For me, it's about knowing the system well enough to guess when you can skip that step and just go for it. Sure, I've messed up, but the direct feedback when something breaks sticks with me.
6
the_noah2d ago
Dry runs might feel slow, but @mason.brian is right that they stop big crashes from happening. Those crashes can cost you more time to fix than just doing a careful check first. In the end, it's better to be safe than sorry.
8