![]() For a civil engineering project, there are well understood standards. Use other ways to describe it and you can easily introduce entropy, where the diagram gradually diverges from reality.Įven if there is an architecture diagram, it can be hard to get the level of resolution right. That's because code isn't like a building. Attempts at describing codebases have often been imperfect. Part of the answer is to do with history. So, why does it feel uncomfortably familiar for us as developers? Code should speak for itself, right? You'd be confused and, no doubt, you'd question the competence of everyone involved.īut, of course, this wouldn't really happen on a construction site. With that they advise you to start prodding around at what's already been built and then they leave for their next meeting. Then they show you a handful of hinges, a few pipe connectors, and an unopened bag of cement. They start by telling you that it's a steel frame building with precast panels on the exterior. ![]() You join a construction project as a contractor and the construction manager gets you up to speed. So, then, why aren't they a core part of every software development project? Why are software architecture diagrams important? Outward communication: they're easily consumed by non-hands-on stakeholders.Collaboration: they make it easier to onboard new developers and to work across different parts of a large codebase.Coherent vision: they provide a clear statement of direction and of decisions made.There are three core reasons why architecture diagrams make sense for even moderately sized codebases: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |