Ten IT jobs to save up for those rare lulls

Ten IT jobs to save up for those rare lulls

Summary: It's not a bad idea to have a few IT tasks in reserve in the unlikely event that the daily grind eventually lets up, says Jack Wallen

TOPICS: IT Employment

 |  Image 7 of 10

  • Thumbnail 1
  • Thumbnail 2
  • Thumbnail 3
  • Thumbnail 4
  • Thumbnail 5
  • Thumbnail 6
  • Thumbnail 7
  • Thumbnail 8
  • Thumbnail 9
  • Thumbnail 10
  • Old software

    6. Test new systems and software
    We're always looking for new systems to use but we rarely have the time to test them out. It might be an open-source CMS you've been meaning to try for ages or some new groupware. When things are quiet you may finally get the chance to get those systems up and running and check them over to see if they're up to the job.

    Image credit: Churl/Flickr

  • Document systems

    7. Document systems and software
    Documentation is often left until last yet it's one of the most important tasks around. Without it, your systems end up relying on people's memories — and with the inevitable staff turnover, you could find yourself in a hole. When people leave, you still need to be able to log on to mission-critical servers. Take the opportunity of quiet periods to push on with the process of documenting your systems, software and users. In the end, you'll be glad you did.

    Image credit: Boetter/Flickr

  • Network diagram

    8. Audit the network
    You should know every piece of hardware on your network — or at least you should have them all recorded. Downtime gives you the chance to audit your network and create digital and paper maps of that topology. At some point, you'll be pleased you created these records. Just ensure that if the map includes passwords, it's stored in a secure location, such as a safe.

    Image credit: Shutterstock

Topic: IT Employment

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Related Stories


Log in or register to join the discussion
  • From my mainframe operating days...

    1) Play hoopla with write permit rings & a can of screen cleaner.
    2) Make enormous paper chains (Christmas time only).
    3) Read the entire 'Lord of the Rings' in a single night shift.
    4) Underseal car (yes seriously).
    5) Think up ever more daring practical jokes to play on the installation manager.

    happy days ....
  • Skittles with tapes and coffee cups.

    Old tapes so we didn't have to rewind them afterwards.
  • 2. Bad idea. Making up patch cables loses you your commission from the cable supplier.
    3. If you tidy up, other people can understand where the cables connect and you'll be less in demand.
    4. Yes to study, No to showing juniors around. They'll respect your knowledge right up until they steal your job and salary.
    5. Don't even think of cleaning up your working code. 99 % of the time you'll break the program, besides if other people understand your code, you might be out of a job.
    7. I agree with this but there's a danger that if other people understand your code, you might be out of a job.
    8. Absolutely but store it at home out of other people's (your boss and people after your job) access.
    9. Yes - but wouldn't you rather go to the pub ?
    10. Yes, but announce it as a planned strategy so that when an attack occurs you can use it to justify a budget increase or a higher salary.