(no subject)
Jun. 14th, 2005 10:45 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
nockergeekI would just like to take a moment to say something about customers who lie.
If we give you a week to test the system we're developing for you -- a week during which there are no code changes, and after which only issues brought up in testing will be dealt with -- we expect you to test the system to the best of your ability. This means that there's a basic expectation between developer and client that any feedback you provide on the system will be accurate. When I've tested everything as best I can, and it seems to be working to me, and I give it to you and say, "Look at this, play with it, go through the entire system, and tell me if anything either doesn't work the way you need it to, or breaks because you use it in a way I didn't anticipate," I expect you to do just that, because we're both professionals here. When you turn around and say, "Oh, it looks great, this looks wonderful, I'm very excited," then I'm taking you at your word.
This means that, the day after launch, when you turn around and say, "What about this feature and this feature and this feature? I used to have these (even if I really didn't), and now I don't, and I need them," I feel a little betrayed. You told me that you'd tested it. Then, when you turn around and say, "Oh, no, I didn't really test it," that tells me that you lied to me. It's one thing to say, "I'll test it when I can," and not do it. It's something else entirely to say, "Yes, I tested it, it looks wonderful," and then get short with me when it goes live because it doesn't match your nebulous, unstated expectations.
Hopefully, today will go smoother than yesterday. At the moment, though, I want to set a few choice people on fire with my brain.
If we give you a week to test the system we're developing for you -- a week during which there are no code changes, and after which only issues brought up in testing will be dealt with -- we expect you to test the system to the best of your ability. This means that there's a basic expectation between developer and client that any feedback you provide on the system will be accurate. When I've tested everything as best I can, and it seems to be working to me, and I give it to you and say, "Look at this, play with it, go through the entire system, and tell me if anything either doesn't work the way you need it to, or breaks because you use it in a way I didn't anticipate," I expect you to do just that, because we're both professionals here. When you turn around and say, "Oh, it looks great, this looks wonderful, I'm very excited," then I'm taking you at your word.
This means that, the day after launch, when you turn around and say, "What about this feature and this feature and this feature? I used to have these (even if I really didn't), and now I don't, and I need them," I feel a little betrayed. You told me that you'd tested it. Then, when you turn around and say, "Oh, no, I didn't really test it," that tells me that you lied to me. It's one thing to say, "I'll test it when I can," and not do it. It's something else entirely to say, "Yes, I tested it, it looks wonderful," and then get short with me when it goes live because it doesn't match your nebulous, unstated expectations.
Hopefully, today will go smoother than yesterday. At the moment, though, I want to set a few choice people on fire with my brain.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
on 2005-06-14 03:50 pm (UTC)You do good work.
Setting on fire with your brain...
on 2005-06-14 05:57 pm (UTC)...Oops...I understand...that's not what you meant.
Old Man