> Otherwise, get over it and be careful with your stuff if you can’t afford the repair.
I don't know if you're an engineer, but if you are you probably don't take the same approach to errors in your software. Being careful is only part of the solution to reducing risk. Another is adopting practices and patterns that are less error-prone. And another is to reduce the impact of errors when they do happen.
With a software service, we might have redundancy, and a watchdog or orchestration system that restarts any instances that crash. With a laptop, we might purchase accidental damage insurance, or just decide to buy a brand that is cheaper to repair.
When humans are involved, "be more careful" is rarely a successful strategy on its own.
I don't know if you're an engineer, but if you are you probably don't take the same approach to errors in your software. Being careful is only part of the solution to reducing risk. Another is adopting practices and patterns that are less error-prone. And another is to reduce the impact of errors when they do happen.
With a software service, we might have redundancy, and a watchdog or orchestration system that restarts any instances that crash. With a laptop, we might purchase accidental damage insurance, or just decide to buy a brand that is cheaper to repair.
When humans are involved, "be more careful" is rarely a successful strategy on its own.