I've gone back and forth over my career, and have one piece of advice:
Coming in as a "new guy", into a situation where there are existing senior
sysadmins (both in terms of expertise and seniority), who want to do
things their own way (and different from each other's way), is a hard gig.
(e.g. you want to introduce configuration management, or change control,
or some other good-practices thing that seems to have more immediate cost
than immediate benefit to the old-timers.)
It's easier if higher-up management is clearly telling everyone that this
is how it's going to be, and that this isn't just some weird whim of
yours, that it's an organizational priority and folks need to get on
board.
It's much harder if your management tells you they want to do it, but
doesn't back you up when others are reluctant/resistant. :^(
Another way to put that: As a manager, be wary of trying to impose new
things on reluctant sysadmins if you can't very clearly spell out why the
new things are good for them and good for the organization, and not just
some random thing you want to do. (One nice way to do that is to have the
support of upper management, but you need to be doing the right things
whether you have that or not.)
-Josh ([email protected])
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
