(knowledge sharing) hardware and software debugging nine method: Eighth rule to help others, get a new view

1. Soliciting opinions from others

We are all ordinary people, biased or stereotyped about everything, including the idea of where bugs are hidden, which can cause us to be unable to see the facts. Others look at the problem from another point of view (which may also be his own prejudice), but will find new ways to make a big impact on your problem solving.

2. Access to professional knowledge

Sometimes the knowledge of a part of the system seems mysterious, we do not have to go to school for a year, but through the consulting experts to quickly grasp the knowledge, in any case, the experts will understand the system more than we do, so they can know the approximate route map to find the problem, for your search work to provide a good hint.

3. Listen to other people's experience

You may not have enough experience, but you want people around you to quickly describe what's going on, they may have met before and tell you exactly what's wrong.

4, help everywhere

• Seek professional knowledge or experience from your colleagues and experts around you
• If the company has a relevant knowledge management system, you can find useful information from it
• If you use a third-party vendor's software or device, you can ask for help by phone or email.
• If you can access the Internet, you can ask for help through the relevant technical forum.
• There are a lot of resources, such as books, magazines and so on to provide basic and general knowledge, such as tools, programming languages, debugging methods, etc.
• When all the methods fail, go back to the "reading book" and perhaps notice something that was not understood before.

5. Put down your face

When you ask for help, don't assume that you are incompetent, which means you are anxious to fix the bug, and if you get the right understanding, expertise and experience that will help you fix the problem faster, it will not reveal your weaknesses, but can make you grow. The opposite is also set up, do not think experts are God, they will make mistakes, if adhere to their own is wrong, the experts are right, may be worse!

6. Report symptoms, don't tell your theory

When you're looking for help, describe what's happening and what you see, including what happens intermittently, what's not, don't tell you what the reason is, don't tell your judgment, or you'll bring someone you ask for help into your circle of thought! Conversely, if others want you to ask for help, but explain his judgment to you, be sure to cover your ears and run away to avoid being contaminated by his theory.

7. You don't have to be very sure about the questions you ask

Some areas are poorly judged gray areas, such as some that seem wrong, but are not sure why, and are worth proposing, which may not be relevant to the problem, but really useful information to solve the problem. The author gave a practical case, whenever he wore a plaid shirt from a chair to debug the camera, the camera will crash, must reset the initialization to work properly, after submitting to the supplier, they found that the lattice shirt graphic movement, resulting in the camera internal graphics processing algorithm crashes.

(knowledge sharing) hardware and software debugging nine method: Eighth rule to help others, get a new view