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.
The post argues that the best coding model shouldn't also handle worker scheduling. Instead, give a backend workflow the repo, requirements, and examples so the expensive writing model builds code — a key JEV use case.
if your best coding model also decides which worker goes next, you hired a senior engineer to run a traffic light. that’s the JEV use case I care about. Give a backend workflow the repo, requirements and examples of the existing code. The expensive writing model builds the