As someone employed in building complex systems, I appreciate the takeaways listed during the discussion:<p><pre><code>    RethinkDB’s engineers noted three takeaways from tracking
    down this bug. First, fuzz-testing—at both the functional
    and integration-test level, can be a powerful tool for
    verifying systems with complex order dependence. Second,
    runtime invariant assertions were key in identifying the
    underlying cause. A test like Jepsen can tell you that the
    cluster can exhibit split-brain behavior, but can’t tell
    you anything about why. The error messages from those
    leader and log order assertions were key hints in tracking
    down the bug. Rethink plans to introduce additional runtime
    assertions to help identify future problems. Finally, they
    plan to devote more attention to issues which suggest—even
    tangentially—consistency errors.</code></pre>