I realized that the only UML diagrams really helped me back in school were behavioural diagrams: sequence diagram and activity diagram. They describe the hard p

I realized that the only UML diagrams really helped me back in school were behavioural diagrams: sequence diagram and activity diagram. They describe the hard parts of programming/complexity. Structural diagrams: do not "solve" anything really. (I know, they might be good for docs...) Also recently I started to think in terms of events. Look up FRP, "real OOP" and Cycle.js. For these, there is no standard diagram yet, so I am came up with my own - still under change. For that, I started to use Lucidchart, because its available on mobile/tablet as well in browser as desktop view and it gives full functionality. It's also really nice & snappy.