Coder Vs Programmer

Originally Posted by hirak1984

this is an age old debate,who is more effective==>a coder or a programmer...
the definitions of these two terms are also are overloaded multiple times.
lets start with these in TSDN.
when should we be called a programmer and when a coder?
and what do you think is the difference between the terms?

Originally Posted by drhowarddrfine

I agree they are the same thing. When talking about creating web pages, though, I tend to call people who "markup" pages with html/css, 'coders', to differentiate them from those who use programming languages.

Originally Posted by DeMan

I think coders are starting to disappear. I think the essential difference, is that a coder is someone who simply writes code (and there was a time when that was more likely a hobbyist than a formally qualified "engineer/developer/etc").

A programmer, on the otherhand, is someone who is more closely involved with the whole SDLC, and is probably becoming increasingly closer to the role of an analyst.
That is, a programmer works on a project to some result, while a coder just implements solutions leaving much of the planning/documentation to someone else.

Originally Posted by DeMan

I think coders are starting to disappear. I think the essential difference, is that a coder is someone who simply writes code (and there was a time when that was more likely a hobbyist than a formally qualified "engineer/developer/etc").

A programmer, on the otherhand, is someone who is more closely involved with the whole SDLC, and is probably becoming increasingly closer to the role of an analyst.
That is, a programmer works on a project to some result, while a coder just implements solutions leaving much of the planning/documentation to someone else.

Originally Posted by r035198x

I disagree to some extent. I just take them literally. Coders write code programmers write programs. You cannot write a program without writing code. So all programmers are coders. When you write code you are putting together a program so coders are also programmers.

Originally Posted by r035198x

I disagree to some extent. I just take them literally. Coders write code programmers write programs. You cannot write a program without writing code. So all programmers are coders. When you write code you are putting together a program so coders are also programmers.

Originally Posted by Frinavale

In this case why do "software engineers" exist?

Originally Posted by Frinavale

Is a software engineer a programmer?

I've noticed that there is a lot documentation involved with engineering/programing a system. I've been told that software engineers don't even touch code because they are too busy creating/modifying the documents for the system's design.

In practice, a programmer plans the system and implements it. Thus, a programmer is also a coder.

In the university setting, we are told that an engineer plans the system and hands it off to someone else to implement it. Thus the engineer programs the system and a coder implements it.

Its way too hard to ignore the fact that in the real world a programmer plans and implements systems.

So, are programmers also software engineers?
Programmers certainly must design and analyze (engineer) the system they wish to implement before they start coding.

In this case why do "software engineers" exist?

Originally Posted by Frinavale

In this case why do "software engineers" exist?

Originally Posted by DeMan

When I was at school, and was deciding study options/career paths, neither of these titles were very common, rather "Programmer" and "Systems Analyst" were the catchy terms used. I always assumed that a "Programmer" was a "code-Monkey" and a "Systems Analyst" was his boss. These terms are still around, sure, but I'm not sure they still describe exactly the same role they used to. Systems Analysts these days are not necesarily IT qualified

Originally Posted by sicarie

I have a friend who is a 'Systems Analyst' and (though he is entry-level) he handles creating documentation and requirements, as well as determining those requirements with the customer (NOT an easy thing to do - working with both the customers and the programmers to find the balance between feature and feasability). I'm not entirely sure what those above him do...

Originally Posted by DeMan

I sometimes wonder whether this is a matter of where you are in the world. I work for an American Company, and my title is "Software Engineer". The same role in a local (Australian) company would probably be "Software Developer".
When I was at school, and was deciding study options/career paths, neither of these titles were very common, rather "Programmer" and "Systems Analyst" were the catchy terms used. I always assumed that a "Programmer" was a "code-Monkey" and a "Systems Analyst" was his boss. These terms are still around, sure, but I'm not sure they still describe exactly the same role they used to. Systems Analysts these days are not necesarily IT qualified (and infact analyse Systems which aren't necessarily electric, and I think {though I've been wrong once or twice before} that this is sort of where Business Analysts came from....but I digress)

Originally Posted by r035198x

My job title is analyst programmer. I spend 14 hours a day writing code six days a week.

Originally Posted by acoder

You are joking surely...

Originally Posted by DeMan

.....And stil manages 18 posts a day!!!!!! (within those 8 months!!!!!!!!!!)

Originally Posted by hirak1984

There is a popular T-shirt quote here...
I AM A PROGRAMMOR,
I AM A PROGRAMER,
I AM A PROGRAMMAR
.
.
.
I WRITE CODES

funny huh!

Originally Posted by mmccarthy

I like it - have to get one made up.

Originally Posted by r035198x

Sorry Mary. That's for programers only.

Originally Posted by hirak1984

can try to write one specifically for mary

Originally Posted by r035198x

No need for that. She actually is .......(my computer just froze)

Originally Posted by hirak1984

need some explanation.....

Originally Posted by mmccarthy

r0 likes to challenge me on occasion. They do say sarcasm is the lowest form of wit. LOL

Sorry Hirak

You got caught up in an ongoing joke between myself and r0.

Mary

Originally Posted by r035198x

My job title is analyst programmer. I spend 14 hours a day writing code six days a week.

Originally Posted by hirak1984

hey that sounds sentimental mary

Originally Posted by hirak1984

need some explanation.....

Originally Posted by Frinavale

Since you're writing code so much, do you actually do any planning at all?

Originally Posted by hirak1984

hey that sounds sentimental mary

Originally Posted by r035198x

Oh dear. You've got a lot of catching up to do.

http://www.thescripts.com/forum/thread576938.html

Originally Posted by mmccarthy

LOL

That's not even the worst of it.

Have we hijacked this thread yet?

Originally Posted by hirak1984

the answer probably is yes,lol

just joking,didnt mean it.

Originally Posted by mmccarthy

Since it was your thread in the first place you can't hijack it so it's all r0's fault. I'm totally innocent of course.

Originally Posted by sicarie

as well as determining those requirements with the customer (NOT an easy thing to do - working with both the customers and the programmers to find the balance between feature and feasability)

Originally Posted by AricC

This is the part I dislike. I've noticed customers don't seem to do their research on what they really need/want.

Originally Posted by rhbt63

Hi
i used to program machine language ie 165,35,174,01,220...... , so does this mean i was initially a coder to start with and was the task was complete and a program was formed i became a programmer.

things are never as stright forward as you think.



l8r


regards


rab

Originally Posted by nmsreddi

Hello

The job of a programmer is coding i dont think they are two diierent

Originally Posted by Motoma

I would assert that a Coding is a subset of Programming, and Programming is a subset of Software Engineering.

Originally Posted by hirak1984

well that and what is the super set of a software engineer?please

Originally Posted by DeMan

And software Engineering is a subset of Engineering

Originally Posted by Motoma

Or perhaps System Engineering.