Seven common features of efficient programmers

To be efficientProgramPersonnel, you need to have a certain level of comprehensive quality to enable you to use your skills, experience and knowledge to write effectiveCode. Some developers have certain technical skills, but they will never be efficient programmers because they lack the other qualities they need. This article will show seven traits that must be possessed by a great programmer.

1. actively learn new technical and non-technical knowledge

A bad programmer can start learning knowledge only when it cannot. Good programmers will take the initiative to learn new technical knowledge.Great programmers will not only learn new technical knowledge on their own, but also learn non-technical knowledge, and have an open mind for all kinds of knowledge sources.But not as self-built as some people do.

Specifically, a bad programmer starts to learn Xam only when he participates in a WPF project. A good programmer learns Xam a year ago because he feels that it is very interesting; the great programmer also read the design guide, availability theory, or other similar learning courses of the WPF application, so that he can create a unique UI.

2. Be pragmatic and not doggy

Strict adherence to unwritten "programming rules" is often a luxury that few developers can afford. If your specification is not written by top developers or under the guidance of top developers, I can assure you that you may not be able to afford it.

I often come across some programmers who cannot or refuse to do a task because the practice of completing this task is generally not accepted by best practices. Business Requirements are rarely restricted by the technologies used to implement the requirements. No one will say, "We should not write this requirement into the specification, because we need to implement this requirement, programmers have to write a very bad piece of code."

On the end day, the programmer's task was to generate an effective application, not to require technical perfection. I am not defending the spam code. What I want to say is that sometimes you write some code that will never be used as an example to show others the correct way to do things.If there is only one way to write this code, it is not a bad code-but make sure you have exhausted all other possible solutions.

3. Learn how to find answers through research

Finding the answer through research is not just as simple as typing a few keywords in the search engine, nor to stack overflow or msdn
For websites such as forums, send a question post. I have encountered a problem that cannot be found in the search engine, and then I stack overflow or msdn
None of the questions posted in forums have a decent answer, but I still solved the problem that I encountered so that my work could continue.I am not a magician-I just know how to find the answer and how to find the root cause of the problem.

There are many situational questions. If you rely on search engines or forums, you will waste a lot of time on various links and cannot get the real answer.We need to learn how to analyze the root cause and learn the knowledge of the underlying system to find other clues and solutions, we also need to learn how to thoroughly analyze the problem after we have a global understanding.

4. Have passion

If you do not like this job, you cannot become the top professional in this industry. However, some programmers who only regard programming as a common job are also good, but if your three views are the same, you are reluctant to do everything that leads you to success.

This opinion will make many people unhappy, because they will think this is a kind of personal insult. "I am a good programmer, but I still have other important things to do. I cannot make my work a perfect place in my life.
Department ." I fully understand; I also have other more important things. Although I hate to say so, when we are enthusiastic about my work, I am willing (though not eager) to abandon other more important things to finish first.
Into the work at hand. It is a fact that you cannot become a master if you are unwilling to invest in your work.

You must be passionate about your work, the technology you use, your boss, your project, and so on.Me
I have witnessed some very good and even Great programmers who are mediocre, just because some conditions are not suitable. For example, they do not like the projects at hand, or the technologies used in the projects make them hate. I used to be
I have shared things with such a programmer. From any point of view, I do not like such a programmer. If you find this is the case, you need to solve the problem immediately.
It can help you adjust your mood by exploring interesting aspects of your work or projects.

5. Leave yourself out of the door

Many developers are very conceited. It only means that you are a good person than others who are smarter, more knowledgeable, or more experienced. You must respect others and truly listen to and Test
Consider others' opinions, seek help from them when they need them, and do not underestimate others. You should also be more concerned about winning or losing your team, rather than simply concerned about your honors and gains at work.

6. Be entrepreneurial

The best developers will not be idle. For them, the success of products not only means that their salaries have fallen. Because they are enthusiastic and enthusiastic at work, they work for better development of the project and will go forward.

7. Two measurements, one removal-but no more than three measurements

One of the worst mistakes a developer may make is to drag them into the code without knowing what to do. (When they call this method agile development, the situation is even worse, as if using agile
). When great developers jump into the code, it is because the requirement specification is very similar to some of the practices they have previously implemented. Great programmers are facing new problems
They will think, plan, and study.

The best among developers will not fall into
Paralysis) "trap. They know that they need to be careful with certain things (for example, when it comes to money or personal data). Only these special fields are suitable for what I call "three measurements ". Any more than three
It means you are wasting your time (unless in rare cases, such as nuclear reactors, space vessels, hedge fund accounting systems ).

It is very important to stop the plan at a specific time point, start coding, and then see what adjustments are required for your plan. By the way, this is one of the reasons why I became a fan of agile methods. The best developers I know are willing to give up the plan when the plan is no longer appropriate or when they discover that the plan is defective.

Seven traits of valid tive programmers