> I tend to write resilient code, since I work in embedded systems and what you never want is the system to crash. That might be okay too depending on what you

> I tend to write resilient code, since I work in embedded systems and what you never want is the system to crash. That might be okay too depending on what your system is. I've had a cell phone (the monochrome dumb kind) display an assertion error at me, that was kind of cool. A screw was coming loose, so there were hardware issues. Worst case, I'd have to bring it to the store and get it repaired or replaced; there was no threat of injury or large monetary damage.