WEBVTT 00:00:00.000 --> 00:00:03.020 You have probably seen the videos online. BeatBeat, 00:00:03.240 --> 00:00:08.179 an AI tool, builds a flawless, full -stack software 00:00:08.179 --> 00:00:11.179 platform. Yeah, in like 10 seconds on your social 00:00:11.179 --> 00:00:13.480 feed. Right. It looks absolutely incredible. 00:00:13.560 --> 00:00:15.740 I mean, it looks like magic. But when you actually 00:00:15.740 --> 00:00:18.640 sit down at your own keyboard, beat. When you 00:00:18.640 --> 00:00:21.140 try to build something real. Oh, it is a completely 00:00:21.140 --> 00:00:23.500 different story. It is usually a very harsh reality 00:00:23.500 --> 00:00:27.960 check. Two secs silence. Welcome to the deep 00:00:27.960 --> 00:00:29.859 dive. We are really glad you are here with us 00:00:29.859 --> 00:00:31.780 today. Yeah. Thanks for joining us. You know, 00:00:31.859 --> 00:00:35.420 the landscape of AI tools exploded in 2026. Dozens 00:00:35.420 --> 00:00:37.719 of new agentic builders launched this year alone. 00:00:37.939 --> 00:00:39.880 So many. But we want to look past the marketing 00:00:39.880 --> 00:00:42.920 hype. We are putting three of the most talked 00:00:42.920 --> 00:00:45.759 about AI builders to a direct test. Right. Side 00:00:45.759 --> 00:00:49.200 by side. Exactly. We are looking closely at NN, 00:00:49.439 --> 00:00:52.229 Claude Code, and Base 44. Yeah, we really wanted 00:00:52.229 --> 00:00:54.030 to see what happens when the rubber meets the 00:00:54.030 --> 00:00:57.429 road. So we gave all three tools the exact same 00:00:57.429 --> 00:01:00.530 core assignment. We asked them to build an AI 00:01:00.530 --> 00:01:02.750 -powered task manager. Nothing overly bloated. 00:01:02.909 --> 00:01:05.310 Right, nothing crazy, but it needed specific 00:01:05.310 --> 00:01:07.269 functionality. It needed to be a place where 00:01:07.269 --> 00:01:10.230 users can add tasks. They needed to mark those 00:01:10.230 --> 00:01:14.109 tasks as done. And crucially, they needed an 00:01:14.109 --> 00:01:17.450 AI -generated priority ranking feature built 00:01:17.450 --> 00:01:20.430 in. So today, we find out... what they actually 00:01:20.430 --> 00:01:22.950 build for you. We track exactly how long the 00:01:22.950 --> 00:01:25.109 process takes. And we figure out which platform 00:01:25.109 --> 00:01:27.849 actually fits your specific skill level. I mean, 00:01:27.870 --> 00:01:30.269 we want to see the real friction. The kind you 00:01:30.269 --> 00:01:34.030 will actually experience. Yeah. So before we 00:01:34.030 --> 00:01:35.909 try to build a full house, let's look at the 00:01:35.909 --> 00:01:38.310 plumbing. Right, the back end. Exactly. How do 00:01:38.310 --> 00:01:40.790 you handle the back end data securely? That is 00:01:40.790 --> 00:01:42.469 where our first tool comes into the picture. 00:01:42.709 --> 00:01:46.280 We looked at innate end. Now, we gave NAN a slightly 00:01:46.280 --> 00:01:48.299 scoped version of our core assignment. Right. 00:01:48.340 --> 00:01:50.260 And we had to adjust that intentionally because 00:01:50.260 --> 00:01:53.280 NAN is fundamentally an open source workflow 00:01:53.280 --> 00:01:56.599 automation tool. It is brilliant, but asking 00:01:56.599 --> 00:01:59.219 it to build a graphical user -facing app just 00:01:59.219 --> 00:02:02.359 isn't fair. It is outside what the platform is 00:02:02.359 --> 00:02:05.180 designed to do. Exactly. So we asked it to build 00:02:05.180 --> 00:02:08.500 the core logic instead. We prompted it to create 00:02:08.500 --> 00:02:12.259 a workflow for our task lists. A user inputs 00:02:12.259 --> 00:02:15.860 a raw list of daily to -dos. The AI analyzes 00:02:15.860 --> 00:02:19.319 and prioritizes that list. Then, the sorted data 00:02:19.319 --> 00:02:22.139 comes back to the user. So, we're looking at 00:02:22.139 --> 00:02:24.580 raw data movement here. You know, Dan and Ken 00:02:24.580 --> 00:02:27.319 is very famous for using a node -based builder. 00:02:27.500 --> 00:02:29.939 Right. That means a visual interface where you 00:02:29.939 --> 00:02:32.400 connect process steps together like map points. 00:02:32.500 --> 00:02:34.599 Yeah, that is a great way to put it. It's like 00:02:34.599 --> 00:02:37.039 stacking Lego blocks of data. You connect one 00:02:37.039 --> 00:02:39.099 service to another service on a digital campus. 00:02:39.560 --> 00:02:42.080 Exactly. The visual aspect makes complex data 00:02:42.080 --> 00:02:44.719 flows much easier to understand. You literally 00:02:44.719 --> 00:02:47.020 map out the journey of your data. Like a webhook 00:02:47.020 --> 00:02:49.780 node receives the data over here. It passes it 00:02:49.780 --> 00:02:52.819 along to an AI node over there. The AI processes 00:02:52.819 --> 00:02:55.580 it. And then the output flows seamlessly into 00:02:55.580 --> 00:02:57.439 your database or a spreadsheet. You see the whole 00:02:57.439 --> 00:02:59.800 pipeline at a glance. But getting those specific 00:02:59.800 --> 00:03:02.159 blocks to click together smoothly takes real 00:03:02.159 --> 00:03:05.000 effort. Beat. I still wrestle with connecting 00:03:05.000 --> 00:03:07.819 APIs myself. Oh, totally. We all do. It can be 00:03:07.819 --> 00:03:10.759 incredibly frustrating. You miss one little authorization 00:03:10.759 --> 00:03:12.840 header, and everything just breaks down completely. 00:03:13.039 --> 00:03:16.580 The whole pipeline just stops. Exactly. So what 00:03:16.580 --> 00:03:20.759 exactly did Ang8 deliver in our test? Well, it 00:03:20.759 --> 00:03:23.000 took about 10 minutes to complete the workflow, 00:03:23.000 --> 00:03:26.259 and it did succeed. OK, good. It successfully 00:03:26.259 --> 00:03:29.120 pushed the prioritized tasks directly into Google 00:03:29.120 --> 00:03:32.520 Sheets. The AI agent looked at the messy list 00:03:32.520 --> 00:03:35.099 and sorted it logically. But it wasn't perfectly 00:03:35.099 --> 00:03:37.620 smooth. No, the building process was definitely 00:03:37.620 --> 00:03:41.080 not completely smooth for us. The AI's first 00:03:41.080 --> 00:03:44.960 attempt actually missed a basic input form entirely. 00:03:45.240 --> 00:03:47.639 Right. It built the sorting logic but gave us 00:03:47.639 --> 00:03:50.060 no way to actually feed the tasks into it. Yeah, 00:03:50.060 --> 00:03:52.719 exactly. We had to use another prompt to fix 00:03:52.719 --> 00:03:55.379 that oversight. And there were several runtime 00:03:55.379 --> 00:03:57.379 errors we had to solve along the way. Yeah, the 00:03:57.379 --> 00:03:59.240 data formatting was our biggest hurdle there. 00:03:59.580 --> 00:04:02.219 The JSON payload load from the AI node was not 00:04:02.219 --> 00:04:04.120 perfectly aligned with the spreadsheet node. 00:04:04.460 --> 00:04:06.360 Right, I remember that. We spent a good portion 00:04:06.360 --> 00:04:08.159 of those 10 minutes just troubleshooting the 00:04:08.159 --> 00:04:11.960 data structures. NAN is incredibly powerful at 00:04:11.960 --> 00:04:15.060 automating complex back -end processes, but you 00:04:15.060 --> 00:04:17.279 really have to guide it through the exact step 00:04:17.279 --> 00:04:19.839 -by -step logic. It assumes you understand data 00:04:19.839 --> 00:04:22.480 schemas. It really does. So the final result 00:04:22.480 --> 00:04:25.300 was a working back -end workflow system. Yeah. 00:04:25.519 --> 00:04:27.920 But it was absolutely not a finished application. 00:04:28.079 --> 00:04:30.379 No, not at all. There was no front -end interface 00:04:30.379 --> 00:04:32.740 for a user to interact with. There was no user 00:04:32.740 --> 00:04:35.660 login or password system provided. Right. It 00:04:35.660 --> 00:04:37.800 is not something a non -technical user could 00:04:37.800 --> 00:04:41.699 easily publish or monetize. Beat. Right. Let's 00:04:41.699 --> 00:04:44.459 talk about the cost of using this platform. Sure. 00:04:44.819 --> 00:04:47.139 So the pricing model is based mainly on your 00:04:47.139 --> 00:04:49.579 monthly workflow executions. OK. The starter 00:04:49.579 --> 00:04:52.509 plan is 20 euros a month. That gives you 2 ,500 00:04:52.509 --> 00:04:55.850 workload executions and unlimited users. It scales 00:04:55.850 --> 00:04:58.129 all the way up to their business plan. That sits 00:04:58.129 --> 00:05:02.850 at 667 euros a month. Wow. Yeah, that tier includes 00:05:02.850 --> 00:05:06.050 40 ,000 executions and specific self -hosting 00:05:06.050 --> 00:05:07.910 options. Well, let me push back on this a bit. 00:05:07.910 --> 00:05:10.569 Sure. If it didn't build an actual app, why use 00:05:10.569 --> 00:05:13.209 it? Why spend the time troubleshooting JSON formatting? 00:05:13.670 --> 00:05:16.329 Because it gives technical teams absolute control 00:05:16.329 --> 00:05:19.170 over backend pipelines. OK. You know exactly 00:05:19.170 --> 00:05:21.370 where every single piece of data is going. There 00:05:21.370 --> 00:05:24.310 are no black boxes. If you already have existing 00:05:24.310 --> 00:05:27.610 services like a CRM, a database, and an email 00:05:27.610 --> 00:05:29.870 sender, you just connect them together. Right. 00:05:30.069 --> 00:05:31.910 You are essentially building the nervous system 00:05:31.910 --> 00:05:34.990 of your business operations, you do not need 00:05:34.990 --> 00:05:37.269 it to look pretty on the outside. You just need 00:05:37.269 --> 00:05:40.250 it to route information flawlessly. Precisely. 00:05:40.470 --> 00:05:43.009 It handles the invisible heavy lifting securely 00:05:43.009 --> 00:05:45.370 behind the scenes. So it automates the backend 00:05:45.370 --> 00:05:48.009 data, not the actual user interface. Vixirate. 00:05:48.189 --> 00:05:51.279 Two -sec silence. Well, if Anand only handles 00:05:51.279 --> 00:05:54.379 the backend pipelines, what happens next? What 00:05:54.379 --> 00:05:56.360 if you actually want the walls, the roof, and 00:05:56.360 --> 00:05:59.339 the paint? What if you want an AI to write the 00:05:59.339 --> 00:06:03.279 entire code base for a real full stack app? Then 00:06:03.279 --> 00:06:05.660 we step into the world of Claude code. Okay. 00:06:05.819 --> 00:06:08.500 This is Anthropic's major entry into the developer 00:06:08.500 --> 00:06:11.720 space. Claude code is an agentic coding tool. 00:06:11.879 --> 00:06:14.399 Let's define that. Yeah, that means an AI that 00:06:14.399 --> 00:06:17.339 writes, runs, and fixes code entirely on its 00:06:17.339 --> 00:06:20.560 own. Let's unpack that process. You don't have 00:06:20.560 --> 00:06:22.779 to hold its hand through every single line of 00:06:22.779 --> 00:06:25.240 code. No, you don't. You accessed it through 00:06:25.240 --> 00:06:27.420 a terminal interface. Yeah. You give it a plain 00:06:27.420 --> 00:06:29.939 English prompt, and it starts working autonomously. 00:06:30.240 --> 00:06:34.759 Whoa. Imagine an AI checking its own errors without 00:06:34.759 --> 00:06:37.839 human input. It is wild. It really is. It reads 00:06:37.839 --> 00:06:40.660 your prompt. It plans the architectural build. 00:06:40.800 --> 00:06:43.240 It starts writing the actual files into your 00:06:43.240 --> 00:06:46.819 directory. Then it runs a test. If it sees a 00:06:46.819 --> 00:06:49.579 bug in the terminal stack trace, it catches it 00:06:49.579 --> 00:06:51.819 and corrects the code immediately. It loops through 00:06:51.819 --> 00:06:55.319 this process. Exactly. That is a massive paradigm 00:06:55.319 --> 00:06:57.420 shift for software development. Well, we gave 00:06:57.420 --> 00:07:00.879 Cloud Code a A single detailed prompt for our 00:07:00.879 --> 00:07:03.560 test. We asked for a minimal task manager web 00:07:03.560 --> 00:07:05.680 app. Right. We specified that we wanted user 00:07:05.680 --> 00:07:08.339 authentication and our AI prioritization feature 00:07:08.339 --> 00:07:11.000 included. And it took about 15 minutes to finish 00:07:11.000 --> 00:07:14.339 the entire build. Which is fast. Very fast. It 00:07:14.339 --> 00:07:15.860 returned a working app that it independently 00:07:15.860 --> 00:07:18.819 named Taskflow, and the front -end results were 00:07:18.819 --> 00:07:20.639 genuinely impressive to look at. They really 00:07:20.639 --> 00:07:23.740 were. It built a sleek, dark -themed dashboard 00:07:23.740 --> 00:07:27.899 with a very clean sidebar menu. It included a 00:07:27.899 --> 00:07:30.279 solid task input field with a functional date 00:07:30.279 --> 00:07:32.899 picker. It even added a priority drop -down menu 00:07:32.899 --> 00:07:35.759 and custom tag support. It built filter tabs 00:07:35.759 --> 00:07:39.100 so users could toggle between active, done, and 00:07:39.100 --> 00:07:42.180 critical tasks. And it successfully integrated 00:07:42.180 --> 00:07:44.980 working user authentication into the app. But 00:07:44.980 --> 00:07:47.800 again, the experience was not entirely without 00:07:47.800 --> 00:07:50.600 friction. Building the code is one thing. Making 00:07:50.600 --> 00:07:53.259 the external services talk to each other is another. 00:07:53.399 --> 00:07:56.639 Right, the API setup. Yeah, the AI prioritization 00:07:56.639 --> 00:07:59.439 feature required manual configuration from us. 00:07:59.959 --> 00:08:02.500 Claude wrote the function, but we had to source 00:08:02.500 --> 00:08:05.579 an external API key for the AI model ourselves. 00:08:05.720 --> 00:08:08.500 We had to plug that key into the local environment 00:08:08.500 --> 00:08:10.779 variables manually. The tool could not safely 00:08:10.779 --> 00:08:13.180 secure or provision that API key on its own. 00:08:13.290 --> 00:08:15.329 No, it couldn't. And then we hit a significant 00:08:15.329 --> 00:08:17.310 issue with actually sharing the project. Oh, 00:08:17.470 --> 00:08:20.170 the GitHub issue? Right. It attempted to push 00:08:20.170 --> 00:08:22.870 the final code base to GitHub automatically for 00:08:22.870 --> 00:08:25.430 us, but it was blocked by missing write permissions 00:08:25.430 --> 00:08:28.129 on our account. Right. And this is a crucial 00:08:28.129 --> 00:08:30.990 security mechanism. Repositories have strict 00:08:30.990 --> 00:08:35.169 OAuth scopes. Security protocols actively stopped 00:08:35.169 --> 00:08:37.730 the AI from altering the repository directly. 00:08:38.309 --> 00:08:41.129 It did not have the required authentication token 00:08:41.129 --> 00:08:43.570 to push the code live. So it gracefully failed 00:08:43.570 --> 00:08:46.990 that step. Exactly. The app was fully built locally 00:08:46.990 --> 00:08:49.769 on our machine. It worked beautifully on local 00:08:49.769 --> 00:08:52.649 hosts. It was not shareable. No, it was not hosted 00:08:52.649 --> 00:08:54.789 on the live internet. We would have to configure 00:08:54.789 --> 00:08:57.710 those deployment settings and SSH keys manually 00:08:57.710 --> 00:09:01.149 ourselves. The pricing for Claude Code is fairly 00:09:01.149 --> 00:09:03.669 straightforward right now. It is $20 a month 00:09:03.669 --> 00:09:06.750 for the pro plan. Right. That seems to be the 00:09:06.750 --> 00:09:09.129 practical starting point for most active developers 00:09:09.129 --> 00:09:12.029 utilizing these agentic workflows. But I have 00:09:12.029 --> 00:09:14.759 to ask, this sounds amazing. But isn't it still 00:09:14.759 --> 00:09:17.179 just for seasoned developers? Honestly, yes. 00:09:17.320 --> 00:09:19.919 It really does require existing code base and 00:09:19.919 --> 00:09:23.320 API management skills. You need to know how environment 00:09:23.320 --> 00:09:25.500 variables actually work in a local directory. 00:09:25.899 --> 00:09:28.100 You need to understand how to read and fix GitHub 00:09:28.100 --> 00:09:30.600 permission errors when they pop up. Claude code 00:09:30.600 --> 00:09:33.240 builds the application code itself, but you still 00:09:33.240 --> 00:09:35.120 have to manage the surrounding infrastructure. 00:09:35.379 --> 00:09:37.919 Great for developers, but brings its own technical 00:09:37.919 --> 00:09:41.000 setup hurdles. Precisely. You have to be deeply 00:09:41.000 --> 00:09:43.179 comfortable navigating a terminal environment. 00:09:43.440 --> 00:09:46.320 Two sec silence. So we've seen backend automation 00:09:46.320 --> 00:09:49.500 with NAAN. We've seen local code generation with 00:09:49.500 --> 00:09:53.559 Claude code. Both of those paths require a distinct 00:09:53.559 --> 00:09:56.120 level of technical comfort. You have to understand 00:09:56.120 --> 00:09:59.500 data structures or terminal commands. Definitely. 00:09:59.759 --> 00:10:01.740 But what if you just want to skip the infrastructure 00:10:01.740 --> 00:10:04.240 entirely? What if you just want to ship a live 00:10:04.240 --> 00:10:07.649 product right now? That is where our third tool, 00:10:07.929 --> 00:10:10.750 Base 44, enters the conversation today. OK. Base 00:10:10.750 --> 00:10:13.450 44 is designed specifically for non -technical 00:10:13.450 --> 00:10:16.029 builders and founders. It creates full stack 00:10:16.029 --> 00:10:18.789 web applications entirely from plain English 00:10:18.789 --> 00:10:22.009 descriptions. And crucially, it handles everything 00:10:22.009 --> 00:10:24.769 inside one single unified platform. You know, 00:10:24.769 --> 00:10:26.830 there is some really interesting business context 00:10:26.830 --> 00:10:29.509 behind this specific tool. Base 44 was actually 00:10:29.509 --> 00:10:32.669 acquired by Wix back in June of 2025. Right. 00:10:32.889 --> 00:10:34.970 They bought the platform for approximately $80 00:10:34.970 --> 00:10:37.100 million. million dollars. Which is a huge deal. 00:10:37.360 --> 00:10:40.299 It is, but it still operates under its own name 00:10:40.299 --> 00:10:44.840 and domain today. It has not been heavily rebranded 00:10:44.840 --> 00:10:47.399 into the main Wix ecosystem. Yeah, that is interesting. 00:10:47.639 --> 00:10:50.580 Well, we gave Base 44 the exact same task manager 00:10:50.580 --> 00:10:53.000 assignment. We asked for the user interface, 00:10:53.179 --> 00:10:56.639 the filter tabs, and the AI sorting button, and 00:10:56.639 --> 00:10:58.860 the results were incredibly fast compared to 00:10:58.860 --> 00:11:01.399 the other platforms. Very fast. It took just 00:11:01.399 --> 00:11:03.700 under five minutes from a single prompt to a 00:11:03.700 --> 00:11:07.259 finished product. It built a live, complete web 00:11:07.259 --> 00:11:11.639 app that it named Zenith Tasks. And the experience 00:11:11.639 --> 00:11:14.139 was remarkably frictionless from start to finish. 00:11:14.519 --> 00:11:16.940 Completely. Let's talk about the setup. It handled 00:11:16.940 --> 00:11:19.139 the user authentication automatically at the 00:11:19.139 --> 00:11:21.259 platform level. Great. We did not even need to 00:11:21.259 --> 00:11:23.639 prompt it to build a login screen. It just knew 00:11:23.639 --> 00:11:26.460 an app needs secure logins. And because it operates 00:11:26.460 --> 00:11:29.100 in a closed ecosystem, the built -in AI connected 00:11:29.100 --> 00:11:31.500 perfectly without any external setup. Which is 00:11:31.500 --> 00:11:33.519 huge. Yeah. There was no need for us to hunt 00:11:33.519 --> 00:11:36.559 down an external open AI key. There were no complex 00:11:36.559 --> 00:11:38.919 environment variables to configure locally. There 00:11:38.919 --> 00:11:41.559 were no GitHub permission issues blocking the 00:11:41.559 --> 00:11:44.679 deployment process. The hosting was handled entirely 00:11:44.679 --> 00:11:48.159 inside the base 44 platform itself. It leverages 00:11:48.159 --> 00:11:51.289 that massive under underlying hosting infrastructure. 00:11:52.009 --> 00:11:53.649 Exactly. The resulting interface was polished. 00:11:54.289 --> 00:11:57.750 It had clear, active, and done tabs for organizing 00:11:57.750 --> 00:12:01.549 the tasks. It featured satisfying visual strikethroughs 00:12:01.549 --> 00:12:04.330 for all your completed items. And it placed a 00:12:04.330 --> 00:12:08.360 very prominent AI prioritize button. Right in 00:12:08.360 --> 00:12:10.539 corner. Yeah, that button was great. You just 00:12:10.539 --> 00:12:12.360 click the button, the app thinks for a second, 00:12:12.440 --> 00:12:14.500 and the list sorts itself immediately based on 00:12:14.500 --> 00:12:17.320 urgency. And the app was live immediately. It 00:12:17.320 --> 00:12:19.779 was previewable and ready to publish instantly. 00:12:20.419 --> 00:12:22.840 You just copy and share the URL and people can 00:12:22.840 --> 00:12:25.179 start using your software. The pricing model 00:12:25.179 --> 00:12:27.580 makes it very accessible for rapid prototyping 00:12:27.580 --> 00:12:30.559 and testing ideas. It is completely free to start 00:12:30.559 --> 00:12:33.440 building on the platform. If you want more features, 00:12:33.659 --> 00:12:36.500 the starter plan is $16 .90 a month billed annually. 00:12:37.159 --> 00:12:39.960 Sounds incredibly smooth. But let's look at the 00:12:39.960 --> 00:12:43.000 reality here. If it's this fast and it handles 00:12:43.000 --> 00:12:45.980 all the hosting, what are you sacrificing? Well, 00:12:46.039 --> 00:12:47.899 you are definitely making a fundamental trade 00:12:47.899 --> 00:12:50.580 -off here. You trade underlying code ownership 00:12:50.580 --> 00:12:53.360 and custom architecture for pure speed. Okay. 00:12:53.600 --> 00:12:56.000 You are locked into their specific ecosystem. 00:12:56.379 --> 00:12:58.980 You cannot easily export the React code base 00:12:58.980 --> 00:13:01.860 and host it elsewhere like Vercell or AWS. Right. 00:13:02.039 --> 00:13:04.379 You are tied to their proprietary infrastructure 00:13:04.379 --> 00:13:07.120 and their database decisions. Fastest to launch, 00:13:07.360 --> 00:13:09.980 but you do not own the underlying code. Exactly. 00:13:10.159 --> 00:13:12.419 You are essentially renting the infrastructure 00:13:12.419 --> 00:13:15.889 to get your idea live instantly. Let's pause 00:13:15.889 --> 00:13:19.450 right here. Insert provided mid -roll sponsor 00:13:19.450 --> 00:13:22.190 read here. Do not pull any promotional material 00:13:22.190 --> 00:13:25.110 from the newsletter text. And we are back. All 00:13:25.110 --> 00:13:27.049 right. Let's synthesize everything we have covered 00:13:27.049 --> 00:13:29.830 in this deep dive today. The landscape of AI 00:13:29.830 --> 00:13:32.889 tools is evolving incredibly fast. It really 00:13:32.889 --> 00:13:35.889 is. But testing these three specific platforms 00:13:35.889 --> 00:13:39.720 in 2026. is very revealing. Choosing an AI agent 00:13:39.720 --> 00:13:42.740 tool isn't just about which AI model is technically 00:13:42.740 --> 00:13:44.799 the smartest anymore. No, it really isn't. The 00:13:44.799 --> 00:13:46.840 raw intelligence of the major models is somewhat 00:13:46.840 --> 00:13:50.139 commoditized now. They can all write decent code. 00:13:50.460 --> 00:13:53.220 The real choice you have to make is about your 00:13:53.220 --> 00:13:56.559 appetite for infrastructure. It is about how 00:13:56.559 --> 00:13:59.059 much technical setup and maintenance you are 00:13:59.059 --> 00:14:01.580 actually willing to handle. You have to match 00:14:01.580 --> 00:14:04.639 the tool to your own operational capabilities. 00:14:05.120 --> 00:14:07.299 Let's break down the core takeaways for you based 00:14:07.299 --> 00:14:10.419 on this experiment. Sure. If you need to connect 00:14:10.419 --> 00:14:13.659 existing tools together efficiently, you should 00:14:13.659 --> 00:14:17.419 use NAN. It gives you ultimate granular control 00:14:17.659 --> 00:14:20.580 over your backend data flows. It is the absolute 00:14:20.580 --> 00:14:24.259 clear winner for automating repetitive, invisible 00:14:24.259 --> 00:14:26.879 backend processes. Right. You just have to be 00:14:26.879 --> 00:14:29.019 comfortable working with visual logic nodes and 00:14:29.019 --> 00:14:31.340 troubleshooting data payloads. And if you want 00:14:31.340 --> 00:14:33.759 full ownership of a custom code base, use Cloud 00:14:33.759 --> 00:14:36.919 Code. Yes. It gives you a real exportable, full 00:14:36.919 --> 00:14:39.340 stack application environment that you... completely 00:14:39.340 --> 00:14:41.200 control. But you just have to accept some setup 00:14:41.200 --> 00:14:42.940 friction along the way. You have to manage your 00:14:42.940 --> 00:14:46.000 own API keys. You have to manage your repository 00:14:46.000 --> 00:14:48.639 permissions. But at the end of the day, you own 00:14:48.639 --> 00:14:51.559 every single line of that final generated code. 00:14:51.820 --> 00:14:53.980 And finally, if you just want to turn an idea 00:14:53.980 --> 00:14:57.779 into a live URL immediately, use Base 44. Yeah. 00:14:57.980 --> 00:15:01.360 It is perfectly designed for founders who want 00:15:01.360 --> 00:15:04.019 to move incredibly fast. You skip all the complex 00:15:04.019 --> 00:15:06.059 infrastructure decisions, you deploy a working 00:15:06.059 --> 00:15:09.080 product in minutes, you sacrifice total code 00:15:09.080 --> 00:15:11.440 -based ownership, but you gain immediate market 00:15:11.440 --> 00:15:14.320 validation. And sometimes speed is the most important 00:15:14.320 --> 00:15:16.419 feature. It is time to put this knowledge into 00:15:16.419 --> 00:15:19.639 practice today. Pick just one of these tools 00:15:19.639 --> 00:15:23.620 that matches your skill level right now. Do not 00:15:23.620 --> 00:15:25.860 try to learn all three platforms at the exact 00:15:25.860 --> 00:15:28.549 same time. Try building a very simple one page 00:15:28.549 --> 00:15:31.590 project this weekend. Yeah. Keep the scope incredibly 00:15:31.590 --> 00:15:34.009 small for your very first attempt. Right. Build 00:15:34.009 --> 00:15:36.549 a habit tracker or a simple form. Experience 00:15:36.549 --> 00:15:38.750 the workflow firsthand and see exactly where 00:15:38.750 --> 00:15:41.549 you personally encounter friction. Two sec silence. 00:15:41.820 --> 00:15:43.679 I want to leave you with a final thought to consider. 00:15:43.960 --> 00:15:46.620 Platforms like Base 44 can spin up fully hosted, 00:15:46.860 --> 00:15:49.460 authenticated web apps. They do it in five minutes 00:15:49.460 --> 00:15:52.559 from simple, plain English prompts. The authentication, 00:15:52.960 --> 00:15:55.759 the database routing, and the UI are all handled 00:15:55.759 --> 00:15:59.320 perfectly for you. So what does it actually mean 00:15:59.320 --> 00:16:03.740 to be a developer in the future? Us. If these 00:16:03.740 --> 00:16:06.360 tools... handle all the underlying code generation 00:16:06.360 --> 00:16:09.080 for us is the most valuable technical skill in 00:16:09.080 --> 00:16:11.500 the world, simply knowing exactly what to ask 00:16:11.500 --> 00:16:15.299 for. Thank you for joining us on this Keep Dive. 00:16:15.379 --> 00:16:17.139 Keep questioning, keep exploring, and we will 00:16:17.139 --> 00:16:17.840 see you next time.