Writing C++ with Jev by picking valid next tokens
The author experimented with TypeSafe's Jev decision/classifier model for C++: at each step it was given only grammatically valid next tokens to pick from, avoiding free-form generation.
A developer shares experience with multi-day code interventions: switching from React to Svelte, moving to Hono and Vite, with agents doing the work. Jev picks the next move inside the agents.
I've gotten weirdly good at multi-day code interventions. Switch from React to Svelte. Move from Next.js to Hono and Vite. Change your mind about the stack. The agents do the work for you, and every diff still crosses my desk. Jev picks the next move inside the agents, so