From programmer to project manager: be persistent but not stubborn
There is no shortcut to the growth of a programmer . Only by persevering and persistent pursuit can one become an excellent programmer. Perseverance is valuable, but if you can't reflect on yourself often, you may fall into a stubborn situation.
1. Programmers need a little perseverance
There is a famous saying by Xu Sanduo in "Soldier Assault": "Don't give up, don't give up", which is a precious persistent spirit. It is through this persistent pursuit of not abandoning and not giving up that Xu Sanduo has grown from an ordinary soldier to an elite of the regiment. This is also true in real life. It can be said that everyone who has achieved certain achievements is a persistent person at work.
For programmers, persistence is especially valuable. In the process of programming, we will inevitably encounter various problems. If we do not have a bit of persistence, we will complain and avoid problems when we encounter problems. How can we achieve technological breakthroughs? How can we experience the pleasure of solving problems?
Recalling that when I first started learning GIS (Geographic Information System) programming, the manager arranged for me a difficult problem that had been prohibitive for many people before. The use of MapObjects to realize map symbolization requires the function of a custom symbol library. Based on my experience at the time, I didn't know where to start, but I could only bite the bullet. First of all, after I read all the help files of MapObjects carefully, I found a CustomDraw interface. But it's just an interface, and it's far from a complete symbolic function. How to use this interface? At that time, the Internet was still very backward, there were fewer programming materials on the Internet, and there were almost no Chinese development materials about MapObjects, so I checked the relevant English materials abroad through the snail-speed network, and sought inspiration in just a few words. During that period of time, whether I was eating, sleeping, or walking, I was thinking about technical problems all the time. Thanks to my unremitting efforts, I gained little inspiration again and again and approached the solution to the problem step by step. After 6 months of hard exploration, I finally completely solved this problem recognized in the company, and I myself became the core technical personnel of the company from a layman. During this period of time, I not only thoroughly familiarized each interface of MapObjects, but also learned to use more than 100 Windows APIs, which made a leap in both technical aspects and personal career.
Programmers need some persistent spirit to hone themselves and develop themselves. Only with determination and courage can they become truly excellent programmers.
2. Introspection to eliminate stubbornness
Stubbornness, like persistence, is a spirit of perseverance and not giving up. If this is the case, why do people always praise persistent people and despise stubbornness?
In fact, the difference between the two lies in the direction of persistence. Perseverance and stubbornness are like the two ends of a rope, although they are on the same rope, but in opposite directions. Perseverance is moving in the right direction, a kind of rational persistence, while stubbornness is just the opposite. Since they are all insisting, how to judge whether the direction is correct?
In fact, there is no clear distinction between what is right and what is wrong, otherwise, there would not be so many "obsessed" people. Whether the direction is correct is often measured by the results. Therefore, whether it is attachment or stubbornness, in fact, is mainly result-oriented. If the result is good, it is attachment. If the result is bad, it is stubborn. When Edison invented the light bulb, he still persevered after countless failures, and finally found a way to use tungsten filament as the filament, and achieved success. His persistence we call persistence. Later, Edison founded General Electric Company, insisting on using direct current for power supply, ignoring the huge advantages of alternating current in the direction of long-distance transmission, and finally lost to Westinghouse Electric Company, which adopted the alternating current solution, and he himself only left the company he founded in a dim light. , we can only say that the king of invention also has stubborn moments.
So, do we have to wait for the result to happen to know whether our persistence is right or wrong? Is there a way we can make judgments as we go along? It can only depend on our introspection. Confucius said: "I examine my body three times a day." Anyone who is good at self-examination will not be a stubborn person. They are aware of their own problems at any time and have the courage to rationally deny themselves.
Introspection requires common sense. For a person who does not have common sense, does not understand right and wrong, and does not understand the basic rules, how can he correctly judge the direction? No matter how introspective such a person is, it is useless. He can only achieve real growth by constantly hitting a wall.
I have seen some programmers, when their ideas conflicted with the project manager, they always insisted blindly, refused to give in, and even got into endless quarrels with the project manager, thinking that they had mastered the truth. As everyone knows, contradicting with the boss is a stupid behavior, and such excessive insistence will form a disobedient impression in the boss's mind. What's more, obeying the work arrangement of your superiors is a basic workplace rule. You can make suggestions, but you must respect the decision of your superiors. There is no doubt that in this confrontation, not managing project managers right or wrong, programmers are the stubborn side. If programmers had these basic common sense and kept introspection, nothing like this would happen.
Introspection also requires the courage to break out of your mental comfort zone. Everyone has their own comfort zone, where everything is protected by the subconscious, and everything seems to be taken for granted. Our brains do not need to think too much about things, and we can enjoy the relaxation and pleasure brought by this kind of self-enclosure. There is no doubt that the mental comfort zone prevents us from exploring the depths of things and our acceptance of different viewpoints, so we cannot make a truly objective analysis of what we insist on.
In the quarrel between the programmer and the project manager, in fact, both parties should bravely jump out of their comfort zone, consider calmly whether the other party's point of view is also acceptable, and be a rational adherent, so as to achieve a win-win situation. Perseverance or stubbornness is often just the difference between a single thought.
http://developer.51cto.com/art/201211/364725.htm