1,191 karma · joined November 30, 2016
hugespamfan/ at/ proton. me/
In the new world of mostly-AI code that is mostly not going to be properly reviewed or understood by humans, having a more and more robust manifestation and enforcement, and regeneration of the specs via the coding harness configuration combined with good old fashioned deterministic checks is one potential answer.
Taken to an extreme, the code doesn’t matter, it’s just another artifact generated by the specs, made manifest through the coding harness configuration and CI. If cost didn’t matter, you could re-generate code from scratch every time the specs/config change, and treat the specs/config as the new thing that you need to understand and maintain.
“Clean room code generation-compiler-thing.”
https://github.com/jondwillis/jacq
2) Claude code plugin based on some ideas found in https://www.anthropic.com/research/emotion-concepts-function The main idea is to add hooks that inject “baselines” under some conditions to counteract certain “emotions” that can cause subtle misaligned behavior in agents
https://github.com/jondwillis/functional-emotions
3) Final Fantasy XI custom client remaster in Bevy/Rust alongside an MCP integration that aims to allow agents to play autonomously on private servers à la “Claude plays Pokemon”
Contact: https://jonwillis.dev
Maybe I’m misreading what you’re trying to say.
Would love to share notes. I was able to get away with landing.ai and some really careful schema design and multi-step workflow with a few agents sprinkled in at the end.
Source: me. I built it with some folks.
We use landing.ai to parse the PDF, as well as useworkflow.dev to durably perform other work such as rendering PDF pages for citations, and coordinating a few lightweight agents and deterministic checks that flag for inconsistencies, rule violations, bias, verify appraiser credentials, etc. etc. Everything is grounded in the input document so it makes it pretty fast and easy. We’re going to market soon and have an approval sign up gate currently. Plenty of new features and more rigorous checks planned to bring us to and exceed parity with competition and human reviewers.
There’s plenty of margin for cost and latency versus manual human review, which takes an hour or more and costs $100 or more.
Which brings me to... choosing to throw TypeScript under the bus for having an "unsound" type system ignores the fact that you can just throw more tooling at the problem (e.g., a linter that disallows `any`, since that one example cited in the article), and glazes over the fact that the JS ecosystem has a lot more examples in the training data for many LLMs. The further you deviate from the slop-mean, the worse time you're going to have using LLMs to generate code, slop or otherwise.
> We want AI to be aligned with all of humanity.
One of many contradictions. Liars.
It’d be cool to offer one-off event suggestions, but I understand that’s probably not as easily monetizable.
Next to a Koi pond: “Will you help protect these beautiful fish? Help us by not throwing coins, food, …”