WEBVTT 00:00:00.000 --> 00:00:03.240 You know, we live in this strange era of digital 00:00:03.240 --> 00:00:06.679 abundance. There are tools for absolutely everything. 00:00:06.799 --> 00:00:08.419 And when you look at the software landscape, 00:00:08.699 --> 00:00:10.800 especially internal tools, you notice something 00:00:10.800 --> 00:00:15.039 peculiar. A lot of it looks sleek. You know, 00:00:15.179 --> 00:00:17.019 it has the right color palettes, the rounded 00:00:17.019 --> 00:00:18.899 corners. It looks like it belongs in a design 00:00:18.899 --> 00:00:21.980 portfolio. But then you try to actually use the 00:00:21.980 --> 00:00:25.320 thing, and you realize it's just decoration. 00:00:25.579 --> 00:00:28.129 It's the eye candy problem. That's exactly it. 00:00:28.230 --> 00:00:29.850 The difference between a dashboard that gets 00:00:29.850 --> 00:00:32.689 sold for a premium and one that just sits there 00:00:32.689 --> 00:00:34.969 looking pretty and collecting digital dust. Most 00:00:34.969 --> 00:00:36.770 dashboards fail, not because the code is broken. 00:00:37.090 --> 00:00:38.570 It's because they don't actually solve a problem 00:00:38.570 --> 00:00:40.670 for the human being staring at the screen. It 00:00:40.670 --> 00:00:43.229 makes you think about that tension between utility 00:00:43.229 --> 00:00:45.990 and aesthetics. We often conflate the two. We 00:00:45.990 --> 00:00:48.560 assume if it looks good, it must be good. But 00:00:48.560 --> 00:00:51.820 today, we're going to dismantle that idea. We're 00:00:51.820 --> 00:00:54.420 looking at a very specific systematic approach 00:00:54.420 --> 00:00:57.479 to building professional AI dashboards. It's 00:00:57.479 --> 00:01:01.079 called the BU -ILD framework. And what's interesting 00:01:01.079 --> 00:01:03.259 here is that we aren't just talking about writing 00:01:03.259 --> 00:01:05.540 code in the traditional sense. We're talking 00:01:05.540 --> 00:01:09.099 about using tools like Gemini 3 and Google Antigravity 00:01:09.099 --> 00:01:12.280 to essentially orchestrate a system. Right. It's 00:01:12.280 --> 00:01:14.900 less about being a bricklayer, laying every single 00:01:14.900 --> 00:01:17.159 line of code by hand, and more about being the 00:01:17.159 --> 00:01:19.140 architect. The source material we're diving into 00:01:19.140 --> 00:01:22.620 today lays out this acronym, BUILD. It stands 00:01:22.620 --> 00:01:25.459 for business purpose, underlying data, information 00:01:25.459 --> 00:01:28.640 hierarchy, layout, and dynamics. It's a roadmap 00:01:28.640 --> 00:01:31.040 for taking a vague idea and turning it into a 00:01:31.040 --> 00:01:33.400 really high value product, even if you've never 00:01:33.400 --> 00:01:35.519 written the line of syntax in your life. Let's 00:01:35.519 --> 00:01:37.680 start at the beginning then. The letter B, business 00:01:37.680 --> 00:01:39.719 purpose. It sounds a little corporate, almost 00:01:39.719 --> 00:01:43.060 too obvious, have a purpose. But I suspect there's 00:01:43.060 --> 00:01:46.500 more to it. Oh, there is so much more. The source 00:01:46.500 --> 00:01:49.640 emphasizes that the why has to be concrete before 00:01:49.640 --> 00:01:51.879 you touch a single tool. If you build without 00:01:51.879 --> 00:01:53.859 a goal, you're just burning compute credits. 00:01:54.459 --> 00:01:57.459 The core concept here is signal versus noise. 00:01:58.200 --> 00:02:00.799 Signiverse is noise. We hear that a lot. But 00:02:00.799 --> 00:02:03.400 what does it mean for a dashboard specifically? 00:02:03.799 --> 00:02:06.099 In this context, it means every single chart, 00:02:06.659 --> 00:02:09.560 every number on that screen must lead to a specific 00:02:09.560 --> 00:02:12.659 action. If a number drops, the user needs to 00:02:12.659 --> 00:02:15.379 know exactly what to do next. If the dashboard 00:02:15.379 --> 00:02:18.000 doesn't tell them that, it's just noise. It's 00:02:18.000 --> 00:02:20.460 vanity metrics. Okay, but finding that signal 00:02:20.460 --> 00:02:22.780 is hard. People often don't know what they really 00:02:22.780 --> 00:02:24.979 want, so how do you find out what the user actually 00:02:24.979 --> 00:02:27.319 needs before you start building? You have to 00:02:27.319 --> 00:02:29.039 become a detective. Yeah. You have to find their 00:02:29.039 --> 00:02:31.800 pain points, but not by guessing. The source 00:02:31.800 --> 00:02:33.620 suggests some really tactical ways to do this. 00:02:33.639 --> 00:02:36.180 You're looking for frustration. When people complain, 00:02:36.500 --> 00:02:38.580 they are basically asking for a solution they'd 00:02:38.580 --> 00:02:40.719 pay for. Give me an example. Where are we looking 00:02:40.719 --> 00:02:42.939 for these complaints? The guide mentions using 00:02:42.939 --> 00:02:45.000 something called Gummy Search to scan Reddit. 00:02:45.520 --> 00:02:48.639 Reddit? Really? Isn't that mostly just people 00:02:48.639 --> 00:02:50.740 venting and arguing? It feels like a lot of noise 00:02:50.740 --> 00:02:53.340 to sift through. It is venting, but that's the 00:02:53.340 --> 00:02:56.300 gold. You look for communities where your potential 00:02:56.300 --> 00:02:58.520 users hang out and you search for phrases like, 00:02:58.939 --> 00:03:02.439 I'm tired of checking. Or, how can I track? You're 00:03:02.439 --> 00:03:04.520 literally looking for emotional friction. So 00:03:04.520 --> 00:03:06.879 the complaint is a product request in disguise. 00:03:07.460 --> 00:03:09.659 Precisely. And you can go further. You can use 00:03:09.659 --> 00:03:11.439 Answer the Public to see what people are typing 00:03:11.439 --> 00:03:14.219 into Google. Or check Product Hunt to see what's 00:03:14.219 --> 00:03:16.919 standard. But here's the key part. Once you have 00:03:16.919 --> 00:03:20.120 all this raw data, you don't start coding. You 00:03:20.120 --> 00:03:22.800 use AI to synthesize it. This is where Claude 00:03:22.800 --> 00:03:25.340 comes in, I assume. But why bring in an LLM so 00:03:25.340 --> 00:03:28.460 early? Because you need a plan. A concrete plan. 00:03:28.599 --> 00:03:31.840 The strategy is to use Claude to generate a standard 00:03:31.840 --> 00:03:34.199 operating procedure, an SOP. So let's say you 00:03:34.199 --> 00:03:36.199 want to build a dashboard for a coffee shop chain. 00:03:36.620 --> 00:03:38.319 You don't just say, make a coffee dashboard. 00:03:38.800 --> 00:03:41.240 You tell Claude, I need to help owners decide 00:03:41.240 --> 00:03:43.560 when to restock oat versus almond milk based 00:03:43.560 --> 00:03:46.319 on waste. And you ask it to write out a detailed 00:03:46.319 --> 00:03:49.020 SOP with the key metrics and the decisions the 00:03:49.020 --> 00:03:50.960 owner has to make. Pause there for a second. 00:03:51.000 --> 00:03:53.729 That feels... counterintuitive. Usually, developers 00:03:53.729 --> 00:03:55.430 want to get their hands dirty immediately. They 00:03:55.430 --> 00:03:57.969 want to see an interface. You're saying the discipline 00:03:57.969 --> 00:04:01.509 here is to not code. The discipline is to write 00:04:01.509 --> 00:04:04.229 a constitution for the software first. If you 00:04:04.229 --> 00:04:07.629 ask an AI to just write code, it's going to guess 00:04:07.629 --> 00:04:09.750 at the business logic. It'll hallucinate features. 00:04:10.270 --> 00:04:12.949 But if you feed it an SOP, a text document explaining 00:04:12.949 --> 00:04:15.229 the logic in plain English, you're telling it 00:04:15.229 --> 00:04:17.009 what to think before you tell it how to code. 00:04:17.329 --> 00:04:19.550 That's a huge shift in approach. So, probing 00:04:19.550 --> 00:04:22.600 question for you then. Why write a text SOP before 00:04:22.600 --> 00:04:25.160 a single line of code? Because ambiguity in the 00:04:25.160 --> 00:04:27.379 plan creates chaos in the code. That makes a 00:04:27.379 --> 00:04:29.040 lot of sense. If you can't write it in English, 00:04:29.100 --> 00:04:31.759 you can't write it in Python. Okay, so we have 00:04:31.759 --> 00:04:35.560 a why. Now we move to the U and BYLD underlying 00:04:35.560 --> 00:04:38.220 data, the what. This is where we get into the 00:04:38.220 --> 00:04:40.300 actual tools. Right. And for a lot of people, 00:04:40.360 --> 00:04:42.259 this is the scary part. They think, I don't know 00:04:42.259 --> 00:04:45.600 how to set up a server. But the source recommends 00:04:45.600 --> 00:04:48.680 this, fastest combination for beginners. It's 00:04:48.680 --> 00:04:51.680 a three -part harmony. Google AI Studio, Google 00:04:51.680 --> 00:04:54.259 Antigravity, and SuperBase. Can you break those 00:04:54.259 --> 00:04:56.060 down for us? I think people can get lives in 00:04:56.060 --> 00:04:58.579 the brand names. For sure. Think of Google AI 00:04:58.579 --> 00:05:01.420 Studio as your design lab. It's where you experiment 00:05:01.420 --> 00:05:04.399 and set the vision. Then you have Google Antigravity. 00:05:04.480 --> 00:05:06.199 That's the workspace. That's where the app actually 00:05:06.199 --> 00:05:08.980 lives and where you talk to the code. And finally, 00:05:09.620 --> 00:05:12.480 SuperBase. And SuperBase is the database. Think 00:05:12.480 --> 00:05:15.100 of it as the long -term memory. or the vault. 00:05:15.500 --> 00:05:18.379 Gemini is the brain processing the request, but 00:05:18.379 --> 00:05:20.360 it needs to store facts somewhere permanent. 00:05:21.000 --> 00:05:23.259 That's SuperBase. It's where the actual data 00:05:23.259 --> 00:05:26.639 lives. That phrase, talk to the code, really 00:05:26.639 --> 00:05:28.920 highlights how much things have changed. It feels 00:05:28.920 --> 00:05:31.500 less like typing syntax and more like having 00:05:31.500 --> 00:05:34.480 a conversation. It really is. The workflow starts 00:05:34.480 --> 00:05:37.120 in Google AI Studio. You upload that SOP text 00:05:37.120 --> 00:05:39.360 we just talked about. But here's a really cool 00:05:39.360 --> 00:05:42.079 trick the source mentions. You also upload visual 00:05:42.079 --> 00:05:45.519 inspiration. Like... Screenshots. Exactly. You 00:05:45.519 --> 00:05:47.939 go to Dribbble or Pinterest, find a dashboard 00:05:47.939 --> 00:05:49.980 that looks clean, pick one dark mode and one 00:05:49.980 --> 00:05:52.839 light mode, and you upload those images along 00:05:52.839 --> 00:05:56.060 with your text. You're telling the AI, I want 00:05:56.060 --> 00:05:58.060 the logic from this text, but I want it to look 00:05:58.060 --> 00:06:01.480 as professional as these images. Is that cheating, 00:06:01.519 --> 00:06:04.120 or does it just create a derivative product? 00:06:04.379 --> 00:06:06.160 I wouldn't call it cloning. I'd call it setting 00:06:06.160 --> 00:06:08.660 a vocabulary. If you just say, make a dashboard, 00:06:08.759 --> 00:06:11.740 you get a generic kind of 2015 looking website. 00:06:12.220 --> 00:06:14.519 By providing the screenshots, you're giving the 00:06:14.519 --> 00:06:16.839 AI a meta prompt. You're setting the aesthetic 00:06:16.839 --> 00:06:19.480 bar high. You're saying use Tailwind CSS. Make 00:06:19.480 --> 00:06:22.680 it look like a $5 ,000 corporate tool. You know, 00:06:22.959 --> 00:06:25.240 I appreciate the vulnerability in the source 00:06:25.240 --> 00:06:28.069 material here. The author admits to wrestling 00:06:28.069 --> 00:06:30.810 with prompt drift. I still wrestle with prompt 00:06:30.810 --> 00:06:33.589 drift myself. Getting the AI to stay focused 00:06:33.589 --> 00:06:37.709 on the original plan is hard without these strict 00:06:37.709 --> 00:06:39.569 guardrails. Yeah, it's a real thing. It needs 00:06:39.569 --> 00:06:41.310 those guardrails. If you don't set the standard, 00:06:41.750 --> 00:06:43.730 the AI will get lazy. It's like a contractor. 00:06:43.750 --> 00:06:46.550 If you don't specify marble countertops, you're 00:06:46.550 --> 00:06:49.069 going to get laminate. So to wrap up this section, 00:06:49.310 --> 00:06:52.829 then. Why upload screenshots of other people's 00:06:52.829 --> 00:06:55.750 designs? It forces the AI to mimic a professional 00:06:55.750 --> 00:06:58.170 standard visually. Okay, let's unpack the next 00:06:58.170 --> 00:07:01.269 letter. I. Information hierarchy. The where. 00:07:02.230 --> 00:07:04.389 We have our data. We have our look. But how do 00:07:04.389 --> 00:07:06.769 we arrange it all? The source mentioned something 00:07:06.769 --> 00:07:09.569 called the 10 -second rule. This is all about 00:07:09.569 --> 00:07:12.170 cognitive load. The 10 -second rule just means 00:07:12.170 --> 00:07:14.250 a user should understand the state of their business 00:07:14.250 --> 00:07:17.110 within 10 seconds of looking at the screen. And 00:07:17.110 --> 00:07:20.579 to do that, you need a Herometric. The herometric. 00:07:20.879 --> 00:07:23.560 The one number that tells the whole story. Exactly. 00:07:23.920 --> 00:07:26.259 For a sauce company, maybe it's active users. 00:07:26.560 --> 00:07:29.019 For our coffee shop, it's daily sales. And its 00:07:29.019 --> 00:07:31.279 placement is non -negotiable. Top left corner. 00:07:31.519 --> 00:07:33.860 Why so dogmatic about the top left? Couldn't 00:07:33.860 --> 00:07:36.379 I put it in the center and make it huge? You 00:07:36.379 --> 00:07:38.680 could, but you'd be fighting biology. We're talking 00:07:38.680 --> 00:07:40.759 about the F pattern here. The F pattern. Yeah, 00:07:40.759 --> 00:07:43.759 it's a classic user experience concept. Eye tracking 00:07:43.759 --> 00:07:45.579 studies show that when we look at a screen, we 00:07:45.579 --> 00:07:48.920 don't really read it. We scan it. Our eyes instinctively 00:07:48.920 --> 00:07:51.980 anchor top left, scan across, then drop down 00:07:51.980 --> 00:07:55.180 and scan across again. It forms a rough F shape. 00:07:55.720 --> 00:07:57.699 If your most important number isn't in that anchor 00:07:57.699 --> 00:08:00.399 spot, you're making the user hunt for it. That's 00:08:00.399 --> 00:08:02.980 fascinating. So good design is really just anticipating 00:08:02.980 --> 00:08:05.660 human efficiency. Or laziness. You want to reduce 00:08:05.660 --> 00:08:07.860 friction. You make that number the biggest text 00:08:07.860 --> 00:08:11.180 on the screen. Then you group related data together. 00:08:11.470 --> 00:08:14.230 The guide suggests using Google Antigravity's 00:08:14.230 --> 00:08:16.350 planning mode here. You can actually ask the 00:08:16.350 --> 00:08:19.550 AI, based on design best practices, how should 00:08:19.550 --> 00:08:22.250 I order these five metrics before you change 00:08:22.250 --> 00:08:24.750 any code? That's a really smart use of the tool. 00:08:24.910 --> 00:08:28.550 You're treating the AI as a consultant. And it 00:08:28.550 --> 00:08:30.610 usually gives pretty good advice because it's 00:08:30.610 --> 00:08:32.990 ingested millions of design patterns. It knows 00:08:32.990 --> 00:08:36.149 what good looks like. So to pin this down, why 00:08:36.149 --> 00:08:38.750 does the top left corner matter so much? It's 00:08:38.750 --> 00:08:40.789 biological. That is where the human eye naturally 00:08:40.789 --> 00:08:44.450 lands first. It's biological, unavoidable, and 00:08:44.450 --> 00:08:47.049 speaking of things that are unavoidable. Sponsor. 00:08:48.370 --> 00:08:50.789 Okay, we're back. Deep diving into the BUILD 00:08:50.789 --> 00:08:53.169 framework. We've covered business purpose, underlying 00:08:53.169 --> 00:08:55.470 data, and information hierarchy. Now we're on 00:08:55.470 --> 00:08:58.669 to L layout, the how. And this section introduces 00:08:58.669 --> 00:09:01.350 a concept I absolutely love, the museum principle. 00:09:01.690 --> 00:09:03.789 The museum principle. Let me guess, the dashboard 00:09:03.789 --> 00:09:06.110 should be a work of art. Actually, the total 00:09:06.110 --> 00:09:08.850 opposite. Think about a modern art museum. What 00:09:08.850 --> 00:09:11.850 do the walls look like? White. Plain. Empty. 00:09:12.070 --> 00:09:15.009 Exactly. They're invisible. Why? So you only 00:09:15.009 --> 00:09:18.269 look at the art. In a dashboard, the art is the 00:09:18.269 --> 00:09:20.669 data. The design, the containers, the background 00:09:20.669 --> 00:09:23.990 should be the museum walls. If a user is noticing 00:09:23.990 --> 00:09:27.409 your cool gradient menu, you've probably failed. 00:09:28.169 --> 00:09:30.659 Good design should be invisible. That's a fantastic 00:09:30.659 --> 00:09:32.600 analogy. The interface should just get out of 00:09:32.600 --> 00:09:34.559 the way. But that's hard to do, isn't it? We 00:09:34.559 --> 00:09:36.500 have a tendency to want to fill empty space. 00:09:36.620 --> 00:09:38.799 We do. We want to clutter it. And the biggest 00:09:38.799 --> 00:09:41.779 offender is usually the sidebar. The source compares 00:09:41.779 --> 00:09:43.919 it to a steering wheel. If you have 50 buttons 00:09:43.919 --> 00:09:46.179 on a steering wheel, the driver's going to crash. 00:09:46.480 --> 00:09:49.039 Cognitive overload again. Right. The rule here 00:09:49.039 --> 00:09:51.480 is strict. Keep the sidebar to five to seven 00:09:51.480 --> 00:09:54.700 items max. Dashboard, analytics, customers, settings, 00:09:54.919 --> 00:09:57.370 help. That's it. If you have more. Nest them. 00:09:57.509 --> 00:09:59.909 It's about subtraction, not addition. And here's 00:09:59.909 --> 00:10:01.730 another great way to use AI that I hadn't thought 00:10:01.730 --> 00:10:05.429 of. You can run an AI audit. You literally prompt 00:10:05.429 --> 00:10:09.509 the AI to act as a senior UI UX designer. You 00:10:09.509 --> 00:10:11.830 ask it to critique your work. You say, look at 00:10:11.830 --> 00:10:15.889 this code. Suggest items to remove to reduce 00:10:15.889 --> 00:10:18.379 clutter. That's brilliant. You're role -playing 00:10:18.379 --> 00:10:20.120 with the model. Usually you'd have to hire someone 00:10:20.120 --> 00:10:22.080 to get that kind of feedback. It works so well. 00:10:22.179 --> 00:10:23.940 It catches things you miss because you've been 00:10:23.940 --> 00:10:26.200 staring at the screen for six hours. It helps 00:10:26.200 --> 00:10:28.659 you get that expensive look without the agency 00:10:28.659 --> 00:10:32.019 price tag. So what is the ultimate test of a 00:10:32.019 --> 00:10:35.019 good layout? If the user doesn't notice the design, 00:10:35.600 --> 00:10:38.480 you succeeded. That brings us to the final letter. 00:10:38.899 --> 00:10:42.919 D -Dynamics. The feel. And honestly, this is 00:10:42.919 --> 00:10:45.279 where so many tools fall apart. They look fine, 00:10:45.279 --> 00:10:48.440 but they feel Dead. Dead is the perfect word. 00:10:49.059 --> 00:10:52.080 Silence creates distrust. Explain that. Why does 00:10:52.080 --> 00:10:54.820 silence create distrust in software? Well, imagine 00:10:54.820 --> 00:10:56.840 we're having a conversation. I say something, 00:10:56.960 --> 00:10:59.019 and you just stare at me, stone -faced, for three 00:10:59.019 --> 00:11:00.940 seconds. That's awkward. I'd think you didn't 00:11:00.940 --> 00:11:03.419 hear me, or you're angry or something. Exactly. 00:11:03.820 --> 00:11:06.000 Software is a conversation. If you click a button 00:11:06.000 --> 00:11:07.879 and nothing happens, you panic. You think, did 00:11:07.879 --> 00:11:11.399 it work? Did I break it? The dashboard needs 00:11:11.399 --> 00:11:13.940 to feel alive. So how do we manufacture that 00:11:13.940 --> 00:11:17.799 life? Visual feedback. It's the micro interactions 00:11:17.799 --> 00:11:20.539 hover effects when your mouse goes over a button 00:11:20.539 --> 00:11:23.539 It should change color slightly to say I see 00:11:23.539 --> 00:11:26.960 you Loading states never show a blank screen 00:11:26.960 --> 00:11:29.399 show a spinner so the user knows thinking is 00:11:29.399 --> 00:11:32.470 happening success messages It all ends up. It's 00:11:32.470 --> 00:11:35.429 the software nodding back at you. Yes. And this 00:11:35.429 --> 00:11:37.450 is also where we connect to the real world. We 00:11:37.450 --> 00:11:41.049 move from fake placeholder numbers to real API 00:11:41.049 --> 00:11:43.830 data using SuperBase. This is the part that always 00:11:43.830 --> 00:11:45.789 feels like magic to me. Oh, it's a total moment 00:11:45.789 --> 00:11:49.299 of wonder. Whoa. Imagine just handing the AI 00:11:49.299 --> 00:11:52.220 and AP and watching it wire up the entire database 00:11:52.220 --> 00:11:54.539 instantly. It used to take days of writing Fed 00:11:54.539 --> 00:11:57.620 requests and error handling. Now it's just connected. 00:11:57.799 --> 00:11:59.580 But once it's connected, it has to be fast, right? 00:11:59.620 --> 00:12:02.059 That's the snappy test. Page transitions must 00:12:02.059 --> 00:12:04.779 be smooth. Buttons must react instantly. If it 00:12:04.779 --> 00:12:07.200 feels sluggish, people subconsciously assume 00:12:07.200 --> 00:12:09.820 the data is unreliable. It's irrational, but 00:12:09.820 --> 00:12:12.159 it's human nature. So why do things like hover 00:12:12.159 --> 00:12:14.559 effects and spinners really matter? Responsiveness 00:12:14.559 --> 00:12:17.279 builds psychological trust that the data is accurate. 00:12:17.419 --> 00:12:19.159 So let's zoom out. We've walked through the whole 00:12:19.159 --> 00:12:22.700 framework. BUILD. Let's do a rapid -fire recap. 00:12:22.840 --> 00:12:25.899 Okay, let's hit it. B, business purpose. Solve 00:12:25.899 --> 00:12:29.519 a real problem with an SOP. U, underlying data. 00:12:30.120 --> 00:12:33.960 Connect clean data with the right stack. I, information 00:12:33.960 --> 00:12:37.000 hierarchy. Spotlight that hero metric top left. 00:12:37.240 --> 00:12:40.720 L, layout. The museum principle. Keep it invisible. 00:12:41.320 --> 00:12:44.860 D -Dynamics. Make it feel alive to build trust. 00:12:45.120 --> 00:12:47.639 It's a powerful framework. And what I find most 00:12:47.639 --> 00:12:49.620 compelling here is the philosophical shift it 00:12:49.620 --> 00:12:52.019 implies. It really emphasizes that you, the listener, 00:12:52.399 --> 00:12:54.539 you're no longer just a viewer of technology. 00:12:54.639 --> 00:12:57.000 You are a creator. That's the big shift. We're 00:12:57.000 --> 00:12:58.620 moving away from an era where you had to spend 00:12:58.620 --> 00:13:01.740 years learning to code syntax. We are moving 00:13:01.740 --> 00:13:03.639 toward an era where you need to learn to define 00:13:03.639 --> 00:13:07.100 the problem. The AI handles the how. The syntax, 00:13:07.419 --> 00:13:10.240 the database queries, but you have to master 00:13:10.240 --> 00:13:12.279 the why. You're the director. It's a call to 00:13:12.279 --> 00:13:13.799 action really. Don't worry about perfection. 00:13:13.980 --> 00:13:16.600 The barrier to entry has never been lower. Exactly. 00:13:16.919 --> 00:13:19.899 Open antigravity. Build one screen. Just one. 00:13:20.080 --> 00:13:23.019 Do it today. The best way to learn this isn't 00:13:23.019 --> 00:13:25.480 to listen to us talk about it, but to actually 00:13:25.480 --> 00:13:27.639 struggle through that first prompt. I think that's 00:13:27.639 --> 00:13:29.440 the perfect place to leave it. Go build something. 00:13:29.539 --> 00:13:31.360 See what happens. Thanks for diving in with us. 00:13:31.559 --> 00:13:32.200 Always a pleasure.