You don't have to be A+ certified to fix a computer. I was also shown how to fix computers but it was a long time before I became A+ certified. I was exposed to logic gates and procedural programming long before I ever went to college. I learned BASIC as a child because an uncle of mine gave me a Commodore 64 to play with. I spent days straight sometimes typing applications out of the Commodore magazine into the machine by entering hexidecimal code (there were no compilers for that system so it was either BASIC or machine language). But I had no idea why I was doing what I was doing. I heard about assembly language but didn't know what that meant when i was typing in those pages of code. I was basically regurgitating examples I read in the book and making minor tweaks along the way. That' doesn't help you to understand why something is written a certain way. Without truly understanding the fundamental principles then you'r just copy pasting examples together and you'll never understand why what you are doing is not working.
Hardware is physical and tangible and easier to understand... Especially nowadays PC computers are easy to work with internally if you are taught a few precautions and ground yourself properly. And every cable and card nowadays only fits one way. Its not like back in the 70s and 80s when ribbon cables didn't have notches on them!
Understanding how a computer works goes beyond learning how to service it. You can be taught how to service a machine and check for obvious trouble signs but to understand how even the hardware works means learning about logic gates and how they are assembled to design a CPU or RAM. Understanding how logic gates work and how the CPU (an electrical machine) is programmed is no different from learning a higher level programming language. It takes deeper understanding.
So if you want to learn then great! I encourage anyone to learn but please try to understand that programming is not a simple trade. It's a mind-set. Understanding why it does what it does is gradual as is with any learned skill. I and others here will be happy to help you out if you really want to learn but you have to be patient. The fact that you explode on the forums here because something didn't work or you didn't understand an example just shows us you don't have the discipline to learn. Nobody here should be expected to hold your hand either. That's what you pay educators lots of money at universities to do. Show me that patience and discipline and I'll help you as much as I can. The link you pasted for the Commodore is basic is an example of procedural code which is pretty easy to wrap your head around compared to oop. I use procedural code every day at work. The actual developers I support write in Java and procedural and oop are very different beasts. If you want to learn java then that is awesome! But you need a foundation otherwise your just copy/pasting examples. You need a solid understanding of the following concepts: objects, classes, abstracts, methods, class extending, method overriding, interfaces and instances.