Tag: it

  1. Have you tried turning it off and back on again?

    03 June 2019

    Disclaimer: The content of this post does not reflect my current employer, or any of my clients at present.  I've pulled details from my work history dating back about 20 years and stitched them into a more-or-less coherent narrative without being specific about any one company or client because, as unfashionable as it may be, I take my NDAs seriously.  If you want to get into an IT genitalia measuring contest please close this tab, I don't care and have no interest.

    Time was, back in the days of the home 8-bit computers, we were very limited in what we …

    Read more...

  2. Misadventures in IT.

    25 January 2012

    I don't ordinarily write much about work, mostly because it's not that interesting but also because it's a bad habit to get into, lest I let something critical slip and get in trouble. However, the last two days were sufficiently rough (and strange) that I feel that I have to write something about it, if only to give my fellow BOFHes something to go on if they find themselves in the same particular position I was. The past two days have been by far the strangest problem I've ever run into working in IT or information security.

    Let's set …

    Read more...

  3. Radio silence: a sign of the times.

    16 August 2010

    I wish I could say it's been quiet over here, but it's actually been relentlessly busy for Lyssa and I down here in DC. I think I overextended myself a little the weekend of the prototype Spaceblimp launch, which left me fighting off... something.. that kept me at a high fever and feeling run down most of the time. I did a little detail working on my car to cover up the myriad scratches and scuffs that accumulate whenever you park for long periods of time in an urban area. While the speeding edge of an SUV door doesn't actually …

    Read more...

  4. Don't put a box back together until you're sure it's working.

    14 August 2010

    Never bolt the sides back onto a computer you're building until you're absolutely, positively, cutting-charge-wrapped-around-a-major-artery serious that it's working exactly the way it's supposed to. Installing a server in the rack before the systemware's installed and patched and the servers are up and running is a sure-fire way to provoke a hardware failure or hard drive crash.

    Read more...

2 / 2