Kernighan's lever

• "Kernighan's lever": When you code at your ability level, debugging automatically pushes you beyond it, converting pride/stubbornness into motivation for skill growth
• The "flow" framework shows why this matters: writing simple code keeps you bored, while coding at your limit puts debugging in the frustration zone where learning happens
• Cleverness isn't static—the struggle to debug code you barely understand is precisely what makes you clever enough to understand it
• Deliberately dumbing down code to make debugging easier robs you of the primary mechanism for improvement as a programmer
• The answer to "how will you debug it?" is simply: "By becoming more skilled in the process. Yet."

The author challenges the conventional reading of Kernighan's quote about debugging being twice as hard as writing code. Rather than a warning to avoid clever techniques, it's an observation about a powerful growth mechanism. When you write code at your current ability level, you automatically create a debugging challenge that exceeds your current skill—forcing you to improve. This is "Kernighan's lever": a psychological mechanism that converts basic human drives like pride, stubbornness, and curiosity into sustained motivation for skill development.

Using the concept of "flow" (being fully immersed when challenge matches skill), the author maps out two paths: write below your ability and debug in the comfortable flow zone, or write at your ability and get pushed into the frustration zone where actual learning happens. The key insight is that cleverness isn't a fixed trait—it's acquired through exactly this kind of struggle. Every programmer wields techniques today that would have baffled their younger self, but that improvement came from debugging code they barely understood.

The practical implication is that deliberately writing simpler code to avoid debugging challenges—while sometimes necessary—harms long-term development if done consistently. The frustration of debugging clever code isn't a bug in the system; it's the feature that makes programmers improve. Without this automatic source of motivation, skills stagnate. The answer to Kernighan's rhetorical question "how will you ever debug it?" is straightforward: by tackling the problem and becoming more clever in the process.