@sshishkin UML is just one tool. For some purposes, it's at least as good as anything else out there.
@logosity However lame the metaphor, what we commonly mean when we use the term definitely exists.
1
Separating architects to form a team that's separated from development is wrong. They can't and shouldn't be separated. #archflamebait
8
18
3
@nossipova I agree, but in many projects, coding is rightly not part of the architect's role because they're too big.
@TheSandyWalsh Agreed. Some people believe all architects are astronauts, though, and I disagree with that
@ewolff Yes, except the stuff you code yourself is only one part of the overall solution
2
RT +1 @alpengeist_de For each problem a perfect team has at least one person who understands it best. Architecture is a problem space.
1
@ewolff Excellent! disagreement! I think the whole multitude of runtime tools not programmed are equally important
1
It's stupid to conclude anything about an architect's skills because they do or do not call themselves "architects". #archflamebait
1
1
A software architect's most important concerns are not the programming language artifacts being created. #archflamebait
7
1
1
It's stupid to conclude anything about an architect's skills because they do or do not use UML. #archflamebait
5
3
A perfect team doesn't need someone who is a dedicated software architect. Therefore, most teams do. #archflamebait
2
9
1
Quoting @simonbrown: "Sofware Architect" is a role, not a rank #archflamebait
7
1
There are software architects who don't code, but there shouldn't be any who can't. #archflamebait
2
16
4