3 ms·
UML failed because it was yet another attempt to "solve the software crisis", and the "software crisis", which never goes away, is this: Writing software defies
by bitwize 4y ago
UML failed because it was yet another attempt to "solve the software crisis", and the "software crisis", which never goes away, is this: Writing software defies the Taylorist conceit that competence should be vested at the organizational, not individual, level. Delivering good software stubbornly depends on people who are good at what they do; and if you apply the corporate favored technique of throwing a bunch of mediocre people together and forcing them to apply a standardized process laughingly called "best practice", expecting them to turn into top performers, you will be sorely disappointed and will not deliver good software. This has turned out to be a major bummer for middle managers, as good programmers are hard to find and often command higher salaries than said managers are willing to pay.
The intent of UML was to formalize and standardize the communication of all design aspects, from overall architecture to user interactions to class specifications so fine-grained, proponents assured us in the early 2000s that there would no longer be need for programmers because code generators will turn UML into working code that flawlessly implements the spec. This has the effect of constraining and constricting the design process itself to conform to something that will yield the desired UML artifacts, rather than letting designers communicate in a way that shows engineers how to build the product they want.