After watching hundreds of career-changers try to break into software, the pattern is always the same: they can follow a tutorial perfectly, but freeze on a blank file.

Here's why — and the fix.

The problem: Tutorials give you a pre-built roadmap. You're pattern-matching, not problem-solving. Your brain never builds the "what do I do when I don't know what to do" muscle, which is 90% of a real dev job.

The fix — the 70/30 rule:

• 30% of your learning time: structured lessons (docs, courses, videos)

• 70% of your learning time: building something without a tutorial open

Concretely:

1. Pick a tiny project (a todo app, a habit tracker, a markdown notes app — boring is fine)

2. Give yourself a hard constraint: no copy-pasting solutions, only docs + Stack Overflow/AI for concepts, not code

3. Get stuck. Sit in the stuck feeling for at least 20 minutes before looking anything up. This is where the actual learning happens.

4. Ship it ugly. Deploy it even if it's held together with duct tape.

Do this 3-4 times and you'll notice something: technical interviews, take-home assessments, and real tickets at a job stop feeling like foreign territory. You've built the muscle.

The single biggest predictor of who lands a junior dev job isn't how many courses they finished — it's how many times they've sat with being stuck and pushed through without a hand to hold.

Curious what people here are building right now — drop it below.