4 ms·
Maybe I need a better way to phrase it. High level architecture diagrams, user journey diagrams, low level diagrams, are probably all distinct topics. I feel
by urthor 4y ago
Maybe I need a better way to phrase it.
High level architecture diagrams, user journey diagrams, low level diagrams, are probably all distinct topics.
I feel all three are extremely important, but that's bordering on my opinion.
> but I find that low level diagrams usually tend to be a lot more trouble than their worth
Out of date low level diagrams are surprisingly useful.
One of the things that I've found is that, with extremely high LOC projects (LOC definitely measures complexity), you'll find that low level diagrams are worthwhile, at the cost of a time investment in generating them.
When/how to do them is a certainly a fine art. There's no right answer.
- scrapheap 4y agoIt sounds like our experiences differ when it comes to low level diagrams. While I'm dealing with a lot of complexity in systems I'm developing, they don't tend to have a high number of lines of code - or at least they don't once we get the architecture right :) Perhaps there is a correlation between complexity due to a high number of lines of code and benefits provided by low level diagrams. If there is then it does pose the question of when you should invest time in creating and maintaining low level diagrams and when it would be better spent reducing the size of the codebase.