WEBVTT 00:00:00.000 --> 00:00:02.899 Picture this scenario for a second. You are deep 00:00:02.899 --> 00:00:05.299 in the zone today. You're just typing rapidly 00:00:05.299 --> 00:00:07.299 on your keyboard. Yeah, you're using a tool you 00:00:07.299 --> 00:00:09.460 already paid good money for. Right. You type 00:00:09.460 --> 00:00:12.939 exactly five prompts into the chat box. Suddenly, 00:00:13.119 --> 00:00:15.419 a warning flashes across your computer screen. 00:00:15.859 --> 00:00:19.140 Your account just dropped below 25 % capacity. 00:00:19.320 --> 00:00:21.559 Oh, wow. And it only took 30 minutes of your 00:00:21.559 --> 00:00:25.079 time. Exactly. Hitting a paywall on your own 00:00:25.079 --> 00:00:28.820 paid plan. That's a visceral, incredibly frustrating 00:00:28.820 --> 00:00:31.280 feeling to experience. It's incredibly jarring. 00:00:31.679 --> 00:00:33.579 You expect the system to just work smoothly. 00:00:34.240 --> 00:00:37.000 You're paying for seamless access, after all. 00:00:37.520 --> 00:00:40.740 But those invisible walls are closing in rapidly. 00:00:41.179 --> 00:00:42.899 Welcome to our deep dive today. We're really 00:00:42.899 --> 00:00:44.700 glad you're joining us. Today, our mission is 00:00:44.700 --> 00:00:47.420 unpacking this exact frustration. Yeah, we're 00:00:47.420 --> 00:00:50.520 exploring why Gemini usage limits vanish so suddenly. 00:00:50.700 --> 00:00:53.159 Right. We'll also figure out how to optimize 00:00:53.159 --> 00:00:56.070 your workflows. We really want to help you prevent 00:00:56.070 --> 00:00:58.829 those sudden account freezes. It's a vital skill 00:00:58.829 --> 00:01:00.450 for modern work. You kind of have to understand 00:01:00.450 --> 00:01:02.509 the boundaries of your tools. We're going to 00:01:02.509 --> 00:01:05.569 cover the new compute power paradigm first. Then 00:01:05.569 --> 00:01:07.510 we'll walk through the golden rules for daily 00:01:07.510 --> 00:01:10.870 usage. And finally, we'll reveal the hidden tricks 00:01:10.870 --> 00:01:14.489 that advanced users rely on. Exactly. These tricks 00:01:14.489 --> 00:01:16.849 completely save you when the battery hits zero. 00:01:17.010 --> 00:01:18.810 We definitely have a lot of ground to cover. 00:01:19.069 --> 00:01:22.489 So before we can optimize the AI, we need context. 00:01:22.730 --> 00:01:24.989 We need to understand how Google changed the 00:01:24.989 --> 00:01:28.049 rules recently. Right. It's a massive paradigm 00:01:28.049 --> 00:01:30.569 shift in how limits actually work. It really 00:01:30.569 --> 00:01:33.129 is a totally different game now. Google no longer 00:01:33.129 --> 00:01:35.590 counts the flat number of messages you send. 00:01:35.790 --> 00:01:38.010 No. They measure the underlying complexity of 00:01:38.010 --> 00:01:40.629 your prompt instead. They track the actual computing 00:01:40.629 --> 00:01:43.549 power used for every single request. Let's define 00:01:43.549 --> 00:01:46.189 that jargon quickly for clarity. Compute power 00:01:46.189 --> 00:01:48.390 is the total machine energy needed to finish 00:01:48.390 --> 00:01:51.069 tasks. Right. It helps to think about your smartphone 00:01:51.069 --> 00:01:54.269 battery. Reading basic text messages sips your 00:01:54.269 --> 00:01:57.109 battery power very slowly. You can check the 00:01:57.109 --> 00:01:59.290 weather app all day long without worry. Exactly. 00:01:59.890 --> 00:02:02.549 But playing heavy, graphic -intense mobile games 00:02:02.549 --> 00:02:05.250 drains it very rapidly. Uploading a 50 -page 00:02:05.250 --> 00:02:07.549 financial document for a summary is that heavy 00:02:07.549 --> 00:02:10.810 game. Yeah, it really is. The AI handles your 00:02:10.810 --> 00:02:13.729 request the exact same way. It allocates its 00:02:13.729 --> 00:02:16.889 processing power based purely on task difficulty. 00:02:17.009 --> 00:02:20.490 Yeah. In the past, 10 short messages cost the 00:02:20.490 --> 00:02:23.569 exact same as 10 long ones. Right. That old rule 00:02:23.569 --> 00:02:26.310 is completely gone from the system now. The AI 00:02:26.310 --> 00:02:29.189 specifically looks at the energy it has to spend. 00:02:29.629 --> 00:02:31.710 It makes sense when you think about server costs. 00:02:32.550 --> 00:02:35.370 But I still wrestle with prompt drift myself. 00:02:35.930 --> 00:02:38.449 Beat. I just keep asking for more complex things 00:02:38.449 --> 00:02:41.969 without realizing the cost. Oh, I all fall into 00:02:41.969 --> 00:02:43.889 that trap pretty easily. You just assume the 00:02:43.889 --> 00:02:46.330 machine can handle everything instantly. Right. 00:02:46.409 --> 00:02:48.550 We forget there are physical servers burning 00:02:48.550 --> 00:02:50.550 electricity somewhere. That's why you need to 00:02:50.550 --> 00:02:52.289 constantly check your dashboard. You need to 00:02:52.289 --> 00:02:54.490 know exactly where your capacity stands. Exactly. 00:02:54.530 --> 00:02:56.909 If you open your app right now, look at the bottom 00:02:56.909 --> 00:02:59.590 left corner. You'll see a small gear icon sitting 00:02:59.590 --> 00:03:01.530 there quietly. You just click on that settings 00:03:01.530 --> 00:03:04.509 menu to open it up. And then you click directly 00:03:04.509 --> 00:03:07.669 on usage limits. This specific page is very important 00:03:07.669 --> 00:03:09.550 for your daily workflow. You really should make 00:03:09.550 --> 00:03:12.689 it a habit to check it constantly. Yeah. On this 00:03:12.689 --> 00:03:15.349 dashboard, you'll clearly see two tracking bars. 00:03:15.550 --> 00:03:18.469 One bar clearly shows your current daily usage 00:03:18.469 --> 00:03:21.889 limit. The other bar displays your overall weekly 00:03:21.889 --> 00:03:24.789 limit capacity. And as you ask questions, these 00:03:24.789 --> 00:03:28.289 visual numbers go up rapidly. If any bar reaches 00:03:28.289 --> 00:03:31.849 100%, you lose access entirely. The system will 00:03:31.849 --> 00:03:34.840 simply force you to wait it out. The reset schedule 00:03:34.840 --> 00:03:37.319 is a very important detail to understand here. 00:03:37.500 --> 00:03:40.139 Right. The current usage bar resets itself every 00:03:40.139 --> 00:03:42.340 five hours. If you drain it completely in the 00:03:42.340 --> 00:03:45.300 early morning, you're okay. You can easily start 00:03:45.300 --> 00:03:47.300 working again in the late afternoon. But that 00:03:47.300 --> 00:03:50.139 wantly limit is much less forgiving to sex silence. 00:03:50.659 --> 00:03:53.180 How punishing is it if you actually max out that 00:03:53.180 --> 00:03:55.659 weekly limit bar? Oh, it's brutal. You're locked 00:03:55.659 --> 00:03:58.620 out of heavy tools for days. You literally just 00:03:58.620 --> 00:04:00.960 have to sit and wait for the weekly reset. So 00:04:00.960 --> 00:04:03.719 five hours for daily resets or agonizing days 00:04:03.719 --> 00:04:06.199 if the weekly breaks. Exactly. It really forces 00:04:06.199 --> 00:04:08.400 you to be highly strategic. Now we know exactly 00:04:08.400 --> 00:04:10.919 why the battery drains so fast. Let's look at 00:04:10.919 --> 00:04:13.159 what specific tasks are draining it. Yeah, we 00:04:13.159 --> 00:04:15.159 need to configure your settings to stop the bleeding 00:04:15.159 --> 00:04:17.870 today. The biggest danger is accidentally turning 00:04:17.870 --> 00:04:20.649 on extended thinking. Oh, definitely. Let's clearly 00:04:20.649 --> 00:04:23.750 define that feature for everyone listening. The 00:04:23.750 --> 00:04:26.610 AI spends extra time checking its own steps. 00:04:26.930 --> 00:04:29.129 Right. And it creates invisible mini prompts 00:04:29.129 --> 00:04:31.810 in the background. It basically argues with itself 00:04:31.810 --> 00:04:34.629 to verify its own logic. It's very good at solving 00:04:34.629 --> 00:04:37.910 incredibly difficult math problems. True. But 00:04:37.910 --> 00:04:40.730 it eats your digital resources incredibly fast. 00:04:41.069 --> 00:04:44.389 Just one wrong click here wipes out 10 % instantly. 00:04:44.649 --> 00:04:47.490 That is a massive penalty for a simple mistake. 00:04:48.170 --> 00:04:50.670 Beat. You really want to rely on the safe default 00:04:50.670 --> 00:04:53.850 instead. Always use Gemini Flash combined with 00:04:53.850 --> 00:04:56.529 standard thinking for daily tasks. Gemini Flash 00:04:56.529 --> 00:04:59.129 is a lighter model explicitly designed for speed. 00:04:59.410 --> 00:05:01.629 Yeah, this setting handles quick questions and 00:05:01.629 --> 00:05:04.550 short summaries perfectly. It replies fast and 00:05:04.550 --> 00:05:06.920 keeps your limit very safe overall. Let's talk 00:05:06.920 --> 00:05:09.399 about the specific types of media requests. This 00:05:09.399 --> 00:05:12.079 is where the resource strain gets highly variable. 00:05:12.459 --> 00:05:14.379 Generating standard text is usually your safest 00:05:14.379 --> 00:05:17.399 bet by far. Text data is processed very easily 00:05:17.399 --> 00:05:19.899 and quickly by the system. It's the native language 00:05:19.899 --> 00:05:22.680 of the large language model. Exactly. It usually 00:05:22.680 --> 00:05:24.720 burns less than 1 % of your limit. You could 00:05:24.720 --> 00:05:27.420 prompt an expert copywriter persona, for example. 00:05:27.860 --> 00:05:31.279 You ask for 15 AI productivity email subject 00:05:31.279 --> 00:05:34.480 lines. You specify keeping them strictly under 00:05:34.480 --> 00:05:37.819 33 characters long. The system creates that text 00:05:37.819 --> 00:05:41.199 incredibly fast for you. And your limit bar will 00:05:41.199 --> 00:05:44.120 barely move at all. But things change rapidly 00:05:44.120 --> 00:05:46.759 when we shift over to audio. Creating music is 00:05:46.759 --> 00:05:49.459 fun, but highly dangerous for your capacity. 00:05:49.540 --> 00:05:52.199 Oh yeah. Very dangerous. Why does audio hit the 00:05:52.199 --> 00:05:54.259 system so much harder than text? Well, when you 00:05:54.259 --> 00:05:57.000 ask for a song, it creates complex waveforms. 00:05:57.040 --> 00:05:59.620 It has to render high frequency data across time. 00:05:59.759 --> 00:06:02.540 I see. This requires huge computer power from 00:06:02.540 --> 00:06:04.980 the underlying system infrastructure. If you 00:06:04.980 --> 00:06:07.500 use the free plan, it's incredibly expensive. 00:06:07.620 --> 00:06:10.860 Wow. Just one single song eats 13 % of your limit. 00:06:11.040 --> 00:06:13.699 That's over a tenth of your battery for one track. 00:06:13.860 --> 00:06:16.060 Yeah. You should just use the MusicFX tool in 00:06:16.060 --> 00:06:18.920 Google Labs instead. Right. It focuses entirely 00:06:18.920 --> 00:06:21.740 on making music for your creative projects. It 00:06:21.740 --> 00:06:23.600 has an independent credit system to keep your 00:06:23.600 --> 00:06:25.860 main battery safe. That's a great workaround. 00:06:26.779 --> 00:06:29.399 Now, we also need to talk about coding. Writing 00:06:29.399 --> 00:06:32.120 code is incredibly costly compared to standard 00:06:32.120 --> 00:06:34.930 text. Wait, isn't code just text at the end of 00:06:34.930 --> 00:06:37.029 the day? Why does it drain the main battery so 00:06:37.029 --> 00:06:39.629 violently? Because writing functional code isn't 00:06:39.629 --> 00:06:42.250 just simple text generation. The tool must understand 00:06:42.250 --> 00:06:45.769 strict logic and complex structural rules. Right. 00:06:46.009 --> 00:06:48.490 If it messes up a normal word, you still understand 00:06:48.490 --> 00:06:51.759 it. If it misses a semicolon, the entire website 00:06:51.759 --> 00:06:53.819 breaks immediately. That makes perfect sense. 00:06:53.980 --> 00:06:56.839 It has to think much harder. Exactly. Imagine 00:06:56.839 --> 00:07:00.279 asking for a professional locksmith landing page 00:07:00.279 --> 00:07:03.920 layout. You want HTML5 and Tailwind CSS code 00:07:03.920 --> 00:07:07.040 generated perfectly. You mandate a clean design 00:07:07.040 --> 00:07:10.519 and an emergency fee of $99. It looks simple. 00:07:10.670 --> 00:07:13.089 but it outputs hundreds of highly accurate lines. 00:07:13.550 --> 00:07:16.009 It constantly verifies the syntax as it generates 00:07:16.009 --> 00:07:18.509 the response. If you use the Gemini Pro model 00:07:18.509 --> 00:07:21.509 on the free plan, it hurts. You lose 33 % of 00:07:21.509 --> 00:07:24.250 your limit immediately. Even worse, fixing a 00:07:24.250 --> 00:07:26.949 broken button burns more capacity. You ask it 00:07:26.949 --> 00:07:30.009 to debug, and another 33 % vanishes. Yet you 00:07:30.009 --> 00:07:32.589 need a specialized coding platform to avoid this 00:07:32.589 --> 00:07:34.810 trap entirely. Google just launched the free 00:07:34.810 --> 00:07:37.529 anti -gravity model specifically for developers. 00:07:37.790 --> 00:07:40.990 Moving on to visual media, we find a weird paradox. 00:07:41.910 --> 00:07:44.310 Generating images is surprisingly efficient for 00:07:44.310 --> 00:07:46.470 your daily limit. Yeah, you might assume they 00:07:46.470 --> 00:07:49.750 burn massive resources exactly like music. But 00:07:49.750 --> 00:07:52.050 real world tests show they use very few limit 00:07:52.050 --> 00:07:55.649 points. On the free plan, one picture uses barely 00:07:55.649 --> 00:07:58.009 two to three percent. And for the paid plans, 00:07:58.230 --> 00:08:00.649 it stays safely under one percent. You can generate 00:08:00.649 --> 00:08:02.930 a whiteboard -style infographic very easily. 00:08:03.230 --> 00:08:05.410 You can ask for thick markers and absolutely 00:08:05.410 --> 00:08:08.259 no digital fonts. Ingemini creates a beautiful 00:08:08.259 --> 00:08:11.240 picture at a surprisingly small cost. But if 00:08:11.240 --> 00:08:13.500 we jump from static images to moving pictures, 00:08:13.839 --> 00:08:16.680 everything breaks. Video generation is absolute 00:08:16.680 --> 00:08:19.240 chaos for your usage limits today. It is the 00:08:19.240 --> 00:08:22.000 worst offender by a massive margin. It burns 00:08:22.000 --> 00:08:24.680 huge power, and the results are incredibly hard 00:08:24.680 --> 00:08:27.740 to guess. It has to render 24 frames per second 00:08:27.740 --> 00:08:30.220 with temporal consistency. Free users aren't 00:08:30.220 --> 00:08:32.240 even allowed to make videos right now. If you 00:08:32.240 --> 00:08:34.679 have the $20 Pro plan, you can certainly try. 00:08:34.889 --> 00:08:39.129 But one single video eats 33 % of your limit. 00:08:39.330 --> 00:08:41.570 Yeah, and sometimes the system gets completely 00:08:41.570 --> 00:08:44.549 stuck processing the heavy files. It never finishes 00:08:44.549 --> 00:08:46.990 the video, but it steals your credits anyway. 00:08:47.210 --> 00:08:50.470 Oh, that's rough. Whoa. Imagine scaling to a 00:08:50.470 --> 00:08:52.889 billion queries and realizing just one video 00:08:52.889 --> 00:08:55.210 prompt eats a third of the processing power. 00:08:55.330 --> 00:08:57.210 It is staggering when you actually look at the 00:08:57.210 --> 00:08:59.470 math. If you want video, you really should use 00:08:59.470 --> 00:09:01.929 Google Flow. Right. It runs on the new Gemini 00:09:01.929 --> 00:09:06.039 Ami model instead. Neat. Why are images so incredibly 00:09:06.039 --> 00:09:09.159 cheap to generate compared to coding? Well, code 00:09:09.159 --> 00:09:12.220 requires flawless logic, precise structure, and 00:09:12.220 --> 00:09:14.639 complex rules. Images are really just simple 00:09:14.639 --> 00:09:17.440 pixel patterns to the AI. Code demands flawless 00:09:17.440 --> 00:09:19.519 logic and structure. Images just need a pretty 00:09:19.519 --> 00:09:21.840 pattern. Yeah. It's all about how the machine 00:09:21.840 --> 00:09:24.960 thinks underneath. Sponsor. Let's get back into 00:09:24.960 --> 00:09:27.519 optimizing this heavy AI workflow. Even with 00:09:27.519 --> 00:09:30.080 perfect rules, you might hit 100 % capacity. 00:09:30.299 --> 00:09:32.720 Oh, it happens to the best of us. So what are 00:09:32.720 --> 00:09:34.899 the backdoor methods available to you right now? 00:09:35.120 --> 00:09:37.179 How do you keep working when the main tank is 00:09:37.179 --> 00:09:39.820 completely empty? Well, advanced users always 00:09:39.820 --> 00:09:42.419 have their own hidden secrets ready. Trick number 00:09:42.419 --> 00:09:45.259 one is utilizing the tiny flashlight model. When 00:09:45.259 --> 00:09:47.539 you hit the limit, you get blocked from using 00:09:47.539 --> 00:09:50.299 Pro. You get blocked from image and video generation 00:09:50.299 --> 00:09:53.519 entirely. Right. But Google has this super small, 00:09:53.740 --> 00:09:56.759 very light secondary model available. Flashlight 00:09:56.759 --> 00:09:59.840 uses almost zero compute power to actually run. 00:10:00.000 --> 00:10:02.320 It still works perfectly when your main battery 00:10:02.320 --> 00:10:04.700 is completely empty. It's great for basic grammar 00:10:04.700 --> 00:10:07.399 checks and quick translation tasks. You use it 00:10:07.399 --> 00:10:09.379 while waiting patiently for that five -hour reset. 00:10:09.659 --> 00:10:11.720 Another massive trick is moving your reading 00:10:11.720 --> 00:10:14.940 workflows over to Notebook LM. You should absolutely 00:10:14.940 --> 00:10:17.840 not reach huge PDFs in the main chat. Oh, definitely 00:10:17.840 --> 00:10:20.360 not. Doing that is just burning your daily limit 00:10:20.360 --> 00:10:23.149 entirely uselessly. Notebook LM is a totally 00:10:23.149 --> 00:10:25.990 separate and completely free organizational tool. 00:10:26.389 --> 00:10:28.690 It has an independent limit level specifically 00:10:28.690 --> 00:10:31.049 for your uploaded document. Right. It uses a 00:10:31.049 --> 00:10:32.350 different retrieval system in the background 00:10:32.350 --> 00:10:35.309 entirely. You can freely upload large PDF files 00:10:35.309 --> 00:10:38.990 and incredibly long texts. You can upload website 00:10:38.990 --> 00:10:41.730 links and ask for highly detailed summaries. 00:10:41.879 --> 00:10:44.460 It won't touch your main Gemini battery at all. 00:10:44.720 --> 00:10:47.019 Wait, so I can summarize a whole book over there 00:10:47.019 --> 00:10:50.519 safely, and my main Gemini chat remains at 100 00:10:50.519 --> 00:10:52.779 % capacity. Absolutely. This is the smartest 00:10:52.779 --> 00:10:54.840 offloading trick you can possibly use today. 00:10:55.399 --> 00:10:57.559 You also want to look at using specialized developer 00:10:57.559 --> 00:11:00.120 apps. Right. We saw how fast coding and videos 00:11:00.120 --> 00:11:02.600 burn the main limit. Yeah. If you're building 00:11:02.600 --> 00:11:05.519 software, move directly to Google AI Studio. 00:11:06.120 --> 00:11:08.980 It gives you a clean barebone space to test code 00:11:08.980 --> 00:11:11.809 safely. It has a much higher usage limit designed 00:11:11.809 --> 00:11:14.590 explicitly for developers. Exactly. You can test 00:11:14.590 --> 00:11:17.269 HTML and complex CSS all day long there. For 00:11:17.269 --> 00:11:20.110 creating videos, you should look for standalone 00:11:20.110 --> 00:11:23.389 tools like Google Flow. Free users actually get 00:11:23.389 --> 00:11:26.230 50 credits per day just for video. Now let's 00:11:26.230 --> 00:11:28.450 break down our recommendations by your specific 00:11:28.450 --> 00:11:30.850 subscription tier. Your optimization strategy 00:11:30.850 --> 00:11:33.049 changes heavily based on your current specific 00:11:33.049 --> 00:11:35.269 plan. It really does. If you're on the free tier, 00:11:35.809 --> 00:11:38.250 protect your limit aggressively. You must avoid 00:11:38.250 --> 00:11:41.529 complex coding tasks at all costs here. You must 00:11:41.529 --> 00:11:43.870 avoid the heavy Gemini Pro model completely. 00:11:44.049 --> 00:11:46.309 Yeah, just one prompt on Pro can destroy your 00:11:46.309 --> 00:11:49.330 daily limit instantly. Always use Gemini Flash 00:11:49.330 --> 00:11:51.929 and keep your thinking set at standard. Move 00:11:51.929 --> 00:11:54.570 all your long PDFs directly over to Notebook 00:11:54.570 --> 00:11:57.350 LM for reading. Definitely. Now, if you paid 00:11:57.350 --> 00:12:00.710 $20 for the Pro plan, you have freedom. But you 00:12:00.710 --> 00:12:03.669 still absolutely need a highly solid workflow 00:12:03.669 --> 00:12:06.750 strategy. Heavy coding is okay if you stick strictly 00:12:06.750 --> 00:12:10.149 to Gemini Flash. But you must avoid turning on 00:12:10.149 --> 00:12:12.789 extended thinking accidentally. And always remember 00:12:12.789 --> 00:12:15.669 that video generation hits your cap in 30 minutes. 00:12:15.929 --> 00:12:18.289 If you pay for the Ultra Plan, you have massive 00:12:18.289 --> 00:12:21.470 power available. It costs $100 to $200 a single 00:12:21.470 --> 00:12:23.230 month. Right. You generally don't worry about 00:12:23.230 --> 00:12:25.490 limits like other normal users do. But it's really 00:12:25.490 --> 00:12:27.690 only worth it for daily heavy video generation. 00:12:27.870 --> 00:12:30.230 It handles multiple heavy video prompts safely 00:12:30.230 --> 00:12:33.350 without crashing completely. But even on Ultra, 00:12:33.649 --> 00:12:37.009 use Flash for your basic daily text tasks. Yeah. 00:12:37.350 --> 00:12:40.149 To sex silence. Is there ever a reason to use 00:12:40.149 --> 00:12:42.990 the massive ultra brain for simple emails? No. 00:12:43.129 --> 00:12:46.029 It is a massive waste of valuable computational 00:12:46.029 --> 00:12:49.350 resources. You must save the heavy power for 00:12:49.350 --> 00:12:51.830 when you actually need it. Never use a supercomputer 00:12:51.830 --> 00:12:54.809 just to write a simple email subject line. Exactly. 00:12:55.029 --> 00:12:57.470 It's all about using the right tool for the job. 00:12:57.610 --> 00:13:00.149 That brings us directly to the big idea of this 00:13:00.149 --> 00:13:03.169 deep dive. The core philosophy here is ultimately 00:13:03.169 --> 00:13:06.230 about addition by subtraction. Yeah. Removing 00:13:06.230 --> 00:13:09.269 unnecessary heavy requests helps the entire system 00:13:09.269 --> 00:13:12.450 run smoothly. Offloading those heavy workloads 00:13:12.450 --> 00:13:15.529 is the ultimate workflow cheat code today. You 00:13:15.529 --> 00:13:17.669 move them to independent systems like Notebook 00:13:17.669 --> 00:13:21.389 LM and AI Studio. This keeps your main chat account 00:13:21.389 --> 00:13:24.049 fully active for your daily work. Right. You 00:13:24.049 --> 00:13:26.830 divide and transfer tasks to effectively double 00:13:26.830 --> 00:13:29.379 your overall work efficiency. We've entered a 00:13:29.379 --> 00:13:32.279 fascinating and slightly strange era of technology. 00:13:32.740 --> 00:13:34.659 We actually have to budget machine thoughts very 00:13:34.659 --> 00:13:37.419 carefully now. It's why? We budget them the exact 00:13:37.419 --> 00:13:39.879 same way we budget our own mental energy. What 00:13:39.879 --> 00:13:42.299 happens to our personal creativity when our digital 00:13:42.299 --> 00:13:44.559 brains get tired just like our biological ones? 00:13:44.700 --> 00:13:46.580 That's a great question. Something for you to 00:13:46.580 --> 00:13:49.279 ponder as you configure your usage limits today. 00:13:49.419 --> 00:13:51.100 Thank you so much for joining us on this deep 00:13:51.100 --> 00:13:53.279 dive. O -U -T -R -O music.