Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

Possible Duplicate:
How Can I Know Whether I Am a Good Programmer?

Sometimes I hear someone say "good programmer" once I saw I guy saying that he was going to promote programmers that were good.

My question is: what is the definition of good? I am not asking here how to find good programmers or how to identify one, but just knowing what "goo programmer" in professional sense is.

2nd question: How do I know if I am good or bad programmer?

share|improve this question

marked as duplicate by Aaronaught, Mark Trapp Oct 25 '11 at 0:10

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

A good programmer is the one who writes code I can figure out what its doing. –  Ben Oct 24 '11 at 23:46
What if someone writes a great code that you cannot understand? –  Victor Oct 24 '11 at 23:48
That's a bad programmer. What makes the code 'Great' is the fact that its maintainable. And it cant be maintained if you cant figure out what it's doing. –  Ben Oct 24 '11 at 23:49
@Ben, occasionally you end up in a situation where it is more important to solve a problem than it is for everybody to be able to maintain it. Then you will have to do with just somebody being able to. –  user1249 Oct 25 '11 at 5:51
Please read the programmers.stackexchange.com/faq –  Dynamic Oct 25 '11 at 9:49

1 Answer 1

up vote 3 down vote accepted

A good programmer writes good code at a good pace, and helps others do the same.

Good code solves the correct business problem with few bugs, is relatively easy to understand and is maintainable during the lifetime of the software in question.

A good programmer leaves the code base in a better state at the end of the day than it was at the start – every day.

Bad programmers write code slowly, or with lots of bugs, or which cannot be easily understood or maintained in future. Bad programmers may (frequently do, IMHO) have net negative productivity – a project would be better off without their contribution altogether.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.