Simplex3
12-10-2005, 10:12 AM
WTF is it with people needing to tell you what to do rather than report they're having a problem when in fact they don't have a f**king clue? I get calls and emails like this constantly. It's sad and pathetic when someone that doesn't know what they're talking about does it, but it's a freaking travesty when someone in your industry does it.
For example, I just got an email from a supposedly technical guy telling me that the DNS wasn't working for a link I sent him. So I spend 15m trying to diagnose DNS issues. Everything appears to be working fine. I jump on the firewall to see if something has changed there, nothing. While in there I DO notice that I haven't changed my NAT settings to the new internal IP for the web server. So, he is having an issue but it isn't name resolution. A problem he should have been able to diagnose by noticing that the name WAS resolving, but he was getting connection refused messages. Had he told me "I'm getting connection refused messages" I would have known immediately where to look. Had he simply said "something is wrong" I would have asked him a couple of questions and known where to look. But NOOOO, he has to show up with this false confidence and strip me of time in MY life.
A note to everyone: If you don't know WTF you're talking about don't act like you do. Don't tell your technical guy the Internet is down when the truth is you can't get to one web site. Don't tell your mechanic your alternator is hosed when all you really know is that you have to keep jump starting your car. The expert already knows you don't know what the hell you're talking about, that's why you've come to him. Simply give them the facts, not your amateur and stupid interpretation of them.
That is all.
For example, I just got an email from a supposedly technical guy telling me that the DNS wasn't working for a link I sent him. So I spend 15m trying to diagnose DNS issues. Everything appears to be working fine. I jump on the firewall to see if something has changed there, nothing. While in there I DO notice that I haven't changed my NAT settings to the new internal IP for the web server. So, he is having an issue but it isn't name resolution. A problem he should have been able to diagnose by noticing that the name WAS resolving, but he was getting connection refused messages. Had he told me "I'm getting connection refused messages" I would have known immediately where to look. Had he simply said "something is wrong" I would have asked him a couple of questions and known where to look. But NOOOO, he has to show up with this false confidence and strip me of time in MY life.
A note to everyone: If you don't know WTF you're talking about don't act like you do. Don't tell your technical guy the Internet is down when the truth is you can't get to one web site. Don't tell your mechanic your alternator is hosed when all you really know is that you have to keep jump starting your car. The expert already knows you don't know what the hell you're talking about, that's why you've come to him. Simply give them the facts, not your amateur and stupid interpretation of them.
That is all.