On Aug 9, 6:56 pm, John Larkin
<jjlar...@highNOTlandTHIStechnologyPART.com> wrote:
> On Thu, 9 Aug 2012 09:22:50 -0700 (PDT), Bill Sloman
>
> <
bill.slo...@ieee.org> wrote:
> >On Aug 9, 6:01 pm, John Larkin
> ><jjlar...@highNOTlandTHIStechnologyPART.com> wrote:
> >> On Thu, 9 Aug 2012 04:00:09 -0700 (PDT), Bill Sloman
>
> >> <
bill.slo...@ieee.org> wrote:
> >> >On Aug 9, 12:23 am, Jamie
> >> ><
jamie_ka1lpa_not_valid_after_ka1l...@charter.net> wrote:
> >> >> BillSlomanwrote:
> >> >> > On Aug 8, 11:07 pm, John Larkin <
jlar...@highlandtechnology.com>
> >> >> > wrote:
>
> >> >> >>On Wed, 8 Aug 2012 12:48:18 -0700 (PDT),BillSloman
>
> >> >> >><
bill.slo...@ieee.org> wrote:
>
> >> >> >>>On Aug 8, 4:07 pm, John Larkin
> >> >> >>><jjlar...@highNOTlandTHIStechnologyPART.com> wrote:
>
> >> >> >>>>On Wed, 8 Aug 2012 00:52:22 -0700 (PDT),BillSloman
>
> >> >> >>>><
bill.slo...@ieee.org> wrote:
>
> >> >> >>>>>On Aug 8, 6:59 am, John Larkin
> >> >> >>>>><jjlar...@highNOTlandTHIStechnologyPART.com> wrote:
>
> >> >> >>>>>>On Tue, 7 Aug 2012 19:38:01 -0700 (PDT),
>
> >> >> >>>>>>
bloggs.fredbloggs.f...@gmail.com wrote:
>
> >> >> >>>>>>>On Tuesday, August 7, 2012 12:55:41 PM UTC-4, John Larkin wrote:
<snip>
> >> I only model things that matter.
>
> >That you think matter, at the time.
>
> Obviously. What an engineer does is a quick mental, or maybe
> calculated, thing to determine if trace resistance, or pad
> capacitance, or prop delay, or part parasitics, are within orders of
> magnitude of making any difference. Sometimes you just know this from
> instinct or experience, sometimes you have to actually stop and think
> about it.
Yes, but ... When I was designing stuff for production, and we started
using simulation, it became obvious that the simulated schematic
really had to be the same schematic that we used for production
documentation; one of the incidental advantages of simulation is that
if you've made a drop-off on the schematic you are simulating, the
simulation doesn't work, and you want to exploit that as a form of
error-checking, the two documents have to be the same.
So stuff that "doesn't matter" in the simulation should still be
included in the schematic data base. It may not matter now, but ti may
matter when you have to go back through the documentation, years
later, to find out why the hardware you are producing doesn't meet
specification any more.
> It would be insane to do full nonlinear EM analysis of a slow circuit,
Obviously.
> or to include parasitics that won't change things enough to matter.
Much less insane - they document exactly what you thought you were
doing, and how you were doing it. That can be less obvious a few years
later.
> Engineering involves knowing or calculating what matters and what
> doesn't... otherwise you'd never get anything done.
Not just knowing and calculating, but also documenting - so you really
can build the same thing again and again.
> You, apparently, never get anything done.
I'm not getting much done at the moment, but nobody is paying me to do
stuff, or could give a shit when I get it done. When I was getting
paid, and other people were relying on me to get stuff done, I was a
lot more productive - unusually productive by U.K. standards, though
there were times when I wasn't producing what my manager though that I
ought to be producing (because he didn't know enough about what was
going on, and was unwilling to be educated).
> >> It only takes a few seconds of
> >> consideration to exclude the things that really, really don't matter.
And sometimes those few seconds aren't long enough to comprehend
everything that's actually going on. It's fine as long as you really
are excluding stuff that really doesn't matter, but when you get it
wrong it can be difficult to unblinker yourself and recognise that
something small isn't always negligible.
> >And even less to exclude things that might matter, if they changed.
>
> >> You are so determined to act as an authority that you quit thinking.
>
> >You can't recognise thinking when you get your nose rubbed in it. You
> >are in fact advocating not thinking about any aspect of a circuit that
> >isn't actually giving you a problem at the moment, as tinkerers are
> >prone to do. It's a habit that can get you into trouble from time to
> >time.
>
> >> Bad engineering practice.
>
> >You do seem to be an authority on that ...
>
> >> Go put another turn on your transformer.
>
> >Manyana.
>
> Thousands of manyanas. I wonder if it will oscillate in your lifetime.
Unsavoury rhetorical device. You couldn't care less if it's ever going
to work, but pretending to speculate about it gives you an opportunity
to say something unpleasant.
--
Bill Sloman, Nijmegen