it’s in gemini, just create it in ai studio. oh, that’s for your personal google one account. for workspace you need gemini business. no, not gemini advanced, that’s ai pro now. unless you need ai ultra. oh agents? you do that in spark actually. no, not gemini api managed agents, that’s different. for coding use jules. unless you mean the agentic ide, that’s antigravity. no, that’s the old antigravity, download the new one. actually gemini cli is being deprecated, use antigravity cli. no the flash model is smarter than the pro model. unless you need pro. if it’s video, use flow. no, flow uses veo. no, nano banana is images. actually that’s in gemini now. unless you’re in search, then it’s ai mode. no, research is notebooklm. anyway it’s all very simple.

Personal update: I've joined Anthropic. I think the next few years at the frontier of LLMs will be especially formative. I am very excited to join the team here and get back to R&D. I remain deeply passionate about education and plan to resume my work on it in time.

The real tenor in SF is as it would be at the moment AI is usable, more or less at AGI, still expensive and the domain of a priesthood That priesthood is building now, and this is the moment the hobbyist and the inaccessible enterprise tech becomes ubiquitous Personal AI coming

I built an MCP for LinkedIn with @NikolaiWotton! It uses their own APIs and runs on your Mac so it’s super fast + reliable. Get Claude to analyze your biz ops strategy, it can even send messages & connection requests for you. Grab the beta here: candle.fi

It can be unsettling when you notice that a technical assumption you've been making for 40 years has quietly expired. This happened to me a few minutes ago. I maintain a game called "greed". It's an old-style game from the days of character-cell terminals. Not quite a classic deserving of museum status like Colossal Cave Adventure or nethack, but worth keeping alive because it's still solidly playable. And people still are playing it, because yesterday I got a minor bug report about it. Nothing user-visible, just a silly C build problem. I fixed it. Then, because I'm generally trying to get my old C projects out of C into more modern and safer languages, I tried asking my robot friend to port it to Rust. Which it promptly did. But then I noticed something that irritated me. The Rust code had a bunch of unsafe blocks in it, which went directly against my reasons for moving it to Rust. On further examination, I discovered that it was calling the C curses library to do its screen painting. This is where I have to explain about curses. It's an ancient C library for writing TUIs. It looks in your environment for a variable named TERM, uses its value to dredge a bunch of magic strings out of a system-wide database called "terminfo" that tells it how to manipulate your terminal, and then uses those magic strings for screen painting. On modern systems, TERM is always some variant of a color ANSI terminal. In times past, when people attached a wild variety of character cell terminals to Unix systems rather than just sitting at the console, it could have been lots of other things. Those days are gone, but the habit of always going through terminfo so you can support a couple of hundred terminal types has persisted. I prod robot friend to find me a pure Rust equivalent of curses so I don't have to do unsafe and call C code. It says, yes, there is such a thing and it's called crossterm. I tell it: change this code to use crossterm. Robot friend grinds for a bit, and then tells me it can't do that because I don't have cargo (the Rust package manager) installed. This is because I never write Rust by hand. When I ship programs written in Rust, it's because I ported them from some other language and don't expect to ever touch them again without having a robot to do the code-grinding for me. This is when things get slightly strange. It tells me that instead of porting to crossterm, it has written into the greed Rust source its own little screen-painting backend the implements a subset of curses calls and (this is the important part) assumes it's talking to a color ANSI terminal. Robot friend is not an old Unix hand. It doesn't know the unwritten law of the deep magic that you always go through terminfo because...because you might have to support hundreds of terminal types that no longer exist in this century? I blink. I look at the Rust code for the back end. It is small and elegant. No more unsafe. No more dragging around a bunch of C library code. This is ... the right thing? I push it to the public repository. What sealed the deal is that code, even code in a language as rebarbative as Rust, is wet clay now. If, against all odds I get a bug report that says somebody wants to play greed on something that isn't an ANSI terminal emulator, reinstating full curses support will take a one-sentence prompt to my robot friend and mere minutes. I hadn't had to directly confront before the fact that the entire set of assumptions that made TERM and terminfo a thing are as obsolete as dial-up acoustic modems. Still, the moment when I tossed away one of the ancient laws of Unix coding felt a bit like the universe lurching sideways. Indeed do many things come to pass...

A 2005 state-designed worm designed to corrupt physics simulations sat undetected on VirusTotal for nearly a decade. Fast16, intercepted executable files at the kernel level and silently rewrote floating-point calculations to make them produce slightly wrong answers. Targets: high-precision engineering suites used for structural analysis, crash simulations, and physical process modeling, including LS-DYNA, a tool cited in reports on Iran's nuclear weapons research. The sabotage vector relied on deployment of the driver across a network via worm, corrupting calculations on every machine, and eliminating the possibility of cross-checking results against a clean system. Stuxnet got the documentary. Fast16 got twenty years of nothing. sentinelone.com/labs/fast16-…

Something strange is happening in tech. CTOs of billion dollar companies are quitting to take IC roles at Anthropic. Workday CTO -> MTS (Mar 2026) You[.]com CTO -> MTS (Mar 2026) Instagram CTO -> MTS (Jan 2026) Box CTO -> MTS (Dec 2025) Super[.]com CTO -> MTS (July 2025) Adept AI CTO -> MTS (Jan 2025) The mission is that real.