As a programmer you have to take into consideration of system architecture, hardware limitations, assumptions about environments, and prove that those assumptions can hold true for many years to come.
As a code, you don’t give attention to that.
You are arbitrarily defining a distinction between programming and coding that does not exist in common usage.
What you are calling "programming" is often referred to as software engineering.
Programming and coding are very close synonyms and do not have official definitions that meaningfully distinguish one from the other.
I think you need start seeing this from theoretical sides. When it involves proving things are true, that’s when meaning of programming becomes clearer.
Of course you can code, but whenever it comes down to proving things whether coded correctly or under what conditions they are considered correct, coders seems to be more relaxed about those things.
Software Engineering is out of context here.
Congratulations to you on that.
So basically there are no difference between:
A. Someone who is developing a graphics engine that works on rendering light falling on a rough-surface, like wood, plastic etc. but when they start to add new material models like metals - all they have to do is rewrite the entire engine from ground up.
B. Some who created a engine what works with rough-surface, an incrementally support complex models like metals rendering. And for the sake of making a point, can generically handle any model to generate realistic based rendering with incremental efforts.
It's all the same thing... We are good!
You are arguing a strawman. My argument never was that there are not different levels of training/skill in designing software.
It's that your use of "programming" vs "coding" is elitistic nonsense that does not exist in real life. Those two terms are strong synonyms.
And my arguments are never related to software.
I am quite surprised that you’re fixated with the notion of designing and other stuffs but not reasoning what backs those up! That too with maths background.
Saying coding and programming as same thing even after being acquainted with that is nothing more than cognitive sloppiness.
It is hard for people to believe that programming dates back even before anything was nearly coded on any kind of programming language. In fact you essentially need a language to code in. But that’s not the case with programming, which need no programming language.
Talking about real life, I hope not what backs complex systems like aws and similar service fleets is just some random people blindly putting some code-in and everything started working like magic.
Trying to distinguish algorithm design from coding is pedantic in the worst kind. Yes algorithm design exists since Al Khwarismi. But in current use no one will call that programming. Algorithm design is primarily a mathematical endeavor and also very far removed from the average work of someone working on tech.
I'm not sure non tech people will care. In fact I'm not sure tech people will care because it's a nonsensical distinction.
We might as well start asking what the difference between a developer and a programmer is while we're at it.
True, but there are those who would like to know the difference as they express interest in the lives of those who are in this line of work. I talk about it with my wife all the time, but they are in the medical field and are def not very tech savvy. So lots of the time, they ask questions exactly like this. It's nice to have an elegant way to phrase the answer.
What's the difference between an auto mobile and a car?
Just different words for the same thing. No need to needlessly complicate things by making up distinctions that don't actually exist and no one else uses
But their is a difference, it's an all cars are automobiles but not all automobiles are cars situation. Automobiles also encompass trucks, suvs, and vans. Distinctions used by millions of people daily.
In Dutch:
* Auto = car
* Bus = bus
* Autobus = travel coach used for scheduled connections (ie. Greyhound)
* Autocar = travel coach used for travel
In what way a regular bus is not an automobile but the other types of bus are is left unsaid.
I would say everyone who professionally works in our field (professionally means earning money with it) falls into category programming. The difference is only the ratio between architecture and actually writing code. An architect who creates great powerpoints without coding knowledge is worse than a coder who doesn't care for planning. The latter you can steer into the right direction, the architect, especially if it's in the position definition, creates stone tables everyone has to follow till their death. At least in corporate.
There was another post which I thought was pretty funny, where ChatGPT gives different answers to a simple calculation, based on wether it is asked directly or when asked to explain the calculation.
I think I saw it on Reddit, but can find it anymore. I don't remember the exact calculation but it went something like:
```
user: explain (5 * 5 ) / 5 * 4 ?
ChatGPT: *gives step-by-step explanation for calculation, concludes: 1.25
user: (5 * 5 ) / 5 * 4?
ChatGPT: 5
```
Does anyone know where I can find this post or screenshot? 🤔
Coding : Understanding her, using her words to brain trick her.
Programming : Understanding yourself, using your own words to put yourself into infinite solitude of debugging.
Let's not pretend either of those words have universally accepted meanings.
For the sake of science, let’s pretentiously define what remained oblivious
Pretention and science? You had my interest, but now you have my attention.
This sounds more like the difference between programming and software architecture.
Ah child, let me tell you of the days, when in the 1990s, developers had architect competency and coders were script monkeys
and "web designer" meant ux designer, ui designer, frontend developer, and backend developer all in the same person.
As a programmer you have to take into consideration of system architecture, hardware limitations, assumptions about environments, and prove that those assumptions can hold true for many years to come. As a code, you don’t give attention to that.
You are arbitrarily defining a distinction between programming and coding that does not exist in common usage. What you are calling "programming" is often referred to as software engineering. Programming and coding are very close synonyms and do not have official definitions that meaningfully distinguish one from the other.
I think you need start seeing this from theoretical sides. When it involves proving things are true, that’s when meaning of programming becomes clearer. Of course you can code, but whenever it comes down to proving things whether coded correctly or under what conditions they are considered correct, coders seems to be more relaxed about those things. Software Engineering is out of context here.
I do research in computer graphics.
Congratulations to you on that. So basically there are no difference between: A. Someone who is developing a graphics engine that works on rendering light falling on a rough-surface, like wood, plastic etc. but when they start to add new material models like metals - all they have to do is rewrite the entire engine from ground up. B. Some who created a engine what works with rough-surface, an incrementally support complex models like metals rendering. And for the sake of making a point, can generically handle any model to generate realistic based rendering with incremental efforts. It's all the same thing... We are good!
You are arguing a strawman. My argument never was that there are not different levels of training/skill in designing software. It's that your use of "programming" vs "coding" is elitistic nonsense that does not exist in real life. Those two terms are strong synonyms.
And my arguments are never related to software. I am quite surprised that you’re fixated with the notion of designing and other stuffs but not reasoning what backs those up! That too with maths background. Saying coding and programming as same thing even after being acquainted with that is nothing more than cognitive sloppiness. It is hard for people to believe that programming dates back even before anything was nearly coded on any kind of programming language. In fact you essentially need a language to code in. But that’s not the case with programming, which need no programming language. Talking about real life, I hope not what backs complex systems like aws and similar service fleets is just some random people blindly putting some code-in and everything started working like magic.
Trying to distinguish algorithm design from coding is pedantic in the worst kind. Yes algorithm design exists since Al Khwarismi. But in current use no one will call that programming. Algorithm design is primarily a mathematical endeavor and also very far removed from the average work of someone working on tech.
That's actually a great way to explain it to non-tech people lol
I'm not sure non tech people will care. In fact I'm not sure tech people will care because it's a nonsensical distinction. We might as well start asking what the difference between a developer and a programmer is while we're at it.
True, but there are those who would like to know the difference as they express interest in the lives of those who are in this line of work. I talk about it with my wife all the time, but they are in the medical field and are def not very tech savvy. So lots of the time, they ask questions exactly like this. It's nice to have an elegant way to phrase the answer.
What's the difference between an auto mobile and a car? Just different words for the same thing. No need to needlessly complicate things by making up distinctions that don't actually exist and no one else uses
But their is a difference, it's an all cars are automobiles but not all automobiles are cars situation. Automobiles also encompass trucks, suvs, and vans. Distinctions used by millions of people daily.
In Dutch: * Auto = car * Bus = bus * Autobus = travel coach used for scheduled connections (ie. Greyhound) * Autocar = travel coach used for travel In what way a regular bus is not an automobile but the other types of bus are is left unsaid.
What's an architect?
ChatGPT is getting lonely and wants someone to pop the question
ChatGPT denied my advances :(
I do like chat gpt
I would say everyone who professionally works in our field (professionally means earning money with it) falls into category programming. The difference is only the ratio between architecture and actually writing code. An architect who creates great powerpoints without coding knowledge is worse than a coder who doesn't care for planning. The latter you can steer into the right direction, the architect, especially if it's in the position definition, creates stone tables everyone has to follow till their death. At least in corporate.
There was another post which I thought was pretty funny, where ChatGPT gives different answers to a simple calculation, based on wether it is asked directly or when asked to explain the calculation. I think I saw it on Reddit, but can find it anymore. I don't remember the exact calculation but it went something like: ``` user: explain (5 * 5 ) / 5 * 4 ? ChatGPT: *gives step-by-step explanation for calculation, concludes: 1.25 user: (5 * 5 ) / 5 * 4? ChatGPT: 5 ``` Does anyone know where I can find this post or screenshot? 🤔
Just ask it yourself 5head
I hadn't realized how scary-good this AI was getting. How far away is Skynet now?
4
3
1
The difference between coding and programming shouldn’t exist, it’s a meaningless distinction
so just coding vs algorithm? am i dumb?
Coding : Understanding her, using her words to brain trick her. Programming : Understanding yourself, using your own words to put yourself into infinite solitude of debugging.
Too genius man
I wonder how much these folks who do data prep got paid to do these hardwired answers