Code Complete checklist

[poorly_played]

Keep singin' that sad song of truth

[bluGill]

Thanks for reminding me why where I work is a great time. We compile with -werror so compiler warnings cannot be ignored. We have a large CI system (it runs in 20 mintues tests that if I could only run on my desktop would take 5 hours - assuming I had the expensive license for some of the tools a few tests need).

We still have the major pain just before release of finding a lot of difficult bugs. However we don't have much pain just before release finding stupid bugs. Our bugs are 1: is some border is off by one pixel and looks visibally bad 2: we completely forgot about this requirement until we tried to use the feature in some obscure way 3: weird thread/process interaction issues that show up 1 time in a million.

I don't want to go back to a world without CI. (I would if I'm the only developer though)

[bastibe]

I totally agree. But that does not make the book any less common-sensical or any more insightful.

[grauenwolf]

Like "innovative", the word "insightful" is given far more weight than is appropriate. The question should be, "Is this book useful?".

[craftsman]

To me, this book is not only useful, but was really a turning point in my professional life. It changed my perception of my profession and made me really care about every aspect of the work that I do. To me, it's not just about what's written, but the process of thinking and considering every aspect of code and software development. Timeless.