Testing Claude on real-world electronics design
rbinv
25 points
4 comments
November 09, 2026
Related Discussions
Found 5 related stories in 133.5ms across 12,324 title embeddings via pgvector HNSW
- Designing more efficient quantum circuits with Claude pretext · 122 pts · October 16, 2026 · 67% similar
- Discovering and exploiting vulnerabilities in real-world software with Claude ledoge · 13 pts · October 27, 2026 · 60% similar
- Discovering Cryptographic Weaknesses with Claude gslin · 200 pts · July 28, 2026 · 58% similar
- Samsung is using Claude to verify chip designs. It's not going smoothly bundie · 37 pts · August 13, 2026 · 58% similar
- Claude Is Not a Compiler bryanmikaelian · 148 pts · July 21, 2026 · 55% similar
Discussion Highlights (1 comments)
andyfilms1
Maybe I'm missing it, but I don't see how long it took to create these, or how much they cost (in tokens.) PCB layout is a weird problem. As the article says, you can get halfway through before realizing you need to re-do everything, and there's no way to predict that from the outset. It's an inherently self-bottlenecked process. There is also a lot of judgement that goes into it, that I'm not sure could ever be fully covered with AI. You can never hit 100% perfection on every metric (crosstalk, parasitics, DFM, BOM optimization, trace length matching, etc.) so determining where and by how much these things can fall short of optimal is very much a part of the process, and seems like it would be an overfitting nightmare for an AI. There are also simply decisions that have no empirical right or wrong answer, but are still critical to the system functioning. What frequency do you want to run your data busses at? How much power can it draw? How long does it need to last in standby? How hot can it get?