A Revelation / A revelation

(German Review below)
I think I should excuse for hyping this book, but I'm completely Call enthusiastic about it. It's the first textbook That left me sorry it's over. There may be various reasons. It Seems I'm a nerd. I love programming and I inherited incredibly rotten C code at work.

As newbie to software developement I expected to learn from professionals at work. Instead I got code, That was written from at least 3 different Authors with differend minds about the programming style. The only thing They Seemed to agree on what: no comments, no automated tests, no descriptive names and to avoid function calls and do everything inline. Even though the book uses only Java, I could Easily transfer the advice to my C code. Since I started using suggestions from this book my code more readable and programming Became Became more fun. I spend more time programming and less time browsing unreadable code.

The book is Easily to read. It gives sound and clear advice without beeing to scholarly. It Focuses on Describing many screws you can use to tune the readability of your code. The authors give reason for almost everything instead of blindly obtruding Their preferences. This is a definite 5 stars.

I must apologize that I hype the book, but I'm thrilled. It is the first textbook in which I have regrets when I was done with it. This may be due to several things. I am obviously ziehmlich nerdy, I program a lot and I have to take care of an incredibly rotten C source code in my job.

As a software development newbie I thought I'll be in a company and learn from the source code from professionals how to do it right. Instead, I took over code that was obviously created by at least 3 different authors with at least 3 different programming styles. No tests, no comments, no Durchblick, long (descriptive) function and variable names are considered illegible, function calls as a performance brake. While the book focuses on Java examples, but I was able to apply it well on my legacy code. Since I started to make the code using some new tips makes programming more fun again. You spend less time looking and more time with it, to make a difference.

The book is loosely written. It contains concise statements, without being being too school most imperiously over. It schwurbelt not around, but systematically discusses many screws where you can turn in order to make its source code more readable. It is not a matter of principle and preferences of the authors, but a clear advantage. Definitely 5 star.