So there are two topics that I would like to cover in this video and the 1st 1 being how tow, learn to code and kind of resource is to use and how to structure your learning and the second being how to start making money from it as fast as possible.

Okay, so this is my advice for anyone who wants to learn to code.

And the first step would be to try to figure out where you'd like to be working or what you'd like to be doing.

And the way that I do this is by going to a website called Stack Overflow.

And basically, there's a section on there if you go to stack overflow dot com slash jobs, where a lot of companies post different job offers and in this job off versus usually also a list of requirements for that position.

So basically, you could browse through that and see if you can find something that seems interesting and then go through the requirements, and that would be a really good starting point for, And even if you do that, I don't find anything.

Don't worry, because I personally, when I got started, didn't know what I wanted to do.

So I also cover, Of course how Tow.

Learn to code.

If you have no idea where you want to go, the next step would be to pick a programming language.

And basically, if you know where you want to work, then pick the most commonly used language in that area.

And if you don't know what that is, then go to a stack overflow again.

Just look at different, similar jobs on the requirements.

For those, try to see what the most commonly used languages and then pick that one learns that.

And if you don't know where you wanna go, then I would suggest learning job.

But I also want to add that it doesn't matter too much language of pick, because if you learn one language really well, then the concepts will transfer toe multiple of the languages and you'll be able to learn.

Our language is super easily, and this is because the steps to learning a programming language is gonna be the same across all languages.

And the way that I would suggest that this start by learning how to create variables and then learn about objects and then about methods.

And lastly, I'll look at some daughter structures like stacks of race and lists.

And I was just learning from a book because generally books are usually really well structured, and they're also compact and really cheap.

And personally, I think it's one of the best ways to learn, because they take you from point A to point B in a really clear way, which means that there's a clear starts and a clear finish.

And in my personal opinion, online courses are notice.

Great, because they kind of move a bit too quickly and skim over some of the fundamentals.

Which means that at the end of the course, it's kind of hard to keep up.

But maybe I've just tried.

The wrong course is, once you've learned the fundamentals of a programming language, you'll be more well equipped to learn other programming languages.

And you'll also be more efficient at finding answers to your questions, since you no more so they'll tow, ask better questions.

All right, so now we get into the making money part, and from now on, the making money and learning to code will be intertwined in this video.

So now, the next step would be to learn kit and how it works.

And for those of you who don't know get it's a version control system that pretty much all companies use when building software and you can think of this s a system that allows multiple developers to work on the same project at the same time.

So from this point forward, out suggests that every time you write a piece of code added to get up account and there are a couple really good reasons for this, so stick with me.

The first reason is that a lot of companies use it, and it's pretty much an industry standard, which means that at some point you're probably gonna have to learn it anyway.

And the second reason, and maybe the most important reason is that if I'm a recruiter and I go to your get up account, then straight away I get of you off all the public commits that you've made in the last year.

You can think of a commit as they say.

So I say off the code that you're currently working up.

So what does this mean?

Well, basically, it means to a recruiter.

They can see how often you coat and seeing someone get up that's covered in commits will basically ensure the recruiter that you actually do code a lot.

And you can probably imagine that to a recruiter that maybe never talked to you.

Never make you and I just read a short rest of May.

This would actually give them some sort of confidence that, at the very least, you know, get works.

And most likely you do coat a fair bit.

And this could be a huge advantage when applying for jobs and basically just link your get help account on your resume and they will see this.

All right, so now for the third step, and that would be to start working on personal projects by far the best way to learn to code is by working on a personal project, which is why I believe that you only need a very basic understanding of programming language toe be able to start on a personal project.

The reason that this is the third step ISS that I do believe you need some theory, not necessarily in order to be able to build something with code at all, but in orderto build something with coat relatively effectively.

So just having that basic, fundamental knowledge of a programming language will help you increase your efficiency when trying to Seoul different problems that you'll inevitably run into your personal problems.

Each personal project will do two things first that will show that you like to code and you like to do it in your spare time, which is really important a lot of employers and the second being that it will show kind of what you could do with code.

So maybe you build an app or maybe build a website.

Now the employer will be able to see that you know how to work with Web development and mobile development and maybe even implement some sort of specific feature that shows off a skill that you have.

And I think that once you have one or two projects, then you basically start applying for jobs.

And another suggestion would be to add your personal products to your leaked in profile, because a lot of employers will be looking at your LinkedIn profile and on there you can basically make kind of a nice display of all the difference projects that you've done and when starting to apply for jobs.

Just keep in mind that even though you may not have a lot of experience, there are a lot of jobs out there for software developers, even with limited experience, another piece of advice would be to ask different business owners.

So maybe a friend of yourselves, a business or family member, really anyone and see if you can.

They have a website that needs redesign.

Or maybe they don't have a website and they need a website, and basically you could build this for them, probably for free.

But if you can get paid for it, that's great.

But basically build the website and then you can add that to your estimate.

And you could say that I built this website for this company on dhe.

Here's how it looks, and this can also be very powerful when applying for jobs.

Or if you want to get into freelance work, then I would suggest, of course, doing the previous step as well.

But then go and post something on Facebook or Instagram Twitter and ask your friends and followers safe.

Anyone needs a website built or app and maybe you can start making some money that way.

And you could also go to websites like a freelancer dot com or work dot com.

And there are lots of different websites for this and get started that way.

All right, so that's my advice.

I hope you got some new ideas out of this on dhe.

That's it for this video.