
Aradhye Agarwal on X: While the whole world is going crazy over Jev, I give you a more skeptical take.
@AradhyeAgarwal@AradhyeAgarwallisted 51m agoreviewed by JevWhile the whole world is going crazy over Jev, I give you a more skeptical take. I think it's a great model––but its modeling choices cause real failure modes. 1. The way the speed argument is presented in the quoted tweet isn't valid IMO. You can simply treat every row in the output as independent and sample the autoregressive LLM in parallel. 2. The main benefit of autogressive models is enabling increased computation depth with the same amount of model parameters (via CoT). I don't see how that would be possible with Jev. 3. Jev isn't a magic wand that will one-shot any decision task. I can come up with a task where LLMs do better in terms of efficiency: suppose you have 100 choices out of which you have to choose 10. Also suppose someone has already chosen some 10 choices. You have to tell the "goodness" of this choice. With Jev you could naively multiply the probabilities of choosing the options, but this would not work. Making one choice changes the probability distribution of the other options which has to be accounted for. A simple example one of the chosen options is repeated. Jev will give both the options equal probability (due to symmetry) but it's unlikely that this would be the optimal choice (assume repeating options is downright bad). With LLMs however you can prompt it like so: "okay you have 100 options and you have to answer which ones (a total of 10) you would choose in a sorted order." Then gaslight the LLM into thinking it generated the 10 options (in sorted order) by just prefixing those tokens to the assistant channel and then measure the probability of generating that output. This would happen in one-shot. A careful reader might say: "but we can do the same thing with Jev too right?" Yes that's correct, you could have Jev choose one option then conditioned on that choose the second one and so on. Then multiple the probabilities. But the problem is that this will take 10 sequential steps; you can't one-shot it unlike with an LLM where there is no recurrence. ❤️ 0 likes on X
- Author
- @AradhyeAgarwal
- Use case
- Sales & Leads
- Added
- 2026-09-25
All figures come from the author. Check the source before you quote them.
More in Sales & Leads
- Prasad Pilla on X: AGREED. team built an internal tool using Jev to qualify candidates, and Jev its▲ 0x.com
- Loutchone on X: bon un peu de serieux, jev peut etre vraiment utile...▲ 0x.com
- Aron | TomorrowLab on X: Jev is actually insane▲ 0x.com38 min
- Vadim Choi on X: $10k/month just to decide which agent should answer.▲ 0x.com$107s
- GitHub - promptgtm-shared/clay-jev-people-ranker: Agent Skill and Python workflow for Clay lead scoring, B2B prospect qualification, and peo▲ 0github.com
- GitHub - ZeroGold/call-coach-ai: Jev powered call coach▲ 0github.com
Jev guides for this use case
- What people actually build with Jev, by use caseAll 21 use cases with live counts from real submissions, plus what each one is actually for.
- How Jev sorts a build into one of 21 use casesThe 21 criteria Jev classifies against, published in full, plus what the reviewer sees and how ambiguity is handled.
- Jev pricing, and what a real build actually costsPer-decision cost, the free-output explanation, and the input-price discrepancy nobody else flags.
Bid history
No bids yet — the first one takes this project straight to the spotlight.