Why Is Coding So Hard? How to Actually Learn It

TL;DR

You're not bad at coding; you're bad at how you learn it. Stop bingeing tutorials and jumping between six stacks. Instead, pick one real user with one painful problem, commit to a single stack, and ship an MVP end to end. Tech rewards solvers who build, not knowers who consume.

Transcript

You're not bad at coding. Let me start there. You're not bad at coding. You're bad at the way you're trying to learn coding. And that difference is the whole game. Most beginners think coding is hard because they're sitting there memorizing syntax, watching tutorials, copying along, hoping one day the universe opens up and blesses them with full st... Read More

Key Insights

• The real reason coding feels impossible is not a lack of intelligence but a broken learning system: memorizing syntax, watching tutorials, and copying along produces 'fake progress' where you feel productive without shipping a single real thing.
• Tech rewards solvers, not knowers. Nobody pays for 'I understand what a for loop is'; they pay for 'this is broken, can you make it work by Friday.' Aiming at a real problem for a real person is what gives you stability.
• Jumping between JavaScript, Python, Rust, React, and Elixir on day nine is like a new agency offering every service to anyone for $500. It looks like hustle but builds nothing solid, optimizing for knowing stuff instead of solving something.
• Letting AI write code you don't understand is 'dependency with lipstick.' You can't maintain, fix, extend, or sell it, and you can't answer basic questions without running back to AI, so you own nothing and are 'temporarily babysitting a code base.'
• Chasing 'job ready' without becoming 'project ready' means trying to skip from zero to senior salary without finishing one working app front to back. Studying CS curriculum like binary search trees before building a login form is 'studying to pass a class you're not in.'
• Learning alone with zero accountability, no code reviews, and nobody asking 'is it live?' guarantees you quietly quit before getting good. In coding you are the customer, and you leave yourself because the system gives you no reason to stay.
• Applying business metrics: learning the wrong way gives you high CAC (time, frustration, stress) and low LTV (ability to earn and ship), with a payback period near infinity, which is where burnout and month-three quitting come from.
• The fix is to fire the wrong customer (your ego) and become a builder using four steps: pick one customer with one painful problem, pick and commit to one stack, build an MVP core loop only, and stop being a passive learner.

Questions & Answers

Q: Why does coding feel so hard even when I study a lot?

Coding feels hard not because you're dumb but because you're trying to scale on top of a broken base. Most beginners memorize syntax, watch tutorials, and copy along hoping for sudden clarity, which the speaker calls fantasy roleplay rather than learning. This produces fake progress where you feel productive without shipping one real thing. The foundation sucks, so you never feel stable, and it has nothing to do with your intelligence.

Q: How does serving your ego sabotage learning to code?

The speaker says your ego is the wrong customer you're serving. Your ego wants comfort and to feel smart, so you binge YouTube, Instagram reels, and AI prompts, consuming so much content that you feel productive without shipping anything. This is fake progress. You optimize for knowing stuff instead of solving something, building nothing solid. Firing your ego as a customer and becoming a builder is the shift the whole video points toward.

Q: Why is jumping between many programming languages a mistake?

Trying to learn JavaScript, Python, Rust, React, and Elixir at once, especially on day nine with a plan six stacks deep, is like a new agency offering TikTok ads, Facebook ads, email marketing, funnels, sales coaching, and web design to anyone for $500. On paper it looks like hustle, but in reality it's chaos. You build nothing solid and stay generic, and generalists with no reps are invisible while specialists with reps are valuable.

Q: Is using AI to write code good for beginners?

The speaker warns that having AI write code you don't understand is 'dependency with lipstick,' not leverage. When AI spits out a dashboard or complex app, you're temporarily babysitting a code base you don't understand. You can't maintain, fix, extend, or sell it, and you can't answer basic questions without running back to AI. Since everyone with a keyboard can ask AI to generate code, relying only on that makes you fully replaceable.

Q: What is the difference between job ready and project ready?

Chasing 'job ready' means trying to skip from zero to a senior developer salary without finishing a single working app front to back. The speaker compares it to wanting a $3 million agency after selling only two logos but watching 40 hours of sales training. You copy CS curriculum like data structures and binary search trees because it feels official, yet haven't built a login form. School is built for grades; industry is built for shipping, which are different games.

Q: How do business metrics like LTV and CAC apply to learning to code?

The speaker frames your progress in business terms. Your LTV, lifetime value, is your ability to earn, build products, launch startups, and spin up tools; if you never ship end to end it stays near zero. Your CAC, cost to acquire, is the time, frustration, and stress you spend making progress, which explodes when you learn the wrong way. High CAC and low LTV with an infinite payback period is why burnout and month-three quitting happen.

Q: What are the four steps to become a builder instead of a passive learner?

You fix it like a business by firing the wrong customers and moving up market. Step one is pick your customer: one person with one painful problem, not the whole world. Step two is pick one stack, such as React and Node or Next.js and Supabase, and commit to it to raise your value. Step three is build an MVP with the core loop only for that one customer. The speaker presents these as the shift from tutorial consumer to builder.

Q: What does building an MVP core loop actually mean?

Building an MVP means core loop only, not ten features or a dream startup with AI agents, 3D AR, crypto wallets, dark mode, and a marketplace. For the speaker's Let's Social project, a gamified Q&A community, the core loop is ask, get help, earn credibility: can a dev ask a question, can somebody answer, can you track that you helped. That heartbeat is the priority, because if it doesn't work, nothing else matters, just as with the mental health journaling app shipped during lockdown.

Summary & Key Takeaways

• Coding feels hard because you serve the wrong customer, your ego, which craves comfort. You binge tutorials, reels, and AI prompts to feel productive without shipping anything real. Spreading across six stacks on day nine is chaos, not hustle, and builds nothing solid on a broken foundation.

• Tech rewards solvers who fix broken things by Friday, not knowers who understand for loops. Letting AI generate code you can't maintain creates dependency, not leverage. Chasing job-ready over project-ready, copying CS curriculum, letting fear pick your stack, and learning alone all guarantee you quit before getting good.

• Fix it like a business: fire the wrong customers and move up market. Pick one customer with one painful problem, like the English learning game for Korean kids or Gina's church translation app. Commit to one stack to raise your value, then build only the MVP core loop for that person.