Is that cost money?

If you appreciate this education, please think about going to Eli the computer guy dot com and offering a one time or monthly recurring donation.

Welcome back.

As you know, I am Eli the computer guy, and in today's class, I'm going to give you an overview of the track for programming and four coding.

So a lot of people out there nowadays, they hear programming.

They hear coding is the way to make money, which is absolutely 100% true.

But they're a little bit confused about what the field looks like when we're talking about coding.

We're talking about programming.

What are we talking about and how do you get involved with it?

So that's what we're going to be talking about in today's class.

So the first thing that we need to talk about is the basic idea of what is coding.

What is programming now?

Essentially, when we talk about coding and we talk about programming, those are words that can be flip flopped around.

So somebody who's doing coding is doing programming and someone was doing program, and he's doing coding in some instances, it might be a little bit more specialized in that.

But basically programming and coding whenever you're talking about this a coder or a programmer, more or less is synonymous s.

So the first thing that we need to talk about is basically, what are you doing when you're programming or when you were coding?

All you are doing when you're a programming when you're coding is you are telling a computer what to do, right?

So basically what you're doing is you're writing out instructions to tell a computer or what to dio in specific circumstances.

So if somebody clicks a button, you want an email to fire off or you want an A T v A C system to turn on or you want a document to be printed.

If somebody goes and opens up your particular piece of software, you want to tell the computer how that software should operate.

You're going to code that software.

So a very simple application that you may create is something like a basic calculator, right?

Somebody types in numbers they type in an operator operator will be a positive ah, plus side negative sign divided by or multiply so you type in a number you know to you type in plus two, you hit equal, and then you want your little application to add those +22 numbers together and pop out for two plus two equals four right on.

And so that is where you're going to write out how you want that to function.

You may may think about a more complicated piece of software that you may write seconds a piece of invoicing software where the invoices offer actually looks a lot like that calculator that we just talked about.

So what you do is you put in the different items that you have in your inventory.

Eso, maybe a calculator cost $2 a pencil cost $1 a pad of paper cost $3.

So if somebody comes in the store and they purchased three calculators and two pencils and a couple of pads of paper, what can happen is basically you type into the computer or you select and the computer that these items are being purchased, and then this invoicing piece of software will then figure out what the quantity is.

Figure out what the price is in the system they create a total print everything out so the customer could see it on.

Then you can actually take money from the customer and say that the invoice has been paid for beyond that, when we start talking about Cody and programming, something that I get very interested in is you can start doing things where you can start manipulating systems within your environment.

So so, one of things I like to play with a lot nowadays is our Guido's right.

So are, we knows are these little.

They're called micro controllers.

And so with these micro controllers, what you can do is you can add sensors.

He's microcontroller, so you can add temperature sensors, light sensors, motion sensors just about any sense, or you can think about.

You can add when he's microcontrollers on.

Then what you could do is you can write code for these micro controllers that say, When this sensor senses X, y or Z, then I want an output toe happen.

All right, so let's say one of the one of the projects that I do a lot for real.

I think you did not come as I use a lot of the temperature sensors basically little temperature demonstrations.

So basically what you can say is if the temperature gets above a Sergent degree.

So if the temperature, let's say, gets above 90 degrees Fahrenheit, turn on a red led Adel's you doing else?

Uh, so, basically, if it's under 90 degrees Fahrenheit, turn on a green led.

So basically, if the temperature is too high, the light is red.

If the temperature is too low, there is lower than being too high.

The light is green to tell you how the temperature is.

You can also do things again.

With code is you could actually fire off things in order to have things that his notification email sent.

How so?

If the temperature goes above 90 degrees Fahrenheit, turn on the red led and send an e mail to whoever the administrator is right.

So basically what you're doing is you're typing out all of these commands.

You will learn about this later.

Someone called If L statements.

Basically, if this condition is true, do this else do something else.

And the cool part is is you can do a lot of interesting things with coding in ways that you previously couldn't so a lot of you out there maybe thinking, Hey, you know, I've been watching Eli the computer guy for a long time.

He's done some coding videos.

He's done some coding classes in the past, but he has not been a big program.

Has kind of been a bit a little poo poo on the programming thing.

Really?

If you've been watching my videos over the past 10 years, why why is he getting into programming now?

Why is he starting to talk more about Cody now when he didn't really talk a lot about in the past?

Well, one of things to to realize is in the technology field, everything evolves.

Everything is right.

So I got into I t basically I t like M c s C type stuff about 20 years ago.

And so 20 years ago, what you had is you had the system's folks, right?

You have the M.

C.

S C, the list, Lennox system administrators, and maybe the Cisco people.

Right?

And they were over here, and then you had the developers and they were over here.

So basically, if your systems person, if you're in M.

C s see something like that, you took whatever the developers gave you.

However, itwas whatever condition it was another quality awas.

And then you trying to implement it into the real world on the reality is basically there was a massive big wall between the developers and the the operations people.

Basically, I t So the help desk people, the desktop support people, the systems people, right?

There was a big wall.

Even if your company had developers, right?

Basically, they had in house developers.

Chances were the operations people.

