1. Sound foundation. Data structure, discrete mathematics, compilation principle, these are the foundation of all computer science, if you don't master them, it is difficult to write high levels. According to my observation, learning computer majors can more written high quality software than those in other industries. The program will write, but when you find that it is difficult to write a certain degree, it should think about whether it is to go back to learn these most basic theories. Don't go to learn OOP at the beginning, even if you are fine, you may have no hand when you encounter some basic algorithms. 2. Rich imagination. Don't stick to a fixed way of thinking. When you encounter problems, you should think about several solutions to solve the problem, try the way others have never thought about. Rich imagination is based on rich knowledge, except for computers, more about other disciplines, such as astronomy, physics, mathematics, etc. In addition, it is also a good way to see more sci-fi movies. 3. The simplest is the best. This may be a criterion following all sciences. Such complex quality interchange principles are just a simple formula that is simple in Einstein: E = MC2. A simple approach is easier to be understood, more easily implemented, and more easily maintained. When you encounter problems, you should give priority to the easiest solution, and only the simple solution cannot meet the requirements. 4. Do not drill the horn. When you encounter obstacles, you may wish to stay away from the computer, look at the scenery outside the window, listen to light music, chat with friends. When I encounter a problem, I will play games, and it is the kind of violent fighting game. When the part of the brain cell responsible for the game, the part of the brain cells responsible for programming have been fully resting. When I started working, I will find that the problem is now able to solve it. 5. The desire for the answer. The history of human nature science is a process of eager to get the answer, even if you can only know a small part of the answer, we pay for us. As long as you firmly believe, you must find the answer to the question, you will pay energy to explore, even if you don't get answers, you will learn a lot during the process. 6. More than others. Three people must have my teacher, maybe in a conversation with others, you can spark. Many up-to-go, see what others' views on the same issue will give you a lot of inspiration. 7. Good programming style. Pay attention to develop a good habit, the indentation of the code, the naming rules of the variable should be consistent. Everyone knows how to exclude the error in the code, but often ignore the missed troubleshooting. Note is an important part of the program, which allows your code easier to understand, and if the code has clearly expressed your thoughts, you don't have to add any comments. If the comment and the code are inconsistent, it is even worse. 8. Toughness and perseverance. This may be the "master" and general programmers the biggest difference. A good programming is 99 weat and 1ffee. Masters are not genius, they are hone in countless daysday night. Success can bring us extremely joy, but the process is incomparably boring. You may wish to do a test, find a number of items within 1 0000, copy them all, then check three times, if you can complete this work, you can meet this.
-------------------------------------------------- ------------------------------
* Amazing knowledge, and you can add your own knowledge and improve your knowledge structure * Pariety, especially in the commissioning and learning phase, there is no intelligent person in the world. To do two things to learn and change, in the middle of the two things, the development process is actually relatively simple * Always remember: the code is to see, but the computer is running, the computer is executing the program Not afraid, and people are very tired when they look at the code, good coding habits, at least to ensure that they can read the code you wrote before you can understand the code * Try to make your code easily by others, When you write code, think that you will be in two months later, you should be * Don't tolerate your duplicate mistakes and write duplicate code * Know how to do code more important * Try not to do many people have done Things * Learn to respect the achievements of others, unless you don't have to decide to fully replace the previous system * Cherish your time and work results, try to share your own development results * Avoid assumptions, think more about extreme situations and cause errors Sex, effort to reduce low-level mistakes * Don't believe that at least don't believe in the test results of yourself * know how to adhere to your own development ideas, and know how to understand and absorb someone else's thoughts * Society is consistent with others, but you can't give up your own Developing Features * Know the people around you, whether it is the development capability or the development experience * knows how to analyze the importance of the software structure, analyze the structure of the code before analyzing the code * Summary, regularly summarize the knowledge I have learned. Look at the time of the previous time for various reasons, the time is wary, the scheme is planned, try not to think that the task is done by extending your working hours * Learn to correctly estimate your ability and working hours, this is what I think some is more suitable for me. In your own, it is not necessarily suitable for everyone: * Take more magazines, you can see the reference book you have seen before, you are likely to have some details you haven't notified before * Don't be too early To do some things that have nothing to do, because the golden period of learning is very short * Learn to analyze others' systems, see the advanced side of the system developed by others. Here, the development idea of others, the structure used in the realization * often feels that you will be eliminated, often complain about your own, you don't worry, what you are missing, what you don't like to do, such as writing documents * There is courage to rewrite the system you develop, but when you react, you should take the previous different work equation and methods, otherwise it will not be necessary * will simplify the problem rather than complication * will maintenance Part of the problem is transferred to development or when design is designed to solve it. * Sometimes you can ask yourself: I don't do it. * Adhere to your weekly development plan, don't easily do it before things Transfer your attention * As much as possible to teach you to others, because you may no longer be responsible for this system * Do not have the end, unless there is no reason, don't leave before your work is completed. * Don't take away your company, you should take a break because you should take the development experience and the understanding of the development rather than the code and product. * If you feel tired, give yourself a false, after all, people are not machine It's very tired to make a programmer, enough, come on!
