Great article and thoughts, Kathi.
One time after making a really big goof, I thought I was going to catch no end of being yelled at. Still, it was important that my boss know the mistake I made and what I was doing to fix it so that he wouldn't also get into trouble. To make a much longer story shorter, my boss liked my plan for fixing the problem I created but I continued to apologize. He told me to stop and said "Look... if you never make a mistake, it means that I'm not pushing you hard enough. You've done well in the past and I wondered when you'd finally make a mistake. Do you need any help fixing it?"
I was gob smacked at his understanding.
That should also be a lesson to some bosses especially if they have folks "living on the edge" for getting things done as fast as possible. It's an old Navy saying... Don't let one "aw-shit" wipe out a thousand "atta-boys". Embrace the absolute honesty and integrity of the person who just put their head on the proverbial chopping block for you.
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
When you put the right degree of spin on it, the number 318
is also a glyph that describes the nature of a DBAs job. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs