Oh, just idle thoughts. I was reading a couple books, the gist of which are that topic. Got me thinking about this industry. Electronics is abstract, you can;t see electricity, you can only see the results of its work. You can measure it going past, but that is like footprints in the snow made by unseen animals. But if you can;t grasp it in your head, you will never get it.
Around here, I preach troubleshooting, and I make an effort to present the basics of that process. There are guys who know a ton more electronics than I do. I know a lot of that, but I don;t consider myself an electronics expert. I'll go head to head with anyone troubleshooting, but my days of looking at load lines and such was 50 years ago.
A lot of troubleshooting is using logic and reason. You have to pose if-then questions and then gather the evidence to prove or disprove that premise. Some time ago I lamented that kids today come out of school ignorant. I saw that as a problem. Industry sees it as a problem and complains about it. WHen I mentioned it here, no one seemed to care. "Google" they said. Aside from growing a generation of ignoramuses, I note we also never teach anything about critical thinking in our schools. No formal logic. I studied logic, but it was a college course. Not the sort of thing they teach in grade school or vocational college. Not even cause and effect.
I can forgive musicians, it is not their job to be repairmen. But it is disheartening when technicians don;t understand the implications of simple things like swapping the speaker wires to locate the problem with a dead channel. "My left channel speaker didn;t work, so I swapped the speaker wires and now the right channel doesn't work. Must be my speaker, right?"
I won't go into it, but any logic course will present a list of logical fallacies. They even give them names. "Affirming the consequent." If my power tube is shorted, the B+ fuse will blow. The B+ fuse is blown. I must have a bad power tube, right?" Wrong. You may have a bad power tube, even probably, but the blown fuse doesn't prove that. Other things like arcing sockets, shorted rectifiers, shorted caps, and so on can also cause this. "If the moon were made of green cheese, it would have holes in it. The moon has holes in it, therefore it must be made of green cheese." No, other things can cause holes too. Maybe this one. "Look out the front door of my shop, if it is raining, the sidewalk will be wet. The sidewalk is wet, therefore it must be raining. Right?" No, someone could have hosed off the sidewalk. The water main could be broken. Lawn sprinklers could be on. People get the logic backwards. You need to demonstrate the premise, not the consequent. "If it is raining outside, the sidewalk will be wet. It is raining outside, therefore the sidewalk is wet." That works. We set up an if-then, and if the IF is true, then the THEN will be true. Very different from stating the THEN is true so the IF must be as well. We verified the premise.
ANother one I see ALL the time is what they call "post hoc, ergo propter hoc." That is Latin for "after this, therefore because of this." Classic examples are "I was playing with an overdrive pedal and the fuses blew. Must be the pedal blew the amp." Or recently, "I had a wrong impedance speaker connected to my amp and a power tube blew. That proves mis-matching impedance blows power tubes." Hardly. The human mind is wired to see patterns, even ones that are not really there. COincidences happen all the time. "I changed channels too quickly, and (something) blew. How can I avoid blowing it up like that again?" You didn;t blow it up. If an amp is going to blow up, it will almost always happen while you are using it, and that means SOMETHING was happening at the moment it blew. But that doesnl;t make it the cause.
Correlation is not causality. Just because two things happen together doesn;t make them related. Ever flip a switch and at the same moment some noise occurs? Like a car horn outside, or a firecracker popping, or a big truck rumble, whatever. It can be momentarily startling, but related? No.
Not saying we shouldn;t look for patterns and related events, but we cannot assume they are related.
I saw a light in the sky, and I didn;t know what it was. Must be aliens from another planet. Yeah, must be... Argument from ignorance.
Gerald Weber says XXXXX, and he has written a lot of books. It must be true then. Argument from authority.
SO and so says XXXX. SO and so is an asshole, so he must be wrong. Ad hominem agrument.
If this is remotely of interest, the first hit in google for logical fallacies was reasonable:
Fallacies
Maybe I am just nuts and no one cares about this. To me, this is the heart of troubleshooting. We need our young people to be able to think. We certainly need our technicians to think. When I interview tech candidates, that is the one thing I am looking for, the ability to think and reason.
Around here, I preach troubleshooting, and I make an effort to present the basics of that process. There are guys who know a ton more electronics than I do. I know a lot of that, but I don;t consider myself an electronics expert. I'll go head to head with anyone troubleshooting, but my days of looking at load lines and such was 50 years ago.
A lot of troubleshooting is using logic and reason. You have to pose if-then questions and then gather the evidence to prove or disprove that premise. Some time ago I lamented that kids today come out of school ignorant. I saw that as a problem. Industry sees it as a problem and complains about it. WHen I mentioned it here, no one seemed to care. "Google" they said. Aside from growing a generation of ignoramuses, I note we also never teach anything about critical thinking in our schools. No formal logic. I studied logic, but it was a college course. Not the sort of thing they teach in grade school or vocational college. Not even cause and effect.
I can forgive musicians, it is not their job to be repairmen. But it is disheartening when technicians don;t understand the implications of simple things like swapping the speaker wires to locate the problem with a dead channel. "My left channel speaker didn;t work, so I swapped the speaker wires and now the right channel doesn't work. Must be my speaker, right?"
I won't go into it, but any logic course will present a list of logical fallacies. They even give them names. "Affirming the consequent." If my power tube is shorted, the B+ fuse will blow. The B+ fuse is blown. I must have a bad power tube, right?" Wrong. You may have a bad power tube, even probably, but the blown fuse doesn't prove that. Other things like arcing sockets, shorted rectifiers, shorted caps, and so on can also cause this. "If the moon were made of green cheese, it would have holes in it. The moon has holes in it, therefore it must be made of green cheese." No, other things can cause holes too. Maybe this one. "Look out the front door of my shop, if it is raining, the sidewalk will be wet. The sidewalk is wet, therefore it must be raining. Right?" No, someone could have hosed off the sidewalk. The water main could be broken. Lawn sprinklers could be on. People get the logic backwards. You need to demonstrate the premise, not the consequent. "If it is raining outside, the sidewalk will be wet. It is raining outside, therefore the sidewalk is wet." That works. We set up an if-then, and if the IF is true, then the THEN will be true. Very different from stating the THEN is true so the IF must be as well. We verified the premise.
ANother one I see ALL the time is what they call "post hoc, ergo propter hoc." That is Latin for "after this, therefore because of this." Classic examples are "I was playing with an overdrive pedal and the fuses blew. Must be the pedal blew the amp." Or recently, "I had a wrong impedance speaker connected to my amp and a power tube blew. That proves mis-matching impedance blows power tubes." Hardly. The human mind is wired to see patterns, even ones that are not really there. COincidences happen all the time. "I changed channels too quickly, and (something) blew. How can I avoid blowing it up like that again?" You didn;t blow it up. If an amp is going to blow up, it will almost always happen while you are using it, and that means SOMETHING was happening at the moment it blew. But that doesnl;t make it the cause.
Correlation is not causality. Just because two things happen together doesn;t make them related. Ever flip a switch and at the same moment some noise occurs? Like a car horn outside, or a firecracker popping, or a big truck rumble, whatever. It can be momentarily startling, but related? No.
Not saying we shouldn;t look for patterns and related events, but we cannot assume they are related.
I saw a light in the sky, and I didn;t know what it was. Must be aliens from another planet. Yeah, must be... Argument from ignorance.
Gerald Weber says XXXXX, and he has written a lot of books. It must be true then. Argument from authority.
SO and so says XXXX. SO and so is an asshole, so he must be wrong. Ad hominem agrument.
If this is remotely of interest, the first hit in google for logical fallacies was reasonable:
Fallacies
Maybe I am just nuts and no one cares about this. To me, this is the heart of troubleshooting. We need our young people to be able to think. We certainly need our technicians to think. When I interview tech candidates, that is the one thing I am looking for, the ability to think and reason.
Comment