Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.

Clarity is kindness to your future self

We tend to write code like we're the only person who'll ever read it. We skip the obvious variable names, cram logic into dense one-liners, delete comments as we go. Then months later, someone else—maybe you, maybe a teammate—opens that file and spends an hour deciphering what you meant. That friction is real, and it costs time and sanity.

But this quote works beyond programming. It's actually about respecting the person who comes after you, whoever that is. A colleague inheriting your project. Someone reading your documentation. A future version of yourself. The "violent psychopath" part is just hyperbole that sticks in your brain—the real message is simpler: write as if someone will struggle with this, and that struggle matters. Clarity takes effort upfront, but it's an act of kindness to whoever has to untangle it later.

The counterintuitive part? Being considerate this way doesn't slow you down. It forces you to think clearly about what you're building in the first place. You end up with fewer bugs, easier debugging, and code you're not embarrassed to show anyone. Turns out, writing for a hypothetical psychopath is just good practice for writing clearly, period.