Rules of Systems Programming

Hard won wisdom #3 in a series:

1. Never check for an error that you don’t know how to handle.

2. If you DO have to check for such an error, pin the blame on someone else (“This code choked because the IFrobozz packet was malformed, it’s not my fault.”)

3. If you’re completely screwed, crash spectacularly. Everyone hates a subtle failure. Smoking rubble is a pretty good hint that something needs to be fixed.

Author: landon

My mom thinks I'm in high tech.