Video summary

Why You Can Follow Tutorials But Can't Build Anything Yourself

Main summary

Key takeaways

Educational

Main ideas / lessons

  • Tutorials are useful for learning concepts, but “following along” doesn’t equal building skill.

    • Watching/reacting to what someone else does can feel productive, but it often doesn’t force you to understand core ideas (e.g., functions, reusable components, state management, common pitfalls).

  • Relying on tutorials every day can create “tutorial hell.”

    • Learners may get stuck on small or big problems because they only know what works in the tutorial environment.
    • They may freeze when asked to solve new problems from scratch or when a course doesn’t explain a bug.

  • Build fundamentals through practice, repetition, and iteration—not just consumption.

    • Revisit sections that you don’t understand.
    • Practice by building your own version of what you learned and applying it to different problems.

  • Fundamentals matter for real-world performance and interviews.

    • Visual learners may be able to code while seeing an IDE, but struggle to answer conceptual questions if they haven’t internalized fundamentals.
    • Competence is shown by understanding well enough to explain and solve.

  • Coding is not the only goal—problem solving and debugging are.

    • Engineers must be able to:
      • analyze errors (console/logs),
      • trace where issues come from,
      • develop a plan of attack,
      • debug and iterate until fixed.
    • Communicating issues and working with others is also crucial (you can’t fully learn in isolation).

  • Using AI can accelerate learning, but only if you have fundamentals.

    • AI can help you learn, solve, and prompt for tailored guidance.
    • The risk is relying on AI to do everything without learning the underlying concepts.

  • The real “assignment” is to stop looping and start building your own project.

    • Choose a real problem, define a tech stack, build an MVP, and iterate.
    • Use AI/code review to improve your project, and develop something portfolio-ready or demo-ready.

Methodology / instructions (detailed)

How to use tutorials effectively (instead of getting stuck)

  • Use tutorials to gather knowledge, not to replace understanding.
  • While learning:
    • Spend time understanding what you’re learning and why it works.
    • Avoid rushing through videos/courses.
  • When something is unclear:
    • Rewatch the specific section multiple times.
    • Practice it by building on your own rather than only following the instructor.
  • After a section is learned:
    • Apply it to different problems you want to solve.
    • Practice independently to prevent “false mastery.”

Build fundamentals through a practice loop

For each topic/problem:

  1. Build (attempt a solution)
  2. Apply what you learned
  3. Fail
  4. Repeat
  5. Debug
  6. Figure out what broke and why

This builds durable mastery over time and improves competence in interviews and development tasks.

Debugging approach (implied workflow)

When you hit errors:

  • Check console/log errors
  • Analyze where the error is coming from
  • Trace the source
  • Determine your “plan of attack”
  • Fix and verify

Treat debugging as a core skill for solving any complexity level.

“Unstuck” learning strategy / project workflow

  • Pick an application idea you want to build.
  • Determine the tech stack.
  • Set up project boilerplate.
  • Implement features progressively.
  • If you run into problems:
    • Learn debugging and continue iterating.
  • If you don’t know what to do yet:
    • Create a structured plan for learning and building rather than overthinking.

Use AI responsibly

  • Use AI as an assistant to:
    • learn a language/stack,
    • break down tasks,
    • help solve problems,
    • generate guidance by prompting the right questions.
  • Don’t outsource everything:
    • ensure you still understand the underlying fundamentals so you can apply solutions to new problems.

Final assignment: build your own project

  • Choose a project idea that solves a real, currently relevant problem you care about.
  • Define:
    • your tech stack,
    • what it takes to build an MVP,
    • how you’ll present it (portfolio/demo for a hiring manager, friends/family).
  • Build and iterate:
    • Use AI to check/review code.
    • Review the project’s logic/business plan.
    • Fine-tune based on findings.
  • Focus beyond generic “clone” ideas (e.g., not just “Airbnb clone/Netflix clone/weather app”):
    • identify a real problem and extend that idea with potential to generate value.

Speakers / sources featured

  • The speaker(s): A single unnamed creator/host (speaking directly to viewers).
  • Referenced “others”:
    • “People online” who create tutorials and courses (no specific names).
    • “Different companies” providing interview feedback (no specific names).
    • AI tools (referenced generally; no specific tool names).

Original video