Well.. I am a coder - and damn proud of it. The programming / coding / tech world can be quite snobby at times. It's like people just try to look down on others for no real reason.
Quick tip for everyone who wishes to be a coder with a good programming base. Not necessarily a (discrete) math expert, but a solid developer. Invest in learning C. It's syntax, data types, memory handling, usage of pointers and so on. Once you're at a good level in C, most common languages will seem easier to grasp, and you'll have a better understanding about what's happening "under the hood" with more high-level syntax. IMO, if you start at Python or Javascript, for example, without a theoretical background, coding might seem a bit like it's just about knowing the right calls (as if you're spell casting) or the right APIs and Frameworks. These are all useful for sure, but they're tools, not the craft itself.
Totally agree, later you can learn OOP languages and try to implement some of the concepts in C ( such a polymorphism ), and then most languages will come more naturally.
I tend to agree, because that's how I started. Even though C is not an object oriented language, I developed an object oriented mind set. That is due to the the fact that my first project required that I think in those terms. Moving to C++ was a bit of a chore, but it is still my preferred language. Those languages allowed me to start be productive in C# from day one on a new job. I was with the company for 2 years before my manager and teammates learnt that I had not written one line of C# before they hire me (I was hired based on C++ knowledge). Some of the more advanced concepts that a C/C++ programmer takes for granted are almost impossible to accomplish in some of the higher level languages like C#. The advantage of higher level languages is that they just work until they don't, at which point understanding what is happening under the hood becomes a very important factor.
@@user-qy6tu9ip9v It can be. In my case I had a goal and already new what language I wanted to use. I started slow writing one small piece at a time. As time went by I learned more and kept improving the code, based on my research (no internet at the time) and new ideas I had along the way. You can start with something simple like "Hello Wold", but in today's world that's a cut and paste project in just about every programming language out there. I would recommend a more ambitious goal and start at the beginning. Write down what you want to create (your goal), then write down what you need to make that happen (intermediate goals). Don't try to do it all at once or you'll get frustrated and give up. If it is Windows program, then first learn to create an application Window. Modern development environments well normally do that for you. Then you'll probably want buttons, and etc. During each step you'll learn something new. What I am describing here is the top down approach; designing the interface first and then the pieces that make it work. As long as you keep each piece as simple as possible, you should have no problems eventually reaching your goal.
Programming is the action of telling a computer to do something; "You program a computer" and that means you somehow tell a computer to perform a specific task. How you achieve that is not defined by that term. Writing code is one way to do it, feeding specific non-code data to it is another one. One day you may just tell it with your voice what to do and even that would be considered programming. Even feeding data to an AI and correcting its errors would be considered programming and it doesn't involve any code at all. Programming is not abstract, though, unless you perform it only theoretically and thus never need to teach a real computer to perform an action. To really program something, you need to know in practice how to make a computer do it. If you only know how it is done but not how to tell it to a computer, you cannot program that computer. Coding is the action of writing code. You write code to make a computer do something but as I already mentioned above, this is not the only way you can tell a computer to do something. If programming is cooking, coding is baking. Not everything can be baked and not all cooking is baking. Coding is basically the most common way today to program a computer, yet you can also write code with a pen on a piece of paper. So coding can be as abstract and theoretical as programming. As for the person, a programmer is a person hired to program computers. A coder is who writes code. Yet nobody hires coders as a coder is useless. The only reason why you would want someone to write code for money is to program a computer and then he's a programmer. So a programmer is also a job description, a coder is not. People saying they are coders are people that like to code and they may do it for a living but then they are for sure programmers.
I've never met a single programmer who called himself a coder... "coder" is mostly a word used by marketing people who see IT people as magicians reciting some weird ancien spells.
The job market has become huge and diluted. People who deal with instructing computers have become so common, the job itself has become cheapened into a simple lowly word like "coder". makes it easier to pay them less. It's like a general laborer on a construction site. You have the carpenter (the programmer), and the laborer (the coder, or 'junior' something).
@@PPedroFernandes I think it's still useful to make a distinction between HTML and CSS on the one hand, and JS on the other; the former two is about presentation, while the latter is about behaviour, in particular interactive behaviour.
I think the difference in definition is not significant it's just that calling someone a coder is offensive. But that would make his video about 30 seconds long.
In 10 years of being a coder, engineer, programmer, developer, architect, whatever you call it, I've never heard anyone being offended by being called a coder. Everyone I've ever met uses these terms basically as synonyms, because they don't really care. In the real world you will almost allways do all of these things.
Agreed, I just saying programming for simplicity sake.. If I'm working a company they can use whichever title they like as long as it pays well. 🤣🤣🤣😅😅👌
In Germany, gamers (PC) call themselves „Zocker“. But Zocker means gambler. But gamers are nor gamblers (usually). So why do they use this term? I think because kids thought it was cool. I always thought coder was something similar to that in regard to programmer.
Way back in the mid-1980's (yes, I'm old!) I worked for a small company doing assembly language programming for embedded systems that were based on the 8-bit Intel 8085A microprocessor. We always referred to each other as "Programmers", but during technical discussions we talked about our "code" and how we can improve its efficiency and maintainability. As a home "hobbyist" your code can be total garbage as long as it does what you want it to do. But in industry, especially when programming for a medical manufacturer or the military, your code MUST be efficient for the platform it will run on, and your code MUST be maintainable by other engineers who later may be tasked to debug or modify your software long after you are gone!
"...We always referred to each other as "Programmers", but during technical discussions we talked about our "code"... " Not quite as far back as you but that's the same thing I've always known. Code is the what and programmers are the who that create it. Simple. Done. Why do we need to create a separation? What's the logical reason for it?
are there even real programmer Jobs? I worked as a "programmer" in 3 companies up to this day but in the end the tasks for each of the team members were kinda small and needed to be simple in order to be understood by he other developers. I mean its theoretically programming what we did, but the tasks did not require much logic at all and the only thing we did besides this mindbogglingly simple typing was fixing bugs that were mostly related to something like a dependency issue... In my experience the only real programming happens in your personal projects or ironically at coding challenges xD
@@nithishchilumula1992 Find a job where C is the only language you may use. Firmware, BIOS programming, hardware prototyping for example. When there is a scope and money to earn, you learn it in no time 😊
For customer: Having a product that's more reliable. They don't want to call product support because, unknown to them, there is a bug barried somewhere in that spaghetti code. For company: Having a code base that is easier to maintain, modify and export. In the long run, this saves them money on future development and reduced service calls. It also increases repeat business due to the companies reputation for reliable products.
There's no difference. The vid is confusing computer science fundamentals with coding, as to not trigger people who don't have a degree with a chip on their shoulder. But not to say computer science cannot be learned outside of college, it's just silly to say there's a difference between "programming" and "coding". There's designing software and code monkeys but I'm not sure where the new hierarchical jargon came from since it has never been this way before. Reminds me a lot of "clean code"/Ruby on Rails which takes standard computer science concepts, renames, and repackages them to people who went to boot camp looking for gurus.
This seems like the subtle, but important, difference between an author and a writer. Anyone can be an author - just write some stuff in a semi-coherent way and publish it. But a writer is skilled in the nuances of written language, all of the technical terms and styles, and is able to write something deep and complex in a way anyone can understand upon reading it. One is a skill, the other is an art. But both use the same words and tools.
I worked as a Jr. level programmer back in my 20s (all pre-Windows stuff) working primarily in UI and creating coding tools. Back then, there was a much blurrier line between programming and coding. Now days, I would classify myself in a third category as a "scripter". What is the difference? Well, now I am more of an IT generalist. I do, at times need to automate many of the things that I do. For these, I work in scripting languages. I can do some fairly complex and complicated scripts. But would never call myself a programmer or a coder. I just don't do what they do. I'll put together a dynamic website if I need to. I'll completely automate PC and software deployments, complete with network identification and domain registration. I'll automate file and database analysis. I even have scripts that generate and print various barcodes from scratch, without relying on libraries or fonts. But it still isn't the same as what a programmer or a coder does. Writing a script, developing a program, and writing code are definitely three very different things. I can't say one is inherently better (by better, I mean requiring greater knowledge or skill) than another. There are lower and higher levels in each area. I know programmers that couldn't code properly to save their lives. I also know coders that couldn't possibly put a program together. But, contrary to the general public and business views; programming, coding, and scripting are most certainly not the same.
It's all the same. You write a piece of text with instructions the computer has to execute. Wether you call it a program, a code or a script is irrelevant
You need people at all ends of the spectrum. I get the feeling some people use this pedantic differentiation to prove how they're better/smarter than someone else.
To be honest thing he is speaking about big problème here in my contry alot of people think you can be and beat 5 years cs major from few vidéos on TH-cam so they major in diffrent field like medcin then they start learning from youtube then they will never beat cs major guy neither became good doctors basicly thee life is fucked
You can write print(x) as print(x);. This is very helpful for the people reading your code who are blind as a bat and need someone to tell them when a line has ended…
Never watched nor have I subscribed to this channel , and nor have I watched any videos related to programming, yet this video intrigues me. TH-cam Recommendations work in mysterious ways.
To put it into perspective Programmers -> Architect, engineers Coders -> Builders Programmers and coders could, but not necessarily interlap with each other. In the olden time when programs were punched to cards, programmers design and decide where to punch holes, coders punch the holes. Could be the same person, could be not.
@@MADHEWPRAGUE I find Fin's answer here to be good, because you can add the nuance yourself by thinking it through. Builders and architects are colleagues. Architects come to builders for advice on details, and they have important dialogues on things such as which materials to use for a given surface or feature. You can have a building project, such as a private home, where you (the customer) do your own drawings and where they are revised with the help of an architect or perhaps just a highly experienced builder. Many good architects have builder backgrounds, but rarely the other way around. The degree to which you need to involve an architect differs highly from project to project, and the degree to which a builder needs to be able to do architectural thinking differs. And of course you have DIY which compares to open source.
2:03 I’ve actually used scratch as a sort of hobby when I’m bored for quite some time now, and theres a surprising amount that can be done with it. You can create online multiplayer games, full 3d engines with lighting and textures and I’ve also managed to make a near perfect copy of the original super mario brothers so I don’t have to get my hands on an nes.
Never coded with Python, but I saw Print and I fall in love as mainly being an iOS developer And, usually I look at coding as the syntax for a language (it’s more of the literature of the programming world) - and then programming is the actual problem so living skills.
This was very enlightening, I can somewhat appreciate the distinction. Though I would disagree that coders should be held lower than programmers. I don't know if you do read these comments, but can you tell me any concrete steps in how do you grow as a programmer? I am always at a loss as to what to do. If I learn language and syntax, I am forced see a requirement in learning logic. If I learn logic I am again forced to learn languages. Most of the times different projects have different requirements in languages and syntax. Due to which logic is forced to take a backseat. Improving logic is also time taking, difficult and hard to measure. If I solve DS problems, math problems and other logic problems it is always hard to quantify what I have learned and how I have to apply it in my present work. It always feels like an exercise in futility. Because most of what I have learned is of no use temporarily and I would like to save brain power to focus on the problems in front of me before other things.
Exactly. The entire video is pointless. These are just words and who cares if someone calls me a coder, programmer, developer, software engineer. It doesn't matter. All that matter is that you know what you're doing and get the job done. Terminology is useless
There is a difference but this guy misses the point. Codification or coding is putting a program into words basically. You don't even need a computer to program, you can do it in your head, use stuff like UML, or whatever, but to codify into something usable by compiler you certainly do need a computer. Codification is just part of the development cycle.
Something to consider. A developer is a creative mindset behind the need to innovate. When someone invents a programming language, it has built-in commands to run it. For instance the korn-shell is a command-execution program. In unix or windows, ls and dir exist, each is a command and the shell interprets the command and executes it. Here's the next question, is scripting a programming language? The short answer is no. a script is comprised of commands that are written in a format that is understood and executed by the interpreter, be it power-shell, python, perl etc. etc. Coding is the verb for creating scripts and or programs. A programmer can code a set of instructions, then compile them into a program. Just because I understand scripting and one or more programming languages, it does not make me a developer. Why does a writer need a proof-reader? Because the writer is the creative side, the proof-reader is the grammar expert. There are some people who can not create new code, but they can understand and troubleshoot it or make it more efficient. So that's how it see it. -G
The biggest difference is that programmers (usually engineers) have to go through countless hours of maths, physics, imbedded systems, coding etc. to get their degree. as oppose to coders (usually self though or via coding camps) only focus on the coding side of things.
1. Embedded* 2. Im certified in PROGRAMMING in python from Purdue Uni and all we did was “code”. Theyre interchangeable. Stop overthinking it. 3. What youre refering to is computer science/software engineering/computerwngineering
I've been coding 75 years now. Still have no idea what's going on
3 ปีที่แล้ว +24
I had a really GREAT formation in programming: every week they teach us some technique (Bubble sorting, queue processing, tree trailing, etc.) and then gave us a list of ten problems to solve by programming the answer (Normally apliying what we had just learn, but without expliciting it). It was a lot of fun and excitement
That was no course: it was the IUT formation: it was a cooperation between Venezuela and French Government. As a matter of fact I never know how to answer the questions about degree of formation because it's what we call "Pre Grade" but is Universitary nonetheless. It was suppose to fullfil the gap between ingeniers and plain workers
Yep, but not necessarily just a computer though. You can program in anything, mathematicians used to express their algorithms on paper, not even intended for a computer to run it, creating the algorithms itself is programming, and they codified it using math.
I ain't a programmer , I ain't a coder , I am a freaking Engineer. We engineers carefully architect ,design and implement application specific solutions using the best practices. You can think coding as just the implementation part, while programming is the algorithmic design.
Best practices are known to not be best. I use common sense to architect, design and implement. Silver Bullet Patterns are for Losers. They prevent you from thinking and innovating.
@@rickarmbruster8788 You are half right, silver bullet patterns are indeed for losers ,also called script kiddies, however best practices are merely guidelines and they are optimal should you choose to not follow them might lead to messy codebase. Moreover, your innovation will be reflected from your sollution not from how you structured your codebase.
@@sfk1991 As long as we cant prove that P = NP, we are inherently incapable of finding the optimal solution to certain complex problems. I understand the point when we would simply admit we would follow practices to unify the way of handling certain problems. We could also admit that we use practices because we just are familiar with them and they served sufficiently in the past. Thats totally ok. But "best Practice" is no sufficient reason for doing anything in development. Development is an art if we really give it a chance. Thinking out of the box doesnt happen otherwise. And i dont talk about complex algorithms or code to show off, i talk about the way doing things simple and concise without following xyz paradigms and idioms. As a C/C++ Engineer i just felt in love to Software Architecture. When you could see what kind of structural design i have in mind months before i even touch the keyboard, you would exactly understand what i mean.
I have carried the title of engineer since I started designing and implementing solutions 30 years ago. But I have always considered myself a programmer. It wasn't until I worked for a big corporation that I realized, that many, if not most, programmers have never designed or implemented an application or system from scratch. When people ask what I do for a living, I just say that I tell computers what to do.
WHEN YOU'RE FEELING A DEEP APPRECIATION FOR THOSE WHO HAVE MADE A DIFFERENCE IN YOUR LIFE. I AM SO THANKFUL FOR YOU IN MY LIFE NOW I HAVE MY OWN HOUSE IN THIS LIFE.THANKS FOR THE SUPPORT *WILLIAM DORSEY* u such a great mentor
I relegate 'coding' to the implementation using structured commands and 'programming' as the design. I've got over 42 years in the same database language that's still going strong. I have several analogies: Excel formulas versus the underneath VBA. One musical analogy came to mind. I was on a train and two teenagers were listening to rap music on their boom box. One said "He's not rapping, he's just rhyming". Thoughtful observation illustrating the difference between a song with feeling and a song that just has matching words.
Dude. you video was amazing. I've been coding for over a decade(self-taught), it wasn't until I sat in my programming class did the difference become clear.
I have been on this earth for 21 years now and this is legitimately the first time i ever heard of a practical application of math. Think about how wrong that is, the education system is filled with useful subjects in actuality that have many fields of application, yet they never actually show you where you should know the stuff that they get you to know, they just to teach you, but you don't know why you are learning. What we need is to inspire people to learn, but that can only be done if they are shown the full potential, not just taught everything randomly all the way through elementary-, middle-, and high school. My biggest bone to pick with the education system has always been this and it is annoying frankly because they don't seem to realise how important it is to show people and make them understand WHY they are learning. The why gives a strong driving force and motivation.
In order to know what programming is: Write down a sorting algorithm in a recursive manner in pseudo code with pen and paper. In order to know what coding is: Try to implement the pseudo code from your paper in 3 different programming languages. Preferably imperative, functional and object oriented.
I disagree. If you're not writing code then you're not programming. If we're going to be that loose with the word we might as well say all those people back in the 1980's who "programmed" their VCR to record at 3:00pm are programmers too. In that case, let's call everyone who's changed the clock in their car a programmer so we have to invent a new word to describe what we do. While we're at it, let's call the application of a Band-Aid "practicing medicine," and one who does so a "medical doctor." Programming = writing code Coding = writing code The terms are therefore synonymous. Writing down or inventing an algorithm is "writing down or inventing an algorithm," aka "design." It's not "programming" in any sense of the word.
Excellent video. Thank you for quickly showing different levels of programming. For me, programming is having mastery in the assigned industry area, and be able to understand the workflow and problems that arise. It doesn’t matter if it’s in BASIC, DOS batch files, dBase, rBase, Lotus 123 Macros, Prolog, RPG, COBOL, HTML, Lotus Notes, Netware, Visual Basic, Excel, Access, Word, IBM MVS, Oracle, SAP, .NET, Java, JavaScript, SalesForce, or Python (the latest for me), the coding environment is the easiest thing to absorb. The challenge is to understand how people work, what the managers want to see, and maximizing the bottom line. Seeing the big picture interact with the minute details is a skill that develops with time and experience. Being curious about everything and willing to explore from the backend to the final expectation is daunting and fantastically rewarding.
"What benefit does refactoring have to the end user?" The benefit is that refactoring improves code quality and reduces complexity, which in turn makes maintenance easier, which means more features and bugfixes come sooner rather than later. More time polishing the code now = less time fighting with it later = more time to develop = better user experience = loyalty = money. You just gotta speak their language. It's not a "waste of company time". It's an "upfront investment".
> _"You just gotta speak their language. It's not a "waste of company time". It's an "upfront investment"."_ oh lololol. i knew you gotta speak their language, but didnt know what the proper term would have been (:
When I took Com-Sci in university several projects were "build a program to do this simple thing - then implement in 4 different languages and at least 2 paradigms". You learn a lot when your designing some pseudocode planning to implement it in both a state machine as well as an imperative language.
a great programmer once told me that the difference between a good programmer and a great programmer is a good programmer can write a good programme in any language he knows whereas a great programmer can write a good programme in any language he doesn't know.
WORDS ARE NOT ENOUGH TO EXPRESS MY GRATITUDE TOWARDS YOUR KINDNESS TO OUR FAMILY mr. WILLIAM DORSEY WE ALL SAY THANKS YOU VERY MUCH MAAM, your online classes are top notch and one of the best instructor out there…
A bit late to your party. Agree with everything you said, just to add: An extra skill required at the coding end, is coping with language version updates (incl. depricated commands), language bugs and resulting library incompatabilities. A special shout out to Python, thank you guys.
As a computer science graduate, I would describe a programmer someone who writes code from the foundation up. The coder writes code in packets that already do the basics, or are built.
But a programmer uses syntax and compilers aswell. That's also prewritten. This makes no sense. By these standards, only bit-programming is done by programmers.
Good points on bringing up what was taught in a CS curriculum. I kind of forget why some classes are there, usually none of these dots connect until you start your career. I feel that the label of a programmer or a coder is perceived similarly like a monkey that wrenches until something works. Engineers are seen as those who design systems for the longevity of software that will be used for years to come, the ability to implement that necessary code is just expected once the solution is well thought through after tons of planning.
I am learning front end. Currently at the stage of my js part. And I will, build my website. One way or another. Say there are thousands programmed algorithms to reduce my goals to nothing. When I digress, I enjoy coding, and I enjoy getting progress in it. Whatever will happen to me in the future, I will know something. And only the moment I would want to add something to my website, I will hire a team of programmers to work for me. Because in that time, I'll be succesful enterpreneur, with thousands and millions in his business which he created both by coding, and by growing as a person.
The terms "programming" and "coding" are often used interchangeably, but there is a subtle difference between the two. "Coding" refers to the act of writing code, which involves using a programming language to create software or other applications. This can involve writing code from scratch, copying and pasting code snippets, or modifying existing code. "Programming," on the other hand, refers to the broader process of designing and developing software. This includes tasks such as analyzing requirements, designing software architecture, testing, debugging, and maintaining code. In other words, coding is a subset of programming, and it involves the actual writing of code. Programming, on the other hand, encompasses a wider range of tasks beyond just writing code, such as planning, analysis, and testing. Both coding and programming are essential parts of software development, and both require knowledge of programming languages and software development concepts.
Coding is just a part of programming. Here's a simplified breakdown to clarify the relationship between the two: Programming (The Bigger Picture) Programming is the entire process of solving a problem using a computer. It involves: Understanding the Problem: Analyzing the requirements and constraints. Designing a Solution: Creating algorithms and planning the structure of the software. Coding: Writing the actual code to implement the solution. Testing and Debugging: Ensuring the program works as intended and fixing issues. Deploying and Maintaining: Running the software and updating it as needed. Coding (A Subset of Programming) Coding is one step in the programming process. It focuses on writing the instructions in a specific programming language (e.g., Pascal, Python, Java). It's about translating algorithms into machine-readable syntax. Coding doesn't involve planning the solution, testing the program, or deploying the software-it’s only about writing the code. Analogy Think of programming as building a house: Planning the house design (blueprints) = Algorithm creation and problem analysis. Construction (laying bricks, wiring, plumbing) = Coding. Inspecting the house and fixing issues = Testing and debugging. Living in the house and maintaining it = Deployment and maintenance. In this analogy, coding is like the construction work-important, but just one part of the entire process of building the house. Conclusion Coding is essential, but programming involves much more than just writing code. It’s about solving problems and creating complete, functional systems. Coding is the hands-on part of translating a planned solution into something the computer can execute.
The more I program, the more I think about going back to learning math. To be honest, I'm not too good at math, but programming makes me hunger for math. They really are logic bros.
Success is not final; failure is not fatal: it is the courage to continue that counts. Business opportunities are like buses, there’s always another one coming.
Talking about opportunities investing in crypto currency now should be in every wise individuals list. In two to three years time you might be estactic with the decision made today
I'm been programming professionally for 20+ years and was doing it for 10-15 years before that as a hobby. There was a time years ago where I might have imagined making a distinction (but never did), back when HTML was new and consisted of little more than bold and anchor/link tags and so on. It was just a markup thing back in those days that anyone could learn and get pretty good at in a few days of playing around. At that time I would have been annoyed if people making web sites or using HTML or similar called themselves "programmers" or even "coders" because what they were doing wasn't really programming/writing code. "Coding" and "programming" were the same thing in my mind, so I'd have been annoyed with either term being used two or three decades ago to describe what most folks making web pages did: Writing HTML. If a non-tech person knew the word "code" I could describe myself as a "coder" so they'd understand more or less what I did. If they knew the word "programmer" then I could use that term. I'm mainly a physics engine programmer so that kind of thing annoyed me back then. Your 10 year old writing web pages with HTML 1 was not a programmer/coder. Today with modern CSS and HTML and whatever else, I'm not so sure it would bother me like it would have back then. Those have loops and function calls and variable storage and everything else today as opposed to simple tags, much of the same stuff that a C++ programmer uses. In practice today I've never seen any uproar. I primarily do remote game programming contract work for companies of all sizes. When I'm working with a new team I'll often ask if this or that person on the team is a programmer. The response is either "yes" which I take to mean that person writes C++/C# or similar code on the game engine, or it's "no, this person is a 3D artist or vehicle dynamics tuner" or what have you, but doesn't write code. I've never once had somebody respond with "no, person X is a coder, not a programmer" as though they were different things. If someone were to respond that way I'd ask for clarification because what I really want to know is if they are writing code in the game engine or not. If they are, they can call themselves either a programmer or a coder as far as I'm concerned. To my mind "coder" is just shorthand for "programmer." I use the terms interchangeably, as does every other programmer I've ever worked with. I don't see how it helps anyone to make a distinction between the terms. You're either writing computer code in some programming language or you're not. One can argue over whether certain "languages" are programming languages or not, but calling somebody who's writing in a language that isn't a programming language (hard for me to think of one these days) probably shouldn't be called either term. If you're programming, you're writing code, so either term applies.
it is still the same. In German e.g. coding and programming translate into "Programmierung". Maybe he talks about "scripting". What in some form is also programming/coding. Maybe he needed an excuse to make a video. And we watched it.
Discrete math is not specifically for programming and neither is it "often" or "frequently" the case. "Math the logic branch and programming the applied branch." Bruh, not even close to true. You're missing a few branches in that binary tree
I'm a software engineer lead, and those are decently synonyms in practice; they should not be separated based on those made up categories, that's just complicating stuff. Css and html bacaue they are not logical language, they are just more advanced version of something like markdown.
Excellent. Thank you for tackling on this. Programming is a set of mind, which though can and should be trained. Coding is a tool. Learning coding does not necessarily make one into a programmer, whereas to become a programmer coding is a must.
I can tell you put a lot of effort into this video, but please don't use your influence to spread misinformation. 'coding' is just an informal synonym for programming. They are the same thing.
en.wikipedia.org/wiki/Computer_programming Calling this video "misinformation" is rude enough considering the words have different meanings for different people, but if you do so, don't disagree with wikipedia, at the very least.
@@frodeflem9353 The reason why I'm calling this misinformation is because it's 99% semantics that would just confuse people who want to get into the software industry. There are some truths to what he says, but it just doesn't matter. People who are just starting to learn how to write code easily get caught in unnecessary details and it can be quite overwhelming at first. Maybe I exaggerated a bit calling this misinformation, but I'm afraid making a dedicated video about the semantical difference between coding and programming will do more harm than good. I haven't seen other videos this guy makes, maybe he gives really good advice in his other videos.
I decided @30 to disagree. It's silly to compare synonyms and say there is a difference. Coding is used as a slangish synonym for programming. There may be different connotations among certain groups, but certainly no different meaning. That is unless you can code up a program without using any code (?) or committing any action that will in any way utilize any sort of programming code. Perhaps you're an architect and actually writing any programs is far beneath you -- Are you a programmer ? Shut the front door.
3:14 very relatable 😂😂. I wanted to learn Java first but saw this super long code. You need to write a code of 3 lines to print 2 words and I immediately quitted Java and now I'm learning Python 😂
The distinction I have always made between the 2 terms is that coding is the understanding and implementation of general programming language syntax, while programming is the full implementation of a language or system to create a fully functional and self-contained application. Anyone can learn to code on some level of functionality, but few of them can write a program. If someone tells me they are a coder, I roll my eyes and think, "right, who isn't nowadays"? They can write a for loop and parse a text file into an array. If someone tells me they are a programmer, I stand aside with respect, for they create the systems that make our world function. Notice in the speeches of local politicians and education officials, they implore us that "everyone should learn to code". They never say, "everyone should learn to program".
The reason to teach different parts of programming in different languages is so you learn the concept rather than syntax. Like, instead of learning how to write a do while in php, you learn what the while loop does, why to use it. So if you understand iterating through an array, you will know when to look up the exact syntax for whatever language you're working in at that moment because now you know that's the structure or method you need to use rather than memorizing a string of commands specific to a language.
coding: The implementation of functions using written instructions to a computer. programming: THe design of a function or set of functions to achieve a desired set of results. mathematics: When used correctly it can provide the paths to the most effective results sets. In production, it may be used to predict performance, assess performance, evaluate usage patterns and computing resource capacity needs. In IT these skill sets are expected to exist in each IT employee in varying degrees of expertise. If system analysis and design are implemented well they can produce and use reusable code that can greatly reduce time to production for future systems and functions. I like the phrase "write once, use many".
Free Beginner Programming Course
coursecareers.com/a/aaronjack
Free JavaScript Cheat Sheet
dontforgetjavascript.com/
Free Coding Advice (We'll Send you a Video)
aaronjack.dev
keep teaching beginners with your stupid course and charge them for nothing. what can a rookie like you have to teach really?
I'm interested, how do I get the video
Rttttt❤❤
Paying $$ for a IT support cert from Course Career would better if you focus on getting comptia A+ or even CCNA.
Im a senior Software Developer... They're just terms... We use both in sentences and they have both the same meaning
Oh
How do I start programming/coding as an absolute beginner??
@@user-qy6tu9ip9v start by finding the antilife equation ;)
@@peacemekka I already found it. The Armada was ready.
I understand that you have to be coder before being programmer.
Well.. I am a coder - and damn proud of it. The programming / coding / tech world can be quite snobby at times. It's like people just try to look down on others for no real reason.
I think that's common almost anywhere. God, I love freelancing.
If you did some low level programming, some C, C++, you would understand why people look down on those who do HTML and CSS.
@@nnn-ej3zm Nah. I can do C#, Python, JS, HTML and some CSS. It's just arrogance. They're just different art forms that function differently.
@@olympiancss You do understand those languages have nothing to do with low level programming?
@@nnn-ej3zm you’re proving his point
If I was being waterboarded, I would finally have to admit I'm just a lowly computer programmer. On my resume, however, I'm a software engineer.
Underated
Are you DevOps or Full-Stack? Hopefully you're not bottom of the barrel QA/QE/Tester/Click a bunch of buttons and report it loser 😜
Same
Programmers can do it all.
Software Engineers are STEM programmers, with the T(echnology) almost left out.
@@looniper3551 software engineers get hired for 6 figure jobs, programmers make money begging for jobs
"You can think of maths as the theoretical branch and programming as the practical branch."
Physics in the corner: _crying_ ...
Math is the coding of the universe and programming is the coding of computers.
Physics is a little bit to the side and is defined as applied math. Here’s a meme th-cam.com/video/IqYpx22bSwI/w-d-xo.html
Various applications of maths
Math is the coding of the universe, while physics is the program.
And side note, Physics grads I've worked with who moved in to software development have, to a person, been outstanding engineers.
Quick tip for everyone who wishes to be a coder with a good programming base. Not necessarily a (discrete) math expert, but a solid developer. Invest in learning C. It's syntax, data types, memory handling, usage of pointers and so on. Once you're at a good level in C, most common languages will seem easier to grasp, and you'll have a better understanding about what's happening "under the hood" with more high-level syntax. IMO, if you start at Python or Javascript, for example, without a theoretical background, coding might seem a bit like it's just about knowing the right calls (as if you're spell casting) or the right APIs and Frameworks. These are all useful for sure, but they're tools, not the craft itself.
Totally agree, later you can learn OOP languages and try to implement some of the concepts in C ( such a polymorphism ), and then most languages will come more naturally.
I tend to agree, because that's how I started. Even though C is not an object oriented language, I developed an object oriented mind set. That is due to the the fact that my first project required that I think in those terms. Moving to C++ was a bit of a chore, but it is still my preferred language. Those languages allowed me to start be productive in C# from day one on a new job. I was with the company for 2 years before my manager and teammates learnt that I had not written one line of C# before they hire me (I was hired based on C++ knowledge). Some of the more advanced concepts that a C/C++ programmer takes for granted are almost impossible to accomplish in some of the higher level languages like C#. The advantage of higher level languages is that they just work until they don't, at which point understanding what is happening under the hood becomes a very important factor.
I'll certainly take this into consideration! Thank you so much.
@@johnshaw6702 I don't even know where to start with coding. It's so intimidating....
@@user-qy6tu9ip9v It can be. In my case I had a goal and already new what language I wanted to use. I started slow writing one small piece at a time. As time went by I learned more and kept improving the code, based on my research (no internet at the time) and new ideas I had along the way.
You can start with something simple like "Hello Wold", but in today's world that's a cut and paste project in just about every programming language out there. I would recommend a more ambitious goal and start at the beginning. Write down what you want to create (your goal), then write down what you need to make that happen (intermediate goals). Don't try to do it all at once or you'll get frustrated and give up. If it is Windows program, then first learn to create an application Window. Modern development environments well normally do that for you. Then you'll probably want buttons, and etc. During each step you'll learn something new. What I am describing here is the top down approach; designing the interface first and then the pieces that make it work. As long as you keep each piece as simple as possible, you should have no problems eventually reaching your goal.
Programming is the action of telling a computer to do something; "You program a computer" and that means you somehow tell a computer to perform a specific task. How you achieve that is not defined by that term. Writing code is one way to do it, feeding specific non-code data to it is another one. One day you may just tell it with your voice what to do and even that would be considered programming. Even feeding data to an AI and correcting its errors would be considered programming and it doesn't involve any code at all. Programming is not abstract, though, unless you perform it only theoretically and thus never need to teach a real computer to perform an action. To really program something, you need to know in practice how to make a computer do it. If you only know how it is done but not how to tell it to a computer, you cannot program that computer.
Coding is the action of writing code. You write code to make a computer do something but as I already mentioned above, this is not the only way you can tell a computer to do something. If programming is cooking, coding is baking. Not everything can be baked and not all cooking is baking. Coding is basically the most common way today to program a computer, yet you can also write code with a pen on a piece of paper. So coding can be as abstract and theoretical as programming.
As for the person, a programmer is a person hired to program computers. A coder is who writes code. Yet nobody hires coders as a coder is useless. The only reason why you would want someone to write code for money is to program a computer and then he's a programmer. So a programmer is also a job description, a coder is not. People saying they are coders are people that like to code and they may do it for a living but then they are for sure programmers.
This was a way better description then that whole as video I just watched
Thank you 🙌🏾
I appreciate this I'm new to programming. Just getting started, this kinda open my eyes now
nice
Genius!!!
I've never met a single programmer who called himself a coder...
"coder" is mostly a word used by marketing people who see IT people as magicians reciting some weird ancien spells.
Yes yes I agree
The job market has become huge and diluted. People who deal with instructing computers have become so common, the job itself has become cheapened into a simple lowly word like "coder". makes it easier to pay them less. It's like a general laborer on a construction site. You have the carpenter (the programmer), and the laborer (the coder, or 'junior' something).
AKA: my grandmother
Alchemist perhaps, NEVER "a coder" NEVER!!
*Smashes Keyboard*
"I'm in the deep Web Now."
this man's voice makes me feel like i'm ready to make a game without even knowing how to program
So, all these years I've been CODING in HTML and didn't even know that
How
In today's world you can't really do a decent job with HTML without using JS as well so... It's fair enough imo
@@PPedroFernandes I think it's still useful to make a distinction between HTML and CSS on the one hand, and JS on the other; the former two is about presentation, while the latter is about behaviour, in particular interactive behaviour.
I started Coding Python 3 a few weeks ago and Html last week
@@PPedroFernandes the bare minimum for front end right now is HTML, CSS, JS, Bootstrap, and React
next: developer vs software engineer
DVDA
next:poo poo
As a developer of 3+ years I still didn't fully understand the difference lol
I think Programming is basically the logic and a little bit of planning of a project and Coding is the implementation of it.
my take away is that humans are stupid and insecure.
@@381delirius its because you're too stupid to make the connection
It’s because you’re likely a front end dev :p
I think the difference in definition is not significant it's just that calling someone a coder is offensive. But that would make his video about 30 seconds long.
In 10 years of being a coder, engineer, programmer, developer, architect, whatever you call it, I've never heard anyone being offended by being called a coder. Everyone I've ever met uses these terms basically as synonyms, because they don't really care. In the real world you will almost allways do all of these things.
Agreed, I just saying programming for simplicity sake.. If I'm working a company they can use whichever title they like as long as it pays well. 🤣🤣🤣😅😅👌
In the past 30 years, I don't ever remember being called a coder. I've been called every thing else on that list though.
In Germany, gamers (PC) call themselves „Zocker“. But Zocker means gambler. But gamers are nor gamblers (usually).
So why do they use this term? I think because kids thought it was cool.
I always thought coder was something similar to that in regard to programmer.
I need your help on something pls
Way back in the mid-1980's (yes, I'm old!) I worked for a small company doing assembly language programming for embedded systems that were based on the 8-bit Intel 8085A microprocessor. We always referred to each other as "Programmers", but during technical discussions we talked about our "code" and how we can improve its efficiency and maintainability. As a home "hobbyist" your code can be total garbage as long as it does what you want it to do. But in industry, especially when programming for a medical manufacturer or the military, your code MUST be efficient for the platform it will run on, and your code MUST be maintainable by other engineers who later may be tasked to debug or modify your software long after you are gone!
"...We always referred to each other as "Programmers", but during technical discussions we talked about our "code"... "
Not quite as far back as you but that's the same thing I've always known. Code is the what and programmers are the who that create it. Simple. Done.
Why do we need to create a separation? What's the logical reason for it?
Solid advice for newbies there
Yes. Back in the 80's that's exactly how it was. Sometimes a very good programmer would be called a Systems Analyst for some reason.
a big respect to old coders, because there were few guidese back then, compared to today it's like spoon feeding.
@@VRNocturne Yeah, that's like a musician getting offended when someone calls them a pianist. so fucking stupid
TLDR;
Programers are architects, coders are construction workers.
Do you mean that a programer is a person who just direct the way and coder is just a follow of that directed way ?
are there even real programmer Jobs? I worked as a "programmer" in 3 companies up to this day but in the end the tasks for each of the team members were kinda small and needed to be simple in order to be understood by he other developers. I mean its theoretically programming what we did, but the tasks did not require much logic at all and the only thing we did besides this mindbogglingly simple typing was fixing bugs that were mostly related to something like a dependency issue... In my experience the only real programming happens in your personal projects or ironically at coding challenges xD
@@julianfuchs4241 Sir , any software engineering advice for a beginner like me ?
@@julianfuchs4241 waiting in line too
This is a great metaphor that really clarifies the difference in a way that makes perfect sense to me
Those algoexpert ads im gonna break my phone
Use ad-blocker extension
Constantly...
TH-cam premium is great!!
So you wanna be a
@@RXhunter bro it would work in Web only I guess. in mobile how to avoid?
It took me only moments to code, but a life to program.
Can u suggest a best way to learn C language ?
@@nithishchilumula1992 Find a job where C is the only language you may use. Firmware, BIOS programming, hardware prototyping for example. When there is a scope and money to earn, you learn it in no time 😊
"What's the benefit to the end user?"
Getting updates won't require them to sell their organs in ~5-10 years.
For customer: Having a product that's more reliable. They don't want to call product support because, unknown to them, there is a bug barried somewhere in that spaghetti code.
For company: Having a code base that is easier to maintain, modify and export. In the long run, this saves them money on future development and reduced service calls. It also increases repeat business due to the companies reputation for reliable products.
Out of all my friends, none of us would feel offended being called coders instead of programmers. When first asked, none of us knew the difference
There's no difference. The vid is confusing computer science fundamentals with coding, as to not trigger people who don't have a degree with a chip on their shoulder. But not to say computer science cannot be learned outside of college, it's just silly to say there's a difference between "programming" and "coding". There's designing software and code monkeys but I'm not sure where the new hierarchical jargon came from since it has never been this way before. Reminds me a lot of "clean code"/Ruby on Rails which takes standard computer science concepts, renames, and repackages them to people who went to boot camp looking for gurus.
I ave a project that am stuck on.n i really need some help..cud some1 help me plz..i wud realy rwaly apreciate
@@jamaicanhackers1992 I think the best place to ask a question like that would be stackoverflow.com.
A coder is some typical writing machine code, but thermology has misused, and no one where strict about it anyway.
You mean there is one!! HAH
This seems like the subtle, but important, difference between an author and a writer. Anyone can be an author - just write some stuff in a semi-coherent way and publish it. But a writer is skilled in the nuances of written language, all of the technical terms and styles, and is able to write something deep and complex in a way anyone can understand upon reading it.
One is a skill, the other is an art. But both use the same words and tools.
Amazing! 👏🏾🙏🏻
I was about to understand somthin but the last sentence made me hella confused! :d
I actually was going to think exactly the opposite as start to read your comment! hahaha
I got it.
And both are used interchangeably xD
I worked as a Jr. level programmer back in my 20s (all pre-Windows stuff) working primarily in UI and creating coding tools. Back then, there was a much blurrier line between programming and coding. Now days, I would classify myself in a third category as a "scripter". What is the difference? Well, now I am more of an IT generalist. I do, at times need to automate many of the things that I do. For these, I work in scripting languages. I can do some fairly complex and complicated scripts. But would never call myself a programmer or a coder. I just don't do what they do. I'll put together a dynamic website if I need to. I'll completely automate PC and software deployments, complete with network identification and domain registration. I'll automate file and database analysis. I even have scripts that generate and print various barcodes from scratch, without relying on libraries or fonts. But it still isn't the same as what a programmer or a coder does. Writing a script, developing a program, and writing code are definitely three very different things. I can't say one is inherently better (by better, I mean requiring greater knowledge or skill) than another. There are lower and higher levels in each area. I know programmers that couldn't code properly to save their lives. I also know coders that couldn't possibly put a program together. But, contrary to the general public and business views; programming, coding, and scripting are most certainly not the same.
Wow, seriously
It's all the same. You write a piece of text with instructions the computer has to execute. Wether you call it a program, a code or a script is irrelevant
You need people at all ends of the spectrum. I get the feeling some people use this pedantic differentiation to prove how they're better/smarter than someone else.
Yep, and it's been like that for ages. But the truth is most people do suck at most things. Good news, though: it's not hard to be above average.
To be honest thing he is speaking about big problème here in my contry alot of people think you can be and beat 5 years cs major from few vidéos on TH-cam so they major in diffrent field like medcin then they start learning from youtube then they will never beat cs major guy neither became good doctors basicly thee life is fucked
"Pedantic Differentiation"!!! THAT deeservesan Acronym!!! SO PREVALENT in industry!
The greatest thing which i miss from Java in Python is the semicolon. I always feel like something is missing after writing a line.
I dont write a lot of Python, but to my knowledge you can still add the semicolon after a statement,it's just not necessary.
@@TwistInMyth it makes the code ugly to python programmers tho
I couldn't agree more. It really makes it feel like writing a sentence without a peirod (
Same here 😆
You can write print(x) as print(x);. This is very helpful for the people reading your code who are blind as a bat and need someone to tell them when a line has ended…
I'm a programmer and coder, and it's really a good job, I'm definitely happy, with what I do!!
Does it pay well?
Thank you. I liked and subscribed straight away.
Thx and welcome to the channel!
@@AaronJack you're welcome and thank you
Never watched nor have I subscribed to this channel , and nor have I watched any videos related to programming, yet this video intrigues me. TH-cam Recommendations work in mysterious ways.
Good job @Hassan Enzo
@@hassanenzo3680 Hehehe, nice way to make some side income, how much have you made so far?
To put it into perspective
Programmers -> Architect, engineers
Coders -> Builders
Programmers and coders could, but not necessarily interlap with each other.
In the olden time when programs were punched to cards, programmers design and decide where to punch holes, coders punch the holes.
Could be the same person, could be not.
@@MADHEWPRAGUE I find Fin's answer here to be good, because you can add the nuance yourself by thinking it through. Builders and architects are colleagues. Architects come to builders for advice on details, and they have important dialogues on things such as which materials to use for a given surface or feature. You can have a building project, such as a private home, where you (the customer) do your own drawings and where they are revised with the help of an architect or perhaps just a highly experienced builder. Many good architects have builder backgrounds, but rarely the other way around. The degree to which you need to involve an architect differs highly from project to project, and the degree to which a builder needs to be able to do architectural thinking differs. And of course you have DIY which compares to open source.
2:03 I’ve actually used scratch as a sort of hobby when I’m bored for quite some time now, and theres a surprising amount that can be done with it. You can create online multiplayer games, full 3d engines with lighting and textures and I’ve also managed to make a near perfect copy of the original super mario brothers so I don’t have to get my hands on an nes.
@Inverse Music that is amazing......that must have taken a lot of passion, determination and personal habit of wanting to learn......i admire that
Never coded with Python, but I saw Print and I fall in love as mainly being an iOS developer
And, usually I look at coding as the syntax for a language (it’s more of the literature of the programming world) - and then programming is the actual problem so living skills.
I totally agree with you ❤
This was very enlightening, I can somewhat appreciate the distinction. Though I would disagree that coders should be held lower than programmers. I don't know if you do read these comments, but can you tell me any concrete steps in how do you grow as a programmer? I am always at a loss as to what to do. If I learn language and syntax, I am forced see a requirement in learning logic. If I learn logic I am again forced to learn languages. Most of the times different projects have different requirements in languages and syntax. Due to which logic is forced to take a backseat. Improving logic is also time taking, difficult and hard to measure. If I solve DS problems, math problems and other logic problems it is always hard to quantify what I have learned and how I have to apply it in my present work. It always feels like an exercise in futility. Because most of what I have learned is of no use temporarily and I would like to save brain power to focus on the problems in front of me before other things.
Programming is a process which a computer uses to perform a task
Coding on the other hand forms a constituent of the process
Very simple.
In other words: how to create a problem where none existed before. Next step: how to bring cancel culture to development community.
Jose Gunji iz now canceled
Exactly. The entire video is pointless. These are just words and who cares if someone calls me a coder, programmer, developer, software engineer. It doesn't matter. All that matter is that you know what you're doing and get the job done. Terminology is useless
There is a difference but this guy misses the point. Codification or coding is putting a program into words basically. You don't even need a computer to program, you can do it in your head, use stuff like UML, or whatever, but to codify into something usable by compiler you certainly do need a computer. Codification is just part of the development cycle.
😂😂😂😂😂😂😂😂😂
@@straycursor5562 Thankfully, that's just your opinion.
Something to consider. A developer is a creative mindset behind the need to innovate. When someone invents a programming language, it has built-in commands to run it. For instance the korn-shell is a command-execution program. In unix or windows, ls and dir exist, each is a command and the shell interprets the command and executes it. Here's the next question, is scripting a programming language? The short answer is no. a script is comprised of commands that are written in a format that is understood and executed by the interpreter, be it power-shell, python, perl etc. etc. Coding is the verb for creating scripts and or programs. A programmer can code a set of instructions, then compile them into a program.
Just because I understand scripting and one or more programming languages, it does not make me a developer. Why does a writer need a proof-reader? Because the writer is the creative side, the proof-reader is the grammar expert. There are some people who can not create new code, but they can understand and troubleshoot it or make it more efficient.
So that's how it see it.
-G
hey, thanks! i hope this video helps people learn the difference because i know many people don't :)
The biggest difference is that programmers (usually engineers) have to go through countless hours of maths, physics, imbedded systems, coding etc. to get their degree. as oppose to coders (usually self though or via coding camps) only focus on the coding side of things.
1. Embedded*
2. Im certified in PROGRAMMING in python from Purdue Uni and all we did was “code”. Theyre interchangeable. Stop overthinking it.
3. What youre refering to is computer science/software engineering/computerwngineering
@@jamesdrury2387 so you are saying the the computer programming course does not have math ( a lot of math )?
I've been coding 75 years now. Still have no idea what's going on
I had a really GREAT formation in programming: every week they teach us some technique (Bubble sorting, queue processing, tree trailing, etc.) and then gave us a list of ten problems to solve by programming the answer (Normally apliying what we had just learn, but without expliciting it). It was a lot of fun and excitement
From where sir @RafaGómez
What course was this?
That was no course: it was the IUT formation: it was a cooperation between Venezuela and French Government. As a matter of fact I never know how to answer the questions about degree of formation because it's what we call "Pre Grade" but is Universitary nonetheless.
It was suppose to fullfil the gap between ingeniers and plain workers
Thank you so much for sharing this content. This is a big help for everyone.
Thank you!🙏
Programming is set of rules which is used to interact with your computer and when these rules are applied in your application , it is called coding.
Yep, but not necessarily just a computer though. You can program in anything, mathematicians used to express their algorithms on paper, not even intended for a computer to run it, creating the algorithms itself is programming, and they codified it using math.
Your video's got a lot better! light, crips and clear. Keep it up, big fan from Belgium :)
I ain't a programmer , I ain't a coder , I am a freaking Engineer. We engineers carefully architect ,design and implement application specific solutions using the best practices. You can think coding as just the implementation part, while programming is the algorithmic design.
Best practices are known to not be best. I use common sense to architect, design and implement. Silver Bullet Patterns are for Losers. They prevent you from thinking and innovating.
@@rickarmbruster8788 You are half right, silver bullet patterns are indeed for losers ,also called script kiddies, however best practices are merely guidelines and they are optimal should you choose to not follow them might lead to messy codebase. Moreover, your innovation will be reflected from your sollution not from how you structured your codebase.
@@sfk1991 As long as we cant prove that P = NP, we are inherently incapable of finding the optimal solution to certain complex problems. I understand the point when we would simply admit we would follow practices to unify the way of handling certain problems. We could also admit that we use practices because we just are familiar with them and they served sufficiently in the past. Thats totally ok. But "best Practice" is no sufficient reason for doing anything in development. Development is an art if we really give it a chance. Thinking out of the box doesnt happen otherwise. And i dont talk about complex algorithms or code to show off, i talk about the way doing things simple and concise without following xyz paradigms and idioms. As a C/C++ Engineer i just felt in love to Software Architecture. When you could see what kind of structural design i have in mind months before i even touch the keyboard, you would exactly understand what i mean.
I have carried the title of engineer since I started designing and implementing solutions 30 years ago. But I have always considered myself a programmer. It wasn't until I worked for a big corporation that I realized, that many, if not most, programmers have never designed or implemented an application or system from scratch. When people ask what I do for a living, I just say that I tell computers what to do.
Aren't best practices evolving all the time? So we need to keep reading, researching and studying.
WHEN YOU'RE FEELING A DEEP APPRECIATION FOR THOSE WHO HAVE MADE A DIFFERENCE IN YOUR LIFE. I AM SO THANKFUL FOR YOU IN MY LIFE NOW I HAVE MY OWN HOUSE IN THIS LIFE.THANKS FOR THE SUPPORT *WILLIAM DORSEY* u such a great mentor
I relegate 'coding' to the implementation using structured commands and 'programming' as the design. I've got over 42 years in the same database language that's still going strong. I have several analogies: Excel formulas versus the underneath VBA. One musical analogy came to mind. I was on a train and two teenagers were listening to rap music on their boom box. One said "He's not rapping, he's just rhyming". Thoughtful observation illustrating the difference between a song with feeling and a song that just has matching words.
Dude. you video was amazing. I've been coding for over a decade(self-taught), it wasn't until I sat in my programming class did the difference become clear.
I have been on this earth for 21 years now and this is legitimately the first time i ever heard of a practical application of math. Think about how wrong that is, the education system is filled with useful subjects in actuality that have many fields of application, yet they never actually show you where you should know the stuff that they get you to know, they just to teach you, but you don't know why you are learning. What we need is to inspire people to learn, but that can only be done if they are shown the full potential, not just taught everything randomly all the way through elementary-, middle-, and high school. My biggest bone to pick with the education system has always been this and it is annoying frankly because they don't seem to realise how important it is to show people and make them understand WHY they are learning. The why gives a strong driving force and motivation.
Great work! love your content. Keep it up!
In order to know what programming is: Write down a sorting algorithm in a recursive manner in pseudo code with pen and paper.
In order to know what coding is: Try to implement the pseudo code from your paper in 3 different programming languages. Preferably imperative, functional and object oriented.
I disagree. If you're not writing code then you're not programming. If we're going to be that loose with the word we might as well say all those people back in the 1980's who "programmed" their VCR to record at 3:00pm are programmers too. In that case, let's call everyone who's changed the clock in their car a programmer so we have to invent a new word to describe what we do. While we're at it, let's call the application of a Band-Aid "practicing medicine," and one who does so a "medical doctor."
Programming = writing code
Coding = writing code
The terms are therefore synonymous.
Writing down or inventing an algorithm is "writing down or inventing an algorithm," aka "design." It's not "programming" in any sense of the word.
Aaron Impeccable explanation, Bravo.
I STILL dont get it.
😂
Excellent video. Thank you for quickly showing different levels of programming. For me, programming is having mastery in the assigned industry area, and be able to understand the workflow and problems that arise. It doesn’t matter if it’s in BASIC, DOS batch files, dBase, rBase, Lotus 123 Macros, Prolog, RPG, COBOL, HTML, Lotus Notes, Netware, Visual Basic, Excel, Access, Word, IBM MVS, Oracle, SAP, .NET, Java, JavaScript, SalesForce, or Python (the latest for me), the coding environment is the easiest thing to absorb. The challenge is to understand how people work, what the managers want to see, and maximizing the bottom line. Seeing the big picture interact with the minute details is a skill that develops with time and experience. Being curious about everything and willing to explore from the backend to the final expectation is daunting and fantastically rewarding.
"What benefit does refactoring have to the end user?"
The benefit is that refactoring improves code quality and reduces complexity, which in turn makes maintenance easier, which means more features and bugfixes come sooner rather than later. More time polishing the code now = less time fighting with it later = more time to develop = better user experience = loyalty = money.
You just gotta speak their language. It's not a "waste of company time". It's an "upfront investment".
> _"You just gotta speak their language. It's not a "waste of company time". It's an "upfront investment"."_
oh lololol. i knew you gotta speak their language, but didnt know what the proper term would have been (:
This video deserves way more views. Sharing it with all my friends!
When I took Com-Sci in university several projects were "build a program to do this simple thing - then implement in 4 different languages and at least 2 paradigms". You learn a lot when your designing some pseudocode planning to implement it in both a state machine as well as an imperative language.
Great! It is very important to highlight these differences. Congrats for the video.
a great programmer once told me that the difference between a good programmer and a great programmer is a good programmer can write a good programme in any language he knows whereas a great programmer can write a good programme in any language he doesn't know.
Very true
That is a great definition.
That's fucking stupid. How do you program in a language you literally don't know?
@@heinzriemann3213 if you understand the concepts of coding you will pretty much get any programs
@@maxpawa9282 so as a good c# programmer you will be able to write good programs in cobol? Or Haskell?
Yeah no dog.
WORDS ARE NOT ENOUGH TO EXPRESS MY GRATITUDE TOWARDS YOUR KINDNESS TO OUR FAMILY mr. WILLIAM DORSEY WE ALL SAY THANKS YOU VERY MUCH MAAM, your online classes are top notch and one of the best instructor out there…
God I’m taking discrete math rn and oh my god I finally understand how deep CS gets and how I’ve only scratched the surface
DO YOU USE CALCULUS?!
@@BVK_LMZ I didn’t use any calculus
@@messiahno2715 i HATE calculus
A bit late to your party. Agree with everything you said, just to add:
An extra skill required at the coding end, is coping with language version updates (incl. depricated commands), language bugs and resulting library incompatabilities. A special shout out to Python, thank you guys.
Isn't it the same? Here comes Aaron to make us think about it. Appreciate you my friend. See you soon!
thanks for the video! I did not realize there was a difference and was using the terms interchangeably.
As a computer science graduate, I would describe a programmer someone who writes code from the foundation up. The coder writes code in packets that already do the basics, or are built.
So programmer would be mutually exclusive with "OOP coding"
But a programmer uses syntax and compilers aswell. That's also prewritten. This makes no sense. By these standards, only bit-programming is done by programmers.
Short answer they’re the same. People just overthink things
Good points on bringing up what was taught in a CS curriculum. I kind of forget why some classes are there, usually none of these dots connect until you start your career. I feel that the label of a programmer or a coder is perceived similarly like a monkey that wrenches until something works. Engineers are seen as those who design systems for the longevity of software that will be used for years to come, the ability to implement that necessary code is just expected once the solution is well thought through after tons of planning.
In actuality, you should always design code for the long haul
I am learning front end.
Currently at the stage of my js part.
And I will, build my website.
One way or another.
Say there are thousands programmed algorithms to reduce my goals to nothing.
When I digress, I enjoy coding, and I enjoy getting progress in it.
Whatever will happen to me in the future, I will know something.
And only the moment I would want to add something to my website, I will hire a team of programmers to work for me.
Because in that time, I'll be succesful enterpreneur, with thousands and millions in his business which he created both by coding, and by growing as a person.
The terms "programming" and "coding" are often used interchangeably, but there is a subtle difference between the two.
"Coding" refers to the act of writing code, which involves using a programming language to create software or other applications. This can involve writing code from scratch, copying and pasting code snippets, or modifying existing code.
"Programming," on the other hand, refers to the broader process of designing and developing software. This includes tasks such as analyzing requirements, designing software architecture, testing, debugging, and maintaining code.
In other words, coding is a subset of programming, and it involves the actual writing of code. Programming, on the other hand, encompasses a wider range of tasks beyond just writing code, such as planning, analysis, and testing.
Both coding and programming are essential parts of software development, and both require knowledge of programming languages and software development concepts.
I know you have copied this from chat gpt
Coding is just a part of programming. Here's a simplified breakdown to clarify the relationship between the two:
Programming (The Bigger Picture)
Programming is the entire process of solving a problem using a computer.
It involves:
Understanding the Problem: Analyzing the requirements and constraints.
Designing a Solution: Creating algorithms and planning the structure of the software.
Coding: Writing the actual code to implement the solution.
Testing and Debugging: Ensuring the program works as intended and fixing issues.
Deploying and Maintaining: Running the software and updating it as needed.
Coding (A Subset of Programming)
Coding is one step in the programming process.
It focuses on writing the instructions in a specific programming language (e.g., Pascal, Python, Java).
It's about translating algorithms into machine-readable syntax.
Coding doesn't involve planning the solution, testing the program, or deploying the software-it’s only about writing the code.
Analogy
Think of programming as building a house:
Planning the house design (blueprints) = Algorithm creation and problem analysis.
Construction (laying bricks, wiring, plumbing) = Coding.
Inspecting the house and fixing issues = Testing and debugging.
Living in the house and maintaining it = Deployment and maintenance.
In this analogy, coding is like the construction work-important, but just one part of the entire process of building the house.
Conclusion
Coding is essential, but programming involves much more than just writing code. It’s about solving problems and creating complete, functional systems. Coding is the hands-on part of translating a planned solution into something the computer can execute.
As a senior fellow and someone that has programmed since 1980's i agree with your discussion and division and meaning. Very well presented, thank you.
The more I program, the more I think about going back to learning math. To be honest, I'm not too good at math, but programming makes me hunger for math. They really are logic bros.
I bloody hated maths in school
@@steve00alt70 vectors were my saviour when programming simple video games
This is just spectacular 🔥🔥🔥🔥
Nice clarification Broo... Lit 💥💥💥
Success is not final; failure is not fatal: it is the courage to continue that counts. Business opportunities are like buses, there’s always another one coming.
Talking about opportunities investing in crypto currency now should be in every wise individuals list. In two to three years time you might be estactic with the decision made today
It’s fortunate that many of us are still confused about crypto currency while others are busy earning from it
Is never stressful when you're guided by a pro
I remember friends calling me crazy when I started investing in bitcoin now I shut them up with my 4 figures weekly returns.
Thanks so much to Ma'am Diana Lucy for introducing and making me believe in crypto
you explained this very well and lucidly! Thank you
I'm been programming professionally for 20+ years and was doing it for 10-15 years before that as a hobby. There was a time years ago where I might have imagined making a distinction (but never did), back when HTML was new and consisted of little more than bold and anchor/link tags and so on. It was just a markup thing back in those days that anyone could learn and get pretty good at in a few days of playing around. At that time I would have been annoyed if people making web sites or using HTML or similar called themselves "programmers" or even "coders" because what they were doing wasn't really programming/writing code. "Coding" and "programming" were the same thing in my mind, so I'd have been annoyed with either term being used two or three decades ago to describe what most folks making web pages did: Writing HTML. If a non-tech person knew the word "code" I could describe myself as a "coder" so they'd understand more or less what I did. If they knew the word "programmer" then I could use that term.
I'm mainly a physics engine programmer so that kind of thing annoyed me back then. Your 10 year old writing web pages with HTML 1 was not a programmer/coder. Today with modern CSS and HTML and whatever else, I'm not so sure it would bother me like it would have back then. Those have loops and function calls and variable storage and everything else today as opposed to simple tags, much of the same stuff that a C++ programmer uses.
In practice today I've never seen any uproar. I primarily do remote game programming contract work for companies of all sizes. When I'm working with a new team I'll often ask if this or that person on the team is a programmer. The response is either "yes" which I take to mean that person writes C++/C# or similar code on the game engine, or it's "no, this person is a 3D artist or vehicle dynamics tuner" or what have you, but doesn't write code. I've never once had somebody respond with "no, person X is a coder, not a programmer" as though they were different things. If someone were to respond that way I'd ask for clarification because what I really want to know is if they are writing code in the game engine or not. If they are, they can call themselves either a programmer or a coder as far as I'm concerned. To my mind "coder" is just shorthand for "programmer." I use the terms interchangeably, as does every other programmer I've ever worked with.
I don't see how it helps anyone to make a distinction between the terms. You're either writing computer code in some programming language or you're not. One can argue over whether certain "languages" are programming languages or not, but calling somebody who's writing in a language that isn't a programming language (hard for me to think of one these days) probably shouldn't be called either term. If you're programming, you're writing code, so either term applies.
it is still the same. In German e.g. coding and programming translate into "Programmierung". Maybe he talks about "scripting". What in some form is also programming/coding. Maybe he needed an excuse to make a video. And we watched it.
Great feedback and insight. 👍👏🏾
You barley blink bro lol actually intriguing
Discrete math is not specifically for programming and neither is it "often" or "frequently" the case.
"Math the logic branch and programming the applied branch." Bruh, not even close to true. You're missing a few branches in that binary tree
Someone doesn't know their set theory and it shows.
I'm a software engineer lead, and those are decently synonyms in practice; they should not be separated based on those made up categories, that's just complicating stuff. Css and html bacaue they are not logical language, they are just more advanced version of something like markdown.
This video should be 5 seconds long because: THERE IS NO DIFFERENCE!
it shouldint even be a video lol
Great video! Thank you 🙏
2:07
Says C and shows CSharp. Maybe he meant Java? 😅
Or he can just ‘go’ away
Short to the point but long in informative key factors concerning the subject matter. Great video. THANK YOU
Excellent. Thank you for tackling on this. Programming is a set of mind, which though can and should be trained. Coding is a tool. Learning coding does not necessarily make one into a programmer, whereas to become a programmer coding is a must.
This was extremely helpful. Thank you Aaron.
I can tell you put a lot of effort into this video, but please don't use your influence to spread misinformation. 'coding' is just an informal synonym for programming. They are the same thing.
en.wikipedia.org/wiki/Computer_programming
Calling this video "misinformation" is rude enough considering the words have different meanings for different people, but if you do so, don't disagree with wikipedia, at the very least.
@@frodeflem9353 The reason why I'm calling this misinformation is because it's 99% semantics that would just confuse people who want to get into the software industry. There are some truths to what he says, but it just doesn't matter. People who are just starting to learn how to write code easily get caught in unnecessary details and it can be quite overwhelming at first.
Maybe I exaggerated a bit calling this misinformation, but I'm afraid making a dedicated video about the semantical difference between coding and programming will do more harm than good. I haven't seen other videos this guy makes, maybe he gives really good advice in his other videos.
Your video's got a lot better! light, crips and clear. Keep it up, big fan from Belgium :)
I decided @30 to disagree. It's silly to compare synonyms and say there is a difference. Coding is used as a slangish synonym for programming. There may be different connotations among certain groups, but certainly no different meaning. That is unless you can code up a program without using any code (?) or committing any action that will in any way utilize any sort of programming code. Perhaps you're an architect and actually writing any programs is far beneath you -- Are you a programmer ? Shut the front door.
Amazing. Clean, fun to watch and SO educational. Great job! Thanks you so much!!!!
Thank you!
YAY, I've been programming all along.
2:40 wait what is doctype declaration doing over there
😂😂 that's funny
html>html>;
Thanks! Gam Dev is a whole different multiverse to me. Subbed a couple days ago and found it more than helpful.
3:14 very relatable 😂😂. I wanted to learn Java first but saw this super long code. You need to write a code of 3 lines to print 2 words and I immediately quitted Java and now I'm learning Python 😂
Lol we need an update did you complete Python?
Tom DeLonge
The distinction I have always made between the 2 terms is that coding is the understanding and implementation of general programming language syntax, while programming is the full implementation of a language or system to create a fully functional and self-contained application. Anyone can learn to code on some level of functionality, but few of them can write a program.
If someone tells me they are a coder, I roll my eyes and think, "right, who isn't nowadays"? They can write a for loop and parse a text file into an array.
If someone tells me they are a programmer, I stand aside with respect, for they create the systems that make our world function.
Notice in the speeches of local politicians and education officials, they implore us that "everyone should learn to code". They never say, "everyone should learn to program".
Me who didn’t know there was a difference
This changes my life. I found my calling, Hurray!!!
The reason to teach different parts of programming in different languages is so you learn the concept rather than syntax. Like, instead of learning how to write a do while in php, you learn what the while loop does, why to use it. So if you understand iterating through an array, you will know when to look up the exact syntax for whatever language you're working in at that moment because now you know that's the structure or method you need to use rather than memorizing a string of commands specific to a language.
I will like to start learning programming. But I don't know how. Please can you guard me on this.
I'm a game dev and let's just say
You need code to create a program
When will your bootcamp starts?
coding: The implementation of functions using written instructions to a computer.
programming: THe design of a function or set of functions to achieve a desired set of results.
mathematics: When used correctly it can provide the paths to the most effective results sets. In production, it may be used to predict performance, assess performance, evaluate usage patterns and computing resource capacity needs.
In IT these skill sets are expected to exist in each IT employee in varying degrees of expertise. If system analysis and design are implemented well they can produce and use reusable code that can greatly reduce time to production for future systems and functions. I like the phrase "write once, use many".
"That is super long", just like everything on java programmers.
Super helpful. Thank you so much!
Programming vs coding vs stackoverflowing
You make so much sense out of the complexities of it all, thank you homie💯👌🏾
💪🏼🙏🏼