= 27d567bc2d48d9f40e9ccc20ea370b15)
Vaniver comments on How do I "test it"? - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (13)
The situation that calls for testing feels like being confused or curious.
The thought that generates a test looks like this: "If X is true, it is (more/less) likely that Y is true. I can examine Y by doing _."
For example, one day my computer was running slowly. There were a bunch of possible explanations, but my room was hot, dusty, and it'd been a long time since I cleaned it out, so I suspected the slowness was because of overheating. "If my computer is slow because of overheating, it is less likely that it will be slow if I remove the case to increase ventilation. I can examine that by removing the case." I pull the case off, and the computer runs normally again.
Most of the examples tend to be banal, though, and so I've forgotten them. (Not quite sure how I remembered that one.)
Ideally you should also point a room fan at the inside of the computer after you take off a panel. Some systems, especially small form factor PCs and rack mount servers, actually need the case in order to be properly cooled. Removing a panel means that e.g. an exhaust fan no longer forces air across passively cooled components near the intake.
Right, thanks. I probably need to work on noticing when I'm confused. Your example reminded me of a few cases where I've behaved similarly (everyone I expect has), so I guess I do some "testing" occasionally.