'Build 100 projects'

1. The advice

"Just build 100 projects." You've heard it in every learn-to-code thread, every Twitter post, every YouTube comment section. It is the most common piece of "tough love" advice in the field.

It is also wrong, in a specific way worth understanding.

2. Why the count is wrong

The advice is half right. Reps matter. Building things matters. Trying matters.

The wrong part is the number. The number assumes that all reps count equally — that one project is one unit of learning, and a hundred such units is a hundred units of progress.

In practice, one well-done rep teaches more than ten half-done ones. And the way most people interpret "build 100 projects" is as a permission slip to half-do everything: ship the todo-app to one-third complete, ship the weather app to one-third complete, ship the chat app to one-third complete, and call it nine percent of the way to 100.

Nine projects, each abandoned at the boring part, teaches you only one thing in nine different costumes: how to start.

3. What actually counts

A rep that counts is one where:

• You took a real thing to a real finish.
• You hit at least one problem you didn't know how to solve, and solved it.
• You can explain, after, what you'd do differently next time.

Three projects like that beats a hundred clones. The reps the brain stores around are the painful ones — the ones where you had to choose, verify, and admit you were wrong.

4. Try it

If the second number is much smaller than the first, "build 100 projects" was the wrong target. The right target is: finish the next one. Then finish another. Stop counting starts.