The joys of working remotely

I work remotely full time, which is pretty cool – the dress code is casual, my coworker is a cat, and nobody cares that I listen to The Dillinger Escape Plan all day. Unfortunately, it has its downsides – like when my coworker decides to sit on my keyboard, or when my home office (affectionately referred to as The Spider Hole) turns out to be an actual hole full of spiders, or when I need to get the IT department involved.

I was back at the office – the actual office, filled with real people and not just disembodied voices I talk to twice a week – for work last week, and I dropped my laptop off at the IT department for them to check out an issue. That laptop is still at the office, 1500 miles away.

A corrupted Windows Update was causing my computer to take about 90 minutes to boot. It can’t be backed out, because Windows doesn’t recognize it as a valid update. It can’t be pushed through or overwritten, because Windows doesn’t recognize it as a valid update. This was something the IT department hadn’t seen before, and they weren’t entirely sure how to fix it. Unfortunately, if an attempted fix fails… it takes 90 minutes before you can try again.

You can imagine how frustrating this is for someone trying to fix the issue.

After three days of unsuccessfully trying to get my laptop working (mostly staring at the “Staring Windows” screen), they gave me a temporary laptop to bring home while they tried to fix my old one.

This laptop’s great and all (it takes 60 seconds to boot!), but… it doesn’t have my stuff.

And I need my stuff to work.



  1. Chamelaeon Wombatowski says:

    Well that explains why you are not on IRC.
    You should get on IRC.

  2. I don’t get it. What’s the problem, just ssh in to the mainframe and…

    • falseflag says:

      I know you’re joking, but I’ve probably spent more time poking around green screen interfaces and working with EBCDIC files than most developers my age.

  3. alcoholfueledmachine says:

    damn i wanna hack that registry so bad!

    I’d think removing it from system32/?????, and any mention of it from the registry would fix it, but… UGH