I felt the same when reading that book, and I never finished it because following the rules he suggested produced horrible code.

If memory serves, he also suggested that the ideal if statement only had one line inside, and you should move multiple lines into a function to achieve this.

I once had to work on a codebase that seemed like it had followed his style, and it was an awful experience. There were hundreds of tiny functions (most only used once) and even with an IDE it was a chore to follow the logic. Best case the compiler removed most of this "clean" code and the runtime wasn't spending most of its time managing the stack like a developer had to do.