Sounds like throwing away the good parts of XML with the bad parts, and now instead using the pointless disaster called YAML

What I remember from UML distilled is that you shouldn't be too strict with following the UML spec - just use what works for you on a whiteboard. AML is an extreme form of that advice from @martinfowler , but it follows the spirit of it.

well, as long as i only use it as a means to discuss something f2f on a whiteboard, any "notation" is okay as long as it helps discussing. but if i try to transport this information over time or space, we need some more constraints for a shared understanding ...

What were the good parts: Use Case, sequence and/or class diagrams? For me, even the state diagram was helpful in some contexts.

I think, personally, UML failed because it got too vendor and tool focused. The association is strong that people got burned before they could discover the good bits.

"Big Design Up Front is a failed technique in almost all software development. The only exceptions are systems that are truly life and death." *closes window* This writer is part of the problem. #softwarecrisis

Agreed, and AML is incredibly pervasive. I still don’t understand why there aren’t more people trying to fix this problem. 🤷🏻‍♂️

UML failed because it tried to be too much. It should not be "executable"

To (re-)discover the "good" parts I found UML Distilled martinfowler.com/books/uml.h… by @martinfowler a very valuable resource.

AML has no relation to UML - it was there long before. And it will be for a long while I'm afraid.