How I Would Learn To Code (If I Could Start Over in 2025)

Summary

In this video, the speaker shares insights on how to approach learning to code in 2025, based on personal experience. Emphasizing hands-on learning, the speaker encourages beginners to spend minimal time on basics and theory, instead focusing on building projects right away. They stress the importance of sticking to one tech stack, avoiding distractions from new frameworks, and learning through building rather than relying on tutorials. The speaker also highlights the value of building in public, using AI tools wisely, and learning to read and debug code effectively, all while continually challenging oneself to build bigger and more meaningful projects.

Takeaways

• 🚀 Spend as little time as possible on theory and basics—learn just enough to start building real things quickly.
• 🧠 Follow the 80/20 rule: focus on the small set of concepts you’ll use most often and learn everything else only when needed.
• ⌨️ Start writing code immediately; avoid passive learning like watching tutorials or reading without practice.
• 🎯 Choose one tech stack based on job market demand and commit to it for at least six months without switching.
• 🧱 Master your chosen stack deeply, including its ecosystem, tools, testing practices, and common design patterns.
• ✨ Avoid shiny object syndrome—new frameworks and tools won’t make you a better programmer as a beginner.
• 🔥 Escape tutorial hell by building your own projects, modifying tutorial code, and relying more on documentation.
• 🌍 Learn and build in public by sharing progress, struggles, and projects on platforms like GitHub, LinkedIn, or Twitter.
• 🤖 Use AI tools wisely: let them explain concepts and unblock you, but don’t let them do all the thinking or coding for you.
• ⏱️ Apply the 20-minute rule—struggle with a problem first, then seek help if you’re truly stuck to accelerate learning.
• 🏗️ Focus on building larger, more complex projects instead of many small ones to better simulate real-world development.
• 📖 Spend time reading other people’s code to learn structure, patterns, and how real production codebases work.
• 🛠️ Learn essential developer skills like debugging, using dev tools, navigating codebases, and stepping through code.
• 🔁 The best way to learn coding is to keep building—reuse components, grow your toolbox, and apply knowledge continuously.

Q & A

Why is it important to spend as little time as possible on learning the basics of coding?

Spending too much time on the basics can lead to procrastination and prevent you from applying what you learn. It's better to learn just enough to start building projects and gain hands-on experience. Focus on learning the essential concepts that you'll use frequently and learn the rest in context as you build.

What does the 80/20 rule mean in coding, and how should it be applied?

The 80/20 rule suggests that 20% of the concepts will cover 80% of what you need to do in coding. Focus on mastering the key concepts (like variables, functions, loops, and conditionals) that are used frequently, rather than trying to learn every possible detail. This approach saves time and helps you build faster.

What is 'productive procrastination,' and how can it affect learning to code?

'Productive procrastination' occurs when you spend too much time preparing or researching before actually starting to code. While it might feel like you're getting ready, it can delay your progress. The key is to start coding and learn through practice instead of endlessly researching or gathering information.

How can AI tools like ChatGPT help in learning to code?

AI tools can be extremely helpful for learning to code by providing answers to questions, explaining complex code, and offering suggestions for debugging. However, it's important to use AI as a learning aid, not as a shortcut for writing entire programs. It should help reinforce your learning, not replace the process of problem-solving.

Why should you focus on one tech stack when learning to code?

Focusing on one tech stack allows you to become proficient in that stack before moving on to others. Trying to learn multiple technologies at once can lead to confusion and a shallow understanding. By dedicating 6 months to one stack, you build deep knowledge and gain real proficiency.

How do you avoid the temptation of 'shiny objects' in coding?

Stay focused on mastering the tech stack you’ve chosen instead of constantly jumping to the latest framework or technology. New tools and frameworks often create distractions, but the fundamentals of coding and problem-solving remain the same. Stick to your learning path and resist the FOMO (fear of missing out).

What is 'tutorial hell,' and how can you escape it?

Tutorial hell happens when you get stuck in a loop of following tutorials without applying what you've learned to real projects. To escape it, start building your own projects as soon as possible. Don't just replicate tutorial projects—modify them, add your own features, and start coding independently.

Why is it important to build real-world projects as a beginner?

Building real-world projects helps you gain practical experience and understand how to solve actual problems. Small projects are useful for learning, but larger projects challenge you to think more creatively, structure your code better, and prepare you for real job requirements.

What role does reading other people's code play in learning how to code?

Reading other people's code is vital for understanding how real-world applications are structured. It helps you learn best practices, recognize common patterns, and see how experienced developers solve problems. This is especially useful when you start working with large codebases in professional environments.

What is the 20-minute rule when it comes to asking for help in coding?

The 20-minute rule suggests that you should spend about 20 minutes trying to solve a coding problem on your own before seeking help. This gives you the chance to learn through problem-solving and boosts your ability to figure things out independently. After 20 minutes, if you're still stuck, it’s okay to ask for help.