@thejayfields @logosity @myfear I think there's a strong relation to the team you're part of. If it's great, no architect may be needed
@TheSandyWalsh Interesting post, U guess I agree with all of it. As I wrote, a perfect team doesn't need an architect.
@MMahlberg Disagree. If it only supports the creation, its value ends once the system is there
1
@thejayfields I strongly disagree because you judge a whole number of different people by a label they may or may not have chosen.
1
@TheSandyWalsh It's a role. You're doing different things. Doesn't mean you can't be both, nor that you need it as a title.
@thejayfields I strongly disagree. There are people who are bad at their job at every level and in every role.
@thejayfields @logosity I guess what I'm trying to say is that not everyone who self-identifies as an architect is necessarily an idiot.
4
. @CMontemuino I'd prefer architects do other stuff in the same project than do architecture in more than one
2
5
@TheSandyWalsh There is a wealth of knowledge about software architecture and architects. Don't see what's gained by dropping the term.
@sshishkin Some examples of useful UML diagrams: package, sequence, state. Your alternatives being …?
1
. @logosity One common problem IMO is throwing out the baby with the bathwater because all of the crap done under the label "architecture"
@logosity Architecture is not about patterns. Architecture is what you tell me about if you have 30 minutes to explain your system.
1
There is absolutely no conflict between the concepts software architects, architecture, and Agile development. #archflamebait
1
1
Documentation in itself has no value unless its purpose is to operate and maintain a running system. #archflamebait
3
6
2