It's stupid to conclude anything about an architect's skills because they do or do not use UML. #archflamebait
5
3
@stilkov well, I consider ignorance to be an indication of a lack of a skill. There're better ways to communicate architecture than UML
3
@sshishkin Some examples of useful UML diagrams: package, sequence, state. Your alternatives being …?
1
@stilkov boxes, arrows and labels work fine for me and my target audiences
2
@sshishkin So using boxes and lines with defined semantics is somehow worse?
1
@stilkov rigid notation implies rigid architecture
1
Replying to @sshishkin
@sshishkin If you really believe there is a causal relationship, I guess we'll have to disagree

Sep 28, 2012 · 6:07 PM UTC

2
Replying to @stilkov
@stilkov I believe comprehension is hindered by notation details and flexibility is hindered by amount of effort invested
1
@sshishkin I can only assume you believe I'm talking about UML tools, not the notation itself. I'm not.
Replying to @stilkov
@stilkov This discussion is a perfect fit for architectureopenspace.de/
1
@sshishkin Interesting, don't know if I can make it, but will try