A walkthrough of why Typesafe's new model "Jev" matters, framed as the history of classifiers \u2014 machines that sort things into piles rather than write answers. The speaker traces the line from Rosenblatt's 1958 perceptron through Paul Graham's 2002 spam filter and 2012 image recognition, all of which required custom training, to zero-shot LLM classification, which works but is slow and expensive. Jev is pitched as a fast, sub-cent, single-API-call classifier that returns a label plus a calibrated confidence number, and the speaker shows a small real example: a plain-English markdown "decision file" that Claude turned into a working script on the first try.
- Classifiers answer only one question \u2014 which pile does this go in \u2014 and the speaker argues a huge share of everyday software is doing exactly that.
- The history runs from Rosenblatt's 1958 perceptron (which learned left from right after 50 tries on a $2 million borrowed computer) through Minsky and Papert's 1969 book and the first AI winter, to Paul Graham's 2002 spam filter that missed under five spams per thousand without discarding a real email, to the 2012 neural network that sorted a million photos into a thousand categories.
- Every classical classifier needed labels, thousands of examples, ML expertise, and weeks of work per new task, so small businesses and individuals effectively got no classifier at all.
- LLM zero-shot classification solved the access problem but is "like hiring a professor to sort your mail" \u2014 slow, expensive, essay-laden, and inconsistent across repeat calls.
- Jev takes three question shapes \u2014 pick one from a list, yes/no, or rate on a described scale \u2014 and returns each answer with a calibrated confidence number you can write threshold rules against (above 0.8 act, below 0.5 escalate, in between act but flag).
- The name references Jevons' 1865 observation that cheaper coal-burning engines increased coal use; the bet is that cheap decisions get made in places nobody bothered before \u2014 the speaker priced labeling all 26,000 markdown files on his desktop at about $2.65.
- His usage test: if a step where you currently use an LLM outputs a pick, rating, or yes/no and happens more than a few times, it's a classifier in an expensive coat; if the output is a paragraph, keep the LLM, and if code can compute it exactly, use code.
- In his demo, a plain-English markdown file with three questions plus thresholds ran in about half a second for two thousandths of a cent, returning "a plan" at 100%, "no receiver named" at 91%, and readiness 1.5 of 3 at 59% \u2014 which tripped the flag-for-human rule.
- He admits a purpose-trained classifier still beats Jev on its own task; what changes is who gets a classifier at all.
The clearest articulation of the gap Jev fills, plus an honest caveat that purpose-trained classifiers still win on their own task.
It's a bit like hiring a professor to sort your mail. Brilliant, slow, expensive. Every envelope comes back with an essay about it when all you wanted was a desk name.
Explains calibration and the threshold pattern that makes these outputs safe to automate, then gives a one-line test for whether your own LLM step should be replaced.
Because you can put a rule on a number, above 0.8, just do it. Below 0.5, show a person. In between, do it, but flag it... So across lots of answers, when it says 80%, it should be right about 80% of the time.
The Navy expected it to walk, talk, see, write, reproduce itself, and be conscious of its own existence. What it actually did was learn to tell left from right after 50 tries.
That step is essentially a classifier wearing a very expensive coat.
The LLM writes the if statement once, and Jev runs it forever.