(no subject)
Nov. 5th, 2004 01:50 pmFor a moment, let's pretend that you're a software developer. For some of you, that won't be much of a stretch, since you're already software developers. Then let's pretend that you want to really piss off the people who test your code— which, to the best of my knowledge none of you do, at least intentionally.
Here's a good way to do it:
When a tester comes to you and tells you that something is a blocking issue (for those of you not in the industry, it's just what it sounds like- a code problem which completely stops test progress on something, and which needs to be fixed ASAP), nod and indicate that you have an idea what needs to be fixed. Then, when the tester comes back hours later, wondering why he hasn't heard anything, indicate that you haven't done anything about it, but will send notification when you're done so that the whole thing can be rebuilt.
Two and a half hours, and i'm still waiting, and this wasn't an "i just can't figure out why this isn't working" issue, but a "this file has the wrong namespace, this database proc needs to be in this label, and you need to give me these navigational elements in this version.
Here's a good way to do it:
When a tester comes to you and tells you that something is a blocking issue (for those of you not in the industry, it's just what it sounds like- a code problem which completely stops test progress on something, and which needs to be fixed ASAP), nod and indicate that you have an idea what needs to be fixed. Then, when the tester comes back hours later, wondering why he hasn't heard anything, indicate that you haven't done anything about it, but will send notification when you're done so that the whole thing can be rebuilt.
Two and a half hours, and i'm still waiting, and this wasn't an "i just can't figure out why this isn't working" issue, but a "this file has the wrong namespace, this database proc needs to be in this label, and you need to give me these navigational elements in this version.