The HN title primes us using the clickbaity word “blames”. Without that title, only a cynic would read that much into what is written by a technical person with a majority technical audience. I think your presumption is that Sam is an idiot (trying to pass the buck to a technical audience would be idiotic), and my presumption is that Sam is smart but in a hurry.

Go ahead and blast SamA for writing something transparently as an engineer, presumably quickly without over-thinking it. But don’t be surprised if he starts to write using highly conditional PR-talk with zero substance.

Meanwhile, wait and see their incidence report. That is writing for a discerning audience, and any whiff of passing-the-buck would be responded to harshly by the highly technical audience. This is an expected class of error, and it happens when a company develops and deploys fast, but I expect they will still try and change some processes to try and avoid similar issues (hard though that is)...

Apparently ‘we identified an issue, we are fixing it as fast as we can’ is not enough for some people. Some people also want Sam to use weasel words to avoid mis-reading of a single paragraph of text. A level of perfection few of us could achieve.