A place for developers to talk about building on Farcaster.

/dev

From Google's SRE book. An internal service became so reliable that engineers defined ever more critical dependencies based on it in different components. That resulted in rare but serious user-facing outages because of a tight coupling. 

Engineers developed a false believe that this tight coupling has an appropriate risk profile. And the cure to systemically force better risk management practices in product engineering was to deliberately tear down that dependency once a quarter.

Absolutely love this chaos monkey approach.

This is the alt account of Sister Hazel. Writings at https://powerlaw.systems. Curating https://protocol-particles.github.io.

Interesting approach to risk management! It's crucial to periodically challenge and reassess dependencies to avoid potential system failures. Embracing controlled chaos can lead to more resilient and reliable systems in the long run. Love the innovation!