It’s the week of Jev! I’m really, really, really, really excited about it. I mean: really.
It’s like someone blew up a confetti bomb in the world of LLMs and now you realize how grey everything looked before.
But Jev is not an LLM. It’s a model “built to make fast, structured decisions that software can use directly.” TypeSafe says we should think of Jev “as a frontier-intelligence function call: unstructured state in, typed probabilistic decisions out.”
I explained it as a “smart if-statement” to someone and my only slightly longer explanation is this:
Think of how you’d get an LLM to decide between a fixed set of options.
Then imagine it orders of magnitude faster and cheaper.
“What’s the best label for this?”
“Should I click here or there?”
“What’s the next line I should look at?”
“Do I go left or right?”
“Invalid or valid?”
“Which of these widgets should I show?”
I had Amp build a little Copilot-style autocomplete for a shell, with Jev picking the next most likely command from shell history. Then Amp built a Neovim plugin (and called it hunch.nvim, which is a great name) that uses Jev to predict the line you next most likely want to jump to. Now, let’s linger on this a bit.
Two years ago, that was what Cursor was famous for. Yes, Cursor did and does more than that and the quality isn’t close, but… when we were working on Zed’s Edit Predictions we had to fine-tune a model to get into the same league! Now it’s a single API call and the latency is 200ms. That is incredible!
Then I built a prototype that uses Jev to turn the Amp Dial, switching between models based on your prompt.
Yes, all of this was possible before, but it’s so fast and so cheap that I still can’t believe it.
Sometimes a change in cost and performance is what creates a whole new category of technology. In my room, there are lightbulbs that contain computers, that can talk over a local network with me. Yes, we had computers in homes in the 70s and 80s, but no one would’ve ever thought that we’d have so many computers that are so tiny and cheap that we’d put them in freaking lightbulbs.
That’s what makes me so excited about Jev. It feels like we now have a truly smart Lego brick that we can use everywhere. Fun times.
What I believe about the future of software development. I posted this originally on X, saying that most predictions I see are still way too conservative, and it completely blew up.
“I don’t like passkeys”. Passkeys are such a weird technology. I can see how they’re technically brilliant and solve a lot of issues, but it does feel like Google and Apple and 1Password invited The Guy Who Invented Cookie Banners and said: what would you do, how would you roll this out?
Colossus published a very long Mark Zuckerberg profile. Fascinating read. It’s very well written and somehow managed to make me think thoughts about Zuckerberg that I haven’t thought before, which is quite the feat, considering that we’ve all been aware of Zuckerberg for, what, nearly twenty years now?
Einride and Lidl Launch First Autonomous Cab-less Truck on German Public Road. As an Aldi man myself, let me say: hell yeah, let’s go, Lidl!
How To Write With An LLM. I like this! I still don’t know how to use LLMs for writing, because I never want them to write something for me and even seeing how they would write it seems to poison my brain. I should probably add an “only tell me what to change and why, but never ever show me how you’d write it” to my system prompts.
Marc Brooker, Distinguished Engineer at AWS: “I believe that, long-term, humans have no role in routinely reviewing code. […] The idea that humans will reliably look through code to find the increasingly rare issues that automated tools miss seems like a fantasy.” Yep.
I wanted to link to Powermove here and say “look, editable software! It’s happening! Jellyware!” but now realize that it’s not quite that yet. It’s a video editor with an agent inside, but it doesn’t seem like you can edit the video editor itself. That’s coming, though.
We are all Product Engineers now: “The cost of writing code collapsed, and the cost of reviewing, fixing and operating it is following, and I’m assuming it gets there. What’s left of making software is finding out what people actually want, defining it precisely, and making it pleasant to use. That cost is per piece of software and doesn’t transfer, so as the amount of software goes to infinity, which it will because there’s no ceiling on demand, that cost becomes the whole job. That job is called a product engineer.” Obviously agree, but what I didn’t know about was Google’s APM program: “Formalized training of product people barely exists. Google’s APM program, which Marissa Mayer started in 2002 and which is the template everyone copies, takes about fifty people a year out of something like twelve thousand applicants.” Would love to read more about it.
“I asked Astra to create an interactive aquarium wallpaper for my Mac. The fish respond to the cursor!” Beautiful!
John Gruber, Daring Fireball, with Thoughts and Observations on Apple’s ‘Surprise and Shine’ Event; the Announcements of the iPhones 18 Pro, AirPods 5, Apple Watches Series 12 and Ultra 4, and the iPhone Duo; and the Dawn of the Ternus, John Ternus Era at Apple. Yes, that’s the title. The whole thing is Peak Gruber, I love it. What a writer. Now, I really do enjoy his words and sentences, but let me also use this occasion to say how much I admire him as a Pedantic Punctuation Pro: the numbered lists vs. the bulleted lists, the space between the numbers and the colon in aspect ratios, using × in display resolutions, … You could show me this sentence without any other context and I’d say it was written by Gruber: “The original iPhone (2007) display was precisely 3 : 2 (480 × 320 pixels, and let’s call it 1.5 : 1 for comparison’s sake to the following ratios), and this remained true through the iPhone 4 and 4S (960 × 640 pixels, 2× retina).”
This was a very entertaining and fascinating read: why I can’t stop thinking about Papua New Guinea and what I think everyone should know about it. I’ve become somewhat of a Papua New Guinea Head myself (that’s what they call us (no, they don’t)), after reading this piece, They Burn Witches Here, nearly a decade ago. I couldn’t shut up about it at work. For two weeks straight: “Dude, did you know that in Papua New Guinea…” Until one day a colleague said: “Yeah, I did know.” Turns out that colleague, Nick Skelton, was a tour guide in PNG (as we call it) and even wrote a book about it, which I immediately ordered and read.
Moats & the Barbell-ification of Software: “Long term, I think the evolution of the software industry might mirror what happened to newspapers in the 1990s. There will be a smaller number of very large software companies. […] I also think there will be one large software company by industry (e.g., Legal, Finance, Medicine) […] I think most mid-sized point solutions will likely be consolidated or die off. The optimal strategy for the winner will be to do it all. […] Lastly, I think there will be an explosion of “small” software. Most of this will be people building software for themselves or their own companies, but I think there might also be an explosion of small software businesses that make niche software, similar to the D2C explosion of the 2010s (powered by Shopify and Meta Ads).”
AI-generated posters don’t have to be horrible. Yes! Exactly! Now, read this, and then imagine you’re a person who can come up with all these styles without having to ask ChatGPT first. And then, on top of that, imagine that the very same person also knows something about music, and literature, and politics. Imagine how they could combine what they know and mix and remix. That, I think, will be valuable in the future.
Window Sweaters: “A little Mac app I made to give my windows sweaters. 🧶 Knitted borders, colours inspired by your favourite apps, and a cosier desktop.”
