This is a great write-up. When describing my own bugs and issues to stakeholders I often find the following difficult to communicate: * Bug was introduced on d

This is a great write-up. When describing my own bugs and issues to stakeholders I often find the following difficult to communicate: * Bug was introduced on date X but only caused problems on date Y ("if the bug was introduced on date X then we would have seen it on date X, so you’re wrong") * Doing X led to the outage but X wasn’t the fault, X was a valid thing to do, the code should have been able to handle X, the fact the code couldn't handle it was the actual problem which needs to be fixed ("look, you said X caused the problem, so the solution is just not to do X right?") This article conveys both these points clearly and effortlessly. I might borrow some terminology from this in the future.