RFI
[Top] [All Lists]

Re: [RFI] Don't ask, "What is it?" Instead, ask, "Where is it?"

To: RFI RFI <rfi@contesting.com>
Subject: Re: [RFI] Don't ask, "What is it?" Instead, ask, "Where is it?"
From: Michael Coslo <mjc5@psu.edu>
Date: Tue, 3 May 2011 12:55:13 -0400
List-post: <rfi@contesting.com">mailto:rfi@contesting.com>
On May 3, 2011, at 12:08 PM, Sam Morgan wrote:
> 
> I might try to apply those words of wisdom and,
> "just find it"



I think that the point he was trying to make is that when the source of the RFI 
is found, we kind of know what it is. 

While I think that an experienced troubleshooter might get some advantage in 
hearing a noise, then having some good idea to look for it, an inexperienced 
person might accidentally create a red herring, a false lead. That might take 
up more time and effort than simply DF'ing the noise, and then knowing for sure 
what it was.

Coming up - and not directed toward anyone in particular - just an observation 
on troubleshooting.

Troubleshooting skilz are an interesting thing. The idea is to find and fix the 
problem. That sounds obvious, of course. But I've found that many people at 
some level want to be "right". This gets in the way of fixing the problem, 
because the person thinks what they think the problem might be, then goes about 
trying to prove that what they thought the problem was, was the problem.  I 
don't care, I want to fix the problem. Clear the mind, and try to fit the 
symptoms to the problem, not fit the problem to the symptoms. There is a subtle 
and critical difference.  I've walked into many rooms where people tell me what 
they think the problem is. A few occasions I've had to ask them to shush a 
moment, because if what they thought the problem was indeed the problem, they 
would have had it fixed by then.


- 73 de Mike N3LI -

_______________________________________________
RFI mailing list
RFI@contesting.com
http://lists.contesting.com/mailman/listinfo/rfi

<Prev in Thread] Current Thread [Next in Thread>