Loading video...

Video Failed to Load

Go Home

🚨 Tired of spending credits debugging errors generated by Cursor? Here’s the real problem: It can’t solve the error… because it doesn’t know what the bug is. Read this before you waste hours fixing the wrong bug. A thread for builders ⬇️

MVP_Builder's profile picture

Harsh ⚡

2,751 subscribers

38,302 views • 1 year ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Spending isn't a “conspiracy” just because Musk doesn’t know how to read A program isn't waste just because it doesn’t help the richest man in the world. It isn't fraud because he doesn’t like it. A law is not illegal just because he disagrees with it.
1:30

Spending isn't a “conspiracy” just because Musk doesn’t know how to read A program isn't waste just because it doesn’t help the richest man in the world. It isn't fraud because he doesn’t like it. A law is not illegal just because he disagrees with it.

Senator Patty Murray

1,363,655 views • 1 year ago

Oh look, it’s Trump pretending to save the day, by fixing a problem that he created with a bailout. But it doesn’t solve the real problem. Farmers wouldn’t have been in this position if it weren’t for Trump’s insane tariff policy. #TrumpInflationCrisis
0:56

Oh look, it’s Trump pretending to save the day, by fixing a problem that he created with a bailout. But it doesn’t solve the real problem. Farmers wouldn’t have been in this position if it weren’t for Trump’s insane tariff policy. #TrumpInflationCrisis

Christopher Webb

29,399 views • 11 months ago

Errors!! That's the most stressful part about AI coding We lose 40% credits in debugging code We tried to solve it with CodeGuide Debug Agent Just screenshot your error message and upload/paste it The Agent will write a detailed debug prompt Copy & paste it. Error solved.
0:43

Errors!! That's the most stressful part about AI coding We lose 40% credits in debugging code We tried to solve it with CodeGuide Debug Agent Just screenshot your error message and upload/paste it The Agent will write a detailed debug prompt Copy & paste it. Error solved.

CJ Zafir

12,554 views • 1 year ago

Fixing any problem starts by identifying the problem. Now that we all know what the problem is, when do we start fixing it? #Goodluck to you all #LonglivetheRepublic
1:18

Fixing any problem starts by identifying the problem. Now that we all know what the problem is, when do we start fixing it? #Goodluck to you all #LonglivetheRepublic

The Artist known as Jess

46,448 views • 1 year ago

Jake Shane says his dream role is Mary in “Oh, Mary!”: “If you’re asking what the dream is, that’s the dream… I do have the theater bug now. It’s a real bug and I have it.” Read more:
1:31

Jake Shane says his dream role is Mary in “Oh, Mary!”: “If you’re asking what the dream is, that’s the dream… I do have the theater bug now. It’s a real bug and I have it.” Read more:

Variety

1,348,438 views • 7 months ago

🚨💥 XRP $22.54 💥🚨 Coinbase once displayed XRP at $22.54 because of an error. It wasn’t the real market price. But here’s the question… If $22.54 has already appeared on the screen by mistake, why can’t we see it FOR REAL one day? 👀
0:30

🚨💥 XRP $22.54 💥🚨 Coinbase once displayed XRP at $22.54 because of an error. It wasn’t the real market price. But here’s the question… If $22.54 has already appeared on the screen by mistake, why can’t we see it FOR REAL one day? 👀

John Squire

60,604 views • 2 months ago

Most people that get “muscle knots” in the upper back or neck try to fix it them with stretching or rolling the area out. But it often doesn’t fix the problem for more than a few minutes because it’s not fixing the true underlying cause. Here’s what you need to know 👇
2:27

Most people that get “muscle knots” in the upper back or neck try to fix it them with stretching or rolling the area out. But it often doesn’t fix the problem for more than a few minutes because it’s not fixing the true underlying cause. Here’s what you need to know 👇

Conor Harris

678,131 views • 8 months ago

🚨NEW PICKAXE BUG🚨 There appears to be a bug where the hitbox of cones changes if there is a floor underneath it?
0:56

🚨NEW PICKAXE BUG🚨 There appears to be a bug where the hitbox of cones changes if there is a floor underneath it?

DIG Aussie Antics

178,619 views • 1 year ago

🚨 Securing ZK, Bug by Bug Part 1: Discover the "Code Bug" in our series "A Tale of Two ZK Bugs." Learn how a simple coding error can jeopardize blockchain security. An error in the Load8 instruction can cause improper memory access, compromising ZK transactions. Watch now! 🔐
0:43

🚨 Securing ZK, Bug by Bug Part 1: Discover the "Code Bug" in our series "A Tale of Two ZK Bugs." Learn how a simple coding error can jeopardize blockchain security. An error in the Load8 instruction can cause improper memory access, compromising ZK transactions. Watch now! 🔐

CertiK

647,778 views • 2 years ago

MIT GAVE DEBUGGING ITS OWN FULL LECTURE -- BECAUSE MOST DEVS STILL HUNT BUGS WITH PRINT STATEMENTS LIKE IT'S 1995 54 minutes that take the thing you do every single day, badly, and show you the tools schools never bothered to teach. -> The moment it lands, you realize "add a print, run it, add another print" was never debugging. It was guessing with extra steps. Most people never learned the real toolkit. A proper debugger, breakpoints, tracing what the program actually does instead of what you assume it does. In 2026 guessing isn't good enough -> the bug is buried in code you didn't even write, and printf won't find it for you. An AI agent will generate hundreds of lines in seconds. When one of them quietly breaks, finding it runs on exactly the skills in this lecture. Anyone can add a print statement. The person who can actually trace a bug to its source is the one who ships while everyone else guesses. Bookmark & Watch it ↓
54:10

MIT GAVE DEBUGGING ITS OWN FULL LECTURE -- BECAUSE MOST DEVS STILL HUNT BUGS WITH PRINT STATEMENTS LIKE IT'S 1995 54 minutes that take the thing you do every single day, badly, and show you the tools schools never bothered to teach. -> The moment it lands, you realize "add a print, run it, add another print" was never debugging. It was guessing with extra steps. Most people never learned the real toolkit. A proper debugger, breakpoints, tracing what the program actually does instead of what you assume it does. In 2026 guessing isn't good enough -> the bug is buried in code you didn't even write, and printf won't find it for you. An AI agent will generate hundreds of lines in seconds. When one of them quietly breaks, finding it runs on exactly the skills in this lecture. Anyone can add a print statement. The person who can actually trace a bug to its source is the one who ships while everyone else guesses. Bookmark & Watch it ↓

slash1s

10,864 views • 5 months ago

This guy went to his local fair, after getting thirsty he decided to check out a stall and get some bug juice. Only problem is the bug juice is made with real bugs. It has scorpions and ants and other bugs in it too. The vendor was encouraging him to eat the bugs too, the fact that it is neon green makes it even worst for me, would you try this?
0:26

This guy went to his local fair, after getting thirsty he decided to check out a stall and get some bug juice. Only problem is the bug juice is made with real bugs. It has scorpions and ants and other bugs in it too. The vendor was encouraging him to eat the bugs too, the fact that it is neon green makes it even worst for me, would you try this?

SonnyBoy🇺🇸

127,858 views • 7 months ago

🇺🇸 Stop debugging like it’s 2023... This guy already did. A SpaceXAI engineer claims GrokBot started fixing every bug he threw at it, so he quit doing it by hand. Now he runs 20 to 30 agents at once. He’s showing the setup live, watch before it gets buried. Grok / Writer: Val
27:24

🇺🇸 Stop debugging like it’s 2023... This guy already did. A SpaceXAI engineer claims GrokBot started fixing every bug he threw at it, so he quit doing it by hand. Now he runs 20 to 30 agents at once. He’s showing the setup live, watch before it gets buried. Grok / Writer: Val

Mario Nawfal

64,651 views • 1 month ago

Coach Prime still doesn’t get it. It’s not a QB problem, they have the WRONG IDENTITY. This is by far the biggest problem:
1:23

Coach Prime still doesn’t get it. It’s not a QB problem, they have the WRONG IDENTITY. This is by far the biggest problem:

Overthink Buffs

16,094 views • 1 month ago

"The bug was there before the AI found it."
0:43

"The bug was there before the AI found it."

a16z crypto

18,201 views • 5 months ago

The end of ownership. It’s not a bug, it is the feature.
0:40

The end of ownership. It’s not a bug, it is the feature.

Brian Roemmele

64,890 views • 1 year ago

“The libs create a problem so they can PRETEND to solve it!” GregGutfeld calls out the “homeless industrial complex” for maintaining the crisis instead of FIXING it.
1:21

“The libs create a problem so they can PRETEND to solve it!” GregGutfeld calls out the “homeless industrial complex” for maintaining the crisis instead of FIXING it.

The Five

29,151 views • 3 months ago

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

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

914,037 views • 9 months ago