The reason UML died is that most code is written by people who do not care about bureaucracy or much else than writing code. UML was borne to have a language t

The reason UML died is that most code is written by people who do not care about bureaucracy or much else than writing code. UML was borne to have a language to specify the design so that somebody else can implement it, or at very least that's how I have seen it used. But this doesn't make sense in most cases. We have learned that the more efficient way to write the software is have one person both design and implement that design. And this means the UML has been relegated to serve as documentation only. Which we know nobody likes to do and few do it. The UML is still strong in organizations that write code to order or when comprehensive documentation is formal output of the process. This has been more popular in the past but these days companies that shape our development consciousness decided (and rightly so) that developing their products is core part of their business.