Episode Transcript
[00:00:05] Welcome to Prompting Curiosity, a podcast for the AI curious. No coding background required. I'm your host, Dr. Shantae Cofield, also known as the Maestro, and I created this show to explore what these AI tools actually are. Really, though, are the files in the computer, how to use them, and what they might mean for how we think, work, create, and move through life. Whether you're skeptical, intrigued, or already experimenting, you're in the right place. All that I ask is that you stay curious. All right, let's get into it.
[00:00:38] Hello, hello, hello, my curious people, and welcome to episode 38 of Prompting Curiosity. I'm your grateful host, the Maestro, and today we are talking about using Claude to build custom tech solutions. The inspiration for this episode. Well, remember that wish list I spoke about in episode 36? Hopefully you do this, like, two episodes ago. Uh, well, I went ahead and used Claude code to check off the second item. I was a little bit pushed, uh, if you will, by the fact that Claude had rolled out or anthropic had rolled out, like, bonus usage tokens, like, extra usage. And it was expiring, and I was like, imma get mine. I'm going to use it. Uh, so I stayed up and I, uh, built it. And I actually did not save as late as with the other one with the other project. Um, but I use cloud code to build out that second item on the list, which was a custom. Which is a custom dashboard for my messaging coaching clients. So if you listen to the episode, episode 36, I will link it. Um, but yes, y', all, sorry about that. I'm just moving the mic here. Vibe coding with AI absolutely requires a bit of tech tenacity, but like I've said before, it's more so patience than anything else because you communicate with it via natural language. You're just typing, talking to it. I use whisper flow, and I'm just talking to it and being like, this isn't working. This is what I want. And you can literally ask it anything. You can ask it to do anything. You can ask it how to do anything. It will walk you through step by step, anything that you need to do. And if you're unsure because it's written out, you can just take screenshots of things and upload it and be like, this is what I'm seeing. And, yeah, you got to go back and forth. And sometimes it assumes things that, like, just aren't true.
[00:02:16] Um, but again, that is an exercise in patience, right? And it's. The rest is just, you know, you just gotta tell it what you Want and be patient and go back and forth. The only real limitations that I see as you're using AI to, to build this stuff is that one, you are paying for usage and you can hit your usage limits. I have yet to hit them, but also that was, that is why I wanted to take advantage of the like bonus that they were doing. Um, worth noting, Anthropic did just have an issue with usage and you know, people were hitting their usage in like 15 minutes and there was clearly like a bug. Um, but I have not experienced that. But the solution here as it relates to the fact that there are usage limits, which I think is a good thing, right? Solutions. One, you could pay more, right? You can pay for higher usage limits. I'm only on the 20 tier, I could go to the hundred tier and I would definitely be fine. I'm more than enough fine. I've been more than enough fine with the 20 tier. Uh, you could use a model that uses less tokens. I think this is a big issue for people. Um, I have built everything with Sonnet as opposed to the more token hungry Opus. Um, the one that's not, that's like normally the default that's selected is Sonnet and I just use that. I know that you know, in the coding world people are all about Opus but like it, it's like very apparently very, very token hungry. And I don't for what I'm doing, I'm just like, it's fine, it's totally fine. Uh, so that's one solution to the fact that there are usage limits. Uh, another option is that you can do some of the coding, you can do some of the um, implementation yourself. Right? So part of what happens when you use cloud code is that it makes files, it changes things, that it writes things, it creates code, it writes code, it deletes the code, it's putting it in the files itself that takes tokens, Right? You could do some of that yourself if you want. And when I was building out some of the other things earlier on, I, I was doing that and I would ask it for the code and then I would go into the specific files and I would do that. Um, um, so that is another option, another option for these users, you know, dealing with usage limits is just being able to ask better questions and needing less back and forth with the model because you know what you're doing. And so, you know, this is my. I've uh, been doing this for a bit now. I know and I'm going to go into this in a bit. But Like, I know the tech stack that I want to use. I know what I want this thing to look like, I know how I want it to work. I know what kind of some of the integrations that I'm going to need. And so I don't have to go back and forth and like, one, I don't have to go back and forth and have the conversation. But two, I don't have to go back and forth with trial and error of like, it builds. And then I'm like, wait, this isn't what I wanted. This, like, doesn't work this way because I know it's not going to work that way because I know what I know now from having already done that trial and error. Um, but, um, that's a good segue into the next limitation is that you don't know what you don't know, right? So a limitation in using AI, uh, and vibe coding is that you don't know what you don't know. And so you don't know that you need a way to deploy this thing so that it's not just available on your local browser. You don't know that you need a database attached to it so that it stores in front information between sessions and you can actually access it from all of your devices and, you know, continue m it continuously ongoing, um, access it. And all the stuff that you put there is still there.
[00:05:20] What is the solution for that? Well, one is the podcast. This podcast, because I'm sharing this stuff with you. Two, trial and error.
[00:05:27] And three, you learn as you go, right? You ask it how to solve those problems as they come up for you. So, you know, the first time you make one of these custom tech solutions, it will probably just be local. And you may not understand what I am saying until you build, build one. And then you're like, wait, but how do I, like, access it from my phone or access it from anywhere else besides this very computer? How do I access it from my laptop? And then it'll be like, oh, you have to deploy it somewhere. And then you're like, okay, how do I do that? And it'll give you solutions, right? So I realized and I learned, you know, I took some courses on this and I didn't really understand what it was talking about until I started building stuff. And, you know, uh, hat tip to these courses because they do have you.
[00:06:09] Sorry, I'm moving the mic again. They do have you build stuff. And so you're like, okay, I have to, like, deploy it via this. And so, you know, you get your Favorites early on. Um, but a lot of it, you will just learn. And it will, you will learn as you go, and it will make sense as you go. You'll solve the problems as they arise, and you'll be like, okay, I understand. And you'll ask it, you'll be like, claude, what the fuck? What is happening? How do I do this? I want this to look like this. I want this to be able to do this. How do I do that? And that will be.
[00:06:34] It'll give you the answer. All right, so for the 11 billionth time, my goal with these episodes and with this podcast is largely just to expose you to things so that you realize what's even possible.
[00:06:45] I am by no means here to tell you that you need to go and try this stuff today. You must do it. You're going to miss out. None of that. I, uh, I told you before a million times. I don't, I don't actually don't care if you use it or not. I just want to open your eyes to what's possible.
[00:06:57] I, I, that's all I want you to know. It's possible. And then, you know, realistically, what is possible will only become more possible and easier to access as time goes on. So I don't, I actually don't think, I think we're in a point where things are getting better and now it is definitely about implementation, but things continue to get easier. And like, I learned this not that long ago, right? So I went away, what, in October? November, I think. I'm trying to think when we go away December, uh, we go away with, with our couple friend, and that's when I was, like, really starting to get to December. Yeah, I started this podcast last August, got into this vibe, coding stuff in December. It is currently April, and things are so much different. Like, there's a, a storage system, as I'll call it, called GitHub, Git.
[00:07:51] And I was learning the commands for that and how to push things, how to send files there so that they could be backed up there. That's essentially what GitHub is doing. And, and you can just have Claude do it. You can just say, hey, push to get, and it will do, it will commit it, it will stage, it will do all of the things. And like, I'm like, I'm forgetting the commands now because I haven't had to run them. And that wasn't a thing in December. Like, that's crazy to me that, how you can just, it's crazy. And so I don't think that you know, people are going to be like, you're going to, like, oh, you don't pick it up now. You're going to be left behind. I do think that there may be a little bit of ease, uh, you know, if you wait and you learn later on. But I think that there is, uh, protection, future proofing, I don't know, a little bit more safety in learning the full way of doing things. Right? Like, you know, like, everyone. You're gonna give them everybody a calculator. Go ahead. But, like, I think you should know how to do addition and subtraction and those things. But by all means, yes. And multiplication might. But by all means, yes, go ahead and use the calculator. I think what's gonna happen is that people are just gonna be handed a calculator. They have no idea how to actually do the cal.
[00:09:00] That's like a little bit.
[00:09:01] You know, there's something there. But again, like, I am, um, by no means a coder, Uh, I. Someone that's actually a coder would listen to hear me saying this and being like, you don't know about. And I'm like, that's fair. That is fair. But I do think whatever we can do to, like, somewhat understand how things are working, that's not a bad thing. All right, but all that to say, I'm never here to scare you and be like, you're gonna fall behind, get left behind. No, Like, I think things are getting easier to use. And, uh, I really just want you to know that this stuff is possible. Right. It is my hope that you continue to live your life and run your business. And one day when you're like, damn, I wish I could do X. Or I wish I had a robot that did X for me, you think to yourself, hey, I could probably build that with AI or I could probably have AI build that for me. And then you give it. You give it a shot, right?
[00:09:49] A great starting point for building these custom tech solutions is literally thinking about what you hate doing and figuring and then figuring out a way to have the robots do it for you. And by figuring out a way, I mean, talking to Claude and being like, hey, I don't want to do this. I don't like doing this. What can you automate? What can. What can you do for me within this? Again, I never recommend you outsourcing the creative part of things, but the paper pushing, by all means, outsource that, the organizing of stuff. Outsource it so that you can have all of your brain left to do the creative stuff.
[00:10:24] In last week's episode, I talked about I. How I had Claude coat build out an automation for my podcast workflow, namely, uh, all the copy and pasting parts that I hate doing. I actually, fun fact, before I came on to record this, I did have some troubleshooting with that, but I was like, I know what's going on. I think this is why. And it's still faster than me going in and doing all the copy pasting myself. Even though there was, uh, you know, there was a little troubleshooting that was required, there was some fragility with this stuff. And I think that, you know, that's why I'm kind of like, hey, understand a little bit what's going on so that when it breaks, you're not just like, so frustrated and then you try to use like all of your tokens to try and troubleshoot this thing. Right? So, but what I was trying to get, the point I'm getting across there is that my, you know, first big build out was that automation, uh, for the, for the podcast workflow. Because I was like, I don't want to do this. I hate doing the, the copy and pasting. So this time, friends, I had Claude co build out a custom dashboard. And that's kind of all the rage right now. People. If you feel on threads and you're in that, uh, echo chamber, uh, it is like everyone showing their custom dashboards and then like people on them because they haven't like, deployed them to a. Somewhere that they can actually like, you know, that's live and they, they don't have any actual integrations. And it's like, dude, stop yucking people's yum and just teach them more. So I had Claude build this thing out. It's for my messaging, coaching clients. And I built it out, I had it built out because I needed an organizational solution that would allow me to have all of the things in one place without any extra or any ext. Like all these CRMs and things like that. You have so many other, so many moving parts, so many extra stuff, and you have to pay for them. I'm not paying for this thing. It's. It's free, right? I, I pay for Claude, but everything else, there's no cost to it.
[00:12:04] So my particular process for this was perhaps a little bit different than yours will be if and when you go to try and do that. And that's largely because I'm familiar with the frameworks that I wanted Claude to use and the da, you know, to build the dashboard. Um, FYI, A custom. A dashboard. This custom dashboard is simply a custom web app, which means it is web pages. That's all that it is. Files that get read and turned into web pages, right? They are live, they are deployed, and it is. They have URLs. I put it behind a. An authorization, right? So there's a login for it, but it is just web pages as what's getting built.
[00:12:41] I knew that I would also need a database for this because I want this. It's for clients and they're going to have things attached to each client and that requires the information to be stored somewhere. That's a database. I knew which provider I wanted to use for that database and I knew which service I wanted to use to deploy the whole thing, right? And when I say deploy, that just means make it live on the Internet. Make these web pages live on the Internet so that I can access them from anywhere, right? So for the nerds out there who care, the tech stack that I used and that I will always use, that's what I like to use to build these kinds of things. The framework is next, uh, js. The database is Supabase and the deployment platform is Vercell.
[00:13:19] There are other options out there. Netlify or netlify, it's. I don't even have to pronounce it. That's another option for a deployment platform. Um, the big database, um, providers that we see out there, like Supabase is a big one because it's all in one and it allows for auth to be in there. Meaning if you want to have authorization for things.
[00:13:39] If you're just doing this yourself and you're, you don't need, like, you're not having multiple people and you need to protect each, each, you know, line and things like that. When, um, I say each line, I mean each line in the database. Then you don't need to use something like that. But it's free, has. It does have a free tier. Uh, and that's what I learned with. So that's what I use. And it integrates really nicely with Vercel and Next js. And that's why I use it, right? They all just play really nicely together. But by all means, use what you want. I use them because like I said earlier, uh, when I first started learning this stuff, I took some courses and about Vibe coding and that's what they used. And so I use them and I still use them, right? For you use Claude. Tell Claude that what you want and what you're trying to do and it will make recommendations. Right. I think something to note there, I know I said that, I just said tell Claude, but you're going to be building this thing with Claude code, not Claude AI.
[00:14:35] You can Google.
[00:14:37] And, uh, this is what I want you to Google, Install Claude code desktop app and it will walk you through how to install it. And yes, that is the easiest way to find out how to install it is to just Google it. You'd think they'd like, make it more front and center on Claude and they don't. Um, they kind of scare people away from it. I think they kind of.
[00:14:57] And maybe I'll do an episode about this because I do find it interesting. Um, they have three, it has three tiers, right? We have Claude AI, we have Claude co work and we have Claude code. And Claude cowork. Is this like Claude code for the average person? But I find that they are, that it is just becoming so functional. And Claude itself is Claude AI is becoming so functional that I, I, I wouldn't be surprised if that middle tier gets cannibalized and just gets eaten. Um, but I'm interested to see what happens with that. Um, but you'll be using cloud code to build this thing. And so easiest way to do to like install it and understand that is to install the desktop app. Before it was only in terminal. They've made it so much again. Things are just changing and the accessibility is changing so quickly. Uh, so just Google, Install Claude code desktop app and it'll walk you through it. But, uh, in building these custom tech solutions, as is the case with coming up with any solution, the more familiar you are with the problem, the better the solution will be. So to that end, in my humble opinion, it's advisable to wait until you have some reps doing that thing that you want a solution for or executing that task, ask so that you can discuss it with Claude and then, you know, you can discuss with Claude what you actually want to build this way. I'm not just telling you, like, just go build something right now. Because you're like, well, I don't really know what I want and what I need. And like, you know, every single Vibe coding course, like, will have you build a Pomodoro timer and you're like, fine, I can like do that. But like, it's fine to do that, but it is, in my opinion, you're more invested and you care more when it's a problem that you have firsthand. You're like, dude, I want a solution for this. And I'm really familiar with it and I know what I want to happen with this, right? So just circling back a little bit there because I said you can talk to Claude to. About, you know, discussed with Claude what you want to build and then you have the planning session, right? The planning session is very important, right? The, the sitting there, going back and forth and being like, what do I want? How do I want this thing to work?
[00:16:58] What, uh, what. Just everything about it and to kind of get in the weeds here. You can have this conversation with Claude AI, but the actual planning that gets executed, an actual plan that gets executed, that will happen by via Claude code. And you have to do that planning portion inside of Claude code in what's called plan mode.
[00:17:21] Again, I know that if you haven't used cloud code, if you haven't used CLAUDE for desktop, you don't know what the I'm talking about. I know this. I just want you to have the exposure to. This is how I learned as well when I'm. I just, I watched a bunch of Claude videos and YouTube videos and I didn't know what the they were talking about. But when I went to use it, finally it made sense because of that exposure that I had before. I'm like, oh, that's what they're talking about. So if you're like, what in the world.
[00:17:51] I get it. There are. If and when you download CLAUDE for desktop or Claude code for desktop, you're going to see it's like, uh, a, it's an app and it has three little sections at the top like a toggle, and one is chat, one is cowork, and one is code. When you go to build this thing, you're actually going to be in code. I like to start in chat and just go back and forth with it. That's regular Claude, right? Chat is regular, regular cloud. The chat toggle. I just go back and forth with it and talk about the things that I want and then I have to start a new conversation in code. Nothing goes over or like, you know, copies over into Claude code. You can ask the chat toggle. So Claude AI. Hey, can you summarize what we just went over? And I'm going to go start a project in cloud code, but nothing. It doesn't like talk to each other, which is a little bit annoying. Um, and I think that at some point they'll change that, but it doesn't do that for now. So you can bring that conversation over via, you know, copy it, ask it to summarize it, and then bring it over and then you will actually do planning inside of cloud code. It will plan things out, it'll tell you the steps it wants to take. And then you have to authorize each of the steps.
[00:18:59] Uh, again, put in effort with this, Put effort into this and ask Claude to ask you questions. You know, all the episodes that I've done, even when we were talking about Chat GPT, I was just, uh, you know, always emphasizing that the better the input, the better the output. And so ask it questions and have it ask you questions. Right? Tell it to ask you questions. Tell it that you are completely new to this, you have no idea what you're doing. Ask for things that you might have missed but would be helpful. Ask it for things that you don't know to ask for, but would. Would improve the quality of the project. Ask about problems that could arise and how to prevent them.
[00:19:34] This actually, and you may not even change this because you're just like, oh, I did it, but I didn't really understand and I just experienced this. I saw a thing, you know, I was having the conversation with Claude and, and when I built out the workflow and I saw it mention something about basically, um, the version that it was, that it uses for that workflow, the version of Claude, it's like hard coded in, which means that if Claude updates, that it will break. And that's exactly what happened. Claude updated. And I went to run it and it was like, this is, I can't find Claude. And I was like, I think I know what happened. So even if you don't take the advice, at least you're exposed to it. And you're like, oh, wait, I think I know. And then you can fix it. All right?
[00:20:14] Ask Claude about anything you could possibly want this tech solution to do. The coolest thing with AI is that you don't have to settle for a quote, unquote, good enough. Right? Uh, at least not a night. At least not initially. Right. And especially when it comes to aesthetics or, you know, stylistic things. I did have an experience with the Dashboard project where I couldn't get an, you know, what I would consider a nice to have feature to connect. Uh, but that was fine because it wasn't an aesthetic thing. It was a. It was called an MCP server and would basically have allowed me to just talk to Claude and have Claude change things.
[00:20:48] Uh, not within the functionality of the Dashboard. Um, but if I wanted to, like, add this client and I could just message Claude and I couldn't get that to work, I'm okay with that. It's not the biggest deal. Everything else that I want, every single other thing that I want, stylistic button related actions that take place, Claude has made happen, Cloud code has made it happen. And I have been updating in this thing, uh, along the way. Right. So actually speaking of, speaking of connections, uh, for my custom dashboard, I wanted it to be able to connect to my scheduling software, Acuity, so that it would automatically pull clients from there. Um, and it would organize it by the specific service and it would pull over any corresponding dates. And I wanted it to be able to connect, also connect with Google Drive so that a new Google Drive folder would be created whenever someone booked and things like that are possible. I actually, just before hopping on here, was doing some troubleshooting because what's called a web hook wasn't working. Um, so it wasn't pulling them automatically. I had done like a hard import to start off, and so I was like, oh, it's working. But I realized that, no, it's not updating automatically. Um, I hadn't, like, I hadn't finished the second half of that connection, but went back and forth with Claude and it's all fixed.
[00:21:58] But, um, I want, what I want you to take away from that is that things like this are possible, right? But this connection that I'm talking about, this is where some of that, not some, a lot of that tech tenacity comes in because there are steps that you have to take and things that you have to do and copy and paste and like, there's a lot of copy and pasting and matching things. Um, and I think that's a good thing from a safety perspective. Uh, but again, Claude will hold your hand through this and you literally just copy and paste. You can, you can copy and paste in both ways. One, you can take a screenshot and then you drag that into the, into Claude and be like, hey, this is what I'm seeing. What do I do next? And it will walk you through it and then it will output the things that you need to copy and that you need to paste into the respective files and such so that things connect and things work.
[00:22:42] Building the custom dashboard, it did take me a couple of hours. It was not like a, you know, 30 minute thing.
[00:22:48] It took a couple of hours, but it's exactly what I need. And you know, I said two weeks last week, uh, that building out the, uh, the workflow, the automation for the podcast, that took seven hours. Absolutely.
[00:23:00] These things don't take like one second. But this dashboard, I literally use it multiple times a day every Day. And I continue to tweak it. And I can tweak it as things come up that, you know, I realized like, hey, it would better if this was like this, or it would be better if this did this. I know you have all experienced that with apps that you use, you can fix it. Now. That, to me is a super cool part about building your own custom tech solution. You can continue to change the, the, the tech as you need, and as what you need changes, that's amazing to me. You can continuously change it, update it, upgrade it, switch this, take away that thing, add that thing, make this thing look like that, move this thing over here.
[00:23:43] One, uh, of things I changed was just the size of it. I think one of the hallmark and one of the telltale signs that AIs made something is that the font is really small. And I'm like, this is like so hard to see. And it's also like, hard to click on, especially when I'm on the phone. So I was just like, I need to change the font on all this. Make it, make it so I can actually read it and. Or I want this, I want this entire line to be hyperlinked, not just this one little arrow at the end. Just little things like that that you're like, this would be easier for me. This is what I want.
[00:24:08] It will do it. As an aside, I know it doesn't my notes, but I do want to share it. When you're building these things out, you have to ask it to optimize, uh, it for mobile because it doesn't do that. The default is to make it for your desktop. And then when you go to look at it on your phone, you're like, jesus, this looks fucking terrible. So you also have to make sure that you, that you optimize it for mobile. Um, and that's been a cool journey as well. Like, as I was getting more into coding stuff and like learning how you do that, and it's very, it's simple actually do that. I have to do that. I sometimes play around with that stuff on my website, but it is a separate thing that you will have to ask it to do. All right.
[00:24:42] Um, but one of the things I wanted to highlight with this is like, yes, I'm so excited about it. I just, I'm always like, about expectation management and being real. And so, like, building this stuff takes time. And by time, I mean hours. Right before coding this, like I said, before recording this, like I said, I was troubleshooting the webhook thing. That's probably about 45 minutes, uh, and figuring out why things weren't showing the dashboard. And then I took another, I don't know, half an hour to figure out the podcast automation workflow. And m like, why isn't that working? Um, these things take time. It's time to build. And then there is the troubleshooting component, which is why for any of you that are out there and reading stuff, and it's like, SAS is dead. SaaS is a service as a solution. Software. Excuse me, software as a solution.
[00:25:19] Um, no, these things aren't dead because people don't want to do this themselves, right? They don't want to troubleshoot the shit themselves. They don't have to worry about maintaining it. But if you are willing to do that, sky's the limit. And there's a lot less to maintain because it's just you using it. It's just your desires, your wishes for this, right? It's not like everyone, a bunch of people using it, and it's broke for this person and this person wants it different.
[00:25:39] It's just you all, uh, right. And again, that, that troubleshooting largely looks like taking screenshots of things or copying outputs and being like, hey, it just shot this out to me. It's not working.
[00:25:51] Help. And then having lots of patience, right? So again, friends, no pressure to go and build anything. I just want you to realize that it is possible. And I truly, truly, truly believe that these personal custom tech solutions are the, you know, next big thing. And, and, and by next big thing, I mean that they're already here, people are already doing it. It's just that they're being, you know, it's siloed to the early adopters. But this is definitely going to be a thing. It's going to continue to be a thing, especially because it's just going to become easier to, to build these things out. Right? So building them. Right. Like I said, it's on. It's only going to become easier. And I, I really do hope that you take advantage of that and you solve your own problems in a way that is an absolute perfect fit. And, um, that's an exciting. Like, this is exactly the very thing that you need. You can do that, whatever it is, talk to Claude. There's probably a way to do it. All right, last things last and then we'll wrap this up. How I used AI this week. Each episode. If you're new here, you don't know. I share a quick example of how I used AI that week. Clearly, this whole episode is how I use AI this week building the custom dashboard. But something super cool that I did last week that I want to share is I had Claude build me a bomb ass custom Google sheet to give to the folks who attended the live event that I host with Lex for our lecture, My mastermind. So I had it make it a fillable Google sheet that I use as part of a drill for creating content. I, um, wasn't gonna have. I don't really like making sheets and, and worksheets. It's like just, I don't like doing it, I don't like using them, I don't like making them, but I do understand the utility and do I think people really like them.
[00:27:29] And so as, as um, sitting there and Lex was actually presenting, I had to build it in that time. It literally took it, it took like seven minutes to do it. So I was gonna worth noting, I was gonna have Cloud cowork do it, do this. Admittedly, I still don't really understand the utility of Cloud cowork. I understand Claude, I understand cloud code. Cloud cowork to me is in this really weird middle fuzzy space. But I know that it is good at um, Excel and like being in PowerPoint. So I was like, okay, cool. It can make this, this Excel spreadsheet, but it can do Excel and it can also do Google Google Sheets. And so I went in there to have it do it and it didn't work. It was just like, you know, basically the equivalent of the, the wheel of death just spinning. So I toggled over to Claude Chat. Uh, I know it sounds funny to say Claude Chat, but if you, once you go to the desktop app, you'll see there's three toggles at the top. Chat co worker and Claude. Excuse me, Chat co work and code. Uh, and so I, I toggled over to the chat section, um, which is just regular Claude. And I was like, yo, what's up with code? Is it broken? And it was like, yeah, it hasn't been working. Which is like, I think it's just lying and hallucinating. But either way, I told Claude what I wanted and it was just like, hey, I want to make a Google sheet that's fillable. Um, I want them to be able to do this. And actually I just uploaded my screen, uh, a, uh, screenshot of two pages.
[00:28:49] Two, uh, what are they called? Um, two slides from the presentation. And I said, I want you to make a, a, what is it? A Google sheet from this, from the information on this. And it did it. It was literally that Easy. And it stylized it in my. It made the font small. It always does. Um, that's easy to change.
[00:29:10] It locked the cells, like, incredible. I, uh, had to do anything. It was my brand, colors, and all I had to do was share it, right? All I had to do was share it with the attendees. And again, I made it. I built it, quote, unquote, in the time that, you know, while Lex was coaching. I simply told it what I wanted. I uploaded the screenshots, and it did it. There was a few changes that I did want after it made it, and I just typed the request in the chat, it updated it, and I had a fully functional Google Sheet. And, uh, that's fucking awesome. Awesome. So definitely give that a try if you need a Google sheet built out, because it's as simple as just telling Claude what you want.
[00:29:47] All right, that, my friends, is all for today. Hopefully you found this episode helpful. If you did consider sharing it with someone you know who is curious about the old AI. And don't forget, I have a companion newsletter, the Curious Companion, that drops every Thursday. That is basically the podcast episode in text format. So if you prefer to read or you just want a written record, join the newsletter fam. You can head to prompting curiosity.com um, forward/newsletter, or check out the link in the show notes. As always, endlessly, endlessly, one more time. Endlessly appreciative for every single one of you. Until we chat again next Thursday, stay curious.
[00:30:31] It.
