All the UML you need to know
I've generally found UML to be a complete waste of time.I'd rather outline the major components of a system by drawing (on real paper) simple boxes and lines, or write the code that implements the system.Not sure what code-as-picture achieves - it's generally has worse tooling (less editable, less versionable, etc.) and tends to be used by 'architects' who don't write code, only for that UML to be essentially ignored by the coders on the ground.