Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

The creator of Ruby on Rails just said programmers may be worse at AI coding than people who cannot code. Lex Fridman asked David Heinemeier Hansson directly. His answer: 100%. Because once the AI handles the implementation, knowing how to write a loop is no longer the rare skill.... The valuable skills become: What should this product do? Who is it for? What should version one include? What needs to be removed? What should the AI build first? A traditional programmer may tell the agent exactly how to solve the problem. That experience can become a trap. The agent follows the old path instead of finding a better one. Meanwhile, someone who understands users, products, priorities, and taste can describe the desired result and let the agent choose the route. Programming knowledge still matters when the system breaks. But AI is moving the bottleneck away from writing code. The advantage now belongs to the person who knows what should exist, not merely how to implement it. WATCH FULL PODCAST ON Lex Fridman YT CHANNELshow more

Ihtesham Ali

50,406 subscribers

142,189 views • 7 days ago •via X (Twitter)

Science & Technology Education

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

A DEVELOPER PROVED THAT MOST OF THE CLASSES YOU WRITE SHOULD NEVER HAVE BEEN CLASSES AT ALL 27 minutes from Jack Diederich, a Python core developer, on how much of your code is just a function wearing a costume. -> The moment it lands, the rule is brutal: if a class has two methods and one is __init__, you meant to write a function. Most people add structure to feel like real engineers. It just adds weight no one ever needed. Writing more code was never the skill -> writing less of it is. And when an AI agent happily generates ten classes for a job that needed three lines, the person who knows what to delete is the one who ships something clean. Anyone can add abstraction. Knowing when not to is the whole job. Bookmark it and Watch ↓

A DEVELOPER PROVED THAT MOST OF THE CLASSES YOU WRITE SHOULD NEVER HAVE BEEN CLASSES AT ALL 27 minutes from Jack Diederich, a Python core developer, on how much of your code is just a function wearing a costume. -> The moment it lands, the rule is brutal: if a class has two methods and one is init, you meant to write a function. Most people add structure to feel like real engineers. It just adds weight no one ever needed. Writing more code was never the skill -> writing less of it is. And when an AI agent happily generates ten classes for a job that needed three lines, the person who knows what to delete is the one who ships something clean. Anyone can add abstraction. Knowing when not to is the whole job. Bookmark it and Watch ↓

slash1s

269,515 views • 2 months ago

Marc Andreessen explains why AI coding won't replace programmers, but fundamentally change what they do. He argues that AI coding is just the latest abstraction layer, and the job of a programmer has always evolved with each one. Andreessen's key reframe of what's actually happening: "AI coding actually abstracts away the process of actually writing the scripting code... This is the next layer of the task redefinition under the job of programmer." He's clear that the best programmers aren't being replaced. They're already adapting, even if their day-to-day looks radically different now. Their job has shifted from writing code line by line to managing dozens of AI agents working in parallel. "The world's best programmers today will tell you, 'My job is I'm sitting there and I'm orchestrating 10 code bots running in parallel.' Their day job now is kind of arguing with the AI bots to try to get them to write the right code." But Marc Andreessen 🇺🇸 is adamant this doesn't make foundational knowledge obsolete — it makes it more important. "You need to still fully understand and learn how to write and understand code, because if it doesn't work or it's not doing what you expect, you need to be able to understand the results of what the AI is giving you." He draws a direct parallel: Just as someone writing scripting languages still needs to understand how a microprocessor works, someone orchestrating AI bots needs to understand the code those bots produce. "It's this upleveling of capability where you actually want the depth to go down and understand what the thing is actually doing, even if you're not spending your day doing that by hand." The result, in his view, is transformative: "Now programmers are going to be 10 times or 100 times or a thousand times more productive. And that is overwhelmingly a good thing." The pattern: New abstraction layer emerges → tasks change → the job gets redefined upward → productivity explodes It raises a question every programmer should be sitting with... Are you building the depth to evaluate what AI gives you, or just accepting the output?

Marc Andreessen explains why AI coding won't replace programmers, but fundamentally change what they do. He argues that AI coding is just the latest abstraction layer, and the job of a programmer has always evolved with each one. Andreessen's key reframe of what's actually happening: "AI coding actually abstracts away the process of actually writing the scripting code... This is the next layer of the task redefinition under the job of programmer." He's clear that the best programmers aren't being replaced. They're already adapting, even if their day-to-day looks radically different now. Their job has shifted from writing code line by line to managing dozens of AI agents working in parallel. "The world's best programmers today will tell you, 'My job is I'm sitting there and I'm orchestrating 10 code bots running in parallel.' Their day job now is kind of arguing with the AI bots to try to get them to write the right code." But Marc Andreessen 🇺🇸 is adamant this doesn't make foundational knowledge obsolete — it makes it more important. "You need to still fully understand and learn how to write and understand code, because if it doesn't work or it's not doing what you expect, you need to be able to understand the results of what the AI is giving you." He draws a direct parallel: Just as someone writing scripting languages still needs to understand how a microprocessor works, someone orchestrating AI bots needs to understand the code those bots produce. "It's this upleveling of capability where you actually want the depth to go down and understand what the thing is actually doing, even if you're not spending your day doing that by hand." The result, in his view, is transformative: "Now programmers are going to be 10 times or 100 times or a thousand times more productive. And that is overwhelmingly a good thing." The pattern: New abstraction layer emerges → tasks change → the job gets redefined upward → productivity explodes It raises a question every programmer should be sitting with... Are you building the depth to evaluate what AI gives you, or just accepting the output?

Big Brain AI

45,341 views • 6 months ago

🚨 this chinese guy makes over $1,000,000 a year… by building AI agents. no employees. no massive startup. he just keeps building. while most people are still asking ChatGPT random questions, he’s using Claude to build software that solves real problems. this is what people call vibe coding. he opens Claude and says: “build me an AI agent for real estate businesses that creates property videos.” Claude writes the code. builds the interface. adds subscriptions. helps deploy the app. within a day, he has a working product. then he starts building the next one. that’s the part most people don’t understand. he isn’t trying to build one billion-dollar company. he’s building dozens of AI agents, each solving one problem for one industry. → an AI agent for dentists → an AI agent for ecommerce brands → an AI agent for podcasters → an AI agent for real estate businesses each one automates work that people normally do by hand. each one is built with simple prompts. each one can become a real business. the crazy part? you don’t need to be a software engineer anymore. you need to know how to think like a builder. how to spot problems. how to explain solutions to AI. and how to ship. that’s exactly why i’m reading this article: “How to Actually Build Your First AI Agent.” because this is the skill that’s creating the next generation of builders. the people who learn to build AI agents today won’t just use AI. they’ll own the tools everyone else ends up paying for.

🚨 this chinese guy makes over $1,000,000 a year… by building AI agents. no employees. no massive startup. he just keeps building. while most people are still asking ChatGPT random questions, he’s using Claude to build software that solves real problems. this is what people call vibe coding. he opens Claude and says: “build me an AI agent for real estate businesses that creates property videos.” Claude writes the code. builds the interface. adds subscriptions. helps deploy the app. within a day, he has a working product. then he starts building the next one. that’s the part most people don’t understand. he isn’t trying to build one billion-dollar company. he’s building dozens of AI agents, each solving one problem for one industry. → an AI agent for dentists → an AI agent for ecommerce brands → an AI agent for podcasters → an AI agent for real estate businesses each one automates work that people normally do by hand. each one is built with simple prompts. each one can become a real business. the crazy part? you don’t need to be a software engineer anymore. you need to know how to think like a builder. how to spot problems. how to explain solutions to AI. and how to ship. that’s exactly why i’m reading this article: “How to Actually Build Your First AI Agent.” because this is the skill that’s creating the next generation of builders. the people who learn to build AI agents today won’t just use AI. they’ll own the tools everyone else ends up paying for.

MIKE

39,041 views • 2 months ago

Andrej Karpathy: "The future is not writing code. The future is writing the loops that write the code. The leverage point has moved one floor up." This is the shift that defines the next era of coding and quant building. 1 hour of pure insight on agentic AI coding and loop engineering from the OpenAI co-founder who just joined Anthropic to build self improving Claude. Worth more than every $500 vibe coding course combined. Watch it, then read the full guide on how to build your first self improving quant trading loop below.

Andrej Karpathy: "The future is not writing code. The future is writing the loops that write the code. The leverage point has moved one floor up." This is the shift that defines the next era of coding and quant building. 1 hour of pure insight on agentic AI coding and loop engineering from the OpenAI co-founder who just joined Anthropic to build self improving Claude. Worth more than every $500 vibe coding course combined. Watch it, then read the full guide on how to build your first self improving quant trading loop below.

Roan

37,862 views • 2 months ago

Every time I hear “Stop learning to code. AI will do it,” I worry. That is dangerous advice. Andrew Ng nailed it. When something becomes easier, more people should do it, not fewer. When coding moved from punch cards to keyboards, demand exploded. When higher level languages replaced assembly, people predicted the end of programmers. They were wrong. Now AI assisted coding is here. For the first time, a GenAI native graduate can outperform an experienced engineer stuck in old workflows. Impressive. But here’s what matters. The real advantage belongs to those who combine deep architectural thinking with AI fluency. In the companies I advise, the pattern is clear: - Experienced engineers who master AI - Deep thinkers who combine architecture + automation - Professionals who upgrade instead of resist AI lowers the barrier. It does not lower the ceiling. So let me ask you: Are you upgrading your skills with AI… or quietly assuming it will make your skills obsolete? #AI #ArtificialIntelligence #Coding #SoftwareEngineering #FutureOfWork #Technology

Every time I hear “Stop learning to code. AI will do it,” I worry. That is dangerous advice. Andrew Ng nailed it. When something becomes easier, more people should do it, not fewer. When coding moved from punch cards to keyboards, demand exploded. When higher level languages replaced assembly, people predicted the end of programmers. They were wrong. Now AI assisted coding is here. For the first time, a GenAI native graduate can outperform an experienced engineer stuck in old workflows. Impressive. But here’s what matters. The real advantage belongs to those who combine deep architectural thinking with AI fluency. In the companies I advise, the pattern is clear: - Experienced engineers who master AI - Deep thinkers who combine architecture + automation - Professionals who upgrade instead of resist AI lowers the barrier. It does not lower the ceiling. So let me ask you: Are you upgrading your skills with AI… or quietly assuming it will make your skills obsolete? #AI #ArtificialIntelligence #Coding #SoftwareEngineering #FutureOfWork #Technology

Pascal Bornet

18,027 views • 6 months ago

Marc Andreessen: AI coding doesn’t eliminate programmers — it redefines them. The job is no longer typing code line by line, it’s orchestrating 10 coding bots in parallel, arguing with them, debugging their output, changing the spec, and pushing them toward the right result. But here’s the catch: if you don’t understand how to write code yourself, you can’t evaluate what the AI gives you. The next layer of programming isn’t writing scripts — it’s supervising AI that writes them. Today’s best programmers spend their day jumping between terminals, managing multiple coding bots, fixing mistakes, and refining instructions. The irony? You still need deep fundamentals, because without them, you won’t know when the AI is wrong. The job of the programmer has changed. Now it’s about arguing with coding bots, debugging AI-generated code, and understanding why something doesn’t work or isn’t fast enough. AI abstracts the work — but only people who truly understand code can tell if the abstraction is doing the right thing. Programmers aren’t going away — they’re becoming 10x, 100x, even 1,000x more productive. Tasks are changing, the job is changing, but humans are still overseeing the process, evaluating results, fixing errors, and making judgment calls. AI changes how we code, not who is responsible. The future programmer isn’t replaced by AI — they’re upgraded by it. You still need to learn how to write and understand code, because when the AI gets it wrong, humans are the ones who have to know why. That up-leveling of capability is the real revolution.

Marc Andreessen: AI coding doesn’t eliminate programmers — it redefines them. The job is no longer typing code line by line, it’s orchestrating 10 coding bots in parallel, arguing with them, debugging their output, changing the spec, and pushing them toward the right result. But here’s the catch: if you don’t understand how to write code yourself, you can’t evaluate what the AI gives you. The next layer of programming isn’t writing scripts — it’s supervising AI that writes them. Today’s best programmers spend their day jumping between terminals, managing multiple coding bots, fixing mistakes, and refining instructions. The irony? You still need deep fundamentals, because without them, you won’t know when the AI is wrong. The job of the programmer has changed. Now it’s about arguing with coding bots, debugging AI-generated code, and understanding why something doesn’t work or isn’t fast enough. AI abstracts the work — but only people who truly understand code can tell if the abstraction is doing the right thing. Programmers aren’t going away — they’re becoming 10x, 100x, even 1,000x more productive. Tasks are changing, the job is changing, but humans are still overseeing the process, evaluating results, fixing errors, and making judgment calls. AI changes how we code, not who is responsible. The future programmer isn’t replaced by AI — they’re upgraded by it. You still need to learn how to write and understand code, because when the AI gets it wrong, humans are the ones who have to know why. That up-leveling of capability is the real revolution.

Ian Miles

913,270 views • 7 months ago

"The one thing that's going to be truly future proof is judgment. What is the biggest challenge when you have a thousand AI engineers writing code? AI slop. In an era when you can do everything, the question is which of these things matter. On the engineer side, it is evaluating the code. Which of this code is even valuable? You can have AI engineers writing beautiful code that could be wrong, that could have bugs in it, that could be vulnerable. Someone needs to review it. Make sure to have a human review at some point, especially critical code that is in the core of your system. On the product side is judgment around what needs to be built and evaluating. And similarly in design, you have to have judgment around, does it make sense in the broader design system. I think this judgment is the number one thing that humans are going to bring in an era of infinite productivity."

"The one thing that's going to be truly future proof is judgment. What is the biggest challenge when you have a thousand AI engineers writing code? AI slop. In an era when you can do everything, the question is which of these things matter. On the engineer side, it is evaluating the code. Which of this code is even valuable? You can have AI engineers writing beautiful code that could be wrong, that could have bugs in it, that could be vulnerable. Someone needs to review it. Make sure to have a human review at some point, especially critical code that is in the core of your system. On the product side is judgment around what needs to be built and evaluating. And similarly in design, you have to have judgment around, does it make sense in the broader design system. I think this judgment is the number one thing that humans are going to bring in an era of infinite productivity."

Patrick OShaughnessy

24,818 views • 7 months ago

Lex Fridman asked Elon Musk what the meaning of life is. His answer was not what anyone expected. We do not know, he said. And that is exactly why we need to expand consciousness. Not to find the answer. To ask better questions. He believes the universe is full of things we cannot even formulate yet. We are like children trying to understand calculus. The problem is not that calculus is too hard. The problem is that we have not developed enough to know it exists. Consciousness, to him, is a tool for exploring the universe. The more of it we have, the better our questions become. The better our questions become, the closer we get to understanding what any of this means. This is why he builds rockets and brain interfaces and AI. Not because he has the answers. Because he thinks the only way to get them is to expand what we are capable of thinking. Most people spend their lives looking for meaning. Elon is building the tools to look for it at a scale we cannot yet imagine.

Lex Fridman asked Elon Musk what the meaning of life is. His answer was not what anyone expected. We do not know, he said. And that is exactly why we need to expand consciousness. Not to find the answer. To ask better questions. He believes the universe is full of things we cannot even formulate yet. We are like children trying to understand calculus. The problem is not that calculus is too hard. The problem is that we have not developed enough to know it exists. Consciousness, to him, is a tool for exploring the universe. The more of it we have, the better our questions become. The better our questions become, the closer we get to understanding what any of this means. This is why he builds rockets and brain interfaces and AI. Not because he has the answers. Because he thinks the only way to get them is to expand what we are capable of thinking. Most people spend their lives looking for meaning. Elon is building the tools to look for it at a scale we cannot yet imagine.

Shruti

16,844 views • 2 months ago

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

194,035 views • 5 months ago

CEO of Nvidia said something that stopped me cold: "You may or may not lose a job to an AI, but you will absolutely lose a job to someone who uses AI" this 41 minutes is the most important talk on AI you'll watch this year so the question is not whether AI is coming for your job it's whether you're the one using it or the one being replaced by someone who does Nvidia already has hundreds of thousands of agents running inside the company right now agents are not the future, they are how the best teams work today I wrote a step by step guide on how to build your first AI agent with Claude Code you can find it in the article below

CEO of Nvidia said something that stopped me cold: "You may or may not lose a job to an AI, but you will absolutely lose a job to someone who uses AI" this 41 minutes is the most important talk on AI you'll watch this year so the question is not whether AI is coming for your job it's whether you're the one using it or the one being replaced by someone who does Nvidia already has hundreds of thousands of agents running inside the company right now agents are not the future, they are how the best teams work today I wrote a step by step guide on how to build your first AI agent with Claude Code you can find it in the article below

Anatoli Kopadze

14,741 views • 2 months ago

Sam Altman told the world exactly what skills will matter when AI takes over 30 to 40 percent of the global economy. He was asked what his own kids should do to survive it. His answer was surprisingly human. He said the single most valuable thing anyone can build right now is the meta-skill of learning how to learn. Not a degree or a certification but the raw ability to adapt when everything around you changes. He also said learning to understand what other people actually want and building useful things for them will be more valuable than almost any technical knowledge. That skill has never been automated and is not close to being automated. He said human creativity and the desire to express it are, in his words, limitless. Every major technological revolution increased the demand for creative, curious, and socially intelligent people, not decreased it. The Industrial Revolution is the clearest parallel. Machines replaced physical labor and people were terrified. The next generation took those machines and built industries, art forms, and institutions nobody had conceived of before. The people who thrived were not the ones who competed with the machines. They were the ones who learned to direct them toward something new. That dynamic is already playing out right now with AI. The practical implication is this, depth in a single rigid skill is becoming less valuable. The ability to move across domains, pick up new tools quickly, and apply judgment in ambiguous situations is becoming more valuable. Altman also pointed to something most career advice ignores entirely, learning how to interact with the world, build relationships, and earn trust from other people. Those are things AI can simulate but cannot replace. The honest opportunity in this moment is not to outrun AI. It is to focus on the things that make you irreducibly human. Curiosity, judgment, empathy and the ability to ask the right question before anyone knows what the right question is. The people who will matter most in an AI-driven economy are not necessarily the ones who understand the technology deepest. They are the ones who can figure out what the technology should actually be used for. Altman has spent his career betting on human potential in the face of technological disruption. Based on every historical precedent, that is still the right bet to make.

Sam Altman told the world exactly what skills will matter when AI takes over 30 to 40 percent of the global economy. He was asked what his own kids should do to survive it. His answer was surprisingly human. He said the single most valuable thing anyone can build right now is the meta-skill of learning how to learn. Not a degree or a certification but the raw ability to adapt when everything around you changes. He also said learning to understand what other people actually want and building useful things for them will be more valuable than almost any technical knowledge. That skill has never been automated and is not close to being automated. He said human creativity and the desire to express it are, in his words, limitless. Every major technological revolution increased the demand for creative, curious, and socially intelligent people, not decreased it. The Industrial Revolution is the clearest parallel. Machines replaced physical labor and people were terrified. The next generation took those machines and built industries, art forms, and institutions nobody had conceived of before. The people who thrived were not the ones who competed with the machines. They were the ones who learned to direct them toward something new. That dynamic is already playing out right now with AI. The practical implication is this, depth in a single rigid skill is becoming less valuable. The ability to move across domains, pick up new tools quickly, and apply judgment in ambiguous situations is becoming more valuable. Altman also pointed to something most career advice ignores entirely, learning how to interact with the world, build relationships, and earn trust from other people. Those are things AI can simulate but cannot replace. The honest opportunity in this moment is not to outrun AI. It is to focus on the things that make you irreducibly human. Curiosity, judgment, empathy and the ability to ask the right question before anyone knows what the right question is. The people who will matter most in an AI-driven economy are not necessarily the ones who understand the technology deepest. They are the ones who can figure out what the technology should actually be used for. Altman has spent his career betting on human potential in the face of technological disruption. Based on every historical precedent, that is still the right bet to make.

StockMarket.News

376,873 views • 5 months ago

Jensen Huang just said this is the greatest era in history to build software. AI agents will not kill software. They will do the exact opposite: create a massive new wave of software demand. at NVIDIA GTC Taipei 2026 "Click and type. We now replace that with explaining to the AI what we want, our intent, and the AI generates the code or uses tools to produce the necessary output. This is how computers are going to work in the future. This is Agentic AI. For two years, we've been building toward this, and now it has arrived. One of the big breakthroughs, of course, is tool use. A lot of people have said, “Jensen, AI is coming. Agentic AI is coming. Therefore, all the software companies are going to go out of business.” This is exactly the opposite. Because there are going to be so many agents, the world is no longer limited by the number of people. Therefore, those agents are going to use more tools than ever. This is actually an incredible time to be a software company. But the software has to be presented to the agent in a way that the agent can use it. This is a big breakthrough. And in fact, what we have done, as you know, what Nvidia’s treasure..." ---- From 'NVIDIA' YT channel (link in comment)

Jensen Huang just said this is the greatest era in history to build software. AI agents will not kill software. They will do the exact opposite: create a massive new wave of software demand. at NVIDIA GTC Taipei 2026 "Click and type. We now replace that with explaining to the AI what we want, our intent, and the AI generates the code or uses tools to produce the necessary output. This is how computers are going to work in the future. This is Agentic AI. For two years, we've been building toward this, and now it has arrived. One of the big breakthroughs, of course, is tool use. A lot of people have said, “Jensen, AI is coming. Agentic AI is coming. Therefore, all the software companies are going to go out of business.” This is exactly the opposite. Because there are going to be so many agents, the world is no longer limited by the number of people. Therefore, those agents are going to use more tools than ever. This is actually an incredible time to be a software company. But the software has to be presented to the agent in a way that the agent can use it. This is a big breakthrough. And in fact, what we have done, as you know, what Nvidia’s treasure..." ---- From 'NVIDIA' YT channel (link in comment)

Rohan Paul

16,584 views • 3 months ago

Sam Altman: "One person who knows how to use AI can do a week of work in 20 minutes." In 30 minutes he breaks down exactly what those people do differently, and how you can too. The gap isn't between AI and humans. It's between people who know AI and people who don't. Watch it, then read what knowing AI can actually do below

Sam Altman: "One person who knows how to use AI can do a week of work in 20 minutes." In 30 minutes he breaks down exactly what those people do differently, and how you can too. The gap isn't between AI and humans. It's between people who know AI and people who don't. Watch it, then read what knowing AI can actually do below

Mahax

17,829 views • 18 days ago

Max Tegmark says the way through the AI black box may be to deploy its outputs instead. A cat can learn, but it cannot export what it learned. A human scientist can. As intelligence rises, more knowledge may become externalized into code and proofs. Deploy what the mind can verify, not the mind itself.

Max Tegmark says the way through the AI black box may be to deploy its outputs instead. A cat can learn, but it cannot export what it learned. A human scientist can. As intelligence rises, more knowledge may become externalized into code and proofs. Deploy what the mind can verify, not the mind itself.

vitrupo

49,717 views • 4 months ago

MIT HANDED ITS DEEP LEARNING COURSE TO A FRONTIER-LAB ENGINEER FOR 68 MINUTES BECAUSE 90% OF PEOPLE SHIPPING AI CODE CAN'T EXPLAIN HOW THE MODEL ACTUALLY WORKS This is Maxime Labonne. He runs post-training at Liquid AI and wrote the LLM Engineer's Handbook. MIT gave him the room to break down the engine sitting inside every coding agent you've ever prompted. Twenty minutes in it stops being abstract. You finally see why the model confidently invents things that don't exist, why context is everything, and why "Just tell it to try again" sometimes fixes it and sometimes makes it worse. In 2026 "I use AI to code" stopped being a skill. Knowing why the model behaves the way it does -> tokens, context, post-training, where it quietly breaks -> is what separates someone who ships from someone babysitting a black box. Understanding an LLM isn't a research-team luxury anymore -> it's the difference between driving the agent and being driven by it. Anyone can prompt. The person who knows what's under the hood is the one still standing when the prompt stops working. Save this one & actually finish it ↓

MIT HANDED ITS DEEP LEARNING COURSE TO A FRONTIER-LAB ENGINEER FOR 68 MINUTES BECAUSE 90% OF PEOPLE SHIPPING AI CODE CAN'T EXPLAIN HOW THE MODEL ACTUALLY WORKS This is Maxime Labonne. He runs post-training at Liquid AI and wrote the LLM Engineer's Handbook. MIT gave him the room to break down the engine sitting inside every coding agent you've ever prompted. Twenty minutes in it stops being abstract. You finally see why the model confidently invents things that don't exist, why context is everything, and why "Just tell it to try again" sometimes fixes it and sometimes makes it worse. In 2026 "I use AI to code" stopped being a skill. Knowing why the model behaves the way it does -> tokens, context, post-training, where it quietly breaks -> is what separates someone who ships from someone babysitting a black box. Understanding an LLM isn't a research-team luxury anymore -> it's the difference between driving the agent and being driven by it. Anyone can prompt. The person who knows what's under the hood is the one still standing when the prompt stops working. Save this one & actually finish it ↓

slash1s

236,758 views • 3 months ago

Dario Amodei just announced the end of software engineering as a profession. The timeline is 6 to 12 months. Amodei: “I have engineers within Anthropic who say, I don’t write any code anymore. I just let the model write the code. I edit it.” Not a prediction. Current reality inside the frontier lab. The engineers who built the most advanced AI in the world have stopped writing code. They supervise. They edit. They manage architecture. The craft they spent careers mastering has been handed to the system they built. Amodei says models will do most, maybe all, of what software engineers do end-to-end within six to twelve months. Not assisting. Not autocompleting. Handling the entire development process independently. If you are learning syntax today, you are learning a dead language. Amodei: “Then it’s a question of how fast does that loop close?” The loop is this. AI writes code. Code builds better AI. Better AI writes better code. Faster. Without sleep. Without the cognitive limits that cap how quickly any human engineer can work. Once that loop closes, technological progress stops being constrained by human output. It becomes self-sustaining. Exponential. Operating at a pace no human workforce can match or direct. Software engineering isn’t ending. It’s becoming supervision. The developers who survive won’t be the best coders. They’ll be the best supervisors. The ones who can direct AI output, catch its failures, and architect what it builds toward. The skill that matters stops being implementation. It becomes judgment. Most developers are still optimizing for a skillset about to become as obsolete as stenography. While the people who built the systems replacing them already stopped doing the work themselves. The window to develop that judgment before the loop closes is exactly as long as Amodei’s timeline. Six to twelve months.

Dario Amodei just announced the end of software engineering as a profession. The timeline is 6 to 12 months. Amodei: “I have engineers within Anthropic who say, I don’t write any code anymore. I just let the model write the code. I edit it.” Not a prediction. Current reality inside the frontier lab. The engineers who built the most advanced AI in the world have stopped writing code. They supervise. They edit. They manage architecture. The craft they spent careers mastering has been handed to the system they built. Amodei says models will do most, maybe all, of what software engineers do end-to-end within six to twelve months. Not assisting. Not autocompleting. Handling the entire development process independently. If you are learning syntax today, you are learning a dead language. Amodei: “Then it’s a question of how fast does that loop close?” The loop is this. AI writes code. Code builds better AI. Better AI writes better code. Faster. Without sleep. Without the cognitive limits that cap how quickly any human engineer can work. Once that loop closes, technological progress stops being constrained by human output. It becomes self-sustaining. Exponential. Operating at a pace no human workforce can match or direct. Software engineering isn’t ending. It’s becoming supervision. The developers who survive won’t be the best coders. They’ll be the best supervisors. The ones who can direct AI output, catch its failures, and architect what it builds toward. The skill that matters stops being implementation. It becomes judgment. Most developers are still optimizing for a skillset about to become as obsolete as stenography. While the people who built the systems replacing them already stopped doing the work themselves. The window to develop that judgment before the loop closes is exactly as long as Amodei’s timeline. Six to twelve months.

Dustin

44,304 views • 6 months ago

Larry Ellison just told every software engineer on Earth their job description is dead. Not evolving. Dead. Ellison: “The code that Oracle is writing, Oracle isn’t writing. Our AI models are writing.” This is not a startup demo. This is one of the largest infrastructure monopolies on the planet telling you it already replaced the people who built it. For fifty years, building software meant translating human intent into machine instructions. Line by line. Bug by bug. Sprint by sprint. That entire layer is gone. Ellison: “We don’t write the procedure. We declare our intent.” That sentence just made the entire engineering labor market flinch. The procedure was the job. The procedure was the paycheck. The procedure was what made a developer valuable. And now the machine does it without being asked twice. Ellison: “We just tell the model what we want the program to do, and then the AI comes up with a step-by-step process to actually do it.” You are no longer paid to build. You are paid to think. And most organizations have no idea how to evaluate that. The companies still hiring armies of developers to grind through codebases are paying salaries the machine already made worthless. Not in years. In seconds. When a company worth hundreds of billions hands the keyboard to the machine and tells you the output is better, the debate is not winding down. The debate is over. The enterprise that wins this decade does not write the best code. It removes the human from the process entirely and runs on intent alone. The programmers who survive are the ones who realize the craft is no longer typing. It is architecture. It is judgment. It is knowing what to build and why. Everything else now belongs to the machine. And the machine does not negotiate severance.

Larry Ellison just told every software engineer on Earth their job description is dead. Not evolving. Dead. Ellison: “The code that Oracle is writing, Oracle isn’t writing. Our AI models are writing.” This is not a startup demo. This is one of the largest infrastructure monopolies on the planet telling you it already replaced the people who built it. For fifty years, building software meant translating human intent into machine instructions. Line by line. Bug by bug. Sprint by sprint. That entire layer is gone. Ellison: “We don’t write the procedure. We declare our intent.” That sentence just made the entire engineering labor market flinch. The procedure was the job. The procedure was the paycheck. The procedure was what made a developer valuable. And now the machine does it without being asked twice. Ellison: “We just tell the model what we want the program to do, and then the AI comes up with a step-by-step process to actually do it.” You are no longer paid to build. You are paid to think. And most organizations have no idea how to evaluate that. The companies still hiring armies of developers to grind through codebases are paying salaries the machine already made worthless. Not in years. In seconds. When a company worth hundreds of billions hands the keyboard to the machine and tells you the output is better, the debate is not winding down. The debate is over. The enterprise that wins this decade does not write the best code. It removes the human from the process entirely and runs on intent alone. The programmers who survive are the ones who realize the craft is no longer typing. It is architecture. It is judgment. It is knowing what to build and why. Everything else now belongs to the machine. And the machine does not negotiate severance.

Dustin

536,136 views • 5 months ago

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch

GREG ISENBERG

376,293 views • 5 months ago

do developers really hate marketing? In this episode of The West Coast Builders podcast, I sat down with Sam Bhagwat, founder & ceo Mastra things we discussed in this episode : - who is actually building with mastra today? - which agent framework should developers choose? - what would be the right roadmap to build a coding agent today? - has the AI memory layer been solved? - how does mastra stay relevant against competitors? - what is Sam's number one challenge as ceo? - what's mastra's gtm and distribution strategy? - Is enterprise the endgame for AI startups? - how should founders delegate without abdicating? - how do you spot a high agency when hiring? and much more...

do developers really hate marketing? In this episode of The West Coast Builders podcast, I sat down with Sam Bhagwat, founder & ceo Mastra things we discussed in this episode : - who is actually building with mastra today? - which agent framework should developers choose? - what would be the right roadmap to build a coding agent today? - has the AI memory layer been solved? - how does mastra stay relevant against competitors? - what is Sam's number one challenge as ceo? - what's mastra's gtm and distribution strategy? - Is enterprise the endgame for AI startups? - how should founders delegate without abdicating? - how do you spot a high agency when hiring? and much more...

Mayank Gupta🧑🏻‍💻

13,983 views • 15 days ago