Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

LeetCode is dead. Developers don't write code line-by-line anymore. They orchestrate AI agents working in parallel, review AI-generated code, and make architectural decisions. That's the job now. But most interview processes haven't caught up. They still test algorithm memorization instead of AI fluency, code review, and judgment. We're building... show more

HackerRank

96,880 subscribers

343,660 Aufrufe • vor 3 Monaten •via X (Twitter)

Bildung Nachrichten & Politik Wissenschaft & Technologie

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Next-gen developers don’t just write code; they orchestrate AI across the entire software development lifecycle. This evolution is reshaping the way software gets built and what skills matter most in hiring and upskilling. Presenting our October '25 release:

Next-gen developers don’t just write code; they orchestrate AI across the entire software development lifecycle. This evolution is reshaping the way software gets built and what skills matter most in hiring and upskilling. Presenting our October '25 release:

HackerRank

24,847 Aufrufe • vor 9 Monaten

The best programmers don't write code anymore. They write a spec. A test. An eval. T Then they turn the AI on and walk away for hours. It runs. It ships. They review. Evals are the unlock most devs are sleeping on. Here's how top agent teams build them right.

The best programmers don't write code anymore. They write a spec. A test. An eval. T Then they turn the AI on and walk away for hours. It runs. It ships. They review. Evals are the unlock most devs are sleeping on. Here's how top agent teams build them right.

Rohit

690,904 Aufrufe • vor 3 Monaten

After reaching AI-native terminal velocity we are swamped in code review. The core insight is that as long as you can write code in parallel you will continue to be stuck until you can review it in parallel. I was surprised by how quickly this became my daily driver for not just review code, but writing it as well.

After reaching AI-native terminal velocity we are swamped in code review. The core insight is that as long as you can write code in parallel you will continue to be stuck until you can review it in parallel. I was surprised by how quickly this became my daily driver for not just review code, but writing it as well.

Evan Boyle

23,954 Aufrufe • vor 5 Monaten

Reviewing AI-generated code is the new bottleneck. Writing code was slow before. Now, in a few minutes, you can generate virtually unlimited lines of code using AI. But developers are now spending 70% of their time checking that code. That's the new bottleneck. I've been using Cline, and they have a feature that actually helps with this: You can click a button and have Cline generate an inline explanation for every single line of AI-generated code. Take a look at the attached video. What it does: 1. You can read the code and the explanation together 2. You don't lose context while reviewing code 3. You understand the "why" behind each change And here is the best part: It works on any git diff. You can use it to review PRs, understand commits from other people, or catch up on a codebase you haven't touched in a while.

Reviewing AI-generated code is the new bottleneck. Writing code was slow before. Now, in a few minutes, you can generate virtually unlimited lines of code using AI. But developers are now spending 70% of their time checking that code. That's the new bottleneck. I've been using Cline, and they have a feature that actually helps with this: You can click a button and have Cline generate an inline explanation for every single line of AI-generated code. Take a look at the attached video. What it does: 1. You can read the code and the explanation together 2. You don't lose context while reviewing code 3. You understand the "why" behind each change And here is the best part: It works on any git diff. You can use it to review PRs, understand commits from other people, or catch up on a codebase you haven't touched in a while.

Santiago

64,399 Aufrufe • vor 7 Monaten

At the AI in America Summit, Scott Dietzen, Executive Chair of Augment Code and former CEO of Pure Storage, described how AI is reshaping software development through “meta programming”—where engineers guide and refine AI-generated code rather than writing everything line by line. He argued this shift isn’t about cutting developers, but about unlocking far greater productivity and building more ambitious software than ever before. Explore more: #TheHillTech #AIinTech #FutureOfWork

At the AI in America Summit, Scott Dietzen, Executive Chair of Augment Code and former CEO of Pure Storage, described how AI is reshaping software development through “meta programming”—where engineers guide and refine AI-generated code rather than writing everything line by line. He argued this shift isn’t about cutting developers, but about unlocking far greater productivity and building more ambitious software than ever before. Explore more: #TheHillTech #AIinTech #FutureOfWork

The Hill Events

10,971 Aufrufe • vor 6 Monaten

Nobody is writing 90% of their code using AI. Here's the uncomfortable truth: The real productivity gain from using AI to write code is closer to 10%, nowhere near the 90% people claim. Sundar Pichai said in 2024 that 30% of the new code at Google was AI-generated. However, he went on to admit, during Lex Friedman's podcast, that engineering velocity had only increased by about 10%. AI-generated code isn't free code. It still has to be reviewed, tested, and made production-ready. Optimizing a single step (code generation) doesn't boost output if bottlenecks shift elsewhere (code reviews). It doesn't matter how much code you generate if you can't keep up the review process. The solution: Automate as much as you can the review and verification of your code. I'm working with Sonar, who is sponsoring this post, and they will take care of the code quality and security analysis of your code: • They review over 300B lines of code every single day • They cover reliability, security, and maintainability for your code • You can integrate them into your CI/CD pipeline • You can install them in your IDE (I use their VSCode extension) • Support for more than 30 languages Here is a link so you can check them out:

Nobody is writing 90% of their code using AI. Here's the uncomfortable truth: The real productivity gain from using AI to write code is closer to 10%, nowhere near the 90% people claim. Sundar Pichai said in 2024 that 30% of the new code at Google was AI-generated. However, he went on to admit, during Lex Friedman's podcast, that engineering velocity had only increased by about 10%. AI-generated code isn't free code. It still has to be reviewed, tested, and made production-ready. Optimizing a single step (code generation) doesn't boost output if bottlenecks shift elsewhere (code reviews). It doesn't matter how much code you generate if you can't keep up the review process. The solution: Automate as much as you can the review and verification of your code. I'm working with Sonar, who is sponsoring this post, and they will take care of the code quality and security analysis of your code: • They review over 300B lines of code every single day • They cover reliability, security, and maintainability for your code • You can integrate them into your CI/CD pipeline • You can install them in your IDE (I use their VSCode extension) • Support for more than 30 languages Here is a link so you can check them out:

Santiago

296,535 Aufrufe • vor 9 Monaten

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 Aufrufe • vor 6 Monaten

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 Cheong

912,454 Aufrufe • vor 5 Monaten

Chamath on how AI agents are making the "10x engineer" distinction disappear because the most efficient "code paths" are now obvious to everyone. Just as AI solved chess and removed the mystery of the best move, AI is doing the same for coding, making the process reductive and removing technical differentiation. "I'm going to say something controversial: I don't think developers anymore have good judgment. Developers get to the answer, or they don't get to the answer, and that's what agents have done. The 10x engineer used to have better judgment than the 1x engineer, but by making everybody a 10x engineer, you're taking judgment away. You're taking code paths that are now obvious and making them available to everybody. It's effectively like what happened in chess: an AI created a solver so everybody understood the most efficient path in every single spot to do the most EV-positive (expected value positive) thing. Coding is very similar in that way; you can reduce it and view it very reductively, so there is no differentiation in code." --- From The All-In Podcast YT channel (link in comment)

Chamath on how AI agents are making the "10x engineer" distinction disappear because the most efficient "code paths" are now obvious to everyone. Just as AI solved chess and removed the mystery of the best move, AI is doing the same for coding, making the process reductive and removing technical differentiation. "I'm going to say something controversial: I don't think developers anymore have good judgment. Developers get to the answer, or they don't get to the answer, and that's what agents have done. The 10x engineer used to have better judgment than the 1x engineer, but by making everybody a 10x engineer, you're taking judgment away. You're taking code paths that are now obvious and making them available to everybody. It's effectively like what happened in chess: an AI created a solver so everybody understood the most efficient path in every single spot to do the most EV-positive (expected value positive) thing. Coding is very similar in that way; you can reduce it and view it very reductively, so there is no differentiation in code." --- From The All-In Podcast YT channel (link in comment)

Rohan Paul

832,427 Aufrufe • vor 4 Monaten

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 Aufrufe • vor 2 Monaten

Anthropic engineer showed how one person can run 5 AI agents, that code, test, review, and deploy at the same time. In 30 minutes they built the whole thing live in one session. Here's what they cover: > when to use one agent vs a full team > how to split work so agents don't step on each other > the exact framework for deciding what each agent handles that's exactly why, I put together a guide on building agent teams that actually work. full guide in the article below 👇

Anthropic engineer showed how one person can run 5 AI agents, that code, test, review, and deploy at the same time. In 30 minutes they built the whole thing live in one session. Here's what they cover: > when to use one agent vs a full team > how to split work so agents don't step on each other > the exact framework for deciding what each agent handles that's exactly why, I put together a guide on building agent teams that actually work. full guide in the article below 👇

darkzodchi

840,181 Aufrufe • vor 1 Monat

Boris Cherny: "I don't write code anymore, I just prompt with Claude" he spent 57 minutes explaining exactly where this is all going here's what stood out: > Claude Code grew faster than anyone at Anthropic expected > AI agents are moving beyond coding into every industry > running 1,000 agents in parallel is already happening > SaaS may not survive the agent era if the Head of Claude Code prompts instead of codes, what does that tell you about the next 2 years? that's exactly why I put together an article on Claude features most people don't know exist it will change how you work with Claude completely you can find it below

Boris Cherny: "I don't write code anymore, I just prompt with Claude" he spent 57 minutes explaining exactly where this is all going here's what stood out: > Claude Code grew faster than anyone at Anthropic expected > AI agents are moving beyond coding into every industry > running 1,000 agents in parallel is already happening > SaaS may not survive the agent era if the Head of Claude Code prompts instead of codes, what does that tell you about the next 2 years? that's exactly why I put together an article on Claude features most people don't know exist it will change how you work with Claude completely you can find it below

Anatoli Kopadze

20,003 Aufrufe • vor 1 Monat

An MCP server that detects production-grade code quality issues in real-time! Even though AI is now generating code at light speed, the engineering bottleneck has just moved from writing to reviewing, and now devs spend 90% of their debugging time on AI-generated code. AI reviewers aren't that reliable either because they share the same fundamental blind spots as AI generators do: - They pattern match, not proof check. - They validate syntax, not system behavior. - They review code, not consequences. I have been using the SonarQube MCP Server (by Sonar) to solve this. It produces enterprise-grade code analysis and returns instant feedback on bugs, vulnerabilities, and code smells right where you're working (Claude Code, Cursor, etc.). Its capabilities have emerged from the 750B+ lines of code SonarQube processes daily, so it has seen every bug pattern that exists. This includes: - Security vulnerabilities (SQL injection, XSS, hardcoded secrets) - Code smells and technical debt - Test coverage gaps - Maintainability issues The setup is simple: - Install the SonarQube MCP server - Add it to your AI assistant's config Done! SonarQube is now part of your AI coding workflow. I have shared the GitHub repo in the replies! P.S. Thanks to Sonar for working with me today.

An MCP server that detects production-grade code quality issues in real-time! Even though AI is now generating code at light speed, the engineering bottleneck has just moved from writing to reviewing, and now devs spend 90% of their debugging time on AI-generated code. AI reviewers aren't that reliable either because they share the same fundamental blind spots as AI generators do: - They pattern match, not proof check. - They validate syntax, not system behavior. - They review code, not consequences. I have been using the SonarQube MCP Server (by Sonar) to solve this. It produces enterprise-grade code analysis and returns instant feedback on bugs, vulnerabilities, and code smells right where you're working (Claude Code, Cursor, etc.). Its capabilities have emerged from the 750B+ lines of code SonarQube processes daily, so it has seen every bug pattern that exists. This includes: - Security vulnerabilities (SQL injection, XSS, hardcoded secrets) - Code smells and technical debt - Test coverage gaps - Maintainability issues The setup is simple: - Install the SonarQube MCP server - Add it to your AI assistant's config Done! SonarQube is now part of your AI coding workflow. I have shared the GitHub repo in the replies! P.S. Thanks to Sonar for working with me today.

Avi Chawla

28,027 Aufrufe • vor 7 Monaten

“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."

“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 Aufrufe • vor 5 Monaten

claude code can now write sql almost perfectly. but it still needs to be retaught the same definitions over and over. ontology is how AI agents get 7x faster on your database over time. today we shipped Ontology 3.0 — memory for AI agents, specialized for databases:

claude code can now write sql almost perfectly. but it still needs to be retaught the same definitions over and over. ontology is how AI agents get 7x faster on your database over time. today we shipped Ontology 3.0 — memory for AI agents, specialized for databases:

ethan ding 📊

25,309 Aufrufe • vor 2 Monaten

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,270 Aufrufe • vor 5 Monaten

"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 Aufrufe • vor 5 Monaten

Databricks CEO and co-founder Ali Ghodsi joined Bloomberg Technology to discuss the launch of Genie Code, an autonomous AI agent built specifically for data teams. "Just six months ago, we were talking about autocompleting code — now agents automate the code. The new question is: how do we take the code that’s been written into production and make sure we're monitoring it?" Watch the full conversation

Databricks CEO and co-founder Ali Ghodsi joined Bloomberg Technology to discuss the launch of Genie Code, an autonomous AI agent built specifically for data teams. "Just six months ago, we were talking about autocompleting code — now agents automate the code. The new question is: how do we take the code that’s been written into production and make sure we're monitoring it?" Watch the full conversation

Databricks

19,463 Aufrufe • vor 4 Monaten