The document discusses ways to make applications more resilient to crashes. It suggests using caches instead of master copies to avoid data loss on crashes. Database transactions can maintain consistency even if the database crashes. Atomic operations like file renames can be used to update counts reliably. Recovery is also important - inconsistent states after crashes should be detected and resolved. The document advocates designing systems with crashes in mind through techniques like logging, versioning, and watchdog processes.