I'm not doing this one in the car today because this is something I feel really passionate about, and I want to take it very seriously.

Today.

I'm gonna tell you my eight bits get it of advice for new programs.

Program is just starting out, and this is the stuff they roam.

Teacher in school.

I'm not going to talk about any language in particular because the real roots of being a great program is understanding the structure on the nature of code.

Everything else is just syntax and could be lent in days.

So let's get started.

Bit eight.

Don't make life hard for yourself.

Set yourself realistic expectations.

You're gonna have to learn to walk before you can run the first thing the program it should be learning about.

It is variables and arithmetic and then followed up with sequence and loops and a raise and then functions and then extend it with structures and classes on.

Then you can think about the more advanced stuff like object oriented programming inheritance polymorphism going further, still talking about template classes on pre processes stuff.

Then if you want to interact with anything, you're gonna have to learn libraries, You're gonna have to learn protocols.

Don't jump into the deep end.

Make sure you understand thoroughly the basics.

First.

You don't need to care that about what language you're using.

You understand the order of things.

You understand how the process is handling the data, and you understand how these tools these hardware till CP use and graphic scouts can be leveraged to your advantage.

So don't make the first thing that you write your ultimate ambition.

Start by doing little programs on route Learn things.

Don't say your expectations too high a start you still beginning.

It may be really tempting thing.

I'm going to go and write a computer game.

I'm going to create a massive, complicated Web structure for my website will be a bit more reasonable.

Why not start off with writing some little consul replication, simply really simple stuff and to your name, and it does funny things with the organization of the characters or its souls.

The arithmetic or it's a simple little game High Low is an excellent example for really starting up.

You're not going to be able to get very far if you try and jump in at the very deep end bit.

Seven.

Choose the right tools.

Choosing the right tools goes hand in hand with the language you want to use, but you're just starting out.

Don't start with really complicated compiler chains and make files.

Stick to the rapid application development environments.

Fully integrated stuff You want tools, which always edit the source.

Show you the compiler information.

See what it's doing if it is not a compile code.

If it's interpreted, you want to be able to step food line by line.

That means you also want you integrated development environment to have the really good debugging facilities.

You want to be ableto perhaps look a memory so you can see what's going on as your program is stepping through the loads of really good free development environments online.

But I would recommend you stay away from the ones that require you to compile them yourself.

Start off with something that really tightly integrated.

Find a nice execute herbal that will just click on wrong.

And most importantly, whatever the tool, make sure that you can run your program within seconds of finishing that last line of code.

You're learning you're going to want to run the program.

It doesn't do what you wanted to do.

You want edited ruinous again.

This this rapid turnaround time is great for giving satisfaction and free back bit.

Six.

Keep it fun once you have just off the ground and you familiar with some basic loops and things.

Try and like the programs that you want to write, but understand you're not going to write a Triple A title within a few days of starting to code.

If you want to write games, sat with a very small level game.

So do things like a Tetris clothes.

I'll be really good for teaching about algorithms and thinking about data.

If you're into music software, trying manipulating away for, load up a music file and see if he can understand how the file is structured, then had some crazy effects to it by playing with the maths.

If you're into sports is a hobby, why not write some applications that can keep track of scores or personal best something that you might actually consider using yourself?

It's not up to me to tell you what the program, but all I can say is just make sure that you enjoy doing it.

If it becomes a chore, it's probably gonna dissuade you from doing it.

And that's not what you want it all if you're just starting out.

Programming bit.

Five Practice When I was learning to code, the best way to practice was to create a whole program dedicated to learning one function.

When I was learning about loops, my program would contain four loops and wild leaps.

Always repeat until in those days, but, you know, break it up.

So you got a program that just contains a working luke, so it doesnt might just do something boring like add up all of the numbers between 100 on display.

But then you've always got a reference points later on, you can go back to that program and look, how did I do the loops that as your skill set developed, you'll have a whole library of little program is what she could label, and they can always use them as a reference.

But just remember, it takes time, and it takes efforts and it takes practice.

