WEBVTT 00:00.270 --> 00:04.880 As you saw in this video were create two completely different solutions for problems that both cope 00:04.890 --> 00:06.490 the same output. 00:06.540 --> 00:10.340 With that in mind you can understand that the user doesn't see any differences. 00:10.380 --> 00:16.080 So why do so Done to spend more time developing a different program when the solutions that we already 00:16.080 --> 00:19.170 have works correctly. 00:24.840 --> 00:26.630 The ADA is called optimization. 00:26.770 --> 00:31.420 This is one of the most important areas in programming especially when you want to program for a game. 00:31.500 --> 00:34.130 There's three or four areas of scores and many more. 00:34.210 --> 00:37.670 Let's break down the solutions that lead to the same exact outcome. 00:37.690 --> 00:44.350 The first one we use each statement with a corresponding else and although that is consume less computational 00:44.350 --> 00:47.290 power put it now we can see that we have six. 00:47.300 --> 00:53.280 You state it in context with a second program that we have only a statement which is a huge difference 00:53.380 --> 00:57.940 enough for the vaudevilles in the first program or use three exact variables in context with a second 00:57.940 --> 00:59.340 one that we use on day 1. 00:59.440 --> 01:03.930 Finally for the on monklands perspective we use 16 versus eight lines of code. 01:03.940 --> 01:06.020 So the difference is certainly interesting. 01:06.130 --> 01:10.960 But for a practical point of view we don't really see anything interesting liberal sometime between 01:10.960 --> 01:15.890 the first and the second one out which is approximately the same in Dade County that we have a huge 01:15.900 --> 01:16.450 difference. 01:16.490 --> 01:20.110 They may want be part of the program after all is funded three versus one. 01:20.410 --> 01:22.590 So this is a huge waste of time right. 01:22.640 --> 01:25.810 No actually it is the complete opposite for several reasons. 01:25.810 --> 01:29.910 The first one is that this process can develop for a year and they've good Ethan way of thinking. 01:29.920 --> 01:35.740 We already started talking about how you didn't used to solve problems and learn how to develop your 01:35.800 --> 01:41.920 own solutions in what better way to correct yourself in create better solutions and better programs. 01:41.980 --> 01:46.930 The second one is that optimization is your way of thinking into into completely the final product. 01:47.020 --> 01:52.480 In that big product can actually make or break our research this morning results that we observe here 01:52.570 --> 01:57.850 with the listicle monk lines is Kir linked with the point that that program not optimize is an important 01:57.860 --> 01:59.860 day in order to give our result. 01:59.860 --> 02:04.690 In contrast we found optimized one that can give you results and the whole time that is one or two of 02:04.690 --> 02:05.270 seconds. 02:05.290 --> 02:10.510 I hope they inspire you to try different solutions and succeed in improving your program in the future. 02:10.540 --> 02:14.470 Don't worry you don't need to understand everything about optimization right now. 02:14.470 --> 02:17.980 We will talk about this again and again in the future.