Is this guy a hack?
Sidenote: If anyone is wondering what "Uncle Bob" has against databases, he was an oldy-timy Smalltalk user, and like many Smalltalk users he has an irrational dislike for all things databasey (unless it's a persistent object graph, aka an object database, then it's ok. Bias).
The biggest obstacle we have to making good software is complexity. Adding complexity will never lead to simplicity, and as has been noted again and again over the years. Simplicity is prerequisite (and this doesn't mean that solutions have to be simplistic!)
What software architecture (and all of these other software movements) do manage to do is to funnel money to people who are more interested in techno babble and management processes than they do about solving problems, or writing good code.
Software architecture doesn't solve the complexity problem, if just hides it behind cute diagrams and disguise it with process.
Martin Fowler is an enterprise buzzword methodologist. He was into UML, refactoring and patterns and Java back in the days. Nowadays he is into agile, TDD and ruby.
He has a big respect in certain circles, and even I have the Refactoring book, which was a disappointment for me, because it was about practices that was trivial for me after two years of proferssional work, while going into the details too much.
I used to really like Uncle Bob's talks, about SOLID and craftsmanship and the like. They were really informative. Lately though everything with these guys, Uncle Bob, Fowler, etc. are all fad things. All the developers that I looked forward to reading their blogs about software design either started jumping on whatever the bandwagon du jour was, or just deviating so much from talking about things that are relevant to me that I just can't follow them anymore.