131–140 of 300 posts
Earlier quoted context omitted.
> I could only get about 80% of what I wanted together with my hacky workflow. I literally did this yesterday with solid results using Codex CLI. I used xhigh thinking and gpt 5.5. I had it use KiCad directly via cli rather than via MCP, and I did make Claude Opus review it's work after every round. I got what I think will be a working revision A in about 10 hours of tinkering spread over a few days.
Is 10 hours a short amount of time for designing a PCB?
Earlier quoted context omitted.
They vibe coded their system and it showed Adafruit something? Or showed some information with trivial prodding? Sounds like your average cross-tenant leak. Maybe showing more than intended or some caching issue. Many options some not really not fault of Adafruit.
Or someone found server.domain/path/subdirectory/resourceX and was like "shit, I was hoping to find resourceY but I can't find a link to it, I wonder if I just click in my address bar and change the X to a Y", and voila, resourceY is right there. To some of us, this is elementary navigation. Like going up the stairs if the elevator is out. Often it's faster than waiting for the damn elevator, too. To others, it's cyb…
She was nevertheless welcome at a frequent flyer event hosted by Continental in Houston, where she beat me at poker.
Earlier quoted context omitted.
They vibe coded their system and it showed Adafruit something? Or showed some information with trivial prodding? Sounds like your average cross-tenant leak. Maybe showing more than intended or some caching issue. Many options some not really not fault of Adafruit.
Or someone found server.domain/path/subdirectory/resourceX and was like "shit, I was hoping to find resourceY but I can't find a link to it, I wonder if I just click in my address bar and change the X to a Y", and voila, resourceY is right there. To some of us, this is elementary navigation. Like going up the stairs if the elevator is out. Often it's faster than waiting for the damn elevator, too. To others, it's cyb…
Earlier quoted context omitted.
> I could only get about 80% of what I wanted together with my hacky workflow. I literally did this yesterday with solid results using Codex CLI. I used xhigh thinking and gpt 5.5. I had it use KiCad directly via cli rather than via MCP, and I did make Claude Opus review it's work after every round. I got what I think will be a working revision A in about 10 hours of tinkering spread over a few days.
Is 10 hours a short amount of time for designing a PCB?
PCBs come in all different levels of complexity.
Earlier quoted context omitted.
> mixed-technique approach I think my biggest annoyance with the way we rolled out AI is that nobody seemed to want to use it to augment already working solutions. Just throw everything out and have an LLM do it instead.
I recently saw a Claude skill that used Claude, with no tools, as a spell checker. I wanted to hurl my laptop out to the window.
Pasting something directly into the chat interface seems weird, but if you could somehow just see where P(token | context) falls off a cliff, that's a pretty good hint that your writing has problem.
Earlier quoted context omitted.
Spellchecking is absolutely not a solved problem. I immediately disable spellchecking on every avenue it tries to approach because managing a bunch of dictionaries on every browser/device/application that has its own spellchecker for some godforsaken reason to not have squigglies spammed over every piece of jargon, slang, and slightly atypical spelling is incredibly annoying. I don't know how effective LLMs are, but…
An interesting idea I saw long ago in some book (I thought it was K&P's "Software Tools," or my second guess was K&R1, but neither of those panned out — a strong Mandela effect) was the clever idea of a whole-document spellchecker that works purely probabilistically, by histograms: you feed it a document, it tallies the trigraphs, and any trigraph that appears only rarely is flagged as a likely typo. This approach le…
Earlier quoted context omitted.
> There are some AI-driven autorouters out there now. Placement is probably the big issue that needs to be solved now. Interesting that within an IC this is basically "solved", or at least properly automated with classical numeric techniques such as simulated annealing. I would have thought there's a big opportunity in a mixed-technique approach, where you use AI to extract unstructured data from datasheets and then…
Within an IC you don't have large obstructions for metal layers, distances are short, and buffers can be inserted at will to manage SI.
> distances are short
I remember we had a catastrophic error for "wire longer than 2cm".
> and buffers can be inserted at will to manage SI.
Effective buffering of large nets was a massive pain. Areas where you want to buffer are inevitably areas with a very high level of placement congestion. So you push some cells out of the way to add a buffer. That ends up worsening their timing. So they need a bit more sizing/buffering. Rinse and repeat for a few hours.
( https://web.archive.org/web/20071028033035/http://www.edn.co... ; long since absorbed into Cadence)
Earlier quoted context omitted.
What would be a better way to incorporate AI as a spell checker? In comparison to non-AI traditional tools, AI has the advantage of "understanding" the text, reducing the number of "stupid" mis-corrections. And its spelling correctness is usually already impeccable, so what is there to gain by interfacing it with traditional solutions, and how can it be achieved?
The fact that it produces correctly spelled words says nothing about it’s ability to find spelling mistakes or to correct them without errors like completely changing the word.
Earlier quoted context omitted.
I've been frustrated with Copilot in this regard. I work on a large C++ codebase, with large files. Human developers jump around between files with the Visual Studio fuzzy search, set breakpoints to trace execution in the Debugger, use the IDE's refactoring tools. Microsoft's answer to this was to just ... expose none of this to their Agent Mode!? Replace the working semantic autocomplete with fucking lies!? Maybe it…
It frustrates me too, it really feels like the next breakthrough will be when someone gets agents working "natively" with LSP on large code-bases. Anthropic added LSP support to claude-code, but the current implementation is worse than useless, because any changes aren't reflected fast enough, so it's constantly working on outdated views / compilation caches, and it gets in a right muddle between its "internal" state…