We're talking about two different types of programmer I think. You're talking about a maintenance programmer and I'm talking about someone who might be able to move the technology stack forward and possibly save some money in the process by finding a new and more efficient way of programming. I wouldn't expect someone who is happy doing the same thing over and over again in maintenance mode to be that person, although this type of programmer is a very necessary part of the team.

It might be a function of team size. I've spent most of my career in small teams, and so the flexibility to wear a couple hats at a time is relatively more important, and helps reduce the bus factor.