> It allows programmers to be lazy, take short cuts and not think about good software architecture.

I think it has little to do with laziness, and more to do with the taboo of reinventing wheels. If there's a very generic and very broad solution to your very specific and very narrow problem, you're encouraged to use (or invent!) the very generic and very broad solution.

This leads to everything being abstracted to the point where most of your application does absolutely nothing. Just look at the call stack of a modern java web application. The depth of the layers of abstractions that you need to navigate to reach anything that performs any real work is vertigo inducing and nauseating.

It far from ideal and I agree that economics is behind it, but I strongly oppose the wording that it "allows" programmers to be lazy.