Doug
A technique I learned a long time ago from the late Chris
Kendall is to not remove a "fix" until the problem is fully resolved.
Rather keep adding changes until the problem is solved and then start
backing them out.
I visual this as a water filled balloon over my head with several pin
hole leaks and I'm trying to not get wet. Some of the leaks are striking
me but others are not. Since its over my head I can't see them directly.
If I plug one of the pin holes that are leaking on me I still get wet.
If I plug a hole that isn't leaking on me I still get wet. Only when I
plug all of the holes leaking on me do I remain dry. But in the process
I've plugged holes that weren't leaking on me and which I don't really
care about. So assuming I don't want to pay the price for fixing things
that don't need to be fixed I can start removing patches. If it rains on
me I re-patch it, if it doesn't rain on me then I leave the patch off.
Eventually I remove only those patches I don't care about and leave
exactly the number of patches I do need.
For you eye rollers I don't want to sully Mr. Kendall's reputation by
implying that he gave me the visualization itself. That is just a
mechanism produced by my fever wracked brain that helps my understanding
of why the process the advice can make sense.
You probably don't want to know the mental gymnastics that I use to
comprehend what my wife is telling me - and I don't think she wants to
know either! :)
Gary McInturff
208 635 8306
From: Doug Smith [mailto:[email protected]]
Sent: Wednesday, January 06, 2010 10:16 AM
To: [email protected]
Subject: Re: [PSES] ESD Test Failure of Stainless USB Mouse
Hi Everyone,
I recently had a
product that had three distinct mechanisms and all had to be fixed
simultaneously for the product to work. A solution would never happen if
one tried experiments one at a time and just looking at the pass-fail
state on a product like this.
Doug
On 1/6/10 7:06 AM, John Woodgate wrote:
> In message
>
<769907F0D19EFA45BD6F04FC6E896D6D220970D160@GVW0538EXC.americas.hpqcorp.
n
> et>, dated Wed, 6 Jan 2010, "Conway, Patrick R (bNB Houston)"
> <[email protected]> writes:
>
>> 1- Keeping all other parameters the same, swap the mouse,
>> re-test, then swap the PC, and re-test.
>>
>> a. use a completely different mouse type and completely
>> different PC.
>>
>> b. Try to determine if the problem follows the mouse or follows
>> the PC.
>
> If totally confused, change the test gear. (;-)
--
___ _ Doug Smith
\ / ) P.O. Box 1457
========= Los Gatos, CA 95031-1457
_ / \ / \ _ TEL/FAX: 408-356-4186/358-3799
/ /\ \ ] / /\ \ Mobile: 408-858-4528
| q-----( ) | o | Email: [email protected]
\ _ / ] \ _ / Website: http://www.dsmith.org
-
This message is from the IEEE Product Safety Engineering Society
emc-pstc discussion list. To post a message to the list, send your
e-mail to <[email protected]>
All emc-pstc postings are archived and searchable on the web at:
http://www.ieeecommunities.org/emc-pstc
Graphics (in well-used formats), large files, etc. can be posted to that
URL.
Website: http://www.ieee-pses.org/
Instructions: http://listserv.ieee.org/request/user-guide.html
List rules: http://www.ieee-pses.org/listrules.html
For help, send mail to the list administrators:
Scott Douglas <[email protected]>
Mike Cantwell <[email protected]>
For policy questions, send mail to:
Jim Bacher: <[email protected]>
David Heald: <[email protected]>
-
This message is from the IEEE Product Safety Engineering Society emc-pstc
discussion list. To post a message to the list, send your e-mail to
<[email protected]>
All emc-pstc postings are archived and searchable on the web at:
http://www.ieeecommunities.org/emc-pstc
Graphics (in well-used formats), large files, etc. can be posted to that URL.
Website: http://www.ieee-pses.org/
Instructions: http://listserv.ieee.org/request/user-guide.html
List rules: http://www.ieee-pses.org/listrules.html
For help, send mail to the list administrators:
Scott Douglas <[email protected]>
Mike Cantwell <[email protected]>
For policy questions, send mail to:
Jim Bacher: <[email protected]>
David Heald: <[email protected]>
