More Architecture Mistakes To Avoid
One thing that should be blatantly obvious to anyone who has ever had to fix some code on the weekend, or in the middle of the night, is the importance of excellent error trapping and logging routines.
When you need to fix something, now, you don’t want to be reverse engineering the code or the whole system. You want to know what happened, and what to do. Now.
You need what I call, instantly digestible error messages. I don’t want to hunt it. I don’t want to kill it. I don’t want to clean it. I don’t want to cook it. I just want to eat it. I want both the cause, and the solution, in the same message.
The error trapping routine must be totally reliable. Let me list some strange things that I’ve seen in production.
Complex and Useless:
Read the rest of this entry »