Not really a thing these days IMHO. I know people used to be obsessed with diagrams and using them as documentation, or worse as part of some hideous model driven architecture monstrosities. I find I rarely consult them these days even if they are available, which in itself is extremely rare.
As for producing them, IMHO time spent on artifacts that don't co-evolve with software produced needs some really strong argumentation for being a distraction from doing that. So, I tend to not waste time on this. Whiteboards are nice but sadly my handwriting has devolved to the point of being completely useless. Pretty much the only time diagrams come up as a thing is when some customer or manager insists on having them, usually for box ticking reasons rather than any practical reasons. Usually feels like an epic waste of time and I've never really observed people getting actual value out of having them.
Besides, you can't really convey a lot of complexity in a diagram so their added value is limited to pretty much stating the obvious. Like, "we have a layered architecture involving a DB, a bunch of servers that talk to each other, etc.".
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.
Not really a thing these days IMHO. I know people used to be obsessed with diagrams and using them as documentation, or worse as part of some hideous model driven architecture monstrosities. I find I rarely consult them these days even if they are available, which in itself is extremely rare.
As for producing them, IMHO time spent on artifacts that don't co-evolve with software produced needs some really strong argumentation for being a distraction from doing that. So, I tend to not waste time on this. Whiteboards are nice but sadly my handwriting has devolved to the point of being completely useless. Pretty much the only time diagrams come up as a thing is when some customer or manager insists on having them, usually for box ticking reasons rather than any practical reasons. Usually feels like an epic waste of time and I've never really observed people getting actual value out of having them.
Besides, you can't really convey a lot of complexity in a diagram so their added value is limited to pretty much stating the obvious. Like, "we have a layered architecture involving a DB, a bunch of servers that talk to each other, etc.".