Fully Integrated AI that Actually Ships

[Music] I will not be talking about cache components today. So this is AI. All right. Please build me a million dollar B2B SAS using Nex.js and Neon DB. No mistakes. Please send it. And that's the talk. Thank you. No, no, no, no, no, no. So, we've all seen these these vibe coders though where they are just shipping unsafe

production code and it's just it's just breaking data and they're spending thousands and thousands of dollars on like exposed API keys. But at the same time, it begs the question, can you like reliably use AI in your daily workflow? Yes. Yes, you can. My name is Ryan Vogel. As he said, I am a devril for data bricks and I've shipped a ton of personal and professional projects with many over having users over thousands and thousands of users and I've used

billions of tokens on cursor which is probably the only accolade I need. Anyways, we're going to be focusing on a side project of mine called inbound. Inbound is my email infrastructure project and I've personally shipped over 500 commits in the past 6 months. The average bug is fixed and deployed within 10 to 20 minutes because I'm using my agents. So, let's look at the inbound progress. A little bit more background context. Inbound is an email service that allows you to send, receive, reply in threads, making it easy for AI agents

to sort of manage and work with email. This is the landing page 4 months ago. This is it now. That is I mean that just looks so much more of a legit product if you're if you would tell me. I would believe that. I wouldn't even believe that. That looks like a scam. Anyways, I've done a ton of great stuff with AI and I've learned how to use it incredibly well. I've been using it for almost 2 years. So, let's talk about the important part

of treating AI as a teammate. AI isn't here to replace you, but it's your teammate. But people badly prompt an agent like we'll jump into where they're like please fix this or something like that and it doesn't fix it. You've got to break down what you want in your head like the problem like you would diagnose it yourself and give that to the agent. So this is the email flow page in inbound and it worked. It is aggregating

a ton of data from a bunch of different data sources. the outbound emails table, the inbound email table, all the scheduled stuff, but it was slow. It took like 3 seconds to load like a week ago and it would work, but why why can it be this slow? We can't have it be like that. Now, I could have manually investigated this and looked into it and been like, "All right, let's dive into the code. Let's look into the drizzle stuff and the SQL queries. Where can I optimize this?" But why if I why would I do that if I have an AI assistant to

help me? So, I opened up cursor and uh just opened up my prompt and said, "Can you fix this, please? I don't need grammar. AI can understand me, right?" And uh yeah, it didn't really fix anything. There's no scope. There's no context. There's no end goal. What could any of you, if I gave this prompt to you, would any of you know what to do? No. There's no nothing to do. This is a C-tier prompt. All right, let's upgrade. Let's upgrade. We'll go from Ctier to Btier. All right, I'll give you a second to read this.

It's a little bit of a better prompt. It's an upgrade because we're having more refined scope. It gives the agent a better mental picture of what we're actually working with. We have some in goals kind of set. But this is the prompt that gets you the dreaded, let me generate a readme file for this. So that way we can just put everything together and and and put it all together. And no, we don't want readme files generated and markdown stuff. So, we'll upgrade again.