« A "BackBlog" | Main | Why Thunderbird Rocks? »

February 16, 2006

Alas poor Communication, I knew him well.

I frequently accuse myself of being lazy. I rarely take umbrage at this, knowing it's all in good fun. Despite my more sedentary tendencies, I attempt to give it the 'ole college try whenever I geek-speak to a client. There exists certain vernacular that is associated with our crew that I do not expect the rank and file user to have in their word-a-day calendars. Whenever services are suspended, interrupted or otherwise unavailabe to the Campus at large, an email notification is usually sent out detailing what had occurred. In Travis' Blog, he has several entries that deal with jargon, frustrations with understanding and seeming unwillingness for many users to read before reacting.

This was brought to the front of my mind today when I made a routine service call...

...the user was unable to open new files created on the i drive. In the background I could hear another person prompting the user to ask "does this have anything to do with the server crashing yesterday." Honestly, this ticked me off a bit. There were two issues with this. The first is that, for a period of 30 - 45 minutes, many users were unable to access their i drive. This was discovered and fixed within that 30 - 45 minute time frame. The server did not crash (any of the dozens of servers....), web was up, printing was up, etc etc etc.....

The thing that steamed me the most was that the person in the background ostensibly has a technical background. In other words s/he should have known far better than to make such a sweeping false statement.

Today, due to the implementation of ACL's, new files were being created without the execute bit. This was discovered quickly and a remedy was ready within a short time. I don't expect very many folks to know what that means. In the spirit of good fun, i propose we send the following from now on whenever a trouble is detected:

Dilbert

Posted by crowej at February 16, 2006 09:10 PM

Comments

Post a comment

Thanks for signing in, . Now you can comment. (sign out)

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)


Remember me?