Channel
Interviewed Person
v0
"I used to be more skeptical than I am now. Especially when everyone was talking about 'one-shotting' and 'vibe coding.' But then I forced myself to download Cursor and build an entire project without typing any code, making the computer type the code for me. I had to throw myself in the deep end." All three of us (@AdamWathan , @JustinJackson , and @briancasel) give our honest takes on AI and software development, and how it's going to affect our businesses (@TailwindLabs, @TransistorPodcasting, Instrumental.dev). "AI is like keyboard shortcuts on steroids for the things I am an expert in." 🎧 Listen to the whole episode on @ThePanelPodcast: https://panelpodcast.com/11 Adam and Brian share how AI lets them program more, not less, by eliminating grunt work. They think experienced developers will have a huge advantage in this AI era. We also dive into the business implications: how AI is already affecting traffic and sales for Tailwind UI, why building an audience is more important than ever, and what Adam is building next. This conversation actually got me curious to try Claude Code and Cursor AI. Chapters 00:00 - Adam's Initial AI Skepticism 01:15 - The Cursor Experiment: Building Without Typing Code 02:45 - Why You Need to Be Specific with AI 03:15 - The Evolution of AI Models (Claude Sonnet 4) 04:00 - Cursor Rules: Training AI to Match Your Style 04:45 - The 90% Grunt Work Problem 06:30 - AI as "Keyboard Shortcuts on Steroids" 07:15 - Why AI Fails for Learning New Technologies 08:15 - Using ChatGPT vs Cursor: Learning vs Coding 09:00 - The Future of AI in Every App 10:15 - How AI Should Work in Design Tools (Figma) 10:30 - How AI is affecting the Tailwind business (traffic is down) 14:00 - Keeping JavaScript Commercial This Time 14:45 - New Ventures: Video Editing Software 16:30 - Removing Grunt Work from Video Editing 17:45 - The Paradigm Shift and New Opportunities 19:00 - AI for Custom Personal Tools 20:30 - Building AI Automation Flows 22:00 - The Future: AI Pull Requests for Tailwind 🔗 Links: Bryan's new Rails components: https://instrumental.dev/ Bryan's SaaS: https://clarityflow.com/ Integrate Open AI and Anthropic APIs into your Rails applications (video): https://www.youtube.com/watch?v=5dW1Kkx7utQ Rob Walling's Stair Step approach: https://robwalling.com/essays/2015/03/26/the-stair-step-method-of-bootstrapping Vercel's new V0 AI tool: https://v0.dev/ Thorsten Ball's article: How to build an agent https://ampcode.com/how-to-build-an-agent ★ More about me: ★ I'm Justin Jackson. I founded https://transistor.fm (a podcast hosting and analytics platform) with Jon Buda. I write, podcast, and make videos about bootstrapping, startups, marketing, calm companies, and business ethics. My blog: https://justinjackson.ca Bluesky: https://bsky.app/profile/justinjackson.ca

Prismic
Interviewed: Guillermo Rauch

AI with Avthar
Interviewed: v0

This Dot Media
Interviewed: Malte Ubl
Justin Jackson: Adam, is there other ways you're using it? This is actually the first time I've talked I've heard you talk about using AI at all. I I couldn't I didn't know if you were, like, for it or against it. Adam Wathan: I used to be more skeptical than I am now. And I think the thing for me is I was seeing everyone talk about, like, one shotting things and, like, vibe coding things. And to me, that feels like bullshit and is just not not interesting. To me, it felt like, okay. I like programming.
Like, why would I wanna not program? But when especially when the agent mode stuff came out, I think I started to see how it's more useful. Because I forced myself to download Cursor and just try to basically build an entire project, which was like this this course platform template that we released not too long ago. Yeah. So it's like a Next.
Js website that's, like, pretty dynamic and does a bunch of different things. And I just forced myself to build the entire thing without typing any code and just making the computer type the code for me just to really, like, throw myself in the deep end and learn, like, okay. You know? Because in my head, I was like, okay. Well, if I have to tell them exactly what to do, isn't it just faster to do it myself? And it turns out, no. It's still not faster to do it yourself. Brian Casel: Like, just the fact that it can it can build multiple files.
Adam Wathan: Yeah. And you can what it feels like is it feels like having your feet up on the desk pair programming with someone next to you that you can just, like, talk to like a human being that understands what you want them to do and they do it. You know? Brian Casel: Yeah. And and also, like, there's a lot of the skeptics will say, like, oh, but it's just gonna spit back, like like, code slop that I can't use. Adam Wathan: Yeah. Then you're not being specific enough with what you're asking it to do. Justin Jackson: So did you have to babysit it at all? Like Adam Wathan: Yeah. Like, extremely, honestly, but not not
in a it's still faster, you know? Brian Casel: You're you're still approving every Adam Wathan: Yeah. Brian Casel: Page and every change. So you're so experienced developers can read the code that it Yeah. That it spits back and you can improve it. But the other thing is that, like, this stuff is improving so fast. I mean, I'm using today, I'm using mostly Claude Sonnet four. Even 3.7 was so much better than the models from, like, six months ago. Justin Jackson: Mhmm. Brian Casel: Like, it's it's not only better at, like, just
programming and, like, and just, like, knowing, like, the like, the Rails conventions and everything, and and it's also better at reading my project. Mhmm. And like, the when it when it creates when it generates new code, it first reads my code base and understands how I've implemented certain features in other areas and then implements based on that. Like, it it it is really good at, like, adapting. And then you can take it to the next level. Like, you can have, like, a day one with Cursor, like, just
fresh install Cursor, try it out. But once you're using it for six, twelve months, now you're getting into, like, Cursor rules. Yeah. Now you Adam Wathan: really started doing that on the very first day. Basically, anytime I found myself correcting something that it did, I added it to a rules file to make sure I never had to ask it to do that again. So just like little opinions in, like, our tailwind projects. If it used, like, a bottom margin, I always use top margins instead. So add it to the rules file. Don't use bottom margins unless you're doing this. Or when I ask you to, like like, a common thing that I need to do, like, a
workflow so I guess, like, here's the other thing that I I kind of became acutely aware of when I started using these workflows is just like how much of the program I do is not programming. It's just like grunt work. There's a it's like 90% grunt work. So Steve has an icon in Figma. I need to take that icon, bring it into my project. I need to optimize the SVG so it's not big. I need to convert it into a React component. I need to add props to it so that I can add classes to it when I'm using it. And the workflow for me has