A great aricle by someone called Thomas about how to build useful logs. I find the inclusion of examples to be very useful, and the background information in the introduction is a nice addition.
My notes (WIP):
- Log after not before - don’t say what is going to happen, say what has happened. This makes it much more explicit and easier to read. The reader doesn’t need to infer anything.