Through college I worked as a technician at a local repair shop. Countless times I'd have customers come in spouting off about being computer science majors, computer programmers, whatever the title was. Then, a day or two later, they'd come back in with a broken Athlon XP cpu. I'd look at it for 15 seconds and say, yeah, you put your fan on backwards. Most likely the dye is cracked and you'll need to buy a new CPU due to physical damage.
A couple of jobs ago, I worked with a programmer who constantly bragged about what an "elite" programmer he was and how he was the only "true" IT person in the department since he had a degree in Computer Technology (lol!). Anyway, one day, he needed to have a development machine configured and needed Office installed. He came over and asked me about it and I handed him the Office CD and told him to go install it himself, as I wasn't a help desk or desktop support person and I was too busy to help him out. He could not figure out how to install Office and had to call the help desk.
This same "elite" programmer wrote a program for one of our really profitable business units for inventory tracking, IIRC. As usual, he was bragging and saying his stuff was the most important in the entire company since this business unit was our biggest money maker and used his program. Well, when he rolled it into production, performance was TERRIBLE -- I mean, when you loaded it and did a search, it would literally take 5 minutes per search. Being the "elite" programmer he was, he refused to believe he was at fault and started pointing at the infrastructure group (of which I was a member).
Well, I reviewed everything (network metrics with the network engineer, server resources, etc) and saw no evidence that the network or server was too slow for his stuff. He kept arguing with us and finally, the business owner called me directly to get the scoop -- I told him we suspected it was his software and were going to run some network captures during transactions to see if we could nail it down. The business owner then called the programmer and told him what I said and the programmer called me and yelled at me, calling us "too lazy" to fix the problem. I yelled right back that there was NO PROBLEM with the network and we were going to capture the transaction traffic to see what the problem was.
Want to guess who was right? The dumbass, "elite" programmer was using an ACCESS DATABASE SITTING ON A FILE SHARE as his backend database when I have told him -- NUMEROUS TIMES -- not to do that and use SQL. His program was literally copying over all 500 MB of the DB whenever updates were being made to it. He never even apologized to us for the name calling and left the company a few months later. I'm convinced that incident was such a blow to his ego that he couldn't bare to look us in the eye anymore.
The moral of the story? Don't assume anyone who professes to be a "computer guy" or "programmer" knows what they're doing. Make them prove it first.
