Separating architects to form a team that's separated from development is wrong. They can't and shouldn't be separated. #archflamebait

Sep 28, 2012 · 12:18 PM UTC

8
18
3
Replying to @stilkov
@stilkov any proof of that?
1
@bzzam Proof? No. Experience to support this? Plenty.
Replying to @stilkov
@stilkov absolutely right, but IMHO it's also very important to maintain architects across projects, and not assign them to a single one.
1
. @CMontemuino I'd prefer architects do other stuff in the same project than do architecture in more than one
2
5
Replying to @stilkov
@stilkov architect isn't a position, it's a role you play - an arch team is a group of people who think they're too important to code.
3
7
5
Replying to @stilkov
@stilkov It can be useful if you need to protect them from deliverable-obsessed managers; A mental separation is really the bad thing IMO.
Replying to @stilkov
@stilkov It's like separating Siamese Twins: possible, but you risk killing both.
2
Replying to @stilkov
@stilkov I could not agree more!