Differentiate between programming and coding?

Question

Differentiate between programming and coding?

Answer 1

A Systems Analyst looks at how a company could and should use computer systems within their business. (Okay, I know you did not ask about Systems Analysts.) This can involve looking at poor efficiency in their processes. This may not only be inefficiencies in the way they use computers but may also include inefficiencies within other parts of the processes.



A Programmer looks at the way the computer can best perform the tasks it has to do as part of the company's processes. This can mean devising flow charts and process descriptions.



A Coder takes the flow charts and process definitions and how they are to be performed and translates these into the actual instructions that the computer executes.



Sometimes there can be an overlap between the Systems Analyst and the Programmer, and also between the Programmer and the Coder.



I hope this helps.

Answer 2

Some of these answers are outright hilarious, if not plain disgusting.



Look, the term 'coding' is just slang. For example, I could call myself a "coder" (i.e. a person who writes computer program code), "programmer", or "computer programmer." Even when you put the words into different contexts as some people have done here, you arrive at the same conclusion. Let's put the idiocy into a different context: If you wanted to, you can call the person who puts the jelly in the jelly doughnuts a "jellyist" and then convince other people to adapt that word. Do you see what I'm getting at?



Regarding Santrupt's answer, if you bring those high-tech engineers and college grads to me, I'll prove that they are at best a bunch of MORONS who shouldn't even be allowed near a computer. Actually, at least 98% of "programmers" today are like that. Despite having the internet, these idiots are too stupid & lazy to THINK, and so they just make up a bunch of nonsense.



I'll give you an example of similar stupidity. Have you heard of the term, "virtual machine?" Well, it seems that some years ago, some BRAINLESS IDIOTS decided that they should call interpreted code that. Now, for anyone who actually knows about computers and programming, a "virtual machine" in the programming and hardware contexts entails something completely different. If the brainless idiots would have simply asked the right people, or used the freaking internet, then they would know that we didn't refer to interpreted languages and code as "virtual machines" long ago.



Here's some bonus knowledge for you:

Do you know what the REAL problem is?

For over 25 years now, programming and computer knowledge has degenerated into complete garbage to the point where these chicken-brained "programmers" today don't even know what a computer is. In fact, they don't even know the difference between a good programming job and a bad programming job. In ANY profession or trade, a person like that is CLEARLY incompetent; That's just common sense. The programs, drivers, and kernel code on the computer you're using now takes up way too much memory, CPU cycles, and storage space because the code & design is pure bloated, slow crap...but that's okay. You can just keep spending more time and money on upgrading your programs & computer to compensate for that.



What do I know? Well, I've been programming for over 30 years, I do virtually all my Windows programming in optimized assembly language (a.k.a. machine language programming), I can hack/crack programs, I've programmed computer hardware DIRECTLY (i.e. without idiotic high level language procedures), written optimized machine code for various CPUs, wrote optimized machine code for programs regarding such things as high speed graphics (e.g. 3D graphics code long before 3D video chips entered the scene), and much more. So, at least 1/8th of what I know would put me in the "God Class" of programmers today. Oh, and I'm not bragging. I'm not calling myself a super, spectacular programmer, it's just that modern programmers have absolutely no business being programmers. For example, it took me very little time in the 80's to see that Object Oriented Programming is complete stupidity and the author of such stupidity is obviously a complete idiot. Modern programmers? As I've already mentioned, they can't evaluate anything because they don't know anything, so they just go with whatever they learned from some other IDIOT, who learned from another idiot, and so on.

Answer 3

It could be that my idea of coder is wrong. I've heard the following analogy:

A programmer is an inventor and a coder is an assembly line worker. A programmer creates things, a coder follows instructions and assembles things.

As Software Engineering becomes commodified, there is less demand for skilled programmers and more demand for coders. Coders are cheap, Programmers are expensive.

Some "Hi-Tech" Engineers or college grads will now pop up and say 'Coders & Programmers are same' but they are NOT!



Programmers develop logics, deeply analyse a problem and solve it using math principles.



Coders are the people who translate logics into real code.



Coders are more language oriented people. If someone says "He's a coder". It simply means he is strongly familiar with ABC language.

Programmers are the people who use blackboards, paper, sketch apps to draw or write substantial logic and figure out how to execute their imagination.



But in today's world, there is a necessity of people with both qualities (Coding & Programming) i.e. A person should be capable of developing logic and should also know how to implement that logic in computer in the form of codes.

Coding

On to coding. I don’t like this term personally, but sometimes I am a coder too – it’s part of the job – When I’m a coder I’m like this guy:



So a coder is someone who codes from one language to another. It can be from English to Morse code, or from English to Java code. When you are coding, you are translating requirements into a language the environment your application will run in will eventually understand (server, PC, iPhone, browser, etc.), and this is where the term “code monkey” comes in and why I dislike the term coding. Sometimes you got to do what you got to do and just crank out code.

Programming



To program any machine or application requires you provide it with a set of instructions to run. Be it your fancy coffee machine that is programmed to have coffee ready by 7:15am. It can be the radio in your car i.e. you program your favourite channels into it. Or it can be set of instructions telling your browser how bounce a ball GIF around on the page.

So what does this all mean? It means they’re all the same – sorry there is no big bang explanation here. At the end whether you are scripting, coding or programming, you are providing some environment like a PC, robot, or browser, a set of instructions on what tasks it needs to perform. Whether the language you do this is high level or low level has nothing to do with it. Whether it ends in “script” or ends in “++” has nothing to do with it. Whether it runs on your browser or on a mainframe has nothing to do with it. Whether it is intended to be sold to millions or just used by you has nothing to do with it.

Answer 4

programming and coding is same thing because programmer is responsible for coding...

Answer 5

Some people might consider these to mean different things but in general they are the same thing.

Answer 6

They really mean the same thing, like synonyms.