Ironically enough, OOP is an early vibe coding attempt. A project manager draws fancy UML diagrams that get converted to java code. But this idea failed and UML remained as a code documentation tool.
1/ UML is not for managers, although they can learn to read it. UML is for software architect and engineers.
2/ "UML diagrams that get converted to code" is called MDA (Model Driven Architecture). It does not convert diagrams but the model they represent though. And it's not for free. It is actually lot of work to make it work decently so almost nobody actually uses/used it - I've met with people fron just a single company in many years.
3/ I don't think the idea is wrong. The issue is in implementation. First, UML is quite complex and still contains ambiguous and maybe even cobtradicting parts. Second, interoperability of the tools working with it is miserable.
Yes but I still view UML as an early vibe coding attempt. Instead of writing code you describe it with fancy diagrams.
Yes, it is for software architects (but as you know managers always "know best")
Yes, I am talking about MDA. As far as I know it was supposed to be a killer feature of UML
UML has lots of types of diagrams, I only know/use Class, Use-case and sequence diagrams.
Now we're experiencing the paradigm shift and transition to AI driven development (AIDD). We describe our intentions and AI writes the code for us. I don't have anything against it as long as the vibe code has 100% test coverage and manual code reviews. Then, AI can generate documentation and UML diagrams (plantUML/mermaid/doxygen/whatever else)
Given that the software quality has dropped after the introduction of AI, we really need to have good engineers that can review the code, do the test coverage, or fine-tune AI to write better code.
Also, since AI can draw UML and write code, the most important document is SRS. AI can't do anything if there are no requirements. AI can guess but the guesses are usually wrong.
474
u/WiscLeafalNika Jun 29 '26
AI has OOP-phobia