• AI pcb design

    From john larkin@3:633/10 to All on Monday, October 05, 2026 14:22:37
    https://www.electronicdesign.com/technologies/eda/article/55408466/quilter-the-us-is-reshoring-chips-but-its-still-missing-the-board-designers

    Maybe AI can do PCB design.

    The graph midway down is interesting.


    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Martin Rid@3:633/10 to All on Tuesday, October 06, 2026 15:15:35
    john larkin <jl@htigct.com> Wrote in message:r
    https://www.electronicdesign.com/technologies/eda/article/55408466/quilter-the-us-is-reshoring-chips-but-its-still-missing-the-board-designersMaybe AI can do PCB design.The graph midway down is interesting.

    Actually, there are not that many design rules to implement.
    Should be fairly easy to do.

    Cheers
    --


    ----Android NewsGroup Reader---- https://piaohong.s3-us-west-2.amazonaws.com/usenet/index.html

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill-Sloman@3:633/10 to All on Sunday, October 11, 2026 23:19:17
    On 7/10/2026 6:15 am, Martin Rid wrote:
    john larkin <jl@htigct.com> Wrote in message:r
    https://www.electronicdesign.com/technologies/eda/article/55408466/quilter-the-us-is-reshoring-chips-but-its-still-missing-the-board-designersMaybe AI can do PCB design.The graph midway down is interesting.

    Actually, there are not that many design rules to implement.
    Should be fairly easy to do.
    Until you start worrying about cross-talk between traces, and voltage
    drops along traces.

    There were a couple of occasions in my career where cleaning up a
    printed circuit layout to deal with the unfortunate consequences of
    these effects turned out to be essential to the success of a project or
    a product.

    The really horrible example was a ground layout which routed about 100mA
    of logic supply current along a ground trace which subtracted about
    100mV from a control voltage that had been carefully derived from 6.2V
    voltage reference generator. When the control voltage was at low end
    it's range at it's source it had reversed sign by the time it had got to
    it's destination.

    At least it was easy to fix.

    --
    Bill Sloman, Sydney

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Johann 'Myrkraverk' Oskarsson@3:633/10 to All on Sunday, October 11, 2026 22:24:07
    On 10/11/2026 8:19 PM, Bill-Sloman wrote:
    On 7/10/2026 6:15 am, Martin Rid wrote:
    john larkin <jl@htigct.com> Wrote in message:r
    https://www.electronicdesign.com/technologies/eda/article/55408466/
    quilter-the-us-is-reshoring-chips-but-its-still-missing-the-board-
    designersMaybe AI can do PCB design.The graph midway down is
    interesting.

    Actually,˙ there are not that˙ many design rules˙ to implement.
    Should be fairly easy to do.
    Until you start worrying about cross-talk between traces, and voltage
    drops along traces.

    There were a couple of occasions in my career where cleaning up a
    printed circuit layout to deal with the unfortunate consequences of
    these effects turned out to be essential to the success of a project or
    a product.

    The really horrible example was a ground layout which routed about 100mA
    of logic supply current along a ground trace which subtracted about
    100mV from a control voltage that had been carefully derived from 6.2V voltage reference generator. When the control voltage was at low end
    it's range at it's source it had reversed sign by the time it had got to it's destination.

    At least it was easy to fix.


    In my experience -- albeit perhaps limited -- the business people really
    don't care if a project fails because the technical expertise to realize
    it is insufficient in-house. Nor do they care when people with good
    technical skills are let go [presumably to a different employer.]

    After all, the business people continue to be paid, even when several
    projects fail.


    Best wishes, and happy searching for new employment!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From JM@3:633/10 to All on Sunday, October 11, 2026 17:10:42
    On Mon, 05 Oct 2026 14:22:37 -0700, john larkin <jl@htigct.com> wrote:

    https://www.electronicdesign.com/technologies/eda/article/55408466/quilter-the-us-is-reshoring-chips-but-its-still-missing-the-board-designers

    Maybe AI can do PCB design.

    The graph midway down is interesting.


    That article is a load of crap. Written by the founder of an AI tool
    company with a product which assists in PCB design, justifying the
    need for such a tool.

    There is no shortage of PCB layout staff. There is no shortage of
    engineers full stop. Never have been. Pay enough and you'll get
    staff.

    As for AI in PCB layout the problem is not in routing, but in
    optimising placement. Autorouters have worked for several decades -
    if you spend time creating the constraints they work.

    As for AI in design it is already offered by the big 3 EDA vendors for
    both Analogue and Digital work.

    Cadence for example have at least four agents that I know of
    (viraStack ChipStack auraStack innostack) which specialise in
    different areas. Virastack pairs up with Virtuoso (which is probably
    used for 99%+ of all analogue chip designs) for analogue work.
    Aurastack assists in PCB work, and the others in the 1's and 0's
    stuff.

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Sunday, October 11, 2026 10:27:38
    On Sun, 11 Oct 2026 17:10:42 +0100, JM
    <sunaecoNoChoppedPork@gmail.com> wrote:

    On Mon, 05 Oct 2026 14:22:37 -0700, john larkin <jl@htigct.com> wrote:

    https://www.electronicdesign.com/technologies/eda/article/55408466/quilter-the-us-is-reshoring-chips-but-its-still-missing-the-board-designers

    Maybe AI can do PCB design.

    The graph midway down is interesting.


    That article is a load of crap. Written by the founder of an AI tool
    company with a product which assists in PCB design, justifying the
    need for such a tool.

    There is no shortage of PCB layout staff. There is no shortage of
    engineers full stop. Never have been. Pay enough and you'll get
    staff.

    As for AI in PCB layout the problem is not in routing, but in
    optimising placement. Autorouters have worked for several decades -
    if you spend time creating the constraints they work.

    As for AI in design it is already offered by the big 3 EDA vendors for
    both Analogue and Digital work.

    Cadence for example have at least four agents that I know of
    (viraStack ChipStack auraStack innostack) which specialise in
    different areas. Virastack pairs up with Virtuoso (which is probably
    used for 99%+ of all analogue chip designs) for analogue work.
    Aurastack assists in PCB work, and the others in the 1's and 0's
    stuff.

    We've come a long way from when people drew PCB designs with ink on
    paper, or with black tape on mylar.

    I was at a meetup at FLUX.AI last week. They are one of many outfits
    that are trying to do AI pcb design. They do understand that I want to
    do some of the layout myself, place and route the critical stuff. But
    then I want AI to do the grunt work, connect the 150 dangling FPGA
    pins following my rules and the data sheet, and do the power pours and
    stuff. Maybe do some thermal analysis.

    Allspice.io is interesting. They can use AI to check a design, flag
    possible gotchas.

    Sure, we need to employ PCB layout people, as we need to employ
    engineers and coders. But we need them to be efficient to compete. We
    can't just "pay enough" if our competitors can get boards designed
    cheaper and faster.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From CĂłilĂ­n NioclásĂ­n GlostĂ©ir@3:633/10 to All on Sunday, October 11, 2026 19:58:29
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> skrev: |-------------------------------------------------------------------------| |"In my experience -- albeit perhaps limited -- the business people really| |don't care if a project fails because the technical expertise to realize |
    |it is insufficient in-house. Nor do they care when people with good | |technical skills are let go [presumably to a different employer.] |
    | | |After all, the business people continue to be paid, even when several | |projects fail. |
    | |
    | | |Best wishes, and happy searching for new employment!" | |-------------------------------------------------------------------------|

    Interesting!
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Don Y@3:633/10 to All on Sunday, October 11, 2026 18:12:58
    There is no shortage of PCB layout staff. There is no shortage of
    engineers full stop. Never have been. Pay enough and you'll get
    staff.

    As for AI in PCB layout the problem is not in routing, but in
    optimising placement. Autorouters have worked for several decades -
    if you spend time creating the constraints they work.

    The problem with EDA is always all of the niggly details that
    need to be present (in a tool or in the mind of the designer)
    to optimize a design.

    Initially, it was petty things like symbol libraries. Footprints.
    Gate swapping criteria. etc.

    Then, things like current carrying capacity of foils based on
    the static and dynamic needs of the loads they powered.

    And, increasingly, there are constraints on trace impedances,
    trace lengths, etc.

    This is all just tedium. Nothing "exciting" to motivate but
    often consequential if ignored.

    Where AI can add value is in extracting those constraints from
    the components' requirements and the nature of the design and
    conveying them to a layout agent.

    As for AI in design it is already offered by the big 3 EDA vendors for
    both Analogue and Digital work.

    Cadence for example have at least four agents that I know of
    (viraStack ChipStack auraStack innostack) which specialise in
    different areas. Virastack pairs up with Virtuoso (which is probably
    used for 99%+ of all analogue chip designs) for analogue work.
    Aurastack assists in PCB work, and the others in the 1's and 0's
    stuff.


    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill-Sloman@3:633/10 to All on Monday, October 12, 2026 14:37:18
    On 12/10/2026 1:24 am, Johann 'Myrkraverk' Oskarsson wrote:
    On 10/11/2026 8:19 PM, Bill-Sloman wrote:
    On 7/10/2026 6:15 am, Martin Rid wrote:
    john larkin <jl@htigct.com> Wrote in message:r
    https://www.electronicdesign.com/technologies/eda/article/55408466/
    quilter-the-us-is-reshoring-chips-but-its-still-missing-the-board-
    designersMaybe AI can do PCB design.The graph midway down is
    interesting.

    Actually,˙ there are not that˙ many design rules˙ to implement.
    Should be fairly easy to do.
    Until you start worrying about cross-talk between traces, and voltage
    drops along traces.

    There were a couple of occasions in my career where cleaning up a
    printed circuit layout to deal with the unfortunate consequences of
    these effects turned out to be essential to the success of a project
    or a product.

    The really horrible example was a ground layout which routed about
    100mA of logic supply current along a ground trace which subtracted
    about 100mV from a control voltage that had been carefully derived
    from 6.2V voltage reference generator. When the control voltage was at
    low end it's range at it's source it had reversed sign by the time it
    had got to it's destination.

    At least it was easy to fix.


    In my experience -- albeit perhaps limited -- the business people really don't care if a project fails because the technical expertise to realize
    it is insufficient in-house.˙ Nor do they care when people with good technical skills are let go [presumably to a different employer.]

    After all, the business people continue to be paid, even when several projects fail.

    Companies fold if all their projects fail.

    Business people do like to encourage their technical experts to make up
    their minds faster than they ought to. There's a delusion that engineers
    are pathological perfectionists and won't make up their minds unless put
    under a lot of pressure to do so.

    This usually results in products being released before they should be
    and the faults corrected by post-production modifications, which tend to
    be more expensive than a pre-release redesign.
    On the same project I got to salvage the DC power by replacing a single
    2N3055 with a much more expensive single power transistor that could
    handle the worst case power dissipation. Two 2N3055's would have been a cheaper way to get the power dissipation, but there was no way to fit
    them into the space available at that stage. Earlier in the process
    making the extra space would have been trivial.

    The power supply design had initially been done by a technician rather
    than an engineer - a very competent technician, but he hadn't been
    taught about worst case design. It was a false economy, and didn't do
    anything good for the technicians peace of mind either.

    --
    Bill Sloman, Sydney

    --
    Bill Sloman, Sydney

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Martin Rid@3:633/10 to All on Monday, October 12, 2026 14:23:05
    Bill-Sloman <bill.sloman@sophia-elektronica.com> Wrote in message:r
    On 7/10/2026 6:15 am, Martin Rid wrote:> john larkin <jl@htigct.com> Wrote in message:r>> https://www.electronicdesign.com/technologies/eda/article/55408466/quilter-the-us-is-reshoring-chips-but-its-still-missing-the-board-designersMaybe AI can do PCB design.The graph midway down is interesting.> > Actually, there are not that many design rules to implement.> Should be fairly easy to do.Until you start worrying about cross-talk between traces, and voltage drops along traces.There were a couple of occasions in my career where cleaning up a printed circuit layout to deal with the unfortunate consequences of these effects turned out to be essential to the success of a project or a product.The really horrible example was a ground layout which routed about 100mA of logic supply current along a ground trace which subtracted about 100mV from a control voltage that had been carefully derived from 6.2V voltage reference generator. When the control voltage was at low end it's range at it's source it had reversed sign by the time it had got to it's destination.At least it was easy to fix.-- Bill Sloman, Sydney

    Well, that part of the design rules. Distance from regulator.
    Route supplies first, buss's, special, and the rest.

    Cheers
    --


    ----Android NewsGroup Reader---- https://piaohong.s3-us-west-2.amazonaws.com/usenet/index.html

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Martin Davies-Roundhill@3:633/10 to All on Thursday, October 15, 2026 03:52:20
    The point about AI extracting layout constraints is the interesting part to me. It suggests a useful division of labour: the system can collect details and explore arrangements, while people still decide what the design is for, what trade-offs are acceptable, and who is responsible when the constraints were incomplete.

    I?m Martin Davies-Roundhill, making a small non-commercial video project about possible life in 2036. There is no product, fundraising, paid offer, or request for money here; I?m sharing this one essay because it connects with the question of what AI access actually gives people:

    https://youtu.be/0giLhX4tS7E

    The essay?s argument is that access to a capable system is not the same as freedom if the person cannot inspect its work, keep control of the tool, or share in the gains. In practical electronics work, where do you think the most important human boundary remains: specifying the objective, checking the constraints, or accepting responsibility for the finished board?

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Don Y@3:633/10 to All on Wednesday, October 14, 2026 22:44:44
    On 10/14/2026 8:52 PM, Martin Davies-Roundhill wrote:
    The point about AI extracting layout constraints is the interesting part to me. It suggests a useful division of labour: the system can collect details and explore arrangements, while people still decide what the design is for, what trade-offs are acceptable, and who is responsible when the constraints were incomplete.

    Machines should always handle the "grunt" work -- the work that
    is repetitive, error prone (due to its repetitive/boring nature)
    and comprehensive.

    This is as things have been done, historically.

    Doing placement with rough connectivity algorithms (heuristics for which
    humans would rely on ratsnests), autorouting, enforcing design rules, validating layout against schematic, etc. All dreary tasks that
    no one really looks forward to.

    It's only recently that NLP suggests an AI could "read a datasheet"
    (or an app note) and extract layout criteria from that -- instead of relying
    on a human to express those constraints in a manner that an *existing*
    tool could understand (if your tool *doesn't* understand them, then it
    relies on the human operator to enforce them -- let the AI assume the role
    of the human in that case).

    Only humans can assess the relative value tradeoffs in a design;
    how much reliability do you sacrifice to save on production costs?
    how much performance do you trade for ______________? etc.

    The essay?s argument is that access to a capable system is not the same as freedom if the person cannot inspect its work, keep control of the tool, or share in the gains. In practical electronics work, where do you think the most important human boundary remains: specifying the objective, checking
    the constraints, or accepting responsibility for the finished board?

    I don't think anyone is equating AI with "freedom".

    The problem with LLMs is you can't see their reasoning, just their
    conclusions.

    Ages ago, I recall listening to a grandmother lament the fate
    of one of her friends recently diagnosed with cancer.
    "Once the AIR gets to it, their gone!"

    She refering to exploratory surgery (predating MRI) to ascertain
    the extent of a cancer's spread. "Opening up" the patient
    ("exposing it to air"). But, this step often precedes death,
    not because of the "air" but because of the procedure that
    exposed the cancer.

    What seemed to make sense to the grandmother (air -> death)
    was based on a faulty rationale.

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Thursday, October 15, 2026 08:10:10
    On Wed, 14 Oct 2026 22:44:44 -0700, Don Y
    <blockedofcourse@foo.invalid> wrote:

    On 10/14/2026 8:52 PM, Martin Davies-Roundhill wrote:
    The point about AI extracting layout constraints is the interesting part to >> me. It suggests a useful division of labour: the system can collect details >> and explore arrangements, while people still decide what the design is for, >> what trade-offs are acceptable, and who is responsible when the constraints >> were incomplete.

    Machines should always handle the "grunt" work -- the work that
    is repetitive, error prone (due to its repetitive/boring nature)
    and comprehensive.

    This is as things have been done, historically.

    Doing placement with rough connectivity algorithms (heuristics for which >humans would rely on ratsnests), autorouting, enforcing design rules, >validating layout against schematic, etc. All dreary tasks that
    no one really looks forward to.

    It's only recently that NLP suggests an AI could "read a datasheet"
    (or an app note) and extract layout criteria from that -- instead of relying >on a human to express those constraints in a manner that an *existing*
    tool could understand (if your tool *doesn't* understand them, then it
    relies on the human operator to enforce them -- let the AI assume the role
    of the human in that case).


    We have data sheets that run to 600 pages or more. I'm happy with the
    ide of an AI tool that looks at my schematic and PCB and prowls all
    the related data sheets and flags possible errors. Alspice claims to
    do that and I think it may be useful. They showed mr one example that
    clains to have discovered an open drain that needs a pullup, and that
    it checked all the power supplies and in/out direction on all the
    chips, stuff like that.

    Data sheets seem to be getting progressively longer and worse.



    Only humans can assess the relative value tradeoffs in a design;
    how much reliability do you sacrifice to save on production costs?
    how much performance do you trade for ______________? etc.

    The essay?s argument is that access to a capable system is not the same as >> freedom if the person cannot inspect its work, keep control of the tool, or >> share in the gains. In practical electronics work, where do you think the
    most important human boundary remains: specifying the objective, checking
    the constraints, or accepting responsibility for the finished board?

    I don't think anyone is equating AI with "freedom".

    The problem with LLMs is you can't see their reasoning, just their >conclusions.

    That's fine if it's spotting possible mistakes.



    Ages ago, I recall listening to a grandmother lament the fate
    of one of her friends recently diagnosed with cancer.
    "Once the AIR gets to it, their gone!"

    She refering to exploratory surgery (predating MRI) to ascertain
    the extent of a cancer's spread. "Opening up" the patient
    ("exposing it to air"). But, this step often precedes death,
    not because of the "air" but because of the procedure that
    exposed the cancer.

    What seemed to make sense to the grandmother (air -> death)
    was based on a faulty rationale.

    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Thursday, October 15, 2026 08:17:58
    On Thu, 15 Oct 2026 08:10:10 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Wed, 14 Oct 2026 22:44:44 -0700, Don Y
    <blockedofcourse@foo.invalid> wrote:

    On 10/14/2026 8:52 PM, Martin Davies-Roundhill wrote:
    The point about AI extracting layout constraints is the interesting part to >>> me. It suggests a useful division of labour: the system can collect details >>> and explore arrangements, while people still decide what the design is for, >>> what trade-offs are acceptable, and who is responsible when the constraints >>> were incomplete.

    Machines should always handle the "grunt" work -- the work that
    is repetitive, error prone (due to its repetitive/boring nature)
    and comprehensive.

    This is as things have been done, historically.

    Doing placement with rough connectivity algorithms (heuristics for which >>humans would rely on ratsnests), autorouting, enforcing design rules, >>validating layout against schematic, etc. All dreary tasks that
    no one really looks forward to.

    It's only recently that NLP suggests an AI could "read a datasheet"
    (or an app note) and extract layout criteria from that -- instead of relying >>on a human to express those constraints in a manner that an *existing*
    tool could understand (if your tool *doesn't* understand them, then it >>relies on the human operator to enforce them -- let the AI assume the role >>of the human in that case).


    We have data sheets that run to 600 pages or more. I'm happy with the
    ide of an AI tool that looks at my schematic and PCB and prowls all
    the related data sheets and flags possible errors. Alspice claims to
    do that and I think it may be useful. They showed mr one example that
    clains to have discovered an open drain that needs a pullup, and that
    it checked all the power supplies and in/out direction on all the
    chips, stuff like that.

    Data sheets seem to be getting progressively longer and worse.



    Only humans can assess the relative value tradeoffs in a design;
    how much reliability do you sacrifice to save on production costs?
    how much performance do you trade for ______________? etc.

    The essay?s argument is that access to a capable system is not the same as >>> freedom if the person cannot inspect its work, keep control of the tool, or >>> share in the gains. In practical electronics work, where do you think the >>> most important human boundary remains: specifying the objective, checking >>> the constraints, or accepting responsibility for the finished board?

    I don't think anyone is equating AI with "freedom".

    The problem with LLMs is you can't see their reasoning, just their >>conclusions.

    That's fine if it's spotting possible mistakes.



    Ages ago, I recall listening to a grandmother lament the fate
    of one of her friends recently diagnosed with cancer.
    "Once the AIR gets to it, their gone!"

    She refering to exploratory surgery (predating MRI) to ascertain
    the extent of a cancer's spread. "Opening up" the patient
    ("exposing it to air"). But, this step often precedes death,
    not because of the "air" but because of the procedure that
    exposed the cancer.

    What seemed to make sense to the grandmother (air -> death)
    was based on a faulty rationale.

    https://www.derekthompson.org/p/i-know-why-the-mathematicians-weep


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Martin Davies-Roundhill@3:633/10 to All on Thursday, October 15, 2026 16:32:47
    That is a fair distinction. I did not mean AI itself is freedom; I meant that handing repetitive work to a system might create more room for choice, but only if the system remains understandable and accountable. Your datasheet example makes the practical boundary clear: an assistant that flags a possible missing pull-up could save a search through hundreds of pages. I would want each flag to point to the exact datasheet requirement, the pin or net it matched, and a check the designer can reproduce. That gives us something inspectable instead of asking us to trust an opaque conclusion. The person still makes the trade-off and signs off on the design. Do current tools show that source-level evidence clearly enough, or does the engineer still have to verify everything manually?

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Don Y@3:633/10 to All on Thursday, October 15, 2026 13:54:53
    On 10/15/2026 9:32 AM, Martin Davies-Roundhill wrote:
    That is a fair distinction. I did not mean AI itself is freedom; I meant
    that handing repetitive work to a system might create more room for choice, but only if the system remains understandable and accountable. Your
    datasheet example makes the practical boundary clear: an assistant that
    flags a possible missing pull-up could save a search through hundreds of pages. I would want each flag to point to the exact datasheet requirement, the pin or net it matched, and a check the designer can reproduce. That

    Exactly. "Not that I don't trust you -- but I don't trust you!"
    If a technician flagged such a fault, you'd want *him* to back up his
    claim so no reason why an AI "agent" should be held to the same
    standards.

    It would just be faster, more accurate and more thorough (hopefully).

    E.g., the Technical Manual for the MCU I'm currently using is almost
    17,000 pages. Wading through that and designing symbolic references
    for registers, settings within registers, subassembly constraints,
    etc. is REALLY tedious.

    One can trust the manufacturer's opinion as to what the programming
    model should look like and how it should be conceptualized. But,
    there's no guarantee that it doesn't contain errors. And, that it
    fits with your naming and organizational scheme.

    If there are N instances of a <widget>, one would think
    their interfaces would be identical; are they, in fact?
    How many details do I have to review to convince myself
    of that fact?

    It would be nice to just tell an agent how you want things
    organized and let it generate the manifest constants, module
    abstractions, etc. None of this really needs human assistance
    (other than approving the decisions made by the agent)

    gives us something inspectable instead of asking us to trust an opaque conclusion. The person still makes the trade-off and signs off on the
    design. Do current tools show that source-level evidence clearly enough, or does the engineer still have to verify everything manually?

    Dunno. I've implemented a Production System in my current
    project and the AI agents just propose new rules -- within
    the constraints that have been imposed on them (i.e., you can
    only make recommendations based on observations of the
    following variables/events). The hope is that this will
    let a user decide if the "reasoning" behind the rule "makes
    sense".

    E.g., when I was prototyping the HVAC controller, it kept
    telling me that the air conditioner was broken. At first,
    I assumed there was some flaw in the code that interfaces
    to the field -- that some input was being corrupted
    (after all, the house is *cool*!).

    Eventually, I walked through the actual rules with current
    data and realized where the conclusion originated. Then,
    manually started making the same measurements.

    And, the ACbrrr shit the bed shortly thereafter!

    But, I was able to see where the admonition originated instead
    of just trusting its conclusion.

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