3 ms·
I consider diagrams as being useful at different levels. There's the high level, conceptual style for either non-technical or CxO level discussion. There's th
by xarope 4y ago
I consider diagrams as being useful at different levels. There's the high level, conceptual style for either non-technical or CxO level discussion.
There's the larger, more detailed with lots of annotations for architects, engineers.
Surprisingly, the higher level the diagram, actually the longer lived it is. This is because it details intent, and not implementation.
The worst, IMHO, is when things are super-detailed, as you either need to ensure it's kept updated, or it will be outdated as soon as it's complete.
P.S. all this discussion reminds me of a short story from Borges: https://en.wikipedia.org/wiki/On_Exactitude_in_Science https://en.wikipedia.org/wiki/On_Exactitude_in_Science
- oaiey 4y agoCorrect, that is the way. I stopped doing code blue prints. They are either documentation only or you should look at code. There is however a area (think systems in a network) where typical IT Management / Cloud Management / etc fails. Here documenting a blueprint model helps with analysis (e.g. checking against reality)