It’s inevitable that one will make mistakes while doing whatever it is they do for their job.
However, take situation A:
Harry America is working on Joe Customer’s old car. Harry needs to perform maintenance on Joe’s carburetor. While monkeying with the fuel jet, Harry drops the nut that holds the carburetor together down the manifold into the engine block. Harry is, for the most part, screwed. He really should have taken the carburetor off the manifold before working on it. Harry does, however, have possible retribution for the mistake, however ugly and time consuming it is.
…now, compare situation A to situation B:
Matt…err, we’ll call him Max. Max Henderson, the mighty IT administrator. Max is making adjustments to Joe Important’s database systems, where the database importantdb is chugging away, doing important things which Joe relies on 24 hours a day.
Max is given the charge to expand Joe’s empire and creates the database importantdb2:
create database importantdb2;
A few minutes later, it is concluded that importantdb2 should be somewhere else, not on the same system as importantdb.
So, Max removes importantdb2:
drop database importantdb;2
..whoops! Max was typing too fast and made a small error. It should have been:
drop database importantdb2;
The result of the misplaced semicolon instantly trashes Joe Important’s extremely valuable database. Weeping and gnashing of teeth occur. Max prepares for seppuku. Max is, without a doubt, completely and utterly screwed. He really should have been typing a bit more carefully. There is no chance for retribution.
…
I should have been a mechanic.