the causes of failures that you explicitly enumerate which were under your control aren't always You Did A Bad Thing. For example, "I trusted this dependency w

the causes of failures that you explicitly enumerate which were under your control aren't always You Did A Bad Thing. For example, "I trusted this dependency which broke" doesn't mean you Did Something Bad, it just means that the cause of the failure was the lack of a way to validate the dependency and fall back on a known-good version. A good example of this is build pipelines relying on the ability to download npm/nuget/debian packages from a remote server instead of vendoring them locally - this is an intrinsically unreliable choice to make. The remote server being unreachable is not your fault, but there are steps you can take to fix this problem in the future. Avoiding external blame in your 5Ys (without ignoring the external factors) encourages you to make local changes. As always you have to apply reason here and not adhere to dogma, but it's a useful dogma.