Quote:
Originally Posted by DMcCunney
|
I've read that stuff a long time ago. Non-IT people are lusers
The one thing that always stuck to me was:
*Luser nagging for more space on the network drive*
"There. You now have 4 MB of space."
- "Cool, so you upgraded my account to 8 MB?"
"I said: You now have 4 MB of space."
- "Huh? I don't underst..."
*hangs up phone*
"It'll come to him." (*hear evil laughter*)
Quote:
An old friend is a QA engineer. He once said "You know what the difference is between a software developer and a QA Engineer? The developer assumes the code will work. The QA Engineer assumes it will fail!" He was right in his definition, and his assumption.
(Of course, making it fail, and documenting how and why it did is what he got paid for, so he could cite lots of supporting evidence.)
______
Dennis
|
I'm my own QA. If you assume your code works, you're a bad developer; IMHO. I *always* assume my code doesn't work. That's the reason why implementing error handling and testing everything is easily 50-60% of the work I do.
I just get irked when people seeom to think that writing a new function within a program is the same as swapping a tire on a car. "Why would you need to test that? If you do everything correctly it should just work."