Do you want to know if someone is a good or bad programmer, here is the link to the signs of bad programmer:
1. Inability to reason about code
2. Poor understanding of the language's programming model
3. Deficient research skills / Chronically poor knowledge of the platform's features
4. Inability to comprehend pointers
5. Difficulty seeing through recursion
What do you think about these things, any more signs of bad programmer which you know? Thanks
AdamSpeight2008, on 20 October 2011 - 03:36 PM, said:
I'll say it before the rest of you. You program in Visual Basic?
I would say that programming in VB is not so much a sign of a bad programmer in itself, however, the unwillingness to move on from VB definitely is. I personally know people who wish to be game programmers (professionally) but refuse to move beyond Visual Basic, which I'm sorry to say, is naive at best.
i think alot of those "bad programer" signs are more indicative of people learning to program or learning a new language. for instance, Java programers can be very good programers but doing the same thing in C++ will produce code that would make a more seasoned C++ programer rip their head off. that still isn't to say that the Java programer didn't understand what they where doing they just didn't know what the right way to do it was. that is going to happen with any language you learn; your first attempts will be feeble and horribly bad.
that being said, if these symptoms persist passed a normal learning period you have a bad programer.
read into that a bit, i like the "Signs that you shouldn't be a programmer" part
This post has been edited by ishkabible: 22 October 2011 - 11:18 AM