On Taking a Configuration Management Position?

Bravo_Two_Zero asks: "I've recently been offered a Configuration Management position as a lateral (with a slight incline) move. I'm darn happy as an admin, and my heart really lies with system engineering rather than the more mundane operational concerns. But, the position is new, so I would have a chance to define many parameters. Also, it could lead to a management opportunity (if I'm interested) much faster than my current admin slot. It's a hideously complex environment, but I already live through that as an admin. Mileage will vary widely, I know, but I was hoping there might be a school of thought or two from some devoted Slashdot readers who perform or have performed the position. What did you do, and what would you change? And, to the broader audience, is this something you think of as a growth field, or is this just another layer of administrivia foisted on us by an unrealistic development model? Is there a book or other resource that professional Configuration Managers consider a must-read?"

Comments

Face facts

[Anonymous Coward]

You're doomed to a life which is primarily that of an IT janitorial staffer.

Sysadmins and their myriad variants are no more interesting, useful, or valuable than the folks who show up in the middle of the night to empty my trashcan. The only thing I'll grant is that they're generally more annoying, and often smell worse. The IT world was a far better place when programmers ran the shop. And it was a hell of a lot easier to just get something done.

Sorry, I'm just telling it like it is.