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.
Contracts and Structured Returns
The author discusses module contracts and structured returns, noting that free text forces interpretation, tools like Jev help, but the real point is to require structured schemas in your own flows.
Once each module has a contract, ask what it hands back. Free text forces interpretation. “Probably fine to merge” is not a decision. Tools like Jev help. Useful, but still not the whole point. Consider requiring a structured schema in your own flows too.
· 1 likesOpen on X
More like this
Using Jev for Code Review
The author thinks code review is a really good use case for using Jev.
Fascin: A Jev-Powered PR Triage Tool
A developer shares Fascin, a PR triage tool built with Jev that assesses urgency, change type, and merge readiness, noting Jev handles the actual reasoning.
