> I learned about UML in a course, but have never used it or seen it in practice as a junior developer. Sometimes I'll see a flowchart, but that's not too commo

> I learned about UML in a course, but have never used it or seen it in practice as a junior developer. Sometimes I'll see a flowchart, but that's not too common. Is this the same in other companies? Welcome to the industry! sobs in time constraints > So, is it a good idea to try documenting the code design through some sort of visualization? Yes, I think it's a good idea, though I'm afraid I don't have much advice on how to accomplish that. The problem I've always had is that there's so many ways to cut up a system. Some people want higher-level architecture diagrams, that show how all the various systems fit together. Some people want infra diagrams showing what VMs, DBs, cloud resources, etc., are all wired to what else. Some people want sequence diagrams detailing RPC/API calls between systems/component. Invariably, for whatever documentation does exist, the person wanting documentation wants the diagram that doesn't exist. I've tried PlantUML, but it is complete garbage when it comes to emitting useful diagnostics. Paired with a language that seems to be nothing but special case after special case, and the result is basically unusable.