# About This Book As a programmer, I have always considered how the source code should look, how it is logical, and how it can reflect what it is doing. I learned about the Clean Code book and other books on good coding practices. I collected all my knowledge in this field and added my thoughts too—you can find them on the left, under the Clean Code group. I also did a few presentations and training about clean code. But I realized that although most programmers knew the main clean code rules, and despite them all being experienced software engineers, the source code always became very complicated. So in the recent 10 years, I tried to find the traps we often fell into and tried to understand the programming habits that may lead to overcomplicated code. I would like to share my unusual message that we should *not* do many things during programming that we used to do. Of course, I try to tell what to do instead. This is what you can read under 'clear code'. It is all based on the clean code principles. The name is explained here: [The problem with Clean Code's name](https://petozoltan.gitbook.io/clearcode/various/the-problem-with-clean-codes-name). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://petozoltan.gitbook.io/clearcode/introduction/about-this-book.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.