I would have to disagree. If you have a larger system, then onboarding, design discussions, and communicating changes will be more efficient if you have a consistent language and up-to-date conceptual understanding of the system compared to having to perform code archaeology and reverse-engineer the previous maintainer's intent each time you want to change something.
https://www.unravelled.dev/how-architecture-diagrams-enable-...
https://news.ycombinator.com/item?id=37222855