I spent $20,000 on Devin in a month. Here’s what I learned | Ryan Carson (solo founder)

If you're out there listening and you are doing engineering, you're doing your work locally, you really need to open your eyes. I think the future is pretty much 100% cloud agents. I went all in, so much so I spent $5,000 on Devin, and then I went up to $20,000 one month. You know, I think one of my big messages for today is that all of us have to uplevel our ability to manage agents. Like, that is our job. How do you effectively manage 10, 20, 100, 500 employees? This is the whole reason that organizations were built as pyramids. Like, humans can't scale and have a thousand directs. What is in your stack right now, and how have you structured stuff to make you successful and build things effectively? So what I'm doing is figuring out how to manage, you know, throngs of agents. And in Devin, what you're seeing is folders. And you'll notice P0 is the big stuff. These are the main things I need to move forward as the business, new features, P1, P2. So priorities zero. I've got bugs. Let them work. Usually give them a goal, and it's just such a crazy different world we live in now. Welcome back to How I AI. I have a super special guest, Ryan Carson, one of our earliest How I AI episodes, who is here to show us what has changed in the last 12 months in the age of coding agents. We're going to wax poetic about our favorite little AI intern, Devin, talk about all the ways you're underutilizing your coding agents, and give maybe the most anti-AI episode of How I AI, where we talk about where AI can't solve your problems, how you need to get out in front and actually talk to people, and how pen and paper still have a place in his stack. Let's get to it. This episode is brought to you by WorkOS. AI has already changed how we work. Tools are helping teams write better code, analyze customer data, and even handle support tickets automatically. But there's a catch. These tools only work well when they have deep access to company systems. Your copilot needs to see your entire codebase. Your chatbot needs to search across internal docs. And for enterprise buyers, that raises serious security concerns. That's why these apps face intense IT scrutiny from day one. To pass, they need secure authentication, access controls, audit logs, the whole suite of enterprise features. Building all that from scratch, it's a massive lift. That's where WorkOS comes in. WorkOS gets you drop-in APIs for enterprise features, so your app can become enterprise-ready and scale upmarket faster. Think of it like Stripe for enterprise features. OpenAI, Perplexity, and Cursor are already using WorkOS to move faster and meet enterprise demands. Join them and hundreds of other industry leaders at WorkOS.com. Start building today. Ryan Carson, number one episode of How I AI from our early, early days is back again. I am so happy to have you here, my friend. Oh, it's so fun to reconnect. And the reason why the show is good is because of you. And just everybody listening, I'm not just kissing ass here. Everybody that I meet, I say, there's one show, if you're stressed about keeping up in AI, just listen to Claire's show. Oh, thank you. Well, I'm stress keeping up with AI, so I will take all that stress on behalf of the audience and pass on what I know. What I also am so excited about this conversation is, you know, we did our first episode a year ago, or even a little more than a year ago, and, like, it's so different now. Oh my God. We were such babies. I know. It's kind of funny, like, what we chatted about now, and it'll be funny what we chat about now in a year, right? Yes, totally. And for those who have not gone in the archives, we did a really, really popular episode about how to manage your agents with, like, it was like pre-skills even. It was like three-step, like you invented skills from first principles. It was like three-step Markdown file. We were in an IDE, which I hadn't opened an IDE in months. We were in an IDE, and we were really, you were very— Prescriptive and directive of your agents. Very hand-holdy. Very hand-holdy. And now, you know, I don't know about you. I'll speak for myself. What the agents are doing is none of my business. No, let them work. You know, usually give them a goal and, yeah, it's just such a crazy different world we live in now. It's so exciting. Well, catch us up, because there's also been a lot of changes on your side in the last year. So what are you up to, and how has it, you know, impacted how you think about and work with AI these days? Yeah. So I basically had this idea to make divorce better. So I have three amazing sisters. We're like best friends. I have a sibling tattoo that's hard to show. It's right there. You know, we talk every week. And then two of them started to go through a pretty gnarly divorce. And my parents got divorced too. So, you know, I was like, divorce. Like, no one seems to be talking about divorce and AI. Why? Like, and so I just started working on that and was, of course, empowered by Thor's hammer, you know, which is large language models, and I started to build it. And this is when we chatted last. You know, I was in Cursor, you know, like you said, really hand-holdy on the agent. And since then, thankfully, it's just blown up. I basically figured out product-market fit. And everyone who's listening, there's probably a ton of startup founders out there. You know, you're trying to find product-market fit. You're pivoting fast. And I did what all founders do, right? You know, launched a version of Untangle, which is the product. Thought it was for consumers. Went out. Turns out nobody wants to use AI for divorce. They want lawyers, people. Just, I'm just gonna say it. And then I basically thought, okay, not PMF. I'm old enough to know, like, not hang on to things, just pivot. And I was like, okay, I'm gonna get a meeting with a lawyer and just see what they think of this thing. And she met with this amazing lawyer named Renee Bauer, and I was like, Do you love this? Do you hate it? Is this like an enemy? Is it a friend? And she said, I love it. You know, there's a paralegal shortage. There's this discovery thing we do in divorce is a nightmare. I love it, and I want to pay for it. And I was like, Oh, how much would you pay? And she said a great number. And now we're B2B, and we sell to family law firms, and it's just exploding. So I've been trying to hang on to this solo founder, I'm gonna do it all myself thing, and I'm completely overwhelmed. You and me both. And for folks that can't wait for the punchline, the punchline is Ryan Carson and Clairevo, famous, famous solo founder, I can do it all myself, I need no friends other than AI, did our pre-show conversation talking about our regretful and imminent hiring of a bunch of humans. Of humans. I'm gonna have to hire humans. And if any of those humans I'm talking to are listening, I love you, and I'm excited about working with you. But the AI, yeah, you get spoiled hiring AIs. I mean, you know, you give them— 45 pieces of feedback an hour. You know, you're— anyway. So yeah, gonna hire some humans and grow the Tingle team. Very excited. But you haven't yet. And so, I mean, the good part of the story is you were able to get to rapid iteration, lots of prototypes, product-market fit with you and our mutual intern, Mr. Devin. Mr. Devin. Mr. Devin. And so, you know, when you were starting out, again, you were, like, really coding, doing requirements documents, all of that with AI, but you were very human in the loop. And as I've watched you over the past year, I've seen you slowly turn into AI bro who runs agents overnight. So tell us about, like, what is in your stack right now? What is, like, very different from when we talked about a year ago? And how have you structured stuff to make you successful and build things effectively? Totally. I like to say I'm in max Q right now, for those of you that are, you know, SpaceX fans. It's like the maximum pressure that I need to hire somebody. I'm doing all the work. And so, yeah, what am I actually doing day to day? So I'll walk you through it. I started off, you know, in a more specific agent like a Cursor, like an Amp. And then I saw cloud happening. I'm like, okay, I'm really limited because I have to be at my machine. And there's a lot of things I need to, you know, quick PRs, like, here's a bug, need to sort it out. Or what about this piece of data? Need to, you know. And I was like, why isn't cloud, like, I feel like I should be working on the cloud. And I thought, what about Devin? Like Devin, you know, they've been doing cloud for like years now. It was kind of crap in the beginning, right? But maybe it's good now. And I tried it and I was like, wow, this thing's really good. This is not—it's really good. And, you know, and I thought, okay, I'm gonna try it. And I was just blown away by how mature the cloud agent was. And if you're out there listening and, you know, you are doing engineering, you're doing your work locally, you really need to open your eyes. Like, I think the future is pretty much 100%, you know, cloud agents. There's gonna be some local dev, but—so I started looking at that and was really impressed. So now I went all in, so much so I spent, at one point I was like spending $5,000 on Devin, and then I went up to $20,000 one month, and I'm like, whoa, wait a minute. I have a big Twitter account. I'm gonna go talk to the Cognition guys and tell them to give me free credits, and they did. So anyway, I, you know, get 20 grand of credits per month in Devin. Great. But the point is, I live in Devin. I live in the cloud, right? So all of my engineering almost—and it's Devin's right here on my screen—I've got probably, you know, 10, probably 10, 15 threads, and I bucket them in folders because I remember one of your shows, you know, it was either you or your guest was saying it's sort of like four or five concurrent tasks you can actually keep track of, and I agree with that. So what I use is folders. Is there any way to show it? I can show it. I'll show you one thing, which is this piece of paper. Perfect. And this is the AI podcast we're doing where we say we're going to hire humans, and we're just going to show you pieces of paper we scribble on. Okay, but there's a—I'm doing this for a reason, okay? So the reason why I have folders for threads and the reason why I have a piece of paper is because the skill is managing throngs of agents. Like, that is what I do now. And to keep it straight in your head, you basically have to bucket these things. And so I have one bucket that—I'll try to show this to you. Let's see how dangerous this is going to become, everybody. Okay, so everybody, this is Devin. This is my real setup that I'm literally working on today. And, you know, I think one of my big messages for today is that all of us have to uplevel our ability to manage agents. Like, that is our job, right? And so how do you do that? How do you effectively manage 10, 20, 100, 500 employees, basically? This is the whole reason that organizations were built as pyramids, right? Like, humans can't scale and have a thousand directs unless you're like Jensen Huang, then you can. But so what I'm doing is figuring out how to manage throngs of agents. And in Devin, what you're seeing is folders. And you'll notice I've got bugs, right? I've got P0, P1, P2. So it's sort of priority zero. What are the things that I really need to move forward no matter how distracted I get today? And so I'm going to show you again my piece of paper. Okay, so I have two methods for this. Don't laugh. It works. So the way I stay focused is, number one, have a P0 folder. But then, you know, I've got a Dell 52 here. I've got eight screens concurrently open, right? And so the way I stay focused is by also having this piece of paper, which has weekly priorities on it. Okay, so it's all about weekly. What is important? And I'll pass my eye down here at this beautiful UG Monk system I have, which I'm not being paid to say that. It's a fun little to-do system, and that just keeps me grounded. Okay, so let's dig into this a little bit. Bugs is like, okay, there's some stuff going on. I want to get it pretty fast. It's not necessarily P0. You know, let's look at a couple of those. You know, that's the one we're looking at here. Investigate red error retries, right? So Devin's cranking on that. There's a couple other bugs in there. P0 is the big stuff. I'm not going to show you that, but that's just like, these are the main things I need to move forward as the business, new features. Usually P1 is like, ah, stuff that's important. Anyway, it goes down. Investors. By the way, tip, oh my God, like if you're not using an agent to help draft your investor updates and help you keep track of the business, like clearly do that. But here's the key: build a skill to do it. And this is probably obvious to everybody, but another thing I love about Devin is this idea it has playbooks. And playbooks are sort of, there's this weird mix of skills, playbooks, you know, sort of thing going on, but I built an investor update skill, basically, which does a lot. So this is most of where I do work, and then you'll find, like, then that means I do a lot of work here. Like I'll be on my phone. And this is the other reality, is like, unfortunately that means I can work like 21 hours a day now. And so you do. I do. And then, you know, and how do you deal with this? How do you deal with, like, the decision fatigue? Yeah. So I want to reflect. I'm going to answer that question in just a second, but I want to reflect for folks what I'm seeing here, because you and I are different AI managers. And every time you come on, I'm like, no. I'm like, what an organized, what an organized individual. I am so impressed by you. You're like, Where's my three steps to managing my agents? And I'm like, You don't just, like, float in the tokens, see what comes out the other side. And you're like, Here are my, like, prioritized triaged folders for Devin. And I'm like, I just Slack Devin. Like, he belongs to me. I just, like a Sentry link, WTF? Question, question, fix. And that works. There's nothing wrong with that. Yeah, it totally works. We're so different. But I do think, you know, something you said earlier I want people to hear, which is, like, the job right now is to figure out how to manage agents. And the reason why, I know both you and I are 27, so of course we're young, we're spring chickens. Infinite energy. The reason why I think folks of a certain level of experience are, like, ready to cook right now with AI is all those management skills that you have developed over your career can be applied right here, right now. How do you structure? How do you team? How do you prioritize? How do you delegate? When you have a team of 500, how do you still stay anchored on, like, the three things that are most important for you to do? Where do you micromanage? Where do you let go? Like, all that stuff still pays off. Yeah, and it pays off. Yep. I think in multiples. Like, so another practical tip I want to talk about is I have—it's a playbook, but it could be a skill if you're not using Devin. It's called Watchdog. And, you know, we're starting to pick up a lot of family law firms now, and they have a lot of cases, right? And I'm literally doing customer success and engineering and sales, right? And so it's like, whoa, how do you keep track of actually what's going on in these cases? You know, where are clients hitting UX bugs? Like, where—oh my God, how do you keep track of it? So Watchdog, what it does—and this is multiple iterations, everybody—so what you want is, like, when that moment where you feel like, I need to know what's going in the business right now. I feel stressed. I don't know what's happening. This is when I run Watchdog. And what it does is it basically, it has a skill that's repeated for each firm. So think of these as customers, right? And it goes into each account and says, What's going on with this account? Like, what was the activity since we last did Watchdog? Where are the errors? Where are the sentry errors? You know, where does all this happen? But then you don't want just data. You want it to be transposed and filtered and sorted for you. So then it comes up with the top three things that are going wrong. And then either like, well, wait, have they been fixed? Because we're shipping a lot of PRs. Like, I'm shipping probably 40 PRs a day now. So did it get fixed, or is it currently being fixed, or is there an open PR that never got merged, right? And it just gives me all that. And then I talk to that thread about, okay, let's dig in a little bit. And that's how I manage the chaos. Yeah, I, you know, you asked me, how do I manage the decision fatigue? And I feel like I start a business for every child I have. So like three kids, three businesses. I have a lot of decision fatigue. There's a couple things that I do. I approach it very differently, which is I think about bucketing my time more than I think about bucketing the tasks, which is like, there's time in the day that I do like very, very specific tasks where I'm co-piloting with AI. There's other time where I'm just like, I dedicate to spinning off everything or checking in. So I have to, as a solo founder, I have to bucket my own time on things. The other thing that I use is I use decision fatigue as a prioritization heuristic, which is functionally, if there's a feature that I'm working on that I let die on the vine, that is my— That's your symbol. That's my symbol for maybe this one is not the one I really care or believe in. And so I sometimes think that people, you know, don't tell anybody, I know I'm a token maxer, and you should let your agents run 24 hours a day and ship as much code as humanly possible and software everywhere. And I really don't. Ship more than I think the market wants. Like, I really try to, like, constrain my output capacity — not on quality, not on bugs — but, like, because I don't think I get multiples of quality off of multiples of output. I totally agree. And so I would rather reserve that creative energy for something else, or at least keep it inside till there is something there. And so I do — I run less overnight. I run, like, bugs and triage and all that kind of stuff. I also work with an engineer, so we kind of ping-pong overnight. But I don't do the sort of, like, seek out ideas, solve them, and always ship them, because I just don't want it. It puts too much on me, and two, I don't think it actually adds value. I agree. I actually think we're nowhere near any frontier model having the intelligence to know what to ship. I agree. It's like a million miles. I mean— I agree. So, yeah, I think, you know, I think we all wanted these sort of, like, automatic improvement loops, and they just don't work with product. They're kind of a joke. And I tell people it's also because all of this intelligence has not magically created markets where there were none before, other than AI markets, right? It's not like all of a sudden there are these, like, buyers that have shown up for solutions— Yeah, for stuff. And so I do think there's this, like, mismatch between the quantity of output of code and, like, commercializable product. Amen. So I want to double-click on that. I think what is happening is people are not getting out of their chair enough and actually talking to real people. So, you know, the way I figured out PMF for Untangle was, you know, I went outbound with an email. I did a Google Meet with a potential customer, and I talked to them. Boom, that was step one. But then step two is, like, as soon as we landed them as a customer, I was like, Can I come to your office? And I just want to sit and I want to talk and I want to, and this is all like obvious product stuff. But I think because we can ship so much and build so much digital product, we're not getting out of our chairs enough. I totally agree. Go talk to humans, for real. Humans, yep. And build stuff they need. This episode is brought to you by Jira by Atlassian. The teamwork graph in Jira delivers 44% more accurate agent results with 48% less token usage. That's a huge difference when working with AI coding agents like Claude, Cursor, Codex, or Copilot. The hardest part of shipping with AI isn't the code, it's the context. What's the right ticket? What did the spec say? What got decided in Slack? The teamwork graph pulls all of that from across your entire stack, from Jira and Confluence to GitHub, and feeds it directly to your agents before they write a single line. You assign the work, the agent gets everything it needs, and a PR surfaces when it's ready. No digging, no context switching, no broken flow. Same team, smarter agents. Try them free at jira.dev. That's J-I-R-A dot D-E-V. The other thing I want to touch on, because I think you breezed past it, but it has been a game changer for me in terms of using background agents, and in particular Devin, which is I think people have still bucketed these cloud coding agents as coding agents, which is like their only job is to write code for a product or software product. And in fact, Devin runs deal desk for me. So Devin's doing quoting, custom quoting for me, like setting up operations, documentation, customer triage. Like I always think, you know, what would you do with somebody who both knew your code base and could write code to solve anything in your business? That's how I use these background agents. And I do think that people really don't ask enough of their background agents, and especially ones that are very good at coding. I think this is why it's so interesting. Cursor just yesterday came out, or Cursor, Grok, whoever, whoever they are, came out with GrokBot. And I was like, you know what? The Cursor chat experience as a background agent was a great one. It was like one of our first episodes. And so I'm not surprised to see these, like, coding platforms start to generalize into business agents in general. And I also feel like more than engineers need to get hands-on with background agents and cloud agents, because there's so much that they can do for your business pretty autonomously. A hundred percent. But let's talk about, though, why probably both of us are still using local agents for some things. So right now as well, I have Codex running, and I have it using Go. And I find that in particular, like the low latency plus the browser on my machine... Pairing, like, plus, like, basically infinite tokens, you know, from OpenAI. Yeah, cool. I'll take the subsidy. That, you know, plus goal really, really is good for when you have this kind of, I've got a feature, it's a lot of front-end UI. I just need you to grind for a lot, and I need to be here and kind of hold your hand. I find Codex unmatched for that. Yeah, so if I were to, because what we said we would do is compare and contrast our solo founder AI setups. So I would say I am personally spending my time in Codex when I'm pair programming or managing a product. It falls into a couple categories. It's going to be, like, large feature initiatives that span front-end and back-end that both, like, again, need, like, a lot of code written and you have to grind on it, and needs that, like, intervention every now and then to narrow it to the experience that you want. A lot of, like, long-running refactors and tech debt stuff. Like, again, I think the latency is unmatched. Its goal is really, really effective. Sub-agents are really, really effective. And then I use Codex a lot for verif- I think it's very good at verification. And so a combination of Goal plus a CLI tool inside your codebase that can verify core flows, or I use Goal and browser use to do front-end verification a lot. So I say, write user stories, use Chrome, pull up the preview branch in Chrome, go through it as a user, list which user stories pass, identify bugs, fix them until you're good. Those are kind of what I'm using Codex for. When I'm using background agents, it's a lot of, like, auto-fixes on bugs. One-off, like when I'm on calls with— With customers, and they say, Oh, do you have this MCP? I'm like, I do now. So one-off things, and then sort of operations, as you said. Like, I use a lot of agents for operations. And then, you know, I do have a couple, like, purpose-built agents in the stack. So I use BugBot a lot for PR review. And then I just built this thing delightfully called Merge Mommy that does risk assessment on my PRs and auto-approves low-risk ones, because I am also shipping a lot of PRs. And so that's— Tell me about Merge Mommy. And then I'll tell you about my land PR skill. I want to compare and contrast. Yeah, so I did an episode on this a week or two ago. It's an Eve agent, so it's deployed on Vercel. And whenever a PR is opened and then passes all its CI checks, including BugBot, Merge Mommy gets triggered. And then what she looks at is she scores the PR on, like, five aspects of risk, like how big, blast radius, security, whatever it is. And then if it gets scored as a low, Merge Mommy stamps it with an approval, and we can merge without a human approval. Cool. But if it's medium or high, then it pings us in Slack and says—it pings either my colleague or I or somebody else in Slack and says, This one's ready for you to review, because for our SOC 2 compliance and all our controls, we require kind of like alternative review. And it just allows us to, like, get through our PR queue very efficiently. Okay. First of all, annoyed I missed that episode. That sounds amazing. I'm gonna go watch it. But number two, interesting. So I have something called land PR, where basically it's a playbook in Devin, but you can think of it as a skill. And it's usually it's when the agent comes back and says, Okay, the PR is done, you know, and then I trigger it, and then— What it does is it basically makes sure that, number one, it runs a fresh Devin review on the PR, which—and Devin review is like an actual product inside of Devin, which is another reason why I think people should just pick—I'll sort of rant about that later—but the Code Factory, like, it should have a good built-in review that is a real review product, right? So it triggers a review, and then it basically allows up to two loops on that, right? You know, okay, all right, find all the bugs, check that all the comments are resolved, and then there'll be some more that come up, do it again, does it twice. And then the thing is, is it records a video walkthrough. And this I find Devin's just really good at. Like, so what it does is it records in the browser, and it actually kind of narrates over it. It's got captions about what it's doing, and it's got this cool little list of tests it's doing and whether they're red or green. And you get all this out of the box. Like, I tried to build my own Code Factory and get all this stuff, and I was like, I don't have time to do this. And so the land PR, basically it has to show me that video, and then I say, video approved, land it, and then it will merge. So that really works for me. It's kind of that—I think this is where CI/CD and DevOps, like now you have to be even better at it, like, and really care about it. And we use merge queues in GitHub as well. I'm loving merge queues. So a couple of the nitty-gritty, this is what I'm actually doing stuff. Have you—okay, you all know, this is how you know, not sponsored by Cognition, but you all are welcome. We love you. Yeah, come on. I can't get Devin video verification to work. I can occasionally get it to screenshot. Really? And like on front-end stuff, it taps my— My credits for the session and then just falls over. I don't know if it's probably a problem. It's probably a me problem. All AI things are probably a me problem. But I have not been able—but actually, I do want to show this for folks that want to know exactly what it looks like, because I found an example of it. So I'm claiming that it doesn't work, but then I'm going to make it work. Devin will actually go ahead and test it and record a little video of it using—and you can see these little captions down here. Isn't that cool? It's exposing its reasoning. It's super cool. It's very useful. I can just only get it to work. Okay, so a couple interesting comments I have on that. Number one, interesting that you're in Slack. Oh, I'm never in Devin UI. Never. Okay, so interestingly, I'm never in Slack. I am trying to cut Slack completely out of Untangle and the way the company is going to exist. And I was laughing because you have so many sidebar, you know, notifications and exclamation points. And we were saying, you know, you're seeing the Devin preview in Slack. And I have a very kind of perfect experience with the video playback testing of Devin, and that's because I use the web app. And so here's what I'm thinking. And again, this is probably going to change, but as we hire people, I'm actually going to require, like, multi-user interaction to happen through Devin. So we talk in threads about what is going on. That's thing one, because then you're not trying to always figure out where's the context for this thing. You know, is it in your agent? Is it in Slack? Is it in Google Docs? Like, where is it? So I'm going to try to do that. Now, obviously that doesn't work for DMs and channels and all that stuff. But I also think—and Jack Dorsey, I think, was saying this—you know, they launched Buzz. It's kind of interesting. I think he banned DMs, or somebody banned DMs in their company. And I think, you know, as we scale, I'm going to do the same thing. Like, I don't want any one-on-one chats. Like, if we're having private— Like, if we're having private conversations, I'll call you. So that's why I just think Slack is not built for the AI age. Well, let me tell you why I love Slack. Okay. Convince me. I like to personify—first, I like to personify my agents. I like to, as a solo founder, I need my colleagues to be fun. Fair. I'm just boring and mean. It's marginally more fun in Slack to use Devin than in the web app, although they're interchangeable, actually. You're just seeing a reflection of the web app. The reason why I think I have been so committed to Devin in Slack is actually not because I think it's a better experience. It's that very early on deploying background agents inside companies—this is where we're going to agree to agree—inside companies. So when I was at LaunchDarkly and we were first deploying background agents, in particular Devin, it was such an effective change agent move to put these background agents in public Slack threads. Interesting. And so, like, it was one of the places—actually, it was the only place I had experienced up to that point where you could do real-time coding work in public. Cool. And I think that changes people's perception of, oh, what is AI capable of doing? How do I work with AI better? And then I do think, you know, in particular Devin's pretty good at multiplayer chat. It's one of the few ones that, like, you don't trip over your colleagues when you're both chatting in a thread. In Slack. But I think it's—yeah, in both, in Slack and in the web app. Okay. And I think it's just, I'm a creature of habit, having told everybody to shove their Devin threads in public channels. Yeah. That that's why I'm using it. Okay. You know, I'm— I do think that chat's not going away because I think that's how humans like to work, like communicate. So it's hard to feel like chat's going away, but I do think more and more people, if they don't want to get rid of Slack, want to get rid of Slack culture, which is like DM culture, private channel culture, like needless conversation culture that doesn't result in anything. Yeah. And so almost like every thread in Slack should result in work. Yep. But it doesn't. It feels better. It doesn't. It devolves into just, you know, and I love humans, trust me, but I don't—listen, you know, I did a stint at Intel where I was an employee, and I learned a lot about what it's like to be an employee, you know? And I just realized you spend a lot of time talking about stuff that doesn't matter. You're not empowered to do anything, and it's like, you know, what's the point of that? So, and the agent is always going to need the context of whatever you're talking about. So have the conversation there. So before we leave, I know you have a hard stop. I do want to talk about the third plane that I have, which is a little bit of Claude Code. So I, yeah, so I'm number one, it's like it feels like infinite tokens, but I just can't get around how good Claude design is. Now, I don't mean in coming up with new design. I think it's bad, but I think for carrying forward, you know, a design system, it does something magical that Codex is hilariously bad at, Devin is terrible at design. And so I always have to go back to Claude design. So... Am I missing something, or do you do something magical design that's working for you? So this is a great question. I was telling you before this, I'm launching a new business. We've got a new brand, new design, and so I went through this process very recently, so I can tell you what I did. I think Claude Designs, Create a Design System, is, like, unmatched right now. Okay, I agree. It does a great job of decomposing either an example site or a Figma or something into relative non-slop design tokens you can reuse across a property. Now, that being said, my most recent process is I went to Claude Design, I created the kind of, like, design.md and the design file in Claude Design. I downloaded that, gave it to Codex, and said, Take this plus what's in the Figma and actually build me a technical design system. Oh. And it built all the shared components. It made this nice, like, interlinking inner mono repo. Oh, wow. And then I also tested with Codex using the Figma plugin to then go pull all those design tokens back into Figma into components that I could use. So once you had the design.md and ported it to Codex, then you were unlocked. Yeah, that's exactly what I did. I mean, my problem with Claude: infinite tokens, very intelligent. My blood boils reading Claude output. It, like, actually raises my blood pressure. It makes me so angry. So the one podcast I listened about the opinion on Opus 5 was yours. Yeah. Because I love your take, and I couldn't agree more. I'm so sick of Opus 5. Like, it's just so frustrating. It's terrifying in one way because it's like, Oh my God, it's way worse than we thought, you know, about everything. And so you're like, Okay, you know, which is actually, what's wrong here? And so it's, like, super smart, but I really am sick of Opus 5. Yeah. But I do think the applications in some, like, very specific deep spikes... Cybersecurity design, like kind of unbeatable on the execution side still in Claude, but I am, I just, the Harness experience of Codex is just a lot more effective and enjoyable for me. It's so good. So last question I had before we go is, we can both answer. You go first. Like, what's your current actual EA? Like, who's your actual sidekick that does all of your agent work as an executive assistant? Polly the OpenClaw. Interesting. Okay, you're on OpenClaw. Still live in OpenClaw. Okay. Just pod committed there. Yeah. I love OpenClaw. I love Pete. I love the team. I love it. I just moved off. I was like, screw it. I'm just gonna run Claude Code on my Mac Mini. And I actually want to switch to Codex because I just love, love, love the UI of Codex. It's so, it's wonderful, the whole thing. Yep. Yep. Yeah, no, I use, I still, Polly the OpenClaw is still running, but I do now have my emails constantly open in the browser in Codex, and Codex functionally runs my email. It ran through 2,000 unread emails in my Gmail the other day and just changed my life. This has been a game changer. So like you, I've hired a lot of people in my life, like hundreds and hundreds of people, and let go lots of people and all this kind of stuff. So the way I'm running my hiring process right now, I really love it, and we'll see if it works out, but I think this is interesting. So what I decided to do is I basically, on Twitter, I was like, okay, we're hiring our first engineer. You got to be like super duper duper AI forward, you know, of course, and I don't really care where you live. And all I want you to do is record a video, full screen, everything, your whole desktop of you building a new feature for an app that already exists, and I just want to see the whole thing. I don't want to talk to you. I don't want to have a meeting with you. I don't want to get to know if I like you. I just want to see how good of an agent manager you are. And the videos I'm getting are fascinating and very revealing about whether I would want to work with this person. And I'm liking it. So I've got, you know, a number of people that are probably going to move to phase two, where then what I'm going to do is say, okay, give them access to Devin and actually build a real thing, and then—but record a video of that. And then basically at the end, I'll do some sort of quick, well, we should meet, you know, and chat, and then I'm going to hire them, and then I'm just going to watch their agent output, and that's how I'm going to manage them. I mean, well, one other thing is if they work with Devin, you get the replay video anyway of how the Devin computer works. So saved you a step. Thank you. Although the one meta observation I have on this is you're almost hiring a human like you would hire an agent, which is like, I love you, like we'll get along, I'm sure. But like really, I just want to see how you do this. You're doing a verification loop is what you're doing. Yeah. And think about how much better this is in this insane way we used to hire. Yeah. You're like, I like this person, and then you're like, we're going to kind of ask you to do some weird technical project, and then—so very excited to see this shake out. Okay, well, just to recap for everyone, the two most AI-pilled people on your timelines spent most of our time talking about how too much AI code doesn't really get you great product. Amen. You should just go outside with your human body and talk to customers. Agreed. Keep your priority on a piece of paper. It works. It works. But, you know, on the technical stuff, set up your background agents, prioritize their work in a way that you can manage. Everybody's becoming agent managers. Your coding agent can do more for you than just code. And the new interview is— Just let them cook and do a screen share. And also, to conclude, the solo founder AI agent managers are both hiring. So, Ryan, where can we—we, I know we can find you online, but where can we find you, and how can we be helpful? Who are you hiring for? Thank you. So I'm super active on X, so just Ryan Carson, hit me up anytime. And then if you want to help people have better divorces, because people are going to get divorced, okay, go to Untangle.us. Check us out. And then just shoot me a DM with a video of you working, and I think we're going to hire someone pretty fast. So move fast and say hello. And I'll say, if you impress Ryan with your video, you're probably going to be an upcoming guest of How I AI, where he will show us how you use your background agents. Awesome. Well, Ryan, thank you so much for joining. This has been a blast. Thank you. Thanks so much for watching. If you enjoyed the show, please like and subscribe here on YouTube, or even better, leave us a comment with your thoughts. You can also find this podcast on Apple Podcasts, Spotify, or your favorite podcast app. Please consider leaving us a rating and review, which will help others find the show. You can see all our episodes and learn more about the show at howiaipod.com. See you next time.