4 ms·
Just 15 years here. I've worked at somewhere where they did put a lot of emphasis on UML diagrams. To the point they had a product where some of the code was g
by cs02rm0 8y ago
Just 15 years here. I've worked at somewhere where they did put a lot of emphasis on UML diagrams.
To the point they had a product where some of the code was generated from UML, not once moving from the initial design to code, but repeatedly every time the design became out of date. It became the project everyone tried to get away from and project all new joiners were thrown into the deep end on, many quitting as a result.
A couple of years ago I interviewed for a contract role with a sister company and they waxed lyrical about their love of "best practice" UML in the interview. I declined the offer, I'm too old for worrying about which arrow type to use when no one reading it's going to understand the significance anyway. I think there are a lot of attempts to move away from code because it's complex, but the bottom line is it's the best we have for now.