What every bit of code you write should have - Rambli
It should be testable. It should defend. It should be clear to understand. It should catch errors. If it is not the sole source of all the logging, it should provide valuable fragments that render what it logs usable. It should do what it is meant to do, not what we hope it to do
