Search This Blog

Wednesday, May 13, 2015

Blame Squad


That looks like circumstantial evidence to me.  I could get an acquittal.




We see this stupid error message a lot.  It has caused me to intensely dislike the number 42 and the stupid beep that accompanies the error message.  I’ve even seen this error appear when no one is using the computer, which is how I know the machine has been lying.

The idea for this elite squad originated after I had an off-track incident with a Best Buy Geek Squad vehicle.  I wasn't a fan of Best Buy before the incident, and I am even less of a fan now.  The incident was not at all my fault in case you were wondering.


True geeks would have hired robots to push start the car.

Because the Geek Squad members were unwilling to resolve the incident on-site, I had to take drastic action.  I called in a strike team to talk down the Geek Squad, but they were delayed by traffic.

We needed a dedicated squad that was ready to handle blame like the toxic substance it is under every circumstance.  This had to be an elite team used to being blamed and capable of accepting the immense pressure that entailed.  Thus the Blame Squad was born.  The squad doesn’t just handle blame though.  That wouldn’t be efficient.

The squad’s special skill is blame shifting to maintain a perfect operating reputation for AcMo.  We are pursuing options to loan out the squad for special assignments in the future.  The squad could have fixed this situation without any hassle.



It should be obvious to any reasonable person that this bus only caught on fire because the design department thought it would be acceptable to tempt lightning by placing bolts all over the bus.  That’s just a quick example of how the blame squad does its thing.  Don’t blame AcMo if you don’t like the response.  AcMo has a squad for that.

No comments: