Machines and IT

People always look at me a little strange when I say that I work on sewing machines as well as IT and network systems.

     It's one of those things that you don't think would ever mix well, but in some ways, it makes sense. If you're a little weird in the head and have a lot of patience, they can kind of make sense. Or, it does in my head, anyway. I've never met another sewing machine mechanic that also does mid-range IT support. If there are any out there, I'd love to hear your opinions
     To me it all boils down to pattern recognition and knowing how it should, ideally, operate. If something is wrong in a network or with a machine, there will either be something telling that it's not running efficiently. In a machine, that might mean a skipped stitch. On a computer or on a network, that might mean that either is running a little slower than normal, or it'll pop an error code. 
      On a machine, power should flow in, make the motor turn, which turns the main drive shaft of the sewing machine, and then get transferred internally until it causes the needle and hook to make a stitch. On a network setup, you have your line come in from the outside world, and then hit the modem, and then hit a router, and then get transferred internally across ports or wireless until it eventually hits your computer/phone/etc. Depending on the network equipment, it could be easier or harder than looking at a sewing machine depending on the sewing machine. 
     Old shuttle bobbin treadle machines only had a few, comparatively, moving parts, while some home networks have their modem, router and wifi all combined in one unit where all you have to do is make sure it's plugged in and everything works fine. Then you have computerized home or computerized industrial machines versus commercial IT infrastructure. When computers get in the mix, the network systems I deal with will always and forever be easier to work with. 
​     Thank you for listening to my ramblings. Have a great week!