The sysadmin team is not one role

A recent discussion led me to once again revisit the whole issue that a good sysadmin team is not made up of just one role repeated several times.  I may use different roles than are used in some of the standard books about the sysadmin team, but here are a few I outline:

• Developer: Someone who can script and automate things
• Writer: The person who knows how to write in English, be it change requests, documentation, or even reports for management
• Leader: Someone who can serve as a team organizer and leader, keep the team moving together as well as represent the team well up to management and help keep internal strife at a minimum
• Problem Solver: The person who has the mindset to solve problems, knowing what kind of steps to take to find the solution to even very complex issues.
• The hand holder: Someone who is good at dealing with irate users or managers.  Different from the writer because often this is more a listening role than a sending role.  
• Project Manager: Someone who can help manage complex projects, keeping different tasks in line, often used for efforts or companies where you don't have access to a dedicated project manager.

A good team should have people covering each role.  Ideally, a person should be able to cover at least two of the roles to some extent, but it is not realistic to assume that a sysadmin, especially a junior one, will be comfortable with all roles, even if you exclude the leader role.
The recent trend in sysadmin forums is to overemphasize the developer role, to the detriment of the other roles.  I've seen too much both now and in the past few years to think that such overspecialization is a good thing.