Write your error states for a stranger three months from now, not for yourself today

Из ленты dev.to devops — кратко, чтобы не потерять.

Most error messages are written for the wrong reader. They’re written for the person who’s watching when the thing breaks. You’re at the terminal, the run fails, the message says connection refused or validation failed at step 3 , and that’s enough, because you have all the context in your head right now. You know what you were doing, what you changed, what the system was supposed to do. The message just has to jog a memory you already have. The reader who actually needs the error state is someone else entirely, and they show up months later. I got talked into this view in a long comment thread on an earlier post, and it changed how I think about failure handling, especially for the async, agent-driven work I do a lot of now. The reader you’re not designing for Here’s the gap. When an inte

Полный текст и контекст у первоисточника: https://dev.to/rapls/write-your-error-states-for-a-stranger-three-months-from-now-not-for-yourself-today-54jm