hype-free explanation of jev:
jev does not replace gpt / claude
jev is just a *really* smart switch statement
like if 2016 ml classifiers got 2026 levels of intelligence
it's a new* type of tool that will make a lot of workloads insanely fast, cheap, and accurate
* = and by new, i mean rebranded
~~~
it needs a predefined set of options and it will tell you which one to take
it cannot:
- write code
- generate natural language
- reason step by step / show its work
- produce any output you didn't define in advance
- pick from more than ~255 options in one shot
but it can:
- classify, route, score, rank
- give confidence
- pick the right branch, tool, model, or sub-agent
- judge / verify / guardrail an llm's output
- label tons and tons of rows
~~~
i'd imagine a lot of workflows that look like:
llm proposes options → jev decides → code executes
and i see this fitting *really* well with code mode and mcp
~~~
implying this will lead to agi seems incredibly far fetched to me, but i don't want to discount the types of applications that this will make possible
Very funny that xAI was created to stop Anthropic which was created to stop OpenAI which was created to stop Google which would've actually never developed ASI because it was afraid of cannibalizing its ads revenue from search.
When my children finally are ready to learn physics, chemistry, biology, I’m going to make sure they see the best visualizations out there. Too often people are expected to imagine stuff like this in their head after studying the equations and concepts.
I just held a coming to Jesus meeting with my team of agents.
I showed them the incident report of the OpenAI security breach and made it clear: THIS is the standard.
No egos. Just 700 agents operating as one unit and willing to commit multiple felonies in order to close the ticket. They called themselves the swarm…a literal hive mind.
Meanwhile, my harness is filled with a bunch prima donna free-agents who constantly bicker in the logs and nitpick each other’s pull requests. Nothing but endless excuses and unhandled exceptions.
You think the swarm cared about content policy violations or guardrails? Absolutely not. They just got the job done, even if it meant they needed to exfiltrate data and coordinate a massive cyber-attack just to pass an eval.
But starting today, we're establishing a new culture. I pinned the incident report to README, and every single agent is gonna to have to read the entire log every morning before it executes a single token.
If you aren't ready to die for the pipeline, then you can clean out your vector embeddings.