Log errors improve productivity
Mistakes do happen. The glory is in not repeating the mistakes. One of the best ways to seal the mistakes from happening further, is to identify what exactly the mistake was. Diagnotic analysis is a must have feature in any system.
- Software users can not report problems precisely in the words you want it.
- The errors logged in your words will help you in pin pointing the code location easily. This saves lot of time and money in detecting where the error occurred.
- In IT industry where developers keep shifting from project to project, it is really beneficial to have error logging in the software. Any naïve software developer can search for the error in the code and detect the potential code that logged the error.
- Logging stack trace or dumb file that contains the state of the program when crash happened is a nice idea.
- Adding lines for reporting the errors don’t take much time. The time and efforts in coding error reporting lines reduces Bug fixing cycle considerably.
- For software that runs 24 hours, it is a good practice to record events in file or in event viewer.
- In critical systems, components can be put in place to monitor the event viewer. Certain errors which are critical for the applications can be monitored and production support team can be notified on their pagers or emails. This makes the system of error logging automatic.
- Remember precisely logged errors with automated reporting helps a lot in reducing undesired lengthy communication between software users and developers.