Why You Really Struggle to Code
45sIt directly addresses a common frustration, creating immediate relatability and engagement.
▶ Play Clip"Delivers on the promise with a clear, actionable technique, though some parts feel padded with motivational filler."
The video addresses the common struggle of learning to code, emphasizing that the hardest part is not writing code but building projects independently. It critiques the tutorial-following approach, which often leads to a false sense of accomplishment, and introduces a memory technique based on understanding first principles, inspired by the author's physics background. The solution involves actively engaging with code by understanding each line, writing or drawing explanations, and practicing problem-solving without immediate reliance on tutorials.
When starting to learn coding, the basics seem straightforward, building confidence, but the real challenge emerges when trying to build personal projects.
The hardest part of learning to code is not writing code but building projects. People often search for tutorials to build websites, APIs, or games.
Finding the perfect tutorial leads to copying code without understanding, resulting in a working project but a lack of comprehension, leading to getting stuck on similar future projects.
Instructors present a polished, working solution, hiding the struggles and failures they encountered, which are often crucial for memory retention.
The author learned a skill in physics: memorizing 15 equations by understanding their derivations from first principles, which made learning easier and more memorable.
Understanding the meaning behind equations uses different parts of the brain, aiding memory, similar to how memory champions use visualization.
Memory champions don't dryly memorize; they assign cards to objects in a familiar room, using spatial memory to recall, a technique applicable to coding.
When following a tutorial, understand what each line of code does, write it down or draw a diagram, as the act of writing or drawing helps use different brain parts.
Don't rely on tutorials for projects; it's okay to Google syntax, but don't search for solutions immediately. Struggle and overcome obstacles to remember better.
It's common to feel like others know more, but with these techniques, you can improve. The video ends with a call to like and subscribe.
The key takeaway is to move beyond passive tutorial-following by actively engaging with code—understanding each line, writing or drawing explanations, and embracing struggle. This approach, rooted in memory techniques, helps retain knowledge and build projects independently.
What is the hardest part about learning to code according to the video?
Building your own projects, not writing code.
00:14
Why do tutorials often lead to a false sense of accomplishment?
Because you copy and paste code without understanding it, so you can't apply it to new projects.
00:30
What technique did the author learn from physics to memorize equations?
Understanding the meaning behind equations and deriving them from first principles.
01:54
How does understanding the meaning behind something help memory?
It uses different parts of the brain, aiding retention.
02:31
What is the memory palace technique?
Assigning items to objects in a familiar room to use spatial memory for recall.
02:55
What should you do when following a tutorial to improve retention?
Understand each line of code, write it down or draw a diagram.
03:10
Is it okay to Google syntax when coding?
Yes, but you shouldn't search for full solutions.
03:36
First Principles Learning
Introduces a powerful learning technique from physics that can be applied to coding.
01:54Meaning Enhances Memory
Explains the cognitive benefit of understanding meaning, not just memorizing.
02:31Memory Palace Analogy
Connects a proven memory technique to coding education.
02:55Active Engagement with Code
Provides a concrete action: write or draw to understand code.
03:10[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.
⚡ Saved you 0h 04m reading this? Transcribe any YouTube video for free — no signup needed.