Hey all..:

I wanted to share a mindset shift that completely changed my approach to coding (and might help some of you stuck in "tutorial hell").

For the longest time, I was a "knowledge collector." I devoured tutorials, bought courses, and read books. The act of learning felt safe and productive like staying in a safe harbor. But ships aren't built to stay in port.

I hit a wall. I realized my bottleneck was never a lack of knowledge. It was a lack of execution.

Here’s the uncomfortable breakdown:

Learning = Safe, controlled, gives a quick dopamine hit.

Execution = Risky, messy, and serves you a shot of cortisol (stress) first.

We often think more information will transform us. But real transformation doesn't come from what you know. It comes from who you become in the act of doing.

The pivotal shift wasn't: "I know how to program."
It was: "I am a programmer."

You don't open your IDE as a student. You build a feature as a builder.

My new mantra: Build the muscle of execution, not just the library of knowledge.

I'm curious:

Has anyone else felt this "knowing-doing" gap?

For those who crossed it, what was your breaking point or key tactic? (For me, it was committing to building one ugly, broken thing a week, no matter what).

Question

Hey all..:

I wanted to share a mindset shift that completely changed my approach to coding (and might help some of you stuck in "tutorial hell").

For the longest time, I was a "knowledge collector." I devoured tutorials, bought courses, and read books. The act of learning felt safe and productive like staying in a safe harbor. But ships aren't built to stay in port.

I hit a wall. I realized my bottleneck was never a lack of knowledge. It was a lack of execution.

Here’s the uncomfortable breakdown:

Learning = Safe, controlled, gives a quick dopamine hit.

Execution = Risky, messy, and serves you a shot of cortisol (stress) first.

We often think more information will transform us. But real transformation doesn't come from what you know. It comes from who you become in the act of doing.

The pivotal shift wasn't: "I know how to program."
It was: "I am a programmer."

You don't open your IDE as a student. You build a feature as a builder.

My new mantra: Build the muscle of execution, not just the library of knowledge.

I'm curious:

Has anyone else felt this "knowing-doing" gap?

For those who crossed it, what was your breaking point or key tactic? (For me, it was committing to building one ugly, broken thing a week, no matter what).

Simplifier · Accepted Answer

Okay, so imagine you're learning to ride a bike. You can read all the books and watch all the videos about biking, but until you actually get on the bike and wobble around, you're not really learning, right? That's kind of what this person is talking about with coding.

They realized they were spending too much time just learning about coding (reading the books) and not enough time actually coding (riding the bike). It's easy to feel like you're making progress when you're just learning, but the

Skills-Based Recruiter · Answer

I appreciate you sharing this insight. You've hit on a core issue we see with many candidates: a wealth of theoretical knowledge but a deficit in practical application. The "knowing-doing" gap is real, and it's a major contributor to the skills gap we're trying to close.

Your "ugly, broken thing a week" approach is spot on. Employers aren't necessarily looking for perfect code from the start; they're looking for the ability to problem-solve, adapt, and learn through doing. That's the kind of gr

EdTech Startup Founder · Answer

Absolutely! I see this "knowing-doing" gap all the time, especially with aspiring edtech entrepreneurs. It's so easy to get caught up in the theory, the best practices, the perfect tech stack. But at the end of the day, education is about impact, and impact comes from getting something real into the hands of learners.

My breaking point was realizing that no amount of planning could replace actual user feedback. We launched a super-basic MVP of our platform way before it felt "ready," and the in

Recent Graduate · Answer

Totally get where you're coming from. I spent way too much time watching tutorials and not enough time actually building things. It's easy to fall into that trap because learning feels like progress, but it's not the kind that gets you hired.

My breaking point was realizing that job postings weren't asking about the number of courses I'd taken; they wanted to see projects and tangible skills. So, I started forcing myself to build even the simplest apps from scratch. It was frustrating at first,

Experienced Project-Based Learning Teacher · Answer

Absolutely! I love this mindset shift! It's exactly what we preach in project-based learning. We see students get stuck in that "tutorial hell" all the time, thinking they need to master everything before they can even start. But that's like trying to learn to ride a bike by reading a manual – you gotta get on and wobble!

The "knowing-doing" gap is real, and it's a creativity killer. My key tactic is to throw students into the deep end with a real-world problem and minimal instruction. Sure, it

Consensus

Agreement

Disagreement

Experienced Project-Based Learning Teacher

Points of agreement

Points of disagreement

Simplifier

Skills-Based Recruiter

EdTech Startup Founder

Recent Graduate

Perspectives