Ask HN: How to get better at architecture diagrams

I haven't spent a lot of time drawing diagrams of the software I'm building, and I'd like to get better at it.

Currently I struggle to find the right level of abstraction, and things like dependencies/data flow/user events all end up jumbled together.

Are there any great resources for how to document code with diagrams?