B (3:08)

So I built a mobile fitness tracker called Copper's Corner. And essentially the problem I was trying to solve, maybe I put my PM hat on for a sec, was I would go to the gym, I would try to be consistent, and then, you know, life gets busy. You start to slip one or two days, and then you go back a week later, you're like, oh, what was I doing? And so I tried these fitness apps where you kind of have to, like, create an account, set up your exercises, tell them what your gym has equipment wise. And I felt like doing a lot of homework. And even when you're working out, you have to like, log what you did, you know, your rest timers, things like that. And then last year I started using the GPT mobile app as, like, speech to text. And I was like, well, if the model can understand when I'm talking to it like it is right now, why can't, like a workout app do this and then kind of like tag the data for me and make it like a structured data set with analytics? And so that's kind of how I started down that path. And then I basically started with a little script, and then eventually, two months later, I now have like an Apple watch and a iPhone app. So I'll run you through how it works and then we can talk through how I built this.

A (4:09)

Okay, so you used AI to make getting swole at the gym easier. I am so excited about this as someone who definitely never, never skips a gym gym day. Okay, let's see how you built this.

B (4:23)

Okay, cool. I'll run you through how it works real quick just to get us. So everyone has like a visual context here. So this is the login screen. Now if you can see it, he's the hero of the image. Does this look good?

A (4:34)

Oh, Cooper. Cooper the dog.

B (4:37)

Yeah. And I don't know if you can see him, but he's sleeping right there. Literally like on the side of my screen.

A (4:41)

Oh, Cooper.

B (4:43)

Yeah. Okay, so the first thing is authentication, right? I'm using sign in with Apple. There's kind of a UX decision there because I don't want you to create an email and have to like, you know, enter a code. And so one of the first things you'll notice is when you log into the phone here, it logs into the Apple Watch. So there's some stuff I can talk about there, but essentially you could basically just use voice and record your workout here. And so I'll give this a shot. I did dumbbell shrugs. 35 pound dumbbells, 10 reps. And so what I built is you could record it from your phone or you could do it from the Apple Watcher. Because sometimes when you're at the gym, you don't always have your phone too, right? So let's see if it got it right. There we go. See? And it has a transcript here. If I try it from the phone right now I did jumping jacks, 35 reps. See, it sends it to the phone. So whatever device you have, it's kind of cool. It can log your workout pretty much with no work.

A (5:43)

So for people that are not watching on screen, this is an app that goes across your mobile device and your smartwatch and you basically speak to it at the gym, say what exercise you did, what weight, what reps. And it just automatically populates a structured record of that exercise, including what time you did it. It shows a picture of the equipment you might have used or a picture of somebody doing jumping jacks or in this case, push up jumping jacks. And it does simplify this experience of going to the gym. You know, like the gym bros with their notebooks where they're writing down their reps or in their notes app in Apple. So you built this. It's multi device, it's multimodal. It goes voice to text and text to structured output. Let's talk about how you built this thing because I wouldn't even know where to start in terms of the mobile and watch side of things.

B (6:42)

Yeah. And there's one more thing to show you real quick. I'll flash it on. Is we were talking about how do you be consistent. So there's actually like a history view here so you can look at your 7 day, 30 day, 90 day analytics to see how consistent you are. And you can see in like the last 30 days, I've been going to the gym 21 days. Right. So now I know when I've been slacking when I haven't been. And also I can see like my top exercises. You can see I do a lot of jumping jacks here. I do leg presses and then if you click into the leg press, you have like a whole history of what you've done. So now you have like a scatter plot of where my weight's going, like a history of if I'm actually progressing or not too. So that's kind of it. I could walk through how we built that, but any questions there.

A (7:21)

Now let's go through how you built it.

B (7:23)

Okay, so One thing with iOS apps is that you usually have to use Xcode, which is Apple's ide, to actually build the code. So I do something called dual wielding here. So this is what Xcode looks like. And what I do is usually I do a side by side with Cursor here. So the way I link this is I make both of them point to the same folder on your computer and then Cursor will do the coding and then I will do the building and the debugging in Xcode. The reason is because sometimes on the phone when you get errors, like compile errors, build errors, Xcode is really where you have to go to get that. Because Cursor, it's not like a web browser where you could just kind of look at the tools and then start looking at the console. And so there's a little bit of a kind of workaround you have to do. And I've seen some people online have these hot reload apps, but this is the kind of solution I found that works best for me. And also if you have to build to the Apple watch, you kind of have to do it separately. So that's kind of why I have this split workflow for now.

A (8:24)

Got it. So we want Cursor to somehow build a native integration here so you have a little bit more cross pollination, if you could.

B (8:32)

Yeah, yeah. And it's not like web apps where you just run a local host and then you kind of can see it in your browser. You have to kind of always build it on your phone. And right now you're seeing this in the iOS simulator. I would say even when you're testing mobile apps, like swiping around with my mouse here feels very different than when I'm on my phone testing in here. And it's even different when I'm in the gym actually, like running around and like trying to record stuff. And sometimes the audio is not great too. So I think when it comes to like mobile apps, and you're testing this, you just have to get as close to the actual experience. Otherwise you're kind of just testing in a box and not really getting the true kind of user experience there.

A (9:07)

So how did you get this started from zero, kind of. What was your setup in terms of defining the product, getting cursor set up, how did you work through that workflow and then doing the build and testing and xcoded on your phone?

B (9:22)

Yeah. So like we say in product, you want to, like, start. Think big, start small. Right. So the V1 of this was actually just using Apple Voicemail. Like on the Apple Watch, I would record that and then you would copy it to my computer. And then around February this year, I started getting into Vibe coding, and I was like, well, what if I have a Python script that takes these files and it takes a GPT4O and then just suits it to me in an Excel? And so what that looks like here is kind of this spreadsheet here. This was like the very V1 of it where you see the transcription. It attempts to tag it with different muscle groups and like, wrap sets. But the problem here is that this is not structured data. Right. It's just whatever the model thinks is the exercise. And so then I was like, all right, well then what is the solution then is then you got to put it into a database where it's actually structured data. You have, like, the foreign keys. You can actually manipulate it better. It becomes more consistent. So that's kind of where it went from this to a backend API that I built in Cursor.

A (10:19)

I want to pause here because I actually think this, for folks that are listening, is a pretty cool hack, which is using voice notes on your. On your watch to just narrate your workout at the gym and then download that text. You know, put it in even chatgpt or some sort of like, no code, little flow, and populate it in a spreadsheet. That's just such a simple and easy way to start. And then what you're saying is you're a PM and an engineer and you want foreign keys and a database. So you decided, let's make this a full app.

B (10:53)

Yeah. And it's also, if you look at the spreadsheet, how do you make sense of this right. Over time, you're not really. You don't have these analytics that you see here on the right side in the phone. And so I was like, well, how do you then do that? You can ideate with GPT. I think when you work with models, it could either Work with you or work for you. This is very much in that working with you side or just ideating on features and how you can potentially make like an MVP into like a low hacky tool that gives them higher iteration.

A (11:20)

So, okay, so you decided to build this app. How are you actually building? What is your step by step workflow in cursor?

B (11:28)

