Now, keep in mind that this is not a detour on python the language yourself.

It is a tutorial on how to learn.

So Step Zero is to get yourself a cup of water, say tea or coffee.

Find yourself a quiet place to work and the gulf?

This is such that you can actually sit down and read a python tutorial.

The next thing you wanna do is start searching up python tutorial and check out the first few top results on any search engine of your choice.

You can use Google search, Yahoo search or being searched, and those are just some of the more popular ones that you can use on your path to learning by now.

Unbeknownst to you, you've already messed up at this point because the fact is, you don't actually want to be looking at Python tutorials.

And let me tell you what we'll that found for myself is language tutorials are actually pretty useless because they always covered the same material.

It's always the hello world that maybe a to do list that may be a calculator app or something like that, but you keep doing the same to tour is over and over, and you have tons of gaps in your knowledge.

Each to tour covers, a few basics, a few things you've never heard of.

And you just keep doing to Touro after two Toro and you never push very far because each tutorial assumes that you have zero knowledge at the beginning and you never get very deep into the language.

And what you find after doing 10 2030 tutorials is you've made very little progress.

You still feel that there's tons of gaps in your knowledge, and you've made no progress in your mind.

You can't really do anything more beyond that simple hello world app or to do this.

That or something like that.

The other thing that I'm a little bit confused about is why are you watching this video when there is a complete python tutorial on the official python website, and that's what I really recommend that you check out if you go to the official platform website.

There's a very good tutorial there, and they cover all of the material from start to finish and all you have to do is just plow through that material chapter by chapter.

And it's really like a book.

And when you finish the book, you know, I hope so.

What's so hard about that?

You can read the book right and generally is going to be in every language.

Authors best interest to make sure that their language is used by as many people as they can.

So usually they invest in creating very good tutorials.

Quick start guides documentation to get people all set up so that they can actually use the languages.

Pathan has been around for a while.

At their tutorial, I found this pretty well fleshed out.

You can go there with very little requisite knowledge and just go through each chapter until you get to the end and the great and bother is each chapter.

You go deeper and deeper into the language.

You learn more and more.

And what I really like about in the official language bed is that you have no gaps in your knowledge.

When you finish the official guide, you'll have known everything, and nothing will look mysterious to you anymore.

At that point, you begin to build your confidence in the language.

But let me tell you that very few people actually know python entirely.

Most people know bits and pieces of the language.

So the way I would do this is I would first read through the first few chapters of dictatorial where they cover the basics and fundamentals and make sure that I know that once they get into the more advanced topics, like, say, network security, encryption, connecting today the bases and things like that, these are areas that you may not need to know Right now.

You may not need to ever know, and you can quickly skim through those chapters.

What I like to do is make sure that I at least have a broad understanding of what language has to offer.

I may not look into it too deeply, but it helps if I can de mystify areas of the language such that I know.

Okay, I've seen this happen before.

This was a language feature, and that just helps me have a better understanding of what language is able to provide me.

So what I like to do when I learn a new language and I've learned like a dozen languages by now is I would usually get a complete guide, and I like the official guides, and I will go through the whole thing.

I will read through the first few chapters in very close detail and once again to the events ever is.

I would just probably skin those now.

The other thing you want, make sure you understand, is why are you learning python?

And if it's really something that you want to be learning, I might remind you that there are a few popular tracks and programming.

Python is generally on the back, and service is where you work on the A P I connecting to the day, the base calculating and few results and returning it to the front.

There's also the front in folks who may be working on mobile like IOS Android, or they could be doing JavaScript and HTML, and you may want to understand which area of peace you want to get into.

Because sure, you can do full stack engineering where you're working on both the back and the front then, and that's really great.

But if you're just getting started, you may want to pick a specific track and, you know, I just wanted to let you know that there's other tracks besides just Python.

Like I would say, I was where you work on Swift or Android with Coughlin or Job.

Those are also great tracks, really.

The whole Java script track isn't too bad either, and that has the benefit of being very easy to learn.

And most people eventually need to learn some form of draft script anyway.

And it comes in handy in various areas of mobile development as well.

So if you're intent on their name Python, I'll keep in mind that every language you will eventually forget.

You know, I learned swift and I forgot it because I didn't use it very often.

So you need to have a clear understanding of what you're go is when you learn python.

And I would say that for most people there's a few different goals when this, maybe you want a job.

If you want a job, then your goal should be to create a demo project, something that could go on your resume that you can talk about in an interview.

So that would be your ago for other people.

Maybe they just want to have a brief understanding of python, but they don't really care about getting a job and then necessarily, and you know that may steer their direction a little bit differently.

But you need to understand that every language is constantly changing.

They're always pushing out new frameworks, new versions of the language.

And no one really ever knows the full language.

I would say that probably most Python developers only knows half the language features or so, and that's enough to get them really going.

And the other half they kind of have some broad understanding of how the reference and look it up.

But you know, they may not know off the top of the head.

How could do encryption, security, networking, database connections, things like that.

So people generally pick and choose and learn just parts of a language that they need to know to get a specific task done.

I would also say that as you're learning, pattern is going to be very important to have a creative outlet.

If all you're doing is writing Python scripts on the terminal, that's not something that you can really show to your friends.

It's not something that's all that useful, and I have a feeling that after a while you're going to lose interest in it because it's not going to be very useful at all for anybody, and you can't show anyone.

So if I were you, I might think about getting some sort of Web pages set up that can connect to the python back and a P.

I calculate something at them, return that result for the front end to display.

That's pretty fun.

And that's something that you can show the people you can show to your friends.

You can put on your resume.

You can show your employer, and it's also fun enough to keep you motivated such that you can keep going.

So you might feel like to do list, but it wouldn't be accessed through the terminal.

It would actually be usable through a Web page, and it would be pretty neat to see that.

So thinking about it this way, there are a few things you might want to think about getting set up for yourself.

One is getting a Web server set up, and there are a few service is that offer this personally, I you softly and they have a paper you set up.

There's also others like I've heard good things about the ocean and I've used Google Compute Engine myself, which also has a free service here.

If you use one that their smallest server configurations Once you get Web Server set up, you're gonna want to learn a little bit of HTML CSS JavaScript such that you can use this for them.

What project Now when it comes to set up a Web server, Python offers a few different frameworks.

Two of the most popular are jango and flask, and I might recommend chicken flask first because it's simpler.

Some people might recommend Django, which is good, too.

I think Jango requires a little bit more programming, background and knowledge to get set up and going, so if you feel pretty comfortable in programming, you can choose either framework.

But I might recommend flask for the beginners out there.

These Web server frameworks.

What they generally do is make a such that you can access the website and they would hate your python scripts.

Your path on program can return some text that can then be displayed on some Web page.

Once you have this set up, you can pretty much find yourself a full stack developer because then you have the front end, which is HTML javascript, C.

S s.

Or if you're using mobile, might be android or IOS, and then you can connect that threw that back and using the Web server framework.

The next step after that might be the Consider getting a database system like my sequel set up, such that you can actually store information by user and return that.

But as you're getting started, you may not even need a complete database system set up like you could just rent two files and read from files.

And that's a simple way to save and restore information as you're getting all set up and started.

I think if you were to follow the steps, it would get you well on your way to learning Python.

So let me just summarize for you the key steps that I might take.

The first is to go through the official Patan tutorial guy.

They have a very good reference there.

It's a black reading a book, and you could go through the first few chapters and this came through the rest The next step is to set up a basic Web server, use either Google compute engine, soft layer or digital ocean or something like that.

Maybe Amazon Web service is, and then get a simple website going this Web server with act like a creative outlet for your work.

I might also mention that for me at least, I would never try to learn a language through watching the deals.

I think that's a pretty slow way to learn things.

I really like reading materials because it's fast absorb knowledge, and I could jump around as I need to after that.

Optionally.

If you want to, you can set up a day the base system, like my sequel, such that your website service just has a little bit more functionality with allowed to save data and restore that data.

So there you go.