What is the difference between Programmer and Good Programmer ?

Question

Post reply

What is the difference between Programmer and Good Programmer ?

karthik M

One Orange Chip

Points: 29139
More actions
November 20, 2007 at 6:36 am

#179390

Inputs are welcome !
karthik

Viewing 15 posts - 1 through 15 (of 34 total)

You must be logged in to reply to this topic. Login to reply

karthik M One Orange Chip Points: 29139 More actions · Answer 1

karthik M

One Orange Chip

Points: 29139

November 21, 2007 at 5:59 am

#753059

Any idea ?

karthik

Andrew Stanton Ten Centuries Points: 1115 More actions · Answer 2

Seriously, if you dont know, then you should not be a Senior Software Engineer.

Loner SSC-Insane Points: 21279 More actions · Answer 3

A programmer writes the programs.

A good programmer writes program for users, the program is easy to understand, always wants to advance his/her technical skills. 😉

my 2 cents

karthik M One Orange Chip Points: 29139 More actions · Answer 4

Andrew, I dont think so. Because i am not asking what is mean by programming ? i am asking the difference between programmer and good programmer.

I know the basic difference between programmer and good programmer;).But some experts definitely should have different thought about my question.Thats why i posted this question.

Because i have read an article 'who can program' written by Steve Jones - Editor of this site. Really i have learnt so many things from the article. Like that if any experts share their idea then it would be very useful for me.

karthik

Ewan Hampson SSCrazy Points: 2780 More actions · Answer 5

There are so many different aspects you could choose - quality of design, testing standards, clarity... - which will get different weighting according to the requirements and business environment.

On the coding side of my job I'm just a programmer, with no pretentions to anything more than trying to do it well. But when I have to revisit and revise some of my own code for an RFC, and find the change is easy to incorporate and the new or revised class (or the new subclass) easy to design, implement and integrate, then I think This is the sort of code a Good programmer produces all the time without thinking about it. It's just that I have to think about it, and notice those occasions when I manage to do it.

I suppose this means "I know it when I see it", and that I rate maintainability highly.

karthik M One Orange Chip Points: 29139 More actions · Answer 6

I suppose this means "I know it when I see it", and that I rate maintainability highly.

--------------------------------------------------------------------------------

I think you didn't understand my question;). Moreover you are newbie to this site. So i don't want to blame you because you dont have a chance to know about me:cool:.Well, If i dont know,i would say, no i don't know. So i dont have the habit to say ' I know it when i see it' ,Understood.

Whistling:. Just go through my post once again:I think you didn't read my post.I have mentioned

----------------------------------------------------------------------

Because i have read an article 'who can program' written by Steve Jones - Editor of this site. Really i have learnt so many things from the article. Like that if any experts share their idea then it would be very useful for me.

-----------------------------------------------------------------------

karthik

Ewan Hampson SSCrazy Points: 2780 More actions · Answer 7

Assuming you've read Janet Wong's "What makes a good programmer" article that picked up from Steve's editorial, what more do you want anyone to say?

I am far from a newbie to the site. I rarely say anything because most people here are better than I am with SQL Server, which is just one part of my job. I thought what I said was a reasonable small contribution to the possible responses, but then I'm not very good at forums. Or people. But perhaps you are not aware that your reply reads like a put-down to an infant, though I don't suppose that was the intention.

Jeff Moden SSC Guru Points: 1004406 More actions · Answer 8

i am asking the difference between programmer and good programmer.

Knowledge of all things...

A good programmer will have an extreme knowledge of the language (s)he's writing in, understand/how to use external resources/systems/data, have the ability to document so others "get it", the ability to solve problems (sometimes using a tool not built to solve such a problem), the ability to correctly interpret requirements, the ability to use the internet/books to find solutions instead of relying on forums to answer generic questions, and the ability to talk with users/managers to find out what they really need and not just what they want.

A great programmer knows how to do all of that, continues to learn new things every day, is not afraid to experiment and try new things, knows that not all new things are good things, is willing to share their knowledge (mentorship), is usually not concerned with titles under their name, and does so without being arrogant. 😉

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Loner SSC-Insane Points: 21279 More actions · Answer 9

A great programmer needs a great manager. In many cases, I saw many potential good programmers staying at the same position, doing what the manager told them to do, they did not dare to do anything else because they were afraid to lose their jobs. The worst of all, some of the managers were technical themselves, they got promoted to become the managers because of their seniority, it did not mean they were good programmers nor good managers. Those people kill great programmers.

I just listened to the radio the other day, the host was talking some company complained they could not hire good employees. Just liked many IT departments complained they could not hire good DBA or SQL developers. The problem was the managers interviewed those candidates, once they saw great DBA or SQL developers, they might feel a potential threat to themselves, so they said those people were over qualified or not a team player. In my last job, my manager said he rather hired a programmer following direction instead of a great programmer who keeps trying new techniques. This way he could keep the whole team under his control.

My advice - Don't be a great programmer !!!!!!!:sick::exclamationmark:

Jeff Moden SSC Guru Points: 1004406 More actions · Answer 10

Heh... forgot to mention that great programmers also know when and how to buck the system. Otherwise, the become unemployed programmers. 😉

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

karthik M One Orange Chip Points: 29139 More actions · Answer 11

karthik M

One Orange Chip

Points: 29139

November 22, 2007 at 11:12 pm

#753519

Jeff and Loner,

Thanks for your explanations.

karthik

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 12

I would say that a good/great programmer is never content with 'good enough' but always wants to do the best job possible.

A good/great programer is always learning. Reading technical books/blogs/white papers. Participating in discussions, attending (speaking at) user group meetings or conferences. Investigating new technologies.

These days, I won't recommend a programmer/DBA for employment where I work, unless they can answer the question "What technical books or blogs are ou reading at the moment"

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Jeff Moden SSC Guru Points: 1004406 More actions · Answer 13

Moreover you are newbie to this site.

Ummmm... that's a bit arrogant on your part... you're a bit of a newbie yourself and, so far, I've not seen you answer a whole lot of questions.

And, yes, I "know it when I see it", as well. And, I've seen enough. :sick:

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

matt stockham SSCrazy Eights Points: 9942 More actions · Answer 14

I just listened to the radio the other day, the host was talking some company complained they could not hire good employees. Just liked many IT departments complained they could not hire good DBA or SQL developers. The problem was the managers interviewed those candidates, once they saw great DBA or SQL developers, they might feel a potential threat to themselves, so they said those people were over qualified or not a team player. In my last job, my manager said he rather hired a programmer following direction instead of a great programmer who keeps trying new techniques. This way he could keep the whole team under his control.

I have to disagree ... if a programmer tries new techniques outside the framework in use by the rest of the team, it isn't necessarily a good thing. Certainly it might benefit the company as a whole, but it could also result in code that nobody else knows how to maintain. The ability to experiment certainly does not define a good programmer.

Ultimately, it comes down to individual circumstances - I don't think there is any right answer to the original question.