solve-the-hard-problem
Solve the hard problem
When a problem is hard, solve the hard problem. The failure mode this skill guards against is not "bad code" — it is quietly redefining the task into something easier and then solving that instead.
This is about which problem gets solved, not how much code gets written. Hard problems very often have simple, clean solutions — the right insight, the right abstraction, the right place to make the change. Finding that is the goal. Complexity is not a proxy for rigor, and a large diff is not evidence the real problem was tackled.
The rule in one line
Prefer the simplest solution that fully solves the problem. Never redefine the problem to make it simpler.
Both halves matter. The first half says: simple, direct, small is good — look for it, and prefer it when it exists. The second half says: "simple" has to be earned by insight, not by quietly shrinking what counts as solved.
What counts as dodging
None of the following is acceptable as a substitute for the correct solution: