I find this book is nice. Three years ago, I found it in the MPI library. But I did not read that, since I thought, ``how does it match with the title and the publisher?'' I was wrong. I agree most of the guideline of this book to write a solid code.

The author is the director of development (MS Office). But even for him, it is hard to make sure his developers follow his guideline. There are such stories in the book.

For example, once Excel needed 32 new features for an Expo. However, 1742 known bugs were in Excel at that time. His guideline is ``Don't fix bugs later, fix them now.'' However, the decision of the company was against that. ``Let's implement all the new features first for the Expo, then if we have time, fix the bugs.'' This caused quite hard time for the company. They could not know they were fixing bugs or making another bugs in debug. He wrote why the developer should follow the guideline quite vividly and I convinced this extraordinary story instantly.

He stressed in the book ``Nowadays our company is not like that!'' But interestingly, the book is out of print. It was originally written for Microsoft developers. I see some part of the book is out of date now. But still I think it is good to make the book in print again.

Berlin, 2006-12-3(Sun), Hitoshi