zlacker

[parent] [thread] 2 comments
1. loxias+(OP)[view] [source] 2022-07-09 04:34:26
> We aren’t here because changing a tire is interesting, unique, nor will we learn anything from it

Speak for yourself, some of us (at least me) find "postmortum writeups" FASCINATING!!

I read them every chance I get. Most of the time the root cause wouldn't have affected me, but, I still occasionally will read one, think "oh crap! that could have bit me too!", then add the fix to my "Standard Operating Procedures" mental model, or whatnot. Some of us are still trying to "finish the game" with zero losses. :)

replies(1): >>dangus+n4
2. dangus+n4[view] [source] 2022-07-09 05:18:41
>>loxias+(OP)
What I’m saying is that other businesses/products end up with more interesting postmortems thanks to their more complex operating scenarios.
replies(1): >>loxias+D9
◧◩
3. loxias+D9[view] [source] [discussion] 2022-07-09 06:07:10
>>dangus+n4
Ohhh. Gotcha. Agree. Agree.

Though... I've also read at least one "interesting" postmortem with complex operating scenarios and thought to myself (partially joking) that their failure isn't what they thought it was. The failure was having an unnecessarily complicated architecture in the first place, with too many abstractions and too much bloat. ;-) I would have "just" written it in C++ on Debian... ;-) (I'm exaggerating)

(I know that "my way" is fantastic.. until you need to scale across people)

[go to top]