Slashdot Mirror

← Back to Stories (view on slashdot.org)

Ask Slashdot: Best Practices For Leaving an IT Admin Position?

Posted by Soulskill on from the many-bosses-are-panicking-while-reading-this dept.

An anonymous reader writes "I've been the server admin at a university for the past five years. Recently, I was given the chance to move from servers to networking, and I jumped at it. I now find myself typing up all my open-ended projects, removing certain scripts and stopping others. What would the community recommend as best practices for passing on administration of some servers? I am trying to avoid a phone call that results in me having to remote in, explain something, jog to the other side of campus to access the machine, etc. Essentially, I'm trying to cover all my bases so any excuse my replacement has to call me is seen as nothing but laziness or incompetence. I am required to give him a day of training to show him where everything is on the servers (web and database), and during that day I'm going to have him change all the passwords. But aside from locking myself out and knowing what is where, what else should I be doing?"

7 of 290 comments (clear)

  1. Wiki by cyrano.mac · · Score: 5, Informative

    Build an internal Wiki. You won't be free from questions since you can 't cover everything in a one day training session. I'd make that two half days with a month or so in between.

    1. Re:Wiki by Mysticalfruit · · Score: 3, Informative

      I agree with the wiki idea. You should also diagram your whole environment. Both the physical machines and also the applications and how they fit together. Then, unless you're going to let the guy follow you around for two weeks, you're going to have to provide support.

      --
      Yes Francis, the world has gone crazy.
    2. Re:Wiki by K.+S.+Kyosuke · · Score: 5, Informative

      I thought you are supposed to keep documentation of your setup since day 1, in case of a bus error.

      --
      Ezekiel 23:20
    3. Re:Wiki by dimeglio · · Score: 5, Informative

      Mod this up... As a manager, I would be a total failure if I didn't ensure all systems were adequately documented. Yes, it's probably the most challenging task next to HR.

      --
      Views expressed do not necessarily reflect those of the author.
    4. Re:Wiki by nahdude812 · · Score: 4, Informative

      Documentation is part of the job. Are you saying that managers do not give you time to do your job?

      Lack of documentation is a form of technical debt. Many managers are happy to accept technical debt if it means they can meet customer demands in the short term. I bumped into a good analogy on technical debt a few days back. It's short, and highly recommended. On Technical Debt - Now With Chickens!

      --
      Slay a dragon... over lunch!
  2. Already covered at length on Slashdot by Anonymous Coward · · Score: 3, Informative

    Here, here and here. :-)

  3. Re:Just Leave by justforgetme · · Score: 3, Informative

    I, inadvertently, experienced this "job security" once. It wasn't an experience I want to relive. It's much better to earn job security by being an outstanding contributor rather than by being the keeper of keys.

    --
    -- no sig today