Log Nature is needed, especially the formal product; but if you just own a small or internal tools used, it also needs to be serious?
Honestly I always got the idea to log, debugging always feel good, run, and enough.
So was Aunt hate it several times log, did not put on the agenda taken seriously until the last, aunt finish the code says: There is no error, but do not know whether to finish the ...
Well, I realized that I did not write the log, beginning - progress - end, no clear instructions, or will affect the user experience.
Although it is a small tool, but there are in use, you have to take seriously, treat products, the others have, small but perfectly formed.
However, the question is, is a good start planning log, or re-commissioning the regular?
Ask Aunt,
Are gradually coming. Not a good debugging function to clean up the corresponding log.
Of course, what should be the final output is successful, the function also can be added at any time on the consistency.
I like this because there is no suggestion of aunt, written by one function to clean up the log, resulting in spent half an hour, go over a few thousand lines of code down, clean-up, time-consuming, but also a great lesson.
As for how to write, do not write. This is purely make up the numbers, give yourself mind you.
This article from the blog article multiple platforms OpenWrite release!