[sdiy] Design Process

[thx1138]

Hi Guys,

I usually have students work in pairs on some projects and if they get into 
a jam that they can't resolve, then we take it to the entire class to see 
the whole project.

I try to see how they solve problems then correct them with them watching.

Now when I get into a jam, I usually have to walk away for a bit and think 
about something else for a while. this seems to get me re-charged to dig in 
to the issue. Harware is completely different that software. If you have a 
short or open trace, that is easier but if you mak serious design mistakes , 
it is much more difficult to correct if it is not a protoboard. But you guys 
already know this I am sure.

regards,

Terry
----- Original Message ----- 
From: "Aaron Lanterman" <lanterma at ece.gatech.edu>
To: "synth diy" <synth-diy at dropmix.xs4all.nl>
Sent: Saturday, February 13, 2010 11:50 PM
Subject: Re: [sdiy] Design Process


>
> On Feb 12, 2010, at 10:30 AM, Rainer Buchty wrote:
>
>> On Fri, 12 Feb 2010, Ian Smith wrote:
>>
>>> What do you do when something just refuses to work?
>>
>> Explain it so someone.
>
> I use the reverse of this when helping students with programs and 
> circuits. I have them explain it to me, asking them random questions as 
> they're explaining it, and they usually figure out what's wrong  on their 
> own while they're explaining it, while I'm pretending to be all insightful 
> and stuff. ;)
>
> The tradition is that final projects work fine until the professor comes 
> in to see the demo. On two separate occasions I've had the opposite 
> effect - some aspect of the project won't be working, and they'll show it 
> to be to show it's not working and their thoughts on why it's not 
> working... and it's spontaneously worked. :)
>
> - Aaron
> _______________________________________________
> Synth-diy mailing list
> Synth-diy at dropmix.xs4all.nl
> http://dropmix.xs4all.nl/mailman/listinfo/synth-diy
>