Catching up: Thursday.
Apr. 12th, 2004 01:02 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
elfsWell, my weekend started off with a nuisance. I took Friday off from work so I could attend Norwescon, which opened Thursday evening. So, I get there Thursday evening only to get a call saying I have to come back to the office and fix a bug. The "Now, Or Else" was very clear.
I get back to discover that the bug is rather boring. When creating a Microsoft Windows share on our product, if you decide not to use the wizard but instead choose to edit the field values directly (the advanced view) and you neglect to type in a name for the share, you're supposed to get a warning and then get sent back to the wizard's opening page to type in a name. Instead, you get the warning and then a blank screen. If you hit the 'Go Back' button, you get the opening page and can proceed. This is (a) a relatively rare operation in the field, (b) requires user stupidity to make the bug arise, and is (c) completely cosmetic.
I fix it. But I questioned why the bug was given a "Priority 1: Critical" status in the first place. Apparently, the triage team thought that the bug meant that the "advanced view" was completely inaccessible. It was not, and even the initial bug report said so. They just misread it. When it was passed by my manager, he said the same thing and apologized for misreading it.
Y'know what I think happened? I think my manager knew that the priority change was unnecessary, but he wanted the fix made because if it went in before midnight, his would be the only department with zero bugs when Release Candidate One was compiled-- and wouldn't that just look marvelous on his record?
I get back to discover that the bug is rather boring. When creating a Microsoft Windows share on our product, if you decide not to use the wizard but instead choose to edit the field values directly (the advanced view) and you neglect to type in a name for the share, you're supposed to get a warning and then get sent back to the wizard's opening page to type in a name. Instead, you get the warning and then a blank screen. If you hit the 'Go Back' button, you get the opening page and can proceed. This is (a) a relatively rare operation in the field, (b) requires user stupidity to make the bug arise, and is (c) completely cosmetic.
I fix it. But I questioned why the bug was given a "Priority 1: Critical" status in the first place. Apparently, the triage team thought that the bug meant that the "advanced view" was completely inaccessible. It was not, and even the initial bug report said so. They just misread it. When it was passed by my manager, he said the same thing and apologized for misreading it.
Y'know what I think happened? I think my manager knew that the priority change was unnecessary, but he wanted the fix made because if it went in before midnight, his would be the only department with zero bugs when Release Candidate One was compiled-- and wouldn't that just look marvelous on his record?
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2004-04-12 01:17 pm (UTC)Y'know what I think happened? I think my manager knew that the priority change was unnecessary, but he wanted the fix made because if it went in before midnight, his would be the only department with zero bugs when Release Candidate One was compiled-- and wouldn't that just look marvelous on his record?
Is it cultornei to, ummm, remind said mgr of the over the top support you're giving him at, say, next review time. Document this instance, anyway, I suggest.
"Speak funny you would too, if Frank Oz's hand up your butt was..."
no subject
Date: 2004-04-12 02:54 pm (UTC)no subject
Date: 2004-04-12 02:59 pm (UTC)And unless you want to get 0wNed by the PHB, make it very clear next time you declare vacation that you're Leaving The Known Universe and are Inaccessible until such time as your granted vaca is over. 24x7 coverage demands combat pay, and even then some things aren't worth it.