I was once married to a senior level software QA person. She was on the Ventura Publisher 1.0 team if any of you remember that.
When we got married I had just started my programming career, so I used to proudly show off the latest little thing I was working on at home. She was known to lean over and gleefully bang on the keyboard like a drunken chimpanzee (or, you know, the average drummer). Naturally, the screen would go up in flames, smoke would pour out the back of the box and a reboot was never far behind.
The first time she pulled that stunt I asked, "What the hell did you do that for?"
She just smiled and said, "A user might," and then merrily waltzed out the door mumbling something about better error handling.
Reason #1 kazillion why software verification and validation should never be undertaken by anyone who had the remotest (Is that a word?) knowldege of the product or application being developed. I can't tell you how many times we got screwed when the apps team was forced to verify their own code and the minute it got released into the wild, it was Problem Report Central. Conversely, when we farmed V&V out to foreign country test houses (I'm looking at you, India, and you, Bulgaria), we got a kazillion bugs filed... even if they were the most remote of corner cases. "No, 'David' (I know that's not your real name, Srinivasan, so stopping calling yourself that!), no one is going to ever try to do that with the application. Failing our code for something that literally is beyond stupid is not a valid bug!" You'd think they got paid per bug or something.
Ugh... all of this talk of software and bugs is giving me PTSD. I'm going back to pretending to work at my day job.