Clean code : Introduction

Here the author talks about how the content is structured and the reasons for it.

At a high level, there are 3 parts to it. The first part imparts the knowledge i.e, the principles, practices that a programmer needs to be aware of. The second part has case studies which involves work on the reader's part to carefully understand code, identify issues and refactor it. The third part captures the learning acquired through the hands-on as heuristics.

The justification for this structure of the book's material is that it is not enough for the programmer to be just informed of good practices and principles, which would be akin to telling you the theory of riding a bike which is fine but would not prevent you from falling the first time you get on one.

The author sets expectations that the reader should be prepared to work hard(esp the second part with the case studies) and read a lot of code.
Wow, that's three chapters before the actual material even starts. I cannot wait to start..