Just enjoying some morning reading and realized that I designed processes for community engagement with some of the largest technical ecosystems in history in a way which very much mirrored incident response practices on SRE teams but almost no one was willing to code these as similar types of work.
So that's cute.
=> More informations about this toot | More toots from anthrocypher@hachyderm.io
If you don’t think every large, complex ecosystem of massively engaged constituents is in some sort of state of perpetual large or small incident, you are living a fantasy.
=> More informations about this toot | More toots from anthrocypher@hachyderm.io
This morning’s reading, btw, was @mononcqc's wonderful article on Honeycomb incident response practices in The New Stack.
We need so much more like this.
https://thenewstack.io/how-we-manage-incident-response-at-honeycomb/
=> More informations about this toot | More toots from anthrocypher@hachyderm.io
This is a really important point.
Almost no one dealing with sociotechnical factors in prod is getting resourced properly.
Our industry’s obsession with individual genius means reality gets retrofitted into the shape of problems that prop up the lone hero myth, rather than designing for what it actually takes to collaboratively maintain working systems.
https://dair-community.social/@trochee/113765351777452728
=> More informations about this toot | More toots from anthrocypher@hachyderm.io
@anthrocypher
I've always loved how the compassionate theory behind blameless post-mortems, as was pioneered also at Etsy, an idea of collective responsibility, is itself also a mirror of contemporary ethics.
cc @linse
=> More informations about this toot | More toots from yala@degrowth.social
text/geminiThis content has been proxied by September (3851b).