998: How to Fix Vibe Coding

Syntax - Tasty Web Development Treats44mApril 22, 2026

Get the full intelligence

Search transcripts, export clips, track mentions, and explore all topics from “998: How to Fix Vibe Coding” inside PodZeus.

AI-Generated Summary

In this episode of Syntax, Scott Tolinski and Wes Bos dive deep into the growing problem of 'Vibe Coding'—where AI-generated code lacks consistency, maintainability, and quality due to its reliance on subjective, non-deterministic outputs. They argue that while AI has democratized development, it often produces sloppy, duplicated, and overly complex code that breaks easily and is hard to debug. To combat this, they introduce a suite of deterministic tools that bring structure and logic back into the development workflow. These include code quality analyzers like Fallo (which detects dead code, complexity hotspots, and duplication), CSS-specific tools like Project Wallace and Clint, and agent-enabling tools such as Storybook MCP and Sentry’s Spotlight for real-time debugging. The hosts emphasize the importance of enforcing rules through linters, custom ESLint plugins, and pre-commit hooks to make AI behavior predictable. They also explore headless browser solutions like Agent Browser and Light Panda for reliable testing and automation, and advocate for structured task management with tools like Dex. Ultimately, they stress that the future of AI-assisted development lies not in trusting vibes, but in building guardrails—tools that are fast, enforceable, and integrated into the workflow to ensure code quality, maintainability, and reliability.

Key Takeaways
1

Use deterministic tools like Fallo, Project Wallace, and Clint to automatically detect code quality issues such as duplication, complexity, and bad CSS practices.

2

Enforce code standards through custom ESLint plugins and pre-commit hooks instead of relying on vague instructions in agents.md files.

3

Integrate tools like Storybook MCP and Sentry Spotlight to give AI agents real-time, contextual feedback during development.

4

Replace vague AI prompts with structured workflows—run quality checks, linting, and formatting automatically after every feature.

5

Adopt headless browser tools like Agent Browser or Light Panda for faster, more reliable testing and automation in AI workflows.

…and 2 more takeaways available in PodZeus

Chapters
0:00
5 min

The Problem with Vibe Coding

I had clients and I made all these automations for them and I just lost all these clients because things were not working properly. They were breaking all the time. I had no way to tell that things were breaking, which is like... throw a century on there, brother.

Highlight
5:00
10 min

Code Quality Tools: Fighting the Slop

This is the exact types of things that, like you mentioned, that AI loves to do. It loves to just solve a problem as efficiently as it can, not as efficiently as your code base should have.

Highlight
15:00
15 min

CSS and Component Quality: Beyond Linting

One thing that I want to see more of is tools like the Svelte AutoFixer, which comes in their Svelte MCP, which will basically read your file and tell you what is not Svelte best practices.

Highlight
30:00
15 min

Bug Finding and Debugging with Sentry

It gives you essentially a local interface for debugging in development. And so this is a tool that is primarily used for while you're in dev, you're talking back and forth.

Highlight
45:00
18 min

Making AI Deterministic: Workflows and Enforcement

You can run them yourself and give the output to the AI agent and say, hey, fix these things. Or you can say in your agents, please do this.

Highlight
High-Impact Quotes
I had clients and I made all these automations for them and I just lost all these clients because things were not working properly. They were breaking all the time. I had no way to tell that things were breaking, which is like... throw a century on there, brother.
Wes Bos1:06
Viral: 90.0
The thing that nobody is talking about with these like AI agents and whatever is that you need a lot of IP addresses and you need a lot of compute to actually run these browsers.
Scott Tolinski30:25
Viral: 88.0
This is the exact types of things that, like you mentioned, that AI loves to do. It loves to just solve a problem as efficiently as it can, not as efficiently as your code base should have.
Scott Tolinski10:56
Viral: 85.0
Speakers

Hosts

Scott TolinskiWes Bos
Topics Discussed
code quality95%ai development workflows90%deterministic tooling88%code duplication85%debugging and error tracking82%css code quality80%headless browsers78%task management75%
People & Brands

Wes Bos

person

15xPositive

Scott Tolinski

person

12xPositive

Fallo

product

8xPositive

Storybook

product

6xPositive

ESLint

product

6xPositive

Agent Browser

product

5xPositive

Sentry

product

5xPositive

Svelte

other

5xPositive

Project Wallace

product

4xPositive

Light Panda

product

4xPositive

Get the full intelligence

Search transcripts, export clips, track mentions, and explore all topics from “998: How to Fix Vibe Coding” inside PodZeus.

Start discovering podcast insights today

Start with a 7-day trial and explore a growing catalog of popular podcasts. No credit card required.

No credit card required • 7-day trial • Cancel anytime