So let me just quickly tell you a short story of kind of when I got started in programming and what happened to me when I got started, I lost motivation several times, and that kind of led me to quit several times.

And I just remember feeling like, completely overwhelmed by the sheer amount of stuff that I didn't know and that I knew I'd have to learn in order to be able to do this.

The thing is, I got started in the wrong end.

I tried to get a complex at built with absolutely zero programming knowledge.

At that point, I didn't even know what a variable Waas and I remember struggling so hard with just trying to understand a four loop.

And that was like one month into the build, working on the app like 8 to 10 hours per day.

So this might seem a little bit strange that I'd been programming for several weeks for, like, 10 hour days and still couldn't wrap my head around a four loop.

The reason I didn't understand it was because I'd spent, like, zero time learning the basics.

So essentially what I did during these 10 hour days was I watched tutorials, copied the code, pasted it in and then Googled the errors.

But when you have no understanding of the basics and tried to stitch together a complex piece of code, you'll have no clue what's going on.

And you're running too complex or like semi complex errors that even if you find the solution, you won't understand how to implement it.

Or at least that's what happened to me.

Actually remember one thing that I was struggling with a lot, which was like I'd spent, like, three weeks, I think, working on this and I was getting like, super frustrated super demotivated, and it was essentially trying to build some sort of like spreadsheet type you y.

That was similar to kind of what Excel looks like.

And I just spent, like, three weeks, 10 hour days.

I couldn't get it to work.

And that's something that today would take me, maybe like 30 minutes to d'oh!

And it's something that if I would have just spent a little bit of time learning like the fundamentals of programming, I would have saved so much time on this.

This video, sponsored by atlantic dot net atlantic dot net provides great VPs hosting, and they're offering a free one gig virtual server with SS Days and Bluff Storage for free for a year, plus $50 in free credits to use for other service is that they offer.

It's really easy to use.

And unlike many other big names in this industry, they have great, always available technical support and their support.

People actually worked there, so it's no outsourced.

And that's really valuable to me, especially when I'm coding late at night and I get stuck on some issue.

Then I want to be able thio, get in contact with support and just solve that problem as quickly as possible.

Try atlantic dot net to develop tests or launch your next projects.

So go to atlantic dot net slash cow and use the Cuban Code Cal with capital letters to get a $50 credit.

So in order to maintain motivation, it's important that you start in the right end.

I'm 100% for project based learning, so picking a project that your sighted about and then trying to build it, but and this is important, you need to learn the basics first and I'm just talking about spending an hour a day for just four weeks, learning the basics and then start your project.

So I'm in no way saying that it's impossible to start out that way by just building on a pout or I d out straight away.

But I do believe that it's a lot harder than it has to be.

And when it comes to programming, just a tiny bit of very basic knowledge will take you so far.

Make sure that you don't start like I did looking back at it, if I would have just spent a week or two reading a book like Java Head first before I started building my ass, I would have saved myself so much time and so many headaches.

My strategy, if I was trying to maintain motivation while learning how to code, would be to start out with some sort of book, because books are usually really well structured and you can kind of take them at your own pace.

I would do this.

Go with this books of job I had first, and that's because I have read this book and I know that it's really good.

It's really easy to read, and the explanations in this book works really well for me.

I understood them really easily, and before I read this book, I was kind of struggling with understanding what classes and objects were in programming.

But this book literally explained it in, like, two pages, and I understood it perfectly after that.

And, yeah, it's just a really good book.

So just reading some like this, even if you just read half of it, you will get a really good understanding of kind of the fundamentals of programming because it will give you the understanding that you need to be able to learn other frameworks or languages and to be able to solve other problems that you're running too.

So I would start with a book like this, and then after I read that, I then get started on a personal project that I'm really passionate about, because then I understand kind of fundamentals.

So when I run into errors or problems, I'm gonna be better or more well equipped to actually solve those problems faster.

So instead of wasting a ton of time because you don't understand some of the fundamentals, you'll kind of understand that, and you'll be able to solve the problems a lot better.

I also just wanted to touch on motivation.

I think a lot of people confuse motivation with excitement.

Being motivated to do something is not the same as being excited to do something.

Motivation is doing the things that you aren't excited about because it will get you to your goal.

You may be excited about coding on the project today, but that feeling may change tomorrow, and it's easy to do things that you're excited about.

The difficult part is forcing yourself to do the things that you really don't feel like because you know it will get you to go.

So don't look for the feeling of excitement about what you're going to do, because excitement is fleeting thing instead about why you're doing it in the first place.

So that's kind of my advice.

Don't let your first metaphorical climb be a Mount Everest, where you're going to try to send it barefoot and without oxygen, because then it'll get really easy to get discouraged and just give up and quit instead.

Spend a tiny bit of time just learning the very basics and then you'll go so far when it comes to programming.

All right, that's it for this one.

I hope you enjoyed it.

And I hope I'll see you in the next one.

By the way, did you see that giant dog run across the screen in the drone shot?

In the beginning, I mean, Oh, dear.