Well, yes. A big part of the problem is the lack of terminology and models. "Software development" is a stupidly large scope, it encompasses activities that are

Well, yes. A big part of the problem is the lack of terminology and models. "Software development" is a stupidly large scope, it encompasses activities that are comparatively as varied as backyard astronomy and heart surgery. There are many different kinds of developers and many different kinds of software, but we lack the words to express the differences clearly. Which makes it that much more difficult to improve processes and standards. It's common for bromides and recommendations to be made as blanket statements applying to all software development, when it's clear that no one set of practices could possibly apply universally. Worse, many devs aren't even aware this is a problem, and few people are working on fixing it. We're deep in a morass that will take a long, long time to get out of.