September 9 was supposed to be the foldable show, and in a way it was: the iPhone Duo, Apple’s first folding phone, $1,999, in stores October 23. But the moment I keep replaying is the opening. John Ternus, in his first keynote as CEO, did not start with hardware. He described what the perfect AI device would be, then claimed the iPhone already is one: “something that is always with you, deeply personal, and able to bring intelligence to the moments when it matters most.” Five days later Siri AI started rolling out on iOS 27. Read in order, the keynote stops being a device story. Apple unveiled a chassis; the product is the agent.

A few weeks ago I watched a video with a title that sounds like a taunt: “AI Was Supposed To Take Your Job. Why Hasn’t It?” (Maxinomics, July 2026). Halfway through, it dropped a fact I could not shake off. The US census has been cataloguing occupations for over a century, and for all the noise about machines eating work, history contains only one job that a single technology completely erased: the lift operator. Meanwhile the airline pilot — whose routine flying has been largely handed over to computers for decades — is more in demand than ever. Same big wave of automation. Two jobs. Opposite outcomes.

Moonshot AI dropped Kimi K3.1 Pro on October 23. It’s the first model in their new K3.1 series, a 3T-class open-weight model with a 1-million-token context window. The weights go public by November 4. For anyone tracking the open-vs-proprietary gap, this release matters — it’s the closest an open model has come to matching the frontier on coding and agentic benchmarks.

Two things are true at the same time in my world right now. Every experienced developer I know ships noticeably more with an agent sitting next to them — and every junior I know is finding it harder to get a first job. A note I left myself a while back put it as a question: is the real transition not “fewer programmers” but “fewer programmers per unit of software”? And if so, what happens to the career ladder when the bottom rung disappears?

Google finally shipped a new flagship this week. Gemini 4 Argon was announced on September 30 — the first new Gemini generation in nearly a year, after the June model that never arrived and a summer of uncomfortable press about DeepMind morale. I have learned to read launch-week benchmark charts the way I read vendor load-test reports: politely, and then I check who ran the test. So forget the crown for a minute. What actually matters to me, as someone who ships AI systems inside a bank, is the shape of this release: defenders first, everyone else later, and a cyber-capable version going out the door with the guardrails off to a vetted few.

That pattern should look familiar. It is the same two-track playbook every frontier lab is converging on.

Two years ago I wrote that in RAG, retrieval is the bug, not the model. I spent that winter fiddling with chunk sizes and embeddings and blaming the ranker every time an answer went sideways. This year I noticed something funny: every agent sketch I draw on a whiteboard ends at the same boring box. Not a shiny new vector startup. Postgres.

A seed note I left myself asked the obvious question: does the AI revolution make the boring relational database more important rather than less? After watching Neon, Supabase, Lakebase, and the Kubernetes folks all converge on the same answer, I think it does.