The phone rang, a fight over the implementation engineer, said field data collection does not come up, ask how to solve. I asked the software version of the instrument type, operating system information, specific description of the problem. I told him what might be the reason, gave a solution, let him try. He tried it after that or not, and asked how to do, so I gave him a way, he tried again, and came back and said feedback or not, and asked how I do. I then gave him my offer programs, to continue to address ...... finally resolved.
This scenario not the first time, nor is it a person two people to solve the problem in such a way. In fact, the problem is not complex, some even very simple, simple to the point where just need to restart the software can be solved. However, many people still do not know how to solve the problem. A similar situation also includes developers encounter when programming bug can not get independence, has also been asked my colleagues how to solve.
We have a department architect, he has been engaged in development of c ++ language, c ++ almost any aspect of his difficult problems can be quickly resolved. Need to use mobile applications, Big Data technologies, java, js, python and other development projects in different development language, he can quickly learn from scratch, as we indicated direction, build the frame, encountered new problems, you can always find a solution to solve the problem, to ensure the progress and quality of the project.
I often wonder why this phenomenon? What is the most important capability engineer? I think it is a problem-solving abilities. Be independent, fast and effective solution to the problem, it is the ability to at least one of a good engineer must have. Have the ability to solve problems of people naturally have an own core competitiveness. Others not solve the problem, you can solve; others clash of things that you can settle; others can not handle trouble, you can do it. Something happens promotion of pay, which may not think of your boss? Think of a word, grew more and more sense: "Done is stable, settle is the level."
How to cultivate the ability to solve problems? The topic may be some large, I think the following points:
1, first of all have a sense of responsibility, to put right state of mind to bring the issue as a problem to be handled independently of their own, do not always feel the backing, there is retreat. I clearly have to remember a Implementation Engineer, to call a colleague at the scene, said data acquisition device does not come up. Later, I asked about my colleagues, because data collection software is not installed. This is really a dilemma. Like a person to buy a car, how to step on the gas car sales called and said do not move, because the car is not the same as the key is inserted mobilized. A little bit of knowledge, use our brains and think about it, this low-level jokes do not appear. If you feel that this thing even if you do not, someone will do to help you do so, it is prone to the phenomenon of lazy, to the bed, make a phone call, let others solve their own sleeping there. This state is impossible to have trained any problem-solving skills. Only things as their own thing, they have to face and solve the problem, in order to step up the mind to think how to solve this problem, will it be possible to solve this problem themselves independent, will it be possible to solve this problem through accumulated a similar solution to the problem experiences and lessons. Otherwise, always in a state of zero, there will be no progress.
2, need to reserve certain knowledge and skills. This is the premise. The boss will not arrange for a chef to give the guests a haircut. All scheduled tasks for you, is a high probability in the relevant skill areas you work in, at least to dip side. An engineer must have their own good is a little familiar. This skill or expertise, need to accumulate a certain time, for example, the university is professional or attend a training class and master. Learn the knowledge, master the skill, he has the basic premise to solve the problem in this area. With this premise, an engineer have the ability to solve a specific problem. If you do not have this premise, we can now start learning.
3, cultivating your skills. Have a certain amount of skill to be able to solve some common problems, but want to solve more complex problems, you need more advanced skills. This is the master and cow's request, and would like to become a master, it is essential to spend more time and effort to upgrade their skills. "Ten thousand hours theory" describes a person wants to become experts in a particular area, you need to accumulate ten thousand hours of. This may be no shortcuts to take, but to master the skills of a good solution to the problem, there will always be some good way to accelerate the time to master the skills. Some students like the student mastered the method is suitable for their own learning, to achieve a multiplier effect. Good approach is to think more about their own needs more practice try to figure out, slowly summed up a routine, which usually requires more practice to learn. In short, you have to pay, and in the course of the effort, and continue summarizes, to put your skills trained reached a pinnacle.
4, a method of thinking and problem-solving. With a deep technical skills, a person's energy is limited, too often a particular aspect. When a problem occurs beyond the technical field of a well-known person, we need to have a certain way of thinking and problem-solving methods, in order to further solve the problem. For example, if only one embodiment of the software engineer implemented well aware, and on-site computer network, database and other ignorant, he still can not solve the ultimate problem. So, he needs a global vision of all aspects related to the problem, he must understand the root of the problem to a comprehensive analysis of where, and then find a way to solve the problem. Problem-solving thinking, including steps to resolve the problem of what to do first, what to do the second step, the association between the problem, how about if the first step, then the second step should be done. We have the solution to the problem of thinking and methods, even if a particular aspect of the lack of appropriate skills, it also can have some temporary learning skills in order to advance the progress of solving the problem. In addressing these questions, the best step to think, dare to break their own limits, to believe in their potential.
5, good at summing up, forming a knowledge base. After solving a problem, we should pay attention to sum up the best record. Take programming, often encounter such a situation, I encountered a bug, it took some time and effort to solve, very happy. After a couple of weeks, you may have encountered the same bug, then just remember that solved this bug, but how to solve, forget the need to re-find information, but also spent a lot of time to solve it. While eventually resolved, but still waste a lot of time. If after the solve the problem, timely recording method and steps of solving encountered the same problem again, you can quickly get rid of it that way, saving time is their own. It's a bit like a student "wrong title" and sometimes a question wrong, when the next encounter, but also can make mistakes. Because this is a bad place to master student, weak knowledge areas. With time "wrong title" deepen the impression for the wrong problem, more concerned about learning, then encountered a similar problem, it becomes a familiar knowledge, and they will not be wrong. As more and more problem solving, knowledge own form of increasingly large, the ability to engineer the natural growing.
How to enhance problem-solving skills, there are many ways and means, all roads lead to Rome, as long as the problem seriously, I believe that sentence: Nothing is unachievable.
----------------
Disclaimer: This article is the original article CSDN bloggers "beyondhaven", and follow CC 4.0 BY-SA copyright agreement, reproduced, please attach the original source link and this statement. .
Original link: https: //blog.csdn.net/beyondhaven/article/details/78494936