Something I've had good progress with using local models and simple open-source harnesses is to repeat, in a new context, simple verification prompts.
I'd run the following 5-10 times with one model, then again with a 2nd model.
"Verify the correctness and completeness of all security configs/rules in SETUP.md. Consider if anything is missing, and if anything is not needed. Do not modify any files; only write potential findings to report.txt"
"Verify all findings and claims in report.txt."
Replace "SETUP.md" with whatever you're working on.
It's both terrifying and incredible watching what the models get correct and what they get completely wrong.
However, after enough runs they tend to settle on a state they claim does not need any more edits. And that result is generally useful with much fewer errors/hallucinations compared to a single run.
I would love a resource to get more into the details of bend radius and vibrational modes in harnesses, specifically as they're used on different types of vehicles. Marine wiring endures very different motion than road-vehicle wiring, for instance.
I wonder about failure modes and fault identification. I've heard stories of things like screws or brackets wearing through the insulation and causing an intermittent fault that defies diagnosis. One of those things I think about when I am procrastinating.
My first impression, based upon the title was that this was about Wire Harness Engineering, which is a thing. Apparently it's not about that at all, and is (surprise!) AI related.
Couldn't tolerate the content; it's too structured; I'm open to something more chaotic.
The content is clearly AI-generated, which is really ironic.
Something I've had good progress with using local models and simple open-source harnesses is to repeat, in a new context, simple verification prompts.
I'd run the following 5-10 times with one model, then again with a 2nd model.
"Verify the correctness and completeness of all security configs/rules in SETUP.md. Consider if anything is missing, and if anything is not needed. Do not modify any files; only write potential findings to report.txt"
"Verify all findings and claims in report.txt."
Replace "SETUP.md" with whatever you're working on.
It's both terrifying and incredible watching what the models get correct and what they get completely wrong.
However, after enough runs they tend to settle on a state they claim does not need any more edits. And that result is generally useful with much fewer errors/hallucinations compared to a single run.
I would love a resource to get more into the details of bend radius and vibrational modes in harnesses, specifically as they're used on different types of vehicles. Marine wiring endures very different motion than road-vehicle wiring, for instance.
I wonder about failure modes and fault identification. I've heard stories of things like screws or brackets wearing through the insulation and causing an intermittent fault that defies diagnosis. One of those things I think about when I am procrastinating.
My first impression, based upon the title was that this was about Wire Harness Engineering, which is a thing. Apparently it's not about that at all, and is (surprise!) AI related.
Couldn't tolerate the content; it's too structured; I'm open to something more chaotic.
The content is clearly AI-generated, which is really ironic.
ai generated by this guy: https://www.aispacewalk.cn/about
Why not just look through the actual Claude code codebase and use your own AI to deconstruct it
https://github.com/codeaashu/claude-code
slop
[dead]
[flagged]