Don't try and write a program with Star, which has every single feature that that language might sell for.

You keep these little practice programs.

Simple and discreet.

They only do one thing, and one thing was to teach you how to code bit for never couldn't paste.

You're just starting out.

The worst thing you could be doing is going online, highlighting loaded code you've seen on a website and trying it for yourself.

That's very useful later on, but you're just starting out.

Get used to syntax by typing it out.

Get used to write in concise code rather than really the most code because it's less to type.

Get used to writing readable code.

Get in the habits off good variable naming conventions.

You won't be able to do any of this if all you're doing is cutting and pasting code from other people.

Write it yourself, even even if you're copying it from the website.

Trust me, it's the quickest way to learn that the nuances of the language bit.

Three.

Don't listen to people on the Internet.

Internet forms have a peculiar type of people, even though the Internet could be a really good source of information.

And I wish I had it when I was learning.

There were always people online who want to show how good they are really arrogant program is out there.

That's whenever a gully starting out is requesting for some help before and the first thing they get told.

If you do any wrong, you should be doing it like this.

That's not correct.

I don't want to use that technique.

How is this helpful for somebody just starting out?

If all he wanted to do was display your name on the screen that some guy on the Internet is yelling at you, telling you, using the wrong encoding format for your strings?

How's that gonna help?

Don't get me wrong is a lot of good advice to be found on the Internet and certainly don't shy away from asking people for help.

But just identify that there are people out there who see you as a threat.

The last thing they want is more coders in the world, and they also really need to show off just how good they are.

Don't let those morons ruin your day by making your little programs really overly complicated.

It only leads to confusion and frustration bit too.

Remember that the tools work for you and you can't hurt them.

This goes hand in hand with bet three.

Break the rules.

Use global variables all over the place.

Use unsafe system calls.

Don't check all of your introduced to make sure that within range, This is stuff that will not advise you to do at school.

But you know what?

It doesn't matter.

You're learning.

You're not gonna cause any harm.

You're not going to break your computer.

Mostly the computer doesn't have feelings.

You're not gonna upset it on your code.

Isn't being reviewed by somebody on the Internet?

Doesn't matter.

Do whatever you need to do to get the job done.

It'll be more satisfying and more rewarding on dhe.

You'll want to keep on with it over time.

You can learn that there are accepted standards that you should probably follow and good and good practice as well.

But don't swamp yourself with all of those concerns right at the beginning.

That will come with time.

And mostly it'll come through experience because you'll realize, Well, hang on.

I'm breaking the rules and I know what I'm doing now.

And all I'm doing is making life more difficult for myself.

That's fine when you're writing enterprise level code.

When you're just starting out.

It really doesn't matter.

Do what you want.

Get yourself into a real mess.

There's no greater mental challenge for a program than debugging stuff.

And if you want a career as a programmer, you're going to be debugging a lot of stuff so you could make it make a complete hash of everything.

Because if you can get yourself out of it, that journey will present its so much new learning Tiu.

And if you get really stuck, Selecta LL Dooley starts again.

It doesn't matter.

You're learning, and that leads me into a bit warm.

Get things wrong?

Absolutely.

The best way to learn is to make mistakes.

Don't worry about writing really complicated specifications and plans to start with.

Doesn't matter.

Final new start writing code gets stuck in Get things wrong.

Programming tools available today becoming so sophisticated they'll tell you is you typing in the code Whether something is right or wrong and you think, well, why is that wrong?

And it was over time it will become logical.

Oh, of course, that's wrong.

I understand now, once that's built in once that's in here, that's still never go away and you can use this talent that you developed for programming in any language.

So there you have it.

My eight bits of advice for new programmers.

If you're just starting out, I wish you the best of luck.

And I hope it becomes a happy hobby and possibly a career for you.

I don't know.

Just make sure that you're enjoying yourself, not demoralizing yourself.

If you found any of these tips controversial or helpful, I'd really like to know.

Leave a comment below.

If you've enjoyed this video, please check out my list.

Thanks.