I've got mixed emotions here. First, I do agree that the best of us will make mistakes. No question about that.
But that's also why we have certain procedures at work and those procedures also include some checks and balances. "Urgencies" and "Emergencies" all follow the exact same procedure as all of the normal stuff except that we have people standing by to accelerate the steps in the process.
"The Process" we follow has prevented us from making many mistakes and, don't forget, you'll make the most mistakes when you can least afford to and that's when there's an emergency.
With that in mind, there is something pretty much unforgivable at work and that's when someone doesn't follow the established, documented, buttered and breaded, very well known process. That doesn't happen anymore, either. We're pretty close to zero defects being deployed to production and we haven't deployed even a missed defect in well over 2 years or so.
It DOES take teamwork, though. Even in previous companies I worked for, we were doing what people are calling DevOps long before it became a term (current company employment started after that).
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)