Code Quote by Martin Kleppmann
““However, a real implementation may still have to include code to handle the case where something happens that was assumed to be impossible, even if that handling boils down to printf("Sucks to be you") and exit(666) — i.e., letting a human operator clean up the mess [93]. (This is arguably the difference between computer science and software engineering.)””
About This Quote
Source Book: Designing Data-Intensive Applications, 2017
Software must anticipate and handle unexpected failures, even those deemed impossible, to ensure reliability.
In simple terms: Plan for impossible errors.
Design robust error handling.
Themes
Mood
Type
When to use this quote
- critical systems
- API development
- user interfaces
- devops
Key Concepts
Questions to Reflect On
- What impossible scenario could break your system?
- How do you balance safety and simplicity?
Over‑engineering can add complexity and cost.