I wrote about a question we’ll have to ask our AI agents: who are you actually working for?
Knowing what I want doesn’t help much if someone else paid to narrow my options.
My piece for Every’s Thesis about the world "After automation": every.to/thesis-statements/t…
Ooof. The experience with 6.2 Astra and Sol have been rough so far, and seems universally shared opinion across many, many ppl. Will be interesting to see how OpenAI reacts and iterates.
Some of you have been asking very politely. Some of you have just been asking.
GPT-6.2 Astra and Sol are now available.
Super efficient and built to perform where it counts—the real world.
openai.com/index/introducing…
Over the past week, I’ve been overwhelmed by the love and support of friends, industry colleagues, and people I've never met. Thank you to everyone who has shown kindness to my family and me. It means the world to me.
I came to the United States 53 years ago, and becoming an American citizen is one of the greatest gifts and proudest moments of my life. NVIDIA has been my life’s work. Building it into the company it is today alongside my colleagues has been a privilege and an honor. Nowhere but in America could a company like NVIDIA be possible. I love our country, and I love NVIDIA.
I did not live up to the standards expected of everyone at NVIDIA, and I have made serious mistakes in my personal life. I created problems for the Board that I deeply regret. I own my mistakes completely, and I am committed to cooperating with the Board’s independent investigation.
Since my departure, I’ve seen an outpouring of calls from NVIDIA’s employees, investors, business partners, and customers for me to return as CEO. Many continue to reach out to me directly as the company navigates complex technology, market, competitive, and geopolitical dynamics. NVIDIA is a once-in-a-generation company. If the Board of Directors decides that my return is in the best interest of our shareholders, our employees, the company, and America, I would be honored to answer these calls and return as CEO.
Thank you again to everyone who has shared their good wishes. I am profoundly humbled by your support. To my family: I love you, and I will spend the rest of my life being worthy of yours.
Jensen
A key point @satyanadella makes is to maintain a separation of AI church and state: keep the harness, memory and model decoupled. This decoupling gives you the flexibility to swap any of them.
Model and harness are already the easy swaps. Our skills pretty much run fine in both Claude Code, Codex, etc. Memory is still the hard one, and every AI app wants to be the place it lives.
The next real fight will be over who holds your agent's and organization’s memories, not whose model is smarter. That context is key to unlocking outsized results from your agents.
What does software engineering look like when generating the code becomes cheap and verifying it is the hard part? A rare podcast focused on everything around building software, with @satyanadella. Timestamps:
00:00 Intro
02:12 Microsoft’s open-source shift
04:15 Building VS Code in the open
05:55 Copilot, Cursor, and Claude Code
09:52 Decision engines
12:32 Verifying AI-generated code
15:39 The software factory
20:45 Bringing AI to existing products
24:06 Why adopting AI is different to adopting React
26:29 The changing role of software engineers
29:25 Microsoft’s voluntary exit offers
34:05 AI anxiety and changing roles
36:35 Junior hiring
42:36 Open models
45:39 Owning your AI infrastructure
51:21 Building trust in AI agents
53:48 Local models and hybrid intelligence
56:39 Microsoft’s model strategy
59:26 Advice for engineers
1:01:21 Closing takeaways
Brought to you by:
• @turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. turbopuffer.com/pragmatic (I built a greatly improved podcast/newseltter search with it, check it out: pragmaticengineer.com/search)
• @linear – the product development system for teams and agents. linear.app/pragmatic
• @WorkOS – everything you need to make your app enterprise-ready. workos.com/
3 interesting takeaways from Satya:
1. A new form of software engineering: teams building software factories to improve their work.
Satya cites the Azure networking team which manages 500+ fiber network operators and recently built an agentic system to better manage emails and processes. Now, they operate much more efficiently as a result. Satya sees this as the reality of “AI transformation”: brownfield work on building software factories to improve how teams operate, all while continuing the day-to-day work.
2. “Own the intelligence”: avoid lock-in & treat agents as an insider risk.
Satya cautions companies to avoid lock-in with any single model provider by ensuring that the harness, memory, and model are not coupled, so that they can be changed with ease. He also thinks more companies should consider using open models as a way to protect their core intellectual property (IP) from leaking out, and build private evals to decide what models to use and upgrade to. He also says that models are intelligent but unreliable, so it’s best to treat them as “insider risks” and build a separate system to verify that agentic systems work as expected.
3. What’s with those voluntary exit offers?
I asked Satya directly why Microsoft recently made voluntary exit offers to most of its software engineers for the first time in the company’s history. I also wanted to know if it could mean layoffs in the future. Unsurprisingly, his reply was diplomatic, but in the podcast I rehashed what I heard in a more direct way.
I made a game you play by humming. It’s inspired by good ole flappy bird and the shan shui art style.
Your pitch is the crane's altitude, and silence means you fall.
Fair warning, you'll look ridiculous playing this in public. Watching my kids play this for like 20 mins was hysterical.
It's most fun on your phone, but will work on any device with a mic.
demos.trev.in/hum
Someone made his old TV 10x faster without buying a new one.
His LG TV took 30 seconds to open Plex. So he sat down with Claude Code and rebuilt the app from scratch in Rust, with his own graphics engine.
Now it opens in 3 seconds. It's called PlxNative and works on LG TVs from 2018 on.
The smartest part: one person did the work of an engineering team.
The thing that’ll never get old is using personal agents like @muse to do tasks I would otherwise forget to do or defer indefinitely.
In this case I had to buy new tires for our car and there’s a manufacturer’s rebate. The install receipt was in my inbox so @muse was able to complete it.
The original Heat one of my favorite movies of all time, I’ve probably watched it at least 25 times over the years.
I really hope this sequel is actually good and doesn’t victimize us like Gladiator 2 did.
Michael Mann’s HEAT 2 (2027) officially begins production on January 19.
The cast includes Leonardo DiCaprio, Christian Bale, Adam Driver, Stephen Graham, Odessa Young, Ebon Moss-Bachrach and Jason Clarke.
agent-browser v0.43
→ up to 7.5x smaller
→ starts in 2 ms
No more Node wrapper: npm, pnpm, yarn and bun link straight to the native binary for your platform
This is worth a read as it reinforces security issues with chat transcripts.
The chain started with an access key Cursor had issued to Fireworks, and the bucket it opened held mostly 2025 agent traces from sessions outside Privacy Mode. A few of those traces still had API keys people had pasted in, unredacted, and the attacker used them to get further in.
Lesson: The key you pasted into an agent chat "just this once" can sit in a training bucket a year later. Treat anything you've ever pasted into an agent as leaked and rotate it.
We’ve published an update on our recent security incident. See a detailed overview of what happened and our remediation steps here: cursor.com/blog/security-inc…