Reading (3): Is your light on? -- Locate the real problem

Author: fasiondog
Source: http://blog.csdn.net/kongdong

Fourth question: who is the problem?

When others can solve their own problems well, do not go beyond the limit.

If this is their problem, let it be their problem.

If someone is able to solve this problem, but he will not encounter this problem, the first thing you need to do is to make him feel the problem.

Try again and blame yourself-even if there is only one second

Think of the problem as their problem-is your light on?

If people's lights are on, a small reminder may be more effective than your complicated solutions.

As you may want:

"Do not go beyond the proxy", maybe it is one of the rules that QA should follow. Its highest strength is to encourage the product to solve its own problems. The skill should be to let the product fully understand the problem and work with the product to find a solution. Simply relying on the process to blame the product for not doing well or doing well, it will only get bored, the reason is very simple, because it does not understand the disadvantages and consequences of violations of the process. Good QA, of course, should also understand the reasons for the process arrangement if it wants to benefit the product itself. Otherwise, it will be boring like the useless supervisor for a long time, it is better to write a Checklist and throw it to the product for self-check.

Maybe, no matter what you do, you must make others feel useful. It is indeed for the sake of it and really help. This "sincerity" is the key behind it. Only those who respect others can win the respect of others. Yesterday, a SE (girl) called me and almost cried. I asked my apprentice to provide precautions for the project beforehand. I quickly comforted a few words and asked why. It turned out that the apprentice refused to provide the precautions in advance and was still hurtful, it should have been said that they did not have enough level. "Guidance" was originally one of the main responsibilities of QA. Besides, this requirement was not too great. I called the apprentice to talk about it. The apprentice was actually very studious and very interested in the soft engineer, however, it seems that some developers are not very good at it, and they are easy to hurt people when talking. In fact, SE is eager to do a good job, so it will be anxious and angry. This does not provide a good environment for QA to do a good job. Alas, it is sad to say that this kind of practice has a great relationship with the orientation of the current Department. The prospective new supervisor Peng manzhi said that it is necessary to let the QA out of guidance and only audit, and he will disagree with his opinion, I had a big quarrel with each other several times, and it was estimated that I would not be able to stay in the Department. It was just because I really liked QA work, and I was not so sure whether I was so specific to the old supervisor, I just mentioned the need for back-development. At present, the old employees in the department have quietly asked the old supervisor to leave the team, and the new employees have also heard the so-called Department experts and prospective supervisors give speeches about the QA career, I began to plan to leave one after another. I don't know what the real reason behind the departure was. Maybe I should make up my mind to leave, but I really like quality work.

"If people's lights are on, a small reminder may be more effective than your complicated solutions, QA sends a short reminder email to the project team to remind you of the precautions. It is easy for you and others. If you are interested, sort out the reminder emails at each stage, so you don't have to worry about it every time. To be honest, the process is still very complex. Even QA is hard to remember every detail, let alone busy PL. A kind reminder is that you have paid less and gained more. Why not?

I think of the most taboo issue in online posts, but I don't know the source. Criticism and complaints are inevitable. However, I have to look at myself from another perspective and see if I have provided other people's means of posting, for example, you can help to indicate the author and source directly before and after your article. The reseller only needs to Copy & Paste, saving the author's hard work of writing the author and marking the source.

The author also gave an example, which has a great sense of life and skill. It is worth learning: "A friend of mine, a level-1 professor, often takes a nap after a big dinner at a senior Hotel, I found that I didn't bring any money. In this case, he just smiled and looked at the hotel manager and said, 'We're in trouble '. You can imagine what the consequence would be if he said, 'You're in trouble? Or is he saying, 'I have trouble '?"

Http://blog.csdn.net/KongDong/archive/2006/03/15/624636.aspx (1 ):

Http://blog.csdn.net/KongDong/archive/2006/03/19/628789.aspx (2)