A technique for building more reliable software by treating unhappy paths as first class use cases.

4m read timeFrom roughlywritten.substack.com
Post cover image
Table of contents
0. Open a blank document1. Identify the top 1-2 most critical parts of your service2. Imagine through failure scenarios3. For each failure case, reason through a fix4. Prioritize and execute

Sort: