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.

For 20 years software had a stable playbook. Need reliability? Here are five ways to write tests. Now that writing code is nearly free, the engineers best at that playbook turn to it, and it's blank.

Kent Beck 🌻

185,290 subscribers

13,176 views • 20 days ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Joakim Recht (Uber Distinguished Eng) on tech leads: "Software engineers need to write code. If you're not writing code, you're not a software engineer." Joakim grew from a Senior Engineer to a Distinguished Engineer at Uber and I asked him what it took to get there. We covered: • The project that grew his career • What makes a great software engineer • Learnings from promo committees • When promos are unfair • Biggest technical mistake at Uber in hindsight • Advice for his younger self 𝗣𝗼𝗱𝗰𝗮𝘀𝘁 𝗹𝗶𝗻𝗸𝘀: • YouTube: • Transcript: • Spotify: • Apple:

Joakim Recht (Uber Distinguished Eng) on tech leads: "Software engineers need to write code. If you're not writing code, you're not a software engineer." Joakim grew from a Senior Engineer to a Distinguished Engineer at Uber and I asked him what it took to get there. We covered: • The project that grew his career • What makes a great software engineer • Learnings from promo committees • When promos are unfair • Biggest technical mistake at Uber in hindsight • Advice for his younger self 𝗣𝗼𝗱𝗰𝗮𝘀𝘁 𝗹𝗶𝗻𝗸𝘀: • YouTube: • Transcript: • Spotify: • Apple:

Ryan Peterman

72,223 views • 8 months ago

Dario Amodei just told software engineers exactly how long they have. Six to twelve 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, I do the things around it.” The people building the most powerful AI in history have already stopped writing code. That is not a forecast. That is the current working condition inside the lab closest to the frontier. Amodei: “We might be six to 12 months away from when the model is doing most, maybe all, of what SWEs do end-to-end.” The tech industry spent a decade making software engineers its highest-paid, most protected class. That era has a last day now. When a model can execute an entire software build end-to-end, the ability to write syntax stops being a skill. It becomes a credential for a job that no longer exists. Amodei: “And then it’s a question of how fast does that loop close.” That is the sentence everyone skipped. The code was never the hard part. The hard part was everything around it. The model just learned everything around it. Writing the code is already nearly gone. Testing is next. Deployment is next. When all three collapse into a single autonomous execution loop, the machine no longer needs a human in the chain at all. The corporation or sovereign state that closes that loop first does not gain a competitive advantage. It gains a category of speed that biological engineers cannot match, track, or reverse. That is not disruption. That is replacement at a systems level. Amodei is not describing a future disruption. He is describing the current state of his own building. The loop is already closing. The only question is whether you are inside it or outside it when it seals.

Dario Amodei just told software engineers exactly how long they have. Six to twelve 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, I do the things around it.” The people building the most powerful AI in history have already stopped writing code. That is not a forecast. That is the current working condition inside the lab closest to the frontier. Amodei: “We might be six to 12 months away from when the model is doing most, maybe all, of what SWEs do end-to-end.” The tech industry spent a decade making software engineers its highest-paid, most protected class. That era has a last day now. When a model can execute an entire software build end-to-end, the ability to write syntax stops being a skill. It becomes a credential for a job that no longer exists. Amodei: “And then it’s a question of how fast does that loop close.” That is the sentence everyone skipped. The code was never the hard part. The hard part was everything around it. The model just learned everything around it. Writing the code is already nearly gone. Testing is next. Deployment is next. When all three collapse into a single autonomous execution loop, the machine no longer needs a human in the chain at all. The corporation or sovereign state that closes that loop first does not gain a competitive advantage. It gains a category of speed that biological engineers cannot match, track, or reverse. That is not disruption. That is replacement at a systems level. Amodei is not describing a future disruption. He is describing the current state of his own building. The loop is already closing. The only question is whether you are inside it or outside it when it seals.

Dustin

318,457 views • 4 months ago

Anish Acharya: We're going to see a "YouTube moment for software": "If you think about YouTube 20 years ago—we had lots of video and lots of television, and it was high production quality, and it wasn't clear that we needed more and 20 years later, YouTube's a $550 billion enterprise that would be one of the biggest companies in the world if it was independent." "I think the same thing is going to happen for software. People want to make software, and for the first time they can—and they can distribute it and they can consume it." "Sometimes it's going to be important software. Sometimes it's going to be totally trivial. It's going to be software for a bachelor party weekend, software for a joke, software for a prompt. We have this sort of seriousness about software that we had about video and television 20 years ago." "Now it's like—I just took a video on my phone. It's going to be like—I just made an app on my phone. Same energy." Anish Acharya on BILLIONS with Guillaume Moubeche

Anish Acharya: We're going to see a "YouTube moment for software": "If you think about YouTube 20 years ago—we had lots of video and lots of television, and it was high production quality, and it wasn't clear that we needed more and 20 years later, YouTube's a $550 billion enterprise that would be one of the biggest companies in the world if it was independent." "I think the same thing is going to happen for software. People want to make software, and for the first time they can—and they can distribute it and they can consume it." "Sometimes it's going to be important software. Sometimes it's going to be totally trivial. It's going to be software for a bachelor party weekend, software for a joke, software for a prompt. We have this sort of seriousness about software that we had about video and television 20 years ago." "Now it's like—I just took a video on my phone. It's going to be like—I just made an app on my phone. Same energy." Anish Acharya on BILLIONS with Guillaume Moubeche

a16z

102,781 views • 4 months ago

The best tools aren’t built at a distance. They’re built next to the people using them. Watch how Ethan and nearly 1,000 engineers in the UK are building software that delivers for the people who need it most: patients, clinicians, and the NHS. We’re hiring in London. Join us.

The best tools aren’t built at a distance. They’re built next to the people using them. Watch how Ethan and nearly 1,000 engineers in the UK are building software that delivers for the people who need it most: patients, clinicians, and the NHS. We’re hiring in London. Join us.

Palantir

97,506 views • 9 days ago

Even noted crypto critic Molly White is now slamming the government's handling of the Roman Storm 🇺🇸 🌪️ Tornado Cash trial: "I agree with Storm on the fact that writing code is not a crime. It's not illegal to write privacy-preserving software."

Even noted crypto critic Molly White is now slamming the government's handling of the Roman Storm 🇺🇸 🌪️ Tornado Cash trial: "I agree with Storm on the fact that writing code is not a crime. It's not illegal to write privacy-preserving software."

Coinage

17,860 views • 1 year 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.

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

78,872 views • 6 months ago

#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.”

#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 • 28 days ago

Your brain is programmable, start treating it like software. Here are 28 ways for you to do that 🧵👇:

Your brain is programmable, start treating it like software. Here are 28 ways for you to do that 🧵👇:

Neuron Powers 🧠

395,021 views • 1 year ago

The worst thing about dealing with C (and C++ to an extent) code is understanding and debugging macros that you didn't write. Here are a couple ways of how to deal with them!

The worst thing about dealing with C (and C++ to an extent) code is understanding and debugging macros that you didn't write. Here are a couple ways of how to deal with them!

Valentin Ignatev

64,414 views • 6 months ago

Emilie Nicolas on David Parker and Alberta separatist groups: "I think there's a tactical playbook here that is also being borrowed or imitated and copied. And we need to look at the ways in which democracy south of the border is being eroded to be able to at least anticipate what moves could be done next."

Emilie Nicolas on David Parker and Alberta separatist groups: "I think there's a tactical playbook here that is also being borrowed or imitated and copied. And we need to look at the ways in which democracy south of the border is being eroded to be able to at least anticipate what moves could be done next."

Scott Robertson

12,262 views • 2 months 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.

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

