WEBVTT 00:00:00.000 --> 00:00:02.359 We all have that feeling, right? The execution 00:00:02.359 --> 00:00:05.200 gap. You get an idea maybe in the shower or you're 00:00:05.200 --> 00:00:07.360 stuck in traffic and it's perfect in your head. 00:00:07.860 --> 00:00:09.919 A brilliant app, a new business, little game. 00:00:10.439 --> 00:00:13.179 But then there's this friction between your brain 00:00:13.179 --> 00:00:15.460 and the screen. And that friction is almost always 00:00:15.460 --> 00:00:19.059 code. It's code, it's syntax, it's the thousands 00:00:19.059 --> 00:00:21.440 of dollars you'd need to hire a dev team. It's 00:00:21.440 --> 00:00:23.719 the classic technical wall. It's where most great 00:00:23.719 --> 00:00:26.199 ideas go to die. Right. And usually on this show, 00:00:26.199 --> 00:00:28.780 when we talk about AI, we're talking about tools 00:00:28.780 --> 00:00:30.679 that help you climb that wall. You know, they're 00:00:30.679 --> 00:00:33.659 like assistants. Or librarians. But the guide 00:00:33.659 --> 00:00:35.939 we're looking at today, it covers Manus AI 1 00:00:35.939 --> 00:00:39.659 .6 Max, makes a much bolder claim. It says the 00:00:39.659 --> 00:00:43.200 wall is just gone. It is a bold assertion. But 00:00:43.200 --> 00:00:45.929 looking at this, the shift is very real. We're 00:00:45.929 --> 00:00:49.350 moving from AI as a consultant to AI as a contractor. 00:00:49.710 --> 00:00:52.409 And that distinction is everything. I want to 00:00:52.409 --> 00:00:54.170 drill down on that right away, because consultant 00:00:54.170 --> 00:00:57.450 implies advice, but contractor, that implies 00:00:57.450 --> 00:00:59.469 labor. What's the real difference here? Well, 00:00:59.469 --> 00:01:02.350 think about chat GPT or Claude. They're text 00:01:02.350 --> 00:01:04.489 engines, right? So if you say, I want a pet grooming 00:01:04.489 --> 00:01:07.230 app, they act like a consultant. You'll say, 00:01:07.329 --> 00:01:09.430 OK, here's a recipe. Here's a block of Python 00:01:09.430 --> 00:01:11.969 code. Good luck. They hand you the blueprint, 00:01:12.129 --> 00:01:13.810 but you still have to pour the concrete. You 00:01:13.810 --> 00:01:16.709 have to compile it, host it. debug it. And the 00:01:16.709 --> 00:01:19.549 contractor. The contractor. Manus AI. It has 00:01:19.549 --> 00:01:21.230 file system access. It creates the directory. 00:01:21.269 --> 00:01:23.569 It writes the index .html. It writes the CSS. 00:01:23.989 --> 00:01:26.030 It spins up the server. It doesn't just tell 00:01:26.030 --> 00:01:27.969 you how to build a website. It just builds it. 00:01:28.010 --> 00:01:30.989 It builds the website. Precisely. It's the difference 00:01:30.989 --> 00:01:34.109 between asking for a recipe and asking a chef 00:01:34.109 --> 00:01:36.950 to put the meal on your table. So that's the 00:01:36.950 --> 00:01:40.510 promise. But I want to test the reality. The 00:01:40.510 --> 00:01:43.469 guide lays out this whole journey, starting with 00:01:43.469 --> 00:01:46.430 a pretty simple app, then a game, then some deep 00:01:46.430 --> 00:01:49.409 market research, and then a full business launch. 00:01:49.650 --> 00:01:51.950 So let's start with that first stress test. The 00:01:51.950 --> 00:01:54.609 local business, happy pause. Right, happy pause. 00:01:55.189 --> 00:01:58.069 The local pet grooming service. Now, traditionally, 00:01:58.650 --> 00:02:00.750 building a booking app for a local dog groomer 00:02:00.750 --> 00:02:03.750 is a total nightmare of logistics. You're managing 00:02:03.750 --> 00:02:06.469 freelancers, you're worrying about server costs. 00:02:06.730 --> 00:02:10.009 It's months of work, minimum. So in this case 00:02:10.009 --> 00:02:11.750 study, what was the input? What did they tell 00:02:11.750 --> 00:02:14.750 it to do? It was a single paragraph of just plain 00:02:14.750 --> 00:02:18.210 English. The prompt was basically, build a fully 00:02:18.210 --> 00:02:21.250 functioning mobile app for happy paws. Use soft 00:02:21.250 --> 00:02:24.270 blue and white colors. List services like dogwash 00:02:24.270 --> 00:02:26.810 and nail trim. Oh, and add a booking page and 00:02:26.810 --> 00:02:29.590 a map placeholder. OK, but I have to be the skeptic 00:02:29.590 --> 00:02:32.169 here. I can ask an image generator to make a 00:02:32.169 --> 00:02:34.310 picture of an app, and it'll look pretty. But 00:02:34.310 --> 00:02:36.409 it doesn't do anything. Is this just a really 00:02:36.409 --> 00:02:39.449 good mockup, or is it actual software? That is 00:02:39.449 --> 00:02:41.610 the aha moment in the guide. A little window 00:02:41.610 --> 00:02:44.189 pops up, a preview pane, and it's live. You can 00:02:44.189 --> 00:02:45.789 click the Book Now button. It actually takes 00:02:45.789 --> 00:02:48.210 you to a confirmation screen. The guide even 00:02:48.210 --> 00:02:51.449 notes the AI included a mobile view icon so you 00:02:51.449 --> 00:02:53.610 can see exactly how it feels on a phone. Does 00:02:53.610 --> 00:02:56.050 this actually result in usable software or just 00:02:56.050 --> 00:02:58.789 a mockup? It creates real functioning technology 00:02:58.789 --> 00:03:00.789 you can use immediately. You could run the business 00:03:00.789 --> 00:03:02.849 off it five minutes later. That's significant. 00:03:03.650 --> 00:03:05.629 But an appointment app, you know, it's useful, 00:03:05.669 --> 00:03:07.990 but it's kind of static. It's forms and buttons. 00:03:08.479 --> 00:03:10.680 I want to see if this thing can handle real complexity, 00:03:10.900 --> 00:03:13.840 like state management. Yeah. Physics. The guide 00:03:13.840 --> 00:03:16.539 moves on to a game next, right? Space Dodger. 00:03:16.919 --> 00:03:21.439 Space Dodger. OK. A browser game. This feels 00:03:21.439 --> 00:03:24.819 like a proper stress test. Moving from pure utility 00:03:24.819 --> 00:03:28.099 to entertainment. It is. They really wanted to 00:03:28.099 --> 00:03:30.460 see if Manus AI could handle the fun factor. 00:03:30.780 --> 00:03:33.419 So they asked for a game inspired by Dino Run. 00:03:33.919 --> 00:03:36.930 Really simple concept. You're a rocket. Asteroids 00:03:36.930 --> 00:03:38.710 fly from right to left, and you just don't crash. 00:03:39.090 --> 00:03:41.650 And again, a simple prompt. Super simple. Rocket 00:03:41.650 --> 00:03:43.810 moves up and down, asteroids come from the right, 00:03:43.990 --> 00:03:46.699 keep score, and bam, it built it. But here's 00:03:46.699 --> 00:03:48.599 where it gets really interesting for anyone who's 00:03:48.599 --> 00:03:51.379 ever tried to code a game with an LLM. The dreaded 00:03:51.379 --> 00:03:54.460 context window. Exactly. Usually you build version 00:03:54.460 --> 00:03:56.199 one and it works. Then you say, okay, now make 00:03:56.199 --> 00:03:59.000 the asteroids faster. The AI rewrites the code, 00:03:59.120 --> 00:04:01.560 but it forgets how the rocket moves. Or it breaks 00:04:01.560 --> 00:04:03.599 the collision detection. Yeah. It's like playing 00:04:03.599 --> 00:04:05.719 Jenga. You pull one block out and the whole tower 00:04:05.719 --> 00:04:08.360 just collapses. So how did Manus handle that, 00:04:08.400 --> 00:04:10.939 the iteration? The guide calls it conversational 00:04:10.939 --> 00:04:13.939 iteration. The user just typed. Make it more 00:04:13.939 --> 00:04:16.889 challenging. Every 10 seconds, make the asteroids 00:04:16.889 --> 00:04:19.889 move 20 % faster. Also change the background 00:04:19.889 --> 00:04:22.180 from blue to black as it gets harder. And it 00:04:22.180 --> 00:04:24.339 didn't break the original movement logic? Not 00:04:24.339 --> 00:04:26.680 at all. It understood the existing code base 00:04:26.680 --> 00:04:29.439 it had just created. It just injected a timer 00:04:29.439 --> 00:04:31.939 function and a speed variable multiplier without 00:04:31.939 --> 00:04:34.519 touching the core rendering loop. The code updated 00:04:34.519 --> 00:04:37.079 in real time. So the coding happens dynamically 00:04:37.079 --> 00:04:39.540 during the conversation? Exactly. You just keep 00:04:39.540 --> 00:04:41.920 talking and the software mutates to match what 00:04:41.920 --> 00:04:44.740 you want. It treats the code like a living project, 00:04:45.120 --> 00:04:47.800 not some disposable text snippet. Let's pivot 00:04:47.800 --> 00:04:49.819 to something that I think plagues a lot of us. 00:04:50.040 --> 00:04:52.579 It's not always the coding that stops an idea. 00:04:52.680 --> 00:04:55.720 It's just the chaos of the process. The research 00:04:55.720 --> 00:04:57.920 rabbit hole. I have to admit, I still wrestle 00:04:57.920 --> 00:05:00.279 with this. I call it prompt drift. You start 00:05:00.279 --> 00:05:03.019 researching a market, and three hours later, 00:05:03.060 --> 00:05:05.420 you have 50 tabs open. You've completely lost 00:05:05.420 --> 00:05:06.920 the thread, and now you're reading about the 00:05:06.920 --> 00:05:09.600 history of coffee beans. It's cognitive overload. 00:05:09.720 --> 00:05:12.819 Yeah. Yes. Yeah. And Manus AI seems to tackle 00:05:12.819 --> 00:05:16.040 this with a specific feature, automating deep 00:05:16.040 --> 00:05:19.100 market research. The example they used was for 00:05:19.100 --> 00:05:21.300 a healthy snack subscription box called Green 00:05:21.300 --> 00:05:24.639 Bites. Okay, Green Bites. So how does the AI 00:05:24.639 --> 00:05:26.800 handle that research any differently than me 00:05:26.800 --> 00:05:29.819 just Googling for three hours? It brings structure 00:05:29.819 --> 00:05:32.720 to the chaos. The prompt actually asked for a 00:05:32.720 --> 00:05:35.480 spreadsheet. It said, conduct a deep competitive 00:05:35.480 --> 00:05:37.319 analysis. I need a spreadsheet with multiple 00:05:37.319 --> 00:05:41.040 tabs. Tab 1, top 10 competitors and their prices. 00:05:41.519 --> 00:05:45.079 Tab 2, target audience analysis. Right, but usually 00:05:45.079 --> 00:05:47.560 if I ask an AI for competitor prices, it either 00:05:47.560 --> 00:05:50.759 hallucinates or it gives me data from 2021 because 00:05:50.759 --> 00:05:52.620 that's when its training data cuts off. Right, 00:05:52.939 --> 00:05:55.100 but Manus has a live browser agent, so it goes 00:05:55.100 --> 00:05:57.680 out to the live web right now. It checks the 00:05:57.680 --> 00:05:59.939 current pricing on the competitor websites. And 00:05:59.939 --> 00:06:02.620 the output, is it just a wall of text? This is 00:06:02.620 --> 00:06:04.860 the cool part. It rendered a functional spreadsheet 00:06:04.860 --> 00:06:08.000 UI right there inside the chat. Rows, columns, 00:06:08.139 --> 00:06:10.319 tabs, you could sort it. It looks just like Excel 00:06:10.319 --> 00:06:12.519 or Google Sheets. That's a huge workload change. 00:06:12.639 --> 00:06:14.180 I'm always copying and pasting into a separate 00:06:14.180 --> 00:06:16.819 document. It removed that whole copy -paste tax. 00:06:17.319 --> 00:06:20.300 It formatted the live data perfectly. It even 00:06:20.300 --> 00:06:23.399 identified gaps in the market. For Green Bites, 00:06:23.500 --> 00:06:26.160 it pointed out that nobody was offering a low 00:06:26.160 --> 00:06:28.899 -sugar option specifically for office workers. 00:06:29.199 --> 00:06:31.540 How does it link the research to the strategy? 00:06:31.980 --> 00:06:34.649 It remembers the context. using the spreadsheet 00:06:34.649 --> 00:06:37.269 data to inform the plan automatically. The user 00:06:37.269 --> 00:06:40.410 just said, OK, use that data to build me a go 00:06:40.410 --> 00:06:42.490 -to -market plan. It just remembers the spreadsheet. 00:06:42.629 --> 00:06:44.930 It remembers everything. So it looked at the 00:06:44.930 --> 00:06:47.230 competitor pricing in that spreadsheet. Let's 00:06:47.230 --> 00:06:50.329 say the average was $35. And it automatically 00:06:50.329 --> 00:06:53.329 suggested a penetration price of $28 a month 00:06:53.329 --> 00:06:56.269 for GreenBytes. So it didn't just guess a number, 00:06:56.589 --> 00:06:59.459 it calculated a strategy based on the research 00:06:59.459 --> 00:07:02.180 it had just done. Exactly. It linked the raw 00:07:02.180 --> 00:07:05.259 data to a strategic decision without the human 00:07:05.259 --> 00:07:07.540 having to connect all the dots. OK, let's talk 00:07:07.540 --> 00:07:09.699 visuals, because a business needs a brand. And 00:07:09.699 --> 00:07:12.480 honestly, AI image generation has been, well, 00:07:12.579 --> 00:07:14.800 it's been hit or miss, especially with text. 00:07:14.939 --> 00:07:17.019 Oh, the alien text struggle is real, yeah. You 00:07:17.019 --> 00:07:19.579 ask for a sign that says coffee and you get coffefe 00:07:19.579 --> 00:07:22.540 or some weird hieroglyphics. Right. But Manus 00:07:22.540 --> 00:07:26.199 AI has this feature they call magic edit. And 00:07:26.199 --> 00:07:30.259 honestly, whoa, it is a bit of a game changer 00:07:30.259 --> 00:07:33.160 for design. And the example was for Greenbite's 00:07:33.160 --> 00:07:35.579 marketing assets, the Instagram posts. Right. 00:07:35.779 --> 00:07:38.319 So they asked for a close -up of a vegan cookie 00:07:38.319 --> 00:07:43.199 with the text 100 % plant power. Simple enough. 00:07:43.300 --> 00:07:46.060 Yep. And the AI generates it. Looks great. But 00:07:46.060 --> 00:07:48.439 then the user decides, you know what? Plant power 00:07:48.439 --> 00:07:52.579 is a bit generic. Let's change it. in Mid -Journey 00:07:52.579 --> 00:07:55.279 or Dali -E, if you change the prompt, you get 00:07:55.279 --> 00:07:57.379 a completely new image. The cookie looks different, 00:07:57.480 --> 00:07:59.620 the lighting's all wrong. You lose all the consistency. 00:07:59.800 --> 00:08:01.819 Exactly. But with Manist, you click a button 00:08:01.819 --> 00:08:04.199 that says Edit Text, you type Power Your Morning, 00:08:04.519 --> 00:08:07.339 and the AI swaps the text inside the image while 00:08:07.339 --> 00:08:08.920 keeping the cookie, the lighting, everything 00:08:08.920 --> 00:08:11.720 else exactly the same. Is this basically Photoshop 00:08:11.720 --> 00:08:14.439 inside the chat? It's a visual editor that understands 00:08:14.439 --> 00:08:16.939 text inside images perfectly. No more re -rolling 00:08:16.939 --> 00:08:19.100 the dice. That solves so many workflow headaches. 00:08:19.279 --> 00:08:21.120 Okay, so we've built the app, the game, done 00:08:21.120 --> 00:08:23.720 the research, the strategy, the visuals. Now 00:08:23.720 --> 00:08:26.560 for the big one, the mega prompt. The indoor 00:08:26.560 --> 00:08:29.139 jungle. I love this example. It shows the sheer 00:08:29.139 --> 00:08:31.879 scale of what's possible here. They wanted to 00:08:31.879 --> 00:08:34.460 launch an entire education business, an indoor 00:08:34.460 --> 00:08:37.330 gardening course. And instead of doing it piece 00:08:37.330 --> 00:08:39.470 by piece, they asked for everything at once. 00:08:39.730 --> 00:08:42.590 The audacity of this prompt. They asked for four 00:08:42.590 --> 00:08:46.289 distinct things. A course outline with four modules, 00:08:46.629 --> 00:08:49.529 a five email launch sequence, a 30 -minute sales 00:08:49.529 --> 00:08:52.889 webinar outline, and 10 blog post titles. All 00:08:52.889 --> 00:08:55.090 at once. That's a week's worth of work for a 00:08:55.090 --> 00:08:57.429 human copywriter. How long did it take? About 00:08:57.429 --> 00:08:59.940 10 to 12 minutes. which, yeah, is longer than 00:08:59.940 --> 00:09:02.519 a typical chat response, but it produced a whole 00:09:02.519 --> 00:09:05.059 business in a box. And normally, an AI would 00:09:05.059 --> 00:09:07.279 just choke on that. It would time out or give 00:09:07.279 --> 00:09:10.340 you four short, generic paragraphs. Right. But 00:09:10.340 --> 00:09:12.419 because Manus works in the background, it generated 00:09:12.419 --> 00:09:15.720 these really detailed, deep assets for all four 00:09:15.720 --> 00:09:17.799 deliverables. But the killer feature for me, 00:09:18.279 --> 00:09:20.620 it's the interconnectivity that turned into website 00:09:20.620 --> 00:09:23.169 button. Yes. This is it. So it writes the webinar 00:09:23.169 --> 00:09:25.370 outline, just text. The user highlights that 00:09:25.370 --> 00:09:27.850 text, selects turn into website, and boom, instantly 00:09:27.850 --> 00:09:30.230 it renders a registration landing page connected 00:09:30.230 --> 00:09:32.980 to the site builder based on that text. It actually 00:09:32.980 --> 00:09:35.539 parses the meaning of the text. Yes. It sees 00:09:35.539 --> 00:09:38.200 introduction, so it makes a hero header. It sees 00:09:38.200 --> 00:09:40.519 key learning points, so it creates a bulleted 00:09:40.519 --> 00:09:42.879 list section. It interprets the meaning of the 00:09:42.879 --> 00:09:45.200 text and translates it directly into design elements. 00:09:45.440 --> 00:09:48.399 That's the end of the lorem ipsum placeholder. 00:09:48.919 --> 00:09:51.320 You're designing with real content from day one. 00:09:51.399 --> 00:09:53.960 It's totally seamless. Can you customize the 00:09:53.960 --> 00:09:55.879 website after it's generated? Yes. And again, 00:09:55.960 --> 00:09:57.399 it's just natural language. You don't have to 00:09:57.399 --> 00:09:59.960 touch any CSS. You just tell the chat, make the 00:09:59.960 --> 00:10:02.379 background a lighter mint green, or make that 00:10:02.379 --> 00:10:05.840 headline bigger. And it just updates. The recurring 00:10:05.840 --> 00:10:08.919 theme here seems to be about flow, about removing 00:10:08.919 --> 00:10:11.779 all the little points of friction between I want 00:10:11.779 --> 00:10:15.159 this and here it is. Absolutely. It's just compressing 00:10:15.159 --> 00:10:17.899 the time between your intent and the final execution. 00:10:18.559 --> 00:10:22.899 Sponsor. We are back on the deep dive, exploring 00:10:22.899 --> 00:10:26.600 Manus AI 1 .6 Max. We've walked through the examples, 00:10:26.820 --> 00:10:29.240 Happy Paws, Space Dodger, Green Bites. It's all 00:10:29.240 --> 00:10:31.840 very impressive. But I want to ground this for 00:10:31.840 --> 00:10:33.960 our listeners who might be thinking, OK, I already 00:10:33.960 --> 00:10:36.740 pay for Chad GPT+. Do I really need this? It's 00:10:36.740 --> 00:10:39.480 the million dollar question, right? And the guide 00:10:39.480 --> 00:10:41.960 has a really helpful comparison table that kind 00:10:41.960 --> 00:10:44.480 of visualizes the whole thing. It really boils 00:10:44.480 --> 00:10:46.960 down to three main differences. OK, let's run 00:10:46.960 --> 00:10:49.440 through them. The first one is the role. Right. 00:10:49.580 --> 00:10:51.919 Consultant versus contractor. We touched on this. 00:10:52.419 --> 00:10:56.080 Yeah. Chat GPT talks. Manus builds. If you want 00:10:56.080 --> 00:10:58.580 advice, you get a consultant. If you want a house 00:10:58.580 --> 00:11:00.919 built, you get a contractor. Second is workflow. 00:11:01.340 --> 00:11:03.419 Disconnected versus connected. With the standard 00:11:03.419 --> 00:11:06.500 LLMs, you are the clipboard. You copy the text. 00:11:06.840 --> 00:11:09.200 You paste it into Word. You paste the code into 00:11:09.200 --> 00:11:11.480 your editor. You're the glue holding the entire 00:11:11.480 --> 00:11:14.320 process together. And with Manus? With Manus, 00:11:14.519 --> 00:11:17.409 the data is all synced. The research talks to 00:11:17.409 --> 00:11:19.570 the strategy, which talks to the website builder. 00:11:19.970 --> 00:11:22.269 You aren't the glue anymore. You're the architect. 00:11:22.649 --> 00:11:24.950 And the third one. Editing. It's start over versus 00:11:24.950 --> 00:11:27.789 visual editing. That ability to just tweak the 00:11:27.789 --> 00:11:30.230 text on that cookie image or change the game 00:11:30.230 --> 00:11:31.870 difficulty without having to scrap the whole 00:11:31.870 --> 00:11:34.110 thing and start from scratch, it turns generation 00:11:34.110 --> 00:11:37.250 into iteration. And iteration is where good products 00:11:37.250 --> 00:11:39.370 actually come from. It really feels like we are 00:11:39.370 --> 00:11:41.710 seeing the complete removal of that technical 00:11:41.710 --> 00:11:43.970 wall we talked about. That's the conclusion the 00:11:43.970 --> 00:11:46.470 source draws, and I have to agree. For decades, 00:11:46.789 --> 00:11:49.970 I don't know how to code was a perfectly valid 00:11:49.970 --> 00:11:52.549 reason not to start something. It was a real 00:11:52.549 --> 00:11:54.929 tangible barrier. And now... That barrier is 00:11:54.929 --> 00:11:57.870 gone. It's just evaporated. The only limit now 00:11:57.870 --> 00:12:00.009 is your imagination. You know, as we wrap this 00:12:00.009 --> 00:12:03.330 up, I'm struck by a thought. We spent years, 00:12:03.549 --> 00:12:06.570 a decade really, telling people... Learn to code. 00:12:07.029 --> 00:12:09.090 It was the golden ticket. It was the literacy 00:12:09.090 --> 00:12:12.070 of the 21st century, for sure. But looking at 00:12:12.070 --> 00:12:14.169 this, it feels like the definition of literacy 00:12:14.169 --> 00:12:17.710 is changing. It's not about speaking the machine's 00:12:17.710 --> 00:12:20.210 language anymore. It's about speaking your language 00:12:20.210 --> 00:12:22.350 clearly enough that the machine understands. 00:12:22.750 --> 00:12:26.299 It shifts the premium from how to what. If the 00:12:26.299 --> 00:12:28.379 cost of building something drops to near zero, 00:12:28.799 --> 00:12:31.580 the value of a truly unique idea goes through 00:12:31.580 --> 00:12:34.200 the roof. So it democratizes the build, but it 00:12:34.200 --> 00:12:36.480 meritocratizes the idea. I love that. That's 00:12:36.480 --> 00:12:38.759 perfect. OK. It puts the focus back on human 00:12:38.759 --> 00:12:42.779 creativity and taste and strategy. So for the 00:12:42.779 --> 00:12:44.960 listener who's sitting there, maybe with that 00:12:44.960 --> 00:12:47.480 idea they had in the shower this morning, what's 00:12:47.480 --> 00:12:51.960 the first step? The move is to just start. The 00:12:51.960 --> 00:12:54.639 guide encourages you to use the free credits. 00:12:54.840 --> 00:12:56.679 You don't have to build the next Facebook today. 00:12:56.799 --> 00:12:59.519 Just build a portfolio. Build a silly game for 00:12:59.519 --> 00:13:01.500 your kids. Just get your hands dirty with it. 00:13:01.559 --> 00:13:04.460 Yes. Because once you see your own words turn 00:13:04.460 --> 00:13:07.580 into a real thing, once you type make the rocket 00:13:07.580 --> 00:13:10.820 fly and the rocket actually flies, you will never 00:13:10.820 --> 00:13:13.500 look at technology the same way again. It fundamentally 00:13:13.500 --> 00:13:15.460 changes your relationship with the machine. I 00:13:15.460 --> 00:13:17.000 think that is the perfect place to leave it. 00:13:17.019 --> 00:13:19.559 The wall is down. The tools are here. The rest 00:13:19.559 --> 00:13:21.679 is up to you. Thank you for joining us on this 00:13:21.679 --> 00:13:23.440 deep dive. We'll catch you on the next one. Go 00:13:23.440 --> 00:13:24.120 build something cool.