Re:Sequence diagrams, the only good thing UML brought to sof...
by bluGill on Thursday June 15, 2023 @09:06PM
(#36349500)
UML didn't help though because it is never kept up to date with what the code really is
[ Parent
| on HN ]
Re:Sequence diagrams, the only good thing UML brought to sof...
by ivan_gammel on Thursday June 15, 2023 @10:18PM
(#36350200)
How was it supposed to keep up? The most popular programming languages did not introduce concepts that are too hard to reflect with UML.
Or do you mean the problem of maintaining documentation?
Re:Sequence diagrams, the only good thing UML brought to sof...
by bluGill on Friday June 16, 2023 @12:28AM
(#36351246)
Maintaining documentation. UML cannot go even one developer-week without being updated, but the developer will often not do that. By the time your UML is a month out of date it is useless at best, and misleading at worst.
Re:Sequence diagrams, the only good thing UML brought to sof...
by ivan_gammel on Friday June 16, 2023 @04:12AM
(#36353136)
This has nothing to do with UML. Ad-hoc diagrams or plain text descriptions become outdated at the same speed, which depends only on the level of detail that you put in documentation and not on the format if it. If you cannot keep up with the changes in the code, you are choosing the wrong level of detail, that’s it.
Re:Sequence diagrams, the only good thing UML brought to sof...
by bluGill on Friday June 16, 2023 @09:16AM
(#36356054)
Ad hoc diagrams are much more likely to be tossed in the trash can after a week. If you keep them longer than the same problems apply. If you only keep them for a week than ad hoc is good enough as everyone still remembers what the symbols mean from when you created it, and the next time it won't matter that the symbols mean something different