Carefully prioritize the bugs

Monday, May 22. 2006

This morning I got a high priority e-mail sent out the day before telling me that there was an urgent bug which has to be fixed as soon as I stepped in the office. Without spending time blinking my eyes, I launched the bug database and search for the bug, but the bug's description surprised me:

A full stop has to be added to the end of the message.

According to the bug reporter, the bug was categorized as urgent because the users are doing the testing and the bug has to be eliminated before any user notices it. The explanation might sound reasonable but yet they're taking a very high risk that the programmers may not feel the importance and pay full attention on any up-coming urgent bugs.
Urgent bug has to be, at least, look like urgent.

Posted by Steven Yong in non-computer at 08:26 | Comment (1) | Trackbacks (0)

...

Trackbacks

Trackback specific URI for this entry

No Trackbacks

Comments

Display comments as (Linear | Threaded)

LOL!!!!

Well, its down to people's perceptions. For this person, the language and grammar of the message is very important to the person.

I'd guess this person is a perfectionist or very detailed person to have caught that bug.

Anyway, I got this bug request before from my product manager, who also said, "please add a fullstop at the end of the message." when they did this testing. I was concerned for the # of characters left (because it was a mobile message) but they insisted. In the end, the message was lengthened to 2 SMS (2 x 160) characters long. What does this mean? Higher cost per message borne by the company because we can't forward the cost to the consumer.