Comment by antirez
7 years ago
I want to politely disagree with the comments here telling that this book should be categorized as a "undergrads book". This is a way to neutralize the content of the book for a broader audience, that is, we are doing everything wrong in most software development environments.
Moreover the author commits a big mistake in saying that Google is a good example of clean software design. Talk with people inside the company to get a real picture, it's full of monsters that you have to maintain just with "tactical programming". This book is very well applicable inside Google as well.
I totally agree with your point. Categorizing the book as undergrads book is really trying to minimize the importance of the message. Those recommendations does apply to everyone, thinking that it could be only useful for junior or undergrads is almost admitting that you don't really have to care, hence you are probably not trying to follow this philosophy. As a senior, I've been trying to apply and you have to be humble and question your choices all the time. One of the problem is the culture of complexity among developers, seniors not being an exception.