A relatively new term "Devops" is starting to become more widespread. As with most new terms it means different things to different people (a bit like "the cloud" or "grid computing" does even now).

Recently we've been involved in a project where a third party were due to supply hardware using their "standard configuration". Cutting the story short, this is how the hardware should have been setup prior to being handed over to us:

Hardware specification should be agreed upfront:

• Vendor
• Model
  • You may want to check compatibility
  • Not just of the server itself, but management features, components and peripherals
  • Perhaps match existing models, or alternatively wait until the next generation ships

Overview

Tracks is an Open Source GTD(Getting Things Done) program. Speaking personally, I'm a huge fan of Dave Allen's book - the GTD system and way of thinking has made me far more productive and effective. More importantly I feel so much more in control - no more worrying! GTD really requires some programs to allow you to use it - Tracks has worked very well for us.

How to

Documentation is incredibly important, however many people seem to only regard it as backup in case someone leaves the company. That's only the tip of the iceberg. Good documentation can save vast amounts of time (a short note about an error could save hours of headscratching when the same problem strikes again). We've all said at one point "oh, I've seen it before, I just can't remember what the solution was".