I guess one upside is that developers know how to make diagrams. Which is good.
I guess one upside is that developers know how to make diagrams. Which is good.
I think it was valuable. I suspect many engineers use simple diagrams in notebooks on a regular basis, and by introducing it very early in the degree it gave us another tool to help think about the code we were writing.
It wasn't actually UML, but I think it's a good thing to cover at the beginning of a course.
A simple diagram with components and how they communicate is pretty explanatory if you want a bird's eye view.
UML seems to try to be too specific and detailed when it comes to relationships, inheritances, hierarchies, etc but it's often just unnecessary, because every language/API/framework have their own way of dealing with details.
Not to mention that UML is often poorly specified and developers will not really respect the UML spec. It's like math, there are dialects. Programming language are better just because they have a proper parser that will verify correctness.
It's hard to understand why one would verify the correctness of an UML diagram.
But knowing the difference and being able to draw more or less accurate high-level sequence/flow/component diagram is vital skill for skilled developer.
>> Programming language are better just because Programming language is usually poor choice for explaining design of system
Same thing with design patterns: they won't solve all your problems but give engineers a common vocabulary.