gaaclarke

Someone said it elsewhere but the point of UML was to remove the 5-10 minutes from every meeting where you describe the language of your diagram.

From the authoring side it helped that it was UML because that meant I had a standard language for defining the diagram with plantuml.

I work on a large project and I find it impossible to work on without UML. No one else on my team draws them and that doesn't make them any less useful to me. I just think some people think better visually. I wonder if it's related to being an autodictat. My programming grey matter was formed with concrete exploration as a kid as opposed to learning later in life when more abstract thinking is possible, who knows?

I suspect more people could benefit from using it if they spent time with it. I don't think I'm that odd. I was around when writing automated tests was becoming common practice and I saw all the resistance and hate for something that is hard to know the benefit of until you do it. That might be in play and I suspect a lot of the resistances was because enterprise software development tried to make it into some oppressive process.

Here's an example design I made last year that features UML diagrams that I think are useful: http://flutter.dev/go/multiple-engines

[flutter developer]

Hi, I audited the performance of the GPay app. Almost all of the performance issues in GPay are related to its use of vector graphics libraries which make Skia spawn many new shaders that have to get compiled. The suggestion was given to move to raster graphics but since GPay ships in many locations that are sensitive to app size, like India, they made the tradeoff to keep raster graphics.

That said there are some longer term initiatives to address this problem on Flutter's side and Skia's side since the problem can show up outside of vector graphics, it's just more unlikely.