Debugging
One of the other architects at work was running a reading group for our North American comrades, and I felt left out so I figured I may as well just pick up the book to see what the deal was. This book is a bit old, and was written at the time to try and be funny, but to be honest I don't think the humour has aged well and it makes the book jarring to read. Overall I'd describe the book as having been written in the style of a long form chatty blog post, which is a bit unusual. 90% of the readers of this book will be looking for advice on how to debug software systems, but the book frequently uses hardwaare systems as examples. That speaks to the author's background, but its not super helpful for modern audiences living in a software defined world. The book is also a bit dated in terms of terminology and expectations of the work environment -- for example, the discussion of repeatable testing doesn't mention automated regression testing at all, and the only mention of automated tests is fleeting at best. Another example is that the author recommends that you…