WEBVTT 00:00:00.000 --> 00:00:02.759 So you've just spent, what, weeks, maybe months, 00:00:02.940 --> 00:00:05.360 mastering a powerful automation tool, something 00:00:05.360 --> 00:00:07.679 like NAN. Yeah, you know the basics. You get 00:00:07.679 --> 00:00:10.019 the nodes, the triggers. And you build that first 00:00:10.019 --> 00:00:12.480 simple workflow. It sends a good morning message 00:00:12.480 --> 00:00:16.800 to your team on Slack. And that workflow, it 00:00:16.800 --> 00:00:19.960 proves you learned the syntax. But it doesn't 00:00:19.960 --> 00:00:22.980 solve any real problem. It has no value. And 00:00:22.980 --> 00:00:26.019 why so fascinating is that pivot? How do you 00:00:26.019 --> 00:00:28.500 get from that cool demo, from what we call tutorial 00:00:28.500 --> 00:00:31.899 hell, to building something robust? Something 00:00:31.899 --> 00:00:33.960 that's actually production ready. A system that 00:00:33.960 --> 00:00:36.280 actually earns you money or saves you real time. 00:00:36.460 --> 00:00:38.740 That's the jump, isn't it? The one from student 00:00:38.740 --> 00:00:40.740 to professional builder. And that is exactly 00:00:40.740 --> 00:00:43.539 the challenge we're diving into today. Our sources 00:00:43.539 --> 00:00:46.500 gave us this really... detailed map for it. A 00:00:46.500 --> 00:00:49.340 blueprint, really. For escaping that trap after 00:00:49.340 --> 00:00:51.320 you learn a tool like an ENAN, you know, that 00:00:51.320 --> 00:00:53.479 visual node platform. It's all about direction, 00:00:53.600 --> 00:00:56.020 not just effort. Yeah. You have to think about 00:00:56.020 --> 00:00:57.560 this strategically. I like the drill metaphor. 00:00:57.799 --> 00:01:00.280 Oh, the drill metaphor. Yeah. Right. Owning a 00:01:00.280 --> 00:01:02.500 really high quality power drill is great. You 00:01:02.500 --> 00:01:04.680 know how it works, how it spins. But it only 00:01:04.680 --> 00:01:07.120 creates value when you actually use it to build 00:01:07.120 --> 00:01:09.400 something. Something that's functional. That 00:01:09.400 --> 00:01:11.939 can stand up to some stress. That's it. That's 00:01:11.939 --> 00:01:14.040 how you turn these skills into tangible assets. 00:01:14.590 --> 00:01:17.129 OK, so let's unpack this. Our mission here is 00:01:17.129 --> 00:01:20.030 to distill this down to five immediate high impact 00:01:20.030 --> 00:01:22.909 actions you can take right now. To make sure 00:01:22.909 --> 00:01:25.590 that Indian knowledge actually translates. Exactly. 00:01:25.590 --> 00:01:28.510 We're building a foundation for, you know, being 00:01:28.510 --> 00:01:32.349 a real authority in this space come 2026. So 00:01:32.349 --> 00:01:34.150 let's start with the first thing, the absolute 00:01:34.150 --> 00:01:37.359 foundation. The sources are incredibly blunt 00:01:37.359 --> 00:01:40.140 about this. The biggest mistake beginners make 00:01:40.140 --> 00:01:42.540 is immediately trying to sell their skills. They 00:01:42.540 --> 00:01:44.480 launch an agency or they try to build these huge 00:01:44.480 --> 00:01:47.340 complex client systems. Right. They try to automate 00:01:47.340 --> 00:01:49.659 problems they don't really truly understand. 00:01:49.980 --> 00:01:51.980 And that's the key. So before you build anything 00:01:51.980 --> 00:01:53.920 for anyone else, you have to automate something 00:01:53.920 --> 00:01:57.480 you hate doing. The selfish rule. Fix the pain 00:01:57.480 --> 00:02:00.379 in your own house first. And when you do that. 00:02:00.780 --> 00:02:03.200 When you live inside your own automation, you 00:02:03.200 --> 00:02:05.739 really start to see where it fails. It guarantees 00:02:05.739 --> 00:02:08.159 two things. One, you already know all the weird 00:02:08.159 --> 00:02:11.759 edge cases, the frustrating parts. And two, you're 00:02:11.759 --> 00:02:14.580 guaranteed to actually use it and, more importantly, 00:02:14.780 --> 00:02:17.599 to maintain it. That maintenance part, that's 00:02:17.599 --> 00:02:19.780 where the real learning happens, in the mess 00:02:19.780 --> 00:02:22.280 of your own business data, not some clean tutorial 00:02:22.280 --> 00:02:25.930 example. So to pick the right target, the sources 00:02:25.930 --> 00:02:27.909 have this simple metric. It's called the Payne 00:02:27.909 --> 00:02:30.810 score test. This just rates a task from 1 to 00:02:30.810 --> 00:02:34.909 10 across four different criteria. Time wasted, 00:02:35.169 --> 00:02:38.030 frequency, frustration, and complexity. The whole 00:02:38.030 --> 00:02:40.849 idea is to just quantify how much that manual 00:02:40.849 --> 00:02:43.150 task is costing you. So let's say you have a 00:02:43.150 --> 00:02:45.330 task you do every day. So frequency is a 10. 00:02:45.509 --> 00:02:48.069 It takes you 40 minutes. So time wasted is an 00:02:48.069 --> 00:02:50.349 8. It makes you want to pull your hair out. So 00:02:50.349 --> 00:02:52.930 frustration is a 9. But it's pretty simple to 00:02:52.930 --> 00:02:54.969 do. Just annoying. So complexity is maybe a 3. 00:02:55.169 --> 00:02:57.370 Right. You add that up and you get a pain score 00:02:57.370 --> 00:03:00.289 of 30. And if that score is over 30, that's your 00:03:00.289 --> 00:03:03.379 target. You build that workflow today. That fixed 00:03:03.379 --> 00:03:06.319 build forces you to deal with real -world errors, 00:03:06.560 --> 00:03:10.060 real problems. That's the only true way to learn 00:03:10.060 --> 00:03:12.240 this stuff. Abandoned practice projects just 00:03:12.240 --> 00:03:14.300 don't teach you resilience. The data's too clean. 00:03:14.580 --> 00:03:17.599 We're talking about small, powerful wins here. 00:03:17.919 --> 00:03:21.340 Like an auto -invoicing system for a designer 00:03:21.340 --> 00:03:24.620 when a project in Notion gets marked done. Or 00:03:24.620 --> 00:03:27.520 a creator who pulls their YouTube analytics into 00:03:27.520 --> 00:03:30.340 a Google Sheet every Monday morning. Simple things 00:03:30.340 --> 00:03:32.930 that solve a real recurring pain. But there's 00:03:32.930 --> 00:03:35.469 a really crucial rule here, a cautionary tale 00:03:35.469 --> 00:03:38.789 almost. Yeah. Do not try to automate a process 00:03:38.789 --> 00:03:40.949 you haven't done manually at least 10 times. 00:03:40.969 --> 00:03:42.810 And that's so important. If you automate a process 00:03:42.810 --> 00:03:45.669 too early, you just end up automating a bad process. 00:03:45.849 --> 00:03:48.030 You make an inefficient thing go faster. Cleaning 00:03:48.030 --> 00:03:50.759 that up later takes 10 times as long. So if that 00:03:50.759 --> 00:03:53.199 selfish rule is so critical, what does automating 00:03:53.199 --> 00:03:55.439 for yourself teach you that just reading the 00:03:55.439 --> 00:03:58.180 documentation can't? It teaches resilience and 00:03:58.180 --> 00:04:00.900 real -world error management under true pressure. 00:04:01.099 --> 00:04:03.099 Okay, so you've solved your own pain. Now what? 00:04:03.819 --> 00:04:06.240 The challenge shifts from just doing automation 00:04:06.240 --> 00:04:09.259 to actually managing it. Which brings us to essential 00:04:09.259 --> 00:04:12.599 action number two, building your automation portfolio. 00:04:13.289 --> 00:04:15.490 This is what separates people who build one -off 00:04:15.490 --> 00:04:18.029 scripts from those who build actual careers. 00:04:18.350 --> 00:04:21.290 It's a strategic shift. You move beyond these 00:04:21.290 --> 00:04:23.430 isolated little flows. And you start building 00:04:23.430 --> 00:04:26.889 a searchable, reusable library of your work. 00:04:27.050 --> 00:04:29.850 And this is not a client showcase. It's your 00:04:29.850 --> 00:04:32.829 personal inventory of building blocks. The sources 00:04:32.829 --> 00:04:35.170 called it an automation factory, which I think 00:04:35.170 --> 00:04:37.170 is a perfect metaphor. It is. You're creating 00:04:37.170 --> 00:04:40.500 these standard... repeatable patterns that you 00:04:40.500 --> 00:04:43.100 can just remix for new problems later on. So 00:04:43.100 --> 00:04:45.360 if you have a workflow that connects a Google 00:04:45.360 --> 00:04:47.899 sheet to a Slack alert. You don't rebuild that 00:04:47.899 --> 00:04:50.540 every single time. You save it. It becomes a 00:04:50.540 --> 00:04:52.720 standard component in your factory. So you focus 00:04:52.720 --> 00:04:55.339 on these repeatable units, data collection, alerts, 00:04:55.579 --> 00:04:58.639 business ops, like invoicing or CRM updates. 00:04:58.860 --> 00:05:01.939 Exactly. And then 80 % of any new project is 00:05:01.939 --> 00:05:03.910 just simple remixing. You're not starting from 00:05:03.910 --> 00:05:05.769 scratch. But that all comes down to organization, 00:05:06.029 --> 00:05:08.290 which sounds boring. It sounds boring, but it's 00:05:08.290 --> 00:05:10.649 the professional's secret weapon. Your flows 00:05:10.649 --> 00:05:13.110 have to be simple and searchable. So how do people 00:05:13.110 --> 00:05:15.230 actually do this? You could use a GitHub repo, 00:05:15.430 --> 00:05:18.430 right? Like an automation library. Or just a 00:05:18.430 --> 00:05:21.170 simple Notion database with columns for the name, 00:05:21.189 --> 00:05:24.129 the use case, and a link to the workflow's JSON 00:05:24.129 --> 00:05:27.430 file. Or you could just use... NNN's own internal 00:05:27.430 --> 00:05:30.170 folders and tags, something like data inbound 00:05:30.170 --> 00:05:33.129 or finance outbound. The key, though, is the 00:05:33.129 --> 00:05:36.920 external part. Export to JSON. Write a quick, 00:05:37.040 --> 00:05:39.639 clear explanation of what it does and where it 00:05:39.639 --> 00:05:41.779 might fail. Store that somewhere you can find 00:05:41.779 --> 00:05:43.939 it. That is professional workflow management. 00:05:44.220 --> 00:05:46.660 And that also helps if you need to bring someone 00:05:46.660 --> 00:05:49.480 else in to help or if you go on vacation, your 00:05:49.480 --> 00:05:51.959 business doesn't grind to a halt. So how much 00:05:51.959 --> 00:05:54.120 time does proper organization like that really 00:05:54.120 --> 00:05:56.639 save you in the long run? Reusing a documented 00:05:56.639 --> 00:05:58.839 workflow takes minutes, fundamentally avoiding 00:05:58.839 --> 00:06:01.240 hours of rebuilding and troubleshooting. All 00:06:01.240 --> 00:06:03.180 right, our third essential action is all about 00:06:03.180 --> 00:06:05.800 the speed limit of learning. It's about communities. 00:06:06.120 --> 00:06:08.259 Because if you try to learn this stuff in a vacuum, 00:06:08.439 --> 00:06:11.379 in isolation, you're going to hit a wall. Inevitably. 00:06:11.980 --> 00:06:14.319 You'll get stuck on some complex problem. You'll 00:06:14.319 --> 00:06:17.220 search for hours using the wrong keywords. And 00:06:17.220 --> 00:06:19.540 then you just kind of give up. You plateau. We've 00:06:19.540 --> 00:06:22.519 all been there. The fix is pretty simple. Join 00:06:22.519 --> 00:06:24.540 the communities where people are actually building 00:06:24.540 --> 00:06:27.279 and breaking things. The official NEN forum, 00:06:27.560 --> 00:06:30.579 certain Discord channels, engaging with experts 00:06:30.579 --> 00:06:33.589 on YouTube. These places are where you get a 00:06:33.589 --> 00:06:35.689 sanity check when you need it. But the sources 00:06:35.689 --> 00:06:39.189 warn about this lurker trap. Ah, yes. Where you 00:06:39.189 --> 00:06:42.129 join, you save a bunch of posts, download some 00:06:42.129 --> 00:06:43.930 workflows. And you tell yourself you'll get to 00:06:43.930 --> 00:06:46.149 it later. But you never actually apply it, so 00:06:46.149 --> 00:06:48.689 you stay in that student mindset. But isn't just 00:06:48.689 --> 00:06:51.209 listening the most efficient way to learn? I 00:06:51.209 --> 00:06:53.970 mean, why should I spend my time answering basic 00:06:53.970 --> 00:06:56.470 questions for other people? It feels efficient, 00:06:56.629 --> 00:06:59.490 but it's passive. You don't truly own a concept 00:06:59.490 --> 00:07:01.389 until you have to explain it to someone else. 00:07:01.550 --> 00:07:04.189 And honestly, we all struggle. I still wrestle 00:07:04.189 --> 00:07:07.230 with prompt drift myself when I'm building complex 00:07:07.230 --> 00:07:09.790 automations. Okay, for clarity, what do you mean 00:07:09.790 --> 00:07:12.240 by prompt drift here? It's when an AI driven 00:07:12.240 --> 00:07:15.759 workflow or any complex chain of logic, it just 00:07:15.759 --> 00:07:19.319 slowly loses focus. It starts off answering your 00:07:19.319 --> 00:07:21.459 prompt, but by step seven, it's talking about 00:07:21.459 --> 00:07:23.839 something else entirely. Right. And having a 00:07:23.839 --> 00:07:26.480 community to sanity check that kind of complex 00:07:26.480 --> 00:07:30.620 logic is just, it's essential. Which makes that 00:07:30.620 --> 00:07:33.540 shift from consuming to contributing so important. 00:07:34.000 --> 00:07:36.959 The sources suggest this contribution rule. For 00:07:36.959 --> 00:07:39.360 every three questions you ask, answer one for 00:07:39.360 --> 00:07:41.660 somebody else. Because teaching is the fastest 00:07:41.660 --> 00:07:44.360 way to master something. It forces you to check 00:07:44.360 --> 00:07:46.800 your own knowledge. Plus, it builds your reputation. 00:07:47.399 --> 00:07:49.360 Experts are way more likely to help you with 00:07:49.360 --> 00:07:51.639 a really tricky problem if they've seen you helping 00:07:51.639 --> 00:07:53.800 others. And there's a huge difference in how 00:07:53.800 --> 00:07:56.050 you share. Professionals share workflows that 00:07:56.050 --> 00:07:59.189 solved a specific thorny problem. They don't 00:07:59.189 --> 00:08:01.110 just post a screenshot of an error and say, what's 00:08:01.110 --> 00:08:02.870 wrong? That's just asking for free consulting. 00:08:03.050 --> 00:08:06.009 Right. So why is it so dangerous to just lurk 00:08:06.009 --> 00:08:09.209 and save posts without ever contributing? Lurking 00:08:09.209 --> 00:08:11.730 keeps you in passive student mode and actively 00:08:11.730 --> 00:08:15.290 prevents true conceptual mastery. Sponsor. So 00:08:15.290 --> 00:08:17.550 once you've automated your own pain and you're 00:08:17.550 --> 00:08:20.209 active in the community, it's time for action 00:08:20.209 --> 00:08:23.740 number four, the portfolio project. And this 00:08:23.740 --> 00:08:25.860 is what moves you into professional territory 00:08:25.860 --> 00:08:28.339 because now you're building to solve problems 00:08:28.339 --> 00:08:30.240 for other people. And you have to manage all 00:08:30.240 --> 00:08:33.419 the complexity that comes with that with external 00:08:33.419 --> 00:08:35.899 users. This is really the strongest proof of 00:08:35.899 --> 00:08:38.500 your skill. When you build for yourself, you 00:08:38.500 --> 00:08:41.500 can be messy. You can have bad naming, no logging. 00:08:41.740 --> 00:08:44.320 But building for others, it forces you to be 00:08:44.320 --> 00:08:47.320 professional. Clean design, good user experience, 00:08:47.820 --> 00:08:50.960 robust error handling, data security. And if 00:08:50.960 --> 00:08:53.960 the workflow only runs once. or it only works 00:08:53.960 --> 00:08:57.259 on your machine, it doesn't count. This can't 00:08:57.259 --> 00:08:59.840 be a rush thing either. The sources break this 00:08:59.840 --> 00:09:02.379 build process down into four distinct phases. 00:09:02.539 --> 00:09:04.919 And phase one is planning. This is the part that 00:09:04.919 --> 00:09:07.240 everyone skips, and it's why they fail. You have 00:09:07.240 --> 00:09:09.799 to define the problem. Who has it? What are the 00:09:09.799 --> 00:09:12.019 limits, like API rate limits? You have to map 00:09:12.019 --> 00:09:13.779 out the logic first in a notebook or something. 00:09:13.980 --> 00:09:15.379 If you skip that, you're just going to waste 00:09:15.379 --> 00:09:17.460 time rebuilding it later. Then you move to phase 00:09:17.460 --> 00:09:22.200 two. Build the MVP. the minimum viable product. 00:09:22.440 --> 00:09:25.399 Create the smallest possible version that actually 00:09:25.399 --> 00:09:28.580 solves the core problem and test it like crazy 00:09:28.580 --> 00:09:32.179 until it stops breaking. Phase three is Polish. 00:09:32.539 --> 00:09:35.120 This is what separates the amateur from the professional 00:09:35.120 --> 00:09:37.980 asset builder. Polish means great error handling. 00:09:38.139 --> 00:09:40.879 What happens when an API goes down? It means 00:09:40.879 --> 00:09:43.820 clear logging so you know when it ran. It means 00:09:43.820 --> 00:09:46.590 clean design, consistent naming. Another builder 00:09:46.590 --> 00:09:48.590 should be able to look at it and understand it 00:09:48.590 --> 00:09:50.750 in 10 minutes. And that polish is what lets you 00:09:50.750 --> 00:09:54.370 move to phase four, share and document. You post 00:09:54.370 --> 00:09:56.769 it to the communities, write a little blog post 00:09:56.769 --> 00:09:59.289 about it, package it up with a re -ADE file, 00:09:59.629 --> 00:10:02.629 a simple diagram, some use cases. That documentation 00:10:02.629 --> 00:10:05.789 turns a small project into undeniable professional 00:10:05.789 --> 00:10:08.610 credibility. So which of those phases is the 00:10:08.610 --> 00:10:10.730 most commonly skipped and what's the consequence? 00:10:11.210 --> 00:10:13.519 Planning is frequently skipped. leading directly 00:10:13.519 --> 00:10:16.899 to wasted time and exponential unnecessary rebuilding 00:10:16.899 --> 00:10:19.480 down the line. Okay, our fifth and final action 00:10:19.480 --> 00:10:21.840 is about leveling up your technical game. If 00:10:21.840 --> 00:10:24.779 you only ever use basic triggers and simple HTTP 00:10:24.779 --> 00:10:27.419 requests, you're driving a Ferrari in first gear. 00:10:27.580 --> 00:10:29.639 Yeah, to build professional -grade automations, 00:10:29.639 --> 00:10:32.120 you have to master the power features, the things 00:10:32.120 --> 00:10:34.919 that give you scale, security, and modularity. 00:10:35.000 --> 00:10:37.679 And that starts with reusable architecture. It 00:10:37.679 --> 00:10:40.649 means mastering sub -workflows. Absolutely. You 00:10:40.649 --> 00:10:43.690 should never rebuild common logic 10 times. You 00:10:43.690 --> 00:10:46.169 build it once as a sub workflow and you just 00:10:46.169 --> 00:10:48.690 call it from your other flows. We recommend prefixing 00:10:48.690 --> 00:10:52.070 them with SCB, like sub slack notification. It's 00:10:52.070 --> 00:10:54.470 easy to find. And that modular approach feeds 00:10:54.470 --> 00:10:57.809 right into professional resilience. You should 00:10:57.809 --> 00:11:00.669 have one master error handling workflow. So all 00:11:00.669 --> 00:11:02.889 your critical flows point to this one single 00:11:02.889 --> 00:11:05.929 place. If something breaks at 3 a .m., the system 00:11:05.929 --> 00:11:08.570 logs the error to a sheet and sends one slack 00:11:08.570 --> 00:11:11.580 alert. It's a unified system. Then we have to 00:11:11.580 --> 00:11:13.960 talk about webhooks. They are your automation 00:11:13.960 --> 00:11:17.279 superpower. They let NADN become a real -time 00:11:17.279 --> 00:11:19.720 integration layer. They let your custom apps 00:11:19.720 --> 00:11:22.759 or forms trigger your workflows instantly. You're 00:11:22.759 --> 00:11:24.899 not stuck polling for changes every five minutes. 00:11:25.019 --> 00:11:27.240 It just happens. And look, the visual nodes are 00:11:27.240 --> 00:11:29.519 amazing, but sometimes you hit a wall. The logic 00:11:29.519 --> 00:11:32.179 gets too complex. And that's when you need the 00:11:32.179 --> 00:11:34.429 code node. And you don't need to be a developer. 00:11:34.610 --> 00:11:36.570 Just learning some basic JavaScript for data 00:11:36.570 --> 00:11:39.970 cleaning or custom math is a game changer. Right. 00:11:40.049 --> 00:11:42.309 It's not about becoming a coder. It's about learning 00:11:42.309 --> 00:11:45.429 a simple expression like JSON data dot filter 00:11:45.429 --> 00:11:48.470 item dot status of filter list. It lets you handle 00:11:48.470 --> 00:11:51.470 edge cases that the normal nodes just can't. 00:11:51.509 --> 00:11:54.129 But maybe the single most important power feature, 00:11:54.289 --> 00:11:57.009 the one with the biggest immediate gain, is using 00:11:57.009 --> 00:12:00.500 environment variables. Yes. For security. We 00:12:00.500 --> 00:12:03.519 have to stop hardcoding passwords and API keys 00:12:03.519 --> 00:12:06.700 directly into our workflows. The risk is just 00:12:06.700 --> 00:12:09.220 catastrophic. If you accidentally share that 00:12:09.220 --> 00:12:11.539 workflow file, your master database keys are 00:12:11.539 --> 00:12:14.159 just out there. Using something like nv .api 00:12:14.159 --> 00:12:16.480 database keeps that sensitive data separate. 00:12:16.639 --> 00:12:19.220 The credentials live outside the workflow itself. 00:12:19.500 --> 00:12:21.059 And what's really cool is that you can then share 00:12:21.059 --> 00:12:22.980 your workflow with a client or the community, 00:12:23.139 --> 00:12:25.120 and you never have to worry about them seeing 00:12:25.120 --> 00:12:27.360 your private credentials. Whoa! Okay, imagine 00:12:27.360 --> 00:12:30.539 scaling that. A secure, modular approach to a 00:12:30.539 --> 00:12:33.360 billion queries without ever leaking a single 00:12:33.360 --> 00:12:36.220 API key. That's real operational security. So 00:12:36.220 --> 00:12:38.899 if you could only pick one power feature to master 00:12:38.899 --> 00:12:41.740 first. Which one offers the biggest immediate 00:12:41.740 --> 00:12:44.419 security game? Environment variables offer the 00:12:44.419 --> 00:12:46.139 quickest and most critical security improvement, 00:12:46.340 --> 00:12:48.399 hands down. So what does this all boil down to 00:12:48.399 --> 00:12:50.779 for you? The real difference between an amateur 00:12:50.779 --> 00:12:53.519 who's stuck in tutorial hell and a true professional? 00:12:54.360 --> 00:12:57.759 It's a focus on reusability and resilience. And 00:12:57.759 --> 00:13:00.120 you get that through these five steps? It's about 00:13:00.120 --> 00:13:02.720 building an automation factory, not just a bunch 00:13:02.720 --> 00:13:04.860 of isolated scripts you have to maintain by hand. 00:13:05.149 --> 00:13:07.529 The core lesson here is just application, pure 00:13:07.529 --> 00:13:09.990 application. You're never going to be done learning 00:13:09.990 --> 00:13:12.610 a tool like an ANAN. But that can't be an excuse 00:13:12.610 --> 00:13:15.610 to stay in student mode forever. The skills you 00:13:15.610 --> 00:13:18.330 have, they depreciate if you don't put them to 00:13:18.330 --> 00:13:21.529 use, to active time -saving use. The professional 00:13:21.529 --> 00:13:23.669 understands that the only thing worse than not 00:13:23.669 --> 00:13:26.389 learning ANAN is learning it inside and out and 00:13:26.389 --> 00:13:28.370 then never using it to solve a hard problem. 00:13:28.509 --> 00:13:30.350 So your challenge starts right now, as soon as 00:13:30.350 --> 00:13:33.110 this is over. Identify that one task you hated 00:13:33.110 --> 00:13:35.470 doing this week, the one that scored over 30 00:13:35.470 --> 00:13:38.210 on the pain score. And don't close this deep 00:13:38.210 --> 00:13:40.389 dive until you have started automating that one 00:13:40.389 --> 00:13:43.070 specific task. Thanks for sharing your sources 00:13:43.070 --> 00:13:45.309 with us and letting us dig in. Happy building. 00:13:45.509 --> 00:13:46.549 Out to your own music.