Modern DevOps workflows move fast. understand systems faster onboard new engineers communicate infrastructure decisions visualize dependencies and workflows But in practice, many diagrams become outdated almost immediately after they’re created. manual updates version confusion difficult collaboration too much overhead for quick changes Lately, newer collaborative tools like DiagramDeck are trying to make diagrams more lightweight and easier to update continuously instead of treating them like static assets. That feels closer to what modern DevOps teams actually need. I’m curious how other teams approach this. Do architecture diagrams still play an important role in your workflow, or have they become mostly outdated documentation?