The Vibe Coding Reality Check

[Mashiane]

Hi Fam!

Welcome to the ultimate deep dive into "Vibe Coding"!

Coined by AI researcher Andrej Karpathy in early 2025, vibe coding is the viral new development method where you describe what you want to build in plain English, and an AI agent writes the code for you. But is it actually the future of software, or just a fast track to broken apps?

In this video, we explore how platforms like Cursor, Bolt.new, Lovable, and Replit are completely transforming the tech industry. These tools are allowing both seasoned engineers and non-technical founders to go from a simple idea to a deployed web app in a matter of minutes

The Success Stories: We look at the massive real-world wins of vibe coding. Discover how the founder of SaaStr used Replit and Claude to vibe-code an app that scaled to 500,000 users in just 45 days

We also break down everyday victories, like how small business operators are saving thousands of dollars by building their own custom sales dashboards and marketing sites instead of paying for expensive SaaS subscriptions.

The Failures & Security Risks: But it’s not all sunshine and rapid deployment. We expose the dark side of vibe coding, including the "90-Day Reckoning"—the point where unchecked AI technical debt brings development to a grinding halt. You’ll hear about real, expensive disasters, such as a $15,000 rescue operation for a vibe-coded marketplace payment system that double-charged users due to missing webhook verifications

We also dive into the terrifying security statistics: studies show that 45% of AI-generated code contains critical OWASP Top 10 vulnerabilities. Because AI optimizes for making things "work" rather than making them "safe," vibe-coded apps routinely lack essential defenses like Row-Level Security (RLS) and CSRF protection, leading to massive data leaks .

The Takeaway: Whether you're a senior software engineer or a startup founder, this video will teach you the right way to use these powerful AI tools. Learn why "accepting without reading" is the most dangerous anti-pattern in modern coding, and how you can ship fast without compromising your users' security

 

[Dr_JU]

If we get serious and speak properly; in programming there are always these problems and dilemmas about what is appropriate and what is not, as well as about what is correct and what is not. Therefore it always ends up in personal accusations like: purist, old, hysterical, Luddite, etc.

And it always brings us back to the same question: What is programming? — as hard to answer as What is technology?

The battles are always latent; only the focus in the Overton window changes: OOP vs Functional vs Procedural, Visual programming vs Code, Native code vs Cross‑platform, Compiled vs Interpreted, Code vs LowCode vs NoCode, Visual Designer vs Code, the matryoshka of Frameworks vs IDEs vs Notepad++, Closed dependencies vs Own code, etc. Now we’re in the Vibe vs Assistant/Plugin stage.

And while we can: Choose a side > Join the fight > “Kill the bad guys because we are the good ones.”

We must not forget that the industry only cares about CI/CD (of money), while everyone else fights over the “technicality of being right.”

But nobody remembers that WebDevs and web development are completely ignorant of everything related to resources, platform, hardware architecture and the operating system.
They live in the abstract world of the browser, where resources “are infinite”; the heap/stack, x86, ARM, RISC‑V, Android, Windows, Linux, distros and versions, etc. What is that?
Their programming is based on liturgical patterns, frameworks and dependencies: “Everything is written and solved, you just have to type.”

And although web development is predominant (95%+ of existing code), not everything is web, so I’m not worried about that, because I belong to that 5% of code where AI and "the Vibe" don’t even know where to start.

What is absurdly repulsive is that nowadays you need 64 GiB of RAM, 8 cores, 2 RTX 6090 Ti and 1200W so a PC can open a notepad with the Apollo code.

And while we can call ourselves programmers, light our pipes, cross our legs, get comfortable and talk about purism and how good we are at what we do... we know there will always be an Erel who will say to us “Oh really?... Tell me more,” as: Where were you when I created the laws that govern your universe?

That’s why I find many of these “fights” absurd, since as a good engineer Buddy would say: To demolish a good building... you have to dynamite it!, the rest will fall from any mishap.