Mon, Oct 30 2006 12:32
Having the right "tude"
I'm not proud. And I'll be the first to admit I didn't have the right 'tude' for dealing with a support incident the other night.
I didn't have the right 'tude' the other night. I called into my ISP support line and didn't have the right "tude" for the first line tech support...and too many us forget that it's the first line that gather the info needed for the second tier. And sometimes we think that we should immediately get esclated up the ladder when sometimes there's some basics that need to be established. And then there are times that WE don't see the fact that at an appropriate time an escalation needs to be made... but the key element is AT THE APPROPRIATE TIME. In my case when the support engineer asked me for the model of the DSL modem, I questioned why they needed the information...but you see they needed to establish baseline information before I was sent to the second tier.
I was thinking again about this post and about this wiki entry and I'm not convinced that the issue is all in that source code isn't available or that the support engineer doesn't have access to the source code and all that. I think "oh but if we/they had access to the source code" is a cop out. I truly do. Show me a break/fix engineer and he doesn't write code. That isn't what they need to determine what's going on under the hood. If a SBS engineer was shipped to a deserted island and given the choice between source code and the entire library of the Sysinternals.com stuff.. I'll bet you a million bucks he or she would take the sysinternals stuff. Look at me... I can't read code worth a darn. The last time I coded ANYTHING up was a Cobol and Basic class in college... but now that Peter showed how to do a BSOD analysis? Man I can't wait until a machine blue screens on me (okay I'm weird..but it's fun).
Reading code is just that... code. Wanna see some? Go over to metasploit or milw0rm ...okay that's code right? Exploit code. Okay ...and? So there's source code for ya right? Mean anything other than bunch of stuff to someone who isn't trained to understand what it's doing? I'm just not convinced that the right place for what seems to me to be a coding issue was a phone call to a department used by folks like me. Break/fix stuff and all that. Not to mention IMAP is just a corner case and I don't see it much in SBSland. I think perhaps somewhere along the line the right "tude" should have been reached and instead of going up the PSS/Break fix... perhaps trying a more coding Exchange newsgroup would have been wiser? Escalation to a different division? And maybe asking for a consult with the Support Supervisor? I don't know...but I do know that .... at least in my opinion... having access to the source code wouldn't give you any better understanding here.
Code doesn't equate to understanding and implementation out here where it counts... ya know?
So next time ... including myself.. when you call into support...can you promise me that you have the right "tude".. google first....put in your "exact" error message in the search box. You may be surprised that someone else had your same problem and someone else has helped them find the answer. Try out http://www.eventid.net for event errors (buy a subscription to that site in fact)
There are no dumb questions. If you think it's a dumb question, it's just dumb because you can't find the answer. Always ask, as someone else probably has the same question that you have.
For the quickest resolution to your posted issues, please remember the following:
1. Include the following details about the Computer exhibiting the Problem:
Service Packs Applied:
Affected application version and Service Pack:
Other applications on the box:
Antivirus Software / Version:
2. Details about **other** Computers, for example a client machine, if applicable
Operating System and Service Pack:
Antivirus Software / Version:
3. Details about the Network, if applicable:
Internet Connection Type:
Number of NICs in the server:
Network Topology particulars:
4. Details about the issue:
Full, complete error message wording or screenshot:
When did the issue first occur?
What changes were made around that time?
Steps to reproduce if any:
Any Additional Information you think would be helpful
* * The fastest resolution is a targeted diagnosis of possible causes. * *
So be patient... and have the right 'tude' ....okay?
Filed under: News