At Drupalcon yesterday, Jeff Eaton (twitter: @eaton) did a presentation on Drupal architecture, and talked about team roles for building a site. His list included the architect, who makes the higher-level decision on how to most effectively piece together the moving parts of Drupal to create a solution; the builder, who does configuration and setup; the developer, who does the module-level coding; the designer, who takes a concept (a design comp?) and turns it into working HTML/CSS (yes, this is a little different than the way we typically think of designer); the themer, who takes the HTML/CSS "design" and turns it into a working theme; and the "migration mule", who moves old data to the new platform.

I don't think Jeff's breakdown is any more or less legitimate than the way our team normally tends to view it, but it's always interesting to hear another's perspective.