Dana White Just Blew the Lid Off Democrats' Obama Playbook Strategy “She [Kamala] talks a lot about the need for change and her hope for the future. Hope and change—does that sound familiar?” “She can use the old Obama playbook, but she's not Obama, and she is no agent of change. She is the sitting Vice President of the United States right now. What she hopes is that voters will focus on the future because she doesn't want us looking at the last four years to see what we really need to change.

Dana White Just Blew the Lid Off Democrats' Obama Playbook Strategy “She [Kamala] talks a lot about the need for change and her hope for the future. Hope and change—does that sound familiar?” “She can use the old Obama playbook, but she's not Obama, and she is no agent of change. She is the sitting Vice President of the United States right now. What she hopes is that voters will focus on the future because she doesn't want us looking at the last four years to see what we really need to change.

The Vigilant Fox 🦊

4,232,792 views • 1 year ago

Elissa Slotkin worked for the CIA. She's now supposedly a Senator, and trying to stoke a color revolution. What's a color revolution? It's a CIA playbook to overthrow governments. Here are recent examples:

Elissa Slotkin worked for the CIA. She's now supposedly a Senator, and trying to stoke a color revolution. What's a color revolution? It's a CIA playbook to overthrow governments. Here are recent examples:

Brian Kennedy

67,067 views • 8 months ago

YC's Diana Hu: 'Good Enough' vs. Top 1% Software of Engineers "There's going to be a generation of software engineers that are good enough because it's so easy to retool there with code gen tools. The barrier to enter is so low. But to be exceptional, like the top 1%, you're going to need to get into deliberate practice." Diana on Y Combinator's Lightcone Podcast

YC's Diana Hu: 'Good Enough' vs. Top 1% Software of Engineers "There's going to be a generation of software engineers that are good enough because it's so easy to retool there with code gen tools. The barrier to enter is so low. But to be exceptional, like the top 1%, you're going to need to get into deliberate practice." Diana on Y Combinator's Lightcone Podcast

Overlap: Business & Tech

82,685 views • 1 year ago

🚨 NEW: Dan Bongino says you need to understand the playbook that the left and their media allies are using on you RIGHT NOW. Do not fall for it ❌ The Dan Bongino Show returns on February 2nd at 10AM ET: 🔥

🚨 NEW: Dan Bongino says you need to understand the playbook that the left and their media allies are using on you RIGHT NOW. Do not fall for it ❌ The Dan Bongino Show returns on February 2nd at 10AM ET: 🔥

Bongino Report

71,112 views • 6 months ago

We've built a massive verification bottleneck: • 72% of developers use AI to generate code every day • 96% of them don't fully trust it Writing code is now free. All the work now is verifying that the code does what it's supposed to. According to a new State of Code Survey, almost half of the respondents believe the number one skill that will matter most in the coming years is "reviewing and validating AI-generated code for quality and security". Not prompt engineering or vibe-coding, but checking AI's work.

We've built a massive verification bottleneck: • 72% of developers use AI to generate code every day • 96% of them don't fully trust it Writing code is now free. All the work now is verifying that the code does what it's supposed to. According to a new State of Code Survey, almost half of the respondents believe the number one skill that will matter most in the coming years is "reviewing and validating AI-generated code for quality and security". Not prompt engineering or vibe-coding, but checking AI's work.

Santiago

16,299 views • 6 months ago

Software engineers are going to love this. Input code in any language and GPT-4 will translate it to any other coding language. & It's free with your OpenAI key👇

Software engineers are going to love this. Input code in any language and GPT-4 will translate it to any other coding language. & It's free with your OpenAI key👇

Rowan Cheung

1,141,650 views • 3 years 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."

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

I started a company! Introducing Melty, an open source AI code editor for 10x engineers. It's the first editor that understands what you’re doing from the terminal to GitHub and collaborates with you to write production-ready code.

I started a company! Introducing Melty, an open source AI code editor for 10x engineers. It's the first editor that understands what you’re doing from the terminal to GitHub and collaborates with you to write production-ready code.

Charlie Holtz

582,687 views • 1 year ago