 What's up team? It is your biggest fan, the real Casadero. And in this video, we're talking about programming language is what is a programming language? Like, like exactly what is a programming language? I believe this knowledge, this knowledge is going to help a lot of people, a lot of people begin their journey into code because now they're going to have some understanding. And hopefully this philosophy will make you think about computers and programming in a whole different way. But where it doesn't seem so complex like you can't learn it, like it's just impossible. Like you have to come from a certain background and be raised by a certain family and go to a certain school. And you have to have these certain habits and all these things. The only habits we need in order to be successful, whatever successful is to achieve the things that we want to achieve is we have to have perseverance and that's pretty much it. But anyway team, let's get to it. This is what programming is. This is what programming languages are. Alright team, so let's break this down super, super, super duper simple, super duper simple, simple, simple. We're not going to go through the whole history of computing, but at some point we arrived in a place where we decided that in order to make computers do what we needed to do, all we needed to do was control an electrical pulse. Voltage, no voltage. Alive or dead and that created a one or zero in computer code. Well, in order to write a program, like let's just think about it this way. Let's think about it this way, right? The smallest possible piece of information that we can give to a computer is a bit. A byte is composed of eight bits. A character is composed of bits and eight bits make a byte. A character of one character like the letter A, B, C, D, E, F, G is one byte. So if we have a word, like a word that consists of five letters, that word could be five bytes. Now that word can get bigger because we can add metadata to it that tells whatever programming language that we're using that, hey, this thing right here that we're going to put in memory. This is a word. This thing right here that we're going to use in this computation. This is a word or this is a number. This is whatever. But that's what it all boils down to. Well, this meant that if we wanted to write one letter because one letter is eight bits, which makes up a byte to write one letter, we'd have to write a series of ones and zeros. And depending on how we wrote that series would determine what letter it was. Well, imagine if you wanted to write a word, it would take you a long time because you got to do this math, right to figure out these ones and zeros. And if you wanted to write a sense, it got even worse if you want to write a whole book. Oh my gosh, it got crazy. Now, if you go into like mathematical calculations or special characters, punctuations, emojis, all this stuff, it gets like stupid complicated. It's insane. So at one point, somebody said, hey, we can abstract all this stuff away, right? Well, if we we if we can come up with a language to keep us from writing these ones and zeros, we'd be cool. And that language is called machine code or machine machine language machine code. This is just a step up from binary. All this stuff that I'm talking about here, you can just go out and Google it. I'm not going to like dig super deep into it in this particular video. But by the end, you're going to understand exactly what the hell I'm talking about. You're going to understand how to put programs together. So let's carry on. So we've got this machine code, which is which is hex still complicated. But now instead of writing, you know, eight ones and zeros, maybe we just write, you know, two or three regular letters that we understand a O, E and what I don't know what that is in hex code. But this would evaluate to something in binary, which would evaluate to a letter or number or whatever. Well, somebody said, hey, man, you know, that's kind of hard, right? This is this is difficult. I want to write a program. If you know, this is way easier than the writing ones zeros, but it could be better. What if we just talk to the computer like we would talk to a computer? Well, mean, you know, just based on the format that we're using right now, this whole YouTube format, that sometimes people say things and they are misinterpreted. This is this is the whole source of the news today. People taking what other people say out of context and just making it all kinds of crazy. So if we try to talk to computers like this the same way I'm talking to you right now, it would not work. Computers are just not smart enough. One day they will be. I don't know what day that'll be. It could be tomorrow. Maybe they are already that smart. We just don't know. I'm sure Google and Microsoft and Amazon and Facebook, all these people are working on ways. So we can just talk. I could just talk to a computer like I'm talking right now and the computer go, OK, let's build something and do something. But as it stands right now, we are not quite there in even. This is what's crazy for us to even get there. We have to write a bunch of code and a bunch of software to do it. So the next best thing to being able to speak a regular language, but not having to write ones and zeros or hex code. It's like this random, you know, series of cryptographic craziness. We came over programming languages inside of the programming language. There's mechanisms to help us do this stuff, right? We can say, hey, put a quote here, type our word, put a quote here and that makes it a string and the computer knows it's a word, but not right away. So what happens is we take all of the thoughts in our head, all of the commands we want to give to a computer and we write them down in the olden days. People used to write this stuff on a piece of paper. Now we just write it inside of the computer. The really good programmers, the really good coders, they still write this stuff on paper. It may not be written out exactly the way it's going to go into the computer, but they have some sort of flow, some sort of diagram that they're going to use that gives them a roadmap to follow while they're trying to translate this into a language that the computer can understand. So we go on to the computer, we open up a text document, we type everything in and we save it. Plain text document, nothing fancy about this. If you don't know what a plain text document is and you want to learn the code, just go to Google, type in plain text and you can learn all about plain text. I wouldn't go too deep. Just know that it is the most basic document you can have. It has no special formatting or anything. What we put in a plain text document is what is read from the plain text document. So we write all of our source code in plain text. Now we may use an editor for this, the editor or add features like different colors and all kinds of stuff. But at the end of the day, it's just the text editor that adds some extra stuff. All the text that we write in there, it's just plain text. It's just regular old text. That text document is then either fed into a piece of software or read by a piece of software. That piece of software is typically written in some other programming language. Most of the time it's written in C because C is a low level language. We can use it on most computers, but it's high enough for regular people to understand so we don't have to write binary. But before the compiler could exist, someone had to write the compiler using either binary or hexadecimal or machine code or whatever it is, right? So the compiler, the original compiler was not written in the same way that we see now. So those people who wrote those compilers, they'd be like, yo, these people don't know nothing about programming. And that's just the way it just is just the way it is, right? Doesn't mean we're dumb or less smart or whatever. Just means that they've done the workforce because they love us and they care about us and they don't want us to struggle into the future. So we've got this program called the compiler and what it does is it reads our text. Our text file is just instructions to another piece of software. And that piece of software sits on top of an operating system. That software talks to the operating system and the operating system talks to the hardware. Talks to the computer monitor and the printer, the fax machine, the headphone, talks to all that stuff. We don't have to think about it. When we go to write a program, we'd have to go sh**, man. I got to write some sound drivers so people can hear. I got to write some video drivers so people can see. I got to write some printer drivers so people can print. I got to write freaking. I got to write. I got to write. I got to write f**king file control protocols so I can transfer this. We don't have to think about any of that stuff. It's built into the language and all of this goes to a text document and it's read by an interpreter or compiler. Now, each language has constructs and inside of those constructs, we're able to encapsulate blocks of instructions that say, do this particular thing. Let's say, for instance, we want to print something to the screen. In Python, we would write print, space, quotation mark, whatever, hello world, quotation mark. And that would be an actual program. When we feed this to the Python interpreter, and I talked about compilers before, the interpreter is just a think of it as a compiler that does it on the fly like we talked about this in another video. So anyway, the Python interpreter reads these instructions, right? In this case, the instructions is print. When the interpreter reads, this says, okay, hey, here's the word print. We want to print this thing. The default for printing stuff is putting it on the screen. The interpreter is going to call the operating system and say, hey, we need to put some stuff on the screen. The operating system may say, where do you want to put it? Maybe the interpreter already knows where they're like, hey, we want to put this stuff on the screen inside of this window right here. The operating system goes, okay, cool. And it contacts the video card and whoever else it needs to do business with. Yo, take this information, put it on the screen. And then that thing puts it on the screen and it sends some other information back to us and says, yo, we wrote this on the screen. This is an error handling mechanism and beginning programmers. We don't see that typically too often because we haven't gotten to that point yet. Some people, some people never get to it, right? They'll be learning code for like 15 years and they'll like, they'll never even write an error handler. It just is what it is. I'm not saying that like you shouldn't or you should, you should understand all of this stuff if you want to go out and be a programmer, a software developer, a coder, all this stuff. You don't need to understand, like you don't have to master all of this stuff. There's no need to go out and get a degree and master all of this stuff. Just understand the very basics of it. Programs, programming languages, they're all just text documents that are being read by other programs. And those other programs are returning oftentimes information in that same format to be read by some other program or a human being. That is it team. That is how programming languages work. If you have any questions, concerns, complaints, whatever, let me know. Leave a comment in the notes below because there's a bunch of people out there who are like, I can't do this because it's too hard. I can't do this because I don't know where to start. I can't do this because of 101 other reasons. It's not that complex. I'm not a smart guy, right? I barely made it out of high school. I was in the army for 14, 15 years and I spent my time flying around the world setting up computer not even not even complex computer networks. People picture this stuff. They think it's so complex. It's not. It's not right. Once you do something over and over again, it just becomes inherent. You're like, oh, okay, I can figure this thing out and then you just do. And after you're doing it so long, what seems complex to other people is very simple to you. But I'm here to tell you it's not it's not that hard. It really isn't any anyone can learn this stuff in their spare time. You don't need a course. You don't need any. All you need is a book and a computer and the willingness to learn and the commitment to act. All right, team. Hey, by the way, before we go, if you would like a hat like this or a shirt like this, check out writecode drinkcoffee.com where I have swag to keep you motivated and inspired along your journey to becoming the person you want to become so you can do the things you want to do and live the life you want to live. You can also check out the code 365 startup lab. I've got a bunch of free courses introductory stuff on how to code. And as it stands right now, while I'm speaking to you, I am putting together a course. It's not the end all be all of all programming courses, right? I cover the fundamentals of web development and how to think about building your thing from beginning to end, right? And most people, most people are never going to go out and do this stuff. But the reason why I put it there is number one, so I can say I have it. And number two, if you want to support the channel, all you got to do is go over to code 365 startup lab, sign up for one of the paid courses and boom, your money goes to support the channel and I can keep producing that course. Or you can check out writecodedrinkcoffee.com where you can get some swag and merch. So you get something. I get something. It's a win-win situation. All right, team, that is it. I'm your biggest fan, The Real Cassadero. This one went a bit long. I'll try to edit it down as much as I can. But I look forward to seeing you in the next episode. Share, subscribe, like, leave a thumbs up. Hit the notification bell if you want to be notified when I upload new videos and I will see you next time where we're talking about code, tech, spiritual. I don't know, man. It doesn't, it doesn't even just go out there and win. You can do this. I know you can. I did. It's hard, but not as hard as we think.