I noticed the hollering for y'all but day of me recording this It is Halloween.

So they could I'd say that.

And welcome to computer science terminology part, too, if you didn't catch part one.

There it is right there.

That's where we went over a lot of the basics, and now we're getting a little bit more complex, starting off with machine language versus programming language.

In order to differentiate the two, you have to understand that computers and humans understand information and different formats whenever you save data such as a word document or a premier project.

The computer stores that in a format that don't understand, called binary or otherwise known as machine language, binary is a language made up of combinations of zeros and ones.

Each character that you'll see on your keyboard numbers, special characters, punctuation letters, spaces, tabs and everything in between as their own binary representation.

That means a combination of zeros and ones are different for each and every character.

And then there's something that I like to describe in a way that is between binary in our human language and that is asking code asking code is a numerical code.

But instead of having zeros and ones like binary or having the actual number of the actual letter like English, it picks two numbers zero through nine for a particular letter.

Doesn't matter if it's an A or B or C.

There are gonna be different, and they'll even be different from upper case to lower case letters.

But that format is also known to us as decimal format.

And since that is based 10 as you could see, because the two numbers are chosen between zero and nine, those Air 10 numbers I'm sure you can guess binary is based to.

That's because they choose only zero or one.

In all honesty, I'm not too sure how well that came across to you.

So let's try to consolidate our thoughts and really drive this point home.

And I think a real world example will do best.

So let's say we're typing something in Microsoft Word.

We type the letter a going to keep it real simple.

We typed the letter capital A.

The numerical value asking code of that is 65 I think.

Let me check.

Yeah, for capital A.

The numerical code is 65 when you save that data from your word document into your computer.

It saves the equivalent of 65 in binary for a computer, so basically you type in a capital.

A numerical code for that is 65 then there's a unique binary code that is the equivalent of a C code.

The numerical code 65 in the binary code of zeros and ones is what has saved into your computer and what your computer can read.

That's machine language it's also referred to as low level language, is considered to be low level because that's the language that machines can understand.

And programmers well, programmers understand programming languages, also known as high level languages.

And just like in English, we have a set of rules to follow and that his grammar everything that that entails a programming language has its own set of rules, called syntax.

It also has a set of define words or keywords, and these have a specific meaning within that programming language.

And unfortunately, humans have no idea how to choose one language or another.

So just like we have so many different spoken languages, we have also so many different programming languages Some are better suited for Web development, and even within what development, they're different languages to do exactly what you need.

Then they're different that build mobile applications.

And then there are different that build enterprise applications in their different that build a hacking software machine.

Learning or what have you?

You get the gist.

But in addition to those differences, we also split our programming languages into classifications called programming paradigms.

So if we look at the actual word paradigm, we see that that's, ah, way of thinking or way of doing something.

Essentially, it's just a mindset.

A programming paradigm is a way of classifying something based on the methodology of that programming language.

A few of the common types of program paradigms are functional, procedural, imperative and object oriented.

As an example, we have two programming languages.

Java and Seek.

However, Java is an object oriented programming language, while see is a procedural programming language.

And for now, we don't need to know what it means to classify a programming language as object oriented or procedural.

But it does help understanding that they're different classifications for different programming.

Languages now want to understanding, writing and saving code So basically, we've discussed this in part one of computer science terminology, which is that programming essentially means to write code.

That code is written to create a program.

A program is essentially an application, an application.

Does something.

Let's compare this to something a little bit more simple, like an essay.

So when you write an essay, you open a piece of software and application like Microsoft Word.

You create a file and Microsoft Word.

You type some stuff and then you save it as a document.

Or a Pdf writing code is essentially the same thing.

Instead of using Microsoft Word, you'll use any type of text editor whether there'd be no pad note, pad plus plus Adam so I can go on and on about this or some type of I D.

E.

And that is integrated development environment.

I D.

While a text editor is a hammer in your tool belt, and I D is essentially the tool belt that has all of the tools within that tool belt.

So and I d will have your text editor, a compiler, a runtime environment and ADA bugger.

So it has all the tools you need to create a proper program, and they do bugger very helpful.

It's a tool that programmers use to find mistakes in their coat, and mistakes in their code are called buck's.

Hence, debunker bugs can appear different times within the development process, whether that be preventing your code from compiling or preventing your program, your application from executing.

Or maybe your application is just doing something incorrectly.

There plenty of jokes that hop around the softer development industry, one of which, being something along the lines of, you know, I spend 10% of my time writing code in 90% of my time.

Debugging debugging is a skill that you will develop your whole entire life.

After you create your program, you save your code within a file.

This is also known as a source file, So instead of saving it as a document or a pdf, you save it as a source file.

This basically shows you that your source code is within this source file.

And just as you would save a pdf as name DOT extension, which is PDF, you would also save your source file as name dot extension, which your extension is, whatever your code is so dot Java is java dot CPP is C plus plus so on and so forth.

And after you save everything in the appropriate source files, you want to run your code to make sure that it works.

But before you can run your code or otherwise known as executing your code, you need to make sure that it compiles you're essentially translate your source file from high level language to low level language in the form of an executed ble.

So your computer knows what you wrote because, as we said before, computers don't understand high level English.

They only understand low level language.

So within that idea environment, you will use the compiler to compile your code.

And that is a process of translating from high level language to low level English.

Let me see that woman Compiling is a process of translating your high level language java c++ swift to low level language, binary machine language.

And in that compilation process, it creates and saves that translated code as an excusable file.

However, if you have bugs in your code that prevent you from compiling, that's when you need to activate the bugger, figure out how to fix your code, fix it until it is able to compile.

Otherwise, it won't be able to create that excusable file.

If it's not able to create the executable file, then you're not able to run your application.

And that is it for computer science terminology, Part two and actually the final part of this series that wasn't sure the beginning if I wanted to stretch it out to Part three, but turns out we were able to just fit into a two part Siri's hope you guys enjoyed.

If there's anything else that you want me to discuss, I'll be happy to just leave them down on the compass below.

If you like the video, be sure to like it.

And if you dislike it, feel free to dislike the video twice and make sure you subscribe, especially if you did like the video until next time.