Over the years I have had many programmers work together, some of them very badly, while others seem mediocre. Not long ago because of some technical and highly skilled programmers work feeling very happy, I spent some time considering I admire what they do? What makes a good programmer so good, bad programmers so bad? In short, what is the reason the achievements of an outstanding programmers to it?
In my experience, to be a good programmer does not have any relationship with age, education level, and how much money you. The key is that you practice more deeply, is that what you think. I noticed that I admire programmers have some similar habits. Knowledge is not the language of their choice, not a deep understanding of data structures and algorithms, not even years of work experience. But the way they communicate, manage their own way, as well as their superb technical level programming speech mode.
Of course, to become a good programmer should have more character, I can not rely solely on the presence or absence (or lack of) these qualities to judge a programmer. But I know that when I saw it, when I saw a programmer with these qualities when I think, "This man really knows what they are doing."
They do research
Or "think twice", or "Google it."
No matter how you call it, most of the programming problems that may be encountered has been solved in some form, Ecclesiastes has long been recorded in the world have never had anything new. Good programmers know until the problem through GitHub library, Internet blog, or do research in the form of experienced programmers exchanges.
I've seen even a good programmer can quickly find a solution, but I worked with and the bad programmers never resort to others, the result of a lot of duplication of work or the wrong solution to the problem, unfortunately, then they will eventually pay the price for his mistakes.
They read the error message (and to act in accordance with them)
This includes parsing stack path information. Yes, this is a very unfortunate thing. But if you do not want to do this, how can we know where wrong? I know that efficient programmer is not afraid to go into the problem. Inefficient programmer saw a mistake, but is not willing to even read these error messages. (It sounds ridiculous, but you'll be surprised I met its frequency)
More particularly, good programmers found the problem immediately resolved it. Read the error message to them is just the beginning, they are eager to get to the bottom of the problem and find out the root of the problem. They do not like to shirk responsibility, but willing to find solutions to the problem, the problem in their stop here.
They went to see the source code
Documentation, testing, team, these will lie. Although not intentional, but if you want to know exactly how things are going, you have to personally look at the source code.
If it's not what you do best language, you do not be afraid. If you are a Ruby programmer, you suspect there is a bug in the C language library in Ruby, crack open look. Yes, you may not get the source code, but who knows? You just might, you have a better chance, than you simply do not try to right.
Unfortunately, if you are in a closed environment, source code, it becomes very difficult, but the truth is unchanging. Lousy programmers have not the slightest interest in viewing the source code, the result of their troubled time, much longer than willing to look at the source code of the time.
They just do it
Good programmers tend to take the initiative to do it. Their hearts had uncontrollable impulse, when they identify problems or discover new demands they will immediately implement solutions, sometimes too early and sometimes too radical. But they question instinctive reaction is positive to solve the problem.
This sometimes very annoyed, but their enthusiasm is an important part of what they do. Some people may delay or avoid the problem that they can wait for the problem to disappear, but good programmers start to solve it. In short (or obvious), if you see someone happily find the problem and resolve, it is likely your hands there was a good programmer.
They avoid crisis
This is usually characteristic of bad programmers: they easily jump to another man-made crises from a man-made crises, in the absence of a real understanding of the problem to the next question. They put the blame on the wrong program, and then spend a lot of time debugging code that has been running well. They let emotions take the initiative, trust their instincts, rather than a careful critical analysis.
If you rush to solve a problem, and even view every problem as a disaster that shocked the world. You are likely to make a mistake or do not solve the underlying problems. Good programmers spend time to understand what went wrong, even if disaster comes; but more importantly, such an important problem to be solved they treat common problems, so they are more accurately solve more problems, and doing so does not increase the tension in the team.
They are good at communication
After all, programming is a form of communication. Write code and write prose, as can succinctly express your ideas is very important. I have found that e-mail can write simple, elegant status report, or even just a valid memo programmers will also be a good programmer.
It can be used in writing the code as well as English. Write a line of code using the function parentheses, brackets and single letters, of course, possible, but if no one understands it, what is it. Good programmers spend their time in a variety of channels to communicate their ideas.
They passionate
I think this may be the most important aspect of good programmer (and perhaps this also applies to other areas in the field of computer science in addition to)
If you really care about what you do, if you do not regard it as work, as a hobby, interest, or a very attractive thing, then you have an advantage in this area than others. Good programmers constantly programming. Ordinary programmers working eight hours a day, and no amateur project, not interested back to the community. They will not continue to try new methods, but just to see how they are run and dedicated to the programming language.
When I saw a programmer to take advantage of weekend time to do their favorite project involved the creation of a day when they can use the tool, dedicated to new meaningful thing: that time I was sure my eyes is a surprising people. Finally, good programmers, as the way their career is not just money, but also make life somewhat different approach. I think that's the real reason for the achievements of the best programmers. For them, writing code is a way to change the world, but also I respect the reasons for their worship.
