Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
vane112815yWhen I use UML I mostly use flow diagram to see the big picture of communication between multiple services, describe some complicated process.
That helps me understand and solve some problems also this diagram makes easier explaining people how data traverse from user trough the applications, optimize some processes etc.
Good method / class naming and code convention is still better then every diagram. -
C0D4682465yUMl isn't suppose to explain code, it's suppose to explain how processors work at a high level so even a business user could vaguely understand that, "data a" goes from your screen on the left, down this chunk of checks, into a service... or 6, and then gets spat out over on the screen to the right in that system / application a few seconds or minutes later depending on the number of processors in between.
Code is low level compared to this. -
I hate it when there's a project with tons of detail documentation but nothing tells what it even does and how the overall architecture looks like. That's when you don't find the forest because all those trees block your view.
-
toor1275yIf you work for the government, some projects have to have complete UML diagrams for things as low level as classes. 🤮
Are there more people here who prefer codual over visual?
UML diagrams are fun and all, but I personally prefer to have a code example over an uml diagram when it comes to a few classes that work together. Not exactly sure why I prefer it that way, in my head I translate uml to code in order to understand it better and if you show me a piece of code I don't have to do that translation.
I wonder what you guys' thoughts are 🤔
question