Loading video...

Video Failed to Load

Go Home

Sam Altman says soon everyone will be a software engineer and he might be right Sam Altman just casually dropped one of the biggest takes about the future of work and software and people are still sleeping on it. Here’s the core idea, and it’s honestly wild: Natural language...

VraserX's profile picture

VraserX e/acc

22,091 subscribers

70,659 views • 7 months ago •via X (Twitter)

EducationScience & Technology
LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

#WATCH | Mumbai, Maharashtra: On the Jevons paradox and software demand expansion, Neelkanth Mishra, Executive Director Designate of the World Bank, says, “…If you think about what the major cost of a software firm is, it is people. So, if the writing of software is getting automated, those firms will be the first to make adjustments. But on the whole, it seems that the Jevons paradox—which dictates that as the cost of writing software falls, the amount of software written goes up—is actually playing out. If an XYZ company, which is a product company, was spending, say, $100 million on writing software and can now do it for $70 million, they might need to lay off some people; that is their business priority. But if the amount of software written goes up three to four times, the number of software engineers in the ecosystem will not change… This panic and paranoia about massive job losses is something that I think is, at this stage, unfounded.”
2:48

#WATCH | Mumbai, Maharashtra: On the Jevons paradox and software demand expansion, Neelkanth Mishra, Executive Director Designate of the World Bank, says, “…If you think about what the major cost of a software firm is, it is people. So, if the writing of software is getting automated, those firms will be the first to make adjustments. But on the whole, it seems that the Jevons paradox—which dictates that as the cost of writing software falls, the amount of software written goes up—is actually playing out. If an XYZ company, which is a product company, was spending, say, $100 million on writing software and can now do it for $70 million, they might need to lay off some people; that is their business priority. But if the amount of software written goes up three to four times, the number of software engineers in the ecosystem will not change… This panic and paranoia about massive job losses is something that I think is, at this stage, unfounded.”

ANI

114,594 views • 1 month ago

Today Sam Asante and I are releasing Typeahead 2.0 on Product Hunt. Sam and I started this company because we think local AI software is going to become a much bigger part of how people use their computers. Typeahead is the first product from that thesis. The first version made the idea clear. AI autocomplete should work in the apps where writing already happens. Since then, we have been shipping toward the product that idea deserves. The app feels faster and more natural. Suggestions are easier to control. The experience is more native to the Mac. It's getting better at staying out of the way until the exact moment it can help. That matters because writing is personal. The best AI writing help keeps you in the sentence. You stay in flow and keep your voice. The machine helps without taking over. Typeahead works across your Mac, runs locally, works offline, and is built to feel like software you own. We’re live on Product Hunt today.
1:10

Today Sam Asante and I are releasing Typeahead 2.0 on Product Hunt. Sam and I started this company because we think local AI software is going to become a much bigger part of how people use their computers. Typeahead is the first product from that thesis. The first version made the idea clear. AI autocomplete should work in the apps where writing already happens. Since then, we have been shipping toward the product that idea deserves. The app feels faster and more natural. Suggestions are easier to control. The experience is more native to the Mac. It's getting better at staying out of the way until the exact moment it can help. That matters because writing is personal. The best AI writing help keeps you in the sentence. You stay in flow and keep your voice. The machine helps without taking over. Typeahead works across your Mac, runs locally, works offline, and is built to feel like software you own. We’re live on Product Hunt today.

Hiten Shah

27,150 views • 1 month ago

Today, Sierra is releasing Ghostwriter, our agent for building agents. With Ghostwriter, you can create an AI agent for your customer experience — one that can chat, pick up the phone, speak dozens of languages, take action on your systems of record, and be protected with industry-leading guardrails — simply by having a conversation. No clicking, no forms, no menus. Codex and Claude Code have transformed how we build software, making it possible for software engineers to orchestrate and review the work rather than doing all the work themselves. We think the same transformation will happen for all software. Rather than every enterprise app having a web app for humans and an API for automation, every software platform’s UI will be an agent that can do the work on your behalf. I recorded a demo of my building and optimizing an agent with Ghostwriter so you can see how powerful and easy it is to use. It’s completely changed the way our early adopters build agents, and it’s changed the way I think about the software industry. Let me know what you think, and, if you’re interested in trying it out at your business, please reach out directly.
10:43

Today, Sierra is releasing Ghostwriter, our agent for building agents. With Ghostwriter, you can create an AI agent for your customer experience — one that can chat, pick up the phone, speak dozens of languages, take action on your systems of record, and be protected with industry-leading guardrails — simply by having a conversation. No clicking, no forms, no menus. Codex and Claude Code have transformed how we build software, making it possible for software engineers to orchestrate and review the work rather than doing all the work themselves. We think the same transformation will happen for all software. Rather than every enterprise app having a web app for humans and an API for automation, every software platform’s UI will be an agent that can do the work on your behalf. I recorded a demo of my building and optimizing an agent with Ghostwriter so you can see how powerful and easy it is to use. It’s completely changed the way our early adopters build agents, and it’s changed the way I think about the software industry. Let me know what you think, and, if you’re interested in trying it out at your business, please reach out directly.

Bret Taylor

1,062,087 views • 4 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)
0:59

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 • 2 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.
0:26

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 • 5 months ago

The trades can build anything... except the software they run on. That changes today. We've raised $9.2M to build Dalton Mills. Software has spent its whole history getting closer to the people who do the work. First, the system of record. Software you stored your business in. Then, the agentic era. Software that did the work for you. Now, the bespoke era. Agentic software you build yourself, without code. Each era closed the gap and this one closes it for good. Software can finally work around your business, instead of you bending your business to make it fit. You ran on software made for everyone… never for you. That's over. Welcome to Dalton Mills. Let the builders build!
2:14

The trades can build anything... except the software they run on. That changes today. We've raised $9.2M to build Dalton Mills. Software has spent its whole history getting closer to the people who do the work. First, the system of record. Software you stored your business in. Then, the agentic era. Software that did the work for you. Now, the bespoke era. Agentic software you build yourself, without code. Each era closed the gap and this one closes it for good. Software can finally work around your business, instead of you bending your business to make it fit. You ran on software made for everyone… never for you. That's over. Welcome to Dalton Mills. Let the builders build!

Todd Saunders

92,793 views • 2 months ago

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."
2:04

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."

The Pragmatic Engineer

39,011 views • 2 months ago

How will AI change writing? For clues, look at the current state of software development. Marc Andreessen says: "The new coding interface is you've got your code and a chatbot. The Copilot is reading your code and giving you real-time comments. Or the chatbot is actually writing the code for you, and then you're giving it feedback. We had this old concept in the old days called pair programming, where you'd put two coders together in front of the same keyboard, and they could talk to each other and write code together. But now you're just going to have pair programming happening much more broadly, which is human plus machine. And by the way, this hasn't happened yet, but I think the same thing will happen for every other form of writing. So I think prose writing and fiction writing and all kinds of professional authors will be working in this format where you'll have this continuous dialogue going with an AI while you're in charge of the overall product." — Marc Andreessen 🇺🇸 (Recorded in 2024)
0:53

How will AI change writing? For clues, look at the current state of software development. Marc Andreessen says: "The new coding interface is you've got your code and a chatbot. The Copilot is reading your code and giving you real-time comments. Or the chatbot is actually writing the code for you, and then you're giving it feedback. We had this old concept in the old days called pair programming, where you'd put two coders together in front of the same keyboard, and they could talk to each other and write code together. But now you're just going to have pair programming happening much more broadly, which is human plus machine. And by the way, this hasn't happened yet, but I think the same thing will happen for every other form of writing. So I think prose writing and fiction writing and all kinds of professional authors will be working in this format where you'll have this continuous dialogue going with an AI while you're in charge of the overall product." — Marc Andreessen 🇺🇸 (Recorded in 2024)

David Perell Clips

13,101 views • 4 months ago

The question we get the most with 8090 Enterprise engagements. Who maintains it and what happens when the software needs to change? Most custom software is built once and patched forever. Every change request becomes a six-week negotiation with a vendor who can no longer explain their own code. 8090 Enterprise inverts that. We design, build, host, AND maintain. Software Factory powers our delivery and is built for the second year of changes, the third year, and the tenth. Reach out to us about what system you want to replace: sales@8090.inc
0:40

The question we get the most with 8090 Enterprise engagements. Who maintains it and what happens when the software needs to change? Most custom software is built once and patched forever. Every change request becomes a six-week negotiation with a vendor who can no longer explain their own code. 8090 Enterprise inverts that. We design, build, host, AND maintain. Software Factory powers our delivery and is built for the second year of changes, the third year, and the tenth. Reach out to us about what system you want to replace: [email protected]

8090

120,538 views • 2 months ago

Sam Altman (CEO of OpenAI) : the idea guys are the ones who win and get funded in the age of AI spoiler ; all you need an idea and think clearly , ai will build it this guy just handed out the hidden cheat code on how to think with AI without rotting your brain bookmark this for the week
17:25

Sam Altman (CEO of OpenAI) : the idea guys are the ones who win and get funded in the age of AI spoiler ; all you need an idea and think clearly , ai will build it this guy just handed out the hidden cheat code on how to think with AI without rotting your brain bookmark this for the week

Avid

47,644 views • 3 months ago

The hard part of building is no longer writing code. Code is easy. Nobody wins by writing more code or doing it faster. If you want to win, you need better thinking. There are a ton of startups focusing on using AI to write more code. I think they are missing the plot. We need a mental shift. We need tools that help us think faster, make better decisions, and focus on the right problems. I want you to check out Atoms because they are doing exactly this. They don't focus on the code, but on helping you build the right structure: 1. It starts by deep-researching marketing insights 2. It turns that into an execution plan 3. It builds both frontend and backend 4. It helps with deployment, SEO, growth, and analytics More importantly, it specializes in the core components you need to build and sell software online: • Authentication flows • Stripe payments • Infrastructure Their goal here is not to be another autocomplete tool or a copilot to help you write software. Their goal is to become a "vibe business team" that helps you build a business from the ground up. Here is a link for you to check them out: Thanks to the team for helping me onboard on the platform and collaborating with me on the post.
3:52

The hard part of building is no longer writing code. Code is easy. Nobody wins by writing more code or doing it faster. If you want to win, you need better thinking. There are a ton of startups focusing on using AI to write more code. I think they are missing the plot. We need a mental shift. We need tools that help us think faster, make better decisions, and focus on the right problems. I want you to check out Atoms because they are doing exactly this. They don't focus on the code, but on helping you build the right structure: 1. It starts by deep-researching marketing insights 2. It turns that into an execution plan 3. It builds both frontend and backend 4. It helps with deployment, SEO, growth, and analytics More importantly, it specializes in the core components you need to build and sell software online: • Authentication flows • Stripe payments • Infrastructure Their goal here is not to be another autocomplete tool or a copilot to help you write software. Their goal is to become a "vibe business team" that helps you build a business from the ground up. Here is a link for you to check them out: Thanks to the team for helping me onboard on the platform and collaborating with me on the post.

Santiago

79,010 views • 6 months ago

.Amjad Masad : Creating software is going to be one of the most exciting areas. The average person will soon be as capable as what a senior software engineer is today, as we shift from doing the work to directing it. Instead of coding line by line, you’ll run multiple agents in parallel, building the frontend, refactoring the database, shipping features, all in the background. On top of that, you’ll have a clean interface to design and interact with AI more creatively. Software creation is moving from execution to orchestration, and soon, it won’t be a specialised skill, it’ll be the baseline.
0:47

.Amjad Masad : Creating software is going to be one of the most exciting areas. The average person will soon be as capable as what a senior software engineer is today, as we shift from doing the work to directing it. Instead of coding line by line, you’ll run multiple agents in parallel, building the frontend, refactoring the database, shipping features, all in the background. On top of that, you’ll have a clean interface to design and interact with AI more creatively. Software creation is moving from execution to orchestration, and soon, it won’t be a specialised skill, it’ll be the baseline.

Extraordinary

19,241 views • 4 months ago

How Base44 Beats Cursor: "I don't think you will want to see the code. Nowadays even the most technical users would prefer building inside Base44 instead of Cursor. They do not want to set up servers and databases and see the code and write tests and navigate through the files etc. This portion of software that you can build in Base44 is going to grow. If you can build it inside Base44, you'd prefer to do that than Cursor." Do you agree, people "will not want to see the code" Anton Osika Scott Wu GREG ISENBERG Theo - t3.gg
0:40

How Base44 Beats Cursor: "I don't think you will want to see the code. Nowadays even the most technical users would prefer building inside Base44 instead of Cursor. They do not want to set up servers and databases and see the code and write tests and navigate through the files etc. This portion of software that you can build in Base44 is going to grow. If you can build it inside Base44, you'd prefer to do that than Cursor." Do you agree, people "will not want to see the code" Anton Osika Scott Wu GREG ISENBERG Theo - t3.gg

Harry Stebbings

70,015 views • 8 months ago

“Our biggest bottleneck is becoming the review of code, rather than the actual writing and generation of code.” Cisco CPO Jeetu Patel says code review is still super important though, because without human taste and judgment, code quickly turns into slop: “Every engineer on that team is now just a spec developer.” “They just build specs. They create markdown files. They give context to the model. They give context to the agent. And then the agent’s writing the code.” “I think, presumably, the review is going to get easier, too.” “You’ll have really crappy software that gets written if people aren’t paying attention to it. It doesn’t obviate the need for having taste, and having judgment, and having instinct, and making sure that you’re thinking about what you’re building."
1:35

“Our biggest bottleneck is becoming the review of code, rather than the actual writing and generation of code.” Cisco CPO Jeetu Patel says code review is still super important though, because without human taste and judgment, code quickly turns into slop: “Every engineer on that team is now just a spec developer.” “They just build specs. They create markdown files. They give context to the model. They give context to the agent. And then the agent’s writing the code.” “I think, presumably, the review is going to get easier, too.” “You’ll have really crappy software that gets written if people aren’t paying attention to it. It doesn’t obviate the need for having taste, and having judgment, and having instinct, and making sure that you’re thinking about what you’re building."

TBPN

11,289 views • 6 months ago

🚨 OpenAI just launched Codex, a brand-new autonomous coding agent that can build features and fix bugs on its own. We’ve been using it Every 📧 for a few days, and I’m impressed. I invited Alexander Embiricos (ben davies), a member of the product staff responsible for Codex, to demo Codex and talk about it live on a special edition of AI & I: What Codex is and how it works Codex is designed to be used by senior engineers—it performs coding tasks like adding features or fixing bugs autonomously. It's built to allow you to start many sessions at once, so you can have multiple agents working in parallel. Codex is built to have "taste" OpenAI trained Codex to have the taste of a senior software engineer. It knows how big codebases work, how to write a good PR, and uses clean, minimal code. Why an “abundance mindset” is best for interacting with agents Codex is designed to allow users to delegate many tasks at once without getting caught up in the details. This lets you point an abundance of agents at a specific task like a difficult bug—it’s worth it even if only one of them succeeds. How OpenAI is thinking about agents Codex is one piece of a unified super-assistant OpenAI wants to eventually build—an agent that helps users easily get things done by selecting the right tools for them behind the scenes. OpenAI’s vision for the future of programming In the future developers will probably spend less time writing routine code and more time guiding agents, reviewing their work, and making strategy decisions. Programming will become more social, letting teams easily delegate multiple tasks at once, allowing people to focus on ideas and collaboration instead of routine coding. Watch below!
44:33

🚨 OpenAI just launched Codex, a brand-new autonomous coding agent that can build features and fix bugs on its own. We’ve been using it Every 📧 for a few days, and I’m impressed. I invited Alexander Embiricos (ben davies), a member of the product staff responsible for Codex, to demo Codex and talk about it live on a special edition of AI & I: What Codex is and how it works Codex is designed to be used by senior engineers—it performs coding tasks like adding features or fixing bugs autonomously. It's built to allow you to start many sessions at once, so you can have multiple agents working in parallel. Codex is built to have "taste" OpenAI trained Codex to have the taste of a senior software engineer. It knows how big codebases work, how to write a good PR, and uses clean, minimal code. Why an “abundance mindset” is best for interacting with agents Codex is designed to allow users to delegate many tasks at once without getting caught up in the details. This lets you point an abundance of agents at a specific task like a difficult bug—it’s worth it even if only one of them succeeds. How OpenAI is thinking about agents Codex is one piece of a unified super-assistant OpenAI wants to eventually build—an agent that helps users easily get things done by selecting the right tools for them behind the scenes. OpenAI’s vision for the future of programming In the future developers will probably spend less time writing routine code and more time guiding agents, reviewing their work, and making strategy decisions. Programming will become more social, letting teams easily delegate multiple tasks at once, allowing people to focus on ideas and collaboration instead of routine coding. Watch below!

Dan Shipper 📧

145,487 views • 1 year ago

Some personal hot takes from AI: engineer Miami follows... 1. Software development is a dead-end profession because anyone can be a software developer now. 2. Anyone can use Cursor or any other tool and generate code. Being a coder and being a software engineer are different. 3. Computers used to be gated; now everyone has the power to make computers malleable. Everyone is a software developer now, but that does not mean they are software engineers 4. If you cannot demonstrate how a coding agent works, you are just a consumer and have imposed an artificial glass ceiling on your career as a software engineer. 5. If you are curious, you will have a job. If you have not been curious in the last two years, you are replaceable. 6. SaaS per-seat economics may become unstable as customers need fewer people to achieve results, prompting founders to think about new unit economics 7. Most companies will take two or three years (or more!) to figure out AI transformation. 8. Some companies are already building AI native teams of five to ten people who can build with the grain of AI 9. There will be an explosion in the number of software developers. Software development is now essentially free, and tokens are cheaper than humans 10. Not enough engineers know what it means to be a product engineer 11. JIRA ticket monkeys are cooked 12. If your company has banned AI, you should quit that company 13. AI is more like a musical instrument than just a tool play with it, make discoveries, build intuition learn where AI is good and where it fails
14:55

Some personal hot takes from AI: engineer Miami follows... 1. Software development is a dead-end profession because anyone can be a software developer now. 2. Anyone can use Cursor or any other tool and generate code. Being a coder and being a software engineer are different. 3. Computers used to be gated; now everyone has the power to make computers malleable. Everyone is a software developer now, but that does not mean they are software engineers 4. If you cannot demonstrate how a coding agent works, you are just a consumer and have imposed an artificial glass ceiling on your career as a software engineer. 5. If you are curious, you will have a job. If you have not been curious in the last two years, you are replaceable. 6. SaaS per-seat economics may become unstable as customers need fewer people to achieve results, prompting founders to think about new unit economics 7. Most companies will take two or three years (or more!) to figure out AI transformation. 8. Some companies are already building AI native teams of five to ten people who can build with the grain of AI 9. There will be an explosion in the number of software developers. Software development is now essentially free, and tokens are cheaper than humans 10. Not enough engineers know what it means to be a product engineer 11. JIRA ticket monkeys are cooked 12. If your company has banned AI, you should quit that company 13. AI is more like a musical instrument than just a tool play with it, make discoveries, build intuition learn where AI is good and where it fails

geoff

64,193 views • 1 month ago

Jensen Huang just explained why every company cutting engineers over AI is asking the entirely wrong question. Huang: “People say, I don’t need software engineers because apparently coding is going to be automated.” That was the narrative. Here is what Huang actually did. Huang: “I’ve given AIs to every one of my software engineers and hardware engineers and engineers period. 100% of NVIDIA has AI assistants, AI coders, and they’re busier than ever.” Not fewer engineers. Not smaller teams. Busier than ever. That is the line most companies are getting completely wrong right now. They hear “AI can write code” and immediately start cutting headcount. Huang did the opposite. He armed everyone. Huang: “And so the question is, what is the task versus what is the job? No different than a financial analyst; the task is mess around with spreadsheets, but the job is to make financial advice. The job is to help a customer.” Writing code was always the task. It was never the job. The job is architecture. Knowing what to build. Why it matters. How it fits into a system that actually creates value. Code is the execution layer between the idea and the outcome. Nothing more. When you automate that layer, you don’t eliminate the engineer. You eliminate the bottleneck between what they can envision and what they can ship. The companies using AI to cut headcount are optimizing for cost. The companies using AI to multiply output are optimizing for territory. Nvidia chose territory. Every engineer at the most valuable semiconductor company on Earth now operates with an AI assistant. Not a pilot program. Not an experiment. Company-wide. Every function. Every team. And the result is not less work. It is more work. Faster. At a scale that was physically impossible twelve months ago. The companies that understand the difference between eliminating engineers and unleashing them will build what comes next. The ones that don’t will watch their best talent walk out the door to the ones that did.
0:35

Jensen Huang just explained why every company cutting engineers over AI is asking the entirely wrong question. Huang: “People say, I don’t need software engineers because apparently coding is going to be automated.” That was the narrative. Here is what Huang actually did. Huang: “I’ve given AIs to every one of my software engineers and hardware engineers and engineers period. 100% of NVIDIA has AI assistants, AI coders, and they’re busier than ever.” Not fewer engineers. Not smaller teams. Busier than ever. That is the line most companies are getting completely wrong right now. They hear “AI can write code” and immediately start cutting headcount. Huang did the opposite. He armed everyone. Huang: “And so the question is, what is the task versus what is the job? No different than a financial analyst; the task is mess around with spreadsheets, but the job is to make financial advice. The job is to help a customer.” Writing code was always the task. It was never the job. The job is architecture. Knowing what to build. Why it matters. How it fits into a system that actually creates value. Code is the execution layer between the idea and the outcome. Nothing more. When you automate that layer, you don’t eliminate the engineer. You eliminate the bottleneck between what they can envision and what they can ship. The companies using AI to cut headcount are optimizing for cost. The companies using AI to multiply output are optimizing for territory. Nvidia chose territory. Every engineer at the most valuable semiconductor company on Earth now operates with an AI assistant. Not a pilot program. Not an experiment. Company-wide. Every function. Every team. And the result is not less work. It is more work. Faster. At a scale that was physically impossible twelve months ago. The companies that understand the difference between eliminating engineers and unleashing them will build what comes next. The ones that don’t will watch their best talent walk out the door to the ones that did.

Dustin

82,757 views • 4 months ago

"In the future, you won't need any software at all. The neural network will completely replace it." - stephen balaban, co-founder of Lambda "Here's the idea: instead of generating a program, just go to ChatGPT and say, 'Hi, please behave like a calculator or a spreadsheet.'" "'Generate an ASCII user interface for me. And I want you to essentially just respond, implement the logic of that program in your mind.'" "This is what I call neural software. Normal software is really brittle. 'Neural software' can't have bugs, only misunderstandings." "Large language models will be the software you interact with."
1:42

"In the future, you won't need any software at all. The neural network will completely replace it." - stephen balaban, co-founder of Lambda "Here's the idea: instead of generating a program, just go to ChatGPT and say, 'Hi, please behave like a calculator or a spreadsheet.'" "'Generate an ASCII user interface for me. And I want you to essentially just respond, implement the logic of that program in your mind.'" "This is what I call neural software. Normal software is really brittle. 'Neural software' can't have bugs, only misunderstandings." "Large language models will be the software you interact with."

TBPN

178,100 views • 1 year ago