• Re: Definitive Handbook

    From someone@3:633/10 to All on Friday, July 17, 2026 22:30:02
    This quote originates from an internal engineering document and training manual for transistor modeling, not a traditionally published textbook. The guide offers practical, step-by-step procedures for extracting parameters and constructing SPICE computer simulation models for NPN Bipolar Junction Transistors (BJTs).

    The exact author of this internal document is not named, as it was written anonymously and collectively by a group of "NEW-HIREs" (newly hired junior engineers) at an unnamed semiconductor or aerospace firm.

    The Transistor Modeling Techniques Guide functions as an informal, internally passed-down "survival guide" rather than an official corporate publication or textbook. It was compiled by entry-level engineers who had just gone through the frustrating trial-and-error process of extracting Gummel-Poon BJT parameters and "tweaking" SPICE simulation files to match physical manufacturer data sheets.Because the guide was written from the perspective of junior employees who had to learn the hard way, they left tongue-in-cheek advice for the next generation of engineers onboarding into the device modeling department.

    Not worth serious consideration.

    --
    For full context, visit https://www.electrondepot.com/electrodesign/definitive-handbook-4406279-.htm


    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From legg@3:633/10 to All on Saturday, July 18, 2026 10:51:59
    On Fri, 17 Jul 2026 22:30:02 +0000, someone <2a59d59e3809f827ce709d3815e3950eef4a6a93af5557a93a7fdfba71460843@example.com> wrote:

    This quote originates from an internal engineering document and training manual for transistor modeling, not a traditionally published textbook. The guide offers practical, step-by-step procedures for extracting parameters and constructing SPICE computer simulation models for NPN Bipolar Junction Transistors (BJTs).

    The exact author of this internal document is not named, as it was written anonymously and collectively by a group of "NEW-HIREs" (newly hired junior engineers) at an unnamed semiconductor or aerospace firm.

    The Transistor Modeling Techniques Guide functions as an informal, internally passed-down "survival guide" rather than an official corporate publication or textbook. It was compiled by entry-level engineers who had just gone through the frustrating trial-and-error process of extracting Gummel-Poon BJT parameters and "tweaking" SPICE simulation files to match physical manufacturer data sheets.Because the guide was written from the perspective of junior employees who had to learn the hard way, they left tongue-in-cheek advice for the next generation of engineers onboarding into the device modeling department.

    Not worth serious consideration.

    They weren't shooting for the Nobel.

    They got the thankless job that senior engineers preferred to
    avoid for one reason or another - those senior engineers
    tending to chuck PCs out the window, if they had sufficient
    seniority.

    . . . . and they didn't have access to the typing pool or a
    secretary.

    It's a practical example of bipolar device spice modeling
    that is well worth the read, typos and all.

    RL

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Don Y@3:633/10 to All on Monday, July 20, 2026 01:05:13
    On 7/18/2026 7:51 AM, legg wrote:
    On Fri, 17 Jul 2026 22:30:02 +0000, someone

    Not worth serious consideration.

    They weren't shooting for the Nobel.

    They got the thankless job that senior engineers preferred to
    avoid for one reason or another - those senior engineers
    tending to chuck PCs out the window, if they had sufficient
    seniority.

    Writing is hard. Especially if you have to ANTICIPATE your audience.

    The first technical document that I authored (~600pp) saw a lot
    of upfront work in figuring out how to present the material
    in a way that someone new to the device could absorb as well
    as someone who had been using it for years and needed it
    just as a "reference" for some seldom used feature/detail.

    Read man pages to see just how piss poor engineers are at
    organizing material for someone ELSE to understand!

    [I've been digging through smb4.conf(5) and have realized that
    the only way to understand the significance and role of each
    enumerated setting is to dig through the sources and ignore
    the documentation! Wanna bet there are lots of errors that
    turn up?]

    . . . . and they didn't have access to the typing pool or a
    secretary.

    It's a practical example of bipolar device spice modeling
    that is well worth the read, typos and all.

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Joerg@3:633/10 to All on Tuesday, July 21, 2026 15:15:20
    On 7/12/26 7:39 AM, legg wrote:
    of Transistor Modeling from 1986 is a modest illustration of
    past 'new-hire' attitudes. In the 'Background Information'
    section, the authors let rip:

    "Since device modeling is a task usually given to a 'NEW - HIRE', it
    is recommended that the advise of a Senior Engineer with experience
    be sort after when a difficult problem is encountered. Get used to
    asking questions because your going to have a lot of them"

    I'm guessing that this hand-typed page didn't rate proofreading, as
    'advise', 'sort' and 'your' got through. They'd possibly pass a
    'spell-check' by commodity word processing software, today.

    . . . . . at that time, some Senior Engineers would just as likely
    have turfed your DOS PC out the window, as offer pertinent advice.

    Saught is still unlikely to get its own dictionary entry - just a
    notation under 'seek'. Using 'sort' suggests UK, Aussy or Kiwi
    origins for one of the self-typing authors. 'Senior Engineers'
    would probably have had typing assistance.


    In my experience the average writing skills of new EEs have gone
    downhill, fast. There are exceptions but many can't even compose a
    decent module spec.

    Regarding what the authors above were saying: A few months after I had
    earned my degree I met a university mate by chance, at a big rail
    station. He got his degree around the same time, also a few months
    before. However, this guy did not have a lick of practical experience
    with electronics. No hobby exposure, no tinkering, no repairing of electronics, nothing, only whatever theory he had learned at the
    university. I asked him what he did at this first job. "Writing
    application notes for [huge semiconductor company]" ... WHAT?!

    --
    Regards, Joerg

    http://www.analogconsultants.com/

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Tuesday, July 21, 2026 16:06:18
    On Tue, 21 Jul 2026 15:15:20 -0700, Joerg <news@analogconsultants.com>
    wrote:

    On 7/12/26 7:39 AM, legg wrote:
    of Transistor Modeling from 1986 is a modest illustration of
    past 'new-hire' attitudes. In the 'Background Information'
    section, the authors let rip:

    "Since device modeling is a task usually given to a 'NEW - HIRE', it
    is recommended that the advise of a Senior Engineer with experience
    be sort after when a difficult problem is encountered. Get used to
    asking questions because your going to have a lot of them"

    I'm guessing that this hand-typed page didn't rate proofreading, as
    'advise', 'sort' and 'your' got through. They'd possibly pass a
    'spell-check' by commodity word processing software, today.

    . . . . . at that time, some Senior Engineers would just as likely
    have turfed your DOS PC out the window, as offer pertinent advice.

    Saught is still unlikely to get its own dictionary entry - just a
    notation under 'seek'. Using 'sort' suggests UK, Aussy or Kiwi
    origins for one of the self-typing authors. 'Senior Engineers'
    would probably have had typing assistance.


    In my experience the average writing skills of new EEs have gone
    downhill, fast. There are exceptions but many can't even compose a
    decent module spec.

    Regarding what the authors above were saying: A few months after I had >earned my degree I met a university mate by chance, at a big rail
    station. He got his degree around the same time, also a few months
    before. However, this guy did not have a lick of practical experience
    with electronics. No hobby exposure, no tinkering, no repairing of >electronics, nothing, only whatever theory he had learned at the
    university. I asked him what he did at this first job. "Writing
    application notes for [huge semiconductor company]" ... WHAT?!

    Makes sense. It's obvious that most appnotes and data sheets are done
    by people who don't rate parking spots.

    There is apparently a plan to defund schools where a majority of grads
    don't make minimum wage, $36K a year.





    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Wednesday, July 22, 2026 13:10:05
    On 13/07/2026 12:39 am, legg wrote:
    of Transistor Modeling from 1986 is a modest illustration of
    past 'new-hire' attitudes. In the 'Background Information'
    section, the authors let rip:

    "Since device modeling is a task usually given to a 'NEW - HIRE', it
    is recommended that the advise of a Senior Engineer with experience
    be sort after when a difficult problem is encountered. Get used to
    asking questions because your going to have a lot of them"

    I'm guessing that this hand-typed page didn't rate proofreading, as
    'advise', 'sort' and 'your' got through. They'd possibly pass a
    'spell-check' by commodity word processing software, today.

    . . . . . at that time, some Senior Engineers would just as likely
    have turfed your DOS PC out the window, as offer pertinent advice.

    Saught is still unlikely to get its own dictionary entry - just a
    notation under 'seek'. Using 'sort' suggests UK, Aussy or Kiwi
    origins for one of the self-typing authors. 'Senior Engineers'
    would probably have had typing assistance.

    As an Australian-born and educated engineer, the suggestion that
    Australian or New Zealand trained engineer would have trouble separating
    sort and sought strikes me as unrealistic.

    The only engineer I know who had that kind of problem was English and dyslexic. We couldn't persuade him that works that sounded the same
    could need to be spelled differently, depending on the different ideas
    that they were expressing. About 15% of readers do sub-vocalise - as you
    can test by printing a piece of verse as if it were prose and asking the reader if it was rythmic (and my wife and one of her colleagues did the experiment and published the result in verse, printed as it were prose),
    but most understand that "theirs" and "there's" are different concepts.

    --
    Bill Sloman, Sydney

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From legg@3:633/10 to All on Wednesday, July 22, 2026 08:44:13
    On Wed, 22 Jul 2026 13:10:05 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/07/2026 12:39 am, legg wrote:
    of Transistor Modeling from 1986 is a modest illustration of
    past 'new-hire' attitudes. In the 'Background Information'
    section, the authors let rip:

    "Since device modeling is a task usually given to a 'NEW - HIRE', it
    is recommended that the advise of a Senior Engineer with experience
    be sort after when a difficult problem is encountered. Get used to
    asking questions because your going to have a lot of them"

    I'm guessing that this hand-typed page didn't rate proofreading, as
    'advise', 'sort' and 'your' got through. They'd possibly pass a
    'spell-check' by commodity word processing software, today.

    . . . . . at that time, some Senior Engineers would just as likely
    have turfed your DOS PC out the window, as offer pertinent advice.

    Saught is still unlikely to get its own dictionary entry - just a
    notation under 'seek'. Using 'sort' suggests UK, Aussy or Kiwi
    origins for one of the self-typing authors. 'Senior Engineers'
    would probably have had typing assistance.

    As an Australian-born and educated engineer, the suggestion that
    Australian or New Zealand trained engineer would have trouble separating >sort and sought strikes me as unrealistic.

    The only engineer I know who had that kind of problem was English and >dyslexic. We couldn't persuade him that works that sounded the same
    could need to be spelled differently, depending on the different ideas
    that they were expressing. About 15% of readers do sub-vocalise - as you
    can test by printing a piece of verse as if it were prose and asking the >reader if it was rythmic (and my wife and one of her colleagues did the >experiment and published the result in verse, printed as it were prose),
    but most understand that "theirs" and "there's" are different concepts.

    Appalachian?

    RL

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)