4 ms·
UML was all the rage for corporate IT in the 00s, so I learned it at a damn expensive course. the teacher concluded the course with: "and this is UML, there is
by franze 4y ago
UML was all the rage for corporate IT in the 00s, so I learned it at a damn expensive course.
the teacher concluded the course with: "and this is UML, there is a high chance you will never see or use it again."
he was wrong, saw it a few times again.
he was right, never used it again.
- xwolfi 4y agoThis idea we could work as little ants on a factory chain still persists to this day, but UML was the bravest most expensive attempt at "no-code" industrialization they've attempted. Sadly, again and again, it is all destroyed by the client-facing people: "guys, the clients cant see the button can you make it yellow" and its infinite never ending variations, which make our job more akin to a jeweller because no amount of pre-code rationalization will prevent post-production resculpting.
- morelisp 4y ago> UML was the bravest most expensive attempt at "no-code" industrialization they've attempted. Most expensive maybe, but "bravest" is surely something like spreadsheets or HTML.
- throw_m239339 4y agoIt wasn't even "no-code" since you actually had to write the implementation. Yahoo Pipes was more no code than UML (I dearly miss that service). It was a descriptive language, somehow useful to do nice charts, but the tools themselves were so bad the only reason devs used them is because of suspicious relationships between management and UML tool vendors... > which make our job more akin to a jeweller because no amount of pre-code rationalization will prevent post-production resculpting. Can I borrow that quote for my professional communications? This is so elegantly formulated.
- zozbot234 4y agoUML had activity diagrams as its own pipe-like notation for low-level code. Not sure whether it was widely used, though. Also in general, conveying high-level data models might be more of a priority than implementations.
- arethuza 4y agoI've only ever seen activity diagrams used by business analysts to capture system dynamic behaviour at a very high level. Mind you - as most people using activity diagrams have never heard of Petri Nets they were a bit vague about what forks and joins actually mean and were using them as convenient ways to join multiple arrows together....