I've also gotten the impression that diagrams are used far less often these days. I myself use them infrequently, if and when they add benefit, and only with the formality that the situation requires.
From a pedagogical perspective, learning how to use diagrams like UML tends to be a great way to expand your understanding and insights into architecture and behaviour flows. They are also a (necessary?) stepping stone to grasping higher-level concepts like design patterns. At some point though, communication can more efficiently be done via those higher-level concepts than through (lower-level) diagrams. This at least in part relates to the notion of Wittgenstein's ladder (wikipedia page).
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've also gotten the impression that diagrams are used far less often these days. I myself use them infrequently, if and when they add benefit, and only with the formality that the situation requires.
From a pedagogical perspective, learning how to use diagrams like UML tends to be a great way to expand your understanding and insights into architecture and behaviour flows. They are also a (necessary?) stepping stone to grasping higher-level concepts like design patterns. At some point though, communication can more efficiently be done via those higher-level concepts than through (lower-level) diagrams. This at least in part relates to the notion of Wittgenstein's ladder (wikipedia page).