News for hackers. Stuff that matters.
Re:PG's Rarely Asked Questions by nl on Sunday September 18, 2011 @09:17PM (#3011806)
Specialization is an adaptation that seems wasteful when it isn't needed but makes a huge increase to efficiency when it is.

Yes, architects and test designers can be a waste. But they can also act to make developer's lives easier.

Good architects can code, but usually act at a higher level - making sure different projects (a) know about each other, and (b) work together. That's important because teams tend to focus on their own success without always taking account of the bigger picture.

Re:PG's Rarely Asked Questions by Volpe on Sunday September 18, 2011 @10:50PM (#3012018)
> Good architects can code...

Is synonymous with good developers are also good architects.

I think (if I can articulate my thoughts correctly) my meaning was, that there is an obsession with breaking tasks into specific roles that are then the sole responsibility of one person. To the point of inefficiency (given the number of people you have to talk to for a given feature).

I don't agree that specialisation is wasteful (for the project at least). If it isn't needed, the person can still be a 'standard' dev. But if it is needed, they contribute more. (The only waste is to the individual if they specialise in an un-needed skill).

Re:PG's Rarely Asked Questions by johnx123-up on Monday September 19, 2011 @02:45AM (#3012608)
> Is synonymous with good developers are also good architects.

But, most architects are lazy genius. Only way to utilize their skills is not allowing them to code, but letting them designs and coach.