News for hackers. Stuff that matters.
Re:Does Not Work by wruza on Sunday January 29, 2017 @06:53AM (#13513725)
Heh. A lot of time ago we programmed and created systems for regular business — accounting, automated workplaces, etc. It was all simple, but of course we occasionally introduced bugs here and there, and sometimes an entire module was built in a wrong way (specification errors). I will tell the rest from my pov, because it applied to everyone in general.

For the first hundred of error reports I tried hard to get any information beyond "nothing works" — yeah, not just something doesn't work, nothing does. Phone line diagnostics were hard and both sides quickly tired because of lack of understanding. Me and my client had different sets of terminology, thinking styles and stereotypes. But as the time goes by, my remote-debug skill grows.

And I started to get feedback. It was still inaccurate and often rough, but two things could easily be noticed: 1) there still are people who won't help; 2) people who help have their own ideas on what's happening depending on their [relatively tiny] computer knowledge. That started an era of the great misunderstanding. As we easily exchanged clients in our tight company, we did entire blocks and modules in wrong ways, based on information from incompetent client. We did work that no one needs. We prepared for something, and it was not there. And then I finally got why (partly) 1)-group exists. They just went through all that a long time ago.

The fact is, whether does your client tell you what's happening, or does not, you have to go there and have all of your tools and instruments and anything you have with you. You do not listen on their interpretations. You just go there and say "show me". And only then you have all the information on what is actually happening and where and who is in charge.

After we realized that, we stopped asking for any feedback. Literally. The only two things we needed to know about the problem were 1) is that a "show stopper"? 2) who encountered it. First one makes your weekly plan. Second one gives a hint about a module name and its developer.

We stopped exchanging info from clients, intentionally. If I need someone to make things for me, I just call and tell him to go to the place and solve anything they need, without details. If I get a call, I just say ok, I'll be there in two hours. That was an improvement.

So, if your client tells you "it doesn't work", just be happy that he doesn't spend your time and be sure that you have remote desktop app or remote access system enabled at his side.

There are no comments on this comment yet.