Live data from Hacker News

Ask HN: What Has Replaced UML?

news.ycombinator.com

1–10 of 14 posts

Re: Ask HN: What Has Replaced UML?

#4
What replaced flowcharts? Um, pretty much nothing. We just quit making flowcharts, and we found that we could get by just fine without them. (In fairness, when structured programming replaced goto-based programming, we didn't need flowcharts nearly as often in order to keep track of what was going on.)

We mostly quit doing UML because for most people, most of the time, it mostly wasn't worth it. It didn't provide enough value to be worth the effort. So what replaced it was usually nothing.

Re: Ask HN: What Has Replaced UML?

#6
post #3

draw.io of course :)

There's a lot of truth in that :D

On the whole I think that the value of "diagrams as the source of truth" turned out to be almost non-existant for much the same reasons that mostly we prefer source code over visual programming environments.

Flowcharts were never all that useful (to me at least) because they were harder to read than the pseudocode!

I use draw.io (diagrams.net) or Miro depending on what's in commonest use at the current Org for informal data flow diagrams and the like. Does Microsoft have some kind of Visio descended monster in Office 365? I hope I never have to find out!

I use PlantUML¹ for sequence diagrams² and state diagrams. So much so that I wish GitHub and its brethren would support PlantUML natively in their flavours of Markdown.

---

¹The IntelliJ plugin is mercifully good

²Or swimlanes.io is quite good for these, especially for sharing ephemeral stuff

Re: Ask HN: What Has Replaced UML?

#7

Nothing. Because UML was pointless to begin with. As a medium to describe systems it was harder to understand that just a flowchart, and less specific than just reading the code code. A useless halfway house.

I tend to sympathise with this view, but I think one interesting thing which it tried to accomplish was code-generation or auto-verification, in a way it was an interesting early form of no-code in this regard

Also it is quite useful to understand sophisticated class dependency diagrams.

Post reply on HN