3 ms·
As someone who learned and used a lot of the methodologies before UML, and developed CASE tools for some of it, looking at discussions of UML are painful, for t
by neilv 4y ago
As someone who learned and used a lot of the methodologies before UML, and developed CASE tools for some of it, looking at discussions of UML are painful, for two reasons:
1. It seems that almost everyone commenting has seen only bad uses of UML. Even before UML, there've always been people who used modeling tools without understanding them, there've always during OO era been people who really only wanted to see a class inheritance hierarchy, and knowing when to use the models and when to code or do other things is an art like much of the rest of software development. We've got a lot of people writing one-star Amazon Customer Reviews for a screwdriver, who've never seen a screwdriver used properly, and only know hammering.
2. When I try to use particular models and views of UML myself, the documentation and tooling I find in the time available borders on unusable, and I end up improvising what I need. Given that I know a lot of the influencing methodologies, and I've even developed tools myself, if this now looks like crazy enterprise sales&consulting cash cow nonsense to me, then I can't be surprised if other effective software engineers are turned off by what they see. But that's sad, because the value is there, just obfuscated.
- thematrixturtle 4y agoThis argument sounds very much like "the problem is not communism, all those countries just weren't doing real communism". And I'm not even being quite as flippant as it sounds about communism here. Communist economic planning relies on accurate central planning, which we've learned the hard way is essentially impossible at the scale of a nation state. In the same way, UML assumes you can meaningfully model a complex computer program in advance, which tends to fall flat back in reality where requirements are poorly understood and evolve continuously.
- cyanydeez 4y agoI think the most coherent argument for failure is the limited automated feedback between real code and the uml
- neilv 4y agoI don't know enough about communism to make analogies there. I do know that there are successful uses of screwdrivers, and that a screwdriver makes an ineffective and dangerous hammer.
- Existenceblinks 4y agoIt's not very conceptual too. Changing / altering database design (migration) of a production database is .. hmm like I'm not going to mess with those relations. Adding, deleting completely, is ok.
- fulafel 4y agoThe central planning problem isthought by some modern socialists to be solved: https://jacobin.com/2019/03/economic-planning-walmart-democracy-socialism https://jacobin.com/2019/03/economic-planning-walmart-democr...
- hbrn 4y agoIf they are so good at central planning, why do both Amazon and Walmart have 3rd party sellers?
- fulafel 4y agoIt's true that the rise in position of the 3rd party sellers puts a dent in the argument, but there was quite a long period without them that we can examine as recent history.
- xbfivhvu 4y ago
- blub 4y agoNo, why would you think that? One can model in UML anything between a bunch of classes, to a state machine to subsystems and entire systems. One can model architectures in advance or after the fact. One can model while brainstorming or when discussing a design with another developer on the whiteboard.
- pydry 4y ago>It seems that almost everyone commenting has seen only bad uses of UML. So what are the good uses? >When I try to use particular models and views of UML myself, the documentation and tooling I find in the time available borders on unusable That's kind of a sign, dont you think? Tools that programmers love and find useful tend to get improved.