Comments on: Seagull Architects and the Tumor Model http://www.techdarkside.com/seagull-architects-and-the-tumor-model Struggles of a Self-Taught Coder Thu, 26 Aug 2010 07:33:27 -0700 hourly 1 http://wordpress.org/?v=3.0.1 By: Five Measures of Competency http://www.techdarkside.com/seagull-architects-and-the-tumor-model/comment-page-1#comment-15605 Five Measures of Competency Tue, 01 Apr 2008 21:54:33 +0000 http://www.techdarkside.com/?p=149#comment-15605 [...] talk in abstractions - instead they get involved in the actual problem at hand, avoiding seagullery. A person who avoids dealing with problems by appealing to higher authority, delegating, or [...] [...] talk in abstractions – instead they get involved in the actual problem at hand, avoiding seagullery. A person who avoids dealing with problems by appealing to higher authority, delegating, or [...]

]]> By: David Christiansen http://www.techdarkside.com/seagull-architects-and-the-tumor-model/comment-page-1#comment-15437 David Christiansen Thu, 30 Aug 2007 21:37:53 +0000 http://www.techdarkside.com/?p=149#comment-15437 I came across the term in Johanna Rothman's book, Manage It! It comes from the tendency of seagulls to swoop in, poop vociferously, and fly away with no concern for the mess they left behind. Why is it seagull architect and not pigeon? I don't know. Maybe it's because it sucks more to get crapped on at the beach than downtown? I came across the term in Johanna Rothman’s book, Manage It! It comes from the tendency of seagulls to swoop in, poop vociferously, and fly away with no concern for the mess they left behind. Why is it seagull architect and not pigeon? I don’t know. Maybe it’s because it sucks more to get crapped on at the beach than downtown?

]]> By: Dennis Gorelik http://www.techdarkside.com/seagull-architects-and-the-tumor-model/comment-page-1#comment-15436 Dennis Gorelik Thu, 30 Aug 2007 17:45:19 +0000 http://www.techdarkside.com/?p=149#comment-15436 There is another term for Seagull architect: "Blah-blah architect". Just talk and no action. I meet these parasitic species quite often, especially in buerocratic environment, when career success does not depend much on project success. I think the major reasons for encountering Blah-blah architects are: 1) Software development is quite complex. 2) The outcome of bad or good architecture is not visible immediately. As the result -- it's a tricky task to distinguish between practical architect and blah-blah architect. BTW, where did "Seagull architect" name come from? There is another term for Seagull architect:
“Blah-blah architect”.
Just talk and no action. I meet these parasitic species quite often, especially in buerocratic environment, when career success does not depend much on project success.

I think the major reasons for encountering Blah-blah architects are:
1) Software development is quite complex.
2) The outcome of bad or good architecture is not visible immediately.

As the result — it’s a tricky task to distinguish between practical architect and blah-blah architect.

BTW, where did “Seagull architect” name come from?

]]>