I think, the biggest issue with UML is that it helps with things that doesn't need such a ceremony and doesn't help in things where you would need it. Modeling

I think, the biggest issue with UML is that it helps with things that doesn't need such a ceremony and doesn't help in things where you would need it. Modeling database structures, class diagrams, interactions between components is usually something, any senior developer can do on a napkin without all the hassle, certifications, $500+ per seat tools and unique terminology. The trickiest things are designed much better, when you just open REPL and start playing with the design until you get it down. It's highly creative, speculative and flexible. So exactly the opposite of UML. In programming, the most exciting parts are things you couldn't productively solve with UML. And calling diagrams Masala is a huge misunderstanding why people mix contexts, views and representations. This is that creative, speculative and flexible part you exactly need.