Concept
Drill the Weak Point
Drilling the weak point means pulling the single sub-skill that most limits your performance out of the real task, practicing it on its own until it improves, and then putting it back into the whole skill to test whether it actually got better.
Most practice repeats what we are already decent at, because whole-task practice feels productive. A complex skill is a chain, though, and the weakest link sets the ceiling. In Ultralearning, Scott H. Young calls this the drill principle. You find the component that holds everything back, cut it out, and work on it alone, where you can get many repetitions and clear feedback. Drills feel uncomfortable, and that is the point: they show exactly what you cannot yet do. Drills are also easy to overdo. Drill too long, far from the real context, and the improvement doesn't transfer. That is why drilling sits inside a cycle. You do the real thing to spot the bottleneck, drill it briefly, then return to the real thing and test. If nothing changed, the diagnosis was wrong.
A real-life example
A self-taught developer builds small apps, but every project stalls in the same place: SQL queries with joins. She doesn't start another full app. Instead, she spends three evenings on twenty short join exercises against a sample database, checking each result. On the fourth evening she goes back to her app. The reporting screen that blocked her for a week takes an hour. Her next weak point is testing.
How to use it
- 1Do the real task once and note where it breaks down: the spot where you slow down, stall or repeat the same mistake.
- 2Design a short drill that isolates only that piece. It needs fast repetitions and a clear right-or-wrong signal, and 20–30 minutes is enough.
- 3Return to the full task within a few days and check whether the weak point improved. If it didn't, rethink the diagnosis. If it did, find the next bottleneck.