We have a vibe coding problem
Read the Portuguese translation →
Author: Riley Brown · Watch on YouTube
Video authored by the channel shown, not by IANIA; all rights belong to the creator. Transcript and summary generated automatically; the original-language content is preserved.
Original language: English
Original video: We have a vibe coding problem · Channel: Riley Brown · 01:33 · Watch on YouTube
Topics: Enterprise AI applications, Cybersecurity and software security, Software engineering with AI
Summary
Section titled “Summary”The video describes the risks of employees using AI to build and deploy apps, noting that a review of corporate-use assets found sensitive data exposed in 40% of them. It argues that vibe coding can still be useful in businesses when people have a secure environment for building. The speaker demonstrates an internal dashboard built with Superblocks and explains its role-based access, data permissions, audit logs, private-network deployment, and security scans. The video concludes that Superblocks offers a path from vibe-coded prototypes to production.
Key points
Section titled “Key points”- Employees are using AI to build apps, modify existing ones, and push changes directly to production.
- Researchers reviewed 380,000 assets built with AI tools and identified 5,000 intended for corporate use.
- Forty percent of the identified corporate-use assets exposed sensitive data.
- The speaker says vibe coding can be useful in businesses when people have the right environment.
- The demonstrated internal dashboard combines videos, sponsorships, revenue, and approvals.
- Different roles can receive access to only the information and actions they need.
- Permissions must apply to the underlying data, not just hide parts of the app interface.
- Superblocks provides company login, role-based access, audit logs, and deployment inside the company’s AWS account and private network.
- Superblocks scans apps before publication, and the speaker describes using a “fix all” action before publishing.
Chapters
Section titled “Chapters”| Start | Chapter | Summary |
|---|---|---|
| 00:00 | The risks of vibe coding | The speaker describes the growing use of AI-built apps in companies and the risk of sensitive data exposure. |
| 00:31 | A business app built with Superblocks | The speaker introduces Superblocks and demonstrates an internal dashboard that can also perform actions such as updating a sponsorship’s status. |
| 01:02 | Permissions, security, and production | The speaker explains role-based data access, audit logs, private-cloud deployment, and pre-publication scans as a path to production. |
Quotes
Section titled “Quotes”We have a vibe coding problem. — 00:00
40% of those exposed sensitive data. — 00:00
Hiding the revenue tab isn’t enough. — 01:02
Most vibe coded apps die as prototypes. — 01:33
Concepts and entities
Section titled “Concepts and entities”vibe coding, Superblocks, Agent Native, AWS, role-based access, audit logs
Full transcript (original language)
Section titled “Full transcript (original language)”00:00 We have a vibe coding [music] problem. In the US alone, hundreds of thousands of employees are now building apps from [music] scratch using AI, making changes to the apps that their developers build, and pushing directly to production. So, researchers reviewed 380,000 assets built with AI tools. They identified 5,000 [music] built for corporate use, and 40% of those exposed sensitive data. Yet, the best companies in the world are all reporting that their marketing teams, sales teams, and design teams are all shipping updates to their apps using AI
00:31 tools. And vibe coding is very useful inside all businesses if you create the right environment for people to build in. And that’s what Superblocks is built for, and why my company uses it. To build apps like this one. It’s an internal dashboard for Agent Native. Our videos, sponsorships, revenue, and approvals all in one place. And this isn’t just a dashboard that I read. I tell it to move a sponsorship to invoiced, and it just does it. But, different people on my team need different access. I need to see the whole business, [music] but an editor only needs to see their videos,
01:02 deadlines, and feedback. While my finance team needs their deals and payments. So, an editor can update a video without getting access to our financial records. And those permissions need to apply to the data itself. Hiding the revenue tab isn’t enough. And so, Superblocks gives us a company login, role-based [music] access, and audit logs to track who did what. And the app and the database both run inside our AWS account in our own [music] private network. Before anything publishes, Superblocks scans the app it just built
01:33 and makes sure everything is secure. I hit fix all, and then it publishes. Most vibe coded apps die as prototypes. Not because the app is bad, but because there’s no path to production. That’s what Superblocks gives us. It runs in our own cloud, permissions on the data, scanned before anything ships. If you’re bringing vibe coding to your company, check out Superblocks. The link is in my bio.