I get that but I&#x27;m wondering who is this postmortem written for? For other engineers? Not entirely - it&#x27;s seems to be written partly as PR piece.<p>In that case I don&#x27;t need to basically congratulate Stripe on messing up and then posting PR piece on how they messed up, especially when it&#x27;s such a trivial mistake (by that I mean it&#x27;s not anything technically interesting for what went wrong). I guess I&#x27;ll concede that what is technically interesting is not objective - many things I consider complicated other would consider basic, so I don&#x27;t really have the right to serve as the arbiter of what is technically interesting.<p>What happened? We dropped an index. Why? Bad tooling. Fix? Patch code, add index. Future fix? Vague goals to stop this from happening.<p>Though I might be taking it too far, I don&#x27;t see why I need to give props to someone for doing messing up something relatively basic and then fixing it - don&#x27;t people complain enough about kids getting participation trophies?<p>Anyway, don&#x27;t mean to call out any specific Stripe engineer, it&#x27;s failed process at multiple levels (guy who drops index has no visibility into DB?).