[00:00] When you first start learning to code, you learn about the This all seems fairly straightforward and you gain some confidence in your abilities, but as time goes on, you start trying to build your own projects, and
[00:14] The hardest part about learning how to code isn't actually writing To overcome this, people tend to go and search for tutorials to try and This could be to build a website or an API or maybe even a game. If they're lucky,
[00:30] they find exactly the right tutorial that matches a project that they want to build, A few superficial things like the colors or the layout. things that they don't understand.
[00:42] something's doing, but they just copy and paste the code and they tell After following the tutorial, they've got something that works and
[00:54] And then they pat themselves on the back. When they go to start a similar project, they get stuck cause they can't remember When they come to build their next project, this is what
[01:11] You can build out the tutorial, it works fine, but when you come to build You're in your own personal programming. The problem is, is instructors make everything look easy.
[01:24] built out the project themselves. They've got stuck, they've debugged it, and they've finally And it's that working solution that you're seeing during the tutorial.
[01:37] and failures that the instructor went through, and it's often those very failures that help you remember how to do something the next time you come to do it. tutorials so we can apply them to the next projects that we come to build?
[01:54] This was a skill that I learned when I was at university studying physics. When I was doing a-level physics, which I think is similar to AP courses in America, At the time, I thought that was impossible.
[02:06] How am I gonna learn 15 equations off the top of my head to be able to do the exams? Not only that, but I needed to know how to derive them from first principles.
[02:18] easier to learn and remember. The first principles were really just the 15 equations that I already knew, so I To get to the other equations, I had to understand how the
[02:31] Originally, I had to understand the meaning behind the equations. What I didn't understand at the time was that by understanding the meaning behind the equations, I was using different parts of my brain in order to remember them.
[02:43] the planets orbiting around stars, or the interaction between atoms. deck of cards in a certain order.
[02:55] The thing is, they don't just try and dryly remember the cards in order. room and assign different playing cards to different objects. have to mentally look around the room and recall what the card is.
[03:10] while you are trying to remember something. cards or a scientific equation. When you're following a tutorial, the key is to understand what each line of code is
[03:24] Then when you've worked out what that line of code is doing, write it down somewhere. If you're more of a visual person, how about you draw a diagram trying to
[03:36] It's the act of writing or drawing that is gonna help you use You don't wanna rely on tutorials to build out projects. It's fine to Google the syntax for things.
[03:51] Don't go searching for a solution straight away. struggle and overcoming those obstacles. When you manage to solve a problem yourself, it's gonna be a lot easier to
[04:06] If you like this video, then please hit the like button and Now, when you're learning to code, it's very common to feel like If you get this feeling and you feel like everyone else knows more
[04:19] Thank you for watching, and I'll see you in the next video.