I definitely agree that an architectural diagram can be more valuable than pages and pages of textual documentation, particularly for giving that at-a-glance overview. "A picture is worth a thousand words"
I'm a bit sceptical about automatically generated diagrams, or rather I know that they're great as far as they go but... I guess I'm thinking of complex systems with separate components in different code repos, and different layers of across a tech stack. To get a good overview diagram of something like that, you kinda have to draw it yourself. Why? Because it would be difficult/impossible for a diagram generator to infer information across all those things, and also because a diagram of a complex system requires some manual decisions and perhaps even a little artistic flair, in choosing what details to leave out!
But of course a manually drawn diagram is something which then needs to be maintained.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I definitely agree that an architectural diagram can be more valuable than pages and pages of textual documentation, particularly for giving that at-a-glance overview. "A picture is worth a thousand words"
I'm a bit sceptical about automatically generated diagrams, or rather I know that they're great as far as they go but... I guess I'm thinking of complex systems with separate components in different code repos, and different layers of across a tech stack. To get a good overview diagram of something like that, you kinda have to draw it yourself. Why? Because it would be difficult/impossible for a diagram generator to infer information across all those things, and also because a diagram of a complex system requires some manual decisions and perhaps even a little artistic flair, in choosing what details to leave out!
But of course a manually drawn diagram is something which then needs to be maintained.