Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> The blameless culture is about the benefits of not blaming the reports I think.

That may have been the case, but their are entire company values that insist on the blameless culture. This certainly sends a message organization wide to all levels that blame is not tolerated.



You are conflating "blameless culture" and blameless retrospectives culture.

You can 100% blame people for doing bad things. But in an engineering incident you want to find the RCA.

In SDE you may find the single git commit that took down everything, it has a author. Fine, there is blame. But why was there no review, no unit tests, no functional tests, QA, etc....

So you fire the engineer but make no other changes and it happens again, how is that helpful?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: