meta_pixel
Tapesearch Logo
Log in
Syntax - Tasty Web Development Treats

998: How to Fix Vibe Coding

Syntax - Tasty Web Development Treats

Wes Bos

Tech News, Technology, News

4.91.2K Ratings

🗓️ 22 April 2026

⏱️ 45 minutes

🧾️ Download transcript

Summary

Wes and Scott talk about making AI coding more reliable using deterministic tools like fallow, knip, ESLint, StyleLint, and Sentry. They cover code quality analysis, linting strategies, headless browsers, task workflows, and how to enforce better patterns so AI stops guessing and starts producing maintainable, predictable code. Show Notes 00:00 Welcome to Syntax! Losing two clients in one week 04:49 Code quality tools jscpd.dev knip.dev fallow.tools wallace 14:11 Finding and using components Storybook AI 17:28 Brought to you by Sentry.io 17:42 Finding bugs Sentry CLI Spotlight 19:55 Formatting and linting Vite+ ESLint StyleLint clint 25:41 Headless browsers agent-browser chrome-devtools-mcp Lightpanda 32:11 Tasks and todos dex beads 33:32 Docs Context7 34:22 TanStack Code Mode 36:01 Getting AI to use these tools 38:18 Sick Picks + Shameless Plugs Sick Picks Scott: Leaf Two Razor Wes: Puzzles Shameless Plugs Phases.fm Podcast Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Transcript

Click on a timestamp to play from that location

0:00.0

Welcome to syntax. Today, we're going to be talking about how to turn vibe coding's vibes into more deterministic solutions with facts and logic. We're going to be really getting into the depths of what are the different tools that you can add to your setup. So that way, AI is not just guessing or making assumptions or anything like that.

0:23.5

So we're going to be talking about different code quality tools, bug finding tools, formatters,

0:29.1

linters, et cetera, but also the techniques in which you can use these things.

0:33.2

That way, you're not just like, hey, make it good, please.

0:36.4

All right, is this good? I have no idea. I have no way of figuring that. My name is Scott Tolensky. I'm a developer from Denver with me, as always is Wes Boss. What's up, Wes? Man, I, this is great because so much of this is, like, people have built stuff. And now that we're, what, three or four months into people building's like serious stuff with it. You're starting to see a lot of

0:55.4

the sort of edges crack around it. People are, oh, this is not actually very good. And I have a problem on my

1:00.6

hands, right? There was this post in the Reddit OpenClaw the other day where this guy was just saying,

1:05.7

like, I had clients and I made all these automations for them. And I just lost all these clients

1:10.3

because things were not working properly.

1:12.6

They were breaking all the time.

1:14.3

I had no way to tell that things were breaking,

1:18.5

which is like, throw century on their brother.

1:21.0

You'll be able to tell when things are breaking.

1:22.9

Just it's an absolute mess.

1:25.2

And if we can have the like pure functional programming

1:29.6

renaissance that we had in JavaScript, what, eight years ago, if we can have that in this

1:35.1

AI slop world, I think that the outputs will become a lot better. Yeah, it's so funny,

1:40.1

because I did my video on the G-Stack stuff and that the video was like 34,000 lines of slop.

1:47.9

I think that's what it was called.

1:49.5

And you get comments, especially on Twitter, where there's some non-developers on there

1:54.8

who are going to be like, you all dinosaurs are going to learn that it doesn't matter what the code quality is.

2:00.6

Or if we shipped 26 test files to the user, it doesn't matter what the code quality is or if we shipped 26 test files

...

Please login to see the full transcript.

Disclaimer: The podcast and artwork embedded on this page are from Wes Bos, and are the property of its owner and not affiliated with or endorsed by Tapesearch.

Generated transcripts are the property of Wes Bos and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.

Copyright © Tapesearch 2026.