3 ms·
I agree with the general direction that you are going, but consider at least one exception: http://en.wikipedia.org/wiki/Sequence_diagram http://en.wikipedia.or
by wglb 16y ago
I agree with the general direction that you are going, but consider at least one exception: http://en.wikipedia.org/wiki/Sequence_diagram http://en.wikipedia.org/wiki/Sequence_diagram. I find these sequence diagrams useful in whatever kind of systems that I am working with.
I feel that the disconnect is the presumption (which at one point in my career I was fully on board with) that Everything Is An Object.
Additionally, I have grown resistant to "methodology" more than anything. In my harsher moments, I argue that methodologies are insisted on by PHB who don't really understand programming and want something to insulate them from the reality of software development.
- nightski 16y agoSequence is only really useful when dealing with computations with side effects. So I have found the value of these diagrams much less as I try to keep the majority of the system referentially transparent. The other huge disadvantage to sequence diagrams is that they are very poor at describing concurrency, and only work real well for simple single threaded systems.
- wglb 16y agoSequence is only really useful when dealing with computations with side effects I disagree. If, for example, you are dealing with cooperating processes, then sequence diagrams are quite useful.