Live data from Hacker News

Show HN: SPICE simulation → oscilloscope → verification with Claude Code

lucasgerads.com

31–40 of 46 posts

Re: Show HN: SPICE simulation → oscilloscope → verification with Claude Code

#31
post #25
post #24

Earlier quoted context omitted.

This matches what I've seen too — the hallucination gets much worse when the loop has no external verifier. "Does this board work?" has no ground truth inside the model, so it defaults to optimistic narration. What OP is doing here is actually the mitigation: SPICE + scope readout is a verifier the model can't talk its way past. The netlist either simulates or it doesn't, the waveform either matches or it doesn't. Th…

What throws me about this comment is the missing space between the period and the T in the last sentence. Did the model itself do that? Was it a paste error?

I’ve also noticed Gemini and Claude occasionally mixing terms recently (eg revel vs reveal) and can’t decide whether it is due to cost optimization effects or some attempt to seem more human.

I can’t recall either using a wrong word prior this month for some time.

Re: Show HN: SPICE simulation → oscilloscope → verification with Claude Code

#32
post #31
post #25

Earlier quoted context omitted.

What throws me about this comment is the missing space between the period and the T in the last sentence. Did the model itself do that? Was it a paste error?

I’ve also noticed Gemini and Claude occasionally mixing terms recently (eg revel vs reveal) and can’t decide whether it is due to cost optimization effects or some attempt to seem more human. I can’t recall either using a wrong word prior this month for some time.

Or just because mistakes are part of the distribution that it's trained on? Usually the averaging effect of LLMs and top-k selection provides some pressure against this, but occasionally some mistake like this might rise up in probability just enough to make the cutoff and get hit by chance.

I wouldn't really ascribe it to any "attempt to seem more human" when "nondeterministic machine trained on lots of dirty data" is right there.

Re: Show HN: SPICE simulation → oscilloscope → verification with Claude Code

#33
post #32
post #31

Earlier quoted context omitted.

I’ve also noticed Gemini and Claude occasionally mixing terms recently (eg revel vs reveal) and can’t decide whether it is due to cost optimization effects or some attempt to seem more human. I can’t recall either using a wrong word prior this month for some time.

Or just because mistakes are part of the distribution that it's trained on? Usually the averaging effect of LLMs and top-k selection provides some pressure against this, but occasionally some mistake like this might rise up in probability just enough to make the cutoff and get hit by chance. I wouldn't really ascribe it to any "attempt to seem more human" when "nondeterministic machine trained on lots of dirty data"…

Sure, but if that were the case why has it gotten worse recently? I would expect it to be as a result of cost optimization or tradeoffs in the model. I suppose it could be an indicator of the exhaustion of high quality training data or model architecture limitation. But this specific example, revel vs reveal, is almost like going back to GPT-2 reddit errors.

I also don’t want to pretend there is no incentive for AI to seem more human by including the occasional easily recognized error.

Re: Show HN: SPICE simulation → oscilloscope → verification with Claude Code

#34
post #33
post #32

Earlier quoted context omitted.

Or just because mistakes are part of the distribution that it's trained on? Usually the averaging effect of LLMs and top-k selection provides some pressure against this, but occasionally some mistake like this might rise up in probability just enough to make the cutoff and get hit by chance. I wouldn't really ascribe it to any "attempt to seem more human" when "nondeterministic machine trained on lots of dirty data"…

Sure, but if that were the case why has it gotten worse recently? I would expect it to be as a result of cost optimization or tradeoffs in the model. I suppose it could be an indicator of the exhaustion of high quality training data or model architecture limitation. But this specific example, revel vs reveal, is almost like going back to GPT-2 reddit errors. I also don’t want to pretend there is no incentive for AI t…

Or just the models are getting bigger and better at representing the long tail of the distribution. Previously errors like this would get averaged away more often; now they are capable of modelling more variation, and so are picking up on more of these kinds of errors.

Re: Show HN: SPICE simulation → oscilloscope → verification with Claude Code

#35
post #31
post #25

Earlier quoted context omitted.

What throws me about this comment is the missing space between the period and the T in the last sentence. Did the model itself do that? Was it a paste error?

I’ve also noticed Gemini and Claude occasionally mixing terms recently (eg revel vs reveal) and can’t decide whether it is due to cost optimization effects or some attempt to seem more human. I can’t recall either using a wrong word prior this month for some time.

Looking at the account's other comment there are subtle grammatical errors in that one too.

Would be good to see the prompt out of morbid curiosity

Re: Show HN: SPICE simulation → oscilloscope → verification with Claude Code

#36
Can we start pivoting to local LLM integration rather than choosing a service that has something like 5 rug-pulls?

Ye'ol poop splatter (Claude) is getting worse, more expensive, and anti-user. Local may be slower, but it is where the future of LLMs are going to.

Re: Show HN: SPICE simulation → oscilloscope → verification with Claude Code

#39
post #34
post #33

Earlier quoted context omitted.

Sure, but if that were the case why has it gotten worse recently? I would expect it to be as a result of cost optimization or tradeoffs in the model. I suppose it could be an indicator of the exhaustion of high quality training data or model architecture limitation. But this specific example, revel vs reveal, is almost like going back to GPT-2 reddit errors. I also don’t want to pretend there is no incentive for AI t…

Or just the models are getting bigger and better at representing the long tail of the distribution. Previously errors like this would get averaged away more often; now they are capable of modelling more variation, and so are picking up on more of these kinds of errors.

That makes sense, but what is the solution?

Re: Show HN: SPICE simulation → oscilloscope → verification with Claude Code

#40
post #2

[flagged]

Claude can absolutely correct itself and change the source code on the MCU and adapt. However, it also does make mistakes, such as claiming it matched the simulation when it obviously didn't. Or it might make dubious decisions e.g. bit bang a pin instead of using the dedicated uart subsystem. So, I don't let it build completely by itself.

[flagged]
Post reply on HN