Just finished watching the Bad Mechanics and the RE: videos, and in the RE: video, ETCG made note of something I had been having the thought of myself. There seems to be a lot of crossover between IT and Automotive. I’ll take it a step further and note the crossover is a bit more prominent specifically between automotive technicians and hardware repair technicians.
I have done hardware repair for about 10yrs, though in the last year I’ve pushed more into web development/design. But I have seen a lot of what ETCG talks about in his videos. Very much the same it seems like people’s PCs, laptops, ect fail at just the wrong time and they just don’t want to have to pay what it cost for repairs.
I’ll admit, a good majority of my time I did not interface with customers. I would be in a “shop” where I was given a product, a problems description, and basically told to have at it.
Another striking similarity is brands. ETCG mentioned in a few videos how your specialist who work on one brand of car will know that much more about the quirks of that brand than someone who works on all the brands because they just see it day in and day out instead of once every few weeks or months. This is very much true in laptop repair, at least more so than say desktop. One brand you may pull two screws to get a hard drive out whereas another you may have to completely take everything out.
I did spend a 4yr period as a field technician though, where I did directly interface with business customers. There were some good understanding customers, but a lot of them were really frustrated and even hard to deal with because understandably, while their product is broke, they cannot get any work done. Sometimes you the service note may be for a dead hard drive, but then you get out and start looking at it and find a bunch of other stuff is actually a problem. Or you get sent out with a hard drive and find out that wasn’t the issue at all. Visa-versa, I’ve had many instances where they ticket says a motherboard is bad and on inspection you find out that the power plug is just bad
Another fascinating similarity is simply the enthusiasm. When I started doing hardware I was pretty excited about it, as time wore on it became just another job. There were IDGAF days, the whole 9 yards. In the profession, I’ve seen hardware techs who really try to do a good job an look out for the customer and I’ve seen techs who just slap things together to collect a paycheck.
Let me tell you, the ones who just slap it together, were really frustrating because then when the product comes back in a week or a month, now you have to not only fix the problem, but also fix their work too. I remember one time in particular… A tech replaced a CPU, the laptop came back for overheating issues and when I looked, they hadn’t bothered to take the cellophane backing off the thermal paste pad.
A big issue in hardware repair comes at commision vs standard pay. When you have people who are paid per job completed, the amount of slop work goes up significantly because they want to just churn out as many jobs as possible to make more money, as was the case of the person who did the CPU noted above.
This is already getting way to long, but a final similarity I found interesting was people gunning for (which was mentioned in a different video). Even among friends, it was always hard to know who really had your back and who would throw you under a bus. Also I’ve been let go from a number of positions for being too ‘slow’ because I take time to make sure the job’s done right. Ironically, in some positions I’ve been in, people who do slop work got celebrated for having so much done. They would basically send something out and then when it broke in a week slop it again and send it out, thus getting multiple credit for doing the same work. I’ve seen people make things up, say a stick of ram unrelated to the current issue was bad so they could open a second ticket and get double credit.
Even with all that I always had a personal belief much like ETCG noted, that techs already had a bad name as it was, so no matter what the other tech may have done, never blame the other tech.