The anti people had no idea who the hell those developers even war like.

It is really hard to explain 20 years ago how remarkable wall there was between the developers and the operations people.

Basically, the developers handed you a product.

And as an I t person, it's right to make the dampening work right.

Well, the thing is, time has gone by.

Things have cake, and the way that we do Architecture now has changed.

So back in the old days, we had something that was called a client server architecture.

So you had servers and servers or things like exchange servers, Web servers.

That's a SharePoint servers.

Whatever else, basically is a computer that was dedicated to providing service is to client computers.

And then you had the quiet computers would have, let's say, a Windows NT server, and then you have a windows in T workstation, right?

And in that environment, the server had specialized software installed on it.

So you had a server that had an operating system that had specialized software installed on it.

It had all the configurations for how it was supposed to provide.

Service is to the client computers and then the client computers that they would have the operating system.

They would have their client software installed on it, and then they would have the configuration to connect to the servers.

Right?

So that's basically how things were before.

And so the developers, the programmers, the coders, and they would develop server software clients off, or whatever else they would pass it over the wall.

We would get it.

We're looking the instructions.

We'd scream way, do a lot of screaming, and then we would try to deploy it into the world, right?

But important thing to understand about the client server architectures again.

This that was a service to the active directory server.

You knew the physical box Active director was running on the exchange server.

You knew the physical box, the email server.

The exchange was running right.

You knew everything you could touch everything.

The server and the service is that that serve was providing everything was one box that the system's folks were responsible for.

Right?

And so one of the big things with I t back in the day is when the developers passed over product to to the operations people to the I t people.

We just kind of had a deal with whatever crap that we were given.

A lot of times, it was crap.

Well, now we have gone to something called a service oriented architectural or even a server Olis architecture.

So now, instead of I t people having to focus specifically on specific machines So this is a server with a hardware with an operating system with the software installed on it with all the configurations.

Now we're just dealing with service is so something about things like box thing to think about things like email service is now, like with female, right?

So with the email, I know my company is uses dream moments in here.

Oh, see this function right here?

I get where you're going with this function, but for us in our environment, this is how we would prefer to solve.

The problem is a lot easier for them to go in and basically proof.

Read the code that you've written versus step by step.

Okay, you need you need to create these variables and you need to use these specific functions and then this.

If, right, if I have to explain all that to you, they literally might as well write the code themselves.

So what these folks are saying is they want to see what projects you've done, whether their projects.

Four businesses.

What projects?

You can talk about four businesses, whether the projects for non profits or whether they're your own projects.

Right.

So if you're going out there, you see something interest you're like, huh?

You know, I wonder if I could create an application that would do X, y or Z.

That's the type of thing that they want to see.

They want to see your own motivation and that you're actually doing projects and things on your own.

I was talking with a recruiter one time when he said that was one of worst problems of boot camps with the first problem of boot camp, He said, Get up, get up is a place where you can put all your codes.

You're doing projects you put all your stuff on to get, huh?

Basically do collaboration, that type of thing.

They said one of biggest problems with a lot of the people that he was dealing with is that while they were in the boot camp, they were posting all this stuff to get hub.

And then you can literally tell that they they graduated from boot camp because that's when there was nothing else.

Right?

And so again, think about it.

If you're if you're a boss, if you remanded here, if you're gonna be hiring coders, right, do you Do you want to hire somebody that only does work while they're in boot camp and then does literally nothing else afterwards?

Or do you want somebody that goes through and again every every couple of days, every week?

They're adding to get help there, adding to their little projects.

They're they're they're learning how to do new things.

You go.

Okay.

This person is actually interested in it.

This person has the mindset to be able to see a problem, to be able to try to figure out a solution for the problem and then try to be able to implement that solution.

So that's the types of things that these owners, the recruiters, the CEOs and suck that they're actually looking for is there.

They're not looking specifically for the certifications.

They're not even specifically looking for the degrees.

For the most part, they're looking for people that are actually out there using code to solve problems.

And so it's very important, even if you don't have a job, even if you don't have, you know, going through college or anything like that actually create applications.

If you're If you're learning swift, right?

So swift is for Iowa, since for iPhones ipads, that type of thing actually create APS.

Don't just learn it, create APS.

Try to get it on to the Apple store so that it could be downloaded by other people so that these people that are hiring could say, OK, this person is motivated enough.

They're interested enough.

They're actually able to solve problems that they see.

This is somebody that I can teach to do something valuable.

So that's when the final things you need to be thinking about is that again with code.

It's not simply about understanding that having a technical ability to do code is that you're actually motivated, self motivated to go out there and do it on your own.

So there you go.

That was just a little class for some of the things that you need to be thinking about.

If you want to learn how to program, learn how to code, especially if you want to do this professionally again.

A big problem in the real world is you have a lot of these news that basically say I want to do computers.

They have no idea what that actually means.

And again, if you if you don't really understand what's going on, it's a little bit complicated.

Toe learn what's happening again.

One of the important things that I would say if you were a systems administrator against this ad man, you do Lennox, even if you do things like networking, Cody now is Maur important than ever.