If you’ve ever done defect management you’ll understand. You get a ticket for a ‘bug’. You go and research the bug, spend a few hours trying to duplicate. Ah ha, you’ve duplicated it! Now dig through tons of code and find out exactly what is happening. Ok, now let’s go through the business requirements and see if what you’re seeing in the code exactly matches the requirements. Yes, it does. (You might say, hmm, why don’t you check the requirements first to see if it’s working the way it should? That would imply the processes aren’t so complicated that you can tell right away from the bug’s scenario what logic is actually taking place). It’s just not what the business team expected to happen (which usually varies quite a bit from what they stated should happen in the requirements.
Thus, the ticket, after several pointless hours, is marked WAD (working as designed). That, and the bug fixer (me) goes and bangs his head against a wall, screaming. Well, ok, maybe just in my mind I do.
*sigh*
Having worked in IT and various related departments, you have my sympathies.
August 5, 2004 @ 4:42 pmThanks. Actually, it wasn’t that bad, but it is annoying! Just glad it’s Friday now.
August 6, 2004 @ 9:06 amUm, I wonder what the ‘MF’ stands for above? Mainline Found? Major Function? Majorly Fubarred? Mother F*cker? Majorly F’d?
WTF?
August 7, 2004 @ 1:54 amI left it open so the reader can choose his or her favorite.
August 9, 2004 @ 6:56 amI look at it this way….as long as they pay you, who cares?
August 9, 2004 @ 7:53 amGood point. That’s usually the idea in my head, and part of the reason I stay: it pays well, I generally enjoy the work, the people, environment, and benefits are good. And, I don’t care THAT much, I’m just here to do a job and go home!
August 10, 2004 @ 10:37 am