Ran a dumb experiment last night: used Jev by @typesafeai

The clip posted with this case (hosted by the collector’s media CDN); original post on X · 19s.

Fed Jev the finite set of grammatically valid next tokens in C++ and let it pick one at each step, producing working code without free-form generation.

The original post

Ran a dumb experiment last night: used Jev by @typesafeai (a decision/classifier model, not a text-gen model) to write C++.

At every step I gave it the finite set of grammatically valid next tokens and let it just... pick one. No free-form generation, no hallucinated syntax, purely "choose from this legal set." It's not built for this, that's what made it fun.

Got a working piece of C++ out of a model that fundamentally does not generate text. Not claiming this is how you should write code, and it's slower and dumber than just using an actual code model. But it's a neat proof that a classifier constrained tightly enough can stumble into looking like a generator.

Novelty over utility here, but it's the kind of dumb experiment that tells you more about a model's actual guardrails than the official demos do.

Engagement when collected

Views12.1K
Likes49
Bookmarks18
Reposts1
Replies7
Quotes2

Numbers are a snapshot taken from X when the case was added to the library (schema v1, collected 2026-09-19); they will not match today.

Where this case fits

Filed under coding & developer tools, classification & data extraction. In the pattern Jev is built for, the model answers a bounded question per step — and ordinary code acts on the answer, because the answer is already a value rather than a paragraph. Other posts in the same family are on the coding & developer tools page.

Related Jev cases

Keep browsing: all 1173 Jev cases · more from @iamAdityaAnjana · builders · what Jev is

Last updated: 2026-09-22 · sources & corrections · every card links to its author's original post