In terms of a dry 960 page reference book, with references to studies, Code Complete is good and I refer to it and tell others to refer to it. Uncle Bob's Clean Code covers the same ground, but the book has a narrative drive, gives examples, and is stylistically well written (although people may or may not agree with certain ideas).

I think both books are good but I usually recommend people read Clean Code first. It is an easier read, and it is also half the size so they're more likely to finish it.

It doesn't really cover enterprise patterns or refactoring in any depth, so I'm not sure why you'd replace Fowler. I agree skipping uncle bob is probably healthy for everyone though.

It has one chapter that sumarizes refactorings. Enterprise patterns or design patterns in general are about software design. IMHO design patters are the worst way to learn about design in software.

The fowler book on design patterns isn't really like gang of four or whatever - it's more descriptive of the different approaches you will really find in enterprise software vs. a bunch of fancy OO madness that turns junior engineers into architecture astronauts.

Almost everything. I was scouring it a few weeks ago for some ideas on naming things according to analogies, for examples of analogies to draw from. Sadly it lacks this, and I still haven't found a good source for inspiration in that department. But yes, it's definitely like an encyclopedia of software construction.