Clean Code is one of the best books I've ever read. I don't even code in Java.
Maybee thats the reason ;P
Clean Code is not bad in itself. The problem is that some people made it a bible, like the absolute truth (I guess it is written in that way), and that's where it fails.
Why? I have heard it recommended but I haven't read much of it.
A lot of people just don't like the author, so viscerally react negatively to the book itself. As a book in and of itself, it's a bit opinionated and maybe a little outdated, but no more so than The Pragmatic Programmer, The Mythical Man-Month, Code Complete, Patterns of Enterprise Architecture, Refactoring and Code (I haven't read the other two books in OP's Software Engineering section, so can't speak to them). It's entertaining to read and something you could finish on a long plane ride - there's good advice in there, but you won't really learn anything like you would if you read, say, Knuth.
I think what people dislike about Code Complete and Uncle Bob is all the dogma. I.e. You _MUST_ do this or you're not a professional and should feel bad.
The book contains some really bad advice (like using instance variables for temporary state instead of passing values via method parameters, with the rationale that parameter-less method calls are easier to read), and you need to already be quite experienced to tell the good from the bad.