Every day I think there’s no way things can get any more ridiculous in the US, and every day I’m proven wrong again bloomberg.com/amp/news/artic…
2
3
2
13
I would call what you call “drawing” “modeling”, too. I’ve seen the kinds of models you refer to, but they’re only worth the effort in particular circumstances
3
Granted, it works best in an OO environment. But a package diagram to show dependencies between modules, a sequence diagram or activity to show a complex interaction, a state chart to show some status – nothing really OO-specific about any of these, is there?
2
Yeah, my guess is @simonbrown wouldn’t object if I called C4 “Essentials UML in disguise”
1
7
I’ve never seen an agile project that didn’t benefit from somebody drawing a diagram on a whiteboard occasionally during a design discussion
1
1
I remember there was some RUP tooling (can’t remember whether it was before or after the IBM acquisition) that was basically just a set of document templates, with an absolutely ridiculous price tag
2
Definitely an interesting discussion. While I think it’s generally true that good ideas will be adopted and bad ideas won’t be, the inevitable backlash after ridiculously unjustified hypes often leads to an equally ridiculous total rejection later
2
I agree. If SOAP were changed to UML, I could do a whole talk with that slide about “Things that are considered bad ideas, but actually weren’t” or maybe “Best examples of throwing the baby out with the bathwater” :)
1
1
Manchmal muss ich die MTV-Unplugged-Version von „Tag am Meer“ hören, weil das das absolut perfekte Stück für den Moment ist, und habe keine Ahnung, was danach kommen soll
2
20