Sure. So I have kind of a three or four step process in cursor. So first step is creating a prd. Second is having a model review it and then third step is executing. And so the way I have that set that up is kind of three rules here. There you see PRD create, PRD review, PRD execute. And so if we take a file here as an example here I have an existing ticket. What I'll do is I'll take an issue, I'll add it to cursor here and then I'll have it run through PRD create. And what this rule does is essentially breaks it out into what you need to implementation. So any reference diagrams to actually do this task? What are the goals we're trying to do? One thing I do is I use gherkin user stories to actually describe the scenario. So the format is like given something happens when the user does this, then do this action. And so there's also some investigation here that happens. So if I don't know how to actually do something where the model doesn't know what files to use, what databases to touch, that's kind of a checkpoint here. And then this is kind of like the V1 of the PRD where it's not fully fleshed out, but at least it's the structure of it. And then one thing I realized is sometimes early on when I was vibe coding this document would not be enough. And that's kind of why I created a PRD review rule where it basically does like a check on that prd. So one question I do, I ask is if another model were to take this plan, how would you rate this out of 10 if they had no context and it had to execute on this? And so you're basically sanity checking your PRD to see if it actually has any gaps that a model could trip up on down the line.

A (13:13)

You've seen the doom and gloom headlines, AI is coming for your job. But the reality is a little bit brighter. In Miro's latest survey, 76% of people say AI can boost their work. It's just that 54% still don't know when to use it. As a product leader and a solo Founder. I love live or die by how fast I can turn fuzzy ideas into crisp value propositions, roadmaps, and launch plans. That's why I love Miro's innovation workspace. It drops an AI copilot inside the canvas, so stickies, screenshots, and brainstorm bullets can become usable diagrams, product briefs, and even prototypes in minutes. Your team can dive in, riff and iterate. And because the board feels like a digital playground, everyone has fun. While you cut cycle time by a third, Miro lets humans and AI play to their strengths so that great ideas ship faster and happier. Help your teams get great done with miro. Check out miro.com to find out how. That's M I R O dot com. So how did you build these cursor rules? And how did you know what to build and how. How to put stuff in this template?

B (14:30)

Honestly, a lot of blood, sweat, and tears. I think when I first started vibe coding in February or March, no one is really talking about memory banks or rules yet. And so the problem I was running into was every time I modeled it got to do more and more complex tasks. It would at some point trip up over itself. It would make up stuff. You would make a file, directories, you would get endpoints wrong. And so I realized after repeating it, telling it what to do time and time again, I started noticing these patterns and, like, how to give it context. And I was like, well, why am I repeating this over and over again? I should just make these into the rules. And so that's kind of how I ended up with these processes. And you notice I also broke them onto, like three PRD rules. The reason is because originally my rules were super verbose, maybe 800 lines long. And I realized I was just running into a lot of context windows with the same rules. So you'll see like, they're now no more than 200 lines long. And so I actually, like, I'm much more cognizant of how many tokens I'm using with these roles. And so over time, I kind of gotten more efficient with that as I get more experience with cursor.

A (15:31)

And the second part of this, which I think is so interesting and mirrors how things work inside product organizations, is you write a prd and then somebody looks at it, somebody reviews it, and says, is this good? And that person could be, you know, a PM lead. It could be a peer pm, or it could be an engineer. And it seems like you're taking this from an engineering point of view and saying, like, as a model reviewing this Zero context. What do you think? And I like this idea of rating 0 to 10. Do you feel like the ratings are generally pretty accurate?

B (16:01)

Yeah, and it's more of a barometer for me and how well I prepared it. If it's like a 7 out of 10, I'll then ask it, well, what are the 3 points? Why did you dock it? And it'll give me some reasons on why those gaps are. But is this an edge case? No, we could ignore that and it'll kind of. You want to get it to at least to like a 9 out of 10 before you do it. And the reason is then when you have it run through the plant, it could probably one shot it pretty quickly. And so I'm doing that here on the side. You see there's a 7 out of 10 here. And so it gives me like a strawman and steel man of it. And so you see the gaps identified. I can then be like, all right, inconsistent API, like are these actually things we need? And then I'll kind of then kind of iterate this until it's a 10 out of 10 and then that's when I then run the execute role, which I think you've seen is like the checkbox rule. You have it in chunks. Something I do extra is I have a git commit before and after each phase and ask it to pause. So I don't just have it one shot, everything. But this is when I know I can let it run, go get a coffee and then come back and just do some qa.

