2 comments

[ 3.4 ms ] story [ 19.4 ms ] thread
Hi folks! So, I’ve been thinking about log messages lately. And, honestly most of them in my opinion feel like system noise instead of something a human can act on. Like, half the time it’s a stack trace, an error code, or “something went wrong,” which doesn’t help anyone. At work, I was discussing what “human‑friendly” logging should look like with my team, and someone wrote up a short guideline about writing clearer, more actionable messages (disclosure: I work at this company). I found it useful, so sharing in case others like this kind of thing.

Curious how others approach this. There are some other good reads as well in this repo, do check out!

When you have a thousand of them, the dry version is easier to parse to find the three that are relevant.