I 100% agree with the blog post, that everyone should collect a journal of bugs. However, looking at the author's example, I can't help but think that the "fix"

I 100% agree with the blog post, that everyone should collect a journal of bugs. However, looking at the author's example, I can't help but think that the "fix" for the bug is really just a good intention. More specifically, they were bitten by a bug where an environment variable wasn't set in production. Checking that the environment variable, in the future, is set is a nice next step however, I would say, another take away would be to encode that intention in the code directly: throw an error, emit a metric, log an error (that hopefully gets monitored).