A Good Programmer
A Good Programmer
Most of programmers nowadays do the needed jobs and fulfill the requirements. But there is still a catch as two different programs could solve the same problem. How could one know which program is better than the other? By analyzing the efficiency of the program, the resources it utilizes, the time it requires to process and so on and so forth. Well analyzing the program sounds to be a known solution. How to analyze a better programmer?
One solution which would be going back and analyzing the code and then pin point the best programmer by the best program he/she has submitted. This is actually choosing the best program. What interests me the most is how to get a good Programmer
The Other solution which I believe best describes a better programmer is analyzing him/her on the following
1. The amount of time he/she spends writing the code:
The amount of time a programmer gives is a key aspect in judging him/her on how long he/she could work. The world is not a slow track any more. It’s all about how fast you can submit your idea before it actually comes to another person’s mind. Time is everything in programming and the faster a programmer can actually program is certainly an advantage.
2. How he/she interprets the problem:
Understanding a problem is said to be half of the solution. A programmer should definitely be a good problem solver and most importantly know what the output should actually be.
3. How the programmer conquers the problem:
Solving the problem is not all what matters. It’s how you solved it, which method the programmer chooses to use. The solution does play a greater role in what the programmer presents, but that’s actually judging a book by its cover, going beneath what meets the eye is judging what one can jugde a programmer.
4. How the programmer is confident on the code he/she wrote:
Writing a code which a programmer is not confident with: is an error already. Being able to back up your code is a characteristic of a good programmer. Knowing if not all but most of the programmers can hardly do much with your code is great feeling of relaxation and comfort. Falling in love with your code is not being confident
5. How the programmer is confident on the solution he/she choose for the problem:
Knowing that a solution can sometimes be an extra problem. Having a solution in mind but not being able to tackle it is the worst thing that can happen to a programmer. A good programmer chooses a solution and is confident on how he/she is going to tackle it to produce the end results.
6. Requirements are not all you need to look at:
An extra cheese on the surface would actually taste better. What I am trying to say, the Requirements are to be considered but that’s not all, a good programmer goes beneath the requirements and meets all the validation in order that the probability of a mistake to occur is very close to none.
7. Keeping room for future improvements:
Having a space for extra improvements is always a good thing. Having the code tight and reasonable is actually providing room for updates. Some applications are re-done from the beginning just because it would actually cost and require more time to understand the current one running. Your code should be an “Open book”.
8. The Environment a programmer chooses:
Although the environment might not play an important role to distinguish the better programmer, choosing a good environment on knowing what you need to do would certainly help you gain time in your work, organize your work in an appropriate way. Although a problem can be solved in different enviroments, there is always a better one and a programmer should be farmiliar with that.
9. Keeping yourself update:
Being able to read and learn new programming languages is a key to successful programming. Having a wider knowledge is good for everything. Keeping yourself updated actually puts you in the first line in any discussion that occurs in your area.
10 Contribution to the community
A good programmer is one who is willing to contribute his/her program for the good. Open source helps programmer re-use and learn.
Being a programmer and being a good programmer is different but it’s not like cats and dogs, one can always improve. You got the tips all you need it to follow them.
Related posts:
One comment
Leave a Reply
Erm…very worthy topic, but your treatment of it is uneven. Your statements don’t really seem to flow together under each topic.
But anyway, I agree with you mostly here–Judge a programmer by how he approaches, captures, and conquers problems, with an eye towards maintainability, clarity, and extensibility. That’s the mark of a craftsman.
If you haven’t read it, I recommend “Pragmatic Programmer” by Hunt and Thomas to reinforce some of the things you’re saying here.
Cheers!