Some of the things I don’t miss with my old employer

CSC - My job went to India and all I got was this lousy shirt. Some of the things I don’t miss with my old employer:

  • Being “re-org’d” in May 2007 while being at a workshop in England.
  • Going from a non-billable position to being required to be 100% billable.  Found this out via email, my manager couldn’t be bothered telling me this face to face.
  • Bedridden with flu for 2 weeks while on annual leave.  Manager didn’t want to reimburse the leave.  And didn’t.
    This was the straw which broke the camel’s back.
  • Seeing a colleague berated in email by our manager, then the email mysteriously disappearing from the email system.  (no, the email system didn’t have a recall function)
  • Manager passing off work as their own, to senior management.
  • Not a word from my team lead or manager when they visited Melbourne
    eg. not “sorry to see you go.”
  • The last year truly sucked.

On a positive note:

  • worked with some truly great people.
    JT – darn fine Team Lead, who’s now working as a architect.
    The guy from Oklahoma.  His capacity for quality work output amazes me.
  • was proud to have led a couple of great guys.
  • worked with some cool technology.

Bookmark and Share

Purpose: Install new data line set, and switch all 5 sites across.

1089 parts… just another Sunday night …
1945hrs – Travel into work.
2030hrs – Some bastard parked across our company car park driveway.
2045hrs – Find and pay for another car park, attend work, sign in.
2050hrs – Make up A4-sized “You have parked across a driveway” sheet, and liberally glue to offending windscreen.
2105hrs – Advise project manager that I’m ready to test the network change.
2145hrs – “We have a problem”
2146hrs – “Ummm, it’s a cabling problem.”
2230hrs – “Ummm, we’ll need to do this again in a couple of weeks.”
1000hrs – (following day) Cause: insufficient patch cables on hand to perform change.
Translation: we forgot the frickin cables.

Bookmark and Share

Hitting the Panic Button

panic button “Bong! Bong! Bong!” goes Windows Messenger.
“Ring! Ring! Ring!” goes the phone.

Yes, my boss has hit the PANIC BUTTON.

Seems we have a customer having some Windows XP SP1 network problems.

Why did I catch the call? Well I’m problem-solving guru. Not that I actually work with day to day desktop problems anymore., but I’m good never-the-less

Now diagnosing the cause of the problem is like that Japanese play Rashômon, every one has a different opinion of the cause.
And it’s about as much fun as herding cats.

The actual cause of the network problem:

  • we replaced a faulty server with a brand new shiny one.
  • we upgraded the software to Windows 2003 R2
  • the customer is still running Windows XP SP1, even though it’s out of support in less than a month.

My solution? Upgrade desktops to XP SP2, or throw a shed load of patches onto the current XP SP1 installation.

My boss might be getting an actual PANIC button for Christmas.

Bookmark and Share