Software developer's hot (reproduced)

Software developer's hot

Below these words is not my original, I occasionally found in the Internet, I really fortunate to see these, I really hope you can be inspired by that article.

Author: IBM middleware company CTO Yuan HONGGANG

Software unwittingly done has been done for 10 years, the joy of success, but also the pain of failure, but that he is not the master, and in my mind, because the real experts are compared with the goal too far. The world has not become the master of the shortcut, but some of the basic principles can be followed.

A solid foundation. Data structure, discrete mathematics, compiler theory, which are the basis of all computer science, if they do not know, it is difficult to write high-level procedures. According to my observation, learning computer professional than those of other professionals to write better quality software. All procedures will be written, but when you wrote that to some extent it is very difficult to further increase the time, we should think about is not to come back to learn these basic theory. Do not go to the beginning of OOP, even if you can master OOP, encountered some of the basic algorithm may also helpless when.
Rich imagination. Do not rigidly adhere to a fixed way of thinking, the problems encountered some time to think of a solution, and others, never try the method. Rich imagination is built on the wealth of knowledge on the basis of, in addition to computers, more numerous other disciplines, such as astronomy, physics, mathematics, and so on. Also, see more science fiction film is a good way.
The simplest is the best. This is perhaps all follow a scientific criteria, the quality can be such a complex exchange of Einstein's theory in the eyes is a simple but are not longer a simple equation: E = mc2. Simple method can be easily understood and more easily achieved, it would be easier maintenance. When they encounter problems, we should consider making the simplest programmes, not only simple solution to meet the complex requirements to consider options.
Most do not. When you encounter obstacles, may temporarily away from the computer, look at the scenery outside the window and listen to light music, and friends chat. When I encountered problems will be the time to play games, and that is very violent fighting game, when the game is responsible for that part of the brain cells when stimulated extreme responsible for the programming part of the brain cells has been fully rest . When the work of the re-start, I will find that even those problems can be solved now.
The answer to the thirst for. Science history of the development of human beings is a desire for the process to get an answer, even if the answer can only be a small part also deserves us to pay. If you firm conviction, we must find the answer to the question, you will have energy to explore, even if not the final answer, in the process, you will learn a lot of things.
More exchanges with others. I visit there must be three divisions, and perhaps others in a casual conversation, we can Pengchu the spark of inspiration. More on the Internet to see if other people's views on the same issue, will give you a source of inspiration.
Good programming style. Pay attention to develop good habits, code indented scheduling, variable naming rules should always consistent. We all know how to get rid of the code wrong, but often overlooked on the Notes of the debugging. Notes procedures is an important component of, it can make your code more easily understood, and if the code has been clearly expressed in your thinking, no need for the Notes, if the Notes and code inconsistencies, it even worse.
Toughness and perseverance. This may be a "master" and the general programmer biggest difference. A good programming is 99 weat and a î˜• ffee. Master who is not gifted, they are in countless days and nights of temper them. Success can bring us immense joy, but the process is extremely boring. You may wish to be a test, find a 10,000-within a few tables, copied them all down, and then check three times, and if we can complete the work without interruption, you meet this one.
To peer-point proposal:
(1) proficiency in a programming tool, not what want to learn what not grasp.
(2) do not seek quick results, which often end up in failure.
(3) Code to regulate style, strict speed.
(4) to strengthen self-management, self-daily summary of their own error rate and fee rate.
(5) happy to open their own results, or will soon be obsolete.