0 Front matter
0.1.1 Preface
In some ways, this book has been in development for as long as I have worked in the software industry. This may sound odd, given my career in IT started in the early 90s. I learned early on the importance of logging and translating error events into diagnosis and problem resolution. Lessons came from being a young lead developer on a critical product development running round the clock system testing. If something wasn't shown on the displays, it was assumed to be a presentation system problem, so get Phil he needs to fix things now, even if that was some anti-social time day or night. The reality was that the presentation subsystem was rarely at fault. The error originating from one of many complex backend systems sent erroneous data or tried to communicate using the wrong version of the interface. The better I made the logging to help show what had or had not been sent to the display system, the fewer the calls received.