Nicholas Carr's Blog on "Large Software" = "Failed Software"

Here is a fun debate item: does "Large Software" equals "Failed Software"? Here is what this guy, Carr (the father of "IT doesn't matter", for those who don't know) proclaims in his blog: Rough Type - Nicholas Carr's Blog: Down the drain: "... you should always create software to solve the day-to-day problems faced by the actual users, not to meet big abstract organizational challenges. Solve enough little problems, and the big ones take care of themselves. "

On the other hand, many software vendors say: "... but shooting elephants is sooo much more fun than swatting flies and squeezing rodents in their holes."

Discussion anyone?