end of an era
I was the opening act for a family of ducks.
Thank you, Berlin. What a GTC.
Europe is building its AI ecosystem and economy, from AI factories to agents to robots.
DSX POD: Vera Rubin modular factories built, cabled and tested in the factory, then delivered ready to produce intelligence.
Agents: models, harnesses, sandboxes, knowledge and tools. NVIDIA Agent Toolkit brings the pieces together so companies control what their agents know, access and do. NVIDIA OpenShell enhances safety.
Physical AI: new customers across AI-RAN, robotaxis and robotics.
Personal AI: after four years building with Microsoft, RTX Spark brings personal agents to the Windows PC.
Thank you to President @EmmanuelMacron, Prime Minister @andyburnham and Chancellor @bundeskanzler for hosting me. Great to celebrate Sferical One with Sweden’s technology leaders. And thank you to President @TokayevKZ for the warm welcome.
And to our partners and NVIDIA teams: thank you for making it happen.
The keynote is here: youtu.be/rF1EsryCAwc
98
1001000𝕏 retweeted
I've been traveling the world a bit. One of the most incredible experiences was getting to visit Taiwan w/ @JensenHuang. It was wild 🤯.. huge crowds of engineers, insanely good street food at night markets, and of course a lot of good conversations across many days. I caught some of it on video, see below. Alright, that's it from me, love you all ❤️
Timestamps:
0:00 - Highlights
0:46 - Intro
3:25 - Computex: crowds, engineers, tech, future of AI
9:12 - Chat with Jensen: keynote prep & nerves
13:03 - Chat with Jensen: Taiwan's tech history
19:47 - Raohe night market
29:37 - Chat with Jensen: memories from childhood
33:44 - NVIDIA party
40:29 - Lunch: braised pig's feet
43:09 - Chat with Jensen: GPUs, AI, and competition
55:07 - Ningxia night market
1:10:14 - Taiwanese breakfast
1:29:54 - Outro
1001000𝕏 retweeted
nanochat now trains GPT-2 capability model in just 2 hours on a single 8XH100 node (down from ~3 hours 1 month ago). Getting a lot closer to ~interactive! A bunch of tuning and features (fp8) went in but the biggest difference was a switch of the dataset from FineWeb-edu to NVIDIA ClimbMix (nice work NVIDIA!). I had tried Olmo, FineWeb, DCLM which all led to regressions, ClimbMix worked really well out of the box (to the point that I am slightly suspicious about about goodharting, though reading the paper it seems ~ok).
In other news, after trying a few approaches for how to set things up, I now have AI Agents iterating on nanochat automatically, so I'll just leave this running for a while, go relax a bit and enjoy the feeling of post-agi :). Visualized here as an example: 110 changes made over the last ~12 hours, bringing the validation loss so far from 0.862415 down to 0.858039 for a d12 model, at no cost to wall clock time. The agent works on a feature branch, tries out ideas, merges them when they work and iterates. Amusingly, over the last ~2 weeks I almost feel like I've iterated more on the "meta-setup" where I optimize and tune the agent flows even more than the nanochat repo directly.
1001000𝕏 retweeted
Proud to work at Anthropic.
A statement from Anthropic CEO, Dario Amodei, on our discussions with the Department of War.
anthropic.com/news/statement…
1001000𝕏 retweeted
Since xAI was formed just 30 months ago, the small and talented team has made remarkable progress.
The future has never looked more exciting!
1001000𝕏 retweeted
A lot of people quote tweeted this as 1 year anniversary of vibe coding. Some retrospective -
I've had a Twitter account for 17 years now (omg) and I still can't predict my tweet engagement basically at all. This was a shower of thoughts throwaway tweet that I just fired off without thinking but somehow it minted a fitting name at the right moment for something that a lot of people were feeling at the same time, so here we are: vibe coding is now mentioned on my Wikipedia as a major memetic "contribution" and even its article is longer. lol
The one thing I'd add is that at the time, LLM capability was low enough that you'd mostly use vibe coding for fun throwaway projects, demos and explorations. It was good fun and it almost worked. Today (1 year later), programming via LLM agents is increasingly becoming a default workflow for professionals, except with more oversight and scrutiny. The goal is to claim the leverage from the use of agents but without any compromise on the quality of the software. Many people have tried to come up with a better name for this to differentiate it from vibe coding, personally my current favorite "agentic engineering":
- "agentic" because the new default is that you are not writing the code directly 99% of the time, you are orchestrating agents who do and acting as oversight.
- "engineering" to emphasize that there is an art & science and expertise to it. It's something you can learn and become better at, with its own depth of a different kind.
In 2026, we're likely to see continued improvements on both the model layer and the new agent layer. I feel excited about the product of the two and another year of progress.
There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. It's possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good. Also I just talk to Composer with SuperWhisper so I barely even touch the keyboard. I ask for the dumbest things like "decrease the padding on the sidebar by half" because I'm too lazy to find it. I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension, I'd have to really read through it for a while. Sometimes the LLMs can't fix a bug so I just work around it or ask for random changes until it goes away. It's not too bad for throwaway weekend projects, but still quite amusing. I'm building a project or webapp, but it's not really coding - I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works.
1001000𝕏 retweeted
+1 for "context engineering" over "prompt engineering".
People associate prompts with short task descriptions you'd give an LLM in your day-to-day use. When in every industrial-strength LLM app, context engineering is the delicate art and science of filling the context window with just the right information for the next step. Science because doing this right involves task descriptions and explanations, few shot examples, RAG, related (possibly multimodal) data, tools, state and history, compacting... Too little or of the wrong form and the LLM doesn't have the right context for optimal performance. Too much or too irrelevant and the LLM costs might go up and performance might come down. Doing this well is highly non-trivial. And art because of the guiding intuition around LLM psychology of people spirits.
On top of context engineering itself, an LLM app has to:
- break up problems just right into control flows
- pack the context windows just right
- dispatch calls to LLMs of the right kind and capability
- handle generation-verification UIUX flows
- a lot more - guardrails, security, evals, parallelism, prefetching, ...
So context engineering is just one small piece of an emerging thick layer of non-trivial software that coordinates individual LLM calls (and a lot more) into full LLM apps. The term "ChatGPT wrapper" is tired and really, really wrong.
1001000𝕏 retweeted
📃The rise of context engineering
"Context engineering" has been an increasingly popular term used to describe a lot of the system building that AI engineers do
But what is it exactly?
The definition I like:
"Context engineering is building dynamic systems to provide the right information and tools in the right format such that the LLM can plausibly accomplish the task."
Builds upon takes from @tobi @dexhorthy @walden_yan @ankrgyl
Not a new concept - agent builders have been doing it for the past year or two, and a lot of the tools we've build (LangGraph, LangSmith) have been built to assist with it. But it's a new term which will hopefully draw new attention to the skills and tools needed to do this properly.
blog.langchain.com/the-rise-…
Colab.new life
As announced on Google's Keyword blog today, we've expanded access to AI coding features in Colab to users in the free-of-charge tier.
Watch the accompanying video to see the HousaNLP team in Nigeria talk about how Colab has helped their research! youtube.com/watch?v=kw0CZkFE…
139

















