Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Like actual UML or UML-ish diagrams?


That’s the real question.

I avoid even trying to use UML , because it just ends up in an argument about whether I’ve used it correctly, and is a distraction from whether the information displayed is correct.


That is picking on the details.

I think most of people were doing UML-ish diagrams anyway because unless you really have a use case for it it is just wasting time to go full "UML".


Probably a bit like REST.

Seems obvious at first sight, then you get 80% right in 20% of the time, and don't bother to put in the last 80% of time to get to 100% understanding.


It is also like using fancy vocabulary. You might sound smart and all but most of people will think you are silly. Then there will be a lot of people who won't understand you and there might be more problems because of that misunderstanding.

When you will make perfect REST API there will be someone who will not understand it and will just try things and he might make a big mess.

The same if you will create beautiful, perfect, UML diagrams. If no one else is proficient using them and it is only you. There is no advantage of working this way.


i don't think it is. the article isn't saying the diagramming is dead. it's saying uml is dead.

using boxes and arrows isn't uml (full uml) and as you say, it's wasting time to go "full uml," which is why it died. diagramming will live on, even if inspired by uml.


He calls it masala in his post. But you know what? Masala is just UML. Because the L stands for language, and languages evolve when used (or die when not used, not when used differently)


by that logic, i can start using braces in python and it'll still be valid python because languages evolve.


You mean, using something like bython[1]?

[1]https://github.com/mathialo/bython


Never say never :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: