The user is amazed by your performance and buys a new project from you. You find the cause of the fault and provide a fix in a short time. How about this way to look at it: When an error hits the user, your application reacts to it in a reasonable way, protecting the data and reporting the error to you. There's nothing positive about errors, is there? Tired of problems, you quit your developer career and start making burgers instead. You get sick of such a user and never want to deal with her again. Naturally, she calls you (or your boss) yelling and demanding immediate action. If it's not her lucky day, her computer jams and the database corrupts. ![]() ![]() When an error hits the user, she runs the risk of losing unsaved data. Caution! A run-time error can cause data loss, user aggravation and severe developer headache.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |