I use diagrams for two distinct use cases : - planning/outlining a solution - documenting/insight into the system I disagree that second can't be autogenerat

I use diagrams for two distinct use cases : - planning/outlining a solution - documenting/insight into the system I disagree that second can't be autogenerated - I've used class diagrams, database schema diagrams etc. to visualize projects, a lot of the time over the documentation - precisely because I can trust the generated diagrams to reflect current state. Documentation is nice for context but I'd take good visualisation tools over most documentation I've seen on projects I've worked on. Tooling to connect/validate documentation against code is non-existent, in my world at least. Maybe LLMs can change that down the line - have PR review against docs run as a part of CI/CD pipeline.