2. I use to use Monodraw exclusively for making diagrams in source code, but over time I’ve become so comfortable with the tool, keyboard shortcuts, etc. that now I just use it for all diagrams. It’s a very nice tool.
// some comment
and // some comment
// additionally see ./diagram.png
Diagrams are often useful tools for communicating information. // some comment
// ... 25 lines of a diagram
and // some comment
// additionally see ./diagram.pngOr maybe they did, and there are advantages and tradeoffs to any approach.
I’m sure your unique insight must be right, though.
If you’re wondering why I need diagrams in source code, then the answer is I usually don’t need them but it helps. The only project where they were game changing was where we were using Neo4j as a backend and being able to clearly diagram the data model was really helpful.
In the Mapless guide, when I've kept it as text (as the first preferred way to have it done) it became challenging to make it work for all screen sizes and an image was the "good enough" approach for the case.