No UML we will not miss you. Maybe architectural astronouts will miss it, but hardly anyone else.
UML was just another bad idea that wanted to reduce the complexity on business logic part but what it did in reality was:
- Add enormous complexity of UML on business logic
- Add enormous overengineering and complexity on "legoland" (code blocks that needed to behave by the UML spec)
- Add enormous complexity on a coding part (developers suddenly were no longer aware of the whole process and were not only doing stupid mistakes but were unable to optimize what could be optimized.
I was working on 200 million revenue project that was destroyed by architectural astronaut with "political connections" to upper management. At the end the whole dev. team was frustrated (those that brought the project to 200 million), top people were leaving and due to "generalization" of each "block" each feature took at least twice the time to deliver without all the overhead to actually get the conformation from UML "experts" what they actually need.
The further you go from the ground, harder it is to see the details. Once you float so high in space that Earth is only a ball, all problems / complexity / people / ... disappear. But it doesnt mean they are not there. You just cant see them. You are just playing with the ball.
The funny thing is that people just never learn, I bet there is a few thousands project running just now that want to do something similar as UML did.
Architects that have authority over development but work at arms length from the actual developmwnenr effort aren’t UML’s fault, and haven’t gone away in the same bureaucratic environments they have always been found just because UML got less popular. They may now communicate (and force developera to communicatr with them) using diagrams with ad hoc symbology and inconsistent annotations esther than a structured visual language, but they still exist.
UML was just another bad idea that wanted to reduce the complexity on business logic part but what it did in reality was:
- Add enormous complexity of UML on business logic
- Add enormous overengineering and complexity on "legoland" (code blocks that needed to behave by the UML spec)
- Add enormous complexity on a coding part (developers suddenly were no longer aware of the whole process and were not only doing stupid mistakes but were unable to optimize what could be optimized.
I was working on 200 million revenue project that was destroyed by architectural astronaut with "political connections" to upper management. At the end the whole dev. team was frustrated (those that brought the project to 200 million), top people were leaving and due to "generalization" of each "block" each feature took at least twice the time to deliver without all the overhead to actually get the conformation from UML "experts" what they actually need.
The further you go from the ground, harder it is to see the details. Once you float so high in space that Earth is only a ball, all problems / complexity / people / ... disappear. But it doesnt mean they are not there. You just cant see them. You are just playing with the ball.
The funny thing is that people just never learn, I bet there is a few thousands project running just now that want to do something similar as UML did.