The Difference Between Programmers and Coders (2013)
1–10 of 41 posts
Re: The Difference Between Programmers and Coders (2013)
#2Potato - Potahto.
Re: The Difference Between Programmers and Coders (2013)
#3It's from the same side of the argument as the "Software Engineer is not really an Engineer" phrase.
Re: The Difference Between Programmers and Coders (2013)
#4I think it is important to distinguish between the two.
It is possible to program a computer without coding. Currently, the tools to do this are very domain specific.
I think, in the future, there will be domain agnostic development tools that will let people program software without the need to write code.
Re: The Difference Between Programmers and Coders (2013)
#5I think it is important to distinguish between the two. It is possible to program a computer without coding. Currently, the tools to do this are very domain specific. I think, in the future, there will be domain agnostic development tools that will let people program software without the need to write code.
Why do you think that it's important to distinguish between the two? The fact that it sometimes possible to program a computer without coding does not relay the "importance" of distinguishing, since it's not done on a regular basis and usually is called "configuring", or "defining workflow" but not "programming".
Re: The Difference Between Programmers and Coders (2013)
#6Oh, come on.) btw, the first chapter of The Programmers Stone explained almost everything about two decades(?) ago.
All this could be summarized in one sentence: Programmer is a writer, like Orhan Pamuk, coder is a translator from Turkish.
Or, according to the classic - programmers are "mappers", they are inveting abstractions. Coders are "packers", they are writing piles of Java classes for a paycheck.
Even simpler. Coders are Georges. (Those who have seen SICP lectures would understand instantly).
Update: my two cents to what it is to be a writer.
Look, there are a standard qwerty keyboard in front of you. All required symbols (letters and digits) are here. You know the rules how to compose them into words of English, and how to chain words info sentences. So, go ahead, open a notepad, or even Emacs, and write, say, 1984. It will be much better than any silly startup, you don't have "to Java", you need no AWS and Docker, you don't have to hide the fact that you cannot grasp Design Patters, etc.
All you need is in front of you, all the knowledge is available since secondary school. You could even apply some agile practices.
It also could be that you are esthetically sophisticated person, so you may would like to use a fountain pen and paper, or a pencil and a notebook - just go ahead. We are not asking about poetry or, god forbid, classic music composition, which is even closer to what programming is.
Re: The Difference Between Programmers and Coders (2013)
#7I believe the author merged the responsibilities of a "programmer" with an "Technical architect". To become a good programmer, all you need to do is enjoy reading books, enjoy coding, and work at a moderately sized company.
An architect is different. You have to understand the picture as a whole. You have to understand that one stupid decision can affect the entire product or company's future.
Hurrying to implement excellent code (as a programmer) won't could cost the company many weeks or months or effort to redo.
Re: The Difference Between Programmers and Coders (2013)
#8The difference is a matter of arbitrary semantics. The quote in the beginning is nothing more than a setup of an argument from authority (http://en.wikipedia.org/wiki/Argument_from_authority).
The only takeaway of value is that, yes, there can be a functional difference between designing logic and implementing it. This in no way means you can only do one or the other, or that any specific job or title dictates that you'll do one or the other.
This might as well have been titled, "The difference between a senior developer and a junior one."
Re: The Difference Between Programmers and Coders (2013)
#9I would consider most of the points as the difference between a senior "Programmer" and a junior "Programmer" rather than "Coder".
Re: The Difference Between Programmers and Coders (2013)
#10I believe the author merged the responsibilities of a "programmer" with an "Technical architect". To become a good programmer, all you need to do is enjoy reading books, enjoy coding, and work at a moderately sized company. An architect is different. You have to understand the picture as a whole. You have to understand that one stupid decision can affect the entire product or company's future. Hurrying to implement e…
I like this distinction, because to me almost every coder is a programmer, but there are still more theoretical positions such as technical architects who don't necessarily even touch the code.