Without perfect information making a hypothesis and then confirming it is a way to get more of it.
That’s actually not true. Or… I mean it is technically true that that is a way. But it’s far from the best way. I’ve observed this a few different times at various software shops; I actually recommended not long ago that someone make it a topic for a work presentation they had to give because to me it is such a key thing for being able to solve problems in engineering.
The main point is this: There are broadly speaking two ways of approaching problems. Method A goes as follows:
- Decide, more or less at random, what is “probably” wrong
- Act on that assumption
- If your action didn’t work, then come up with a new “probably,” rinse and repeat
Method B, to me, is much preferred:
- Investigate with the primary aim of figuring out definitively what is wrong
- Fix the problem
I’m sure I don’t have to lay out the rest of the presentation. The summary is, I don’t agree with the “make a hypothesis at random” strategy. Now I’m not stupid enough to go out and buy a new HDMI cable or whatever weird thing people are telling me very directly to do here, meaning to act on their “hypotheses” to help them very slowly gather nuggets of information when each one doesn’t work. But yeah it does irritate me a little here. I’m short-tempered about this one specifically because I’m already irritated because it involves my computer being not completely working. And while I do actually have a couple of theories now after looking at it today, I still don’t really understand what’s going on or how to fix my computer, which is its own type of frustrating.
(I should say – this whole thing with touching the case is important to me because my audio system is crashing sometimes when playing over headphones, and I think now that this is related. I’m not bothered about it just because my computer is doing something surprising.)
So if the laptop actually is not connected to anything else just touching the case with a grounded or even very not grounded leaky power supply should not produce enough current for anything to happen.
Completely agree. You need to go up and speak to the people higher in the comments who seemed to think it was not an especially big deal (“not that common but it can happen”). Those guys I definitely didn’t agree with. This behavior, to me, is very weird.
Given pretty much everything is soldered on and the modular components (wifi/ram/ssd/keyboard) would straight up just not work without common ground I doubt that’s it.
That’s also not completely true. So I have been reading up; I am still not really that up to speed on how the EE works, but it honestly sounds to me like some failures I’m experiencing including this particular bizarre behavior would be explained if there was a problem in the “chassis ground” in some components. It’s different from “signal ground” or the main ground plane of the PCB; without those, yes, nothing would work.
Think of it like the third pin of the thing you plug in the wall. If you cut off the neutral pin (the bigger of the two “main” pins), nothing’s going to work. That’s the signal ground. But if you cut off the ground pin (the circular third one), then things will “kind of” work, but not safely and you may have weird problems sometimes. I’m saying that my current working theory is that some component is missing its connection to chassis ground, the “third pin” in plug-socket terms.
That’s a sad theory because I don’t think I am really qualified to diagnose or fix it, if that’s what is happening. And quite possibly I am wrong, I’m just throwing around EE stuff that I don’t understand. But I would be happy to share the details of my totally-unqualified-at-EE thoughts on it and how I am proposing that they could relate to the problems I am having with my headphones, if you want to hear.