WEBVTT 00:00:00.000 --> 00:00:02.480 You know that feeling? You find this amazing 00:00:02.480 --> 00:00:06.259 AI coding tool, maybe something using GPT -5 00:00:06.259 --> 00:00:08.980 or Cloud Code Power, and you're excited, you 00:00:08.980 --> 00:00:11.619 start playing with it, and then boom, paywall. 00:00:11.679 --> 00:00:14.759 Or the, your free trial has ended message. It 00:00:14.759 --> 00:00:16.719 just stops you cold. Especially if you're just 00:00:16.719 --> 00:00:19.660 learning or tinkering on your own. Exactly. It's 00:00:19.660 --> 00:00:23.399 frustrating. But what if there was a way, like 00:00:23.399 --> 00:00:26.199 a clever workaround to keep using those really 00:00:26.199 --> 00:00:29.059 powerful tools? For free. Well, that's what we're 00:00:29.059 --> 00:00:30.899 diving into today. There's a guide out there, 00:00:30.920 --> 00:00:33.240 a really practical one, that shows how to do 00:00:33.240 --> 00:00:35.439 just that. Great. And specifically for Windows 00:00:35.439 --> 00:00:38.340 users who maybe aren't command line wizards. 00:00:38.679 --> 00:00:40.719 We're going to unpack the steps. Think of it 00:00:40.719 --> 00:00:42.560 as finding a sort of secret door. We'll talk 00:00:42.560 --> 00:00:45.380 about the tool itself, RoboDev. This kind of 00:00:45.380 --> 00:00:48.000 ingenious email trick. Ah, intriguing. How to 00:00:48.000 --> 00:00:50.679 set things up using that sometimes scary black 00:00:50.679 --> 00:00:53.200 window, the command prompt or PowerShell. We'll 00:00:53.200 --> 00:00:55.960 make it less scary. And the final piece for making 00:00:55.960 --> 00:00:58.560 it basically free forever. OK, let's start with 00:00:58.560 --> 00:01:01.500 that first piece, then. This RovoDev. What exactly 00:01:01.500 --> 00:01:05.480 is it? So, RovoDev, it's the core of this whole 00:01:05.480 --> 00:01:08.260 thing, right? But it's not just like another 00:01:08.260 --> 00:01:10.819 AI model itself. No, that's a common misconception. 00:01:10.920 --> 00:01:15.579 It's more like a smart broker. Or maybe an optimizer. 00:01:15.760 --> 00:01:18.040 A broker? How so? Well, think about all those 00:01:18.040 --> 00:01:22.280 powerful AI models out there. GBT, Claude, others. 00:01:22.849 --> 00:01:26.109 Many have free tiers or trial periods, maybe 00:01:26.109 --> 00:01:28.730 academic access. Right, the initial free credits 00:01:28.730 --> 00:01:31.569 you get. Exactly. RovoDev seems to access these 00:01:31.569 --> 00:01:34.670 models and cleverly pulls together those free 00:01:34.670 --> 00:01:37.129 usage limits from across the board. Ah, so it 00:01:37.129 --> 00:01:39.510 bundles the free initial tries from multiple 00:01:39.510 --> 00:01:41.980 sources? Precisely. It aggregates that initial 00:01:41.980 --> 00:01:44.299 free capacity into one service you can access. 00:01:44.659 --> 00:01:46.599 OK, so it's not just a wrapper. It's managing 00:01:46.599 --> 00:01:49.359 access to the free parts of other powerful models. 00:01:49.379 --> 00:01:51.280 That seems to be the mechanism, yeah, and makes 00:01:51.280 --> 00:01:53.900 efficient use of those trial windows. So if RoboDev 00:01:53.900 --> 00:01:56.640 is the broker pulling all this together, what's 00:01:56.640 --> 00:01:58.939 the single biggest win for someone trying to 00:01:58.939 --> 00:02:01.780 code with it? Continuous, zero -cost access to 00:02:01.780 --> 00:02:04.879 professional AI power. Simple as that. OK, continuous 00:02:04.879 --> 00:02:08.240 access sounds great. But trials end, right? RoboDev 00:02:08.240 --> 00:02:10.719 must have a limit, too. It does. Like any service 00:02:10.719 --> 00:02:13.800 offering a trial, eventually they'll ask for 00:02:13.800 --> 00:02:15.719 a payment to continue. That's where the next 00:02:15.719 --> 00:02:18.280 part comes in this email trick. The door key, 00:02:18.300 --> 00:02:20.800 as the guide calls it. Yeah. It relies on a funny 00:02:20.800 --> 00:02:23.060 thing about Gmail specifically. Let's say your 00:02:23.060 --> 00:02:26.439 email is JaneDoe at Gmail .com. OK. Gmail actually 00:02:26.439 --> 00:02:28.780 ignores any dots you put in the first part before 00:02:28.780 --> 00:02:32.229 the AVO at 2. So Jane .toe at Gmail .com. goes 00:02:32.229 --> 00:02:34.830 to the same inbox. Right, I knew that. J -A -N 00:02:34.830 --> 00:02:36.849 -E -D -D -O -E at gmail .com, too, probably. 00:02:36.990 --> 00:02:39.490 Exactly. All land in your single Jane Doe inbox. 00:02:40.210 --> 00:02:42.449 But, and here's the crucial part, many automated 00:02:42.449 --> 00:02:45.469 systems, like a signup form. Like RovoDev's signup. 00:02:45.590 --> 00:02:48.400 Precisely. They often see Jane Doe and Jane Dot 00:02:48.400 --> 00:02:51.419 Doe as two completely separate unique email addresses. 00:02:51.620 --> 00:02:53.479 Whoa, so you get the email in the same place, 00:02:53.500 --> 00:02:55.740 but Robodev thinks it's a brand new user signing 00:02:55.740 --> 00:02:58.479 up. That's the trick. Each variation with a dot 00:02:58.479 --> 00:03:01.259 gets you a fresh trial period, a new free window 00:03:01.259 --> 00:03:03.879 of usage. That's kind of brilliant. Exploiting 00:03:03.879 --> 00:03:06.879 a legacy feature. You know, I still wrestle with 00:03:06.879 --> 00:03:09.060 prompt drift myself sometimes, just keeping track 00:03:09.060 --> 00:03:11.780 of logins for different things. This trick feels 00:03:11.780 --> 00:03:15.189 genuinely useful, almost like a relief. It simplifies 00:03:15.189 --> 00:03:17.729 managing multiple identities for this purpose, 00:03:17.830 --> 00:03:19.810 definitely. But wait, this sounds almost like 00:03:19.810 --> 00:03:22.189 cheating the system. Why does it even work? Is 00:03:22.189 --> 00:03:24.750 it technically allowed? It works because the 00:03:24.750 --> 00:03:28.449 platform just sees slight email variations as 00:03:28.449 --> 00:03:31.969 new, unique users. It's leveraging email standards. 00:03:33.129 --> 00:03:35.370 Okay, so you've got your magic email alias ready. 00:03:35.909 --> 00:03:37.810 Now you need to connect your computer, your Windows 00:03:37.810 --> 00:03:40.860 machine, to this Rovo Dev account. Right. This 00:03:40.860 --> 00:03:43.379 is the setup part, the part involving towershell 00:03:43.379 --> 00:03:45.479 or the command prompt, the scary black window. 00:03:45.680 --> 00:03:48.479 Yeah. But honestly, the guide emphasizes this. 00:03:49.520 --> 00:03:51.219 You don't need to understand the commands deeply. 00:03:51.419 --> 00:03:53.800 It's mostly just copy and paste. OK, that's reassuring. 00:03:53.879 --> 00:03:56.360 So what's the process? First, you log into the 00:03:56.360 --> 00:03:58.479 RovaDiv website using one of your dot trick emails. 00:03:58.840 --> 00:04:01.139 Find the section for CLI setup, that's command 00:04:01.139 --> 00:04:04.060 line interface. CLI, OK. Select Windows. It'll 00:04:04.060 --> 00:04:06.439 give you a couple lines of code. And these lines. 00:04:06.729 --> 00:04:09.110 You open PowerShell on your computer. You can 00:04:09.110 --> 00:04:10.710 just search for it after hitting the Windows 00:04:10.710 --> 00:04:13.509 key. Then you copy the first line of code from 00:04:13.509 --> 00:04:15.990 the website, paste it into PowerShell, hit enter, 00:04:16.350 --> 00:04:19.550 then copy the next line, paste, enter. Just copy, 00:04:19.610 --> 00:04:22.949 paste, enter twice. Pretty much. That installs 00:04:22.949 --> 00:04:25.189 a little program, the Ackley tool, that lets 00:04:25.189 --> 00:04:27.509 your machine talk to Rovo Dev. How do I know 00:04:27.509 --> 00:04:29.850 it worked? There's a quick check. You type Ackley 00:04:29.850 --> 00:04:32.589 version into PowerShell and press enter. If you 00:04:32.589 --> 00:04:34.990 see some version numbers pop up, you're golden. 00:04:35.230 --> 00:04:38.399 It's installed. So CLI command line interface, 00:04:38.620 --> 00:04:41.040 can you give us the super simple definition? 00:04:41.120 --> 00:04:43.279 Sure. It's just a way to talk to your computer 00:04:43.279 --> 00:04:45.420 using text commands instead of clicking buttons. 00:04:45.740 --> 00:04:48.439 Direct instructions. OK. Now, for someone who 00:04:48.439 --> 00:04:50.620 is a bit nervous about this, how important is 00:04:50.620 --> 00:04:53.519 it to actually understand what those copy pasted 00:04:53.519 --> 00:04:56.259 commands are doing? Honestly, for this process, 00:04:56.740 --> 00:04:59.319 understanding isn't necessary. Simple, precise 00:04:59.319 --> 00:05:01.660 execution of the steps is the key. All right. 00:05:01.660 --> 00:05:03.560 So the software is installed on my Windows machine. 00:05:03.879 --> 00:05:07.610 We've built the... Airport, so to speak. Now 00:05:07.610 --> 00:05:09.509 we need to connect it to the control tower, our 00:05:09.509 --> 00:05:12.370 RovoDev account. Exactly. And for that secure 00:05:12.370 --> 00:05:15.730 connection, you need a secret key. It's called 00:05:15.730 --> 00:05:19.550 an API token. API token. Sounds important. It 00:05:19.550 --> 00:05:22.750 is. Think of it like a digital passport or a 00:05:22.750 --> 00:05:25.310 super secure password specifically for this connection. 00:05:25.829 --> 00:05:27.769 It proves that commands coming from your computer 00:05:27.769 --> 00:05:30.670 are really you. OK, so how do I get this passport? 00:05:30.870 --> 00:05:33.339 You head back to the RovoDev website. still logged 00:05:33.339 --> 00:05:36.120 in. There should be an option to generate an 00:05:36.120 --> 00:05:38.540 API token. Generate, okay. You might need to 00:05:38.540 --> 00:05:40.500 verify it. Maybe they send a code to your email. 00:05:41.019 --> 00:05:42.600 You give the token a name. Something like my 00:05:42.600 --> 00:05:45.560 windows key is fine. Makes sense. Then, crucially, 00:05:46.180 --> 00:05:48.680 select an expiration date. The guide suggests 00:05:48.680 --> 00:05:50.920 picking one really far in the future, like the 00:05:50.920 --> 00:05:53.220 maximum allowed. To make it last longer. Right. 00:05:53.420 --> 00:05:55.660 Then you hit generate and it gives you this really 00:05:55.660 --> 00:05:58.389 long string of random letters and numbers. That's 00:05:58.389 --> 00:06:01.589 your token, your key. Wow, okay. So that long 00:06:01.589 --> 00:06:03.709 string is the key. That's it. Keep us safe for 00:06:03.709 --> 00:06:06.550 the next step. Essentially, the token is an authenticated 00:06:06.550 --> 00:06:08.930 identity used for secure communication between 00:06:08.930 --> 00:06:12.730 your PC and their service. Got it. Now, you said 00:06:12.730 --> 00:06:15.430 it's like a passport, super secure. If this key 00:06:15.430 --> 00:06:18.350 is so long and complex, what's the actual risk 00:06:18.350 --> 00:06:21.029 if, say, I accidentally posted it somewhere or 00:06:21.029 --> 00:06:24.750 someone got it? Big risk. It allows others to 00:06:24.750 --> 00:06:27.500 act as you. using your Rovodev account resources, 00:06:27.920 --> 00:06:30.220 like giving someone your house keys. Okay, you 00:06:30.220 --> 00:06:32.800 have the key. The final step is to actually use 00:06:32.800 --> 00:06:35.360 it to log in from your computer from PowerShell. 00:06:35.560 --> 00:06:37.079 All right, connecting the dots. How do we do 00:06:37.079 --> 00:06:39.680 that? Back in your PowerShell window, there are 00:06:39.680 --> 00:06:42.040 two main commands. First, the guide recommends 00:06:42.040 --> 00:06:45.420 typing ACLU Rovodev off logout and pressing enter. 00:06:45.720 --> 00:06:47.800 Log out. But I haven't logged in yet from here, 00:06:47.860 --> 00:06:49.720 have I? Probably not, but it's a safety measure. 00:06:50.009 --> 00:06:52.089 Just make sure any old credentials or attempts 00:06:52.089 --> 00:06:54.449 are completely cleared out. Ensures a clean slate. 00:06:54.829 --> 00:06:57.350 Okay, good practice. acly -rovadev -off -logout. 00:06:57.529 --> 00:07:00.750 Then what? Then the main command. acly -rovadev 00:07:00.750 --> 00:07:03.610 -off -login. Press enter. acly -rovadev -off 00:07:03.610 --> 00:07:05.269 -login. Got it. Now, it's going to ask you for 00:07:05.269 --> 00:07:07.689 two things. First, the specific email address 00:07:07.689 --> 00:07:09.689 you used to sign up for this particular Rovadev 00:07:09.689 --> 00:07:12.149 account. Ah, so the one with the specific dots 00:07:12.149 --> 00:07:15.370 like j .anydo at gmail .com? Exactly that one. 00:07:15.509 --> 00:07:18.509 Type it in. Press enter. Then it'll ask for the 00:07:18.509 --> 00:07:20.889 API token. And that's where I paste that super 00:07:20.889 --> 00:07:23.089 long string of letters and numbers I just generated. 00:07:23.509 --> 00:07:26.509 Yep. Paste it in carefully. Press Enter one last 00:07:26.509 --> 00:07:29.750 time. And... Fingers crossed. If everything worked, 00:07:29.870 --> 00:07:32.730 you should see a beautiful message. Authentication 00:07:32.730 --> 00:07:36.730 successful. Nice. Okay, so that confirms the 00:07:36.730 --> 00:07:39.069 link is made. My computer can now talk securely 00:07:39.069 --> 00:07:42.649 to the RovoDev AI. You got it. Local machine 00:07:42.649 --> 00:07:45.769 connected to the cloud AI. That whole API key 00:07:45.769 --> 00:07:48.230 thing felt technical. But breaking it down... 00:07:48.459 --> 00:07:50.839 Install the local tool, go get the key from the 00:07:50.839 --> 00:07:53.180 website, come back and use the key to log in 00:07:53.180 --> 00:07:55.899 via Power Shaw. That's the essence of it. Just 00:07:55.899 --> 00:07:58.699 quickly back to that logout command. Eclirova 00:07:58.699 --> 00:08:01.740 Dev Auth Logout. Why is that recommended, even 00:08:01.740 --> 00:08:03.639 if I'm pretty sure I've never logged in before 00:08:03.639 --> 00:08:05.939 on this machine? It just ensures a clean slate, 00:08:06.300 --> 00:08:08.459 preventing any weird authentication conflicts 00:08:08.459 --> 00:08:11.540 or errors from previous attempts or, you know, 00:08:11.740 --> 00:08:14.220 leftover data. Mid -roll sponsor, Redplace Holder. 00:08:14.319 --> 00:08:16.939 Okay, we did the setup, we authenticated. Now 00:08:16.939 --> 00:08:19.279 for the fun part, right? Actually building something 00:08:19.279 --> 00:08:23.040 with this AI. Exactly. The payoff. First, you 00:08:23.040 --> 00:08:26.120 need a place for the AI to put the code it generates. 00:08:26.759 --> 00:08:28.920 So in PowerShell, you'll want to navigate to 00:08:28.920 --> 00:08:31.240 a specific folder. How do you do that? Create 00:08:31.240 --> 00:08:33.259 a new folder somewhere easy to find, maybe on 00:08:33.259 --> 00:08:35.200 your desktop, call it like My Project or something. 00:08:35.820 --> 00:08:38.360 Then use the CD command in PowerShell that means 00:08:38.360 --> 00:08:42.039 change directory. CD. An easy trick is to type 00:08:42.039 --> 00:08:45.559 CD, then a space, and then just drag the folder 00:08:45.559 --> 00:08:48.259 icon from your desktop right into the PowerShell 00:08:48.259 --> 00:08:50.639 window. It pastes the full path automatically. 00:08:50.899 --> 00:08:53.379 Hit enter. Oh, neat trick. Okay, so now PowerShell 00:08:53.379 --> 00:08:55.799 is inside my project folder. Correct. Now you 00:08:55.799 --> 00:08:58.580 tell the AI to start working. The command is 00:08:58.580 --> 00:09:01.480 ocli -rovodev -run. ocli -rovodev -run, that 00:09:01.480 --> 00:09:03.879 kicks it off. It does, but here's a really important 00:09:03.879 --> 00:09:07.080 tip from the guide, a real time saver. Immediately 00:09:07.080 --> 00:09:10.909 after run, Type YOLO. YOLO, like you only live 00:09:10.909 --> 00:09:13.730 once. Yeah, yeah, basically. It tells the AI, 00:09:13.990 --> 00:09:16.289 look, I trust you. Just execute the plan I give 00:09:16.289 --> 00:09:19.009 you. Don't keep stopping to ask me for confirmation 00:09:19.009 --> 00:09:21.389 on every little subtask. Ah, so it just goes 00:09:21.389 --> 00:09:24.049 for it. Makes it faster. Much faster. Otherwise, 00:09:24.070 --> 00:09:26.470 it can be quite chatty. Asking, should I create 00:09:26.470 --> 00:09:29.029 this file? Should I install this package? YOLO 00:09:29.029 --> 00:09:32.029 skips all that. Got it. So Akali Rovodev, run 00:09:32.029 --> 00:09:34.570 YOLO. And then I tell it what to build. Exactly. 00:09:34.590 --> 00:09:36.899 And this is where you need to be specific. Really 00:09:36.899 --> 00:09:38.799 specific. You can't just say, make me a website. 00:09:39.159 --> 00:09:41.580 Right. The examples in the guide were quite detailed, 00:09:41.620 --> 00:09:44.419 like the coffee shop one. It wasn't just make 00:09:44.419 --> 00:09:47.620 a coffee shop site. It was create a React website 00:09:47.620 --> 00:09:50.220 for a coffee shop called Morning Coffee. And 00:09:50.220 --> 00:09:53.039 it specified three distinct sections, home page, 00:09:53.240 --> 00:09:56.039 menu, address. And even details on the menu. 00:09:56.139 --> 00:09:58.799 Specific items and prices. Right. And the colors, 00:09:58.919 --> 00:10:01.440 brown and beige. Exactly. That level of detail 00:10:01.440 --> 00:10:04.299 is key. Or the other example, build an HTML JavaScript 00:10:04.299 --> 00:10:07.450 tool to calculate age. Again, specifying the 00:10:07.450 --> 00:10:09.710 input box, the button, the function name, the 00:10:09.710 --> 00:10:11.330 more constraints you give it. The better the 00:10:11.330 --> 00:10:13.250 result. The more accurate and closer to what 00:10:13.250 --> 00:10:15.649 you actually want. Yeah. Whoa. Just thinking 00:10:15.649 --> 00:10:18.830 about that, you describe the pieces, the look, 00:10:18.929 --> 00:10:21.830 the function, and it just writes the code, installs 00:10:21.830 --> 00:10:24.370 what's needed, and makes a working thing. That's 00:10:24.370 --> 00:10:27.669 pretty amazing. Scaling that idea. Wow. It really 00:10:27.669 --> 00:10:30.950 is a leap from just text description to functional 00:10:30.950 --> 00:10:33.409 software running locally. Speaking of which, 00:10:34.090 --> 00:10:37.179 how do you see the result? Ah, yeah. The guide 00:10:37.179 --> 00:10:39.440 mentioned when the AI finishes, it usually gives 00:10:39.440 --> 00:10:41.799 you a web address in the PowerShell window, something 00:10:41.799 --> 00:10:44.399 like localhost .300. That's the typical one. 00:10:44.440 --> 00:10:46.379 You just copy that address, paste it into your 00:10:46.379 --> 00:10:49.000 normal web browser. And the website or tool I 00:10:49.000 --> 00:10:52.580 asked for just appears working. Should do. Running 00:10:52.580 --> 00:10:54.759 right there in your machine. OK, so back to the 00:10:54.759 --> 00:10:58.360 specificity thing. How is asking this AI for 00:10:58.360 --> 00:11:01.620 code different from asking, say, chat GPT just 00:11:01.620 --> 00:11:04.039 to write some text? Why so much detail needed? 00:11:04.250 --> 00:11:07.490 because code has to be precise. Extremely detailed 00:11:07.490 --> 00:11:10.149 instructions minimize ambiguity and dramatically 00:11:10.149 --> 00:11:12.230 improve the accuracy and functionality of the 00:11:12.230 --> 00:11:15.669 final code. Less room for error. Now, we mentioned 00:11:15.669 --> 00:11:18.590 that API token, that key, has an expiration date, 00:11:18.929 --> 00:11:21.590 even if you set it far in the future. And the 00:11:21.590 --> 00:11:23.690 trial access itself is ultimately time limited. 00:11:23.870 --> 00:11:26.169 Even with a dot trick generating new accounts, 00:11:26.649 --> 00:11:28.649 things will eventually expire. Right. So what 00:11:28.649 --> 00:11:30.690 happens when I'm torting along and suddenly... 00:11:30.750 --> 00:11:34.289 it stops working. My token expired or maybe Rovo 00:11:34.289 --> 00:11:36.850 Dev used up its free tier for that model. Okay, 00:11:36.850 --> 00:11:38.850 two main scenarios and solutions here. Scenario 00:11:38.850 --> 00:11:42.350 one, your API token expired, but the underlying 00:11:42.350 --> 00:11:44.690 Rovo Dev account might still have trial time 00:11:44.690 --> 00:11:46.889 left. Okay, what do we do then? Simple. Yeah. 00:11:46.909 --> 00:11:49.190 Just repeat the process of generating a new API 00:11:49.190 --> 00:11:51.690 token from the Rovo Dev website. Get that new 00:11:51.690 --> 00:11:54.970 long string. The same steps as before. Generate, 00:11:55.190 --> 00:11:58.210 name it, set expiration, copy the key. Exactly. 00:11:58.529 --> 00:12:01.629 Then go back to PowerShell. Do the aclyrovadev 00:12:01.629 --> 00:12:04.090 off logout command again just to be safe. Clean 00:12:04.090 --> 00:12:06.970 slate. And then aclyrovadev off login. Provide 00:12:06.970 --> 00:12:10.129 your same dot trick email, but this time, paste 00:12:10.129 --> 00:12:12.970 in the new API token you just generated. Ah, 00:12:12.970 --> 00:12:14.850 so just refresh the key. That seems easy enough. 00:12:15.009 --> 00:12:18.110 It usually is. That's scenario two. Maybe you 00:12:18.110 --> 00:12:20.610 can't generate a new token or the entire account 00:12:20.610 --> 00:12:22.690 seems blocked or out of his free trial time. 00:12:22.750 --> 00:12:25.250 OK, what now? Is it game over? Not necessarily. 00:12:25.330 --> 00:12:27.190 This is where you loop back to the original tricks, 00:12:27.289 --> 00:12:30.710 the gmail .alias. Just make a brand new Rovo 00:12:30.710 --> 00:12:33.230 dev account using a different .placement in my 00:12:33.230 --> 00:12:36.210 email. Like jad .nito at gmail .com this time. 00:12:36.590 --> 00:12:38.909 Precisely. Sign up fresh. It takes, what, maybe 00:12:38.909 --> 00:12:41.610 two minutes? Then you just run through the initial 00:12:41.610 --> 00:12:44.830 CLI setup and token generation for that new account. 00:12:45.350 --> 00:12:48.450 Huh. So the cycle repeats. Either refresh the 00:12:48.450 --> 00:12:51.169 key or, if needed, refresh the whole account 00:12:51.169 --> 00:12:53.629 with a new email alias. That's the sustainability 00:12:53.629 --> 00:12:55.850 loop described in the guide. OK. But let's be 00:12:55.850 --> 00:12:58.909 real. constantly generating new tokens or new 00:12:58.909 --> 00:13:02.509 accounts, is that actually viable for like a 00:13:02.509 --> 00:13:05.509 serious long term learning project? Does it scale? 00:13:06.129 --> 00:13:07.870 It's definitely sustainable for casual learning 00:13:07.870 --> 00:13:10.190 and short projects, maybe rapid prototyping. 00:13:10.539 --> 00:13:13.080 Precisely because the setup or reset time is 00:13:13.080 --> 00:13:15.259 so quick, just a couple of minutes. OK, let's 00:13:15.259 --> 00:13:17.080 try and wrap this all together then. The big 00:13:17.080 --> 00:13:19.940 idea here seems to be using Rovo Dev not just 00:13:19.940 --> 00:13:23.559 as an AI tool itself, but as this clever aggregator 00:13:23.559 --> 00:13:25.919 almost. Yeah, a sophisticated interface that 00:13:25.919 --> 00:13:28.559 optimizes and bundles the free trial or initial 00:13:28.559 --> 00:13:31.879 usage tiers from multiple other powerful AI coding 00:13:31.879 --> 00:13:34.120 models. And then combining that with this simple 00:13:34.120 --> 00:13:36.559 almost overlooked Gmail dot trick. Which allows 00:13:36.559 --> 00:13:39.000 you to effectively create new unique user accounts 00:13:39.000 --> 00:13:41.259 endlessly. all feeding into your single Gmail 00:13:41.259 --> 00:13:44.480 inbox. Giving you continuous, essentially zero 00:13:44.480 --> 00:13:47.700 -cost access to AI coding power that would normally 00:13:47.700 --> 00:13:51.840 be behind a pretty hefty paywall. Exactly. It 00:13:51.840 --> 00:13:55.220 democratizes access in a way. The guide really 00:13:55.220 --> 00:13:57.639 highlights that you don't need a huge budget 00:13:57.639 --> 00:14:01.139 or deep, deep technical skills to start building 00:14:01.139 --> 00:14:04.340 real things now. It removes that barrier to entry, 00:14:04.519 --> 00:14:06.940 the paywall stopping you from just trying things 00:14:06.940 --> 00:14:09.419 out and learning by doing. Knowledge is power, 00:14:09.419 --> 00:14:12.379 as they say. And this guide provides the knowledge 00:14:12.379 --> 00:14:14.820 to unlock that capability. It proves you can 00:14:14.820 --> 00:14:16.960 get your hands dirty with cutting edge AI without 00:14:16.960 --> 00:14:19.440 needing enterprise resources. So we really encourage 00:14:19.440 --> 00:14:21.580 you, if you're listening and curious, give these 00:14:21.580 --> 00:14:23.519 steps a try. What have you got to lose? It's 00:14:23.519 --> 00:14:25.779 free. Mistakes are just part of the learning 00:14:25.779 --> 00:14:28.120 process here. Absolutely. And maybe it sparks 00:14:28.120 --> 00:14:30.200 something, which leads me to a final thought 00:14:30.200 --> 00:14:32.419 for you to consider building on all this. If 00:14:32.419 --> 00:14:34.899 you could use this method, this AI assistant, 00:14:35.259 --> 00:14:38.600 to build one simple tool in just minutes by describing 00:14:38.600 --> 00:14:41.820 it, what tiny, maybe repetitive, maybe annoying 00:14:41.820 --> 00:14:44.139 task in your daily life would you automate first? 00:14:44.840 --> 00:14:46.679 Interesting question to ponder. Something to 00:14:46.679 --> 00:14:48.519 think about. Thanks for diving deep with us today. 00:14:48.980 --> 00:14:51.100 Always a pleasure. We'll catch you on the next 00:14:51.100 --> 00:14:51.799 deep dive.