HN user

jondwillis

1,162 karma

Get in touch:

hugespamfan/ at/ proton. me/

Posts1
Comments660
View on HN

I don’t think it’s reasonable to think that privacy regulation is coming with the current admin and weak “opposition”, and lack of capacity to care or understand the stakes by the populace. We need some very effective political organizing, yesterday. And normalized, cheap, scramble suits wouldn’t hurt either.

I’ve been considering this as well, and trying to get my colleagues to understand and start doing it. I use it to pretty decent effect in my vibe coded slop side projects.

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.”

1) “AI harness plugin build system” to help improve reliability of and increase compatibility across the fragmented AI coding harness plugin ecosystem.

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

Apple at 50 4 months ago

I’ve had the exact opposite journey. Native apps, disillusioned and frustrated with the backwards tooling, moved on to more open platforms (web apps and backends)

I think your repo is cool, but I don’t think creating APIs from web apps is at all precipated on academic research and the other things you mentioned.

Maybe I’m misreading what you’re trying to say.