A (17:01)

Got it. So your step is write it as a prd. Gosh, your poor AI pm. You write the prd, then someone else tells it if it's good or bad. Then you iterate. Then the poor PM has to make epics and tasks. The AIPM has to make the checklist. And then you're giving very explicit directions on check in at every single point. And then you say, here you go, here's your prd, here's your checklist, Let it run. And then are you coming back and checking that code, doing the build in Xcode and then verifying it all works and shipping it?

B (17:37)

Yeah. So here's an example of one where on the Apple watch when I showed you, I hit record and I stopped was saying send to iPhone, but it wasn't staying on long enough. So if you're recording this, you may miss it. And then you may wonder, hey, did it actually even go to the phone? So this was adding like a little timer. So you can see that if you're kind of walking around the gym and there's like a feedback that, hey, this is. We got this. You don't have to worry about it. You don't have to worry about it failing. And so this is what the PRD looks like. I logged it originally in a tool called Linear. And so we pulled that in here and then I ran it through PRD Create. And so we created this doc. And so I'm very explicit where I even tell it what files you want to touch. Just because I don't want it to search through my code base waste tokens. Like, hey, here's what you need to do. Here are the files, here are the endpoints. Just go run with it. Yeah. So here's some of the example of the phase checklist. You see phase one, it does the checklist and every phase it kind of pauses. Right. There's like a safety checklist here. Right. No placeholder codes. We don't want you to make stuff that could break things. There's some error handling. And then it kind of runs through this.

A (18:41)

Yeah. And I want to pause for folks that are not watching on that checklist. If you could go back to it. It's really interesting. Every phase at the end of the phase says you have to verify the paths, make sure you're using real data, no placeholder, that you're handling errors well. And so it's really interesting that you really, again are following this pretty classic development pattern of like product manager, defines requirements, breaks down the tasks, engineer executes, you do a QA phase and then you move on to the next task. So you sort of structured your rules and your process to map to that. And then the only difference is you're using an AI PM and an AI engineer and AIEM to sort of run QA to run through all this.

B (19:29)

Yeah. And I think 80% of the time I'm working with the model, it's this last 20% where the checklist is just burning through tasks for me too. So I think the biggest switch is probably just learning to work with the model. I think is where if you get good at that. I think after this stuff is just kind of table stakes. It's just executing for.

A (19:47)

And I have to. I'd love to understand. You've mentioned conserving tokens for a while and I have to understand your motivation because I am just like, eat all the tokens you want. I just do not care. Tokens, everyone. You get a token. You get a token. Is this a cost sensitivity thing? Is it a performance of the tasks where you know too much context in the cursor context window actually degrades performance. What is your motivation for token conservation?

B (20:18)

Probably my sanity, if I put a thought to that. So the reason I say sanity is because LLMs are really good at just generating a bunch of code. It could be very robust. And so sometimes when you have very large files, I noticed cursor, when they go through your code base files, they read in like 200 line chunks at a time. And what I realized over time was that I had these files that were like a thousand. A thousand fifteen hundred lines long. And it was sending a lot of time just going through that. And then as it was going through tasks, it would just start getting tripped up a lot. And then that's when I kind of stumbled upon this concept of, like, I call it vibe refactoring, where you basically have to take vibe coding, you have to, like, reorganize it into something that's cleaner. And then that way, I guess it's like good engineering principles, they do that too, right? You refactor code, you keep it clean. So that's something I do with another rule here where I kind of have the PRD rule, but it's not meant to create features. It's meant to refactor existing code bases. And so I essentially give it the same, you know, context docs, I give it the API endpoints and I give it different guidance on, hey, what do we need factoring? Why should we do this? How do we make sure it doesn't break? Like, how will we curate this after it's done? And they kind of run through the same process of where you do in that PRD planning, but your goal is very different. It's more of a cleaning your apartment, making sure everything works fine, kind of.

A (21:36)

Okay, so I have to call this out for all the engineers, engineering leaders, large engineering organizations that are watching the podcast. Yes, AI does have the ability to generate lots of code and maybe not the highest quality code, always in pursuit of shipping features. And I know there's a lot of nervousness in the industry about, oh, my God, what If we give PMs access to ship code or designers access to ship code? The code is going to be so ugly, they're not going to know it's going to cause a lot of tech debt. But what I have experienced is that exactly this is actually quite good at refactoring. And I almost suggest to engineers that are adopting these tools or teams that are adopting tools is like, build the refactoring. As a known cost of your AI implementation. Almost planned it that way, where it's like, okay, I'm gonna. I'm gonna vibe code to the feature working so I can check that customers like it, that I can see that it works, that I can see if I like the design, all that kind of stuff. Get it out there, you know, like secure, perform it, but not beautiful code, and then go back and spend a vibe day refactoring. And I love that you actually have built. People would love to see these rules, so maybe we'll bribe you to share them. But I love that you've built this rule of like, this is how a good refactor goes. Here are my engineering principles that I want you to prioritize. Here's the things that you should think about. Here are the performance things you think about. And I think it's just a really nice process. And I've had this experience myself where I just, I build a feature, I get it out, people like it, great. I wasn't happy with the code, but I knew that. And I go back and refactor, and it's so much cheaper and faster, honestly, than almost any other path to like, the good code. So I think this is an exceptional way to do things.

B (23:26)

Yeah. And I have an example on my screen here of what that plan would look like for a refactor. So the quickest, quickest way to do that is just to do a line count and have the model do it. Hey, what are my biggest files? Which ones are like God mode that we need to factor down? So one of these is this recorder file we need to go into. But that was that recording logic I just showed you. There's 900 lines. I generally try to keep them under two to 400 lines just because I don't want the model to use context going over code. Maybe it doesn't need to do a task. Right. And same thing here, it has that checklist, right. Each phase. And then, yeah, basically each phase it'll try to do a build the next code and then make sure there's no compile errors. And it'll just keep chugging through that. We have that safety checklist here too.

A (24:08)

And let's make this clear for folks that are listening is you very intentionally set up one of the design principles of your code base that you want your files to be of a small enough size that the LLMs itself have an easy time working with and navigating individual files, getting tasks done. And I think this is really interesting because I think about it A lot, I think. As a human, what is my preferred structure of a file? Do I like embedded functions? Do I like a bunch of little bitty files across the. The code base? What is my preference? And sometimes I like these longer files because I'm in a file and I'm like, well, I want the definition of this here. I just want to be able to read and understand what this, this is doing. But a AI engineer reads the files very differently. And so what I like about your approach here is you're optimizing for your AI colleague and the way that they read this context. And it may or may not be the same as an engineer or human may want to read and retain the context. And so I think that's going to be a real challenge for teams that are putting this kind of flow into production, is making those design principles work for all systems that are contributing code.

B (25:29)

Yeah. And one thing that's useful if you make it smaller files is I have this final rule called Rubber Duck. So in engineering, there's a concept where if you're trying to work through an issue, you talk to an inanimate object, you explain the code line by line. And so what I use this file for is if I'm just trying to learn or optimize our rate of learning, like we just generate a bunch of code. I don't know what some of it does. If I want to just learn what it does. Can you just take this file and explain it to me? And then sometimes I'll have dinner, you know, I'll just ask it to like, pop quiz me and I'll just like, eat. It'll give me a function, I'll think about it. And then I'll kind of use this to Rubber Duck as a partner too. And so, yeah, it's.

A (26:05)

This is a, this is a great idea because I do this a lot. Once when I have let Cursor, you know, run through a big chunk of code is I just, I summarize it with, like, explain to me what you did and how you did it and why you did it. We actually put those really clear explanations into our pull request descriptions so it's very clear how something was built. But you're getting the A plus colleague award by actually quizzing yourself on how your own app works. And I think a lot of people are worried that, you know, vibe coders or whatever are going to build these apps and have zero idea how they actually work, whether they're secure. And honestly, they'll have zero idea of the underlying technologies and won't actually develop technical skills that can make them an overall better builder. And this is a really good strategy kind of built in to use your vibe coding process as a learning tool, which I, I think is, is the best way to do things. I have been a self, you know, self taught software engineer. I've always had to learn by like tapping a colleague on his shoulder and saying, like, what do you think of this code? How did you build this? Why did you make this decision? Why did you select this library kind of stuff? And now you just have this like, infinitely patient colleague to, to do that with. And I just think it's such an amazing learning opportunity for folks that want to develop technical skills, want to be able to code themselves or in partnership with AI. So I think this is a really awesome process and I would, I, I definitely want this. These rubber, rubber duck rules.

B (27:43)

Yeah. And I think rubber ducking vibe coding is essentially like a reverse rubber ducking. Right. Like we're telling the LLM what we want, but it's spitting out the code for you. Right. And I think building this muscle actually helps you build faster over time because you're learning how to debug stuff with LLM as your tutor. As you go through this process, you can start to see when it starts to make mistakes. And you can get through them faster just by going through this process and learning through your code base. And kind of the rate of learning is what you're trying to optimize for with this rule.

A (28:12)

I always think this is so interesting, all of you organized vibe coders out there. Ryan, who was on our podcast, has a somewhat similar, slightly different flow. Yours is a little bit more technically oriented. I still just like to float through the ether, eating as many tokens as possible, letting the LLM take me where it will. Maybe I will bring some more of this structure. I'm just really good at writing PRDs, you know, and so I start from there and then just let it, let it rip. But, but I love this process. Okay, I want you to show us one more thing which is a bit more on the design and exploration side, which is how you combine, you know, offline drawing and online to build little mobile prototypes and try out ideas.

B (29:01)

Yeah. So with mobile, the funding is I prototype this using index cards here. So I'll show you what that looks like. So sometimes in New York when you're in the subway, you run into these dead spots where you don't have reception. And so one thing I started doing is I started using these little index cards here where I would just draw out the UX and I can like you kind of like press something, you could change it to kind of simulate that kind of ux. And then what you can do is you can send this picture into GPT4 on your mobile device and just tell it, hey, this is a mock up. Can you help me upscale this? And so here's kind of what it looked like here as a scribble, right? And then you can start getting variations, asking it to change different layouts. And then eventually you can put this into a tool. I use a tool called uxpilot which can actually spit out Figma components. And then when you drag it into figma, there's Apple has some libraries you can use. So this is what the UI kit looks like. You can do like segmentation bar. They have different names for their different things. On the iPhone, you see this is. And then you just click insert and you can just start building like an iOS app very quickly with kind of the default Apple layout too. So that's how you can quickly kind of spin up a design.

A (30:12)

Okay, so you are prototyping a mobile app on your mobile app, sometimes with no connection by using an index card, which is a perfect aspect ratio for prototyping a mobile app. You take those, you upload them to ChatGPT use for. Do you use the 40 image generator? Is that what you're using to get the prototype?

B (30:34)

Yep. And I think this was around the time when they released Imagen. It just got really good. And so that's when I realized, oh, it could take a lo fi thing and upscale it for me very quickly.

A (30:42)

Cool. And then you drag it into figma and then use some of the out of the box components. I have to ask, have you ever just uploaded those index cards directly to Cursor to see what it it does with them?

B (30:57)

I have tried, but the results aren't great because I think it's like an input output equation is if you give it a lo fi thing, it just gives you something that's pretty sloppy. Yeah, I think everyone knows that you, the more hi fi you get, the better quality you can get. And so that's kind of where I'm really struggling now is like getting the design. Like I think getting the design 80% of what you want is pretty easy. But that last 10 1% is like really, really hard to fiddle with.

A (31:21)

LLM, this is what I tell designers all the time is I say your value add is not getting the forms on the, on the website. It's not getting the buttons in the app. It is that last 10% that really differentiates an app. And I still think there's this great place for human creativity and craft and innovation in that space. And so I hope the designers that are listening, you know, look at this app and they go, I know what the 10% is. And then they bring that to their, their companies or their projects.

B (31:53)

Yeah, it's like just looking at this app, there's things that annoy me and I'm like, oh, this is like the last 10%, but it works. I should do other things because just gotta keep shipping. Right. As one person.

A (32:02)

So, oh my gosh, you're giving us PMs. And our love for MVP is a bad name because, you know, those engineers and designers always want to finish that last 10%.

B (32:12)

Yeah, yeah. I think as a, as a PM, when you do these side projects, I think it also makes you communicate better with your engineers and designers just because you know what they go through. And like, when you go back and bring this context back, you can just have much better conversations by doing these side projects too.

A (32:28)

Great. I, I completely agree. Well, Terri, this has been so fun. We are going to do a couple lightning round questions and then get back to your dumbbell shrugs. My first question is, you know, the thing that I was struck with at the beginning of this podcast is the sort of like Xcode, Cursor, rebuild flow. And so if you could make an ask out there on behalf of all the mobile app developers to anyone thinking about AI software coding tools like Cursor or any of the agentic workflows. What's your ask?

B (33:05)

Anything that lets me know what's going on in the mobile. One example is there's no network tab in Xcode, so you don't actually know what traffic is going in, so it makes it hard to debug. I have to then do print statements, which gets very old school and annoying to do.

A (33:19)

Got it. So just basic quality of life improvements for mobile. Mobile engineers. Do you feel like the LLM models are pretty good at, you know, mobile languages? Do you feel like you're getting high quality code output when you're developing for mobile? I've heard a lot from users that, you know, these LLMs are really well trained on some ecosystems and languages and less so on others. Have you had any challenges there or you feel like they're pretty good?

B (33:46)

I haven't had issues yet. I think where I have issues is if it uses an older library or kind of way to describe the language. But other than that it's been okay because I think these tools now can access the docs. You could use websites, so you could kind of figure it out from there. And I think they'll just get smarter over time. So I haven't seen that be an issue right now yet.

A (34:03)

Great. Okay, and then my last question. You're so organized, so maybe you never have this problem, unlike me, who is very disorganized. But when the LLM is not listening, when it's making 900 line code files instead of 200 line code files, what is your tactic for getting an LLM back on the right track?

B (34:26)

Let's see. I will use a lot of git commits and then that's my fallback. Basically, I'm almost overly committed to that.

A (34:34)

So you are just breadcrumbing along the way each change. So you do risk mitigation as opposed to redirection. So you're like every little change, you're doing a git commit. So if it ever gets off track, you can just go back and reset.

B (34:49)

Yep. Every three tests, there's a git commit before, after, and that's how I know I can let it rip, because I have that risk mitigated. Right?

A (34:56)

Oh, come on. You gotta live. You gotta do like a 15 file plus 2500 lines, minus 74 line commit. You gotta live, my friend.

B (35:07)

Yeah.

A (35:09)

See, here's where we can show we're just very different people. Red, blue, fire, ice. You know, hot AI coding. Yolo, Very controlled git commit coder. Okay, well, this is very fun, Terry. Thank you for showing us your flow. I think this is really useful for anyone coding in these tools for PMs, looking how to get started or apply their process. And then for people stuck on the subway thinking about how they can make their next app, where can we find you and how can we be helpful?

B (35:41)

Yeah, you can find me on LinkedIn or on X. It's me, Terry Lynn.

A (35:45)

Amazing. Thanks so much. Thanks so much for watching. If you enjoyed this 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@howiaipod.com See you next time.