Hacker News new | past | comments | ask | show | jobs | submit login

On the home page I read this:

> Extensively fuzz tested for stability > Performance and power mean nothing without reliability. That's why we've subjected Zed's critical code paths to randomized tests that help us find and fix rare edge cases. By creating controlled chaos in development, we achieve stability in production.

How effective is this approach? Does it catch many issues that would not otherwise have been caught through a more risk-based approach? Conversely, does it tend to catch any significant issues?




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: