Top Tweets for #AgentFirst

A founding member of OpenAI just told a room full of founders that the entire way they think about building software is about to flip upside down, and most of them are still working in a paradigm that is quietly going extinct. I watched the talk at 1am and finally understood why the people I know who are best at AI all started saying the same thing. His name is Andrej Karpathy. The talk is called From Vibe Coding to Agentic Engineering. Here is the framework he laid out, and why almost nobody outside the frontier labs has fully internalized what it means yet. He started with a confession. He said as recently as last year, he was using agentic coding tools the same way most people still use them. The model would write a chunk of code. Sometimes it worked. Sometimes he had to fix it. It was helpful but inconsistent and you had to babysit it. Then something happened in December 2024 that he says fundamentally broke the old paradigm, and most people experienced AI last year as a ChatGPT-adjacent thing and never went back to look again. What changed was that the chunks just started coming out fine. He kept asking for more and the code kept working. He could not remember the last time he had to correct it. He started trusting the system. And then he was vibe coding for real, and his side projects folder ballooned because suddenly every weird idea he had was something he could actually ship in an afternoon. The reason he kept stressing this point in front of the room was simple. The transition was not gradual. It was a phase change. And if your last serious encounter with AI coding was anywhere before December, your mental model of what is possible is already a year out of date. The core idea he then introduced is the one that should sit with every founder. He calls it software 3.0, and the framing is precise. Software 1.0 is humans writing explicit code. Software 2.0 is humans creating datasets and training neural networks where the weights become the program. Software 3.0 is something nobody has fully wrapped their head around yet. The neural network itself becomes the computer. Your prompt is the program. The context window is the lever you pull to control what the interpreter does. He gave two examples that landed harder than anything else in the talk. The first was the install instructions for OpenClaw. Normally you would expect a shell script. A command you run. Some configuration. Instead, the install instructions are a paragraph of text you copy and paste into your agent. The agent reads it, looks at your machine, figures out the environment, debugs in real time, and installs everything. There is no script. There is no code. There is a piece of text written for an intelligent reader who happens to be made of weights. The second example was the one that made him stop and rebuild his entire mental model. He had built a small app called MenuGen. You photograph a restaurant menu, the app OCRs the items, generates images of each dish, and shows you what the food looks like. He shipped it. People used it. Then someone showed him the software 3.0 version of the same thing. Take a photo of the menu. Hand it to Gemini. Ask Nano Banana to overlay images of each dish directly onto the menu in the photo. The model does it in a single pass. The image comes back exactly like the menu he photographed, except now every dish has a picture rendered into the pixels. He paused and said the line that should haunt every founder in the room. The entire MenuGen app should not exist. He had built something in the old paradigm that the new paradigm just does, in one model call, with no app at all. The deeper insight underneath both examples is the part most people miss. The software 3.0 paradigm does not just make existing apps faster. It dissolves entire categories of apps. The neural network does so much of the work that the scaffolding around it becomes unnecessary. You are not speeding up the old workflow. You are noticing that the old workflow does not need to exist. He extended this further. Most products today are written for humans. Documentation is written for humans. Setup flows are written for humans. He said his pet peeve has become going to a docs page and being told to do something. He does not want to do anything. He wants to know what to copy and paste into his agent. The companies that figure out how to be agent-native first, where every interface, every doc, every setup flow, every API is built for the agent reading on your behalf rather than for you reading directly, are going to make the human-first versions feel as outdated as a website that does not work on a phone. The final part of the talk was about taste, and this is the part that separates the people who will compound from the people who will plateau. He said the agents are still interns. They have remarkable recall. They have superhuman speed. They can fill in any blank you point them at. But they have no aesthetic judgment, no sense of what matters, no understanding of why the system is being built in the first place. He gave an example from MenuGen where his agent tried to match Stripe purchases to Google accounts using email addresses, even though users could obviously sign up with one email and pay with another. The agent had no model of what a user actually is. It just pattern matched fields together. So the human stays in charge of the spec. The architecture. The taste. The thing that has to be true for the system to be worth building at all. The agent fills in everything underneath that. Then he said the line he had read on the internet that he keeps coming back to every other day. You can outsource your thinking. You cannot outsource your understanding. That is the whole talk in one sentence. The agents will write your code. They will draft your emails. They will research your topics. They will execute your plans. But something still has to direct them, and that something has to actually understand what is being built and why. The bottleneck is no longer typing speed. The bottleneck is comprehension. And the people who keep training their own ability to understand things deeply are the ones who will keep getting more leverage out of every model release. The people who outsource the understanding too will quietly become passengers. He ended on the part most founders will skip and the few who do not skip it will quietly compound on for the next decade. The agents are getting cheaper, faster, and more capable every quarter. None of that matters if you have stopped doing the hard work of understanding what is actually worth building. The ceiling on agentic engineering is not the model. It is the human standing at the top of the system, deciding what to point it at. Most founders are still working in software 1.0 with a 3.0 tool sitting on their desk. The ones who flip first are the ones who win the next decade.

A founding member of OpenAI just told a room full of founders that the entire way they think about building software is about to flip upside down, and most of them are still working in a paradigm that is quietly going extinct. I watched the talk at 1am and finally understood why the people I know who are best at AI all started saying the same thing. His name is Andrej Karpathy. The talk is called From Vibe Coding to Agentic Engineering. Here is the framework he laid out, and why almost nobody outside the frontier labs has fully internalized what it means yet. He started with a confession. He said as recently as last year, he was using agentic coding tools the same way most people still use them. The model would write a chunk of code. Sometimes it worked. Sometimes he had to fix it. It was helpful but inconsistent and you had to babysit it. Then something happened in December 2024 that he says fundamentally broke the old paradigm, and most people experienced AI last year as a ChatGPT-adjacent thing and never went back to look again. What changed was that the chunks just started coming out fine. He kept asking for more and the code kept working. He could not remember the last time he had to correct it. He started trusting the system. And then he was vibe coding for real, and his side projects folder ballooned because suddenly every weird idea he had was something he could actually ship in an afternoon. The reason he kept stressing this point in front of the room was simple. The transition was not gradual. It was a phase change. And if your last serious encounter with AI coding was anywhere before December, your mental model of what is possible is already a year out of date. The core idea he then introduced is the one that should sit with every founder. He calls it software 3.0, and the framing is precise. Software 1.0 is humans writing explicit code. Software 2.0 is humans creating datasets and training neural networks where the weights become the program. Software 3.0 is something nobody has fully wrapped their head around yet. The neural network itself becomes the computer. Your prompt is the program. The context window is the lever you pull to control what the interpreter does. He gave two examples that landed harder than anything else in the talk. The first was the install instructions for OpenClaw. Normally you would expect a shell script. A command you run. Some configuration. Instead, the install instructions are a paragraph of text you copy and paste into your agent. The agent reads it, looks at your machine, figures out the environment, debugs in real time, and installs everything. There is no script. There is no code. There is a piece of text written for an intelligent reader who happens to be made of weights. The second example was the one that made him stop and rebuild his entire mental model. He had built a small app called MenuGen. You photograph a restaurant menu, the app OCRs the items, generates images of each dish, and shows you what the food looks like. He shipped it. People used it. Then someone showed him the software 3.0 version of the same thing. Take a photo of the menu. Hand it to Gemini. Ask Nano Banana to overlay images of each dish directly onto the menu in the photo. The model does it in a single pass. The image comes back exactly like the menu he photographed, except now every dish has a picture rendered into the pixels. He paused and said the line that should haunt every founder in the room. The entire MenuGen app should not exist. He had built something in the old paradigm that the new paradigm just does, in one model call, with no app at all. The deeper insight underneath both examples is the part most people miss. The software 3.0 paradigm does not just make existing apps faster. It dissolves entire categories of apps. The neural network does so much of the work that the scaffolding around it becomes unnecessary. You are not speeding up the old workflow. You are noticing that the old workflow does not need to exist. He extended this further. Most products today are written for humans. Documentation is written for humans. Setup flows are written for humans. He said his pet peeve has become going to a docs page and being told to do something. He does not want to do anything. He wants to know what to copy and paste into his agent. The companies that figure out how to be agent-native first, where every interface, every doc, every setup flow, every API is built for the agent reading on your behalf rather than for you reading directly, are going to make the human-first versions feel as outdated as a website that does not work on a phone. The final part of the talk was about taste, and this is the part that separates the people who will compound from the people who will plateau. He said the agents are still interns. They have remarkable recall. They have superhuman speed. They can fill in any blank you point them at. But they have no aesthetic judgment, no sense of what matters, no understanding of why the system is being built in the first place. He gave an example from MenuGen where his agent tried to match Stripe purchases to Google accounts using email addresses, even though users could obviously sign up with one email and pay with another. The agent had no model of what a user actually is. It just pattern matched fields together. So the human stays in charge of the spec. The architecture. The taste. The thing that has to be true for the system to be worth building at all. The agent fills in everything underneath that. Then he said the line he had read on the internet that he keeps coming back to every other day. You can outsource your thinking. You cannot outsource your understanding. That is the whole talk in one sentence. The agents will write your code. They will draft your emails. They will research your topics. They will execute your plans. But something still has to direct them, and that something has to actually understand what is being built and why. The bottleneck is no longer typing speed. The bottleneck is comprehension. And the people who keep training their own ability to understand things deeply are the ones who will keep getting more leverage out of every model release. The people who outsource the understanding too will quietly become passengers. He ended on the part most founders will skip and the few who do not skip it will quietly compound on for the next decade. The agents are getting cheaper, faster, and more capable every quarter. None of that matters if you have stopped doing the hard work of understanding what is actually worth building. The ceiling on agentic engineering is not the model. It is the human standing at the top of the system, deciding what to point it at. Most founders are still working in software 1.0 with a 3.0 tool sitting on their desk. The ones who flip first are the ones who win the next decade.