WEBVTT Kind: captions Language: en 00:00:00.080 --> 00:00:02.310 align:start position:0% Hi<00:00:00.320> everyone<00:00:00.719> and<00:00:00.960> a<00:00:01.199> very<00:00:01.439> warm<00:00:01.760> welcome<00:00:02.080> to 00:00:02.310 --> 00:00:02.320 align:start position:0% Hi everyone and a very warm welcome to 00:00:02.320 --> 00:00:05.269 align:start position:0% Hi everyone and a very warm welcome to this<00:00:02.560> course<00:00:02.800> on<00:00:03.120> codeex.<00:00:04.319> Really<00:00:04.720> excited<00:00:05.040> to 00:00:05.269 --> 00:00:05.279 align:start position:0% this course on codeex. Really excited to 00:00:05.279 --> 00:00:07.190 align:start position:0% this course on codeex. Really excited to have<00:00:05.359> you<00:00:05.520> here<00:00:05.759> today<00:00:06.160> and<00:00:06.400> hope<00:00:06.640> to<00:00:06.799> learn<00:00:06.960> a 00:00:07.190 --> 00:00:07.200 align:start position:0% have you here today and hope to learn a 00:00:07.200 --> 00:00:08.870 align:start position:0% have you here today and hope to learn a lot<00:00:07.359> of<00:00:07.440> things<00:00:07.680> together.<00:00:08.320> We<00:00:08.480> will<00:00:08.720> learn 00:00:08.870 --> 00:00:08.880 align:start position:0% lot of things together. We will learn 00:00:08.880 --> 00:00:10.790 align:start position:0% lot of things together. We will learn how<00:00:09.040> to<00:00:09.200> use<00:00:09.519> codeex<00:00:10.000> for<00:00:10.240> enterprise 00:00:10.790 --> 00:00:10.800 align:start position:0% how to use codeex for enterprise 00:00:10.800 --> 00:00:12.390 align:start position:0% how to use codeex for enterprise development. 00:00:12.390 --> 00:00:12.400 align:start position:0% development. 00:00:12.400 --> 00:00:14.310 align:start position:0% development. We<00:00:12.639> will<00:00:12.800> see<00:00:12.960> how<00:00:13.200> it<00:00:13.360> works<00:00:13.599> as<00:00:13.840> a<00:00:14.000> coding 00:00:14.310 --> 00:00:14.320 align:start position:0% We will see how it works as a coding 00:00:14.320 --> 00:00:16.550 align:start position:0% We will see how it works as a coding assistant<00:00:14.960> and<00:00:15.200> its<00:00:15.519> many<00:00:15.759> functions<00:00:16.240> in 00:00:16.550 --> 00:00:16.560 align:start position:0% assistant and its many functions in 00:00:16.560 --> 00:00:18.870 align:start position:0% assistant and its many functions in different<00:00:16.800> situations. 00:00:18.870 --> 00:00:18.880 align:start position:0% different situations. 00:00:18.880 --> 00:00:21.990 align:start position:0% different situations. Codeex<00:00:19.439> is<00:00:19.520> a<00:00:19.680> tool<00:00:20.000> made<00:00:20.240> by<00:00:20.480> openai. 00:00:21.990 --> 00:00:22.000 align:start position:0% Codeex is a tool made by openai. 00:00:22.000 --> 00:00:23.670 align:start position:0% Codeex is a tool made by openai. You<00:00:22.160> might<00:00:22.400> know<00:00:22.560> their<00:00:22.880> famous<00:00:23.119> tool<00:00:23.439> called 00:00:23.670 --> 00:00:23.680 align:start position:0% You might know their famous tool called 00:00:23.680 --> 00:00:25.830 align:start position:0% You might know their famous tool called chat<00:00:24.000> GPT. 00:00:25.830 --> 00:00:25.840 align:start position:0% chat GPT. 00:00:25.840 --> 00:00:28.230 align:start position:0% chat GPT. OpenAI<00:00:26.560> is<00:00:26.720> the<00:00:26.960> main<00:00:27.199> company<00:00:27.519> behind<00:00:27.920> chat 00:00:28.230 --> 00:00:28.240 align:start position:0% OpenAI is the main company behind chat 00:00:28.240 --> 00:00:30.950 align:start position:0% OpenAI is the main company behind chat GPT<00:00:29.199> and<00:00:29.439> they<00:00:29.760> handle<00:00:30.080> all<00:00:30.320> the<00:00:30.480> AI 00:00:30.950 --> 00:00:30.960 align:start position:0% GPT and they handle all the AI 00:00:30.960 --> 00:00:33.990 align:start position:0% GPT and they handle all the AI generation<00:00:31.439> and<00:00:31.679> work.<00:00:33.120> First<00:00:33.520> I<00:00:33.760> will<00:00:33.840> show 00:00:33.990 --> 00:00:34.000 align:start position:0% generation and work. First I will show 00:00:34.000 --> 00:00:37.350 align:start position:0% generation and work. First I will show you<00:00:34.079> the<00:00:34.320> OpenAI<00:00:34.960> website.<00:00:36.399> On<00:00:36.640> their<00:00:36.880> website 00:00:37.350 --> 00:00:37.360 align:start position:0% you the OpenAI website. On their website 00:00:37.360 --> 00:00:39.030 align:start position:0% you the OpenAI website. On their website they<00:00:37.600> say<00:00:37.760> their<00:00:38.079> research<00:00:38.480> will<00:00:38.719> lead<00:00:38.879> to 00:00:39.030 --> 00:00:39.040 align:start position:0% they say their research will lead to 00:00:39.040 --> 00:00:41.510 align:start position:0% they say their research will lead to artificial<00:00:39.680> general<00:00:40.079> intelligence<00:00:41.120> which<00:00:41.360> is 00:00:41.510 --> 00:00:41.520 align:start position:0% artificial general intelligence which is 00:00:41.520 --> 00:00:44.709 align:start position:0% artificial general intelligence which is a<00:00:41.680> system<00:00:41.920> that<00:00:42.160> can<00:00:42.320> solve<00:00:42.640> human<00:00:43.040> problems. 00:00:44.709 --> 00:00:44.719 align:start position:0% a system that can solve human problems. 00:00:44.719 --> 00:00:46.869 align:start position:0% a system that can solve human problems. In<00:00:44.960> the<00:00:45.120> product<00:00:45.440> section<00:00:46.000> you<00:00:46.239> can<00:00:46.320> see<00:00:46.559> tools 00:00:46.869 --> 00:00:46.879 align:start position:0% In the product section you can see tools 00:00:46.879 --> 00:00:51.190 align:start position:0% In the product section you can see tools like<00:00:47.120> chat<00:00:47.520> GPT<00:00:48.480> codeex<00:00:49.200> atlas<00:00:49.600> and<00:00:49.840> prism. 00:00:51.190 --> 00:00:51.200 align:start position:0% like chat GPT codeex atlas and prism. 00:00:51.200 --> 00:00:53.510 align:start position:0% like chat GPT codeex atlas and prism. Chat<00:00:51.600> GPT<00:00:52.160> is<00:00:52.320> a<00:00:52.480> very<00:00:52.719> large<00:00:52.960> tool<00:00:53.280> that 00:00:53.510 --> 00:00:53.520 align:start position:0% Chat GPT is a very large tool that 00:00:53.520 --> 00:00:57.189 align:start position:0% Chat GPT is a very large tool that includes<00:00:53.920> images,<00:00:54.800> deep<00:00:55.120> research<00:00:55.680> and<00:00:55.920> GPTs, 00:00:57.189 --> 00:00:57.199 align:start position:0% includes images, deep research and GPTs, 00:00:57.199 --> 00:00:59.670 align:start position:0% includes images, deep research and GPTs, codecs,<00:00:58.239> multiple<00:00:58.719> applications<00:00:59.359> and 00:00:59.670 --> 00:00:59.680 align:start position:0% codecs, multiple applications and 00:00:59.680 --> 00:01:02.630 align:start position:0% codecs, multiple applications and libraries.<00:01:01.039> If<00:01:01.280> we<00:01:01.440> talk<00:01:01.600> about<00:01:01.840> apps,<00:01:02.399> we 00:01:02.630 --> 00:01:02.640 align:start position:0% libraries. If we talk about apps, we 00:01:02.640 --> 00:01:05.189 align:start position:0% libraries. If we talk about apps, we have<00:01:02.800> multiple<00:01:03.280> apps<00:01:03.680> connection.<00:01:04.879> You<00:01:05.119> can 00:01:05.189 --> 00:01:05.199 align:start position:0% have multiple apps connection. You can 00:01:05.199 --> 00:01:07.590 align:start position:0% have multiple apps connection. You can connect<00:01:05.519> it<00:01:05.680> with<00:01:05.840> popular<00:01:06.240> apps<00:01:06.560> like<00:01:06.799> Adobe, 00:01:07.590 --> 00:01:07.600 align:start position:0% connect it with popular apps like Adobe, 00:01:07.600 --> 00:01:11.350 align:start position:0% connect it with popular apps like Adobe, Air<00:01:07.920> Table,<00:01:08.640> Booking.com,<00:01:10.000> Canva,<00:01:10.720> Spotify 00:01:11.350 --> 00:01:11.360 align:start position:0% Air Table, Booking.com, Canva, Spotify 00:01:11.360 --> 00:01:13.109 align:start position:0% Air Table, Booking.com, Canva, Spotify and<00:01:11.600> more. 00:01:13.109 --> 00:01:13.119 align:start position:0% and more. 00:01:13.119 --> 00:01:16.710 align:start position:0% and more. Now<00:01:13.520> let<00:01:13.680> us<00:01:13.920> look<00:01:14.080> at<00:01:14.240> OpenAI<00:01:15.040> codeex. 00:01:16.710 --> 00:01:16.720 align:start position:0% Now let us look at OpenAI codeex. 00:01:16.720 --> 00:01:19.109 align:start position:0% Now let us look at OpenAI codeex. Codeex<00:01:17.280> is<00:01:17.439> an<00:01:17.600> AI<00:01:18.080> software<00:01:18.560> engineering 00:01:19.109 --> 00:01:19.119 align:start position:0% Codeex is an AI software engineering 00:01:19.119 --> 00:01:21.830 align:start position:0% Codeex is an AI software engineering agent.<00:01:20.240> It<00:01:20.560> helps<00:01:20.799> developers<00:01:21.360> write, 00:01:21.830 --> 00:01:21.840 align:start position:0% agent. It helps developers write, 00:01:21.840 --> 00:01:24.469 align:start position:0% agent. It helps developers write, understand,<00:01:22.720> change,<00:01:23.200> test,<00:01:23.600> and<00:01:23.840> ship<00:01:24.159> code 00:01:24.469 --> 00:01:24.479 align:start position:0% understand, change, test, and ship code 00:01:24.479 --> 00:01:27.590 align:start position:0% understand, change, test, and ship code easily.<00:01:25.920> It<00:01:26.159> is<00:01:26.320> not<00:01:26.479> just<00:01:26.640> a<00:01:26.799> simple<00:01:27.040> chatbot 00:01:27.590 --> 00:01:27.600 align:start position:0% easily. It is not just a simple chatbot 00:01:27.600 --> 00:01:30.230 align:start position:0% easily. It is not just a simple chatbot that<00:01:27.840> only<00:01:28.080> answers<00:01:28.479> questions.<00:01:29.759> It<00:01:30.000> works 00:01:30.230 --> 00:01:30.240 align:start position:0% that only answers questions. It works 00:01:30.240 --> 00:01:32.310 align:start position:0% that only answers questions. It works directly<00:01:30.640> with<00:01:30.880> your<00:01:31.119> project<00:01:31.439> files<00:01:32.079> and 00:01:32.310 --> 00:01:32.320 align:start position:0% directly with your project files and 00:01:32.320 --> 00:01:33.830 align:start position:0% directly with your project files and helps<00:01:32.640> with<00:01:32.799> the<00:01:32.960> whole<00:01:33.200> repository 00:01:33.830 --> 00:01:33.840 align:start position:0% helps with the whole repository 00:01:33.840 --> 00:01:36.550 align:start position:0% helps with the whole repository structure<00:01:34.640> and<00:01:34.880> can<00:01:35.040> make<00:01:35.200> the<00:01:35.439> changes,<00:01:36.240> run 00:01:36.550 --> 00:01:36.560 align:start position:0% structure and can make the changes, run 00:01:36.560 --> 00:01:38.390 align:start position:0% structure and can make the changes, run commands,<00:01:37.040> and<00:01:37.280> assists<00:01:37.680> with<00:01:37.920> development 00:01:38.390 --> 00:01:38.400 align:start position:0% commands, and assists with development 00:01:38.400 --> 00:01:41.109 align:start position:0% commands, and assists with development cycles.<00:01:39.759> It<00:01:40.000> gives<00:01:40.240> developers<00:01:40.799> real 00:01:41.109 --> 00:01:41.119 align:start position:0% cycles. It gives developers real 00:01:41.119 --> 00:01:43.510 align:start position:0% cycles. It gives developers real engineering<00:01:41.759> results. 00:01:43.510 --> 00:01:43.520 align:start position:0% engineering results. 00:01:43.520 --> 00:01:46.550 align:start position:0% engineering results. Codeex<00:01:44.079> is<00:01:44.240> also<00:01:44.400> inside<00:01:44.799> chat<00:01:45.200> GPT,<00:01:46.079> so<00:01:46.320> you 00:01:46.550 --> 00:01:46.560 align:start position:0% Codeex is also inside chat GPT, so you 00:01:46.560 --> 00:01:49.270 align:start position:0% Codeex is also inside chat GPT, so you can<00:01:46.640> use<00:01:46.799> it<00:01:47.040> directly.<00:01:48.240> There<00:01:48.479> is<00:01:48.640> a<00:01:48.880> specific 00:01:49.270 --> 00:01:49.280 align:start position:0% can use it directly. There is a specific 00:01:49.280 --> 00:01:51.670 align:start position:0% can use it directly. There is a specific app<00:01:49.520> for<00:01:49.759> codeex<00:01:50.560> and<00:01:50.799> you<00:01:50.960> can<00:01:51.119> download<00:01:51.439> it 00:01:51.670 --> 00:01:51.680 align:start position:0% app for codeex and you can download it 00:01:51.680 --> 00:01:54.469 align:start position:0% app for codeex and you can download it for<00:01:51.920> Windows.<00:01:53.119> We<00:01:53.360> will<00:01:53.520> see<00:01:53.680> how<00:01:53.920> codeex 00:01:54.469 --> 00:01:54.479 align:start position:0% for Windows. We will see how codeex 00:01:54.479 --> 00:01:57.190 align:start position:0% for Windows. We will see how codeex makes<00:01:54.720> real<00:01:55.040> engineering<00:01:55.680> work<00:01:56.000> faster<00:01:56.960> from 00:01:57.190 --> 00:01:57.200 align:start position:0% makes real engineering work faster from 00:01:57.200 --> 00:01:59.510 align:start position:0% makes real engineering work faster from planning<00:01:57.600> and<00:01:57.840> building<00:01:58.159> the<00:01:58.399> features<00:01:59.200> to 00:01:59.510 --> 00:01:59.520 align:start position:0% planning and building the features to 00:01:59.520 --> 00:02:02.789 align:start position:0% planning and building the features to fixing<00:01:59.840> and<00:02:00.159> releases<00:02:00.640> and<00:02:00.960> cross-checking. 00:02:02.789 --> 00:02:02.799 align:start position:0% fixing and releases and cross-checking. 00:02:02.799 --> 00:02:04.950 align:start position:0% fixing and releases and cross-checking. There<00:02:02.960> is<00:02:03.119> also<00:02:03.360> a<00:02:03.520> command<00:02:03.920> line<00:02:04.240> interface 00:02:04.950 --> 00:02:04.960 align:start position:0% There is also a command line interface 00:02:04.960 --> 00:02:08.710 align:start position:0% There is also a command line interface or<00:02:05.360> CLI<00:02:06.320> on<00:02:06.560> GitHub<00:02:07.040> for<00:02:07.200> codecs. 00:02:08.710 --> 00:02:08.720 align:start position:0% or CLI on GitHub for codecs. 00:02:08.720 --> 00:02:12.070 align:start position:0% or CLI on GitHub for codecs. CLI<00:02:09.440> means<00:02:09.840> command<00:02:10.239> line<00:02:10.560> interface.<00:02:11.760> It<00:02:12.000> is 00:02:12.070 --> 00:02:12.080 align:start position:0% CLI means command line interface. It is 00:02:12.080 --> 00:02:14.150 align:start position:0% CLI means command line interface. It is a<00:02:12.239> textbased<00:02:12.879> interface<00:02:13.360> used<00:02:13.599> to<00:02:13.760> talk<00:02:14.000> to 00:02:14.150 --> 00:02:14.160 align:start position:0% a textbased interface used to talk to 00:02:14.160 --> 00:02:16.790 align:start position:0% a textbased interface used to talk to software<00:02:14.560> and<00:02:14.879> computers.<00:02:16.319> Instead<00:02:16.640> of 00:02:16.790 --> 00:02:16.800 align:start position:0% software and computers. Instead of 00:02:16.800 --> 00:02:18.630 align:start position:0% software and computers. Instead of clicking<00:02:17.120> buttons<00:02:17.440> with<00:02:17.599> a<00:02:17.760> mouse<00:02:18.000> on<00:02:18.160> visual 00:02:18.630 --> 00:02:18.640 align:start position:0% clicking buttons with a mouse on visual 00:02:18.640 --> 00:02:21.510 align:start position:0% clicking buttons with a mouse on visual icons,<00:02:19.440> you<00:02:19.680> type<00:02:20.000> text<00:02:20.319> commands<00:02:21.120> and<00:02:21.280> the 00:02:21.510 --> 00:02:21.520 align:start position:0% icons, you type text commands and the 00:02:21.520 --> 00:02:23.510 align:start position:0% icons, you type text commands and the textbased<00:02:22.239> user<00:02:22.560> interface<00:02:23.040> used<00:02:23.280> to 00:02:23.510 --> 00:02:23.520 align:start position:0% textbased user interface used to 00:02:23.520 --> 00:02:25.750 align:start position:0% textbased user interface used to interact<00:02:23.840> with<00:02:24.000> the<00:02:24.239> software<00:02:25.200> operating 00:02:25.750 --> 00:02:25.760 align:start position:0% interact with the software operating 00:02:25.760 --> 00:02:27.990 align:start position:0% interact with the software operating system<00:02:26.480> and<00:02:26.720> on<00:02:26.879> your<00:02:27.040> keyboard<00:02:27.520> instead<00:02:27.840> of 00:02:27.990 --> 00:02:28.000 align:start position:0% system and on your keyboard instead of 00:02:28.000 --> 00:02:30.390 align:start position:0% system and on your keyboard instead of using<00:02:28.160> a<00:02:28.400> mouse<00:02:28.640> to<00:02:28.879> click<00:02:29.040> on<00:02:29.200> visual<00:02:29.599> items 00:02:30.390 --> 00:02:30.400 align:start position:0% using a mouse to click on visual items 00:02:30.400 --> 00:02:33.430 align:start position:0% using a mouse to click on visual items and<00:02:30.720> press<00:02:30.959> enter<00:02:31.280> to<00:02:31.520> make<00:02:31.680> them<00:02:31.920> work.<00:02:33.200> We 00:02:33.430 --> 00:02:33.440 align:start position:0% and press enter to make them work. We 00:02:33.440 --> 00:02:36.550 align:start position:0% and press enter to make them work. We will<00:02:33.599> learn<00:02:33.760> how<00:02:33.920> to<00:02:34.160> use<00:02:34.319> this<00:02:34.640> CLI.<00:02:36.000> Codeex 00:02:36.550 --> 00:02:36.560 align:start position:0% will learn how to use this CLI. Codeex 00:02:36.560 --> 00:02:38.710 align:start position:0% will learn how to use this CLI. Codeex helps<00:02:36.800> what<00:02:37.040> a<00:02:37.200> developer<00:02:37.599> wants<00:02:37.840> to<00:02:38.000> do<00:02:38.400> and 00:02:38.710 --> 00:02:38.720 align:start position:0% helps what a developer wants to do and 00:02:38.720 --> 00:02:41.589 align:start position:0% helps what a developer wants to do and turns<00:02:38.959> it<00:02:39.120> into<00:02:39.440> engineering<00:02:40.000> output.<00:02:41.360> You 00:02:41.589 --> 00:02:41.599 align:start position:0% turns it into engineering output. You 00:02:41.599 --> 00:02:43.910 align:start position:0% turns it into engineering output. You can<00:02:41.760> describe<00:02:42.080> a<00:02:42.319> bug<00:02:42.560> or<00:02:42.800> a<00:02:42.959> new<00:02:43.120> feature, 00:02:43.910 --> 00:02:43.920 align:start position:0% can describe a bug or a new feature, 00:02:43.920 --> 00:02:47.110 align:start position:0% can describe a bug or a new feature, test<00:02:44.319> environment,<00:02:45.040> documentation,<00:02:46.080> task<00:02:46.879> in 00:02:47.110 --> 00:02:47.120 align:start position:0% test environment, documentation, task in 00:02:47.120 --> 00:02:49.030 align:start position:0% test environment, documentation, task in natural<00:02:47.519> language. 00:02:49.030 --> 00:02:49.040 align:start position:0% natural language. 00:02:49.040 --> 00:02:51.110 align:start position:0% natural language. Codeex<00:02:49.680> can<00:02:49.840> analyze<00:02:50.239> the<00:02:50.400> database, 00:02:51.110 --> 00:02:51.120 align:start position:0% Codeex can analyze the database, 00:02:51.120 --> 00:02:53.910 align:start position:0% Codeex can analyze the database, identifying<00:02:51.680> files,<00:02:52.400> propose<00:02:52.959> changes<00:02:53.680> and 00:02:53.910 --> 00:02:53.920 align:start position:0% identifying files, propose changes and 00:02:53.920 --> 00:02:56.949 align:start position:0% identifying files, propose changes and generate<00:02:54.400> limitation<00:02:55.040> steps.<00:02:56.319> This<00:02:56.560> makes<00:02:56.800> it 00:02:56.949 --> 00:02:56.959 align:start position:0% generate limitation steps. This makes it 00:02:56.959 --> 00:02:59.350 align:start position:0% generate limitation steps. This makes it useful<00:02:57.360> not<00:02:57.599> only<00:02:57.760> for<00:02:57.920> the<00:02:58.080> writer<00:02:58.800> but<00:02:59.040> also 00:02:59.350 --> 00:02:59.360 align:start position:0% useful not only for the writer but also 00:02:59.360 --> 00:03:02.869 align:start position:0% useful not only for the writer but also for<00:02:59.599> navigating<00:03:00.239> unfamiliar<00:03:01.040> systemd. 00:03:02.869 --> 00:03:02.879 align:start position:0% for navigating unfamiliar systemd. 00:03:02.879 --> 00:03:05.910 align:start position:0% for navigating unfamiliar systemd. Here<00:03:03.200> we<00:03:03.360> have<00:03:03.519> codeex<00:03:04.080> discussion.<00:03:05.440> In<00:03:05.760> this 00:03:05.910 --> 00:03:05.920 align:start position:0% Here we have codeex discussion. In this 00:03:05.920 --> 00:03:07.350 align:start position:0% Here we have codeex discussion. In this course,<00:03:06.159> we<00:03:06.400> will<00:03:06.560> talk<00:03:06.800> about<00:03:07.040> daily 00:03:07.350 --> 00:03:07.360 align:start position:0% course, we will talk about daily 00:03:07.360 --> 00:03:10.550 align:start position:0% course, we will talk about daily development,<00:03:08.319> prompting,<00:03:09.360> making<00:03:09.760> agents 00:03:10.550 --> 00:03:10.560 align:start position:0% development, prompting, making agents 00:03:10.560 --> 00:03:13.430 align:start position:0% development, prompting, making agents and<00:03:10.800> using<00:03:11.120> codecs<00:03:11.599> for<00:03:11.760> a<00:03:11.920> long<00:03:12.159> time.<00:03:13.280> We 00:03:13.430 --> 00:03:13.440 align:start position:0% and using codecs for a long time. We 00:03:13.440 --> 00:03:15.350 align:start position:0% and using codecs for a long time. We will<00:03:13.680> cover<00:03:13.920> all<00:03:14.159> of<00:03:14.239> these<00:03:14.560> important<00:03:14.959> topics 00:03:15.350 --> 00:03:15.360 align:start position:0% will cover all of these important topics 00:03:15.360 --> 00:03:19.430 align:start position:0% will cover all of these important topics together. 00:03:19.430 --> 00:03:19.440 align:start position:0% 00:03:19.440 --> 00:03:21.990 align:start position:0% So<00:03:20.000> moving<00:03:20.319> on,<00:03:20.959> the<00:03:21.200> next<00:03:21.519> critical 00:03:21.990 --> 00:03:22.000 align:start position:0% So moving on, the next critical 00:03:22.000 --> 00:03:24.070 align:start position:0% So moving on, the next critical discussion<00:03:22.480> is<00:03:22.800> primarily<00:03:23.440> related<00:03:23.840> to 00:03:24.070 --> 00:03:24.080 align:start position:0% discussion is primarily related to 00:03:24.080 --> 00:03:25.910 align:start position:0% discussion is primarily related to exactly<00:03:24.480> how<00:03:24.720> we<00:03:24.959> are<00:03:25.120> going<00:03:25.200> to<00:03:25.440> securely 00:03:25.910 --> 00:03:25.920 align:start position:0% exactly how we are going to securely 00:03:25.920 --> 00:03:28.869 align:start position:0% exactly how we are going to securely install<00:03:26.480> codeex<00:03:26.959> on<00:03:27.120> our<00:03:27.360> machine. 00:03:28.869 --> 00:03:28.879 align:start position:0% install codeex on our machine. 00:03:28.879 --> 00:03:31.670 align:start position:0% install codeex on our machine. first<00:03:29.840> well<00:03:30.159> before<00:03:30.560> actually<00:03:30.959> installing<00:03:31.440> it 00:03:31.670 --> 00:03:31.680 align:start position:0% first well before actually installing it 00:03:31.680 --> 00:03:33.990 align:start position:0% first well before actually installing it anywhere<00:03:32.080> else.<00:03:32.879> We<00:03:33.120> will<00:03:33.280> practically<00:03:33.840> use 00:03:33.990 --> 00:03:34.000 align:start position:0% anywhere else. We will practically use 00:03:34.000 --> 00:03:35.990 align:start position:0% anywhere else. We will practically use the<00:03:34.319> standard<00:03:34.720> command<00:03:35.040> line<00:03:35.280> interface<00:03:35.760> to 00:03:35.990 --> 00:03:36.000 align:start position:0% the standard command line interface to 00:03:36.000 --> 00:03:37.990 align:start position:0% the standard command line interface to get<00:03:36.159> things<00:03:36.400> started. 00:03:37.990 --> 00:03:38.000 align:start position:0% get things started. 00:03:38.000 --> 00:03:40.550 align:start position:0% get things started. But<00:03:38.239> right<00:03:38.480> before<00:03:38.799> that<00:03:39.040> specific<00:03:39.519> step,<00:03:40.319> we 00:03:40.550 --> 00:03:40.560 align:start position:0% But right before that specific step, we 00:03:40.560 --> 00:03:42.470 align:start position:0% But right before that specific step, we can<00:03:40.799> smoothly<00:03:41.280> download<00:03:41.680> the<00:03:41.920> dedicated 00:03:42.470 --> 00:03:42.480 align:start position:0% can smoothly download the dedicated 00:03:42.480 --> 00:03:44.470 align:start position:0% can smoothly download the dedicated version<00:03:42.959> specifically<00:03:43.599> meant<00:03:43.840> for<00:03:44.080> Windows 00:03:44.470 --> 00:03:44.480 align:start position:0% version specifically meant for Windows 00:03:44.480 --> 00:03:46.550 align:start position:0% version specifically meant for Windows operating<00:03:44.959> systems. 00:03:46.550 --> 00:03:46.560 align:start position:0% operating systems. 00:03:46.560 --> 00:03:49.270 align:start position:0% operating systems. Now<00:03:47.200> I<00:03:47.519> already<00:03:47.760> have<00:03:48.000> the<00:03:48.239> necessary<00:03:48.720> codeex 00:03:49.270 --> 00:03:49.280 align:start position:0% Now I already have the necessary codeex 00:03:49.280 --> 00:03:51.910 align:start position:0% Now I already have the necessary codeex installer<00:03:49.840> fully<00:03:50.239> ready<00:03:50.400> to<00:03:50.640> go<00:03:50.799> here.<00:03:51.680> I 00:03:51.910 --> 00:03:51.920 align:start position:0% installer fully ready to go here. I 00:03:51.920 --> 00:03:53.990 align:start position:0% installer fully ready to go here. I simply<00:03:52.319> open<00:03:52.560> up<00:03:52.720> the<00:03:52.879> main<00:03:53.200> system<00:03:53.519> downloads 00:03:53.990 --> 00:03:54.000 align:start position:0% simply open up the main system downloads 00:03:54.000 --> 00:03:57.270 align:start position:0% simply open up the main system downloads folder<00:03:54.400> right<00:03:54.640> now.<00:03:55.599> Then<00:03:56.000> I<00:03:56.319> firmly<00:03:56.799> run<00:03:56.959> the 00:03:57.270 --> 00:03:57.280 align:start position:0% folder right now. Then I firmly run the 00:03:57.280 --> 00:03:59.429 align:start position:0% folder right now. Then I firmly run the executable<00:03:58.000> installer<00:03:58.560> directly<00:03:59.040> as<00:03:59.200> a 00:03:59.429 --> 00:03:59.439 align:start position:0% executable installer directly as a 00:03:59.439 --> 00:04:01.350 align:start position:0% executable installer directly as a system<00:03:59.680> administrator. 00:04:01.350 --> 00:04:01.360 align:start position:0% system administrator. 00:04:01.360 --> 00:04:03.509 align:start position:0% system administrator. The<00:04:01.599> core<00:04:02.000> software<00:04:02.480> immediately<00:04:03.040> starts<00:04:03.280> to 00:04:03.509 --> 00:04:03.519 align:start position:0% The core software immediately starts to 00:04:03.519 --> 00:04:05.830 align:start position:0% The core software immediately starts to install<00:04:03.840> itself<00:04:04.319> smoothly. 00:04:05.830 --> 00:04:05.840 align:start position:0% install itself smoothly. 00:04:05.840 --> 00:04:08.390 align:start position:0% install itself smoothly. Simultaneously,<00:04:07.200> the<00:04:07.439> Microsoft<00:04:08.080> Store 00:04:08.390 --> 00:04:08.400 align:start position:0% Simultaneously, the Microsoft Store 00:04:08.400 --> 00:04:10.710 align:start position:0% Simultaneously, the Microsoft Store seamlessly<00:04:09.040> begins<00:04:09.360> its<00:04:09.680> essential<00:04:10.239> download 00:04:10.710 --> 00:04:10.720 align:start position:0% seamlessly begins its essential download 00:04:10.720 --> 00:04:12.309 align:start position:0% seamlessly begins its essential download process. 00:04:12.309 --> 00:04:12.319 align:start position:0% process. 00:04:12.319 --> 00:04:14.550 align:start position:0% process. Finally,<00:04:13.120> when<00:04:13.360> the<00:04:13.599> entire<00:04:14.080> download 00:04:14.550 --> 00:04:14.560 align:start position:0% Finally, when the entire download 00:04:14.560 --> 00:04:16.949 align:start position:0% Finally, when the entire download completely<00:04:15.120> finishes,<00:04:16.160> codeex<00:04:16.720> will 00:04:16.949 --> 00:04:16.959 align:start position:0% completely finishes, codeex will 00:04:16.959 --> 00:04:19.030 align:start position:0% completely finishes, codeex will successfully<00:04:17.519> run. 00:04:19.030 --> 00:04:19.040 align:start position:0% successfully run. 00:04:19.040 --> 00:04:21.349 align:start position:0% successfully run. Interestingly,<00:04:20.160> we<00:04:20.400> can<00:04:20.560> certainly<00:04:21.040> also 00:04:21.349 --> 00:04:21.359 align:start position:0% Interestingly, we can certainly also 00:04:21.359 --> 00:04:23.189 align:start position:0% Interestingly, we can certainly also manage<00:04:21.680> to<00:04:21.840> install<00:04:22.160> it<00:04:22.320> safely<00:04:22.800> across 00:04:23.189 --> 00:04:23.199 align:start position:0% manage to install it safely across 00:04:23.199 --> 00:04:26.150 align:start position:0% manage to install it safely across multiple<00:04:23.759> different<00:04:24.080> computer<00:04:24.560> systems.<00:04:25.919> As 00:04:26.150 --> 00:04:26.160 align:start position:0% multiple different computer systems. As 00:04:26.160 --> 00:04:28.310 align:start position:0% multiple different computer systems. As we<00:04:26.400> smoothly<00:04:26.960> scroll<00:04:27.360> further<00:04:27.680> down<00:04:27.919> the<00:04:28.080> main 00:04:28.310 --> 00:04:28.320 align:start position:0% we smoothly scroll further down the main 00:04:28.320 --> 00:04:30.550 align:start position:0% we smoothly scroll further down the main page,<00:04:29.120> you<00:04:29.360> will<00:04:29.520> clearly<00:04:29.919> see<00:04:30.240> three 00:04:30.550 --> 00:04:30.560 align:start position:0% page, you will clearly see three 00:04:30.560 --> 00:04:33.350 align:start position:0% page, you will clearly see three distinct<00:04:31.040> setup<00:04:31.440> options<00:04:31.840> presented. 00:04:33.350 --> 00:04:33.360 align:start position:0% distinct setup options presented. 00:04:33.360 --> 00:04:35.430 align:start position:0% distinct setup options presented. The<00:04:33.680> very<00:04:33.919> first<00:04:34.160> one<00:04:34.400> is<00:04:34.639> the<00:04:34.880> standard 00:04:35.430 --> 00:04:35.440 align:start position:0% The very first one is the standard 00:04:35.440 --> 00:04:38.310 align:start position:0% The very first one is the standard standalone<00:04:36.080> app.<00:04:37.120> If<00:04:37.360> we<00:04:37.600> really<00:04:37.840> want<00:04:38.000> to<00:04:38.160> use 00:04:38.310 --> 00:04:38.320 align:start position:0% standalone app. If we really want to use 00:04:38.320 --> 00:04:40.550 align:start position:0% standalone app. If we really want to use a<00:04:38.560> code<00:04:38.800> editor,<00:04:39.600> we<00:04:39.840> can<00:04:40.000> install<00:04:40.320> it 00:04:40.550 --> 00:04:40.560 align:start position:0% a code editor, we can install it 00:04:40.560 --> 00:04:43.590 align:start position:0% a code editor, we can install it directly<00:04:41.040> within<00:04:41.360> our<00:04:41.520> preferred<00:04:42.080> IDE. 00:04:43.590 --> 00:04:43.600 align:start position:0% directly within our preferred IDE. 00:04:43.600 --> 00:04:45.670 align:start position:0% directly within our preferred IDE. Fortunately,<00:04:44.479> we<00:04:44.800> already<00:04:45.040> have<00:04:45.280> Visual 00:04:45.670 --> 00:04:45.680 align:start position:0% Fortunately, we already have Visual 00:04:45.680 --> 00:04:49.430 align:start position:0% Fortunately, we already have Visual Studio<00:04:46.160> Code<00:04:46.560> fully<00:04:46.880> set<00:04:47.120> up<00:04:48.240> right<00:04:48.479> inside<00:04:48.960> VS 00:04:49.430 --> 00:04:49.440 align:start position:0% Studio Code fully set up right inside VS 00:04:49.440 --> 00:04:52.230 align:start position:0% Studio Code fully set up right inside VS Code.<00:04:50.240> A<00:04:50.479> highly<00:04:50.800> helpful<00:04:51.199> AI<00:04:51.680> is<00:04:51.919> fully 00:04:52.230 --> 00:04:52.240 align:start position:0% Code. A highly helpful AI is fully 00:04:52.240 --> 00:04:55.430 align:start position:0% Code. A highly helpful AI is fully available.<00:04:53.520> It<00:04:53.759> is<00:04:53.919> completely<00:04:54.479> automated 00:04:55.430 --> 00:04:55.440 align:start position:0% available. It is completely automated 00:04:55.440 --> 00:04:57.749 align:start position:0% available. It is completely automated and<00:04:55.759> we<00:04:55.919> can<00:04:56.080> easily<00:04:56.560> use<00:04:56.800> various<00:04:57.280> models 00:04:57.749 --> 00:04:57.759 align:start position:0% and we can easily use various models 00:04:57.759 --> 00:05:00.550 align:start position:0% and we can easily use various models right<00:04:58.000> here.<00:04:59.120> To<00:04:59.360> successfully<00:05:00.000> add<00:05:00.160> this<00:05:00.400> to 00:05:00.550 --> 00:05:00.560 align:start position:0% right here. To successfully add this to 00:05:00.560 --> 00:05:02.870 align:start position:0% right here. To successfully add this to our<00:05:00.720> daily<00:05:01.040> workflow,<00:05:02.000> we<00:05:02.240> simply<00:05:02.560> need<00:05:02.720> to 00:05:02.870 --> 00:05:02.880 align:start position:0% our daily workflow, we simply need to 00:05:02.880 --> 00:05:06.469 align:start position:0% our daily workflow, we simply need to install<00:05:03.280> it<00:05:03.440> in<00:05:03.680> VS<00:05:04.160> Code.<00:05:05.440> We<00:05:05.680> securely<00:05:06.160> click 00:05:06.469 --> 00:05:06.479 align:start position:0% install it in VS Code. We securely click 00:05:06.479 --> 00:05:09.189 align:start position:0% install it in VS Code. We securely click allow<00:05:06.880> in<00:05:07.039> VS<00:05:07.520> Code<00:05:08.160> and<00:05:08.400> Codeex<00:05:09.039> will 00:05:09.189 --> 00:05:09.199 align:start position:0% allow in VS Code and Codeex will 00:05:09.199 --> 00:05:12.550 align:start position:0% allow in VS Code and Codeex will seamlessly<00:05:09.759> open.<00:05:11.039> Essentially,<00:05:12.160> it<00:05:12.400> is 00:05:12.550 --> 00:05:12.560 align:start position:0% seamlessly open. Essentially, it is 00:05:12.560 --> 00:05:14.950 align:start position:0% seamlessly open. Essentially, it is OpenAI's<00:05:13.440> powerful<00:05:13.919> coding<00:05:14.320> agent<00:05:14.639> that 00:05:14.950 --> 00:05:14.960 align:start position:0% OpenAI's powerful coding agent that 00:05:14.960 --> 00:05:17.510 align:start position:0% OpenAI's powerful coding agent that constantly<00:05:15.440> works<00:05:15.680> with<00:05:15.919> you.<00:05:16.880> It<00:05:17.039> is<00:05:17.199> fully 00:05:17.510 --> 00:05:17.520 align:start position:0% constantly works with you. It is fully 00:05:17.520 --> 00:05:21.510 align:start position:0% constantly works with you. It is fully included<00:05:17.919> in<00:05:18.160> chat<00:05:18.479> GPT<00:05:19.120> plus<00:05:19.919> pro,<00:05:20.639> business, 00:05:21.510 --> 00:05:21.520 align:start position:0% included in chat GPT plus pro, business, 00:05:21.520 --> 00:05:24.629 align:start position:0% included in chat GPT plus pro, business, education,<00:05:22.240> and<00:05:22.560> enterprise<00:05:23.120> plans. 00:05:24.629 --> 00:05:24.639 align:start position:0% education, and enterprise plans. 00:05:24.639 --> 00:05:27.110 align:start position:0% education, and enterprise plans. First<00:05:24.880> and<00:05:25.120> foremost,<00:05:25.680> we<00:05:26.080> absolutely<00:05:26.800> must 00:05:27.110 --> 00:05:27.120 align:start position:0% First and foremost, we absolutely must 00:05:27.120 --> 00:05:29.990 align:start position:0% First and foremost, we absolutely must carefully<00:05:27.759> check<00:05:28.080> our<00:05:28.400> specific<00:05:28.960> chat<00:05:29.360> GPT 00:05:29.990 --> 00:05:30.000 align:start position:0% carefully check our specific chat GPT 00:05:30.000 --> 00:05:32.710 align:start position:0% carefully check our specific chat GPT subscription<00:05:30.560> plan.<00:05:31.840> I<00:05:32.080> will<00:05:32.240> officially 00:05:32.710 --> 00:05:32.720 align:start position:0% subscription plan. I will officially 00:05:32.720 --> 00:05:35.029 align:start position:0% subscription plan. I will officially open<00:05:32.880> up<00:05:33.039> the<00:05:33.199> chat<00:05:33.520> GPT<00:05:34.160> interface<00:05:34.720> right 00:05:35.029 --> 00:05:35.039 align:start position:0% open up the chat GPT interface right 00:05:35.039 --> 00:05:36.390 align:start position:0% open up the chat GPT interface right now. 00:05:36.390 --> 00:05:36.400 align:start position:0% now. 00:05:36.400 --> 00:05:38.710 align:start position:0% now. As<00:05:36.639> you<00:05:36.800> can<00:05:36.960> clearly<00:05:37.360> see,<00:05:38.080> we<00:05:38.320> currently 00:05:38.710 --> 00:05:38.720 align:start position:0% As you can clearly see, we currently 00:05:38.720 --> 00:05:42.070 align:start position:0% As you can clearly see, we currently have<00:05:38.880> the<00:05:39.120> plus<00:05:39.440> version<00:05:40.000> fully<00:05:40.400> activated. 00:05:42.070 --> 00:05:42.080 align:start position:0% have the plus version fully activated. 00:05:42.080 --> 00:05:44.390 align:start position:0% have the plus version fully activated. Looking<00:05:42.400> closely<00:05:42.880> in<00:05:43.120> the<00:05:43.280> dedicated<00:05:43.919> upgrade 00:05:44.390 --> 00:05:44.400 align:start position:0% Looking closely in the dedicated upgrade 00:05:44.400 --> 00:05:47.350 align:start position:0% Looking closely in the dedicated upgrade plan<00:05:44.720> section,<00:05:45.759> you<00:05:46.000> clearly<00:05:46.400> see<00:05:46.639> our<00:05:46.960> active 00:05:47.350 --> 00:05:47.360 align:start position:0% plan section, you clearly see our active 00:05:47.360 --> 00:05:50.469 align:start position:0% plan section, you clearly see our active billing<00:05:47.680> plan.<00:05:48.800> It<00:05:49.039> is<00:05:49.199> indeed<00:05:49.680> the<00:05:50.000> standard 00:05:50.469 --> 00:05:50.479 align:start position:0% billing plan. It is indeed the standard 00:05:50.479 --> 00:05:53.749 align:start position:0% billing plan. It is indeed the standard plus<00:05:50.800> plan.<00:05:52.240> This<00:05:52.560> essentially<00:05:52.960> means<00:05:53.520> all 00:05:53.749 --> 00:05:53.759 align:start position:0% plus plan. This essentially means all 00:05:53.759 --> 00:05:55.990 align:start position:0% plus plan. This essentially means all our<00:05:54.000> ongoing<00:05:54.560> coding<00:05:54.960> work<00:05:55.199> is<00:05:55.520> completely 00:05:55.990 --> 00:05:56.000 align:start position:0% our ongoing coding work is completely 00:05:56.000 --> 00:05:59.189 align:start position:0% our ongoing coding work is completely safe<00:05:56.320> and<00:05:56.560> secure.<00:05:58.000> Codeex<00:05:58.639> is<00:05:58.800> fully 00:05:59.189 --> 00:05:59.199 align:start position:0% safe and secure. Codeex is fully 00:05:59.199 --> 00:06:01.990 align:start position:0% safe and secure. Codeex is fully available<00:05:59.600> to<00:05:59.840> use<00:06:00.080> today.<00:06:01.280> The<00:06:01.520> strictly 00:06:01.990 --> 00:06:02.000 align:start position:0% available to use today. The strictly 00:06:02.000 --> 00:06:04.070 align:start position:0% available to use today. The strictly required<00:06:02.479> language<00:06:02.880> model<00:06:03.199> is<00:06:03.440> situated 00:06:04.070 --> 00:06:04.080 align:start position:0% required language model is situated 00:06:04.080 --> 00:06:06.150 align:start position:0% required language model is situated right<00:06:04.400> here. 00:06:06.150 --> 00:06:06.160 align:start position:0% right here. 00:06:06.160 --> 00:06:08.469 align:start position:0% right here. Moving<00:06:06.560> back<00:06:06.720> into<00:06:07.039> VS<00:06:07.440> Code,<00:06:08.080> we<00:06:08.319> will 00:06:08.469 --> 00:06:08.479 align:start position:0% Moving back into VS Code, we will 00:06:08.479 --> 00:06:10.710 align:start position:0% Moving back into VS Code, we will effectively<00:06:09.120> start<00:06:09.360> the<00:06:09.680> complete<00:06:10.160> software 00:06:10.710 --> 00:06:10.720 align:start position:0% effectively start the complete software 00:06:10.720 --> 00:06:12.390 align:start position:0% effectively start the complete software installation. 00:06:12.390 --> 00:06:12.400 align:start position:0% installation. 00:06:12.400 --> 00:06:14.390 align:start position:0% installation. It<00:06:12.639> securely<00:06:13.120> installs<00:06:13.759> just<00:06:14.000> like<00:06:14.160> a 00:06:14.390 --> 00:06:14.400 align:start position:0% It securely installs just like a 00:06:14.400 --> 00:06:16.710 align:start position:0% It securely installs just like a standard<00:06:14.720> web<00:06:14.960> extension. 00:06:16.710 --> 00:06:16.720 align:start position:0% standard web extension. 00:06:16.720 --> 00:06:19.270 align:start position:0% standard web extension. First,<00:06:17.280> we<00:06:17.600> smoothly<00:06:18.080> pair<00:06:18.319> it<00:06:18.560> directly<00:06:19.039> with 00:06:19.270 --> 00:06:19.280 align:start position:0% First, we smoothly pair it directly with 00:06:19.280 --> 00:06:20.790 align:start position:0% First, we smoothly pair it directly with codeex. 00:06:20.790 --> 00:06:20.800 align:start position:0% codeex. 00:06:20.800 --> 00:06:23.189 align:start position:0% codeex. We<00:06:21.039> basically<00:06:21.520> add<00:06:21.759> codeex<00:06:22.319> as<00:06:22.479> a<00:06:22.639> dedicated 00:06:23.189 --> 00:06:23.199 align:start position:0% We basically add codeex as a dedicated 00:06:23.199 --> 00:06:26.309 align:start position:0% We basically add codeex as a dedicated side<00:06:23.520> panel<00:06:23.919> within<00:06:24.319> VS<00:06:24.639> Code<00:06:25.440> to<00:06:25.680> seamlessly 00:06:26.309 --> 00:06:26.319 align:start position:0% side panel within VS Code to seamlessly 00:06:26.319 --> 00:06:29.350 align:start position:0% side panel within VS Code to seamlessly chat,<00:06:27.039> intuitively<00:06:27.759> edit,<00:06:28.560> and<00:06:28.800> carefully 00:06:29.350 --> 00:06:29.360 align:start position:0% chat, intuitively edit, and carefully 00:06:29.360 --> 00:06:31.990 align:start position:0% chat, intuitively edit, and carefully check<00:06:29.680> all<00:06:29.919> our<00:06:30.160> changes. 00:06:31.990 --> 00:06:32.000 align:start position:0% check all our changes. 00:06:32.000 --> 00:06:34.629 align:start position:0% check all our changes. Then<00:06:32.639> we<00:06:32.960> can<00:06:33.120> confidently<00:06:33.759> use<00:06:34.000> Codeex 00:06:34.629 --> 00:06:34.639 align:start position:0% Then we can confidently use Codeex 00:06:34.639 --> 00:06:37.029 align:start position:0% Then we can confidently use Codeex directly<00:06:35.039> in<00:06:35.199> the<00:06:35.360> cloud,<00:06:36.240> sending<00:06:36.639> massive 00:06:37.029 --> 00:06:37.039 align:start position:0% directly in the cloud, sending massive 00:06:37.039 --> 00:06:39.990 align:start position:0% directly in the cloud, sending massive jobs<00:06:37.440> straight<00:06:37.680> to<00:06:37.919> it.<00:06:39.120> Moving<00:06:39.520> gracefully 00:06:39.990 --> 00:06:40.000 align:start position:0% jobs straight to it. Moving gracefully 00:06:40.000 --> 00:06:42.629 align:start position:0% jobs straight to it. Moving gracefully to<00:06:40.160> the<00:06:40.319> very<00:06:40.560> next<00:06:40.800> step,<00:06:41.520> we<00:06:41.840> simply<00:06:42.240> need<00:06:42.400> to 00:06:42.629 --> 00:06:42.639 align:start position:0% to the very next step, we simply need to 00:06:42.639 --> 00:06:45.189 align:start position:0% to the very next step, we simply need to safely<00:06:43.120> sign<00:06:43.360> in<00:06:43.680> using<00:06:44.000> our<00:06:44.319> primary<00:06:44.800> chat 00:06:45.189 --> 00:06:45.199 align:start position:0% safely sign in using our primary chat 00:06:45.199 --> 00:06:47.749 align:start position:0% safely sign in using our primary chat GPT<00:06:45.759> account<00:06:46.080> credentials. 00:06:47.749 --> 00:06:47.759 align:start position:0% GPT account credentials. 00:06:47.759 --> 00:06:50.309 align:start position:0% GPT account credentials. Once<00:06:48.080> fully<00:06:48.479> authenticated,<00:06:49.759> our<00:06:50.000> main 00:06:50.309 --> 00:06:50.319 align:start position:0% Once fully authenticated, our main 00:06:50.319 --> 00:06:52.550 align:start position:0% Once fully authenticated, our main application<00:06:51.039> will<00:06:51.360> automatically<00:06:52.000> install 00:06:52.550 --> 00:06:52.560 align:start position:0% application will automatically install 00:06:52.560 --> 00:06:55.430 align:start position:0% application will automatically install directly<00:06:53.039> into<00:06:53.360> the<00:06:53.520> workspace. 00:06:55.430 --> 00:06:55.440 align:start position:0% directly into the workspace. 00:06:55.440 --> 00:06:58.469 align:start position:0% directly into the workspace. Now<00:06:56.160> the<00:06:56.400> third<00:06:56.720> available<00:06:57.199> setup<00:06:57.600> option<00:06:58.240> is 00:06:58.469 --> 00:06:58.479 align:start position:0% Now the third available setup option is 00:06:58.479 --> 00:07:00.710 align:start position:0% Now the third available setup option is to<00:06:58.720> actually<00:06:59.039> install<00:06:59.440> this<00:06:59.759> directly<00:07:00.400> inside 00:07:00.710 --> 00:07:00.720 align:start position:0% to actually install this directly inside 00:07:00.720 --> 00:07:02.870 align:start position:0% to actually install this directly inside our<00:07:00.960> system<00:07:01.360> terminal. 00:07:02.870 --> 00:07:02.880 align:start position:0% our system terminal. 00:07:02.880 --> 00:07:05.350 align:start position:0% our system terminal. For<00:07:03.199> this<00:07:03.360> specific<00:07:03.840> method,<00:07:04.800> just<00:07:05.120> look 00:07:05.350 --> 00:07:05.360 align:start position:0% For this specific method, just look 00:07:05.360 --> 00:07:07.430 align:start position:0% For this specific method, just look closely<00:07:05.840> at<00:07:06.080> the<00:07:06.479> keep<00:07:06.800> going<00:07:07.120> in<00:07:07.280> the 00:07:07.430 --> 00:07:07.440 align:start position:0% closely at the keep going in the 00:07:07.440 --> 00:07:10.550 align:start position:0% closely at the keep going in the terminal<00:07:08.080> prompt<00:07:08.479> section.<00:07:09.840> We<00:07:10.080> carefully 00:07:10.550 --> 00:07:10.560 align:start position:0% terminal prompt section. We carefully 00:07:10.560 --> 00:07:12.629 align:start position:0% terminal prompt section. We carefully copy<00:07:10.960> this<00:07:11.280> exact<00:07:11.680> command<00:07:12.080> string<00:07:12.319> to<00:07:12.479> our 00:07:12.629 --> 00:07:12.639 align:start position:0% copy this exact command string to our 00:07:12.639 --> 00:07:14.309 align:start position:0% copy this exact command string to our clipboard. 00:07:14.309 --> 00:07:14.319 align:start position:0% clipboard. 00:07:14.319 --> 00:07:16.870 align:start position:0% clipboard. Following<00:07:14.720> that,<00:07:15.440> we<00:07:15.759> explicitly<00:07:16.400> open<00:07:16.639> up 00:07:16.870 --> 00:07:16.880 align:start position:0% Following that, we explicitly open up 00:07:16.880 --> 00:07:19.510 align:start position:0% Following that, we explicitly open up the<00:07:17.120> system<00:07:17.520> command<00:07:18.000> prompt,<00:07:18.960> making<00:07:19.280> sure 00:07:19.510 --> 00:07:19.520 align:start position:0% the system command prompt, making sure 00:07:19.520 --> 00:07:22.629 align:start position:0% the system command prompt, making sure to<00:07:19.680> run<00:07:19.919> it<00:07:20.080> strictly<00:07:20.479> as<00:07:20.720> an<00:07:20.880> administrator. 00:07:22.629 --> 00:07:22.639 align:start position:0% to run it strictly as an administrator. 00:07:22.639 --> 00:07:24.469 align:start position:0% to run it strictly as an administrator. The<00:07:22.880> Windows<00:07:23.360> PowerShell<00:07:23.919> interface 00:07:24.469 --> 00:07:24.479 align:start position:0% The Windows PowerShell interface 00:07:24.479 --> 00:07:27.510 align:start position:0% The Windows PowerShell interface naturally<00:07:25.039> opens<00:07:25.360> up<00:07:26.560> within<00:07:26.960> PowerShell 00:07:27.510 --> 00:07:27.520 align:start position:0% naturally opens up within PowerShell 00:07:27.520 --> 00:07:30.550 align:start position:0% naturally opens up within PowerShell itself.<00:07:28.400> We<00:07:28.639> formally<00:07:29.120> install<00:07:29.520> the<00:07:29.759> OpenAI 00:07:30.550 --> 00:07:30.560 align:start position:0% itself. We formally install the OpenAI 00:07:30.560 --> 00:07:33.589 align:start position:0% itself. We formally install the OpenAI codeex<00:07:31.120> tool<00:07:31.919> utilizing<00:07:32.400> the<00:07:32.639> npm<00:07:33.199> package 00:07:33.589 --> 00:07:33.599 align:start position:0% codeex tool utilizing the npm package 00:07:33.599 --> 00:07:37.029 align:start position:0% codeex tool utilizing the npm package manager.<00:07:35.039> Naturally,<00:07:36.080> it<00:07:36.319> will<00:07:36.560> definitely 00:07:37.029 --> 00:07:37.039 align:start position:0% manager. Naturally, it will definitely 00:07:37.039 --> 00:07:38.629 align:start position:0% manager. Naturally, it will definitely take<00:07:37.280> a<00:07:37.520> little<00:07:37.680> bit<00:07:37.840> of<00:07:38.000> time<00:07:38.160> to<00:07:38.400> fully 00:07:38.629 --> 00:07:38.639 align:start position:0% take a little bit of time to fully 00:07:38.639 --> 00:07:41.670 align:start position:0% take a little bit of time to fully install<00:07:39.120> properly.<00:07:40.479> The<00:07:40.720> underlying<00:07:41.280> system 00:07:41.670 --> 00:07:41.680 align:start position:0% install properly. The underlying system 00:07:41.680 --> 00:07:43.909 align:start position:0% install properly. The underlying system will<00:07:42.000> sequentially<00:07:42.639> gather<00:07:43.039> necessary<00:07:43.599> data 00:07:43.909 --> 00:07:43.919 align:start position:0% will sequentially gather necessary data 00:07:43.919 --> 00:07:47.510 align:start position:0% will sequentially gather necessary data in<00:07:44.160> a<00:07:44.400> much<00:07:44.560> better<00:07:44.880> way.<00:07:46.240> Codeex<00:07:46.880> is<00:07:47.039> actively 00:07:47.510 --> 00:07:47.520 align:start position:0% in a much better way. Codeex is actively 00:07:47.520 --> 00:07:50.710 align:start position:0% in a much better way. Codeex is actively installing<00:07:48.319> and<00:07:48.560> we<00:07:48.720> have<00:07:48.800> our<00:07:49.039> app<00:07:49.280> ready. 00:07:50.710 --> 00:07:50.720 align:start position:0% installing and we have our app ready. 00:07:50.720 --> 00:07:53.670 align:start position:0% installing and we have our app ready. Now<00:07:51.360> we<00:07:51.599> go<00:07:51.759> to<00:07:51.919> settings. 00:07:53.670 --> 00:07:53.680 align:start position:0% Now we go to settings. 00:07:53.680 --> 00:07:55.270 align:start position:0% Now we go to settings. We<00:07:53.919> purposefully<00:07:54.560> open<00:07:54.800> the<00:07:55.039> main 00:07:55.270 --> 00:07:55.280 align:start position:0% We purposefully open the main 00:07:55.280 --> 00:07:57.189 align:start position:0% We purposefully open the main application<00:07:55.919> settings<00:07:56.400> directly<00:07:56.879> from<00:07:57.039> the 00:07:57.189 --> 00:07:57.199 align:start position:0% application settings directly from the 00:07:57.199 --> 00:07:59.110 align:start position:0% application settings directly from the main<00:07:57.440> dashboard. 00:07:59.110 --> 00:07:59.120 align:start position:0% main dashboard. 00:07:59.120 --> 00:08:01.110 align:start position:0% main dashboard. Once<00:07:59.440> inside<00:07:59.840> the<00:08:00.080> comprehensive<00:08:00.720> settings 00:08:01.110 --> 00:08:01.120 align:start position:0% Once inside the comprehensive settings 00:08:01.120 --> 00:08:03.510 align:start position:0% Once inside the comprehensive settings menu,<00:08:02.000> there<00:08:02.160> are<00:08:02.400> actually<00:08:02.720> many<00:08:03.120> different 00:08:03.510 --> 00:08:03.520 align:start position:0% menu, there are actually many different 00:08:03.520 --> 00:08:06.390 align:start position:0% menu, there are actually many different customizable<00:08:04.319> options<00:08:04.639> available. 00:08:06.390 --> 00:08:06.400 align:start position:0% customizable options available. 00:08:06.400 --> 00:08:08.309 align:start position:0% customizable options available. I<00:08:06.720> specifically<00:08:07.360> navigate<00:08:07.840> over<00:08:08.000> to<00:08:08.160> the 00:08:08.309 --> 00:08:08.319 align:start position:0% I specifically navigate over to the 00:08:08.319 --> 00:08:10.469 align:start position:0% I specifically navigate over to the appearance<00:08:08.800> tab<00:08:09.520> in<00:08:09.759> order<00:08:09.919> to<00:08:10.080> make<00:08:10.319> some 00:08:10.469 --> 00:08:10.479 align:start position:0% appearance tab in order to make some 00:08:10.479 --> 00:08:13.350 align:start position:0% appearance tab in order to make some visual<00:08:10.879> interface<00:08:11.440> changes. 00:08:13.350 --> 00:08:13.360 align:start position:0% visual interface changes. 00:08:13.360 --> 00:08:15.589 align:start position:0% visual interface changes. First,<00:08:13.840> I<00:08:14.080> completely<00:08:14.560> change<00:08:14.879> the<00:08:15.120> overall 00:08:15.589 --> 00:08:15.599 align:start position:0% First, I completely change the overall 00:08:15.599 --> 00:08:17.909 align:start position:0% First, I completely change the overall display<00:08:16.000> theme<00:08:16.560> to<00:08:16.800> a<00:08:17.039> comfortable<00:08:17.520> dark 00:08:17.909 --> 00:08:17.919 align:start position:0% display theme to a comfortable dark 00:08:17.919 --> 00:08:19.830 align:start position:0% display theme to a comfortable dark mode. 00:08:19.830 --> 00:08:19.840 align:start position:0% mode. 00:08:19.840 --> 00:08:22.150 align:start position:0% mode. Next,<00:08:20.319> I<00:08:20.560> noticeably<00:08:21.280> increase<00:08:21.520> the<00:08:21.840> base 00:08:22.150 --> 00:08:22.160 align:start position:0% Next, I noticeably increase the base 00:08:22.160 --> 00:08:26.550 align:start position:0% Next, I noticeably increase the base system<00:08:22.720> UI<00:08:23.360> size<00:08:24.000> for<00:08:24.240> better<00:08:24.560> visibility. 00:08:26.550 --> 00:08:26.560 align:start position:0% system UI size for better visibility. 00:08:26.560 --> 00:08:28.629 align:start position:0% system UI size for better visibility. We<00:08:26.800> then<00:08:27.039> carefully<00:08:27.599> choose<00:08:27.919> our<00:08:28.160> preferred 00:08:28.629 --> 00:08:28.639 align:start position:0% We then carefully choose our preferred 00:08:28.639 --> 00:08:30.869 align:start position:0% We then carefully choose our preferred font<00:08:28.960> style<00:08:29.680> and<00:08:30.000> slightly<00:08:30.400> adjust<00:08:30.720> the 00:08:30.869 --> 00:08:30.879 align:start position:0% font style and slightly adjust the 00:08:30.879 --> 00:08:33.029 align:start position:0% font style and slightly adjust the visual<00:08:31.199> contrast. 00:08:33.029 --> 00:08:33.039 align:start position:0% visual contrast. 00:08:33.039 --> 00:08:35.829 align:start position:0% visual contrast. Initially,<00:08:33.680> I<00:08:33.919> confidently<00:08:34.560> write<00:08:34.719> in<00:08:35.120> 32<00:08:35.680> for 00:08:35.829 --> 00:08:35.839 align:start position:0% Initially, I confidently write in 32 for 00:08:35.839 --> 00:08:38.630 align:start position:0% Initially, I confidently write in 32 for the<00:08:36.080> primary<00:08:36.399> font<00:08:36.719> size.<00:08:37.760> However,<00:08:38.320> upon 00:08:38.630 --> 00:08:38.640 align:start position:0% the primary font size. However, upon 00:08:38.640 --> 00:08:42.149 align:start position:0% the primary font size. However, upon seeing<00:08:38.959> it,<00:08:39.919> 32<00:08:40.479> is<00:08:40.719> admittedly<00:08:41.440> just<00:08:41.680> a<00:08:41.919> bit 00:08:42.149 --> 00:08:42.159 align:start position:0% seeing it, 32 is admittedly just a bit 00:08:42.159 --> 00:08:45.190 align:start position:0% seeing it, 32 is admittedly just a bit too<00:08:42.399> big<00:08:42.640> for<00:08:42.880> my<00:08:43.039> screen.<00:08:44.399> So,<00:08:44.640> I<00:08:44.880> quickly 00:08:45.190 --> 00:08:45.200 align:start position:0% too big for my screen. So, I quickly 00:08:45.200 --> 00:08:48.230 align:start position:0% too big for my screen. So, I quickly change<00:08:45.440> it<00:08:45.680> down<00:08:45.920> to<00:08:46.160> exactly<00:08:46.720> 24. 00:08:48.230 --> 00:08:48.240 align:start position:0% change it down to exactly 24. 00:08:48.240 --> 00:08:51.110 align:start position:0% change it down to exactly 24. Honestly,<00:08:49.120> 24<00:08:49.680> is<00:08:49.839> a<00:08:50.080> genuinely<00:08:50.640> comfortable 00:08:51.110 --> 00:08:51.120 align:start position:0% Honestly, 24 is a genuinely comfortable 00:08:51.120 --> 00:08:54.550 align:start position:0% Honestly, 24 is a genuinely comfortable size<00:08:51.600> for<00:08:51.920> long<00:08:52.240> coding<00:08:52.640> sessions. 00:08:54.550 --> 00:08:54.560 align:start position:0% size for long coding sessions. 00:08:54.560 --> 00:08:57.350 align:start position:0% size for long coding sessions. For<00:08:54.800> the<00:08:54.959> dedicated<00:08:55.519> code<00:08:55.839> font,<00:08:56.560> we<00:08:56.880> firmly 00:08:57.350 --> 00:08:57.360 align:start position:0% For the dedicated code font, we firmly 00:08:57.360 --> 00:09:00.070 align:start position:0% For the dedicated code font, we firmly use<00:08:57.839> size<00:08:58.320> 20. 00:09:00.070 --> 00:09:00.080 align:start position:0% use size 20. 00:09:00.080 --> 00:09:02.949 align:start position:0% use size 20. Moving<00:09:00.480> on,<00:09:01.120> we<00:09:01.440> strategically<00:09:02.240> turn<00:09:02.480> off<00:09:02.720> the 00:09:02.949 --> 00:09:02.959 align:start position:0% Moving on, we strategically turn off the 00:09:02.959 --> 00:09:05.509 align:start position:0% Moving on, we strategically turn off the reduce<00:09:03.360> motion<00:09:03.839> option. 00:09:05.509 --> 00:09:05.519 align:start position:0% reduce motion option. 00:09:05.519 --> 00:09:07.590 align:start position:0% reduce motion option. We<00:09:05.760> ensure<00:09:06.080> we<00:09:06.399> use<00:09:06.640> standard<00:09:07.120> pointer 00:09:07.590 --> 00:09:07.600 align:start position:0% We ensure we use standard pointer 00:09:07.600 --> 00:09:09.990 align:start position:0% We ensure we use standard pointer cursors<00:09:08.399> and<00:09:08.720> gently<00:09:09.200> lower<00:09:09.440> the<00:09:09.680> screen 00:09:09.990 --> 00:09:10.000 align:start position:0% cursors and gently lower the screen 00:09:10.000 --> 00:09:12.070 align:start position:0% cursors and gently lower the screen contrast. 00:09:12.070 --> 00:09:12.080 align:start position:0% contrast. 00:09:12.080 --> 00:09:14.870 align:start position:0% contrast. Everything<00:09:12.480> is<00:09:12.720> working<00:09:13.040> well.<00:09:14.240> Honestly, 00:09:14.870 --> 00:09:14.880 align:start position:0% Everything is working well. Honestly, 00:09:14.880 --> 00:09:17.110 align:start position:0% Everything is working well. Honestly, the<00:09:15.200> overall<00:09:15.600> reading<00:09:16.000> experience<00:09:16.560> is<00:09:16.800> just 00:09:17.110 --> 00:09:17.120 align:start position:0% the overall reading experience is just 00:09:17.120 --> 00:09:19.750 align:start position:0% the overall reading experience is just so<00:09:17.360> much<00:09:17.600> better<00:09:17.920> right<00:09:18.240> now. 00:09:19.750 --> 00:09:19.760 align:start position:0% so much better right now. 00:09:19.760 --> 00:09:21.590 align:start position:0% so much better right now. Before<00:09:20.080> we<00:09:20.240> made<00:09:20.480> those<00:09:20.720> crucial<00:09:21.200> visual 00:09:21.590 --> 00:09:21.600 align:start position:0% Before we made those crucial visual 00:09:21.600 --> 00:09:23.910 align:start position:0% Before we made those crucial visual tweaks,<00:09:22.480> the<00:09:22.720> default<00:09:23.120> text<00:09:23.440> font<00:09:23.760> was 00:09:23.910 --> 00:09:23.920 align:start position:0% tweaks, the default text font was 00:09:23.920 --> 00:09:26.470 align:start position:0% tweaks, the default text font was incredibly<00:09:24.560> small<00:09:25.200> and<00:09:25.519> honestly<00:09:26.000> hard<00:09:26.320> to 00:09:26.470 --> 00:09:26.480 align:start position:0% incredibly small and honestly hard to 00:09:26.480 --> 00:09:29.750 align:start position:0% incredibly small and honestly hard to read.<00:09:27.760> We<00:09:28.080> absolutely<00:09:28.720> had<00:09:28.959> to<00:09:29.120> step<00:09:29.360> in<00:09:29.519> and 00:09:29.750 --> 00:09:29.760 align:start position:0% read. We absolutely had to step in and 00:09:29.760 --> 00:09:31.670 align:start position:0% read. We absolutely had to step in and make<00:09:29.920> the<00:09:30.160> font<00:09:30.480> significantly<00:09:31.120> bigger<00:09:31.519> for 00:09:31.670 --> 00:09:31.680 align:start position:0% make the font significantly bigger for 00:09:31.680 --> 00:09:33.590 align:start position:0% make the font significantly bigger for basic<00:09:32.000> clarity. 00:09:33.590 --> 00:09:33.600 align:start position:0% basic clarity. 00:09:33.600 --> 00:09:36.949 align:start position:0% basic clarity. I<00:09:33.920> truly<00:09:34.320> believe<00:09:34.560> that<00:09:34.959> 24<00:09:35.519> and<00:09:35.920> 20<00:09:36.640> are 00:09:36.949 --> 00:09:36.959 align:start position:0% I truly believe that 24 and 20 are 00:09:36.959 --> 00:09:39.269 align:start position:0% I truly believe that 24 and 20 are excellent,<00:09:37.680> highly<00:09:38.160> optimized<00:09:38.720> sizes<00:09:39.120> for 00:09:39.269 --> 00:09:39.279 align:start position:0% excellent, highly optimized sizes for 00:09:39.279 --> 00:09:42.470 align:start position:0% excellent, highly optimized sizes for our<00:09:39.519> daily<00:09:39.760> coding<00:09:40.240> tasks. 00:09:42.470 --> 00:09:42.480 align:start position:0% our daily coding tasks. 00:09:42.480 --> 00:09:45.030 align:start position:0% our daily coding tasks. Now,<00:09:43.200> if<00:09:43.440> we<00:09:43.600> quickly<00:09:44.000> navigate<00:09:44.480> over<00:09:44.640> to<00:09:44.800> the 00:09:45.030 --> 00:09:45.040 align:start position:0% Now, if we quickly navigate over to the 00:09:45.040 --> 00:09:47.670 align:start position:0% Now, if we quickly navigate over to the general<00:09:45.360> configuration<00:09:46.080> settings<00:09:46.480> menu,<00:09:47.440> we 00:09:47.670 --> 00:09:47.680 align:start position:0% general configuration settings menu, we 00:09:47.680 --> 00:09:49.670 align:start position:0% general configuration settings menu, we can<00:09:47.839> clearly<00:09:48.240> see<00:09:48.560> multiple<00:09:49.120> distinct 00:09:49.670 --> 00:09:49.680 align:start position:0% can clearly see multiple distinct 00:09:49.680 --> 00:09:51.670 align:start position:0% can clearly see multiple distinct operational<00:09:50.320> modes<00:09:50.720> available<00:09:51.120> to<00:09:51.360> choose 00:09:51.670 --> 00:09:51.680 align:start position:0% operational modes available to choose 00:09:51.680 --> 00:09:54.550 align:start position:0% operational modes available to choose from.<00:09:53.040> I<00:09:53.279> promise<00:09:53.600> that<00:09:53.760> I<00:09:54.000> will<00:09:54.160> carefully 00:09:54.550 --> 00:09:54.560 align:start position:0% from. I promise that I will carefully 00:09:54.560 --> 00:09:56.550 align:start position:0% from. I promise that I will carefully explain<00:09:55.040> all<00:09:55.279> of<00:09:55.440> these<00:09:55.680> specific<00:09:56.160> working 00:09:56.550 --> 00:09:56.560 align:start position:0% explain all of these specific working 00:09:56.560 --> 00:09:58.949 align:start position:0% explain all of these specific working modes<00:09:57.200> in<00:09:57.440> much<00:09:57.760> greater<00:09:58.080> detail<00:09:58.560> a<00:09:58.800> little 00:09:58.949 --> 00:09:58.959 align:start position:0% modes in much greater detail a little 00:09:58.959 --> 00:10:02.150 align:start position:0% modes in much greater detail a little bit<00:09:59.120> later<00:09:59.360> on.<00:10:00.720> Right<00:10:00.959> now,<00:10:01.680> all<00:10:01.920> our 00:10:02.150 --> 00:10:02.160 align:start position:0% bit later on. Right now, all our 00:10:02.160 --> 00:10:03.750 align:start position:0% bit later on. Right now, all our required<00:10:02.640> system<00:10:02.959> packages<00:10:03.519> are 00:10:03.750 --> 00:10:03.760 align:start position:0% required system packages are 00:10:03.760 --> 00:10:06.070 align:start position:0% required system packages are successfully<00:10:04.399> installed. 00:10:06.070 --> 00:10:06.080 align:start position:0% successfully installed. 00:10:06.080 --> 00:10:09.269 align:start position:0% successfully installed. The<00:10:06.320> powerful<00:10:06.800> Open<00:10:07.200> AI<00:10:07.680> codeex<00:10:08.160> itself<00:10:08.880> is 00:10:09.269 --> 00:10:09.279 align:start position:0% The powerful Open AI codeex itself is 00:10:09.279 --> 00:10:11.590 align:start position:0% The powerful Open AI codeex itself is completely<00:10:09.760> installed. 00:10:11.590 --> 00:10:11.600 align:start position:0% completely installed. 00:10:11.600 --> 00:10:13.670 align:start position:0% completely installed. Now<00:10:12.320> we<00:10:12.560> just<00:10:12.959> essentially<00:10:13.360> need<00:10:13.519> to 00:10:13.670 --> 00:10:13.680 align:start position:0% Now we just essentially need to 00:10:13.680 --> 00:10:16.710 align:start position:0% Now we just essentially need to forcefully<00:10:14.240> run<00:10:14.399> it<00:10:14.560> one<00:10:14.800> more<00:10:14.959> time. 00:10:16.710 --> 00:10:16.720 align:start position:0% forcefully run it one more time. 00:10:16.720 --> 00:10:19.670 align:start position:0% forcefully run it one more time. I<00:10:17.040> smoothly<00:10:17.600> tab<00:10:17.920> back<00:10:18.160> over<00:10:18.399> to<00:10:18.560> the<00:10:18.640> chat<00:10:19.040> GPT 00:10:19.670 --> 00:10:19.680 align:start position:0% I smoothly tab back over to the chat GPT 00:10:19.680 --> 00:10:22.949 align:start position:0% I smoothly tab back over to the chat GPT window.<00:10:21.040> I<00:10:21.440> explicitly<00:10:22.079> type<00:10:22.399> out<00:10:22.720> and 00:10:22.949 --> 00:10:22.959 align:start position:0% window. I explicitly type out and 00:10:22.959 --> 00:10:25.750 align:start position:0% window. I explicitly type out and clearly<00:10:23.360> ask.<00:10:24.399> I<00:10:24.640> have<00:10:24.880> basically<00:10:25.279> run<00:10:25.519> this 00:10:25.750 --> 00:10:25.760 align:start position:0% clearly ask. I have basically run this 00:10:25.760 --> 00:10:28.069 align:start position:0% clearly ask. I have basically run this command<00:10:26.000> in<00:10:26.240> the<00:10:26.399> terminal.<00:10:27.360> What<00:10:27.600> do<00:10:27.760> I<00:10:27.920> do 00:10:28.069 --> 00:10:28.079 align:start position:0% command in the terminal. What do I do 00:10:28.079 --> 00:10:30.710 align:start position:0% command in the terminal. What do I do next<00:10:28.320> to<00:10:28.560> start<00:10:28.800> it? 00:10:30.710 --> 00:10:30.720 align:start position:0% next to start it? 00:10:30.720 --> 00:10:33.110 align:start position:0% next to start it? We<00:10:30.959> will<00:10:31.200> now<00:10:31.519> officially<00:10:32.079> start<00:10:32.320> the<00:10:32.560> require 00:10:33.110 --> 00:10:33.120 align:start position:0% We will now officially start the require 00:10:33.120 --> 00:10:35.190 align:start position:0% We will now officially start the require process<00:10:33.760> right<00:10:34.000> here<00:10:34.320> within<00:10:34.640> our<00:10:34.800> local 00:10:35.190 --> 00:10:35.200 align:start position:0% process right here within our local 00:10:35.200 --> 00:10:38.150 align:start position:0% process right here within our local system<00:10:35.600> terminal.<00:10:36.959> The<00:10:37.279> entire<00:10:37.680> background 00:10:38.150 --> 00:10:38.160 align:start position:0% system terminal. The entire background 00:10:38.160 --> 00:10:39.990 align:start position:0% system terminal. The entire background installation<00:10:38.720> procedure<00:10:39.279> is<00:10:39.519> completely 00:10:39.990 --> 00:10:40.000 align:start position:0% installation procedure is completely 00:10:40.000 --> 00:10:42.710 align:start position:0% installation procedure is completely finished.<00:10:41.120> It<00:10:41.360> successfully<00:10:42.000> managed<00:10:42.320> to<00:10:42.480> add 00:10:42.710 --> 00:10:42.720 align:start position:0% finished. It successfully managed to add 00:10:42.720 --> 00:10:45.190 align:start position:0% finished. It successfully managed to add two<00:10:42.959> vital<00:10:43.440> software<00:10:43.839> packages<00:10:44.720> in<00:10:44.959> just 00:10:45.190 --> 00:10:45.200 align:start position:0% two vital software packages in just 00:10:45.200 --> 00:10:48.630 align:start position:0% two vital software packages in just about<00:10:45.519> 36<00:10:46.079> seconds<00:10:46.480> total.<00:10:47.920> The<00:10:48.160> software 00:10:48.630 --> 00:10:48.640 align:start position:0% about 36 seconds total. The software 00:10:48.640 --> 00:10:50.550 align:start position:0% about 36 seconds total. The software carefully<00:10:49.120> checks<00:10:49.440> the<00:10:49.680> current<00:10:50.000> MPM 00:10:50.550 --> 00:10:50.560 align:start position:0% carefully checks the current MPM 00:10:50.560 --> 00:10:52.870 align:start position:0% carefully checks the current MPM installation<00:10:51.200> status<00:10:52.079> alongside<00:10:52.640> the 00:10:52.870 --> 00:10:52.880 align:start position:0% installation status alongside the 00:10:52.880 --> 00:10:56.310 align:start position:0% installation status alongside the available<00:10:53.360> AI<00:10:53.760> models.<00:10:55.040> First<00:10:55.279> and<00:10:55.519> foremost, 00:10:56.310 --> 00:10:56.320 align:start position:0% available AI models. First and foremost, 00:10:56.320 --> 00:10:58.630 align:start position:0% available AI models. First and foremost, we<00:10:56.640> must<00:10:56.800> verify<00:10:57.360> the<00:10:57.600> active<00:10:58.079> codeex 00:10:58.630 --> 00:10:58.640 align:start position:0% we must verify the active codeex 00:10:58.640 --> 00:11:02.310 align:start position:0% we must verify the active codeex version.<00:10:59.839> I<00:11:00.079> simply<00:11:00.480> type<00:11:00.959> MPM<00:11:01.600> codeex 00:11:02.310 --> 00:11:02.320 align:start position:0% version. I simply type MPM codeex 00:11:02.320 --> 00:11:05.269 align:start position:0% version. I simply type MPM codeex directly<00:11:02.800> into<00:11:03.040> the<00:11:03.279> prompt.<00:11:04.480> The<00:11:04.800> resulting 00:11:05.269 --> 00:11:05.279 align:start position:0% directly into the prompt. The resulting 00:11:05.279 --> 00:11:08.630 align:start position:0% directly into the prompt. The resulting Codeex<00:11:05.920> CLI<00:11:06.480> version<00:11:07.279> currently<00:11:07.760> shows<00:11:08.079> up<00:11:08.240> as 00:11:08.630 --> 00:11:08.640 align:start position:0% Codeex CLI version currently shows up as 00:11:08.640 --> 00:11:12.069 align:start position:0% Codeex CLI version currently shows up as 0.139.0. 00:11:12.069 --> 00:11:12.079 align:start position:0% 00:11:12.079 --> 00:11:15.110 align:start position:0% Next,<00:11:12.720> we<00:11:12.959> actively<00:11:13.440> run<00:11:13.760> Codeex,<00:11:14.480> so<00:11:14.720> we<00:11:14.959> can 00:11:15.110 --> 00:11:15.120 align:start position:0% Next, we actively run Codeex, so we can 00:11:15.120 --> 00:11:18.550 align:start position:0% Next, we actively run Codeex, so we can finally<00:11:15.680> start<00:11:15.839> to<00:11:16.160> code.<00:11:17.200> We<00:11:17.440> type<00:11:17.839> codeex 00:11:18.550 --> 00:11:18.560 align:start position:0% finally start to code. We type codeex 00:11:18.560 --> 00:11:21.190 align:start position:0% finally start to code. We type codeex right<00:11:18.880> into<00:11:19.120> the<00:11:19.360> system<00:11:19.680> environment. 00:11:21.190 --> 00:11:21.200 align:start position:0% right into the system environment. 00:11:21.200 --> 00:11:23.430 align:start position:0% right into the system environment. A<00:11:21.519> brand<00:11:21.760> new<00:11:22.160> security<00:11:22.640> message<00:11:23.120> suddenly 00:11:23.430 --> 00:11:23.440 align:start position:0% A brand new security message suddenly 00:11:23.440 --> 00:11:27.030 align:start position:0% A brand new security message suddenly appears<00:11:23.839> on<00:11:24.000> the<00:11:24.160> screen.<00:11:25.440> It<00:11:25.680> clearly<00:11:26.160> asks, 00:11:27.030 --> 00:11:27.040 align:start position:0% appears on the screen. It clearly asks, 00:11:27.040 --> 00:11:29.269 align:start position:0% appears on the screen. It clearly asks, "Do<00:11:27.440> you<00:11:27.680> currently<00:11:28.160> trust<00:11:28.560> the<00:11:28.800> exact 00:11:29.269 --> 00:11:29.279 align:start position:0% "Do you currently trust the exact 00:11:29.279 --> 00:11:32.389 align:start position:0% "Do you currently trust the exact contents<00:11:29.680> of<00:11:29.920> this<00:11:30.160> specific<00:11:30.720> directory?" 00:11:32.389 --> 00:11:32.399 align:start position:0% contents of this specific directory?" 00:11:32.399 --> 00:11:35.350 align:start position:0% contents of this specific directory?" Working<00:11:32.880> directly<00:11:33.360> with<00:11:33.600> untrusted<00:11:34.399> contents 00:11:35.350 --> 00:11:35.360 align:start position:0% Working directly with untrusted contents 00:11:35.360 --> 00:11:37.350 align:start position:0% Working directly with untrusted contents definitely<00:11:35.920> carries<00:11:36.399> inherent<00:11:36.880> security 00:11:37.350 --> 00:11:37.360 align:start position:0% definitely carries inherent security 00:11:37.360 --> 00:11:40.870 align:start position:0% definitely carries inherent security risks<00:11:38.079> or<00:11:38.480> potential<00:11:38.959> prompt<00:11:39.279> injections. 00:11:40.870 --> 00:11:40.880 align:start position:0% risks or potential prompt injections. 00:11:40.880 --> 00:11:43.509 align:start position:0% risks or potential prompt injections. Trusting<00:11:41.360> that<00:11:41.680> directory<00:11:42.240> directly<00:11:43.120> allows 00:11:43.509 --> 00:11:43.519 align:start position:0% Trusting that directory directly allows 00:11:43.519 --> 00:11:45.269 align:start position:0% Trusting that directory directly allows for<00:11:43.760> reading<00:11:44.160> local<00:11:44.480> configuration 00:11:45.269 --> 00:11:45.279 align:start position:0% for reading local configuration 00:11:45.279 --> 00:11:48.630 align:start position:0% for reading local configuration settings.<00:11:46.720> I<00:11:47.040> confidently<00:11:47.600> click<00:11:47.920> yes<00:11:48.399> and 00:11:48.630 --> 00:11:48.640 align:start position:0% settings. I confidently click yes and 00:11:48.640 --> 00:11:50.949 align:start position:0% settings. I confidently click yes and smoothly<00:11:49.200> continue. 00:11:50.949 --> 00:11:50.959 align:start position:0% smoothly continue. 00:11:50.959 --> 00:11:52.949 align:start position:0% smoothly continue. After<00:11:51.360> successfully<00:11:51.920> getting<00:11:52.160> that<00:11:52.480> required 00:11:52.949 --> 00:11:52.959 align:start position:0% After successfully getting that required 00:11:52.959 --> 00:11:55.990 align:start position:0% After successfully getting that required yes<00:11:53.360> confirmation,<00:11:54.640> we<00:11:54.880> now<00:11:55.200> finally<00:11:55.760> have 00:11:55.990 --> 00:11:56.000 align:start position:0% yes confirmation, we now finally have 00:11:56.000 --> 00:11:59.269 align:start position:0% yes confirmation, we now finally have our<00:11:56.320> direct<00:11:56.800> working<00:11:57.200> option<00:11:57.600> ready<00:11:57.839> to<00:11:58.079> go. 00:11:59.269 --> 00:11:59.279 align:start position:0% our direct working option ready to go. 00:11:59.279 --> 00:12:01.829 align:start position:0% our direct working option ready to go. We<00:11:59.600> have<00:11:59.680> the<00:12:00.000> full<00:12:00.320> power<00:12:00.640> of<00:12:00.800> the<00:12:01.040> open<00:12:01.360> AI 00:12:01.829 --> 00:12:01.839 align:start position:0% We have the full power of the open AI 00:12:01.839 --> 00:12:04.310 align:start position:0% We have the full power of the open AI codeex<00:12:02.320> at<00:12:02.560> our<00:12:02.720> fingertips. 00:12:04.310 --> 00:12:04.320 align:start position:0% codeex at our fingertips. 00:12:04.320 --> 00:12:07.110 align:start position:0% codeex at our fingertips. Our<00:12:04.640> specifically<00:12:05.360> selected<00:12:05.920> AI<00:12:06.320> model<00:12:06.800> is 00:12:07.110 --> 00:12:07.120 align:start position:0% Our specifically selected AI model is 00:12:07.120 --> 00:12:10.230 align:start position:0% Our specifically selected AI model is currently<00:12:07.680> GPT<00:12:08.560> 5.5. 00:12:10.230 --> 00:12:10.240 align:start position:0% currently GPT 5.5. 00:12:10.240 --> 00:12:12.870 align:start position:0% currently GPT 5.5. Our<00:12:10.480> active<00:12:10.959> working<00:12:11.360> directory<00:12:12.160> is<00:12:12.480> listed 00:12:12.870 --> 00:12:12.880 align:start position:0% Our active working directory is listed 00:12:12.880 --> 00:12:15.910 align:start position:0% Our active working directory is listed safely<00:12:13.360> as<00:12:13.600> system<00:12:14.160> 32. 00:12:15.910 --> 00:12:15.920 align:start position:0% safely as system 32. 00:12:15.920 --> 00:12:18.069 align:start position:0% safely as system 32. We<00:12:16.160> can<00:12:16.399> comfortably<00:12:16.959> make<00:12:17.279> direct<00:12:17.760> code 00:12:18.069 --> 00:12:18.079 align:start position:0% We can comfortably make direct code 00:12:18.079 --> 00:12:20.949 align:start position:0% We can comfortably make direct code changes<00:12:18.560> right<00:12:18.880> here<00:12:19.120> in<00:12:19.360> this<00:12:19.600> space. 00:12:20.949 --> 00:12:20.959 align:start position:0% changes right here in this space. 00:12:20.959 --> 00:12:23.430 align:start position:0% changes right here in this space. If<00:12:21.200> I<00:12:21.440> quickly<00:12:21.839> send<00:12:22.079> over<00:12:22.399> a<00:12:22.639> very<00:12:23.040> simple 00:12:23.430 --> 00:12:23.440 align:start position:0% If I quickly send over a very simple 00:12:23.440 --> 00:12:26.150 align:start position:0% If I quickly send over a very simple introductory<00:12:24.160> message,<00:12:25.200> it<00:12:25.440> impressively 00:12:26.150 --> 00:12:26.160 align:start position:0% introductory message, it impressively 00:12:26.160 --> 00:12:29.110 align:start position:0% introductory message, it impressively replies<00:12:26.639> back<00:12:27.040> almost<00:12:27.440> automatically. 00:12:29.110 --> 00:12:29.120 align:start position:0% replies back almost automatically. 00:12:29.120 --> 00:12:32.389 align:start position:0% replies back almost automatically. I<00:12:29.440> simply<00:12:29.760> write<00:12:30.079> out,<00:12:31.040> "Can<00:12:31.440> you<00:12:31.680> explicitly 00:12:32.389 --> 00:12:32.399 align:start position:0% I simply write out, "Can you explicitly 00:12:32.399 --> 00:12:35.269 align:start position:0% I simply write out, "Can you explicitly help<00:12:32.639> me<00:12:32.800> in<00:12:33.040> generating<00:12:33.680> some<00:12:33.920> basic<00:12:34.480> HTML 00:12:35.269 --> 00:12:35.279 align:start position:0% help me in generating some basic HTML 00:12:35.279 --> 00:12:36.790 align:start position:0% help me in generating some basic HTML code?" 00:12:36.790 --> 00:12:36.800 align:start position:0% code?" 00:12:36.800 --> 00:12:39.269 align:start position:0% code?" It<00:12:37.120> quickly<00:12:37.519> gives<00:12:37.839> a<00:12:38.079> remarkably<00:12:38.800> short, 00:12:39.269 --> 00:12:39.279 align:start position:0% It quickly gives a remarkably short, 00:12:39.279 --> 00:12:43.350 align:start position:0% It quickly gives a remarkably short, concise<00:12:39.839> response.<00:12:41.120> It<00:12:41.360> plainly<00:12:41.920> says,<00:12:42.480> "Yes, 00:12:43.350 --> 00:12:43.360 align:start position:0% concise response. It plainly says, "Yes, 00:12:43.360 --> 00:12:44.949 align:start position:0% concise response. It plainly says, "Yes, absolutely. 00:12:44.949 --> 00:12:44.959 align:start position:0% absolutely. 00:12:44.959 --> 00:12:47.030 align:start position:0% absolutely. Just<00:12:45.200> tell<00:12:45.440> me<00:12:45.760> exactly<00:12:46.160> what<00:12:46.399> you<00:12:46.639> want<00:12:46.800> the 00:12:47.030 --> 00:12:47.040 align:start position:0% Just tell me exactly what you want the 00:12:47.040 --> 00:12:49.990 align:start position:0% Just tell me exactly what you want the final<00:12:47.440> HTML<00:12:48.160> page<00:12:48.480> to<00:12:48.720> do<00:12:49.200> or<00:12:49.519> what<00:12:49.680> you<00:12:49.839> want 00:12:49.990 --> 00:12:50.000 align:start position:0% final HTML page to do or what you want 00:12:50.000 --> 00:12:53.590 align:start position:0% final HTML page to do or what you want it<00:12:50.160> to<00:12:50.320> look<00:12:50.480> like.<00:12:51.839> Paste<00:12:52.240> any<00:12:52.639> existing<00:12:53.279> code 00:12:53.590 --> 00:12:53.600 align:start position:0% it to look like. Paste any existing code 00:12:53.600 --> 00:12:56.470 align:start position:0% it to look like. Paste any existing code snippets<00:12:54.079> you<00:12:54.320> might<00:12:54.480> already<00:12:54.880> have. 00:12:56.470 --> 00:12:56.480 align:start position:0% snippets you might already have. 00:12:56.480 --> 00:12:58.389 align:start position:0% snippets you might already have. If<00:12:56.720> you<00:12:56.880> happen<00:12:57.120> to<00:12:57.360> start<00:12:57.600> entirely<00:12:58.160> from 00:12:58.389 --> 00:12:58.399 align:start position:0% If you happen to start entirely from 00:12:58.399 --> 00:13:01.190 align:start position:0% If you happen to start entirely from scratch,<00:12:59.279> I<00:12:59.519> can<00:12:59.680> easily<00:13:00.160> create<00:13:00.480> a<00:13:00.720> simple 00:13:01.190 --> 00:13:01.200 align:start position:0% scratch, I can easily create a simple 00:13:01.200 --> 00:13:04.550 align:start position:0% scratch, I can easily create a simple HTML<00:13:01.920> framework<00:13:02.399> for<00:13:02.639> you.<00:13:03.839> Our<00:13:04.079> coding 00:13:04.550 --> 00:13:04.560 align:start position:0% HTML framework for you. Our coding 00:13:04.560 --> 00:13:09.190 align:start position:0% HTML framework for you. Our coding journey<00:13:04.959> begins.<00:13:06.399> I<00:13:06.720> press<00:13:07.040> Ctrl<00:13:07.519> C<00:13:07.760> to<00:13:08.079> pause. 00:13:09.190 --> 00:13:09.200 align:start position:0% journey begins. I press Ctrl C to pause. 00:13:09.200 --> 00:13:12.069 align:start position:0% journey begins. I press Ctrl C to pause. It<00:13:09.519> shows<00:13:09.760> the<00:13:09.920> response.<00:13:11.360> The<00:13:11.600> interface 00:13:12.069 --> 00:13:12.079 align:start position:0% It shows the response. The interface 00:13:12.079 --> 00:13:13.910 align:start position:0% It shows the response. The interface clearly<00:13:12.480> displays<00:13:12.880> our<00:13:13.200> complete<00:13:13.519> token 00:13:13.910 --> 00:13:13.920 align:start position:0% clearly displays our complete token 00:13:13.920 --> 00:13:16.629 align:start position:0% clearly displays our complete token usage<00:13:14.320> statistics<00:13:15.040> right<00:13:15.279> on<00:13:15.519> the<00:13:15.680> screen. 00:13:16.629 --> 00:13:16.639 align:start position:0% usage statistics right on the screen. 00:13:16.639 --> 00:13:19.670 align:start position:0% usage statistics right on the screen. The<00:13:16.880> grand<00:13:17.200> total<00:13:17.600> comes<00:13:17.920> out<00:13:18.079> to<00:13:18.720> exactly 00:13:19.670 --> 00:13:19.680 align:start position:0% The grand total comes out to exactly 00:13:19.680 --> 00:13:21.829 align:start position:0% The grand total comes out to exactly 7,939 00:13:21.829 --> 00:13:21.839 align:start position:0% 7,939 00:13:21.839 --> 00:13:25.350 align:start position:0% 7,939 tokens<00:13:22.320> used.<00:13:23.760> The<00:13:24.000> initial<00:13:24.320> input<00:13:24.880> strictly 00:13:25.350 --> 00:13:25.360 align:start position:0% tokens used. The initial input strictly 00:13:25.360 --> 00:13:28.629 align:start position:0% tokens used. The initial input strictly accounted<00:13:25.760> for<00:13:26.560> 7,881 00:13:28.629 --> 00:13:28.639 align:start position:0% accounted for 7,881 00:13:28.639 --> 00:13:30.150 align:start position:0% accounted for 7,881 tokens. 00:13:30.150 --> 00:13:30.160 align:start position:0% tokens. 00:13:30.160 --> 00:13:32.470 align:start position:0% tokens. Meanwhile,<00:13:30.959> the<00:13:31.200> generated<00:13:31.760> output<00:13:32.160> was<00:13:32.320> a 00:13:32.470 --> 00:13:32.480 align:start position:0% Meanwhile, the generated output was a 00:13:32.480 --> 00:13:36.069 align:start position:0% Meanwhile, the generated output was a remarkably<00:13:33.120> short<00:13:33.760> 58<00:13:34.320> tokens. 00:13:36.069 --> 00:13:36.079 align:start position:0% remarkably short 58 tokens. 00:13:36.079 --> 00:13:38.310 align:start position:0% remarkably short 58 tokens. To<00:13:36.320> seamlessly<00:13:36.959> continue<00:13:37.360> this<00:13:37.600> exact<00:13:38.000> same 00:13:38.310 --> 00:13:38.320 align:start position:0% To seamlessly continue this exact same 00:13:38.320 --> 00:13:40.710 align:start position:0% To seamlessly continue this exact same chat<00:13:38.639> session,<00:13:39.440> we<00:13:39.680> carefully<00:13:40.160> copy<00:13:40.480> the 00:13:40.710 --> 00:13:40.720 align:start position:0% chat session, we carefully copy the 00:13:40.720 --> 00:13:43.110 align:start position:0% chat session, we carefully copy the provided<00:13:41.120> resume<00:13:41.600> command. 00:13:43.110 --> 00:13:43.120 align:start position:0% provided resume command. 00:13:43.120 --> 00:13:45.430 align:start position:0% provided resume command. I<00:13:43.440> smoothly<00:13:43.920> paste<00:13:44.160> that<00:13:44.480> specific<00:13:44.880> command 00:13:45.430 --> 00:13:45.440 align:start position:0% I smoothly paste that specific command 00:13:45.440 --> 00:13:48.550 align:start position:0% I smoothly paste that specific command right<00:13:45.680> back<00:13:45.839> in<00:13:46.079> here.<00:13:47.440> Instantly,<00:13:48.240> the 00:13:48.550 --> 00:13:48.560 align:start position:0% right back in here. Instantly, the 00:13:48.560 --> 00:13:50.629 align:start position:0% right back in here. Instantly, the previous<00:13:48.959> conversation<00:13:49.600> thread<00:13:50.079> beautifully 00:13:50.629 --> 00:13:50.639 align:start position:0% previous conversation thread beautifully 00:13:50.639 --> 00:13:53.590 align:start position:0% previous conversation thread beautifully continues<00:13:51.200> right<00:13:51.440> where<00:13:51.600> we<00:13:51.839> left<00:13:52.079> off. 00:13:53.590 --> 00:13:53.600 align:start position:0% continues right where we left off. 00:13:53.600 --> 00:13:55.590 align:start position:0% continues right where we left off. If<00:13:53.839> I<00:13:54.000> suddenly<00:13:54.480> decide<00:13:54.800> that<00:13:54.959> I<00:13:55.200> want<00:13:55.360> to 00:13:55.590 --> 00:13:55.600 align:start position:0% If I suddenly decide that I want to 00:13:55.600 --> 00:13:57.590 align:start position:0% If I suddenly decide that I want to completely<00:13:56.079> change<00:13:56.399> the<00:13:56.639> underlying<00:13:57.199> AI 00:13:57.590 --> 00:13:57.600 align:start position:0% completely change the underlying AI 00:13:57.600 --> 00:14:00.310 align:start position:0% completely change the underlying AI model,<00:13:58.480> we<00:13:58.720> currently<00:13:59.120> have<00:13:59.519> three<00:13:59.839> distinct 00:14:00.310 --> 00:14:00.320 align:start position:0% model, we currently have three distinct 00:14:00.320 --> 00:14:02.470 align:start position:0% model, we currently have three distinct options<00:14:00.639> available. 00:14:02.470 --> 00:14:02.480 align:start position:0% options available. 00:14:02.480 --> 00:14:06.310 align:start position:0% options available. First<00:14:02.880> is<00:14:03.199> GPT<00:14:04.079> 5.5,<00:14:05.440> which<00:14:05.760> is<00:14:06.000> essentially 00:14:06.310 --> 00:14:06.320 align:start position:0% First is GPT 5.5, which is essentially 00:14:06.320 --> 00:14:08.470 align:start position:0% First is GPT 5.5, which is essentially the<00:14:06.560> Frontier<00:14:07.120> model<00:14:07.519> specifically<00:14:08.160> built 00:14:08.470 --> 00:14:08.480 align:start position:0% the Frontier model specifically built 00:14:08.480 --> 00:14:11.350 align:start position:0% the Frontier model specifically built for<00:14:08.720> complex<00:14:09.199> coding<00:14:09.600> tasks. 00:14:11.350 --> 00:14:11.360 align:start position:0% for complex coding tasks. 00:14:11.360 --> 00:14:14.550 align:start position:0% for complex coding tasks. Next<00:14:11.839> is<00:14:12.160> GPT<00:14:12.959> 5.4, 00:14:14.550 --> 00:14:14.560 align:start position:0% Next is GPT 5.4, 00:14:14.560 --> 00:14:16.949 align:start position:0% Next is GPT 5.4, the<00:14:14.880> strongest<00:14:15.440> overall<00:14:16.000> model<00:14:16.480> strictly 00:14:16.949 --> 00:14:16.959 align:start position:0% the strongest overall model strictly 00:14:16.959 --> 00:14:20.230 align:start position:0% the strongest overall model strictly meant<00:14:17.199> for<00:14:17.440> everyday<00:14:18.000> standard<00:14:18.480> coding. 00:14:20.230 --> 00:14:20.240 align:start position:0% meant for everyday standard coding. 00:14:20.240 --> 00:14:22.310 align:start position:0% meant for everyday standard coding. Finally,<00:14:21.040> we<00:14:21.279> have<00:14:21.440> the<00:14:21.680> incredibly 00:14:22.310 --> 00:14:22.320 align:start position:0% Finally, we have the incredibly 00:14:22.320 --> 00:14:26.949 align:start position:0% Finally, we have the incredibly lightweight<00:14:23.040> GPT<00:14:23.920> 5.4<00:14:24.800> Mini.<00:14:26.160> We<00:14:26.399> also<00:14:26.720> have 00:14:26.949 --> 00:14:26.959 align:start position:0% lightweight GPT 5.4 Mini. We also have 00:14:26.959 --> 00:14:29.189 align:start position:0% lightweight GPT 5.4 Mini. We also have very<00:14:27.279> handy<00:14:27.680> slash<00:14:28.079> commands<00:14:28.720> completely 00:14:29.189 --> 00:14:29.199 align:start position:0% very handy slash commands completely 00:14:29.199 --> 00:14:31.910 align:start position:0% very handy slash commands completely ready<00:14:29.440> to<00:14:29.600> use.<00:14:30.720> we<00:14:30.959> will<00:14:31.199> clearly<00:14:31.519> show 00:14:31.910 --> 00:14:31.920 align:start position:0% ready to use. we will clearly show 00:14:31.920 --> 00:14:33.750 align:start position:0% ready to use. we will clearly show exactly<00:14:32.399> how<00:14:32.560> to<00:14:32.800> effectively<00:14:33.279> use<00:14:33.519> them 00:14:33.750 --> 00:14:33.760 align:start position:0% exactly how to effectively use them 00:14:33.760 --> 00:14:36.069 align:start position:0% exactly how to effectively use them moving<00:14:34.079> forward. 00:14:36.069 --> 00:14:36.079 align:start position:0% moving forward. 00:14:36.079 --> 00:14:38.629 align:start position:0% moving forward. Let's<00:14:36.399> use<00:14:36.639> slash<00:14:37.040> commands. 00:14:38.629 --> 00:14:38.639 align:start position:0% Let's use slash commands. 00:14:38.639 --> 00:14:40.790 align:start position:0% Let's use slash commands. When<00:14:38.880> I<00:14:39.120> proactively<00:14:39.760> type<00:14:40.079> out<00:14:40.240> a<00:14:40.480> forward 00:14:40.790 --> 00:14:40.800 align:start position:0% When I proactively type out a forward 00:14:40.800 --> 00:14:43.509 align:start position:0% When I proactively type out a forward slash,<00:14:41.760> codeex<00:14:42.399> immediately<00:14:42.880> shows<00:14:43.199> a 00:14:43.509 --> 00:14:43.519 align:start position:0% slash, codeex immediately shows a 00:14:43.519 --> 00:14:45.910 align:start position:0% slash, codeex immediately shows a complete,<00:14:44.240> highly<00:14:44.720> detailed<00:14:45.279> working<00:14:45.600> menu 00:14:45.910 --> 00:14:45.920 align:start position:0% complete, highly detailed working menu 00:14:45.920 --> 00:14:47.750 align:start position:0% complete, highly detailed working menu of<00:14:46.160> commands. 00:14:47.750 --> 00:14:47.760 align:start position:0% of commands. 00:14:47.760 --> 00:14:49.829 align:start position:0% of commands. First<00:14:48.079> and<00:14:48.320> foremost,<00:14:49.120> we<00:14:49.360> can<00:14:49.519> fully 00:14:49.829 --> 00:14:49.839 align:start position:0% First and foremost, we can fully 00:14:49.839 --> 00:14:53.269 align:start position:0% First and foremost, we can fully configure<00:14:50.240> how<00:14:50.480> codeex<00:14:51.040> strictly<00:14:51.519> operates. 00:14:53.269 --> 00:14:53.279 align:start position:0% configure how codeex strictly operates. 00:14:53.279 --> 00:14:55.110 align:start position:0% configure how codeex strictly operates. We<00:14:53.519> have<00:14:53.680> the<00:14:53.920> primary<00:14:54.320> model<00:14:54.639> selection 00:14:55.110 --> 00:14:55.120 align:start position:0% We have the primary model selection 00:14:55.120 --> 00:14:57.910 align:start position:0% We have the primary model selection option<00:14:55.440> available.<00:14:56.880> We<00:14:57.199> also<00:14:57.519> have<00:14:57.680> the 00:14:57.910 --> 00:14:57.920 align:start position:0% option available. We also have the 00:14:57.920 --> 00:15:01.509 align:start position:0% option available. We also have the specific<00:14:58.560> fast<00:14:58.959> option<00:14:59.440> explicitly<00:15:00.000> listed. 00:15:01.509 --> 00:15:01.519 align:start position:0% specific fast option explicitly listed. 00:15:01.519 --> 00:15:04.710 align:start position:0% specific fast option explicitly listed. We<00:15:01.760> have<00:15:01.920> the<00:15:02.320> IDE<00:15:02.959> integration<00:15:04.000> to<00:15:04.320> easily 00:15:04.710 --> 00:15:04.720 align:start position:0% We have the IDE integration to easily 00:15:04.720 --> 00:15:07.110 align:start position:0% We have the IDE integration to easily include<00:15:05.279> currently<00:15:05.760> open<00:15:06.079> files<00:15:06.480> and<00:15:06.720> broader 00:15:07.110 --> 00:15:07.120 align:start position:0% include currently open files and broader 00:15:07.120 --> 00:15:08.870 align:start position:0% include currently open files and broader context. 00:15:08.870 --> 00:15:08.880 align:start position:0% context. 00:15:08.880 --> 00:15:11.269 align:start position:0% context. We<00:15:09.199> actively<00:15:09.680> have<00:15:09.920> detailed<00:15:10.480> permissions<00:15:11.040> to 00:15:11.269 --> 00:15:11.279 align:start position:0% We actively have detailed permissions to 00:15:11.279 --> 00:15:13.990 align:start position:0% We actively have detailed permissions to precisely<00:15:11.920> choose<00:15:12.320> exactly<00:15:12.800> what<00:15:13.120> codecs<00:15:13.680> can 00:15:13.990 --> 00:15:14.000 align:start position:0% precisely choose exactly what codecs can 00:15:14.000 --> 00:15:16.710 align:start position:0% precisely choose exactly what codecs can or<00:15:14.320> cannot<00:15:14.720> do<00:15:14.959> safely. 00:15:16.710 --> 00:15:16.720 align:start position:0% or cannot do safely. 00:15:16.720 --> 00:15:19.189 align:start position:0% or cannot do safely. We<00:15:16.959> have<00:15:17.120> dedicated<00:15:17.760> key<00:15:18.079> maps<00:15:18.480> specifically 00:15:19.189 --> 00:15:19.199 align:start position:0% We have dedicated key maps specifically 00:15:19.199 --> 00:15:21.110 align:start position:0% We have dedicated key maps specifically designed<00:15:19.600> for<00:15:19.839> setting<00:15:20.240> custom<00:15:20.639> keyboard 00:15:21.110 --> 00:15:21.120 align:start position:0% designed for setting custom keyboard 00:15:21.120 --> 00:15:23.030 align:start position:0% designed for setting custom keyboard shortcuts. 00:15:23.030 --> 00:15:23.040 align:start position:0% shortcuts. 00:15:23.040 --> 00:15:25.430 align:start position:0% shortcuts. We<00:15:23.279> have<00:15:23.519> Vim<00:15:23.839> mode<00:15:24.320> strictly<00:15:24.800> intended<00:15:25.199> for 00:15:25.430 --> 00:15:25.440 align:start position:0% We have Vim mode strictly intended for 00:15:25.440 --> 00:15:28.069 align:start position:0% We have Vim mode strictly intended for our<00:15:25.600> main<00:15:25.839> code<00:15:26.240> composer. 00:15:28.069 --> 00:15:28.079 align:start position:0% our main code composer. 00:15:28.079 --> 00:15:30.389 align:start position:0% our main code composer. We<00:15:28.320> logically<00:15:28.880> have<00:15:29.040> the<00:15:29.360> sandbox<00:15:29.920> add<00:15:30.160> to 00:15:30.389 --> 00:15:30.399 align:start position:0% We logically have the sandbox add to 00:15:30.399 --> 00:15:33.030 align:start position:0% We logically have the sandbox add to directory<00:15:30.880> feature<00:15:31.360> ready. 00:15:33.030 --> 00:15:33.040 align:start position:0% directory feature ready. 00:15:33.040 --> 00:15:35.189 align:start position:0% directory feature ready. Finally,<00:15:33.839> we<00:15:34.079> have<00:15:34.160> the<00:15:34.399> experimental 00:15:35.189 --> 00:15:35.199 align:start position:0% Finally, we have the experimental 00:15:35.199 --> 00:15:37.110 align:start position:0% Finally, we have the experimental feature<00:15:35.519> section. 00:15:37.110 --> 00:15:37.120 align:start position:0% feature section. 00:15:37.120 --> 00:15:39.430 align:start position:0% feature section. I<00:15:37.440> intentionally<00:15:38.160> select<00:15:38.560> the<00:15:38.800> very<00:15:39.120> first 00:15:39.430 --> 00:15:39.440 align:start position:0% I intentionally select the very first 00:15:39.440 --> 00:15:41.590 align:start position:0% I intentionally select the very first configuration<00:15:40.079> option<00:15:40.800> to<00:15:41.040> explore<00:15:41.360> the 00:15:41.590 --> 00:15:41.600 align:start position:0% configuration option to explore the 00:15:41.600 --> 00:15:43.750 align:start position:0% configuration option to explore the available<00:15:42.079> models. 00:15:43.750 --> 00:15:43.760 align:start position:0% available models. 00:15:43.760 --> 00:15:47.350 align:start position:0% available models. I<00:15:44.160> ultimately<00:15:44.560> choose<00:15:44.880> the<00:15:45.199> GPT<00:15:46.079> 5.4<00:15:46.959> mini 00:15:47.350 --> 00:15:47.360 align:start position:0% I ultimately choose the GPT 5.4 mini 00:15:47.360 --> 00:15:49.269 align:start position:0% I ultimately choose the GPT 5.4 mini variant. 00:15:49.269 --> 00:15:49.279 align:start position:0% variant. 00:15:49.279 --> 00:15:51.590 align:start position:0% variant. Now<00:15:49.839> we<00:15:50.079> selectively<00:15:50.720> choose<00:15:50.959> the<00:15:51.199> preferred 00:15:51.590 --> 00:15:51.600 align:start position:0% Now we selectively choose the preferred 00:15:51.600 --> 00:15:54.870 align:start position:0% Now we selectively choose the preferred reasoning<00:15:52.079> level.<00:15:53.440> We<00:15:53.759> specifically<00:15:54.399> select 00:15:54.870 --> 00:15:54.880 align:start position:0% reasoning level. We specifically select 00:15:54.880 --> 00:15:57.030 align:start position:0% reasoning level. We specifically select low<00:15:55.199> reasoning<00:15:55.839> instead<00:15:56.160> of<00:15:56.320> the<00:15:56.560> standard 00:15:57.030 --> 00:15:57.040 align:start position:0% low reasoning instead of the standard 00:15:57.040 --> 00:15:58.629 align:start position:0% low reasoning instead of the standard medium. 00:15:58.629 --> 00:15:58.639 align:start position:0% medium. 00:15:58.639 --> 00:16:00.949 align:start position:0% medium. We<00:15:58.880> can<00:15:59.040> carefully<00:15:59.519> view<00:15:59.920> current<00:16:00.320> IDE 00:16:00.949 --> 00:16:00.959 align:start position:0% We can carefully view current IDE 00:16:00.959 --> 00:16:03.590 align:start position:0% We can carefully view current IDE sessions<00:16:01.360> and<00:16:01.680> files. 00:16:03.590 --> 00:16:03.600 align:start position:0% sessions and files. 00:16:03.600 --> 00:16:06.310 align:start position:0% sessions and files. Next,<00:16:04.000> we<00:16:04.240> review<00:16:04.560> permissions. 00:16:06.310 --> 00:16:06.320 align:start position:0% Next, we review permissions. 00:16:06.320 --> 00:16:08.389 align:start position:0% Next, we review permissions. There<00:16:06.560> are<00:16:06.720> several<00:16:07.120> highly<00:16:07.600> specific<00:16:08.079> model 00:16:08.389 --> 00:16:08.399 align:start position:0% There are several highly specific model 00:16:08.399 --> 00:16:11.269 align:start position:0% There are several highly specific model permissions<00:16:08.959> carefully<00:16:09.440> listed<00:16:09.839> here.<00:16:11.040> The 00:16:11.269 --> 00:16:11.279 align:start position:0% permissions carefully listed here. The 00:16:11.279 --> 00:16:13.350 align:start position:0% permissions carefully listed here. The readonly<00:16:12.000> setting<00:16:12.480> strictly<00:16:12.959> means<00:16:13.199> that 00:16:13.350 --> 00:16:13.360 align:start position:0% readonly setting strictly means that 00:16:13.360 --> 00:16:16.629 align:start position:0% readonly setting strictly means that Codeex<00:16:13.920> can<00:16:14.160> only<00:16:14.480> safely<00:16:14.959> read<00:16:15.360> active<00:16:15.839> files 00:16:16.629 --> 00:16:16.639 align:start position:0% Codeex can only safely read active files 00:16:16.639 --> 00:16:18.470 align:start position:0% Codeex can only safely read active files located<00:16:17.120> within<00:16:17.440> the<00:16:17.600> current<00:16:17.920> workspace 00:16:18.470 --> 00:16:18.480 align:start position:0% located within the current workspace 00:16:18.480 --> 00:16:21.829 align:start position:0% located within the current workspace environment.<00:16:19.920> It<00:16:20.240> absolutely<00:16:20.959> requires<00:16:21.519> your 00:16:21.829 --> 00:16:21.839 align:start position:0% environment. It absolutely requires your 00:16:21.839 --> 00:16:24.470 align:start position:0% environment. It absolutely requires your direct<00:16:22.480> manual<00:16:22.959> approval<00:16:23.759> before<00:16:24.079> it<00:16:24.320> can 00:16:24.470 --> 00:16:24.480 align:start position:0% direct manual approval before it can 00:16:24.480 --> 00:16:26.949 align:start position:0% direct manual approval before it can ever<00:16:24.720> attempt<00:16:25.040> to<00:16:25.199> edit<00:16:25.519> files<00:16:26.079> or<00:16:26.399> directly 00:16:26.949 --> 00:16:26.959 align:start position:0% ever attempt to edit files or directly 00:16:26.959 --> 00:16:29.670 align:start position:0% ever attempt to edit files or directly access<00:16:27.360> the<00:16:27.600> live<00:16:27.920> internet. 00:16:29.670 --> 00:16:29.680 align:start position:0% access the live internet. 00:16:29.680 --> 00:16:32.310 align:start position:0% access the live internet. The<00:16:29.920> ask<00:16:30.240> for<00:16:30.480> approval<00:16:31.040> setting<00:16:31.920> actually 00:16:32.310 --> 00:16:32.320 align:start position:0% The ask for approval setting actually 00:16:32.320 --> 00:16:34.629 align:start position:0% The ask for approval setting actually serves<00:16:32.639> as<00:16:32.800> the<00:16:33.040> standard<00:16:33.440> default<00:16:33.920> mode 00:16:34.629 --> 00:16:34.639 align:start position:0% serves as the standard default mode 00:16:34.639 --> 00:16:37.509 align:start position:0% serves as the standard default mode where<00:16:34.880> Codeex<00:16:35.440> can<00:16:35.600> seamlessly<00:16:36.240> run,<00:16:36.959> read, 00:16:37.509 --> 00:16:37.519 align:start position:0% where Codeex can seamlessly run, read, 00:16:37.519 --> 00:16:39.829 align:start position:0% where Codeex can seamlessly run, read, or<00:16:37.839> even<00:16:38.079> edit<00:16:38.480> files<00:16:38.959> inside<00:16:39.279> the<00:16:39.519> current 00:16:39.829 --> 00:16:39.839 align:start position:0% or even edit files inside the current 00:16:39.839 --> 00:16:42.150 align:start position:0% or even edit files inside the current workspace<00:16:40.720> and<00:16:40.959> fully<00:16:41.279> read<00:16:41.600> the<00:16:41.759> active 00:16:42.150 --> 00:16:42.160 align:start position:0% workspace and fully read the active 00:16:42.160 --> 00:16:44.310 align:start position:0% workspace and fully read the active command<00:16:42.480> prompt. 00:16:44.310 --> 00:16:44.320 align:start position:0% command prompt. 00:16:44.320 --> 00:16:47.189 align:start position:0% command prompt. Still,<00:16:45.440> explicit<00:16:46.000> manual<00:16:46.399> approval<00:16:46.959> is 00:16:47.189 --> 00:16:47.199 align:start position:0% Still, explicit manual approval is 00:16:47.199 --> 00:16:49.590 align:start position:0% Still, explicit manual approval is completely<00:16:47.759> required<00:16:48.399> to<00:16:48.720> permanently<00:16:49.199> edit 00:16:49.590 --> 00:16:49.600 align:start position:0% completely required to permanently edit 00:16:49.600 --> 00:16:52.710 align:start position:0% completely required to permanently edit files<00:16:50.000> or<00:16:50.320> access<00:16:50.720> the<00:16:50.959> internet. 00:16:52.710 --> 00:16:52.720 align:start position:0% files or access the internet. 00:16:52.720 --> 00:16:55.590 align:start position:0% files or access the internet. Approve<00:16:53.120> for<00:16:53.360> me<00:16:54.000> intelligently<00:16:54.880> only<00:16:55.199> asks 00:16:55.590 --> 00:16:55.600 align:start position:0% Approve for me intelligently only asks 00:16:55.600 --> 00:16:57.430 align:start position:0% Approve for me intelligently only asks for<00:16:55.759> explicit<00:16:56.320> permission<00:16:56.959> when<00:16:57.279> it 00:16:57.430 --> 00:16:57.440 align:start position:0% for explicit permission when it 00:16:57.440 --> 00:16:59.509 align:start position:0% for explicit permission when it encounters<00:16:58.000> potentially<00:16:58.560> unsafe<00:16:59.199> system 00:16:59.509 --> 00:16:59.519 align:start position:0% encounters potentially unsafe system 00:16:59.519 --> 00:17:01.110 align:start position:0% encounters potentially unsafe system actions. 00:17:01.110 --> 00:17:01.120 align:start position:0% actions. 00:17:01.120 --> 00:17:03.990 align:start position:0% actions. Full<00:17:01.519> access<00:17:02.480> simply<00:17:02.880> means<00:17:03.279> Codeex<00:17:03.839> can 00:17:03.990 --> 00:17:04.000 align:start position:0% Full access simply means Codeex can 00:17:04.000 --> 00:17:06.309 align:start position:0% Full access simply means Codeex can freely<00:17:04.400> edit<00:17:04.720> files<00:17:05.360> far<00:17:05.679> outside<00:17:06.079> the 00:17:06.309 --> 00:17:06.319 align:start position:0% freely edit files far outside the 00:17:06.319 --> 00:17:08.949 align:start position:0% freely edit files far outside the designated<00:17:06.880> workspace<00:17:07.839> and<00:17:08.160> easily<00:17:08.559> access 00:17:08.949 --> 00:17:08.959 align:start position:0% designated workspace and easily access 00:17:08.959 --> 00:17:11.029 align:start position:0% designated workspace and easily access the<00:17:09.199> internet<00:17:09.760> without<00:17:10.160> ever<00:17:10.480> asking<00:17:10.799> for 00:17:11.029 --> 00:17:11.039 align:start position:0% the internet without ever asking for 00:17:11.039 --> 00:17:13.350 align:start position:0% the internet without ever asking for prior<00:17:11.360> approval. 00:17:13.350 --> 00:17:13.360 align:start position:0% prior approval. 00:17:13.360 --> 00:17:16.549 align:start position:0% prior approval. Exercise<00:17:14.000> extreme<00:17:14.640> caution<00:17:15.439> and<00:17:15.760> ask<00:17:16.079> vital 00:17:16.549 --> 00:17:16.559 align:start position:0% Exercise extreme caution and ask vital 00:17:16.559 --> 00:17:19.270 align:start position:0% Exercise extreme caution and ask vital questions<00:17:16.959> when<00:17:17.280> using<00:17:17.520> this. 00:17:19.270 --> 00:17:19.280 align:start position:0% questions when using this. 00:17:19.280 --> 00:17:21.909 align:start position:0% questions when using this. I<00:17:19.600> explicitly<00:17:20.240> choose<00:17:20.640> the<00:17:20.880> approve<00:17:21.360> for<00:17:21.600> me 00:17:21.909 --> 00:17:21.919 align:start position:0% I explicitly choose the approve for me 00:17:21.919 --> 00:17:23.590 align:start position:0% I explicitly choose the approve for me setting. 00:17:23.590 --> 00:17:23.600 align:start position:0% setting. 00:17:23.600 --> 00:17:25.510 align:start position:0% setting. Our<00:17:23.839> updated<00:17:24.400> permissions<00:17:24.880> are<00:17:25.120> cleanly 00:17:25.510 --> 00:17:25.520 align:start position:0% Our updated permissions are cleanly 00:17:25.520 --> 00:17:28.630 align:start position:0% Our updated permissions are cleanly applied.<00:17:26.720> I<00:17:27.039> press<00:17:27.280> enter<00:17:27.760> and<00:17:28.079> transition<00:17:28.480> to 00:17:28.630 --> 00:17:28.640 align:start position:0% applied. I press enter and transition to 00:17:28.640 --> 00:17:31.190 align:start position:0% applied. I press enter and transition to the<00:17:28.720> key<00:17:29.039> map<00:17:29.280> configuration. 00:17:31.190 --> 00:17:31.200 align:start position:0% the key map configuration. 00:17:31.200 --> 00:17:33.830 align:start position:0% the key map configuration. In<00:17:31.520> keymap,<00:17:32.240> we<00:17:32.480> have<00:17:32.559> our<00:17:32.799> transcript, 00:17:33.830 --> 00:17:33.840 align:start position:0% In keymap, we have our transcript, 00:17:33.840 --> 00:17:36.390 align:start position:0% In keymap, we have our transcript, external<00:17:34.400> editor,<00:17:35.200> clear<00:17:35.520> terminal,<00:17:36.160> and 00:17:36.390 --> 00:17:36.400 align:start position:0% external editor, clear terminal, and 00:17:36.400 --> 00:17:38.230 align:start position:0% external editor, clear terminal, and more<00:17:36.640> options. 00:17:38.230 --> 00:17:38.240 align:start position:0% more options. 00:17:38.240 --> 00:17:40.390 align:start position:0% more options. We<00:17:38.559> practically<00:17:39.120> have<00:17:39.360> multiple<00:17:39.919> distinct 00:17:40.390 --> 00:17:40.400 align:start position:0% We practically have multiple distinct 00:17:40.400 --> 00:17:42.390 align:start position:0% We practically have multiple distinct configuration<00:17:41.039> options<00:17:41.520> readily<00:17:41.919> available 00:17:42.390 --> 00:17:42.400 align:start position:0% configuration options readily available 00:17:42.400 --> 00:17:45.110 align:start position:0% configuration options readily available right<00:17:42.720> here<00:17:43.600> alongside<00:17:44.240> some<00:17:44.480> incredibly 00:17:45.110 --> 00:17:45.120 align:start position:0% right here alongside some incredibly 00:17:45.120 --> 00:17:48.390 align:start position:0% right here alongside some incredibly useful<00:17:45.600> direct<00:17:46.000> operational<00:17:46.640> options. 00:17:48.390 --> 00:17:48.400 align:start position:0% useful direct operational options. 00:17:48.400 --> 00:17:50.789 align:start position:0% useful direct operational options. What<00:17:48.640> we<00:17:48.880> can<00:17:49.039> actually<00:17:49.440> do<00:17:49.679> here<00:17:50.000> is<00:17:50.480> utilize 00:17:50.789 --> 00:17:50.799 align:start position:0% What we can actually do here is utilize 00:17:50.799 --> 00:17:53.190 align:start position:0% What we can actually do here is utilize the<00:17:51.039> basic<00:17:51.520> left<00:17:51.760> and<00:17:52.000> right<00:17:52.400> keyboard<00:17:52.880> arrow 00:17:53.190 --> 00:17:53.200 align:start position:0% the basic left and right keyboard arrow 00:17:53.200 --> 00:17:55.590 align:start position:0% the basic left and right keyboard arrow keys<00:17:53.840> to<00:17:54.160> smoothly<00:17:54.640> navigate<00:17:55.039> and<00:17:55.280> group 00:17:55.590 --> 00:17:55.600 align:start position:0% keys to smoothly navigate and group 00:17:55.600 --> 00:17:58.870 align:start position:0% keys to smoothly navigate and group items.<00:17:57.039> We<00:17:57.280> firmly<00:17:57.760> use<00:17:58.000> the<00:17:58.160> enter<00:17:58.480> key 00:17:58.870 --> 00:17:58.880 align:start position:0% items. We firmly use the enter key 00:17:58.880 --> 00:18:01.190 align:start position:0% items. We firmly use the enter key whenever<00:17:59.280> we<00:17:59.440> strictly<00:17:59.919> need<00:18:00.160> to<00:18:00.400> modify<00:18:00.880> or 00:18:01.190 --> 00:18:01.200 align:start position:0% whenever we strictly need to modify or 00:18:01.200 --> 00:18:03.990 align:start position:0% whenever we strictly need to modify or edit<00:18:01.600> an<00:18:01.840> existing<00:18:02.240> shortcut. 00:18:03.990 --> 00:18:04.000 align:start position:0% edit an existing shortcut. 00:18:04.000 --> 00:18:06.710 align:start position:0% edit an existing shortcut. We<00:18:04.320> smartly<00:18:04.880> use<00:18:05.120> the<00:18:05.360> star<00:18:05.679> symbol<00:18:06.320> strictly 00:18:06.710 --> 00:18:06.720 align:start position:0% We smartly use the star symbol strictly 00:18:06.720 --> 00:18:08.710 align:start position:0% We smartly use the star symbol strictly for<00:18:07.039> creating<00:18:07.600> completely<00:18:08.240> custom 00:18:08.710 --> 00:18:08.720 align:start position:0% for creating completely custom 00:18:08.720 --> 00:18:11.750 align:start position:0% for creating completely custom shortcuts,<00:18:10.160> the<00:18:10.400> dash<00:18:10.720> symbol<00:18:11.200> to<00:18:11.440> quickly 00:18:11.750 --> 00:18:11.760 align:start position:0% shortcuts, the dash symbol to quickly 00:18:11.760 --> 00:18:14.950 align:start position:0% shortcuts, the dash symbol to quickly unbind<00:18:12.320> an<00:18:12.480> active<00:18:12.880> key,<00:18:13.840> and<00:18:14.000> the<00:18:14.160> escape<00:18:14.559> key 00:18:14.950 --> 00:18:14.960 align:start position:0% unbind an active key, and the escape key 00:18:14.960 --> 00:18:18.310 align:start position:0% unbind an active key, and the escape key to<00:18:15.200> easily<00:18:15.679> close<00:18:15.919> out<00:18:16.160> the<00:18:16.320> menu<00:18:16.640> entirely. 00:18:18.310 --> 00:18:18.320 align:start position:0% to easily close out the menu entirely. 00:18:18.320 --> 00:18:20.549 align:start position:0% to easily close out the menu entirely. I<00:18:18.640> simply<00:18:18.960> press<00:18:19.200> escape<00:18:19.679> right<00:18:19.919> now<00:18:20.320> to 00:18:20.549 --> 00:18:20.559 align:start position:0% I simply press escape right now to 00:18:20.559 --> 00:18:23.990 align:start position:0% I simply press escape right now to smoothly<00:18:21.120> go<00:18:21.280> back<00:18:21.440> to<00:18:21.600> the<00:18:21.840> previous<00:18:22.160> screen. 00:18:23.990 --> 00:18:24.000 align:start position:0% smoothly go back to the previous screen. 00:18:24.000 --> 00:18:26.070 align:start position:0% smoothly go back to the previous screen. Right<00:18:24.240> after<00:18:24.640> successfully<00:18:25.280> configuring<00:18:25.760> our 00:18:26.070 --> 00:18:26.080 align:start position:0% Right after successfully configuring our 00:18:26.080 --> 00:18:28.390 align:start position:0% Right after successfully configuring our system<00:18:26.400> permissions,<00:18:27.440> we<00:18:27.679> logically<00:18:28.240> have 00:18:28.390 --> 00:18:28.400 align:start position:0% system permissions, we logically have 00:18:28.400 --> 00:18:32.150 align:start position:0% system permissions, we logically have our<00:18:28.640> custom<00:18:29.039> key<00:18:29.280> maps<00:18:29.600> fully<00:18:30.000> sorted<00:18:30.400> out. 00:18:32.150 --> 00:18:32.160 align:start position:0% our custom key maps fully sorted out. 00:18:32.160 --> 00:18:34.710 align:start position:0% our custom key maps fully sorted out. Next<00:18:32.400> up,<00:18:32.960> we<00:18:33.200> carefully<00:18:33.679> review<00:18:34.080> our<00:18:34.320> active 00:18:34.710 --> 00:18:34.720 align:start position:0% Next up, we carefully review our active 00:18:34.720 --> 00:18:36.870 align:start position:0% Next up, we carefully review our active system<00:18:35.120> approvals. 00:18:36.870 --> 00:18:36.880 align:start position:0% system approvals. 00:18:36.880 --> 00:18:39.430 align:start position:0% system approvals. You<00:18:37.120> can<00:18:37.280> transparently<00:18:38.000> see<00:18:38.400> absolutely<00:18:39.120> all 00:18:39.430 --> 00:18:39.440 align:start position:0% You can transparently see absolutely all 00:18:39.440 --> 00:18:41.590 align:start position:0% You can transparently see absolutely all the<00:18:39.679> recent<00:18:40.000> system<00:18:40.400> changes<00:18:40.880> we<00:18:41.120> manually 00:18:41.590 --> 00:18:41.600 align:start position:0% the recent system changes we manually 00:18:41.600 --> 00:18:43.750 align:start position:0% the recent system changes we manually made<00:18:41.919> right<00:18:42.240> here. 00:18:43.750 --> 00:18:43.760 align:start position:0% made right here. 00:18:43.760 --> 00:18:46.390 align:start position:0% made right here. We<00:18:44.080> actually<00:18:44.480> changed<00:18:44.799> our<00:18:45.120> primary<00:18:45.600> AI<00:18:46.000> model 00:18:46.390 --> 00:18:46.400 align:start position:0% We actually changed our primary AI model 00:18:46.400 --> 00:18:48.310 align:start position:0% We actually changed our primary AI model twice<00:18:46.799> today. 00:18:48.310 --> 00:18:48.320 align:start position:0% twice today. 00:18:48.320 --> 00:18:50.950 align:start position:0% twice today. We<00:18:48.559> closely<00:18:49.039> reviewed<00:18:49.520> the<00:18:49.760> IDE<00:18:50.480> context 00:18:50.950 --> 00:18:50.960 align:start position:0% We closely reviewed the IDE context 00:18:50.960 --> 00:18:52.470 align:start position:0% We closely reviewed the IDE context settings. 00:18:52.470 --> 00:18:52.480 align:start position:0% settings. 00:18:52.480 --> 00:18:54.470 align:start position:0% settings. We<00:18:52.720> officially<00:18:53.280> updated<00:18:53.760> our<00:18:54.000> security 00:18:54.470 --> 00:18:54.480 align:start position:0% We officially updated our security 00:18:54.480 --> 00:18:58.789 align:start position:0% We officially updated our security permissions<00:18:55.039> to<00:18:55.760> approve<00:18:56.320> for<00:18:56.559> me.<00:18:58.000> Finally, 00:18:58.789 --> 00:18:58.799 align:start position:0% permissions to approve for me. Finally, 00:18:58.799 --> 00:19:01.830 align:start position:0% permissions to approve for me. Finally, I<00:18:59.039> press<00:18:59.360> Ctrl<00:18:59.840> C.<00:19:00.480> Executing<00:19:01.039> that<00:19:01.360> specific 00:19:01.830 --> 00:19:01.840 align:start position:0% I press Ctrl C. Executing that specific 00:19:01.840 --> 00:19:04.070 align:start position:0% I press Ctrl C. Executing that specific command<00:19:02.320> officially<00:19:02.880> closes<00:19:03.280> out<00:19:03.440> the<00:19:03.679> active 00:19:04.070 --> 00:19:04.080 align:start position:0% command officially closes out the active 00:19:04.080 --> 00:19:07.190 align:start position:0% command officially closes out the active chat<00:19:04.400> session<00:19:04.799> entirely.<00:19:06.240> It<00:19:06.480> is<00:19:06.640> crucial<00:19:07.039> to 00:19:07.190 --> 00:19:07.200 align:start position:0% chat session entirely. It is crucial to 00:19:07.200 --> 00:19:09.029 align:start position:0% chat session entirely. It is crucial to note<00:19:07.440> that<00:19:07.600> this<00:19:07.840> specific<00:19:08.400> underlying 00:19:09.029 --> 00:19:09.039 align:start position:0% note that this specific underlying 00:19:09.039 --> 00:19:11.750 align:start position:0% note that this specific underlying configuration<00:19:10.400> genuinely<00:19:11.039> remains<00:19:11.520> the 00:19:11.750 --> 00:19:11.760 align:start position:0% configuration genuinely remains the 00:19:11.760 --> 00:19:14.470 align:start position:0% configuration genuinely remains the exact<00:19:12.240> same<00:19:12.720> across<00:19:13.280> every<00:19:13.600> single<00:19:14.000> linked 00:19:14.470 --> 00:19:14.480 align:start position:0% exact same across every single linked 00:19:14.480 --> 00:19:16.950 align:start position:0% exact same across every single linked application<00:19:15.039> environment. 00:19:16.950 --> 00:19:16.960 align:start position:0% application environment. 00:19:16.960 --> 00:19:19.510 align:start position:0% application environment. Thankfully,<00:19:17.840> the<00:19:18.160> powerful<00:19:18.640> codeex<00:19:19.120> tool<00:19:19.360> is 00:19:19.510 --> 00:19:19.520 align:start position:0% Thankfully, the powerful codeex tool is 00:19:19.520 --> 00:19:22.390 align:start position:0% Thankfully, the powerful codeex tool is readily<00:19:19.919> available<00:19:20.480> right<00:19:20.720> here,<00:19:21.120> too.<00:19:22.160> We 00:19:22.390 --> 00:19:22.400 align:start position:0% readily available right here, too. We 00:19:22.400 --> 00:19:24.390 align:start position:0% readily available right here, too. We can<00:19:22.559> practically<00:19:23.120> do<00:19:23.440> so<00:19:23.760> many<00:19:24.000> different 00:19:24.390 --> 00:19:24.400 align:start position:0% can practically do so many different 00:19:24.400 --> 00:19:27.270 align:start position:0% can practically do so many different amazing<00:19:24.880> things<00:19:25.120> with<00:19:25.360> it.<00:19:26.320> If<00:19:26.559> we<00:19:26.799> smartly 00:19:27.270 --> 00:19:27.280 align:start position:0% amazing things with it. If we smartly 00:19:27.280 --> 00:19:29.350 align:start position:0% amazing things with it. If we smartly decide<00:19:27.520> to<00:19:27.840> switch<00:19:28.080> over<00:19:28.320> to<00:19:28.559> the<00:19:28.720> exclusive 00:19:29.350 --> 00:19:29.360 align:start position:0% decide to switch over to the exclusive 00:19:29.360 --> 00:19:32.230 align:start position:0% decide to switch over to the exclusive pre-release<00:19:30.000> software<00:19:30.480> version,<00:19:31.440> absolutely 00:19:32.230 --> 00:19:32.240 align:start position:0% pre-release software version, absolutely 00:19:32.240 --> 00:19:34.470 align:start position:0% pre-release software version, absolutely all<00:19:32.480> the<00:19:32.720> newest<00:19:33.200> experimental<00:19:34.000> features 00:19:34.470 --> 00:19:34.480 align:start position:0% all the newest experimental features 00:19:34.480 --> 00:19:37.110 align:start position:0% all the newest experimental features become<00:19:34.960> instantly<00:19:35.520> available. 00:19:37.110 --> 00:19:37.120 align:start position:0% become instantly available. 00:19:37.120 --> 00:19:39.750 align:start position:0% become instantly available. I<00:19:37.360> am<00:19:37.520> going<00:19:37.679> to<00:19:37.919> intentionally<00:19:38.640> open<00:19:38.960> up<00:19:39.440> a 00:19:39.750 --> 00:19:39.760 align:start position:0% I am going to intentionally open up a 00:19:39.760 --> 00:19:42.390 align:start position:0% I am going to intentionally open up a brand<00:19:40.160> new<00:19:40.559> dedicated<00:19:41.200> project<00:19:41.600> folder 00:19:42.390 --> 00:19:42.400 align:start position:0% brand new dedicated project folder 00:19:42.400 --> 00:19:44.870 align:start position:0% brand new dedicated project folder officially<00:19:42.880> named<00:19:43.440> Metabrains<00:19:44.480> for<00:19:44.640> our 00:19:44.870 --> 00:19:44.880 align:start position:0% officially named Metabrains for our 00:19:44.880 --> 00:19:46.230 align:start position:0% officially named Metabrains for our work. 00:19:46.230 --> 00:19:46.240 align:start position:0% work. 00:19:46.240 --> 00:19:48.470 align:start position:0% work. We<00:19:46.559> carefully<00:19:47.039> select<00:19:47.360> this<00:19:47.679> exact<00:19:48.000> folder 00:19:48.470 --> 00:19:48.480 align:start position:0% We carefully select this exact folder 00:19:48.480 --> 00:19:51.190 align:start position:0% We carefully select this exact folder directory<00:19:49.200> and<00:19:49.520> smoothly<00:19:50.080> open<00:19:50.400> up<00:19:50.559> our<00:19:50.880> fresh 00:19:51.190 --> 00:19:51.200 align:start position:0% directory and smoothly open up our fresh 00:19:51.200 --> 00:19:53.270 align:start position:0% directory and smoothly open up our fresh chat<00:19:51.600> interface. 00:19:53.270 --> 00:19:53.280 align:start position:0% chat interface. 00:19:53.280 --> 00:19:55.669 align:start position:0% chat interface. I<00:19:53.600> explicitly<00:19:54.160> confirm<00:19:54.559> that<00:19:54.799> I<00:19:55.039> fully<00:19:55.360> trust 00:19:55.669 --> 00:19:55.679 align:start position:0% I explicitly confirm that I fully trust 00:19:55.679 --> 00:19:57.830 align:start position:0% I explicitly confirm that I fully trust the<00:19:55.919> verified<00:19:56.480> authors<00:19:56.960> operating<00:19:57.360> in<00:19:57.600> this 00:19:57.830 --> 00:19:57.840 align:start position:0% the verified authors operating in this 00:19:57.840 --> 00:20:00.150 align:start position:0% the verified authors operating in this specific<00:19:58.320> environment. 00:20:00.150 --> 00:20:00.160 align:start position:0% specific environment. 00:20:00.160 --> 00:20:02.470 align:start position:0% specific environment. I<00:20:00.480> smoothly<00:20:01.039> close<00:20:01.360> this<00:20:01.520> secondary<00:20:02.000> pop-up 00:20:02.470 --> 00:20:02.480 align:start position:0% I smoothly close this secondary pop-up 00:20:02.480 --> 00:20:05.909 align:start position:0% I smoothly close this secondary pop-up window.<00:20:03.919> I<00:20:04.160> promptly<00:20:04.640> open<00:20:04.880> up<00:20:05.120> a<00:20:05.360> brand<00:20:05.600> new 00:20:05.909 --> 00:20:05.919 align:start position:0% window. I promptly open up a brand new 00:20:05.919 --> 00:20:07.990 align:start position:0% window. I promptly open up a brand new code<00:20:06.160> file<00:20:06.720> appropriately<00:20:07.360> named 00:20:07.990 --> 00:20:08.000 align:start position:0% code file appropriately named 00:20:08.000 --> 00:20:10.710 align:start position:0% code file appropriately named index.html. 00:20:10.710 --> 00:20:10.720 align:start position:0% index.html. 00:20:10.720 --> 00:20:12.630 align:start position:0% index.html. You<00:20:10.960> can<00:20:11.039> distinctly<00:20:11.679> see<00:20:11.840> the<00:20:12.080> familiar 00:20:12.630 --> 00:20:12.640 align:start position:0% You can distinctly see the familiar 00:20:12.640 --> 00:20:15.990 align:start position:0% You can distinctly see the familiar codeex<00:20:13.120> logo<00:20:13.600> right<00:20:13.919> inside<00:20:14.240> this<00:20:14.480> document. 00:20:15.990 --> 00:20:16.000 align:start position:0% codeex logo right inside this document. 00:20:16.000 --> 00:20:18.390 align:start position:0% codeex logo right inside this document. We<00:20:16.320> can<00:20:16.480> now<00:20:16.799> finally<00:20:17.360> start<00:20:17.600> to<00:20:17.840> actively 00:20:18.390 --> 00:20:18.400 align:start position:0% We can now finally start to actively 00:20:18.400 --> 00:20:20.549 align:start position:0% We can now finally start to actively write<00:20:18.720> out<00:20:19.039> our<00:20:19.360> core<00:20:19.679> underlying<00:20:20.320> code 00:20:20.549 --> 00:20:20.559 align:start position:0% write out our core underlying code 00:20:20.559 --> 00:20:22.230 align:start position:0% write out our core underlying code snippets. 00:20:22.230 --> 00:20:22.240 align:start position:0% snippets. 00:20:22.240 --> 00:20:25.110 align:start position:0% snippets. The<00:20:22.480> generated<00:20:23.120> codeex<00:20:23.679> AI<00:20:24.080> response<00:20:24.880> will 00:20:25.110 --> 00:20:25.120 align:start position:0% The generated codeex AI response will 00:20:25.120 --> 00:20:27.110 align:start position:0% The generated codeex AI response will seamlessly<00:20:25.760> appear<00:20:26.240> right<00:20:26.559> here<00:20:26.720> on<00:20:26.960> the 00:20:27.110 --> 00:20:27.120 align:start position:0% seamlessly appear right here on the 00:20:27.120 --> 00:20:28.630 align:start position:0% seamlessly appear right here on the interface. 00:20:28.630 --> 00:20:28.640 align:start position:0% interface. 00:20:28.640 --> 00:20:30.549 align:start position:0% interface. We<00:20:28.880> will<00:20:29.039> be<00:20:29.120> able<00:20:29.360> to<00:20:29.520> clearly<00:20:30.000> see<00:20:30.240> our 00:20:30.549 --> 00:20:30.559 align:start position:0% We will be able to clearly see our 00:20:30.559 --> 00:20:33.590 align:start position:0% We will be able to clearly see our active<00:20:31.039> IDE<00:20:31.600> connection,<00:20:32.640> the<00:20:32.880> linked<00:20:33.200> source 00:20:33.590 --> 00:20:33.600 align:start position:0% active IDE connection, the linked source 00:20:33.600 --> 00:20:36.390 align:start position:0% active IDE connection, the linked source repository,<00:20:34.720> the<00:20:34.960> comprehensive<00:20:35.760> onboarding 00:20:36.390 --> 00:20:36.400 align:start position:0% repository, the comprehensive onboarding 00:20:36.400 --> 00:20:39.270 align:start position:0% repository, the comprehensive onboarding bug<00:20:36.720> log,<00:20:37.440> and<00:20:37.679> of<00:20:37.919> course<00:20:38.559> our<00:20:38.799> preferred 00:20:39.270 --> 00:20:39.280 align:start position:0% bug log, and of course our preferred 00:20:39.280 --> 00:20:42.149 align:start position:0% bug log, and of course our preferred dark<00:20:39.600> mode<00:20:39.919> visual<00:20:40.240> theme.<00:20:41.679> we<00:20:42.000> will 00:20:42.149 --> 00:20:42.159 align:start position:0% dark mode visual theme. we will 00:20:42.159 --> 00:20:44.870 align:start position:0% dark mode visual theme. we will consistently<00:20:42.880> get<00:20:43.280> highly<00:20:43.760> accurate<00:20:44.400> direct 00:20:44.870 --> 00:20:44.880 align:start position:0% consistently get highly accurate direct 00:20:44.880 --> 00:20:47.590 align:start position:0% consistently get highly accurate direct responses<00:20:45.520> moving<00:20:45.840> forward. 00:20:47.590 --> 00:20:47.600 align:start position:0% responses moving forward. 00:20:47.600 --> 00:20:49.990 align:start position:0% responses moving forward. Now,<00:20:48.240> we<00:20:48.480> need<00:20:48.559> to<00:20:48.799> take<00:20:48.960> a<00:20:49.200> very<00:20:49.520> close<00:20:49.760> look 00:20:49.990 --> 00:20:50.000 align:start position:0% Now, we need to take a very close look 00:20:50.000 --> 00:20:53.350 align:start position:0% Now, we need to take a very close look at<00:20:50.159> our<00:20:50.480> overall<00:20:50.880> system<00:20:51.280> usage<00:20:51.760> metrics. 00:20:53.350 --> 00:20:53.360 align:start position:0% at our overall system usage metrics. 00:20:53.360 --> 00:20:55.510 align:start position:0% at our overall system usage metrics. I<00:20:53.600> purposefully<00:20:54.240> navigate<00:20:54.720> back<00:20:54.960> over<00:20:55.200> to<00:20:55.360> the 00:20:55.510 --> 00:20:55.520 align:start position:0% I purposefully navigate back over to the 00:20:55.520 --> 00:20:58.070 align:start position:0% I purposefully navigate back over to the main<00:20:55.760> settings<00:20:56.159> page. 00:20:58.070 --> 00:20:58.080 align:start position:0% main settings page. 00:20:58.080 --> 00:21:00.710 align:start position:0% main settings page. The<00:20:58.320> exact<00:20:58.799> same<00:20:59.200> user<00:20:59.600> account<00:20:59.919> is<00:21:00.159> actively 00:21:00.710 --> 00:21:00.720 align:start position:0% The exact same user account is actively 00:21:00.720 --> 00:21:03.909 align:start position:0% The exact same user account is actively being<00:21:01.039> used<00:21:01.440> uniformly<00:21:02.240> everywhere. 00:21:03.909 --> 00:21:03.919 align:start position:0% being used uniformly everywhere. 00:21:03.919 --> 00:21:06.310 align:start position:0% being used uniformly everywhere. We<00:21:04.159> can<00:21:04.320> easily<00:21:04.720> modify<00:21:05.120> our<00:21:05.440> deeper<00:21:05.840> codec 00:21:06.310 --> 00:21:06.320 align:start position:0% We can easily modify our deeper codec 00:21:06.320 --> 00:21:08.950 align:start position:0% We can easily modify our deeper codec software<00:21:06.640> settings<00:21:07.120> right<00:21:07.440> here. 00:21:08.950 --> 00:21:08.960 align:start position:0% software settings right here. 00:21:08.960 --> 00:21:11.830 align:start position:0% software settings right here. You<00:21:09.200> clearly<00:21:09.600> see<00:21:09.919> broad<00:21:10.320> configurations, 00:21:11.830 --> 00:21:11.840 align:start position:0% You clearly see broad configurations, 00:21:11.840 --> 00:21:13.990 align:start position:0% You clearly see broad configurations, custom<00:21:12.320> personalization, 00:21:13.990 --> 00:21:14.000 align:start position:0% custom personalization, 00:21:14.000 --> 00:21:16.870 align:start position:0% custom personalization, advanced<00:21:14.640> MCP<00:21:15.200> servers,<00:21:16.320> web<00:21:16.559> hook 00:21:16.870 --> 00:21:16.880 align:start position:0% advanced MCP servers, web hook 00:21:16.880 --> 00:21:20.149 align:start position:0% advanced MCP servers, web hook integrations,<00:21:18.159> system<00:21:18.559> usage,<00:21:19.360> and<00:21:19.679> active 00:21:20.149 --> 00:21:20.159 align:start position:0% integrations, system usage, and active 00:21:20.159 --> 00:21:21.669 align:start position:0% integrations, system usage, and active billing. 00:21:21.669 --> 00:21:21.679 align:start position:0% billing. 00:21:21.679 --> 00:21:24.070 align:start position:0% billing. We<00:21:22.000> absolutely<00:21:22.720> need<00:21:22.880> to<00:21:23.039> check<00:21:23.280> these<00:21:23.600> panels 00:21:24.070 --> 00:21:24.080 align:start position:0% We absolutely need to check these panels 00:21:24.080 --> 00:21:26.710 align:start position:0% We absolutely need to check these panels timely<00:21:24.559> and<00:21:24.799> consistently<00:21:25.919> to<00:21:26.159> perfectly 00:21:26.710 --> 00:21:26.720 align:start position:0% timely and consistently to perfectly 00:21:26.720 --> 00:21:28.710 align:start position:0% timely and consistently to perfectly know<00:21:27.039> exactly<00:21:27.520> how<00:21:27.760> we<00:21:28.000> are<00:21:28.159> efficiently 00:21:28.710 --> 00:21:28.720 align:start position:0% know exactly how we are efficiently 00:21:28.720 --> 00:21:31.510 align:start position:0% know exactly how we are efficiently carrying<00:21:29.200> all<00:21:29.360> these<00:21:29.679> things<00:21:29.919> forward. 00:21:31.510 --> 00:21:31.520 align:start position:0% carrying all these things forward. 00:21:31.520 --> 00:21:34.950 align:start position:0% carrying all these things forward. We<00:21:31.760> can<00:21:31.919> chat<00:21:32.240> and<00:21:32.640> utilize<00:21:33.120> commands.<00:21:34.559> We<00:21:34.799> can 00:21:34.950 --> 00:21:34.960 align:start position:0% We can chat and utilize commands. We can 00:21:34.960 --> 00:21:37.430 align:start position:0% We can chat and utilize commands. We can switch<00:21:35.280> models<00:21:35.679> and<00:21:35.919> connect<00:21:36.240> apps.<00:21:37.039> Inside 00:21:37.430 --> 00:21:37.440 align:start position:0% switch models and connect apps. Inside 00:21:37.440 --> 00:21:39.350 align:start position:0% switch models and connect apps. Inside the<00:21:37.679> primary<00:21:38.080> settings<00:21:38.400> menu,<00:21:39.120> we 00:21:39.350 --> 00:21:39.360 align:start position:0% the primary settings menu, we 00:21:39.360 --> 00:21:41.029 align:start position:0% the primary settings menu, we prominently<00:21:39.919> have<00:21:40.080> the<00:21:40.240> visual<00:21:40.640> appearance 00:21:41.029 --> 00:21:41.039 align:start position:0% prominently have the visual appearance 00:21:41.039 --> 00:21:43.190 align:start position:0% prominently have the visual appearance and<00:21:41.360> core<00:21:41.679> system<00:21:42.000> configuration<00:21:42.720> tabs. 00:21:43.190 --> 00:21:43.200 align:start position:0% and core system configuration tabs. 00:21:43.200 --> 00:21:46.230 align:start position:0% and core system configuration tabs. Right<00:21:43.440> at<00:21:43.600> the<00:21:43.760> top,<00:21:44.960> we<00:21:45.200> absolutely<00:21:45.919> also 00:21:46.230 --> 00:21:46.240 align:start position:0% Right at the top, we absolutely also 00:21:46.240 --> 00:21:48.789 align:start position:0% Right at the top, we absolutely also have<00:21:46.480> detailed<00:21:46.960> personalization<00:21:47.840> settings, 00:21:48.789 --> 00:21:48.799 align:start position:0% have detailed personalization settings, 00:21:48.799 --> 00:21:51.430 align:start position:0% have detailed personalization settings, custom<00:21:49.200> keyboard<00:21:49.600> shortcuts,<00:21:50.720> active<00:21:51.120> usage 00:21:51.430 --> 00:21:51.440 align:start position:0% custom keyboard shortcuts, active usage 00:21:51.440 --> 00:21:53.110 align:start position:0% custom keyboard shortcuts, active usage limits,<00:21:52.080> and<00:21:52.320> standard<00:21:52.720> billing 00:21:53.110 --> 00:21:53.120 align:start position:0% limits, and standard billing 00:21:53.120 --> 00:21:54.789 align:start position:0% limits, and standard billing information. 00:21:54.789 --> 00:21:54.799 align:start position:0% information. 00:21:54.799 --> 00:21:57.270 align:start position:0% information. The<00:21:55.120> general<00:21:55.520> designated<00:21:56.240> application<00:21:56.880> usage 00:21:57.270 --> 00:21:57.280 align:start position:0% The general designated application usage 00:21:57.280 --> 00:22:00.470 align:start position:0% The general designated application usage limit<00:21:58.080> strictly<00:21:58.559> caps<00:21:58.960> out<00:21:59.120> at<00:21:59.440> exactly<00:22:00.080> 5 00:22:00.470 --> 00:22:00.480 align:start position:0% limit strictly caps out at exactly 5 00:22:00.480 --> 00:22:01.830 align:start position:0% limit strictly caps out at exactly 5 hours. 00:22:01.830 --> 00:22:01.840 align:start position:0% hours. 00:22:01.840 --> 00:22:04.630 align:start position:0% hours. Currently,<00:22:02.320> we<00:22:02.559> happily<00:22:02.960> have<00:22:03.120> a<00:22:03.280> massive<00:22:03.760> 99% 00:22:04.630 --> 00:22:04.640 align:start position:0% Currently, we happily have a massive 99% 00:22:04.640 --> 00:22:07.190 align:start position:0% Currently, we happily have a massive 99% of<00:22:04.799> that<00:22:04.960> time<00:22:05.280> left<00:22:05.520> available. 00:22:07.190 --> 00:22:07.200 align:start position:0% of that time left available. 00:22:07.200 --> 00:22:10.070 align:start position:0% of that time left available. The<00:22:07.440> broader<00:22:07.919> weekly<00:22:08.320> limit<00:22:09.120> currently<00:22:09.520> shows 00:22:10.070 --> 00:22:10.080 align:start position:0% The broader weekly limit currently shows 00:22:10.080 --> 00:22:13.350 align:start position:0% The broader weekly limit currently shows 100%<00:22:10.880> completely<00:22:11.360> left<00:22:11.679> over.<00:22:12.880> We<00:22:13.200> have 00:22:13.350 --> 00:22:13.360 align:start position:0% 100% completely left over. We have 00:22:13.360 --> 00:22:15.830 align:start position:0% 100% completely left over. We have successfully<00:22:14.000> expanded<00:22:14.559> our<00:22:14.880> overall<00:22:15.360> codeex 00:22:15.830 --> 00:22:15.840 align:start position:0% successfully expanded our overall codeex 00:22:15.840 --> 00:22:18.230 align:start position:0% successfully expanded our overall codeex usage<00:22:16.240> capabilities<00:22:17.360> alongside<00:22:18.000> the 00:22:18.230 --> 00:22:18.240 align:start position:0% usage capabilities alongside the 00:22:18.240 --> 00:22:22.710 align:start position:0% usage capabilities alongside the powerful<00:22:18.799> GPT<00:22:19.600> 5.5<00:22:20.400> deep<00:22:20.799> thinking<00:22:21.120> mode.<00:22:22.480> We 00:22:22.710 --> 00:22:22.720 align:start position:0% powerful GPT 5.5 deep thinking mode. We 00:22:22.720 --> 00:22:24.549 align:start position:0% powerful GPT 5.5 deep thinking mode. We can<00:22:22.880> effortlessly<00:22:23.520> purchase<00:22:23.919> an<00:22:24.159> additional 00:22:24.549 --> 00:22:24.559 align:start position:0% can effortlessly purchase an additional 00:22:24.559 --> 00:22:26.630 align:start position:0% can effortlessly purchase an additional credit<00:22:24.880> balance<00:22:25.200> whenever<00:22:25.679> needed. 00:22:26.630 --> 00:22:26.640 align:start position:0% credit balance whenever needed. 00:22:26.640 --> 00:22:29.270 align:start position:0% credit balance whenever needed. Supported<00:22:27.760> system<00:22:28.080> integrations<00:22:28.799> proudly 00:22:29.270 --> 00:22:29.280 align:start position:0% Supported system integrations proudly 00:22:29.280 --> 00:22:32.310 align:start position:0% Supported system integrations proudly include<00:22:30.240> seamless<00:22:30.720> browser<00:22:31.120> connections, 00:22:32.310 --> 00:22:32.320 align:start position:0% include seamless browser connections, 00:22:32.320 --> 00:22:34.470 align:start position:0% include seamless browser connections, broad<00:22:32.720> computer<00:22:33.120> use<00:22:33.360> permissions,<00:22:34.240> and 00:22:34.470 --> 00:22:34.480 align:start position:0% broad computer use permissions, and 00:22:34.480 --> 00:22:37.510 align:start position:0% broad computer use permissions, and robust<00:22:35.039> MCP<00:22:35.679> servers. 00:22:37.510 --> 00:22:37.520 align:start position:0% robust MCP servers. 00:22:37.520 --> 00:22:39.590 align:start position:0% robust MCP servers. The<00:22:37.840> core<00:22:38.080> coding<00:22:38.559> section<00:22:39.039> beautifully 00:22:39.590 --> 00:22:39.600 align:start position:0% The core coding section beautifully 00:22:39.600 --> 00:22:43.029 align:start position:0% The core coding section beautifully includes<00:22:40.640> active<00:22:41.039> web<00:22:41.200> hooks,<00:22:42.159> secure<00:22:42.640> remote 00:22:43.029 --> 00:22:43.039 align:start position:0% includes active web hooks, secure remote 00:22:43.039 --> 00:22:45.430 align:start position:0% includes active web hooks, secure remote connections,<00:22:44.240> complete<00:22:44.720> git<00:22:45.039> source 00:22:45.430 --> 00:22:45.440 align:start position:0% connections, complete git source 00:22:45.440 --> 00:22:48.789 align:start position:0% connections, complete git source control,<00:22:46.480> safe<00:22:46.960> isolated<00:22:47.520> environments,<00:22:48.480> and 00:22:48.789 --> 00:22:48.799 align:start position:0% control, safe isolated environments, and 00:22:48.799 --> 00:22:51.909 align:start position:0% control, safe isolated environments, and managed<00:22:49.200> work<00:22:49.520> trees.<00:22:50.960> Our<00:22:51.280> foundational 00:22:51.909 --> 00:22:51.919 align:start position:0% managed work trees. Our foundational 00:22:51.919 --> 00:22:55.430 align:start position:0% managed work trees. Our foundational setup<00:22:52.320> phase<00:22:52.640> is<00:22:52.880> now<00:22:53.280> entirely<00:22:53.919> complete. 00:22:55.430 --> 00:22:55.440 align:start position:0% setup phase is now entirely complete. 00:22:55.440 --> 00:22:57.909 align:start position:0% setup phase is now entirely complete. The<00:22:55.679> highly<00:22:56.080> anticipated<00:22:56.799> direct<00:22:57.200> usage 00:22:57.909 --> 00:22:57.919 align:start position:0% The highly anticipated direct usage 00:22:57.919 --> 00:23:02.710 align:start position:0% The highly anticipated direct usage strictly<00:22:58.400> begins<00:22:58.960> right<00:22:59.280> now. 00:23:02.710 --> 00:23:02.720 align:start position:0% 00:23:02.720 --> 00:23:05.110 align:start position:0% We<00:23:02.960> will<00:23:03.120> now<00:23:03.440> efficiently<00:23:04.080> set<00:23:04.320> up<00:23:04.640> highly 00:23:05.110 --> 00:23:05.120 align:start position:0% We will now efficiently set up highly 00:23:05.120 --> 00:23:06.950 align:start position:0% We will now efficiently set up highly secure<00:23:05.760> cloud-based<00:23:06.480> development 00:23:06.950 --> 00:23:06.960 align:start position:0% secure cloud-based development 00:23:06.960 --> 00:23:09.270 align:start position:0% secure cloud-based development environments<00:23:07.760> right<00:23:08.080> here<00:23:08.320> in<00:23:08.559> this<00:23:08.799> specific 00:23:09.270 --> 00:23:09.280 align:start position:0% environments right here in this specific 00:23:09.280 --> 00:23:11.029 align:start position:0% environments right here in this specific module. 00:23:11.029 --> 00:23:11.039 align:start position:0% module. 00:23:11.039 --> 00:23:13.029 align:start position:0% module. You<00:23:11.280> probably<00:23:11.679> remember<00:23:12.080> that<00:23:12.320> we<00:23:12.559> previously 00:23:13.029 --> 00:23:13.039 align:start position:0% You probably remember that we previously 00:23:13.039 --> 00:23:15.110 align:start position:0% You probably remember that we previously ran<00:23:13.280> our<00:23:13.520> codeex<00:23:14.000> agent<00:23:14.400> directly<00:23:14.799> here<00:23:14.960> on 00:23:15.110 --> 00:23:15.120 align:start position:0% ran our codeex agent directly here on 00:23:15.120 --> 00:23:17.110 align:start position:0% ran our codeex agent directly here on the<00:23:15.280> local<00:23:15.600> machine. 00:23:17.110 --> 00:23:17.120 align:start position:0% the local machine. 00:23:17.120 --> 00:23:19.350 align:start position:0% the local machine. Absolutely<00:23:17.840> all<00:23:18.080> of<00:23:18.240> our<00:23:18.480> core<00:23:18.799> operational 00:23:19.350 --> 00:23:19.360 align:start position:0% Absolutely all of our core operational 00:23:19.360 --> 00:23:21.669 align:start position:0% Absolutely all of our core operational functions<00:23:19.919> were<00:23:20.159> safely<00:23:20.640> contained<00:23:21.200> directly 00:23:21.669 --> 00:23:21.679 align:start position:0% functions were safely contained directly 00:23:21.679 --> 00:23:25.270 align:start position:0% functions were safely contained directly inside<00:23:22.080> it.<00:23:23.520> Now,<00:23:23.919> however,<00:23:24.880> we<00:23:25.039> will 00:23:25.270 --> 00:23:25.280 align:start position:0% inside it. Now, however, we will 00:23:25.280 --> 00:23:27.110 align:start position:0% inside it. Now, however, we will purposefully<00:23:25.919> run<00:23:26.159> our<00:23:26.480> advanced 00:23:27.110 --> 00:23:27.120 align:start position:0% purposefully run our advanced 00:23:27.120 --> 00:23:29.430 align:start position:0% purposefully run our advanced cloud-based<00:23:27.840> development<00:23:28.320> environment 00:23:29.430 --> 00:23:29.440 align:start position:0% cloud-based development environment 00:23:29.440 --> 00:23:31.830 align:start position:0% cloud-based development environment securely<00:23:30.080> integrated<00:23:30.799> directly<00:23:31.360> within<00:23:31.600> our 00:23:31.830 --> 00:23:31.840 align:start position:0% securely integrated directly within our 00:23:31.840 --> 00:23:34.470 align:start position:0% securely integrated directly within our main<00:23:32.080> codec<00:23:32.640> setup. 00:23:34.470 --> 00:23:34.480 align:start position:0% main codec setup. 00:23:34.480 --> 00:23:36.549 align:start position:0% main codec setup. First<00:23:34.720> things<00:23:35.039> first,<00:23:35.840> I<00:23:36.080> will<00:23:36.240> quickly 00:23:36.549 --> 00:23:36.559 align:start position:0% First things first, I will quickly 00:23:36.559 --> 00:23:38.470 align:start position:0% First things first, I will quickly navigate<00:23:37.039> back<00:23:37.280> over<00:23:37.520> to<00:23:37.679> the<00:23:37.840> main<00:23:38.159> settings 00:23:38.470 --> 00:23:38.480 align:start position:0% navigate back over to the main settings 00:23:38.480 --> 00:23:40.710 align:start position:0% navigate back over to the main settings panel<00:23:39.120> and<00:23:39.440> intentionally<00:23:40.080> make<00:23:40.240> the<00:23:40.480> system 00:23:40.710 --> 00:23:40.720 align:start position:0% panel and intentionally make the system 00:23:40.720 --> 00:23:42.390 align:start position:0% panel and intentionally make the system font<00:23:41.120> slightly<00:23:41.520> smaller<00:23:41.919> for<00:23:42.080> better 00:23:42.390 --> 00:23:42.400 align:start position:0% font slightly smaller for better 00:23:42.400 --> 00:23:44.230 align:start position:0% font slightly smaller for better viewing. 00:23:44.230 --> 00:23:44.240 align:start position:0% viewing. 00:23:44.240 --> 00:23:46.070 align:start position:0% viewing. We<00:23:44.480> gracefully<00:23:45.120> go<00:23:45.280> over<00:23:45.440> to<00:23:45.600> the<00:23:45.760> visual 00:23:46.070 --> 00:23:46.080 align:start position:0% We gracefully go over to the visual 00:23:46.080 --> 00:23:48.630 align:start position:0% We gracefully go over to the visual appearance<00:23:46.559> tab<00:23:47.280> and<00:23:47.600> actively<00:23:48.159> change<00:23:48.400> the 00:23:48.630 --> 00:23:48.640 align:start position:0% appearance tab and actively change the 00:23:48.640 --> 00:23:51.270 align:start position:0% appearance tab and actively change the primary<00:23:49.039> text<00:23:49.360> size<00:23:49.679> down<00:23:49.919> from<00:23:50.240> 24<00:23:50.960> to 00:23:51.270 --> 00:23:51.280 align:start position:0% primary text size down from 24 to 00:23:51.280 --> 00:23:53.590 align:start position:0% primary text size down from 24 to precisely<00:23:52.080> 20. 00:23:53.590 --> 00:23:53.600 align:start position:0% precisely 20. 00:23:53.600 --> 00:23:56.310 align:start position:0% precisely 20. Now,<00:23:54.159> the<00:23:54.480> overall<00:23:54.880> tech<00:23:55.200> size<00:23:55.520> is<00:23:55.760> just<00:23:56.000> so 00:23:56.310 --> 00:23:56.320 align:start position:0% Now, the overall tech size is just so 00:23:56.320 --> 00:23:58.870 align:start position:0% Now, the overall tech size is just so much<00:23:56.480> better<00:23:56.720> and<00:23:57.039> more<00:23:57.200> manageable. 00:23:58.870 --> 00:23:58.880 align:start position:0% much better and more manageable. 00:23:58.880 --> 00:24:00.870 align:start position:0% much better and more manageable. I<00:23:59.120> will<00:23:59.280> clearly<00:23:59.600> explain<00:23:59.919> to<00:24:00.159> you<00:24:00.320> generally 00:24:00.870 --> 00:24:00.880 align:start position:0% I will clearly explain to you generally 00:24:00.880 --> 00:24:02.630 align:start position:0% I will clearly explain to you generally what<00:24:01.120> these<00:24:01.440> advanced<00:24:01.919> cloud-based 00:24:02.630 --> 00:24:02.640 align:start position:0% what these advanced cloud-based 00:24:02.640 --> 00:24:05.669 align:start position:0% what these advanced cloud-based development<00:24:03.120> environments<00:24:03.840> actually<00:24:04.240> are. 00:24:05.669 --> 00:24:05.679 align:start position:0% development environments actually are. 00:24:05.679 --> 00:24:08.070 align:start position:0% development environments actually are. We<00:24:05.919> will<00:24:06.159> deeply<00:24:06.640> understand<00:24:07.200> this<00:24:07.520> entire 00:24:08.070 --> 00:24:08.080 align:start position:0% We will deeply understand this entire 00:24:08.080 --> 00:24:11.190 align:start position:0% We will deeply understand this entire concept<00:24:08.640> right<00:24:08.880> here<00:24:09.200> today.<00:24:10.240> You<00:24:10.559> absolutely 00:24:11.190 --> 00:24:11.200 align:start position:0% concept right here today. You absolutely 00:24:11.200 --> 00:24:13.669 align:start position:0% concept right here today. You absolutely should<00:24:11.440> know<00:24:11.760> right<00:24:12.000> up<00:24:12.240> front<00:24:12.880> that<00:24:13.120> this<00:24:13.440> is 00:24:13.669 --> 00:24:13.679 align:start position:0% should know right up front that this is 00:24:13.679 --> 00:24:16.230 align:start position:0% should know right up front that this is essentially<00:24:14.080> a<00:24:14.320> preconfigured,<00:24:15.520> entirely 00:24:16.230 --> 00:24:16.240 align:start position:0% essentially a preconfigured, entirely 00:24:16.240 --> 00:24:19.590 align:start position:0% essentially a preconfigured, entirely remotely<00:24:16.720> hosted<00:24:17.200> software<00:24:17.760> workspace. 00:24:19.590 --> 00:24:19.600 align:start position:0% remotely hosted software workspace. 00:24:19.600 --> 00:24:22.549 align:start position:0% remotely hosted software workspace. It<00:24:19.840> actively<00:24:20.320> contains<00:24:20.720> your<00:24:21.039> preferred<00:24:21.600> IDE 00:24:22.549 --> 00:24:22.559 align:start position:0% It actively contains your preferred IDE 00:24:22.559 --> 00:24:24.630 align:start position:0% It actively contains your preferred IDE alongside<00:24:23.200> all<00:24:23.440> your<00:24:23.679> necessary<00:24:24.159> background 00:24:24.630 --> 00:24:24.640 align:start position:0% alongside all your necessary background 00:24:24.640 --> 00:24:26.149 align:start position:0% alongside all your necessary background tools. 00:24:26.149 --> 00:24:26.159 align:start position:0% tools. 00:24:26.159 --> 00:24:28.789 align:start position:0% tools. Modern<00:24:26.559> developers<00:24:27.120> can<00:24:27.360> effortlessly<00:24:28.000> code, 00:24:28.789 --> 00:24:28.799 align:start position:0% Modern developers can effortlessly code, 00:24:28.799 --> 00:24:31.669 align:start position:0% Modern developers can effortlessly code, rigorously<00:24:29.440> test,<00:24:30.240> and<00:24:30.640> smoothly<00:24:31.120> deploy 00:24:31.669 --> 00:24:31.679 align:start position:0% rigorously test, and smoothly deploy 00:24:31.679 --> 00:24:33.669 align:start position:0% rigorously test, and smoothly deploy complex<00:24:32.240> software<00:24:32.799> straight<00:24:33.120> from<00:24:33.279> the<00:24:33.440> web 00:24:33.669 --> 00:24:33.679 align:start position:0% complex software straight from the web 00:24:33.679 --> 00:24:35.269 align:start position:0% complex software straight from the web browser. 00:24:35.269 --> 00:24:35.279 align:start position:0% browser. 00:24:35.279 --> 00:24:37.830 align:start position:0% browser. The<00:24:35.520> acronym<00:24:36.320> CDE 00:24:37.830 --> 00:24:37.840 align:start position:0% The acronym CDE 00:24:37.840 --> 00:24:40.149 align:start position:0% The acronym CDE specifically<00:24:38.640> stands<00:24:38.960> for<00:24:39.600> cloud 00:24:40.149 --> 00:24:40.159 align:start position:0% specifically stands for cloud 00:24:40.159 --> 00:24:42.710 align:start position:0% specifically stands for cloud development<00:24:40.880> environment. 00:24:42.710 --> 00:24:42.720 align:start position:0% development environment. 00:24:42.720 --> 00:24:44.710 align:start position:0% development environment. It<00:24:42.960> effectively<00:24:43.600> solves<00:24:43.919> that<00:24:44.240> highly 00:24:44.710 --> 00:24:44.720 align:start position:0% It effectively solves that highly 00:24:44.720 --> 00:24:47.830 align:start position:0% It effectively solves that highly frustrating<00:24:45.840> age-old<00:24:46.559> problem<00:24:47.279> when<00:24:47.600> a 00:24:47.830 --> 00:24:47.840 align:start position:0% frustrating age-old problem when a 00:24:47.840 --> 00:24:50.390 align:start position:0% frustrating age-old problem when a specific<00:24:48.240> piece<00:24:48.480> of<00:24:48.640> code<00:24:49.039> miraculously<00:24:50.000> only 00:24:50.390 --> 00:24:50.400 align:start position:0% specific piece of code miraculously only 00:24:50.400 --> 00:24:52.789 align:start position:0% specific piece of code miraculously only works<00:24:50.720> on<00:24:51.039> one<00:24:51.360> specific<00:24:51.840> person's<00:24:52.400> local 00:24:52.789 --> 00:24:52.799 align:start position:0% works on one specific person's local 00:24:52.799 --> 00:24:54.549 align:start position:0% works on one specific person's local computer. 00:24:54.549 --> 00:24:54.559 align:start position:0% computer. 00:24:54.559 --> 00:24:56.789 align:start position:0% computer. Brand<00:24:54.880> new<00:24:55.120> software<00:24:55.520> engineers<00:24:56.080> can<00:24:56.320> easily 00:24:56.789 --> 00:24:56.799 align:start position:0% Brand new software engineers can easily 00:24:56.799 --> 00:25:00.070 align:start position:0% Brand new software engineers can easily start<00:24:57.200> actively<00:24:57.760> coding<00:24:58.080> in<00:24:58.320> mere<00:24:58.720> minutes. 00:25:00.070 --> 00:25:00.080 align:start position:0% start actively coding in mere minutes. 00:25:00.080 --> 00:25:03.510 align:start position:0% start actively coding in mere minutes. This<00:25:00.320> is<00:25:00.480> our<00:25:00.720> dedicated<00:25:01.360> cloud<00:25:01.679> system. 00:25:03.510 --> 00:25:03.520 align:start position:0% This is our dedicated cloud system. 00:25:03.520 --> 00:25:05.510 align:start position:0% This is our dedicated cloud system. Now<00:25:04.000> let's<00:25:04.320> take<00:25:04.480> a<00:25:04.640> moment<00:25:04.880> to<00:25:05.120> talk<00:25:05.279> about 00:25:05.510 --> 00:25:05.520 align:start position:0% Now let's take a moment to talk about 00:25:05.520 --> 00:25:07.590 align:start position:0% Now let's take a moment to talk about codeex<00:25:06.080> itself. 00:25:07.590 --> 00:25:07.600 align:start position:0% codeex itself. 00:25:07.600 --> 00:25:10.470 align:start position:0% codeex itself. Codeex<00:25:08.240> fundamentally<00:25:09.039> has<00:25:09.279> some<00:25:09.520> massive, 00:25:10.470 --> 00:25:10.480 align:start position:0% Codeex fundamentally has some massive, 00:25:10.480 --> 00:25:13.830 align:start position:0% Codeex fundamentally has some massive, undeniably<00:25:11.360> big<00:25:11.679> advantages<00:25:12.320> here. 00:25:13.830 --> 00:25:13.840 align:start position:0% undeniably big advantages here. 00:25:13.840 --> 00:25:16.470 align:start position:0% undeniably big advantages here. Codeex<00:25:14.400> genuinely<00:25:15.039> works<00:25:15.520> absolute<00:25:16.080> best 00:25:16.470 --> 00:25:16.480 align:start position:0% Codeex genuinely works absolute best 00:25:16.480 --> 00:25:18.789 align:start position:0% Codeex genuinely works absolute best when<00:25:16.720> it<00:25:16.880> can<00:25:17.039> safely<00:25:17.520> access<00:25:17.919> the<00:25:18.240> entire 00:25:18.789 --> 00:25:18.799 align:start position:0% when it can safely access the entire 00:25:18.799 --> 00:25:21.110 align:start position:0% when it can safely access the entire full<00:25:19.120> code<00:25:19.440> repository. 00:25:21.110 --> 00:25:21.120 align:start position:0% full code repository. 00:25:21.120 --> 00:25:23.350 align:start position:0% full code repository. It<00:25:21.360> impressively<00:25:22.080> also<00:25:22.480> has<00:25:22.799> powerful 00:25:23.350 --> 00:25:23.360 align:start position:0% It impressively also has powerful 00:25:23.360 --> 00:25:26.230 align:start position:0% It impressively also has powerful built-in<00:25:23.840> deployment<00:25:24.320> tools.<00:25:25.600> A<00:25:25.840> cloud 00:25:26.230 --> 00:25:26.240 align:start position:0% built-in deployment tools. A cloud 00:25:26.240 --> 00:25:28.710 align:start position:0% built-in deployment tools. A cloud environment<00:25:26.880> safely<00:25:27.279> lets<00:25:27.600> codec<00:25:28.159> seamlessly 00:25:28.710 --> 00:25:28.720 align:start position:0% environment safely lets codec seamlessly 00:25:28.720 --> 00:25:30.310 align:start position:0% environment safely lets codec seamlessly talk<00:25:29.039> directly<00:25:29.520> to<00:25:29.679> remote<00:25:30.080> code 00:25:30.310 --> 00:25:30.320 align:start position:0% talk directly to remote code 00:25:30.320 --> 00:25:32.070 align:start position:0% talk directly to remote code repositories. 00:25:32.070 --> 00:25:32.080 align:start position:0% repositories. 00:25:32.080 --> 00:25:34.789 align:start position:0% repositories. It<00:25:32.320> can<00:25:32.480> reliably<00:25:33.120> run<00:25:33.360> terminal<00:25:33.919> commands, 00:25:34.789 --> 00:25:34.799 align:start position:0% It can reliably run terminal commands, 00:25:34.799 --> 00:25:37.510 align:start position:0% It can reliably run terminal commands, execute<00:25:35.360> unit<00:25:35.760> tests,<00:25:36.480> and<00:25:36.720> thoroughly<00:25:37.200> check 00:25:37.510 --> 00:25:37.520 align:start position:0% execute unit tests, and thoroughly check 00:25:37.520 --> 00:25:39.190 align:start position:0% execute unit tests, and thoroughly check projects. 00:25:39.190 --> 00:25:39.200 align:start position:0% projects. 00:25:39.200 --> 00:25:42.950 align:start position:0% projects. It<00:25:39.520> safely<00:25:40.000> makes<00:25:40.400> automated<00:25:41.039> code<00:25:41.279> changes. 00:25:42.950 --> 00:25:42.960 align:start position:0% It safely makes automated code changes. 00:25:42.960 --> 00:25:44.950 align:start position:0% It safely makes automated code changes. The<00:25:43.200> biggest<00:25:43.679> overall<00:25:44.159> benefit<00:25:44.640> is 00:25:44.950 --> 00:25:44.960 align:start position:0% The biggest overall benefit is 00:25:44.960 --> 00:25:48.070 align:start position:0% The biggest overall benefit is undeniable<00:25:46.320> absolute<00:25:47.039> consistency.<00:25:47.760> In 00:25:48.070 --> 00:25:48.080 align:start position:0% undeniable absolute consistency. In 00:25:48.080 --> 00:25:50.470 align:start position:0% undeniable absolute consistency. In significantly<00:25:48.880> older<00:25:49.440> traditional<00:25:50.080> local 00:25:50.470 --> 00:25:50.480 align:start position:0% significantly older traditional local 00:25:50.480 --> 00:25:52.630 align:start position:0% significantly older traditional local development<00:25:50.960> environments,<00:25:52.159> various 00:25:52.630 --> 00:25:52.640 align:start position:0% development environments, various 00:25:52.640 --> 00:25:54.789 align:start position:0% development environments, various developers<00:25:53.360> constantly<00:25:53.919> use<00:25:54.240> completely 00:25:54.789 --> 00:25:54.799 align:start position:0% developers constantly use completely 00:25:54.799 --> 00:25:57.029 align:start position:0% developers constantly use completely different<00:25:55.120> underlying<00:25:55.679> operating<00:25:56.159> systems 00:25:57.029 --> 00:25:57.039 align:start position:0% different underlying operating systems 00:25:57.039 --> 00:25:58.950 align:start position:0% different underlying operating systems and<00:25:57.360> vastly<00:25:57.919> different<00:25:58.240> local<00:25:58.559> machine 00:25:58.950 --> 00:25:58.960 align:start position:0% and vastly different local machine 00:25:58.960 --> 00:26:00.710 align:start position:0% and vastly different local machine settings. 00:26:00.710 --> 00:26:00.720 align:start position:0% settings. 00:26:00.720 --> 00:26:02.950 align:start position:0% settings. This<00:26:01.039> inherently<00:26:01.760> creates<00:26:02.080> the<00:26:02.320> infamous 00:26:02.950 --> 00:26:02.960 align:start position:0% This inherently creates the infamous 00:26:02.960 --> 00:26:05.750 align:start position:0% This inherently creates the infamous frustrating<00:26:04.320> well<00:26:04.640> it<00:26:04.880> perfectly<00:26:05.279> works<00:26:05.520> on 00:26:05.750 --> 00:26:05.760 align:start position:0% frustrating well it perfectly works on 00:26:05.760 --> 00:26:08.310 align:start position:0% frustrating well it perfectly works on my<00:26:06.000> machine<00:26:06.559> problem. 00:26:08.310 --> 00:26:08.320 align:start position:0% my machine problem. 00:26:08.320 --> 00:26:10.710 align:start position:0% my machine problem. Modern<00:26:08.960> streamlined<00:26:09.679> cloud<00:26:10.000> environments 00:26:10.710 --> 00:26:10.720 align:start position:0% Modern streamlined cloud environments 00:26:10.720 --> 00:26:12.710 align:start position:0% Modern streamlined cloud environments completely<00:26:11.200> remove<00:26:11.520> these<00:26:11.840> highly<00:26:12.240> annoying 00:26:12.710 --> 00:26:12.720 align:start position:0% completely remove these highly annoying 00:26:12.720 --> 00:26:14.950 align:start position:0% completely remove these highly annoying problems<00:26:13.120> entirely. 00:26:14.950 --> 00:26:14.960 align:start position:0% problems entirely. 00:26:14.960 --> 00:26:17.110 align:start position:0% problems entirely. Absolutely<00:26:15.760> everything<00:26:16.159> that<00:26:16.400> we<00:26:16.640> actively 00:26:17.110 --> 00:26:17.120 align:start position:0% Absolutely everything that we actively 00:26:17.120 --> 00:26:19.269 align:start position:0% Absolutely everything that we actively do<00:26:17.360> right<00:26:17.679> here.<00:26:18.320> For<00:26:18.400> example,<00:26:19.039> the 00:26:19.269 --> 00:26:19.279 align:start position:0% do right here. For example, the 00:26:19.279 --> 00:26:21.909 align:start position:0% do right here. For example, the previously<00:26:19.840> pinned<00:26:20.240> chat<00:26:20.559> log<00:26:21.200> specifically 00:26:21.909 --> 00:26:21.919 align:start position:0% previously pinned chat log specifically 00:26:21.919 --> 00:26:23.830 align:start position:0% previously pinned chat log specifically about<00:26:22.240> making<00:26:22.480> a<00:26:22.720> functional<00:26:23.200> calculator 00:26:23.830 --> 00:26:23.840 align:start position:0% about making a functional calculator 00:26:23.840 --> 00:26:25.430 align:start position:0% about making a functional calculator application. 00:26:25.430 --> 00:26:25.440 align:start position:0% application. 00:26:25.440 --> 00:26:27.590 align:start position:0% application. Absolutely<00:26:26.240> all<00:26:26.559> our<00:26:26.799> deep<00:26:27.120> technical 00:26:27.590 --> 00:26:27.600 align:start position:0% Absolutely all our deep technical 00:26:27.600 --> 00:26:29.669 align:start position:0% Absolutely all our deep technical discussions<00:26:28.480> are<00:26:28.799> safely<00:26:29.279> stored 00:26:29.669 --> 00:26:29.679 align:start position:0% discussions are safely stored 00:26:29.679 --> 00:26:33.510 align:start position:0% discussions are safely stored permanently<00:26:30.559> in<00:26:30.799> this<00:26:31.039> robust<00:26:31.600> cloud<00:26:32.000> system. 00:26:33.510 --> 00:26:33.520 align:start position:0% permanently in this robust cloud system. 00:26:33.520 --> 00:26:35.830 align:start position:0% permanently in this robust cloud system. We<00:26:33.760> can<00:26:33.919> effortlessly<00:26:34.640> and<00:26:34.960> rapidly<00:26:35.520> review 00:26:35.830 --> 00:26:35.840 align:start position:0% We can effortlessly and rapidly review 00:26:35.840 --> 00:26:38.470 align:start position:0% We can effortlessly and rapidly review our<00:26:36.159> collective<00:26:36.640> past<00:26:37.039> work<00:26:37.440> right<00:26:37.760> here<00:26:38.240> at 00:26:38.470 --> 00:26:38.480 align:start position:0% our collective past work right here at 00:26:38.480 --> 00:26:41.990 align:start position:0% our collective past work right here at any<00:26:38.799> given<00:26:39.120> time.<00:26:40.559> Other<00:26:40.960> incredibly<00:26:41.600> massive 00:26:41.990 --> 00:26:42.000 align:start position:0% any given time. Other incredibly massive 00:26:42.000 --> 00:26:44.470 align:start position:0% any given time. Other incredibly massive benefits<00:26:42.559> strictly<00:26:43.039> include<00:26:43.600> nearly<00:26:44.000> instant 00:26:44.470 --> 00:26:44.480 align:start position:0% benefits strictly include nearly instant 00:26:44.480 --> 00:26:47.029 align:start position:0% benefits strictly include nearly instant team<00:26:44.799> on<00:26:44.960> boarding,<00:26:46.000> highly<00:26:46.480> consistent 00:26:47.029 --> 00:26:47.039 align:start position:0% team on boarding, highly consistent 00:26:47.039 --> 00:26:49.909 align:start position:0% team on boarding, highly consistent underlying<00:26:47.600> tool<00:26:47.919> setups,<00:26:49.200> absolute 00:26:49.909 --> 00:26:49.919 align:start position:0% underlying tool setups, absolute 00:26:49.919 --> 00:26:52.630 align:start position:0% underlying tool setups, absolute hardware<00:26:50.400> independence,<00:26:51.600> and<00:26:51.840> reliable 00:26:52.630 --> 00:26:52.640 align:start position:0% hardware independence, and reliable 00:26:52.640 --> 00:26:55.909 align:start position:0% hardware independence, and reliable long-term<00:26:53.360> session<00:26:53.679> persistence. 00:26:55.909 --> 00:26:55.919 align:start position:0% long-term session persistence. 00:26:55.919 --> 00:26:58.630 align:start position:0% long-term session persistence. Now<00:26:56.480> moving<00:26:56.880> forward,<00:26:57.600> we<00:26:57.840> will<00:26:58.080> thoughtfully 00:26:58.630 --> 00:26:58.640 align:start position:0% Now moving forward, we will thoughtfully 00:26:58.640 --> 00:27:00.549 align:start position:0% Now moving forward, we will thoughtfully choose<00:26:58.960> a<00:26:59.200> specific<00:26:59.760> cloud<00:27:00.159> development 00:27:00.549 --> 00:27:00.559 align:start position:0% choose a specific cloud development 00:27:00.559 --> 00:27:03.669 align:start position:0% choose a specific cloud development platform<00:27:00.960> to<00:27:01.279> use.<00:27:02.400> I<00:27:02.640> will<00:27:02.799> happily<00:27:03.200> show<00:27:03.440> you 00:27:03.669 --> 00:27:03.679 align:start position:0% platform to use. I will happily show you 00:27:03.679 --> 00:27:05.590 align:start position:0% platform to use. I will happily show you some<00:27:03.919> excellent<00:27:04.400> real<00:27:04.799> world<00:27:05.039> examples 00:27:05.590 --> 00:27:05.600 align:start position:0% some excellent real world examples 00:27:05.600 --> 00:27:07.190 align:start position:0% some excellent real world examples shortly. 00:27:07.190 --> 00:27:07.200 align:start position:0% shortly. 00:27:07.200 --> 00:27:09.590 align:start position:0% shortly. First<00:27:07.440> and<00:27:07.679> foremost,<00:27:08.559> we<00:27:08.799> will<00:27:08.960> take<00:27:09.039> a<00:27:09.279> very 00:27:09.590 --> 00:27:09.600 align:start position:0% First and foremost, we will take a very 00:27:09.600 --> 00:27:12.950 align:start position:0% First and foremost, we will take a very close<00:27:09.919> look<00:27:10.080> at<00:27:10.400> GitHub<00:27:10.960> code<00:27:11.279> spaces<00:27:11.760> today. 00:27:12.950 --> 00:27:12.960 align:start position:0% close look at GitHub code spaces today. 00:27:12.960 --> 00:27:15.909 align:start position:0% close look at GitHub code spaces today. It<00:27:13.120> is<00:27:13.279> a<00:27:13.440> remarkably<00:27:14.080> secure,<00:27:14.880> highly<00:27:15.279> robust 00:27:15.909 --> 00:27:15.919 align:start position:0% It is a remarkably secure, highly robust 00:27:15.919 --> 00:27:17.669 align:start position:0% It is a remarkably secure, highly robust cloud<00:27:16.240> development<00:27:16.720> environment<00:27:17.200> used<00:27:17.520> by 00:27:17.669 --> 00:27:17.679 align:start position:0% cloud development environment used by 00:27:17.679 --> 00:27:19.110 align:start position:0% cloud development environment used by many. 00:27:19.110 --> 00:27:19.120 align:start position:0% many. 00:27:19.120 --> 00:27:21.669 align:start position:0% many. If<00:27:19.360> we<00:27:19.600> genuinely<00:27:20.159> do<00:27:20.400> not<00:27:20.799> want<00:27:20.960> to<00:27:21.200> use<00:27:21.360> this 00:27:21.669 --> 00:27:21.679 align:start position:0% If we genuinely do not want to use this 00:27:21.679 --> 00:27:24.070 align:start position:0% If we genuinely do not want to use this specific<00:27:22.080> one,<00:27:22.799> we<00:27:23.039> can<00:27:23.200> alternatively 00:27:24.070 --> 00:27:24.080 align:start position:0% specific one, we can alternatively 00:27:24.080 --> 00:27:26.149 align:start position:0% specific one, we can alternatively utilize<00:27:24.480> gitpod. 00:27:26.149 --> 00:27:26.159 align:start position:0% utilize gitpod. 00:27:26.159 --> 00:27:28.310 align:start position:0% utilize gitpod. We<00:27:26.480> actually<00:27:26.799> use<00:27:27.039> the<00:27:27.200> git<00:27:27.520> pod<00:27:27.840> platform 00:27:28.310 --> 00:27:28.320 align:start position:0% We actually use the git pod platform 00:27:28.320 --> 00:27:31.110 align:start position:0% We actually use the git pod platform quite<00:27:28.640> a<00:27:28.799> lot<00:27:28.880> in<00:27:29.120> our<00:27:29.279> daily<00:27:29.600> workflows.<00:27:30.960> It 00:27:31.110 --> 00:27:31.120 align:start position:0% quite a lot in our daily workflows. It 00:27:31.120 --> 00:27:34.390 align:start position:0% quite a lot in our daily workflows. It is<00:27:31.279> a<00:27:31.520> fantastic<00:27:32.320> strictly<00:27:32.880> ondemand,<00:27:34.000> highly 00:27:34.390 --> 00:27:34.400 align:start position:0% is a fantastic strictly ondemand, highly 00:27:34.400 --> 00:27:37.269 align:start position:0% is a fantastic strictly ondemand, highly scalable<00:27:35.039> development<00:27:35.520> environment. 00:27:37.269 --> 00:27:37.279 align:start position:0% scalable development environment. 00:27:37.279 --> 00:27:39.909 align:start position:0% scalable development environment. For<00:27:37.520> massively<00:27:38.080> big<00:27:38.400> enterprise<00:27:38.960> companies, 00:27:39.909 --> 00:27:39.919 align:start position:0% For massively big enterprise companies, 00:27:39.919 --> 00:27:43.269 align:start position:0% For massively big enterprise companies, we<00:27:40.159> consistently<00:27:40.880> have<00:27:41.120> the<00:27:41.440> AWS<00:27:42.320> Cloud9 00:27:43.269 --> 00:27:43.279 align:start position:0% we consistently have the AWS Cloud9 00:27:43.279 --> 00:27:46.310 align:start position:0% we consistently have the AWS Cloud9 infrastructure<00:27:44.240> safely<00:27:44.640> available. 00:27:46.310 --> 00:27:46.320 align:start position:0% infrastructure safely available. 00:27:46.320 --> 00:27:48.470 align:start position:0% infrastructure safely available. We<00:27:46.559> can<00:27:46.720> seamlessly<00:27:47.279> use<00:27:47.520> it<00:27:47.760> directly<00:27:48.240> for 00:27:48.470 --> 00:27:48.480 align:start position:0% We can seamlessly use it directly for 00:27:48.480 --> 00:27:51.990 align:start position:0% We can seamlessly use it directly for our<00:27:48.720> larger,<00:27:49.360> more<00:27:49.679> complex<00:27:50.159> coding<00:27:50.640> tasks. 00:27:51.990 --> 00:27:52.000 align:start position:0% our larger, more complex coding tasks. 00:27:52.000 --> 00:27:54.230 align:start position:0% our larger, more complex coding tasks. It<00:27:52.240> is<00:27:52.400> basically<00:27:52.880> a<00:27:53.120> fully<00:27:53.520> complete 00:27:54.230 --> 00:27:54.240 align:start position:0% It is basically a fully complete 00:27:54.240 --> 00:27:56.389 align:start position:0% It is basically a fully complete cloud-based<00:27:55.200> integration<00:27:55.919> development 00:27:56.389 --> 00:27:56.399 align:start position:0% cloud-based integration development 00:27:56.399 --> 00:27:58.950 align:start position:0% cloud-based integration development environment<00:27:57.120> from<00:27:57.440> Amazon. 00:27:58.950 --> 00:27:58.960 align:start position:0% environment from Amazon. 00:27:58.960 --> 00:28:01.830 align:start position:0% environment from Amazon. It<00:27:59.200> is<00:27:59.440> truly<00:27:59.840> a<00:28:00.159> complete<00:28:00.880> fully<00:28:01.279> featured 00:28:01.830 --> 00:28:01.840 align:start position:0% It is truly a complete fully featured 00:28:01.840 --> 00:28:04.789 align:start position:0% It is truly a complete fully featured IDE<00:28:02.640> right<00:28:02.880> in<00:28:03.120> your<00:28:03.279> browser. 00:28:04.789 --> 00:28:04.799 align:start position:0% IDE right in your browser. 00:28:04.799 --> 00:28:07.909 align:start position:0% IDE right in your browser. We<00:28:05.039> can<00:28:05.200> effortlessly<00:28:05.919> write<00:28:06.640> smoothly<00:28:07.279> run 00:28:07.909 --> 00:28:07.919 align:start position:0% We can effortlessly write smoothly run 00:28:07.919 --> 00:28:10.389 align:start position:0% We can effortlessly write smoothly run and<00:28:08.159> quickly<00:28:08.640> fix<00:28:09.039> our<00:28:09.360> complex<00:28:09.919> code 00:28:10.389 --> 00:28:10.399 align:start position:0% and quickly fix our complex code 00:28:10.399 --> 00:28:13.029 align:start position:0% and quickly fix our complex code directly<00:28:10.960> inside<00:28:11.360> it. 00:28:13.029 --> 00:28:13.039 align:start position:0% directly inside it. 00:28:13.039 --> 00:28:15.590 align:start position:0% directly inside it. These<00:28:13.360> are<00:28:13.520> a<00:28:13.760> few<00:28:14.159> older<00:28:14.799> very<00:28:15.200> solid 00:28:15.590 --> 00:28:15.600 align:start position:0% These are a few older very solid 00:28:15.600 --> 00:28:17.269 align:start position:0% These are a few older very solid examples. 00:28:17.269 --> 00:28:17.279 align:start position:0% examples. 00:28:17.279 --> 00:28:19.750 align:start position:0% examples. Now<00:28:17.600> I<00:28:17.840> will<00:28:18.080> explicitly<00:28:18.720> search<00:28:18.960> the<00:28:19.200> web<00:28:19.520> to 00:28:19.750 --> 00:28:19.760 align:start position:0% Now I will explicitly search the web to 00:28:19.760 --> 00:28:21.909 align:start position:0% Now I will explicitly search the web to see<00:28:19.840> if<00:28:20.080> Codeex<00:28:20.640> itself<00:28:21.120> is<00:28:21.440> officially 00:28:21.909 --> 00:28:21.919 align:start position:0% see if Codeex itself is officially 00:28:21.919 --> 00:28:24.230 align:start position:0% see if Codeex itself is officially classified<00:28:22.480> as<00:28:22.720> a<00:28:22.960> cloud-based<00:28:23.760> development 00:28:24.230 --> 00:28:24.240 align:start position:0% classified as a cloud-based development 00:28:24.240 --> 00:28:25.990 align:start position:0% classified as a cloud-based development environment. 00:28:25.990 --> 00:28:26.000 align:start position:0% environment. 00:28:26.000 --> 00:28:29.269 align:start position:0% environment. It<00:28:26.320> confidently<00:28:27.039> says<00:28:27.679> yes. 00:28:29.269 --> 00:28:29.279 align:start position:0% It confidently says yes. 00:28:29.279 --> 00:28:33.029 align:start position:0% It confidently says yes. Codeex<00:28:30.159> created<00:28:30.559> by<00:28:30.799> OpenAI<00:28:31.840> is<00:28:32.159> officially<00:28:32.720> a 00:28:33.029 --> 00:28:33.039 align:start position:0% Codeex created by OpenAI is officially a 00:28:33.039 --> 00:28:35.750 align:start position:0% Codeex created by OpenAI is officially a cloud-based<00:28:34.000> AI<00:28:34.640> software<00:28:35.120> engineering 00:28:35.750 --> 00:28:35.760 align:start position:0% cloud-based AI software engineering 00:28:35.760 --> 00:28:37.430 align:start position:0% cloud-based AI software engineering agent. 00:28:37.430 --> 00:28:37.440 align:start position:0% agent. 00:28:37.440 --> 00:28:40.070 align:start position:0% agent. It<00:28:37.679> remarkably<00:28:38.399> handles<00:28:38.880> incredibly<00:28:39.600> complex 00:28:40.070 --> 00:28:40.080 align:start position:0% It remarkably handles incredibly complex 00:28:40.080 --> 00:28:42.630 align:start position:0% It remarkably handles incredibly complex programming<00:28:40.559> tasks,<00:28:41.440> consistently<00:28:42.159> fixes 00:28:42.630 --> 00:28:42.640 align:start position:0% programming tasks, consistently fixes 00:28:42.640 --> 00:28:44.950 align:start position:0% programming tasks, consistently fixes highly<00:28:43.039> stubborn<00:28:43.520> software<00:28:43.840> bugs,<00:28:44.640> and 00:28:44.950 --> 00:28:44.960 align:start position:0% highly stubborn software bugs, and 00:28:44.960 --> 00:28:47.350 align:start position:0% highly stubborn software bugs, and smoothly<00:28:45.520> proposes<00:28:46.159> absolutely<00:28:46.880> all<00:28:47.120> the 00:28:47.350 --> 00:28:47.360 align:start position:0% smoothly proposes absolutely all the 00:28:47.360 --> 00:28:49.350 align:start position:0% smoothly proposes absolutely all the necessary<00:28:47.919> fundamental<00:28:48.559> work<00:28:48.799> changes<00:28:49.200> for 00:28:49.350 --> 00:28:49.360 align:start position:0% necessary fundamental work changes for 00:28:49.360 --> 00:28:51.350 align:start position:0% necessary fundamental work changes for your<00:28:49.600> review. 00:28:51.350 --> 00:28:51.360 align:start position:0% your review. 00:28:51.360 --> 00:28:53.110 align:start position:0% your review. This<00:28:51.760> essentially<00:28:52.080> means<00:28:52.320> that<00:28:52.559> the<00:28:52.799> powerful 00:28:53.110 --> 00:28:53.120 align:start position:0% This essentially means that the powerful 00:28:53.120 --> 00:28:56.070 align:start position:0% This essentially means that the powerful tool<00:28:53.440> we<00:28:53.679> are<00:28:53.840> actively<00:28:54.399> utilizing<00:28:54.880> right<00:28:55.200> now 00:28:56.070 --> 00:28:56.080 align:start position:0% tool we are actively utilizing right now 00:28:56.080 --> 00:28:58.470 align:start position:0% tool we are actively utilizing right now acts<00:28:56.480> almost<00:28:56.880> exactly<00:28:57.360> like<00:28:57.679> a<00:28:58.000> completely 00:28:58.470 --> 00:28:58.480 align:start position:0% acts almost exactly like a completely 00:28:58.480 --> 00:29:01.350 align:start position:0% acts almost exactly like a completely standalone,<00:28:59.520> fully<00:29:00.000> robust<00:29:00.640> cloud-based 00:29:01.350 --> 00:29:01.360 align:start position:0% standalone, fully robust cloud-based 00:29:01.360 --> 00:29:04.310 align:start position:0% standalone, fully robust cloud-based development<00:29:01.840> environment<00:29:02.399> in<00:29:02.640> itself. 00:29:04.310 --> 00:29:04.320 align:start position:0% development environment in itself. 00:29:04.320 --> 00:29:06.470 align:start position:0% development environment in itself. I<00:29:04.640> strongly<00:29:05.039> suggest<00:29:05.440> that<00:29:05.600> we<00:29:05.840> consistently 00:29:06.470 --> 00:29:06.480 align:start position:0% I strongly suggest that we consistently 00:29:06.480 --> 00:29:08.470 align:start position:0% I strongly suggest that we consistently use<00:29:06.720> this<00:29:07.039> incredible<00:29:07.600> tool<00:29:08.159> to 00:29:08.470 --> 00:29:08.480 align:start position:0% use this incredible tool to 00:29:08.480 --> 00:29:10.950 align:start position:0% use this incredible tool to intentionally<00:29:09.120> make<00:29:09.360> a<00:29:09.600> highly<00:29:10.080> secure, 00:29:10.950 --> 00:29:10.960 align:start position:0% intentionally make a highly secure, 00:29:10.960 --> 00:29:14.070 align:start position:0% intentionally make a highly secure, deeply<00:29:11.440> isolated<00:29:12.080> remote<00:29:12.480> workspace.<00:29:13.919> There 00:29:14.070 --> 00:29:14.080 align:start position:0% deeply isolated remote workspace. There 00:29:14.080 --> 00:29:15.830 align:start position:0% deeply isolated remote workspace. There are<00:29:14.320> honestly<00:29:14.720> quite<00:29:14.960> a<00:29:15.120> lot<00:29:15.200> of<00:29:15.440> highly 00:29:15.830 --> 00:29:15.840 align:start position:0% are honestly quite a lot of highly 00:29:15.840 --> 00:29:17.510 align:start position:0% are honestly quite a lot of highly technical<00:29:16.240> backend<00:29:16.720> things<00:29:17.039> actively 00:29:17.510 --> 00:29:17.520 align:start position:0% technical backend things actively 00:29:17.520 --> 00:29:20.230 align:start position:0% technical backend things actively running<00:29:17.840> here.<00:29:19.039> I<00:29:19.279> will<00:29:19.440> quickly<00:29:19.760> hop<00:29:20.000> back 00:29:20.230 --> 00:29:20.240 align:start position:0% running here. I will quickly hop back 00:29:20.240 --> 00:29:22.630 align:start position:0% running here. I will quickly hop back and<00:29:20.399> change<00:29:20.640> the<00:29:20.799> UI<00:29:21.200> font<00:29:21.520> size<00:29:21.760> once<00:29:22.080> again 00:29:22.630 --> 00:29:22.640 align:start position:0% and change the UI font size once again 00:29:22.640 --> 00:29:24.630 align:start position:0% and change the UI font size once again because<00:29:22.880> it<00:29:23.200> simply<00:29:23.520> does<00:29:23.760> not<00:29:23.919> look<00:29:24.240> visually 00:29:24.630 --> 00:29:24.640 align:start position:0% because it simply does not look visually 00:29:24.640 --> 00:29:26.789 align:start position:0% because it simply does not look visually right<00:29:24.880> on<00:29:25.120> this<00:29:25.279> display. 00:29:26.789 --> 00:29:26.799 align:start position:0% right on this display. 00:29:26.799 --> 00:29:28.549 align:start position:0% right on this display. I<00:29:27.039> will<00:29:27.200> purposefully<00:29:27.760> make<00:29:28.000> it<00:29:28.159> just<00:29:28.320> a 00:29:28.549 --> 00:29:28.559 align:start position:0% I will purposefully make it just a 00:29:28.559 --> 00:29:30.470 align:start position:0% I will purposefully make it just a little<00:29:28.720> bit<00:29:28.960> bigger<00:29:29.520> strictly<00:29:29.919> for<00:29:30.159> the<00:29:30.320> sake 00:29:30.470 --> 00:29:30.480 align:start position:0% little bit bigger strictly for the sake 00:29:30.480 --> 00:29:33.590 align:start position:0% little bit bigger strictly for the sake of<00:29:30.559> our<00:29:30.799> video<00:29:31.200> course<00:29:31.600> clarity. 00:29:33.590 --> 00:29:33.600 align:start position:0% of our video course clarity. 00:29:33.600 --> 00:29:35.669 align:start position:0% of our video course clarity. Now<00:29:33.919> we<00:29:34.159> simply<00:29:34.480> go<00:29:34.720> straight<00:29:34.960> back<00:29:35.200> into<00:29:35.440> our 00:29:35.669 --> 00:29:35.679 align:start position:0% Now we simply go straight back into our 00:29:35.679 --> 00:29:38.149 align:start position:0% Now we simply go straight back into our main<00:29:35.919> codeex<00:29:36.480> application. 00:29:38.149 --> 00:29:38.159 align:start position:0% main codeex application. 00:29:38.159 --> 00:29:40.230 align:start position:0% main codeex application. Everything<00:29:38.640> visually<00:29:39.120> looks<00:29:39.520> exceptionally 00:29:40.230 --> 00:29:40.240 align:start position:0% Everything visually looks exceptionally 00:29:40.240 --> 00:29:43.110 align:start position:0% Everything visually looks exceptionally good.<00:29:40.480> Now<00:29:41.679> we<00:29:41.919> have<00:29:42.000> our<00:29:42.240> advanced<00:29:42.720> reasoning 00:29:43.110 --> 00:29:43.120 align:start position:0% good. Now we have our advanced reasoning 00:29:43.120 --> 00:29:45.190 align:start position:0% good. Now we have our advanced reasoning engine<00:29:43.440> and<00:29:43.760> other<00:29:44.000> vital<00:29:44.399> backend<00:29:44.880> things 00:29:45.190 --> 00:29:45.200 align:start position:0% engine and other vital backend things 00:29:45.200 --> 00:29:47.909 align:start position:0% engine and other vital backend things running.<00:29:46.399> We<00:29:46.640> will<00:29:46.799> take<00:29:47.039> a<00:29:47.279> complete 00:29:47.909 --> 00:29:47.919 align:start position:0% running. We will take a complete 00:29:47.919 --> 00:29:51.350 align:start position:0% running. We will take a complete comprehensive<00:29:48.559> look<00:29:48.720> at<00:29:48.880> this.<00:29:49.120> Nextly 00:29:51.350 --> 00:29:51.360 align:start position:0% comprehensive look at this. Nextly 00:29:51.360 --> 00:29:53.430 align:start position:0% comprehensive look at this. Nextly shows<00:29:51.600> how<00:29:51.840> we<00:29:52.000> put<00:29:52.240> things<00:29:52.480> into<00:29:52.720> a<00:29:52.960> complete 00:29:53.430 --> 00:29:53.440 align:start position:0% shows how we put things into a complete 00:29:53.440 --> 00:29:57.750 align:start position:0% shows how we put things into a complete cloud-based<00:29:54.080> setup. 00:29:57.750 --> 00:29:57.760 align:start position:0% 00:29:57.760 --> 00:30:00.789 align:start position:0% Now<00:29:58.399> moving<00:29:58.880> smoothly<00:29:59.360> forward,<00:30:00.240> our<00:30:00.480> very 00:30:00.789 --> 00:30:00.799 align:start position:0% Now moving smoothly forward, our very 00:30:00.799 --> 00:30:03.430 align:start position:0% Now moving smoothly forward, our very next<00:30:01.120> crucial<00:30:01.600> task<00:30:02.000> is<00:30:02.240> to<00:30:02.480> securely<00:30:03.039> connect 00:30:03.430 --> 00:30:03.440 align:start position:0% next crucial task is to securely connect 00:30:03.440 --> 00:30:06.950 align:start position:0% next crucial task is to securely connect our<00:30:03.760> remote<00:30:04.159> GitHub<00:30:04.640> repositories<00:30:05.279> directly. 00:30:06.950 --> 00:30:06.960 align:start position:0% our remote GitHub repositories directly. 00:30:06.960 --> 00:30:09.430 align:start position:0% our remote GitHub repositories directly. We<00:30:07.279> absolutely<00:30:08.000> need<00:30:08.240> to<00:30:08.399> establish<00:30:08.880> a<00:30:09.120> solid 00:30:09.430 --> 00:30:09.440 align:start position:0% We absolutely need to establish a solid 00:30:09.440 --> 00:30:11.350 align:start position:0% We absolutely need to establish a solid link<00:30:09.760> to<00:30:09.919> our<00:30:10.080> GitHub<00:30:10.559> account<00:30:10.880> directly 00:30:11.350 --> 00:30:11.360 align:start position:0% link to our GitHub account directly 00:30:11.360 --> 00:30:14.470 align:start position:0% link to our GitHub account directly within<00:30:11.679> the<00:30:11.919> main<00:30:12.159> codec<00:30:12.720> system 00:30:14.470 --> 00:30:14.480 align:start position:0% within the main codec system 00:30:14.480 --> 00:30:17.190 align:start position:0% within the main codec system inside<00:30:14.880> our<00:30:15.120> primary<00:30:15.520> GitHub<00:30:16.080> platform.<00:30:16.960> A 00:30:17.190 --> 00:30:17.200 align:start position:0% inside our primary GitHub platform. A 00:30:17.200 --> 00:30:18.789 align:start position:0% inside our primary GitHub platform. A tremendous<00:30:17.760> amount<00:30:18.000> of<00:30:18.240> distinct 00:30:18.789 --> 00:30:18.799 align:start position:0% tremendous amount of distinct 00:30:18.799 --> 00:30:20.950 align:start position:0% tremendous amount of distinct configurable<00:30:19.520> options<00:30:19.919> are<00:30:20.159> always<00:30:20.559> readily 00:30:20.950 --> 00:30:20.960 align:start position:0% configurable options are always readily 00:30:20.960 --> 00:30:22.630 align:start position:0% configurable options are always readily available. 00:30:22.630 --> 00:30:22.640 align:start position:0% available. 00:30:22.640 --> 00:30:24.710 align:start position:0% available. You<00:30:22.880> can<00:30:23.039> clearly<00:30:23.440> see<00:30:23.600> the<00:30:23.840> active<00:30:24.240> status 00:30:24.710 --> 00:30:24.720 align:start position:0% You can clearly see the active status 00:30:24.720 --> 00:30:26.389 align:start position:0% You can clearly see the active status regarding<00:30:25.120> the<00:30:25.360> connection<00:30:25.679> with<00:30:25.840> GitHub 00:30:26.389 --> 00:30:26.399 align:start position:0% regarding the connection with GitHub 00:30:26.399 --> 00:30:29.029 align:start position:0% regarding the connection with GitHub right<00:30:26.720> here<00:30:26.880> on<00:30:27.039> the<00:30:27.200> interface. 00:30:29.029 --> 00:30:29.039 align:start position:0% right here on the interface. 00:30:29.039 --> 00:30:31.269 align:start position:0% right here on the interface. If<00:30:29.279> I<00:30:29.520> cautiously<00:30:30.159> go<00:30:30.320> over<00:30:30.559> to<00:30:30.720> the<00:30:30.880> main 00:30:31.269 --> 00:30:31.279 align:start position:0% If I cautiously go over to the main 00:30:31.279 --> 00:30:33.669 align:start position:0% If I cautiously go over to the main settings<00:30:31.679> panel,<00:30:32.640> specifically<00:30:33.360> looking 00:30:33.669 --> 00:30:33.679 align:start position:0% settings panel, specifically looking 00:30:33.679 --> 00:30:36.310 align:start position:0% settings panel, specifically looking closely<00:30:34.080> in<00:30:34.240> the<00:30:34.480> connections<00:30:34.880> option<00:30:35.279> area, 00:30:36.310 --> 00:30:36.320 align:start position:0% closely in the connections option area, 00:30:36.320 --> 00:30:38.789 align:start position:0% closely in the connections option area, there<00:30:36.480> is<00:30:36.720> currently<00:30:37.279> absolutely<00:30:38.000> no<00:30:38.399> active 00:30:38.789 --> 00:30:38.799 align:start position:0% there is currently absolutely no active 00:30:38.799 --> 00:30:41.029 align:start position:0% there is currently absolutely no active connection<00:30:39.200> established. 00:30:41.029 --> 00:30:41.039 align:start position:0% connection established. 00:30:41.039 --> 00:30:43.750 align:start position:0% connection established. The<00:30:41.360> standard<00:30:41.919> SSH<00:30:42.640> and<00:30:43.039> secure<00:30:43.440> git 00:30:43.750 --> 00:30:43.760 align:start position:0% The standard SSH and secure git 00:30:43.760 --> 00:30:46.070 align:start position:0% The standard SSH and secure git credential<00:30:44.240> options<00:30:45.120> similarly<00:30:45.679> show<00:30:45.840> that 00:30:46.070 --> 00:30:46.080 align:start position:0% credential options similarly show that 00:30:46.080 --> 00:30:47.990 align:start position:0% credential options similarly show that there<00:30:46.240> are<00:30:46.399> simply<00:30:46.720> no<00:30:47.120> active<00:30:47.520> connections 00:30:47.990 --> 00:30:48.000 align:start position:0% there are simply no active connections 00:30:48.000 --> 00:30:49.669 align:start position:0% there are simply no active connections present. 00:30:49.669 --> 00:30:49.679 align:start position:0% present. 00:30:49.679 --> 00:30:52.149 align:start position:0% present. Furthermore,<00:30:50.720> down<00:30:50.960> in<00:30:51.200> the<00:30:51.360> remote<00:30:51.760> servers 00:30:52.149 --> 00:30:52.159 align:start position:0% Furthermore, down in the remote servers 00:30:52.159 --> 00:30:54.310 align:start position:0% Furthermore, down in the remote servers and<00:30:52.399> local<00:30:52.799> browser<00:30:53.200> tab,<00:30:53.919> there<00:30:54.159> is 00:30:54.310 --> 00:30:54.320 align:start position:0% and local browser tab, there is 00:30:54.320 --> 00:30:57.029 align:start position:0% and local browser tab, there is similarly<00:30:54.880> no<00:30:55.200> connection. 00:30:57.029 --> 00:30:57.039 align:start position:0% similarly no connection. 00:30:57.039 --> 00:30:59.430 align:start position:0% similarly no connection. In<00:30:57.279> the<00:30:57.520> computer<00:30:57.840> use<00:30:58.159> section,<00:30:59.039> we<00:30:59.279> can 00:30:59.430 --> 00:30:59.440 align:start position:0% In the computer use section, we can 00:30:59.440 --> 00:31:01.430 align:start position:0% In the computer use section, we can alternatively<00:31:00.159> use<00:31:00.399> the<00:31:00.640> Google<00:31:01.039> Chrome 00:31:01.430 --> 00:31:01.440 align:start position:0% alternatively use the Google Chrome 00:31:01.440 --> 00:31:04.070 align:start position:0% alternatively use the Google Chrome browser<00:31:01.919> extension. 00:31:04.070 --> 00:31:04.080 align:start position:0% browser extension. 00:31:04.080 --> 00:31:06.230 align:start position:0% browser extension. So,<00:31:04.480> our<00:31:04.799> primary<00:31:05.200> GitHub<00:31:05.679> repository 00:31:06.230 --> 00:31:06.240 align:start position:0% So, our primary GitHub repository 00:31:06.240 --> 00:31:08.389 align:start position:0% So, our primary GitHub repository profile<00:31:06.720> is<00:31:07.039> clearly<00:31:07.520> not<00:31:07.840> effectively 00:31:08.389 --> 00:31:08.399 align:start position:0% profile is clearly not effectively 00:31:08.399 --> 00:31:11.590 align:start position:0% profile is clearly not effectively connected<00:31:08.720> to<00:31:08.880> the<00:31:09.120> system<00:31:09.440> just<00:31:09.760> yet.<00:31:11.200> I<00:31:11.440> will 00:31:11.590 --> 00:31:11.600 align:start position:0% connected to the system just yet. I will 00:31:11.600 --> 00:31:13.830 align:start position:0% connected to the system just yet. I will intentionally<00:31:12.399> just<00:31:12.640> type<00:31:12.960> out<00:31:13.120> the<00:31:13.360> specific 00:31:13.830 --> 00:31:13.840 align:start position:0% intentionally just type out the specific 00:31:13.840 --> 00:31:17.110 align:start position:0% intentionally just type out the specific query.<00:31:15.120> Is<00:31:15.440> GitHub<00:31:16.000> firmly<00:31:16.480> connected<00:31:16.880> to 00:31:17.110 --> 00:31:17.120 align:start position:0% query. Is GitHub firmly connected to 00:31:17.120 --> 00:31:19.750 align:start position:0% query. Is GitHub firmly connected to codeex<00:31:17.679> right<00:31:17.919> now?<00:31:18.559> to<00:31:18.880> quickly<00:31:19.200> see<00:31:19.360> if<00:31:19.520> we 00:31:19.750 --> 00:31:19.760 align:start position:0% codeex right now? to quickly see if we 00:31:19.760 --> 00:31:21.510 align:start position:0% codeex right now? to quickly see if we actually<00:31:20.080> get<00:31:20.240> a<00:31:20.399> reassuring<00:31:21.120> green 00:31:21.510 --> 00:31:21.520 align:start position:0% actually get a reassuring green 00:31:21.520 --> 00:31:23.909 align:start position:0% actually get a reassuring green verification<00:31:22.240> tick. 00:31:23.909 --> 00:31:23.919 align:start position:0% verification tick. 00:31:23.919 --> 00:31:26.310 align:start position:0% verification tick. This<00:31:24.240> built-in<00:31:24.720> diagnostic<00:31:25.360> tool<00:31:26.000> will 00:31:26.310 --> 00:31:26.320 align:start position:0% This built-in diagnostic tool will 00:31:26.320 --> 00:31:28.870 align:start position:0% This built-in diagnostic tool will thoroughly<00:31:26.720> check<00:31:27.039> the<00:31:27.200> backend<00:31:27.760> systems<00:31:28.559> and 00:31:28.870 --> 00:31:28.880 align:start position:0% thoroughly check the backend systems and 00:31:28.880 --> 00:31:31.029 align:start position:0% thoroughly check the backend systems and explicitly<00:31:29.520> tell<00:31:29.760> us<00:31:29.919> if<00:31:30.080> our<00:31:30.320> GitHub<00:31:30.720> account 00:31:31.029 --> 00:31:31.039 align:start position:0% explicitly tell us if our GitHub account 00:31:31.039 --> 00:31:34.230 align:start position:0% explicitly tell us if our GitHub account is<00:31:31.279> successfully<00:31:31.919> connected<00:31:32.399> or<00:31:32.720> not. 00:31:34.230 --> 00:31:34.240 align:start position:0% is successfully connected or not. 00:31:34.240 --> 00:31:36.549 align:start position:0% is successfully connected or not. Simultaneously,<00:31:35.600> I<00:31:35.840> will<00:31:36.000> efficiently 00:31:36.549 --> 00:31:36.559 align:start position:0% Simultaneously, I will efficiently 00:31:36.559 --> 00:31:39.350 align:start position:0% Simultaneously, I will efficiently search<00:31:36.880> for<00:31:37.039> the<00:31:37.200> precise<00:31:37.679> phrasing<00:31:38.799> GitHub 00:31:39.350 --> 00:31:39.360 align:start position:0% search for the precise phrasing GitHub 00:31:39.360 --> 00:31:42.310 align:start position:0% search for the precise phrasing GitHub and<00:31:39.679> official<00:31:40.159> codeex<00:31:40.640> integration<00:31:41.760> securely 00:31:42.310 --> 00:31:42.320 align:start position:0% and official codeex integration securely 00:31:42.320 --> 00:31:44.310 align:start position:0% and official codeex integration securely online. 00:31:44.310 --> 00:31:44.320 align:start position:0% online. 00:31:44.320 --> 00:31:46.870 align:start position:0% online. This<00:31:44.640> highly<00:31:45.120> powerful<00:31:45.600> system<00:31:46.000> connection 00:31:46.870 --> 00:31:46.880 align:start position:0% This highly powerful system connection 00:31:46.880 --> 00:31:49.110 align:start position:0% This highly powerful system connection can<00:31:47.120> miraculously<00:31:47.919> be<00:31:48.159> added<00:31:48.480> directly 00:31:49.110 --> 00:31:49.120 align:start position:0% can miraculously be added directly 00:31:49.120 --> 00:31:52.070 align:start position:0% can miraculously be added directly without<00:31:49.519> any<00:31:49.840> significant<00:31:50.399> friction.<00:31:51.760> It 00:31:52.070 --> 00:31:52.080 align:start position:0% without any significant friction. It 00:31:52.080 --> 00:31:54.310 align:start position:0% without any significant friction. It prominently<00:31:52.640> includes<00:31:53.279> highly<00:31:53.679> advanced 00:31:54.310 --> 00:31:54.320 align:start position:0% prominently includes highly advanced 00:31:54.320 --> 00:31:57.110 align:start position:0% prominently includes highly advanced automated<00:31:54.960> pull<00:31:55.279> request<00:31:55.679> code<00:31:56.000> reviews,<00:31:56.880> a 00:31:57.110 --> 00:31:57.120 align:start position:0% automated pull request code reviews, a 00:31:57.120 --> 00:32:00.310 align:start position:0% automated pull request code reviews, a dedicated<00:31:57.760> co-pilot<00:31:58.399> AI<00:31:58.799> coding<00:31:59.200> agent,<00:32:00.080> and 00:32:00.310 --> 00:32:00.320 align:start position:0% dedicated co-pilot AI coding agent, and 00:32:00.320 --> 00:32:02.470 align:start position:0% dedicated co-pilot AI coding agent, and deeply<00:32:00.880> integrated<00:32:01.519> GitHub<00:32:02.000> workflow 00:32:02.470 --> 00:32:02.480 align:start position:0% deeply integrated GitHub workflow 00:32:02.480 --> 00:32:04.070 align:start position:0% deeply integrated GitHub workflow actions. 00:32:04.070 --> 00:32:04.080 align:start position:0% actions. 00:32:04.080 --> 00:32:05.909 align:start position:0% actions. We<00:32:04.320> will<00:32:04.559> comprehensively<00:32:05.360> discuss 00:32:05.909 --> 00:32:05.919 align:start position:0% We will comprehensively discuss 00:32:05.919 --> 00:32:07.909 align:start position:0% We will comprehensively discuss absolutely<00:32:06.640> all<00:32:06.880> of<00:32:07.039> these<00:32:07.360> incredible 00:32:07.909 --> 00:32:07.919 align:start position:0% absolutely all of these incredible 00:32:07.919 --> 00:32:09.909 align:start position:0% absolutely all of these incredible back-end<00:32:08.399> setup<00:32:08.720> options<00:32:09.120> in<00:32:09.440> extreme 00:32:09.909 --> 00:32:09.919 align:start position:0% back-end setup options in extreme 00:32:09.919 --> 00:32:11.509 align:start position:0% back-end setup options in extreme detail. 00:32:11.509 --> 00:32:11.519 align:start position:0% detail. 00:32:11.519 --> 00:32:14.230 align:start position:0% detail. The<00:32:11.840> diagnostic<00:32:12.480> system<00:32:12.880> now<00:32:13.200> clearly<00:32:13.600> shows 00:32:14.230 --> 00:32:14.240 align:start position:0% The diagnostic system now clearly shows 00:32:14.240 --> 00:32:16.149 align:start position:0% The diagnostic system now clearly shows that<00:32:14.399> the<00:32:14.720> official<00:32:15.120> GitHub<00:32:15.600> integration 00:32:16.149 --> 00:32:16.159 align:start position:0% that the official GitHub integration 00:32:16.159 --> 00:32:18.470 align:start position:0% that the official GitHub integration plugin<00:32:16.880> is<00:32:17.200> indeed<00:32:17.600> fully<00:32:17.919> available 00:32:18.470 --> 00:32:18.480 align:start position:0% plugin is indeed fully available 00:32:18.480 --> 00:32:20.470 align:start position:0% plugin is indeed fully available directly<00:32:18.960> within<00:32:19.279> the<00:32:19.440> primary<00:32:19.919> codeex 00:32:20.470 --> 00:32:20.480 align:start position:0% directly within the primary codeex 00:32:20.480 --> 00:32:23.590 align:start position:0% directly within the primary codeex plug-in<00:32:20.880> section.<00:32:21.600> But<00:32:22.159> unfortunately,<00:32:23.360> this 00:32:23.590 --> 00:32:23.600 align:start position:0% plug-in section. But unfortunately, this 00:32:23.600 --> 00:32:26.149 align:start position:0% plug-in section. But unfortunately, this specific<00:32:24.159> local<00:32:24.559> workspace<00:32:25.120> folder<00:32:25.840> is 00:32:26.149 --> 00:32:26.159 align:start position:0% specific local workspace folder is 00:32:26.159 --> 00:32:28.230 align:start position:0% specific local workspace folder is actually<00:32:26.559> not<00:32:26.799> initialized<00:32:27.360> as<00:32:27.519> a<00:32:27.679> valid<00:32:27.919> Git 00:32:28.230 --> 00:32:28.240 align:start position:0% actually not initialized as a valid Git 00:32:28.240 --> 00:32:31.110 align:start position:0% actually not initialized as a valid Git repository<00:32:28.799> right<00:32:29.039> now.<00:32:30.159> A<00:32:30.399> brand<00:32:30.559> new<00:32:30.799> Git 00:32:31.110 --> 00:32:31.120 align:start position:0% repository right now. A brand new Git 00:32:31.120 --> 00:32:32.950 align:start position:0% repository right now. A brand new Git tracking<00:32:31.440> folder<00:32:31.840> is<00:32:32.000> quickly<00:32:32.399> being<00:32:32.640> created 00:32:32.950 --> 00:32:32.960 align:start position:0% tracking folder is quickly being created 00:32:32.960 --> 00:32:34.710 align:start position:0% tracking folder is quickly being created in<00:32:33.200> the<00:32:33.279> background. 00:32:34.710 --> 00:32:34.720 align:start position:0% in the background. 00:32:34.720 --> 00:32:36.950 align:start position:0% in the background. Now,<00:32:35.440> if<00:32:35.679> we<00:32:35.840> explicitly<00:32:36.480> click<00:32:36.720> the 00:32:36.950 --> 00:32:36.960 align:start position:0% Now, if we explicitly click the 00:32:36.960 --> 00:32:38.630 align:start position:0% Now, if we explicitly click the prominent<00:32:37.440> plus<00:32:37.679> button<00:32:38.000> on<00:32:38.240> the<00:32:38.399> user 00:32:38.630 --> 00:32:38.640 align:start position:0% prominent plus button on the user 00:32:38.640 --> 00:32:41.269 align:start position:0% prominent plus button on the user interface,<00:32:39.600> we<00:32:39.840> can<00:32:40.000> clearly<00:32:40.320> see<00:32:40.480> the<00:32:40.640> GitHub 00:32:41.269 --> 00:32:41.279 align:start position:0% interface, we can clearly see the GitHub 00:32:41.279 --> 00:32:43.190 align:start position:0% interface, we can clearly see the GitHub icon<00:32:41.600> safely<00:32:42.080> listed<00:32:42.399> in<00:32:42.559> the<00:32:42.720> available 00:32:43.190 --> 00:32:43.200 align:start position:0% icon safely listed in the available 00:32:43.200 --> 00:32:45.350 align:start position:0% icon safely listed in the available plugins<00:32:43.679> directory. 00:32:45.350 --> 00:32:45.360 align:start position:0% plugins directory. 00:32:45.360 --> 00:32:47.669 align:start position:0% plugins directory. But<00:32:45.519> we<00:32:45.760> critically<00:32:46.240> want<00:32:46.480> to<00:32:46.640> verify<00:32:47.200> exactly 00:32:47.669 --> 00:32:47.679 align:start position:0% But we critically want to verify exactly 00:32:47.679 --> 00:32:50.310 align:start position:0% But we critically want to verify exactly which<00:32:48.080> specific<00:32:48.559> user<00:32:48.960> account<00:32:49.600> is<00:32:49.919> currently 00:32:50.310 --> 00:32:50.320 align:start position:0% which specific user account is currently 00:32:50.320 --> 00:32:52.549 align:start position:0% which specific user account is currently connected<00:32:50.799> directly<00:32:51.279> to<00:32:51.519> our<00:32:51.679> active<00:32:52.080> GitHub 00:32:52.549 --> 00:32:52.559 align:start position:0% connected directly to our active GitHub 00:32:52.559 --> 00:32:55.350 align:start position:0% connected directly to our active GitHub plug-in<00:32:52.960> extension.<00:32:54.399> We<00:32:54.640> currently<00:32:55.039> cannot 00:32:55.350 --> 00:32:55.360 align:start position:0% plug-in extension. We currently cannot 00:32:55.360 --> 00:32:58.310 align:start position:0% plug-in extension. We currently cannot seem<00:32:55.600> to<00:32:55.760> find<00:32:56.000> our<00:32:56.240> primary<00:32:56.640> GitHub<00:32:57.200> profile. 00:32:58.310 --> 00:32:58.320 align:start position:0% seem to find our primary GitHub profile. 00:32:58.320 --> 00:33:00.470 align:start position:0% seem to find our primary GitHub profile. So,<00:32:58.559> we<00:32:58.799> will<00:32:58.960> manually<00:32:59.440> initiate<00:32:59.919> a<00:33:00.159> deep 00:33:00.470 --> 00:33:00.480 align:start position:0% So, we will manually initiate a deep 00:33:00.480 --> 00:33:02.470 align:start position:0% So, we will manually initiate a deep search<00:33:00.799> for<00:33:00.960> it. 00:33:02.470 --> 00:33:02.480 align:start position:0% search for it. 00:33:02.480 --> 00:33:04.630 align:start position:0% search for it. When<00:33:02.720> we<00:33:02.880> effectively<00:33:03.519> run<00:33:03.679> the<00:33:03.919> search,<00:33:04.399> the 00:33:04.630 --> 00:33:04.640 align:start position:0% When we effectively run the search, the 00:33:04.640 --> 00:33:06.950 align:start position:0% When we effectively run the search, the official<00:33:05.120> GitHub<00:33:05.679> authentication<00:33:06.480> app 00:33:06.950 --> 00:33:06.960 align:start position:0% official GitHub authentication app 00:33:06.960 --> 00:33:08.950 align:start position:0% official GitHub authentication app finally<00:33:07.440> appears. 00:33:08.950 --> 00:33:08.960 align:start position:0% finally appears. 00:33:08.960 --> 00:33:11.269 align:start position:0% finally appears. The<00:33:09.279> application<00:33:10.000> safely<00:33:10.480> requests<00:33:10.960> broad 00:33:11.269 --> 00:33:11.279 align:start position:0% The application safely requests broad 00:33:11.279 --> 00:33:12.950 align:start position:0% The application safely requests broad permission<00:33:11.760> to<00:33:12.000> actively<00:33:12.480> access 00:33:12.950 --> 00:33:12.960 align:start position:0% permission to actively access 00:33:12.960 --> 00:33:15.750 align:start position:0% permission to actively access repositories,<00:33:14.000> track<00:33:14.320> software<00:33:14.799> issues,<00:33:15.440> and 00:33:15.750 --> 00:33:15.760 align:start position:0% repositories, track software issues, and 00:33:15.760 --> 00:33:18.789 align:start position:0% repositories, track software issues, and manage<00:33:16.080> pull<00:33:16.399> requests.<00:33:17.840> But<00:33:18.000> we<00:33:18.240> have<00:33:18.399> simply 00:33:18.789 --> 00:33:18.799 align:start position:0% manage pull requests. But we have simply 00:33:18.799 --> 00:33:21.909 align:start position:0% manage pull requests. But we have simply not<00:33:19.039> fully<00:33:19.360> connected<00:33:19.760> it<00:33:19.919> just<00:33:20.159> yet.<00:33:21.360> So<00:33:21.679> we 00:33:21.909 --> 00:33:21.919 align:start position:0% not fully connected it just yet. So we 00:33:21.919 --> 00:33:23.990 align:start position:0% not fully connected it just yet. So we will<00:33:22.080> proceed<00:33:22.399> to<00:33:22.559> log<00:33:22.880> securely<00:33:23.440> into<00:33:23.760> our 00:33:23.990 --> 00:33:24.000 align:start position:0% will proceed to log securely into our 00:33:24.000 --> 00:33:26.630 align:start position:0% will proceed to log securely into our main<00:33:24.240> GitHub<00:33:24.799> account.<00:33:26.080> This<00:33:26.240> is<00:33:26.399> our 00:33:26.630 --> 00:33:26.640 align:start position:0% main GitHub account. This is our 00:33:26.640 --> 00:33:29.029 align:start position:0% main GitHub account. This is our dedicated<00:33:27.360> primary<00:33:27.840> account<00:33:28.320> explicitly 00:33:29.029 --> 00:33:29.039 align:start position:0% dedicated primary account explicitly 00:33:29.039 --> 00:33:32.070 align:start position:0% dedicated primary account explicitly named<00:33:29.679> Metabrains-dell. 00:33:32.070 --> 00:33:32.080 align:start position:0% named Metabrains-dell. 00:33:32.080 --> 00:33:35.029 align:start position:0% named Metabrains-dell. It<00:33:32.399> undeniably<00:33:33.200> has<00:33:33.440> many<00:33:33.760> repositories<00:33:34.799> and 00:33:35.029 --> 00:33:35.039 align:start position:0% It undeniably has many repositories and 00:33:35.039 --> 00:33:37.990 align:start position:0% It undeniably has many repositories and we<00:33:35.200> have<00:33:35.360> done<00:33:35.519> a<00:33:35.760> lot<00:33:35.840> of<00:33:36.000> work<00:33:36.240> here.<00:33:37.600> We<00:33:37.840> will 00:33:37.990 --> 00:33:38.000 align:start position:0% we have done a lot of work here. We will 00:33:38.000 --> 00:33:40.230 align:start position:0% we have done a lot of work here. We will now<00:33:38.240> meticulously<00:33:39.039> connect<00:33:39.440> this<00:33:39.760> specific 00:33:40.230 --> 00:33:40.240 align:start position:0% now meticulously connect this specific 00:33:40.240 --> 00:33:42.710 align:start position:0% now meticulously connect this specific GitHub<00:33:40.799> account<00:33:41.360> directly<00:33:41.840> to<00:33:42.000> our<00:33:42.240> active 00:33:42.710 --> 00:33:42.720 align:start position:0% GitHub account directly to our active 00:33:42.720 --> 00:33:45.350 align:start position:0% GitHub account directly to our active codec<00:33:43.200> system<00:33:43.600> workspace. 00:33:45.350 --> 00:33:45.360 align:start position:0% codec system workspace. 00:33:45.360 --> 00:33:47.190 align:start position:0% codec system workspace. When<00:33:45.600> I<00:33:45.760> confidently<00:33:46.320> click<00:33:46.640> the<00:33:46.880> connect 00:33:47.190 --> 00:33:47.200 align:start position:0% When I confidently click the connect 00:33:47.200 --> 00:33:49.909 align:start position:0% When I confidently click the connect button,<00:33:48.000> it<00:33:48.320> explicitly<00:33:48.960> asks<00:33:49.279> for<00:33:49.519> final 00:33:49.909 --> 00:33:49.919 align:start position:0% button, it explicitly asks for final 00:33:49.919 --> 00:33:52.230 align:start position:0% button, it explicitly asks for final permission<00:33:50.320> to<00:33:50.640> securely<00:33:51.200> connect<00:33:51.519> to<00:33:51.679> GitHub 00:33:52.230 --> 00:33:52.240 align:start position:0% permission to securely connect to GitHub 00:33:52.240 --> 00:33:53.750 align:start position:0% permission to securely connect to GitHub servers. 00:33:53.750 --> 00:33:53.760 align:start position:0% servers. 00:33:53.760 --> 00:33:56.549 align:start position:0% servers. It<00:33:54.000> safely<00:33:54.480> allows<00:33:54.799> the<00:33:55.039> underlying<00:33:55.600> chat<00:33:55.919> GPT 00:33:56.549 --> 00:33:56.559 align:start position:0% It safely allows the underlying chat GPT 00:33:56.559 --> 00:33:58.710 align:start position:0% It safely allows the underlying chat GPT engine<00:33:57.120> to<00:33:57.440> carefully<00:33:57.840> read<00:33:58.080> our<00:33:58.399> previous 00:33:58.710 --> 00:33:58.720 align:start position:0% engine to carefully read our previous 00:33:58.720 --> 00:34:00.789 align:start position:0% engine to carefully read our previous chats<00:33:59.360> and<00:33:59.679> stored<00:34:00.080> memories<00:34:00.480> to 00:34:00.789 --> 00:34:00.799 align:start position:0% chats and stored memories to 00:34:00.799 --> 00:34:03.190 align:start position:0% chats and stored memories to consistently<00:34:01.360> give<00:34:01.679> significantly<00:34:02.399> better 00:34:03.190 --> 00:34:03.200 align:start position:0% consistently give significantly better 00:34:03.200 --> 00:34:05.750 align:start position:0% consistently give significantly better contextaware<00:34:04.080> answers. 00:34:05.750 --> 00:34:05.760 align:start position:0% contextaware answers. 00:34:05.760 --> 00:34:07.509 align:start position:0% contextaware answers. It<00:34:06.000> clearly<00:34:06.399> states<00:34:06.640> that<00:34:06.880> your<00:34:07.120> deep 00:34:07.509 --> 00:34:07.519 align:start position:0% It clearly states that your deep 00:34:07.519 --> 00:34:09.589 align:start position:0% It clearly states that your deep personal<00:34:08.000> privacy<00:34:08.399> permissions<00:34:08.879> are<00:34:09.119> heavily 00:34:09.589 --> 00:34:09.599 align:start position:0% personal privacy permissions are heavily 00:34:09.599 --> 00:34:11.909 align:start position:0% personal privacy permissions are heavily respected<00:34:10.480> and<00:34:10.720> you<00:34:10.879> are<00:34:11.119> always<00:34:11.520> completely 00:34:11.909 --> 00:34:11.919 align:start position:0% respected and you are always completely 00:34:11.919 --> 00:34:14.950 align:start position:0% respected and you are always completely in<00:34:12.240> control.<00:34:13.599> It<00:34:13.839> does<00:34:14.000> warn<00:34:14.240> that<00:34:14.480> external 00:34:14.950 --> 00:34:14.960 align:start position:0% in control. It does warn that external 00:34:14.960 --> 00:34:16.950 align:start position:0% in control. It does warn that external connectors<00:34:15.520> may<00:34:15.760> possibly<00:34:16.159> introduce<00:34:16.639> some 00:34:16.950 --> 00:34:16.960 align:start position:0% connectors may possibly introduce some 00:34:16.960 --> 00:34:20.069 align:start position:0% connectors may possibly introduce some slight<00:34:17.280> security<00:34:17.760> risk.<00:34:18.960> I<00:34:19.200> will<00:34:19.359> boldly<00:34:19.839> open 00:34:20.069 --> 00:34:20.079 align:start position:0% slight security risk. I will boldly open 00:34:20.079 --> 00:34:21.990 align:start position:0% slight security risk. I will boldly open up<00:34:20.320> our<00:34:20.560> direct<00:34:21.040> GitHub<00:34:21.520> developer 00:34:21.990 --> 00:34:22.000 align:start position:0% up our direct GitHub developer 00:34:22.000 --> 00:34:23.349 align:start position:0% up our direct GitHub developer dashboard. 00:34:23.349 --> 00:34:23.359 align:start position:0% dashboard. 00:34:23.359 --> 00:34:25.190 align:start position:0% dashboard. You<00:34:23.599> can<00:34:23.760> visually<00:34:24.159> see<00:34:24.320> that<00:34:24.560> the<00:34:24.800> secure 00:34:25.190 --> 00:34:25.200 align:start position:0% You can visually see that the secure 00:34:25.200 --> 00:34:27.829 align:start position:0% You can visually see that the secure GitHub<00:34:25.760> app<00:34:26.000> authorization<00:34:26.800> connection<00:34:27.599> is 00:34:27.829 --> 00:34:27.839 align:start position:0% GitHub app authorization connection is 00:34:27.839 --> 00:34:30.629 align:start position:0% GitHub app authorization connection is actively<00:34:28.399> starting<00:34:28.720> in<00:34:28.879> the<00:34:29.040> background. 00:34:30.629 --> 00:34:30.639 align:start position:0% actively starting in the background. 00:34:30.639 --> 00:34:32.790 align:start position:0% actively starting in the background. Absolutely<00:34:31.359> all<00:34:31.599> our<00:34:31.839> ongoing<00:34:32.320> critical 00:34:32.790 --> 00:34:32.800 align:start position:0% Absolutely all our ongoing critical 00:34:32.800 --> 00:34:34.869 align:start position:0% Absolutely all our ongoing critical development<00:34:33.280> work<00:34:33.520> is<00:34:33.760> safely<00:34:34.240> housed<00:34:34.639> right 00:34:34.869 --> 00:34:34.879 align:start position:0% development work is safely housed right 00:34:34.879 --> 00:34:37.829 align:start position:0% development work is safely housed right here.<00:34:36.159> We<00:34:36.399> will<00:34:36.560> press<00:34:36.800> firmly<00:34:37.280> to<00:34:37.520> continue 00:34:37.829 --> 00:34:37.839 align:start position:0% here. We will press firmly to continue 00:34:37.839 --> 00:34:40.230 align:start position:0% here. We will press firmly to continue onward<00:34:38.240> to<00:34:38.399> GitHub<00:34:39.200> so<00:34:39.440> we<00:34:39.599> can<00:34:39.760> comfortably 00:34:40.230 --> 00:34:40.240 align:start position:0% onward to GitHub so we can comfortably 00:34:40.240 --> 00:34:43.109 align:start position:0% onward to GitHub so we can comfortably go<00:34:40.399> straight<00:34:40.639> to<00:34:40.879> our<00:34:41.040> main<00:34:41.280> profile<00:34:41.760> account. 00:34:43.109 --> 00:34:43.119 align:start position:0% go straight to our main profile account. 00:34:43.119 --> 00:34:44.869 align:start position:0% go straight to our main profile account. It<00:34:43.359> will<00:34:43.520> naturally<00:34:44.000> take<00:34:44.159> a<00:34:44.399> little<00:34:44.560> bit<00:34:44.639> of 00:34:44.869 --> 00:34:44.879 align:start position:0% It will naturally take a little bit of 00:34:44.879 --> 00:34:47.589 align:start position:0% It will naturally take a little bit of processing<00:34:45.359> time<00:34:45.520> to<00:34:45.760> fully<00:34:46.079> connect.<00:34:47.359> A 00:34:47.589 --> 00:34:47.599 align:start position:0% processing time to fully connect. A 00:34:47.599 --> 00:34:50.069 align:start position:0% processing time to fully connect. A basic<00:34:48.000> connection<00:34:48.320> will<00:34:48.560> form.<00:34:49.679> You<00:34:49.839> can<00:34:49.919> see 00:34:50.069 --> 00:34:50.079 align:start position:0% basic connection will form. You can see 00:34:50.079 --> 00:34:53.349 align:start position:0% basic connection will form. You can see it<00:34:50.240> is<00:34:50.480> connected.<00:34:51.679> I<00:34:52.000> open<00:34:52.320> plugins<00:34:52.800> again. 00:34:53.349 --> 00:34:53.359 align:start position:0% it is connected. I open plugins again. 00:34:53.359 --> 00:34:55.109 align:start position:0% it is connected. I open plugins again. Now<00:34:53.520> you<00:34:53.760> will<00:34:53.919> actively<00:34:54.480> see<00:34:54.639> that<00:34:54.879> our 00:34:55.109 --> 00:34:55.119 align:start position:0% Now you will actively see that our 00:34:55.119 --> 00:34:57.349 align:start position:0% Now you will actively see that our dedicated<00:34:55.760> GitHub<00:34:56.240> plugin<00:34:56.639> is<00:34:56.879> finally 00:34:57.349 --> 00:34:57.359 align:start position:0% dedicated GitHub plugin is finally 00:34:57.359 --> 00:35:00.069 align:start position:0% dedicated GitHub plugin is finally working<00:34:57.760> precisely<00:34:58.320> as<00:34:58.560> intended.<00:34:59.760> It 00:35:00.069 --> 00:35:00.079 align:start position:0% working precisely as intended. It 00:35:00.079 --> 00:35:02.150 align:start position:0% working precisely as intended. It smoothly<00:35:00.560> works<00:35:00.960> specifically<00:35:01.599> because<00:35:01.920> it 00:35:02.150 --> 00:35:02.160 align:start position:0% smoothly works specifically because it 00:35:02.160 --> 00:35:03.829 align:start position:0% smoothly works specifically because it is<00:35:02.320> successfully<00:35:02.960> connected<00:35:03.359> to<00:35:03.520> the<00:35:03.680> back 00:35:03.829 --> 00:35:03.839 align:start position:0% is successfully connected to the back 00:35:03.839 --> 00:35:07.190 align:start position:0% is successfully connected to the back end.<00:35:05.200> If<00:35:05.440> it<00:35:05.599> is<00:35:05.760> ever<00:35:06.079> mysteriously<00:35:06.880> not 00:35:07.190 --> 00:35:07.200 align:start position:0% end. If it is ever mysteriously not 00:35:07.200 --> 00:35:09.270 align:start position:0% end. If it is ever mysteriously not connected,<00:35:08.079> we<00:35:08.320> can<00:35:08.480> easily<00:35:08.800> check<00:35:09.040> our 00:35:09.270 --> 00:35:09.280 align:start position:0% connected, we can easily check our 00:35:09.280 --> 00:35:10.870 align:start position:0% connected, we can easily check our credentials<00:35:09.760> again<00:35:10.079> to<00:35:10.320> see<00:35:10.400> if<00:35:10.560> we<00:35:10.720> can 00:35:10.870 --> 00:35:10.880 align:start position:0% credentials again to see if we can 00:35:10.880 --> 00:35:13.829 align:start position:0% credentials again to see if we can actively<00:35:11.359> reconnect<00:35:11.920> it.<00:35:13.040> We<00:35:13.280> currently<00:35:13.599> have 00:35:13.829 --> 00:35:13.839 align:start position:0% actively reconnect it. We currently have 00:35:13.839 --> 00:35:16.710 align:start position:0% actively reconnect it. We currently have our<00:35:14.079> active<00:35:14.480> user<00:35:14.800> login,<00:35:15.520> but<00:35:15.760> unfortunately 00:35:16.710 --> 00:35:16.720 align:start position:0% our active user login, but unfortunately 00:35:16.720 --> 00:35:18.790 align:start position:0% our active user login, but unfortunately adding<00:35:16.960> the<00:35:17.200> specific<00:35:17.680> external<00:35:18.160> link<00:35:18.560> just 00:35:18.790 --> 00:35:18.800 align:start position:0% adding the specific external link just 00:35:18.800 --> 00:35:20.310 align:start position:0% adding the specific external link just failed. 00:35:20.310 --> 00:35:20.320 align:start position:0% failed. 00:35:20.320 --> 00:35:23.589 align:start position:0% failed. Why<00:35:20.560> exactly<00:35:20.960> did<00:35:21.119> it<00:35:21.280> suddenly<00:35:21.760> fail<00:35:22.160> here? 00:35:23.589 --> 00:35:23.599 align:start position:0% Why exactly did it suddenly fail here? 00:35:23.599 --> 00:35:25.510 align:start position:0% Why exactly did it suddenly fail here? We<00:35:23.839> must<00:35:24.160> remember<00:35:24.400> that<00:35:24.720> this<00:35:25.040> is<00:35:25.200> our 00:35:25.510 --> 00:35:25.520 align:start position:0% We must remember that this is our 00:35:25.520 --> 00:35:29.190 align:start position:0% We must remember that this is our specific<00:35:26.079> chat<00:35:26.480> GPT<00:35:27.119> plus<00:35:27.440> tier<00:35:27.760> account.<00:35:28.880> You 00:35:29.190 --> 00:35:29.200 align:start position:0% specific chat GPT plus tier account. You 00:35:29.200 --> 00:35:31.270 align:start position:0% specific chat GPT plus tier account. You absolutely<00:35:29.839> must<00:35:30.240> remember<00:35:30.560> this<00:35:30.800> vital 00:35:31.270 --> 00:35:31.280 align:start position:0% absolutely must remember this vital 00:35:31.280 --> 00:35:33.270 align:start position:0% absolutely must remember this vital detail<00:35:32.000> because<00:35:32.320> it<00:35:32.560> impacts<00:35:33.040> our 00:35:33.270 --> 00:35:33.280 align:start position:0% detail because it impacts our 00:35:33.280 --> 00:35:35.109 align:start position:0% detail because it impacts our permissions. 00:35:35.109 --> 00:35:35.119 align:start position:0% permissions. 00:35:35.119 --> 00:35:37.030 align:start position:0% permissions. Now<00:35:35.359> we<00:35:35.520> will<00:35:35.760> purposefully<00:35:36.320> open<00:35:36.560> up<00:35:36.800> the 00:35:37.030 --> 00:35:37.040 align:start position:0% Now we will purposefully open up the 00:35:37.040 --> 00:35:39.670 align:start position:0% Now we will purposefully open up the completely<00:35:37.599> alternative<00:35:38.320> chat<00:35:38.720> GPT<00:35:39.280> account 00:35:39.670 --> 00:35:39.680 align:start position:0% completely alternative chat GPT account 00:35:39.680 --> 00:35:41.190 align:start position:0% completely alternative chat GPT account instead. 00:35:41.190 --> 00:35:41.200 align:start position:0% instead. 00:35:41.200 --> 00:35:43.270 align:start position:0% instead. We<00:35:41.359> will<00:35:41.599> securely<00:35:42.079> bring<00:35:42.320> our<00:35:42.560> dedicated 00:35:43.270 --> 00:35:43.280 align:start position:0% We will securely bring our dedicated 00:35:43.280 --> 00:35:45.750 align:start position:0% We will securely bring our dedicated Michael<00:35:43.680> Deont<00:35:44.160> user<00:35:44.560> account<00:35:45.200> right<00:35:45.520> here 00:35:45.750 --> 00:35:45.760 align:start position:0% Michael Deont user account right here 00:35:45.760 --> 00:35:49.109 align:start position:0% Michael Deont user account right here into<00:35:46.079> the<00:35:46.240> active<00:35:46.640> workspace<00:35:47.119> to<00:35:47.359> try<00:35:47.599> again. 00:35:49.109 --> 00:35:49.119 align:start position:0% into the active workspace to try again. 00:35:49.119 --> 00:35:51.910 align:start position:0% into the active workspace to try again. Our<00:35:49.599> premium<00:35:50.079> chat<00:35:50.480> GPT<00:35:51.119> plus<00:35:51.440> subscription 00:35:51.910 --> 00:35:51.920 align:start position:0% Our premium chat GPT plus subscription 00:35:51.920 --> 00:35:55.510 align:start position:0% Our premium chat GPT plus subscription tier<00:35:52.320> is<00:35:52.560> fully<00:35:52.960> available<00:35:53.520> right<00:35:53.839> here.<00:35:55.200> Now 00:35:55.510 --> 00:35:55.520 align:start position:0% tier is fully available right here. Now 00:35:55.520 --> 00:35:57.430 align:start position:0% tier is fully available right here. Now we<00:35:55.680> will<00:35:55.839> carefully<00:35:56.320> attempt<00:35:56.720> to<00:35:56.880> securely 00:35:57.430 --> 00:35:57.440 align:start position:0% we will carefully attempt to securely 00:35:57.440 --> 00:35:59.349 align:start position:0% we will carefully attempt to securely connect<00:35:57.760> the<00:35:58.000> integration<00:35:58.560> system<00:35:59.040> once 00:35:59.349 --> 00:35:59.359 align:start position:0% connect the integration system once 00:35:59.359 --> 00:36:02.069 align:start position:0% connect the integration system once again.<00:36:00.560> It<00:36:00.800> will<00:36:00.960> systematically<00:36:01.760> connect 00:36:02.069 --> 00:36:02.079 align:start position:0% again. It will systematically connect 00:36:02.079 --> 00:36:04.470 align:start position:0% again. It will systematically connect our<00:36:02.400> main<00:36:02.720> chat<00:36:03.040> GPT<00:36:03.680> interface<00:36:04.079> to<00:36:04.320> the 00:36:04.470 --> 00:36:04.480 align:start position:0% our main chat GPT interface to the 00:36:04.480 --> 00:36:06.069 align:start position:0% our main chat GPT interface to the repository. 00:36:06.069 --> 00:36:06.079 align:start position:0% repository. 00:36:06.079 --> 00:36:08.150 align:start position:0% repository. If<00:36:06.320> we<00:36:06.480> ever<00:36:06.800> eventually<00:36:07.359> want<00:36:07.520> to<00:36:07.680> completely 00:36:08.150 --> 00:36:08.160 align:start position:0% If we ever eventually want to completely 00:36:08.160 --> 00:36:10.550 align:start position:0% If we ever eventually want to completely remove<00:36:08.480> it<00:36:08.640> for<00:36:08.880> security<00:36:09.359> reasons,<00:36:10.240> we<00:36:10.400> can 00:36:10.550 --> 00:36:10.560 align:start position:0% remove it for security reasons, we can 00:36:10.560 --> 00:36:12.390 align:start position:0% remove it for security reasons, we can easily<00:36:10.960> uninstall<00:36:11.520> it<00:36:11.680> and<00:36:12.000> quickly 00:36:12.390 --> 00:36:12.400 align:start position:0% easily uninstall it and quickly 00:36:12.400 --> 00:36:15.349 align:start position:0% easily uninstall it and quickly reinstall<00:36:12.880> it<00:36:13.040> from<00:36:13.280> scratch<00:36:13.680> later<00:36:14.000> again. 00:36:15.349 --> 00:36:15.359 align:start position:0% reinstall it from scratch later again. 00:36:15.359 --> 00:36:17.270 align:start position:0% reinstall it from scratch later again. We<00:36:15.680> obviously<00:36:16.160> also<00:36:16.480> have<00:36:16.640> the<00:36:16.880> standard 00:36:17.270 --> 00:36:17.280 align:start position:0% We obviously also have the standard 00:36:17.280 --> 00:36:19.109 align:start position:0% We obviously also have the standard option<00:36:17.599> to<00:36:17.839> immediately<00:36:18.400> disconnect<00:36:18.960> the 00:36:19.109 --> 00:36:19.119 align:start position:0% option to immediately disconnect the 00:36:19.119 --> 00:36:22.069 align:start position:0% option to immediately disconnect the authorization<00:36:19.920> any<00:36:20.240> time.<00:36:21.680> We<00:36:21.920> will 00:36:22.069 --> 00:36:22.079 align:start position:0% authorization any time. We will 00:36:22.079 --> 00:36:24.150 align:start position:0% authorization any time. We will gracefully<00:36:22.720> proceed<00:36:23.200> straight<00:36:23.599> directly 00:36:24.150 --> 00:36:24.160 align:start position:0% gracefully proceed straight directly 00:36:24.160 --> 00:36:26.390 align:start position:0% gracefully proceed straight directly over<00:36:24.400> to<00:36:24.560> the<00:36:24.800> main<00:36:25.040> GitHub<00:36:25.599> authorization 00:36:26.390 --> 00:36:26.400 align:start position:0% over to the main GitHub authorization 00:36:26.400 --> 00:36:27.990 align:start position:0% over to the main GitHub authorization portal. 00:36:27.990 --> 00:36:28.000 align:start position:0% portal. 00:36:28.000 --> 00:36:29.670 align:start position:0% portal. Now<00:36:28.240> it<00:36:28.480> will<00:36:28.640> successfully<00:36:29.200> build<00:36:29.440> the 00:36:29.670 --> 00:36:29.680 align:start position:0% Now it will successfully build the 00:36:29.680 --> 00:36:31.670 align:start position:0% Now it will successfully build the required<00:36:30.160> connection<00:36:30.720> directly<00:36:31.200> in<00:36:31.520> our 00:36:31.670 --> 00:36:31.680 align:start position:0% required connection directly in our 00:36:31.680 --> 00:36:34.470 align:start position:0% required connection directly in our correct<00:36:32.160> targeted<00:36:32.720> application. 00:36:34.470 --> 00:36:34.480 align:start position:0% correct targeted application. 00:36:34.480 --> 00:36:36.870 align:start position:0% correct targeted application. It<00:36:34.720> strictly<00:36:35.200> demands<00:36:35.839> highly<00:36:36.320> secure 00:36:36.870 --> 00:36:36.880 align:start position:0% It strictly demands highly secure 00:36:36.880 --> 00:36:39.910 align:start position:0% It strictly demands highly secure multiffactor<00:36:37.760> user<00:36:38.160> authentication. 00:36:39.910 --> 00:36:39.920 align:start position:0% multiffactor user authentication. 00:36:39.920 --> 00:36:42.069 align:start position:0% multiffactor user authentication. We<00:36:40.079> will<00:36:40.320> comfortably<00:36:40.960> utilize<00:36:41.280> the<00:36:41.599> standard 00:36:42.069 --> 00:36:42.079 align:start position:0% We will comfortably utilize the standard 00:36:42.079 --> 00:36:45.270 align:start position:0% We will comfortably utilize the standard authenticator<00:36:42.880> mobile<00:36:43.280> app<00:36:43.440> to<00:36:43.680> handle<00:36:44.000> this. 00:36:45.270 --> 00:36:45.280 align:start position:0% authenticator mobile app to handle this. 00:36:45.280 --> 00:36:47.270 align:start position:0% authenticator mobile app to handle this. The<00:36:45.520> mobile<00:36:45.920> authenticator<00:36:46.720> app<00:36:46.960> will 00:36:47.270 --> 00:36:47.280 align:start position:0% The mobile authenticator app will 00:36:47.280 --> 00:36:49.270 align:start position:0% The mobile authenticator app will swiftly<00:36:47.760> finish<00:36:48.160> processing<00:36:48.720> our<00:36:48.960> deep 00:36:49.270 --> 00:36:49.280 align:start position:0% swiftly finish processing our deep 00:36:49.280 --> 00:36:51.750 align:start position:0% swiftly finish processing our deep security<00:36:49.760> verification. 00:36:51.750 --> 00:36:51.760 align:start position:0% security verification. 00:36:51.760 --> 00:36:53.990 align:start position:0% security verification. Now<00:36:52.079> you<00:36:52.320> can<00:36:52.400> clearly<00:36:52.800> see<00:36:52.960> that<00:36:53.200> our<00:36:53.520> primary 00:36:53.990 --> 00:36:54.000 align:start position:0% Now you can clearly see that our primary 00:36:54.000 --> 00:36:56.790 align:start position:0% Now you can clearly see that our primary GitHub<00:36:54.560> profile<00:36:55.280> is<00:36:55.599> finally<00:36:56.160> directly 00:36:56.790 --> 00:36:56.800 align:start position:0% GitHub profile is finally directly 00:36:56.800 --> 00:36:59.030 align:start position:0% GitHub profile is finally directly connected<00:36:57.280> perfectly. 00:36:59.030 --> 00:36:59.040 align:start position:0% connected perfectly. 00:36:59.040 --> 00:37:01.109 align:start position:0% connected perfectly. I<00:36:59.280> will<00:36:59.440> quickly<00:36:59.839> pivot<00:37:00.160> back<00:37:00.400> over<00:37:00.640> to<00:37:00.880> our 00:37:01.109 --> 00:37:01.119 align:start position:0% I will quickly pivot back over to our 00:37:01.119 --> 00:37:03.589 align:start position:0% I will quickly pivot back over to our main<00:37:01.440> codeex<00:37:02.000> interface. 00:37:03.589 --> 00:37:03.599 align:start position:0% main codeex interface. 00:37:03.599 --> 00:37:05.349 align:start position:0% main codeex interface. You<00:37:03.760> can<00:37:03.920> clearly<00:37:04.320> see<00:37:04.480> that<00:37:04.640> our<00:37:04.880> secure 00:37:05.349 --> 00:37:05.359 align:start position:0% You can clearly see that our secure 00:37:05.359 --> 00:37:07.349 align:start position:0% You can clearly see that our secure software<00:37:05.839> link<00:37:06.079> is<00:37:06.320> now<00:37:06.480> fully<00:37:06.800> established 00:37:07.349 --> 00:37:07.359 align:start position:0% software link is now fully established 00:37:07.359 --> 00:37:09.910 align:start position:0% software link is now fully established and<00:37:07.680> solidly<00:37:08.240> connected. 00:37:09.910 --> 00:37:09.920 align:start position:0% and solidly connected. 00:37:09.920 --> 00:37:11.990 align:start position:0% and solidly connected. If<00:37:10.160> we<00:37:10.320> carefully<00:37:10.800> look<00:37:11.040> directly<00:37:11.520> at<00:37:11.680> our 00:37:11.990 --> 00:37:12.000 align:start position:0% If we carefully look directly at our 00:37:12.000 --> 00:37:14.470 align:start position:0% If we carefully look directly at our active<00:37:12.320> system<00:37:12.720> plugins<00:37:13.200> list<00:37:13.520> right<00:37:13.680> now, 00:37:14.470 --> 00:37:14.480 align:start position:0% active system plugins list right now, 00:37:14.480 --> 00:37:16.550 align:start position:0% active system plugins list right now, absolutely<00:37:15.119> all<00:37:15.359> our<00:37:15.680> relevant<00:37:16.000> GitHub 00:37:16.550 --> 00:37:16.560 align:start position:0% absolutely all our relevant GitHub 00:37:16.560 --> 00:37:18.390 align:start position:0% absolutely all our relevant GitHub integration<00:37:17.119> tasks<00:37:17.599> have<00:37:17.760> delightfully 00:37:18.390 --> 00:37:18.400 align:start position:0% integration tasks have delightfully 00:37:18.400 --> 00:37:21.510 align:start position:0% integration tasks have delightfully started<00:37:18.800> showing<00:37:19.040> up<00:37:19.280> directly<00:37:19.680> in<00:37:19.920> there.<00:37:21.280> We 00:37:21.510 --> 00:37:21.520 align:start position:0% started showing up directly in there. We 00:37:21.520 --> 00:37:23.670 align:start position:0% started showing up directly in there. We will<00:37:21.760> smoothly<00:37:22.240> navigate<00:37:22.720> back<00:37:23.040> over<00:37:23.280> to<00:37:23.440> our 00:37:23.670 --> 00:37:23.680 align:start position:0% will smoothly navigate back over to our 00:37:23.680 --> 00:37:26.470 align:start position:0% will smoothly navigate back over to our main<00:37:23.920> chat<00:37:24.320> terminal<00:37:24.720> interface. 00:37:26.470 --> 00:37:26.480 align:start position:0% main chat terminal interface. 00:37:26.480 --> 00:37:28.630 align:start position:0% main chat terminal interface. You<00:37:26.720> can<00:37:26.880> very<00:37:27.119> clearly<00:37:27.520> see<00:37:27.760> our<00:37:28.079> dedicated 00:37:28.630 --> 00:37:28.640 align:start position:0% You can very clearly see our dedicated 00:37:28.640 --> 00:37:31.349 align:start position:0% You can very clearly see our dedicated GitHub<00:37:29.200> functionality<00:37:30.240> is<00:37:30.560> directly<00:37:31.040> added 00:37:31.349 --> 00:37:31.359 align:start position:0% GitHub functionality is directly added 00:37:31.359 --> 00:37:34.230 align:start position:0% GitHub functionality is directly added and<00:37:31.680> fully<00:37:32.000> available<00:37:32.560> right<00:37:32.800> there. 00:37:34.230 --> 00:37:34.240 align:start position:0% and fully available right there. 00:37:34.240 --> 00:37:35.829 align:start position:0% and fully available right there. We<00:37:34.480> will<00:37:34.640> quickly<00:37:35.040> go<00:37:35.200> back<00:37:35.359> over<00:37:35.599> to<00:37:35.760> the 00:37:35.829 --> 00:37:35.839 align:start position:0% We will quickly go back over to the 00:37:35.839 --> 00:37:38.390 align:start position:0% We will quickly go back over to the plugins<00:37:36.320> tab<00:37:36.880> and<00:37:37.119> our<00:37:37.280> GitHub<00:37:37.760> features<00:37:38.160> will 00:37:38.390 --> 00:37:38.400 align:start position:0% plugins tab and our GitHub features will 00:37:38.400 --> 00:37:40.230 align:start position:0% plugins tab and our GitHub features will be<00:37:38.560> permanently<00:37:39.040> included<00:37:39.520> in<00:37:39.680> the<00:37:39.839> active 00:37:40.230 --> 00:37:40.240 align:start position:0% be permanently included in the active 00:37:40.240 --> 00:37:43.270 align:start position:0% be permanently included in the active workflow<00:37:40.800> loop.<00:37:41.920> It<00:37:42.160> will<00:37:42.320> effortlessly<00:37:42.960> come 00:37:43.270 --> 00:37:43.280 align:start position:0% workflow loop. It will effortlessly come 00:37:43.280 --> 00:37:45.030 align:start position:0% workflow loop. It will effortlessly come directly<00:37:43.760> into<00:37:44.079> our<00:37:44.240> daily<00:37:44.640> software 00:37:45.030 --> 00:37:45.040 align:start position:0% directly into our daily software 00:37:45.040 --> 00:37:47.109 align:start position:0% directly into our daily software development<00:37:45.599> work. 00:37:47.109 --> 00:37:47.119 align:start position:0% development work. 00:37:47.119 --> 00:37:48.870 align:start position:0% development work. Ultimately,<00:37:47.839> we<00:37:48.079> have<00:37:48.240> incredibly 00:37:48.870 --> 00:37:48.880 align:start position:0% Ultimately, we have incredibly 00:37:48.880 --> 00:37:51.589 align:start position:0% Ultimately, we have incredibly successfully<00:37:49.520> added<00:37:49.839> our<00:37:50.079> robust<00:37:50.640> codeex<00:37:51.200> AI 00:37:51.589 --> 00:37:51.599 align:start position:0% successfully added our robust codeex AI 00:37:51.599 --> 00:37:53.990 align:start position:0% successfully added our robust codeex AI tool<00:37:52.160> to<00:37:52.480> perfectly<00:37:52.960> sync<00:37:53.280> with<00:37:53.440> our<00:37:53.599> remote 00:37:53.990 --> 00:37:54.000 align:start position:0% tool to perfectly sync with our remote 00:37:54.000 --> 00:37:58.710 align:start position:0% tool to perfectly sync with our remote GitHub<00:37:54.480> code<00:37:54.800> repositories. 00:37:58.710 --> 00:37:58.720 align:start position:0% 00:37:58.720 --> 00:38:01.030 align:start position:0% Moving<00:37:59.119> logically<00:37:59.839> to<00:38:00.079> the<00:38:00.240> very<00:38:00.560> next 00:38:01.030 --> 00:38:01.040 align:start position:0% Moving logically to the very next 00:38:01.040 --> 00:38:03.510 align:start position:0% Moving logically to the very next crucial<00:38:01.599> step,<00:38:02.400> we<00:38:02.640> will<00:38:02.800> thoroughly<00:38:03.280> talk 00:38:03.510 --> 00:38:03.520 align:start position:0% crucial step, we will thoroughly talk 00:38:03.520 --> 00:38:06.390 align:start position:0% crucial step, we will thoroughly talk about<00:38:03.680> the<00:38:03.920> highly<00:38:04.400> specific<00:38:05.040> agents.mmd 00:38:06.390 --> 00:38:06.400 align:start position:0% about the highly specific agents.mmd 00:38:06.400 --> 00:38:08.790 align:start position:0% about the highly specific agents.mmd configuration<00:38:07.119> file. 00:38:08.790 --> 00:38:08.800 align:start position:0% configuration file. 00:38:08.800 --> 00:38:11.430 align:start position:0% configuration file. This<00:38:09.200> incredibly<00:38:10.000> important<00:38:10.480> file<00:38:11.119> is 00:38:11.430 --> 00:38:11.440 align:start position:0% This incredibly important file is 00:38:11.440 --> 00:38:13.829 align:start position:0% This incredibly important file is primarily<00:38:12.079> used<00:38:12.400> for<00:38:12.640> organizing<00:38:13.280> massively 00:38:13.829 --> 00:38:13.839 align:start position:0% primarily used for organizing massively 00:38:13.839 --> 00:38:16.710 align:start position:0% primarily used for organizing massively big<00:38:14.160> software<00:38:14.640> development<00:38:15.119> projects. 00:38:16.710 --> 00:38:16.720 align:start position:0% big software development projects. 00:38:16.720 --> 00:38:19.349 align:start position:0% big software development projects. We<00:38:17.040> specifically<00:38:17.760> utilize<00:38:18.160> it<00:38:18.720> whenever<00:38:19.119> we 00:38:19.349 --> 00:38:19.359 align:start position:0% We specifically utilize it whenever we 00:38:19.359 --> 00:38:21.750 align:start position:0% We specifically utilize it whenever we happen<00:38:19.599> to<00:38:19.760> have<00:38:20.000> many<00:38:20.400> complex<00:38:21.119> automated 00:38:21.750 --> 00:38:21.760 align:start position:0% happen to have many complex automated 00:38:21.760 --> 00:38:25.030 align:start position:0% happen to have many complex automated tasks<00:38:22.640> or<00:38:22.880> a<00:38:23.200> full<00:38:23.599> highly<00:38:24.079> detailed<00:38:24.640> business 00:38:25.030 --> 00:38:25.040 align:start position:0% tasks or a full highly detailed business 00:38:25.040 --> 00:38:27.990 align:start position:0% tasks or a full highly detailed business use<00:38:25.280> case<00:38:25.520> to<00:38:25.680> carefully<00:38:26.079> look<00:38:26.320> at.<00:38:27.599> I<00:38:27.839> will 00:38:27.990 --> 00:38:28.000 align:start position:0% use case to carefully look at. I will 00:38:28.000 --> 00:38:29.990 align:start position:0% use case to carefully look at. I will intentionally<00:38:28.560> open<00:38:28.880> it<00:38:29.040> up<00:38:29.359> right<00:38:29.599> here<00:38:29.839> on 00:38:29.990 --> 00:38:30.000 align:start position:0% intentionally open it up right here on 00:38:30.000 --> 00:38:32.230 align:start position:0% intentionally open it up right here on the<00:38:30.240> screen<00:38:30.880> so<00:38:31.040> you<00:38:31.280> can<00:38:31.440> clearly<00:38:31.839> see 00:38:32.230 --> 00:38:32.240 align:start position:0% the screen so you can clearly see 00:38:32.240 --> 00:38:34.230 align:start position:0% the screen so you can clearly see exactly<00:38:32.720> where<00:38:32.960> these<00:38:33.280> vital<00:38:33.839> agent 00:38:34.230 --> 00:38:34.240 align:start position:0% exactly where these vital agent 00:38:34.240 --> 00:38:37.030 align:start position:0% exactly where these vital agent configuration<00:38:34.960> files<00:38:35.520> naturally<00:38:36.079> come<00:38:36.240> from 00:38:37.030 --> 00:38:37.040 align:start position:0% configuration files naturally come from 00:38:37.040 --> 00:38:40.310 align:start position:0% configuration files naturally come from and<00:38:37.359> exactly<00:38:37.839> where<00:38:38.079> to<00:38:38.320> easily<00:38:38.720> find<00:38:38.960> them. 00:38:40.310 --> 00:38:40.320 align:start position:0% and exactly where to easily find them. 00:38:40.320 --> 00:38:42.310 align:start position:0% and exactly where to easily find them. It<00:38:40.560> will<00:38:40.720> reliably<00:38:41.359> give<00:38:41.520> us<00:38:41.680> the<00:38:42.000> system 00:38:42.310 --> 00:38:42.320 align:start position:0% It will reliably give us the system 00:38:42.320 --> 00:38:45.750 align:start position:0% It will reliably give us the system response<00:38:42.960> directly<00:38:43.520> and<00:38:43.839> accurately. 00:38:45.750 --> 00:38:45.760 align:start position:0% response directly and accurately. 00:38:45.760 --> 00:38:48.870 align:start position:0% response directly and accurately. The<00:38:46.000> dedicated<00:38:46.720> agents.mmd<00:38:47.839> file<00:38:48.240> immensely 00:38:48.870 --> 00:38:48.880 align:start position:0% The dedicated agents.mmd file immensely 00:38:48.880 --> 00:38:51.190 align:start position:0% The dedicated agents.mmd file immensely helps<00:38:49.200> us<00:38:49.440> to<00:38:49.680> deeply<00:38:50.079> inspect<00:38:50.880> and 00:38:51.190 --> 00:38:51.200 align:start position:0% helps us to deeply inspect and 00:38:51.200 --> 00:38:53.270 align:start position:0% helps us to deeply inspect and standardize<00:38:51.920> our<00:38:52.320> overall<00:38:52.800> project 00:38:53.270 --> 00:38:53.280 align:start position:0% standardize our overall project 00:38:53.280 --> 00:38:55.030 align:start position:0% standardize our overall project architecture. 00:38:55.030 --> 00:38:55.040 align:start position:0% architecture. 00:38:55.040 --> 00:38:57.190 align:start position:0% architecture. You<00:38:55.280> can<00:38:55.440> clearly<00:38:55.839> see<00:38:56.000> it<00:38:56.240> actively<00:38:56.800> looking 00:38:57.190 --> 00:38:57.200 align:start position:0% You can clearly see it actively looking 00:38:57.200 --> 00:39:00.630 align:start position:0% You can clearly see it actively looking deep<00:38:57.520> inside<00:38:57.920> our<00:38:58.240> raw<00:38:58.560> project<00:38:58.960> files. 00:39:00.630 --> 00:39:00.640 align:start position:0% deep inside our raw project files. 00:39:00.640 --> 00:39:03.109 align:start position:0% deep inside our raw project files. Here<00:39:01.040> it<00:39:01.359> explicitly<00:39:02.000> states<00:39:02.640> that<00:39:02.880> the 00:39:03.109 --> 00:39:03.119 align:start position:0% Here it explicitly states that the 00:39:03.119 --> 00:39:05.670 align:start position:0% Here it explicitly states that the active<00:39:03.520> workspace<00:39:04.160> is<00:39:04.400> entirely<00:39:05.040> empty<00:39:05.440> right 00:39:05.670 --> 00:39:05.680 align:start position:0% active workspace is entirely empty right 00:39:05.680 --> 00:39:09.349 align:start position:0% active workspace is entirely empty right now.<00:39:06.720> There<00:39:06.960> is<00:39:07.200> absolutely<00:39:07.839> no<00:39:08.320> agents.mmd 00:39:09.349 --> 00:39:09.359 align:start position:0% now. There is absolutely no agents.mmd 00:39:09.359 --> 00:39:11.349 align:start position:0% now. There is absolutely no agents.mmd file<00:39:09.760> found. 00:39:11.349 --> 00:39:11.359 align:start position:0% file found. 00:39:11.359 --> 00:39:13.670 align:start position:0% file found. It<00:39:11.599> checked<00:39:11.920> the<00:39:12.160> temporary<00:39:12.640> scratch<00:39:13.040> space 00:39:13.670 --> 00:39:13.680 align:start position:0% It checked the temporary scratch space 00:39:13.680 --> 00:39:17.270 align:start position:0% It checked the temporary scratch space and<00:39:13.920> verified<00:39:14.560> there<00:39:14.800> is<00:39:14.960> no<00:39:15.280> file. 00:39:17.270 --> 00:39:17.280 align:start position:0% and verified there is no file. 00:39:17.280 --> 00:39:19.910 align:start position:0% and verified there is no file. To<00:39:17.520> successfully<00:39:18.240> create<00:39:18.640> one<00:39:18.880> from<00:39:19.119> scratch, 00:39:19.910 --> 00:39:19.920 align:start position:0% To successfully create one from scratch, 00:39:19.920 --> 00:39:23.270 align:start position:0% To successfully create one from scratch, we<00:39:20.240> absolutely<00:39:21.040> must<00:39:21.440> make<00:39:21.760> a<00:39:22.160> brand<00:39:22.480> new 00:39:23.270 --> 00:39:23.280 align:start position:0% we absolutely must make a brand new 00:39:23.280 --> 00:39:27.109 align:start position:0% we absolutely must make a brand new correctly<00:39:23.839> formatted<00:39:24.480> agents.mmd<00:39:25.599> file.<00:39:26.880> I 00:39:27.109 --> 00:39:27.119 align:start position:0% correctly formatted agents.mmd file. I 00:39:27.119 --> 00:39:29.030 align:start position:0% correctly formatted agents.mmd file. I will<00:39:27.280> manually<00:39:27.760> go<00:39:27.920> ahead<00:39:28.240> and<00:39:28.480> create<00:39:28.720> a 00:39:29.030 --> 00:39:29.040 align:start position:0% will manually go ahead and create a 00:39:29.040 --> 00:39:31.349 align:start position:0% will manually go ahead and create a brand<00:39:29.280> new<00:39:29.680> foundational<00:39:30.400> file<00:39:30.880> right<00:39:31.119> here 00:39:31.349 --> 00:39:31.359 align:start position:0% brand new foundational file right here 00:39:31.359 --> 00:39:32.870 align:start position:0% brand new foundational file right here for<00:39:31.599> you. 00:39:32.870 --> 00:39:32.880 align:start position:0% for you. 00:39:32.880 --> 00:39:35.270 align:start position:0% for you. This<00:39:33.200> incredibly<00:39:33.760> efficient<00:39:34.240> way,<00:39:34.880> we<00:39:35.119> can 00:39:35.270 --> 00:39:35.280 align:start position:0% This incredibly efficient way, we can 00:39:35.280 --> 00:39:37.910 align:start position:0% This incredibly efficient way, we can consistently<00:39:36.079> see<00:39:36.480> absolutely<00:39:37.280> all<00:39:37.599> the 00:39:37.910 --> 00:39:37.920 align:start position:0% consistently see absolutely all the 00:39:37.920 --> 00:39:40.790 align:start position:0% consistently see absolutely all the necessary<00:39:38.640> high-level<00:39:39.280> production<00:39:39.760> details 00:39:40.790 --> 00:39:40.800 align:start position:0% necessary high-level production details 00:39:40.800 --> 00:39:43.030 align:start position:0% necessary high-level production details firmly<00:39:41.280> embedded<00:39:41.920> safely<00:39:42.400> within<00:39:42.800> this 00:39:43.030 --> 00:39:43.040 align:start position:0% firmly embedded safely within this 00:39:43.040 --> 00:39:45.270 align:start position:0% firmly embedded safely within this specific<00:39:43.520> file. 00:39:45.270 --> 00:39:45.280 align:start position:0% specific file. 00:39:45.280 --> 00:39:48.230 align:start position:0% specific file. First,<00:39:46.079> the<00:39:46.400> core<00:39:46.800> structured<00:39:47.359> agents<00:39:47.839> file 00:39:48.230 --> 00:39:48.240 align:start position:0% First, the core structured agents file 00:39:48.240 --> 00:39:51.670 align:start position:0% First, the core structured agents file is<00:39:48.480> quickly<00:39:48.880> drafted<00:39:49.440> out.<00:39:50.880> Right<00:39:51.119> after<00:39:51.440> that 00:39:51.670 --> 00:39:51.680 align:start position:0% is quickly drafted out. Right after that 00:39:51.680 --> 00:39:54.230 align:start position:0% is quickly drafted out. Right after that initial<00:39:52.079> phase,<00:39:52.880> we<00:39:53.119> can<00:39:53.280> comfortably<00:39:53.839> make 00:39:54.230 --> 00:39:54.240 align:start position:0% initial phase, we can comfortably make 00:39:54.240 --> 00:39:57.190 align:start position:0% initial phase, we can comfortably make far<00:39:54.560> more<00:39:55.040> highly<00:39:55.520> nuanced<00:39:56.160> text<00:39:56.560> changes<00:39:56.960> to 00:39:57.190 --> 00:39:57.200 align:start position:0% far more highly nuanced text changes to 00:39:57.200 --> 00:39:59.670 align:start position:0% far more highly nuanced text changes to this<00:39:57.359> preliminary<00:39:58.000> draft. 00:39:59.670 --> 00:39:59.680 align:start position:0% this preliminary draft. 00:39:59.680 --> 00:40:01.750 align:start position:0% this preliminary draft. In<00:40:00.000> this<00:40:00.240> specific<00:40:00.720> advanced<00:40:01.280> technical 00:40:01.750 --> 00:40:01.760 align:start position:0% In this specific advanced technical 00:40:01.760 --> 00:40:04.310 align:start position:0% In this specific advanced technical setup,<00:40:02.720> we<00:40:02.960> usually<00:40:03.440> really<00:40:03.839> need<00:40:04.079> to 00:40:04.310 --> 00:40:04.320 align:start position:0% setup, we usually really need to 00:40:04.320 --> 00:40:07.030 align:start position:0% setup, we usually really need to carefully<00:40:04.800> check<00:40:05.119> if<00:40:05.359> our<00:40:05.680> highly<00:40:06.079> specific 00:40:07.030 --> 00:40:07.040 align:start position:0% carefully check if our highly specific 00:40:07.040 --> 00:40:09.910 align:start position:0% carefully check if our highly specific basic<00:40:07.599> operational<00:40:08.240> rules<00:40:09.040> or<00:40:09.359> distinct 00:40:09.910 --> 00:40:09.920 align:start position:0% basic operational rules or distinct 00:40:09.920 --> 00:40:12.230 align:start position:0% basic operational rules or distinct business<00:40:10.320> use<00:40:10.560> cases<00:40:11.119> are<00:40:11.440> actually<00:40:11.839> working 00:40:12.230 --> 00:40:12.240 align:start position:0% business use cases are actually working 00:40:12.240 --> 00:40:13.750 align:start position:0% business use cases are actually working properly. 00:40:13.750 --> 00:40:13.760 align:start position:0% properly. 00:40:13.760 --> 00:40:16.390 align:start position:0% properly. It<00:40:14.079> successfully<00:40:14.720> and<00:40:15.040> directly<00:40:15.680> created<00:40:16.079> an 00:40:16.390 --> 00:40:16.400 align:start position:0% It successfully and directly created an 00:40:16.400 --> 00:40:19.030 align:start position:0% It successfully and directly created an excellent<00:40:16.960> base<00:40:17.440> foundational<00:40:18.160> agent<00:40:18.560> file 00:40:19.030 --> 00:40:19.040 align:start position:0% excellent base foundational agent file 00:40:19.040 --> 00:40:21.430 align:start position:0% excellent base foundational agent file right<00:40:19.359> here<00:40:19.520> for<00:40:19.760> us. 00:40:21.430 --> 00:40:21.440 align:start position:0% right here for us. 00:40:21.440 --> 00:40:23.510 align:start position:0% right here for us. If<00:40:21.680> we<00:40:21.839> carefully<00:40:22.400> review<00:40:22.720> the<00:40:22.960> generated 00:40:23.510 --> 00:40:23.520 align:start position:0% If we carefully review the generated 00:40:23.520 --> 00:40:26.230 align:start position:0% If we carefully review the generated file,<00:40:24.320> we<00:40:24.560> can<00:40:24.720> clearly<00:40:25.119> see<00:40:25.440> its<00:40:25.760> intended 00:40:26.230 --> 00:40:26.240 align:start position:0% file, we can clearly see its intended 00:40:26.240 --> 00:40:28.150 align:start position:0% file, we can clearly see its intended core<00:40:26.560> purpose. 00:40:28.150 --> 00:40:28.160 align:start position:0% core purpose. 00:40:28.160 --> 00:40:30.630 align:start position:0% core purpose. Besides<00:40:28.640> the<00:40:28.960> purpose,<00:40:29.760> there<00:40:29.920> is<00:40:30.079> a<00:40:30.240> clear 00:40:30.630 --> 00:40:30.640 align:start position:0% Besides the purpose, there is a clear 00:40:30.640 --> 00:40:32.710 align:start position:0% Besides the purpose, there is a clear project<00:40:31.119> overview. 00:40:32.710 --> 00:40:32.720 align:start position:0% project overview. 00:40:32.720 --> 00:40:35.510 align:start position:0% project overview. We<00:40:33.040> also<00:40:33.359> see<00:40:33.599> a<00:40:33.839> working<00:40:34.240> agreement,<00:40:35.200> a 00:40:35.510 --> 00:40:35.520 align:start position:0% We also see a working agreement, a 00:40:35.520 --> 00:40:37.829 align:start position:0% We also see a working agreement, a layout,<00:40:36.079> and<00:40:36.320> editing<00:40:36.720> rules.<00:40:37.440> We<00:40:37.680> can 00:40:37.829 --> 00:40:37.839 align:start position:0% layout, and editing rules. We can 00:40:37.839 --> 00:40:39.670 align:start position:0% layout, and editing rules. We can actively<00:40:38.400> cross-check<00:40:39.040> all<00:40:39.280> of<00:40:39.440> these 00:40:39.670 --> 00:40:39.680 align:start position:0% actively cross-check all of these 00:40:39.680 --> 00:40:42.390 align:start position:0% actively cross-check all of these fundamental<00:40:40.400> operational<00:40:41.040> rules<00:40:41.760> precisely 00:40:42.390 --> 00:40:42.400 align:start position:0% fundamental operational rules precisely 00:40:42.400 --> 00:40:44.790 align:start position:0% fundamental operational rules precisely here<00:40:42.640> in<00:40:42.880> the<00:40:43.119> document. 00:40:44.790 --> 00:40:44.800 align:start position:0% here in the document. 00:40:44.800 --> 00:40:46.950 align:start position:0% here in the document. I<00:40:45.040> will<00:40:45.200> also<00:40:45.520> make<00:40:45.760> sure<00:40:45.920> to<00:40:46.160> explicitly<00:40:46.720> tell 00:40:46.950 --> 00:40:46.960 align:start position:0% I will also make sure to explicitly tell 00:40:46.960 --> 00:40:48.870 align:start position:0% I will also make sure to explicitly tell you<00:40:47.280> exactly<00:40:47.760> where<00:40:48.000> this<00:40:48.320> specialized 00:40:48.870 --> 00:40:48.880 align:start position:0% you exactly where this specialized 00:40:48.880 --> 00:40:52.230 align:start position:0% you exactly where this specialized configuration<00:40:49.520> file<00:40:49.839> is<00:40:50.079> typically<00:40:50.560> used. 00:40:52.230 --> 00:40:52.240 align:start position:0% configuration file is typically used. 00:40:52.240 --> 00:40:54.470 align:start position:0% configuration file is typically used. We<00:40:52.560> consistently<00:40:53.280> use<00:40:53.599> the<00:40:53.839> specialized 00:40:54.470 --> 00:40:54.480 align:start position:0% We consistently use the specialized 00:40:54.480 --> 00:40:57.990 align:start position:0% We consistently use the specialized agents.mmd<00:40:55.760> file<00:40:56.480> to<00:40:56.800> effectively<00:40:57.440> establish 00:40:57.990 --> 00:40:58.000 align:start position:0% agents.mmd file to effectively establish 00:40:58.000 --> 00:41:01.030 align:start position:0% agents.mmd file to effectively establish strict<00:40:58.400> working<00:40:58.800> boundaries<00:40:59.680> and<00:40:59.920> core<00:41:00.240> rules 00:41:01.030 --> 00:41:01.040 align:start position:0% strict working boundaries and core rules 00:41:01.040 --> 00:41:03.910 align:start position:0% strict working boundaries and core rules for<00:41:01.280> literally<00:41:01.839> any<00:41:02.240> AI<00:41:02.720> agent<00:41:03.280> operating<00:41:03.680> in 00:41:03.910 --> 00:41:03.920 align:start position:0% for literally any AI agent operating in 00:41:03.920 --> 00:41:05.829 align:start position:0% for literally any AI agent operating in the<00:41:04.079> workspace. 00:41:05.829 --> 00:41:05.839 align:start position:0% the workspace. 00:41:05.839 --> 00:41:07.829 align:start position:0% the workspace. There<00:41:06.079> are<00:41:06.240> basically<00:41:06.720> no<00:41:07.040> other<00:41:07.359> bizarre 00:41:07.829 --> 00:41:07.839 align:start position:0% There are basically no other bizarre 00:41:07.839 --> 00:41:10.309 align:start position:0% There are basically no other bizarre tasks<00:41:08.240> or<00:41:08.480> unrelated<00:41:09.119> work<00:41:09.520> explicitly<00:41:10.079> meant 00:41:10.309 --> 00:41:10.319 align:start position:0% tasks or unrelated work explicitly meant 00:41:10.319 --> 00:41:12.069 align:start position:0% tasks or unrelated work explicitly meant for<00:41:10.560> it. 00:41:12.069 --> 00:41:12.079 align:start position:0% for it. 00:41:12.079 --> 00:41:14.790 align:start position:0% for it. Sometimes,<00:41:12.800> unfortunately,<00:41:14.000> we<00:41:14.319> literally 00:41:14.790 --> 00:41:14.800 align:start position:0% Sometimes, unfortunately, we literally 00:41:14.800 --> 00:41:17.030 align:start position:0% Sometimes, unfortunately, we literally have<00:41:14.960> to<00:41:15.119> go<00:41:15.359> deep<00:41:15.680> down<00:41:15.920> into<00:41:16.160> our<00:41:16.400> underlying 00:41:17.030 --> 00:41:17.040 align:start position:0% have to go deep down into our underlying 00:41:17.040 --> 00:41:19.750 align:start position:0% have to go deep down into our underlying operating<00:41:17.520> system<00:41:18.400> just<00:41:18.640> to<00:41:18.800> manually<00:41:19.359> set<00:41:19.520> up 00:41:19.750 --> 00:41:19.760 align:start position:0% operating system just to manually set up 00:41:19.760 --> 00:41:23.670 align:start position:0% operating system just to manually set up the<00:41:20.000> complex<00:41:20.480> agents.mmd<00:41:21.680> file<00:41:22.000> perfectly. 00:41:23.670 --> 00:41:23.680 align:start position:0% the complex agents.mmd file perfectly. 00:41:23.680 --> 00:41:26.230 align:start position:0% the complex agents.mmd file perfectly. This<00:41:24.000> tedious<00:41:24.640> manual<00:41:25.040> process<00:41:25.599> admittedly 00:41:26.230 --> 00:41:26.240 align:start position:0% This tedious manual process admittedly 00:41:26.240 --> 00:41:27.670 align:start position:0% This tedious manual process admittedly takes<00:41:26.560> quite<00:41:26.800> a<00:41:26.960> lot<00:41:27.119> of<00:41:27.280> valuable 00:41:27.670 --> 00:41:27.680 align:start position:0% takes quite a lot of valuable 00:41:27.680 --> 00:41:30.550 align:start position:0% takes quite a lot of valuable development<00:41:28.240> time.<00:41:29.440> We<00:41:29.839> essentially<00:41:30.240> have<00:41:30.400> to 00:41:30.550 --> 00:41:30.560 align:start position:0% development time. We essentially have to 00:41:30.560 --> 00:41:32.470 align:start position:0% development time. We essentially have to carefully<00:41:31.040> look<00:41:31.200> at<00:41:31.520> so<00:41:31.839> many<00:41:32.079> different 00:41:32.470 --> 00:41:32.480 align:start position:0% carefully look at so many different 00:41:32.480 --> 00:41:35.109 align:start position:0% carefully look at so many different distinct<00:41:33.040> things<00:41:33.839> like<00:41:34.079> our<00:41:34.319> strict<00:41:34.720> project 00:41:35.109 --> 00:41:35.119 align:start position:0% distinct things like our strict project 00:41:35.119 --> 00:41:38.150 align:start position:0% distinct things like our strict project requirements,<00:41:36.160> core<00:41:36.480> team<00:41:36.800> work<00:41:37.119> ethics,<00:41:37.920> and 00:41:38.150 --> 00:41:38.160 align:start position:0% requirements, core team work ethics, and 00:41:38.160 --> 00:41:40.230 align:start position:0% requirements, core team work ethics, and several<00:41:38.560> other<00:41:38.880> highly<00:41:39.280> detailed<00:41:39.760> technical 00:41:40.230 --> 00:41:40.240 align:start position:0% several other highly detailed technical 00:41:40.240 --> 00:41:41.910 align:start position:0% several other highly detailed technical options. 00:41:41.910 --> 00:41:41.920 align:start position:0% options. 00:41:41.920 --> 00:41:44.390 align:start position:0% options. We<00:41:42.240> absolutely<00:41:42.960> need<00:41:43.200> to<00:41:43.359> fully<00:41:43.760> know<00:41:44.000> how<00:41:44.240> to 00:41:44.390 --> 00:41:44.400 align:start position:0% We absolutely need to fully know how to 00:41:44.400 --> 00:41:47.430 align:start position:0% We absolutely need to fully know how to properly<00:41:44.800> handle<00:41:45.119> these<00:41:45.359> nuance<00:41:45.920> things.<00:41:47.280> But 00:41:47.430 --> 00:41:47.440 align:start position:0% properly handle these nuance things. But 00:41:47.440 --> 00:41:49.829 align:start position:0% properly handle these nuance things. But for<00:41:47.599> massively<00:41:48.160> big<00:41:48.400> projects,<00:41:49.280> we<00:41:49.520> only 00:41:49.829 --> 00:41:49.839 align:start position:0% for massively big projects, we only 00:41:49.839 --> 00:41:51.829 align:start position:0% for massively big projects, we only deliberately<00:41:50.480> include<00:41:50.800> our<00:41:51.040> basic<00:41:51.440> setup 00:41:51.829 --> 00:41:51.839 align:start position:0% deliberately include our basic setup 00:41:51.839 --> 00:41:54.470 align:start position:0% deliberately include our basic setup requirements<00:41:52.400> here. 00:41:54.470 --> 00:41:54.480 align:start position:0% requirements here. 00:41:54.480 --> 00:41:57.190 align:start position:0% requirements here. Moving<00:41:54.800> right<00:41:55.040> along.<00:41:56.000> Next,<00:41:56.319> we<00:41:56.560> will<00:41:56.800> deeply 00:41:57.190 --> 00:41:57.200 align:start position:0% Moving right along. Next, we will deeply 00:41:57.200 --> 00:41:59.589 align:start position:0% Moving right along. Next, we will deeply discuss<00:41:57.680> exactly<00:41:58.240> how<00:41:58.480> to<00:41:58.720> effectively<00:41:59.280> use 00:41:59.589 --> 00:41:59.599 align:start position:0% discuss exactly how to effectively use 00:41:59.599 --> 00:42:03.190 align:start position:0% discuss exactly how to effectively use this<00:41:59.920> incredibly<00:42:00.560> vital<00:42:01.440> agents.md<00:42:02.560> file<00:42:02.960> in 00:42:03.190 --> 00:42:03.200 align:start position:0% this incredibly vital agents.md file in 00:42:03.200 --> 00:42:05.750 align:start position:0% this incredibly vital agents.md file in standard<00:42:03.680> practice. 00:42:05.750 --> 00:42:05.760 align:start position:0% standard practice. 00:42:05.760 --> 00:42:08.069 align:start position:0% standard practice. Deeply<00:42:06.240> understanding<00:42:06.880> this<00:42:07.200> specific<00:42:07.760> core 00:42:08.069 --> 00:42:08.079 align:start position:0% Deeply understanding this specific core 00:42:08.079 --> 00:42:11.349 align:start position:0% Deeply understanding this specific core concept<00:42:08.880> is<00:42:09.119> an<00:42:09.359> undeniably<00:42:10.160> very<00:42:10.640> important 00:42:11.349 --> 00:42:11.359 align:start position:0% concept is an undeniably very important 00:42:11.359 --> 00:42:13.349 align:start position:0% concept is an undeniably very important foundational<00:42:12.079> part<00:42:12.400> of<00:42:12.560> the<00:42:12.880> entire 00:42:13.349 --> 00:42:13.359 align:start position:0% foundational part of the entire 00:42:13.359 --> 00:42:15.589 align:start position:0% foundational part of the entire development<00:42:13.920> process. 00:42:15.589 --> 00:42:15.599 align:start position:0% development process. 00:42:15.599 --> 00:42:18.390 align:start position:0% development process. We<00:42:15.920> absolutely<00:42:16.640> need<00:42:16.800> to<00:42:17.040> fully<00:42:17.440> know<00:42:17.839> exactly 00:42:18.390 --> 00:42:18.400 align:start position:0% We absolutely need to fully know exactly 00:42:18.400 --> 00:42:20.630 align:start position:0% We absolutely need to fully know exactly how<00:42:18.720> to<00:42:18.960> actively<00:42:19.520> create<00:42:19.839> the<00:42:20.079> underlying 00:42:20.630 --> 00:42:20.640 align:start position:0% how to actively create the underlying 00:42:20.640 --> 00:42:25.030 align:start position:0% how to actively create the underlying file<00:42:21.440> directly<00:42:22.079> from<00:42:22.400> absolute<00:42:23.040> scratch. 00:42:25.030 --> 00:42:25.040 align:start position:0% file directly from absolute scratch. 00:42:25.040 --> 00:42:27.510 align:start position:0% file directly from absolute scratch. Now<00:42:25.440> we<00:42:25.760> purposefully<00:42:26.400> transition<00:42:26.960> and<00:42:27.280> move 00:42:27.510 --> 00:42:27.520 align:start position:0% Now we purposefully transition and move 00:42:27.520 --> 00:42:29.910 align:start position:0% Now we purposefully transition and move seamlessly<00:42:28.319> right<00:42:28.640> over<00:42:28.880> to<00:42:29.119> the<00:42:29.359> very<00:42:29.599> next 00:42:29.910 --> 00:42:29.920 align:start position:0% seamlessly right over to the very next 00:42:29.920 --> 00:42:31.990 align:start position:0% seamlessly right over to the very next important<00:42:30.480> part. 00:42:31.990 --> 00:42:32.000 align:start position:0% important part. 00:42:32.000 --> 00:42:34.309 align:start position:0% important part. We<00:42:32.240> will<00:42:32.400> fundamentally<00:42:33.119> learn<00:42:33.520> exactly<00:42:34.079> how 00:42:34.309 --> 00:42:34.319 align:start position:0% We will fundamentally learn exactly how 00:42:34.319 --> 00:42:37.030 align:start position:0% We will fundamentally learn exactly how to<00:42:34.560> appropriately<00:42:35.200> handle<00:42:36.000> highly<00:42:36.480> complex 00:42:37.030 --> 00:42:37.040 align:start position:0% to appropriately handle highly complex 00:42:37.040 --> 00:42:39.990 align:start position:0% to appropriately handle highly complex things<00:42:37.760> and<00:42:38.000> deeply<00:42:38.480> understand<00:42:38.960> them<00:42:39.680> right 00:42:39.990 --> 00:42:40.000 align:start position:0% things and deeply understand them right 00:42:40.000 --> 00:42:42.309 align:start position:0% things and deeply understand them right after<00:42:40.480> actively<00:42:41.040> creating<00:42:41.440> the<00:42:41.680> foundational 00:42:42.309 --> 00:42:42.319 align:start position:0% after actively creating the foundational 00:42:42.319 --> 00:42:44.069 align:start position:0% after actively creating the foundational file. 00:42:44.069 --> 00:42:44.079 align:start position:0% file. 00:42:44.079 --> 00:42:46.710 align:start position:0% file. This<00:42:44.240> is<00:42:44.480> fundamentally<00:42:45.200> a<00:42:45.440> highly<00:42:45.920> special 00:42:46.710 --> 00:42:46.720 align:start position:0% This is fundamentally a highly special 00:42:46.720 --> 00:42:50.150 align:start position:0% This is fundamentally a highly special deeply<00:42:47.200> vital<00:42:47.760> system<00:42:48.160> instruction<00:42:48.640> file. 00:42:50.150 --> 00:42:50.160 align:start position:0% deeply vital system instruction file. 00:42:50.160 --> 00:42:52.630 align:start position:0% deeply vital system instruction file. It<00:42:50.400> consistently<00:42:51.040> provides<00:42:51.520> invaluable<00:42:52.240> deep 00:42:52.630 --> 00:42:52.640 align:start position:0% It consistently provides invaluable deep 00:42:52.640 --> 00:42:55.109 align:start position:0% It consistently provides invaluable deep guidance<00:42:53.440> and<00:42:53.680> much<00:42:54.000> needed<00:42:54.400> environmental 00:42:55.109 --> 00:42:55.119 align:start position:0% guidance and much needed environmental 00:42:55.119 --> 00:42:58.790 align:start position:0% guidance and much needed environmental context<00:42:55.760> directly<00:42:56.319> for<00:42:56.560> our<00:42:56.800> automated<00:42:57.359> work. 00:42:58.790 --> 00:42:58.800 align:start position:0% context directly for our automated work. 00:42:58.800 --> 00:43:00.710 align:start position:0% context directly for our automated work. It<00:42:59.040> can<00:42:59.200> absolutely<00:42:59.839> also<00:43:00.240> be<00:43:00.400> used 00:43:00.710 --> 00:43:00.720 align:start position:0% It can absolutely also be used 00:43:00.720 --> 00:43:03.510 align:start position:0% It can absolutely also be used incredibly<00:43:01.359> effectively,<00:43:02.560> exactly<00:43:03.040> like<00:43:03.200> a 00:43:03.510 --> 00:43:03.520 align:start position:0% incredibly effectively, exactly like a 00:43:03.520 --> 00:43:06.550 align:start position:0% incredibly effectively, exactly like a traditional<00:43:03.920> readme<00:43:04.480> developer<00:43:04.960> file.<00:43:06.319> You 00:43:06.550 --> 00:43:06.560 align:start position:0% traditional readme developer file. You 00:43:06.560 --> 00:43:08.470 align:start position:0% traditional readme developer file. You might<00:43:06.720> vividly<00:43:07.280> remember<00:43:07.680> that<00:43:08.000> standard 00:43:08.470 --> 00:43:08.480 align:start position:0% might vividly remember that standard 00:43:08.480 --> 00:43:10.870 align:start position:0% might vividly remember that standard software<00:43:08.880> developers<00:43:09.839> constantly<00:43:10.480> use 00:43:10.870 --> 00:43:10.880 align:start position:0% software developers constantly use 00:43:10.880 --> 00:43:14.069 align:start position:0% software developers constantly use structured<00:43:11.359> readme<00:43:11.839> files.<00:43:13.280> In<00:43:13.520> the<00:43:13.760> exact 00:43:14.069 --> 00:43:14.079 align:start position:0% structured readme files. In the exact 00:43:14.079 --> 00:43:17.349 align:start position:0% structured readme files. In the exact same<00:43:14.319> way,<00:43:14.880> we<00:43:15.119> can<00:43:15.280> use<00:43:15.520> this<00:43:15.760> file.<00:43:16.880> I<00:43:17.200> have 00:43:17.349 --> 00:43:17.359 align:start position:0% same way, we can use this file. I have 00:43:17.359 --> 00:43:20.230 align:start position:0% same way, we can use this file. I have created<00:43:17.680> a<00:43:17.920> basic<00:43:18.400> agents.mmd<00:43:19.520> file,<00:43:20.000> but 00:43:20.230 --> 00:43:20.240 align:start position:0% created a basic agents.mmd file, but 00:43:20.240 --> 00:43:22.870 align:start position:0% created a basic agents.mmd file, but incredibly<00:43:21.280> we<00:43:21.520> can<00:43:21.680> undoubtedly<00:43:22.480> also 00:43:22.870 --> 00:43:22.880 align:start position:0% incredibly we can undoubtedly also 00:43:22.880 --> 00:43:25.750 align:start position:0% incredibly we can undoubtedly also meticulously<00:43:23.680> make<00:43:24.000> a<00:43:24.240> highly<00:43:24.720> reusable 00:43:25.750 --> 00:43:25.760 align:start position:0% meticulously make a highly reusable 00:43:25.760 --> 00:43:28.470 align:start position:0% meticulously make a highly reusable foundational<00:43:26.480> agents.mmd<00:43:27.760> configuration 00:43:28.470 --> 00:43:28.480 align:start position:0% foundational agents.mmd configuration 00:43:28.480 --> 00:43:31.750 align:start position:0% foundational agents.mmd configuration template<00:43:29.359> right<00:43:29.599> here<00:43:29.760> in<00:43:30.000> the<00:43:30.160> workspace. 00:43:31.750 --> 00:43:31.760 align:start position:0% template right here in the workspace. 00:43:31.760 --> 00:43:34.069 align:start position:0% template right here in the workspace. We<00:43:32.000> can<00:43:32.160> comfortably<00:43:32.720> and<00:43:32.960> securely<00:43:33.520> include 00:43:34.069 --> 00:43:34.079 align:start position:0% We can comfortably and securely include 00:43:34.079 --> 00:43:35.829 align:start position:0% We can comfortably and securely include absolutely<00:43:34.800> all<00:43:35.040> of<00:43:35.200> our<00:43:35.440> strict 00:43:35.829 --> 00:43:35.839 align:start position:0% absolutely all of our strict 00:43:35.839 --> 00:43:37.349 align:start position:0% absolutely all of our strict foundational<00:43:36.560> base<00:43:36.880> development 00:43:37.349 --> 00:43:37.359 align:start position:0% foundational base development 00:43:37.359 --> 00:43:40.550 align:start position:0% foundational base development requirements<00:43:38.000> firmly<00:43:38.480> inside<00:43:38.880> it.<00:43:40.240> This 00:43:40.550 --> 00:43:40.560 align:start position:0% requirements firmly inside it. This 00:43:40.560 --> 00:43:43.270 align:start position:0% requirements firmly inside it. This proactive<00:43:41.200> step<00:43:41.760> will<00:43:42.079> flawlessly<00:43:42.720> kickstart 00:43:43.270 --> 00:43:43.280 align:start position:0% proactive step will flawlessly kickstart 00:43:43.280 --> 00:43:46.390 align:start position:0% proactive step will flawlessly kickstart our<00:43:43.520> broader<00:43:43.920> automation<00:43:44.480> work<00:43:44.800> immediately. 00:43:46.390 --> 00:43:46.400 align:start position:0% our broader automation work immediately. 00:43:46.400 --> 00:43:48.390 align:start position:0% our broader automation work immediately. I<00:43:46.720> will<00:43:46.880> gladly<00:43:47.280> proceed<00:43:47.599> to<00:43:47.760> show<00:43:47.920> you<00:43:48.079> an 00:43:48.390 --> 00:43:48.400 align:start position:0% I will gladly proceed to show you an 00:43:48.400 --> 00:43:50.309 align:start position:0% I will gladly proceed to show you an excellent<00:43:48.960> highly<00:43:49.359> structured<00:43:49.760> example. 00:43:50.309 --> 00:43:50.319 align:start position:0% excellent highly structured example. 00:43:50.319 --> 00:43:52.150 align:start position:0% excellent highly structured example. Right<00:43:50.640> now 00:43:52.150 --> 00:43:52.160 align:start position:0% Right now 00:43:52.160 --> 00:43:54.630 align:start position:0% Right now I<00:43:52.400> will<00:43:52.640> purposely<00:43:53.200> open<00:43:53.440> up<00:43:53.760> Microsoft<00:43:54.240> Word 00:43:54.630 --> 00:43:54.640 align:start position:0% I will purposely open up Microsoft Word 00:43:54.640 --> 00:43:57.910 align:start position:0% I will purposely open up Microsoft Word or<00:43:54.880> a<00:43:55.119> standard<00:43:55.520> blank<00:43:55.920> dock<00:43:56.240> text<00:43:56.560> document. 00:43:57.910 --> 00:43:57.920 align:start position:0% or a standard blank dock text document. 00:43:57.920 --> 00:43:59.990 align:start position:0% or a standard blank dock text document. I<00:43:58.160> am<00:43:58.319> deliberately<00:43:58.880> using<00:43:59.119> a<00:43:59.359> blank<00:43:59.599> doc 00:43:59.990 --> 00:44:00.000 align:start position:0% I am deliberately using a blank doc 00:44:00.000 --> 00:44:02.390 align:start position:0% I am deliberately using a blank doc right<00:44:00.160> now<00:44:00.800> strictly<00:44:01.200> so<00:44:01.440> we<00:44:01.680> can<00:44:01.839> comfortably 00:44:02.390 --> 00:44:02.400 align:start position:0% right now strictly so we can comfortably 00:44:02.400 --> 00:44:04.950 align:start position:0% right now strictly so we can comfortably start<00:44:02.640> a<00:44:02.960> fresh<00:44:03.440> entirely<00:44:04.079> new<00:44:04.560> empty 00:44:04.950 --> 00:44:04.960 align:start position:0% start a fresh entirely new empty 00:44:04.960 --> 00:44:06.630 align:start position:0% start a fresh entirely new empty document. 00:44:06.630 --> 00:44:06.640 align:start position:0% document. 00:44:06.640 --> 00:44:09.349 align:start position:0% document. Here<00:44:07.359> you<00:44:07.599> can<00:44:07.760> very<00:44:08.079> clearly<00:44:08.480> see<00:44:08.880> exactly 00:44:09.349 --> 00:44:09.359 align:start position:0% Here you can very clearly see exactly 00:44:09.359 --> 00:44:11.430 align:start position:0% Here you can very clearly see exactly what<00:44:09.680> critical<00:44:10.240> structural<00:44:10.800> things<00:44:11.119> are 00:44:11.430 --> 00:44:11.440 align:start position:0% what critical structural things are 00:44:11.440 --> 00:44:14.470 align:start position:0% what critical structural things are highly<00:44:11.760> recommended<00:44:12.319> and<00:44:12.560> available. 00:44:14.470 --> 00:44:14.480 align:start position:0% highly recommended and available. 00:44:14.480 --> 00:44:17.190 align:start position:0% highly recommended and available. First,<00:44:15.200> we<00:44:15.520> logically<00:44:16.079> have<00:44:16.319> the<00:44:16.560> high-level 00:44:17.190 --> 00:44:17.200 align:start position:0% First, we logically have the high-level 00:44:17.200 --> 00:44:20.150 align:start position:0% First, we logically have the high-level project<00:44:17.599> overview<00:44:18.079> section.<00:44:19.440> This<00:44:19.760> clearly 00:44:20.150 --> 00:44:20.160 align:start position:0% project overview section. This clearly 00:44:20.160 --> 00:44:22.550 align:start position:0% project overview section. This clearly tells<00:44:20.560> us<00:44:20.880> exactly<00:44:21.359> what<00:44:21.680> core<00:44:22.000> deliverables 00:44:22.550 --> 00:44:22.560 align:start position:0% tells us exactly what core deliverables 00:44:22.560 --> 00:44:25.349 align:start position:0% tells us exactly what core deliverables we<00:44:22.800> strictly<00:44:23.200> need<00:44:23.359> in<00:44:23.599> the<00:44:23.760> project. 00:44:25.349 --> 00:44:25.359 align:start position:0% we strictly need in the project. 00:44:25.359 --> 00:44:27.990 align:start position:0% we strictly need in the project. Next,<00:44:26.160> we<00:44:26.400> definitely<00:44:26.880> have<00:44:27.119> the<00:44:27.280> strict<00:44:27.680> team 00:44:27.990 --> 00:44:28.000 align:start position:0% Next, we definitely have the strict team 00:44:28.000 --> 00:44:30.230 align:start position:0% Next, we definitely have the strict team coding<00:44:28.480> standards<00:44:28.880> that<00:44:29.119> we<00:44:29.359> must<00:44:29.599> absolutely 00:44:30.230 --> 00:44:30.240 align:start position:0% coding standards that we must absolutely 00:44:30.240 --> 00:44:31.910 align:start position:0% coding standards that we must absolutely follow. 00:44:31.910 --> 00:44:31.920 align:start position:0% follow. 00:44:31.920 --> 00:44:34.150 align:start position:0% follow. After<00:44:32.240> that,<00:44:32.880> we<00:44:33.119> discuss<00:44:33.520> repository 00:44:34.150 --> 00:44:34.160 align:start position:0% After that, we discuss repository 00:44:34.160 --> 00:44:36.630 align:start position:0% After that, we discuss repository structures,<00:44:35.119> testing<00:44:35.520> requirements, 00:44:36.630 --> 00:44:36.640 align:start position:0% structures, testing requirements, 00:44:36.640 --> 00:44:40.790 align:start position:0% structures, testing requirements, security<00:44:37.200> rules,<00:44:37.920> and<00:44:38.240> large<00:44:38.640> scale<00:44:38.960> systems. 00:44:40.790 --> 00:44:40.800 align:start position:0% security rules, and large scale systems. 00:44:40.800 --> 00:44:42.630 align:start position:0% security rules, and large scale systems. We<00:44:41.040> will<00:44:41.200> practically<00:44:41.760> use<00:44:42.000> a<00:44:42.319> fully 00:44:42.630 --> 00:44:42.640 align:start position:0% We will practically use a fully 00:44:42.640 --> 00:44:45.510 align:start position:0% We will practically use a fully functional,<00:44:43.599> highly<00:44:44.160> complete<00:44:44.720> overarching 00:44:45.510 --> 00:44:45.520 align:start position:0% functional, highly complete overarching 00:44:45.520 --> 00:44:48.390 align:start position:0% functional, highly complete overarching working<00:44:45.920> system<00:44:46.240> here.<00:44:47.680> Our<00:44:47.920> strictly 00:44:48.390 --> 00:44:48.400 align:start position:0% working system here. Our strictly 00:44:48.400 --> 00:44:50.790 align:start position:0% working system here. Our strictly prohibited,<00:44:49.359> highly<00:44:49.839> restricted<00:44:50.400> system 00:44:50.790 --> 00:44:50.800 align:start position:0% prohibited, highly restricted system 00:44:50.800 --> 00:44:53.190 align:start position:0% prohibited, highly restricted system areas<00:44:51.440> will<00:44:51.839> absolutely<00:44:52.560> also<00:44:52.960> be 00:44:53.190 --> 00:44:53.200 align:start position:0% areas will absolutely also be 00:44:53.200 --> 00:44:55.670 align:start position:0% areas will absolutely also be meticulously<00:44:54.160> explicitly<00:44:54.880> listed<00:44:55.359> right 00:44:55.670 --> 00:44:55.680 align:start position:0% meticulously explicitly listed right 00:44:55.680 --> 00:44:58.470 align:start position:0% meticulously explicitly listed right here<00:44:55.920> for<00:44:56.160> immense<00:44:56.640> safety. 00:44:58.470 --> 00:44:58.480 align:start position:0% here for immense safety. 00:44:58.480 --> 00:45:02.069 align:start position:0% here for immense safety. Then<00:44:59.359> our<00:44:59.680> highly<00:45:00.079> nuanced,<00:45:00.880> deeply<00:45:01.359> specific 00:45:02.069 --> 00:45:02.079 align:start position:0% Then our highly nuanced, deeply specific 00:45:02.079 --> 00:45:04.870 align:start position:0% Then our highly nuanced, deeply specific primary<00:45:02.640> AI<00:45:03.119> operational<00:45:03.760> instructions<00:45:04.640> will 00:45:04.870 --> 00:45:04.880 align:start position:0% primary AI operational instructions will 00:45:04.880 --> 00:45:07.670 align:start position:0% primary AI operational instructions will be<00:45:05.040> thoroughly<00:45:05.520> included<00:45:06.000> next. 00:45:07.670 --> 00:45:07.680 align:start position:0% be thoroughly included next. 00:45:07.680 --> 00:45:09.990 align:start position:0% be thoroughly included next. Right<00:45:08.000> after<00:45:08.319> all<00:45:08.560> the<00:45:08.800> comprehensive<00:45:09.599> AI 00:45:09.990 --> 00:45:10.000 align:start position:0% Right after all the comprehensive AI 00:45:10.000 --> 00:45:11.990 align:start position:0% Right after all the comprehensive AI baseline<00:45:10.560> instructions,<00:45:11.599> we<00:45:11.839> will 00:45:11.990 --> 00:45:12.000 align:start position:0% baseline instructions, we will 00:45:12.000 --> 00:45:14.550 align:start position:0% baseline instructions, we will seamlessly<00:45:12.640> have<00:45:12.960> all<00:45:13.280> our<00:45:13.520> broader<00:45:14.160> full 00:45:14.550 --> 00:45:14.560 align:start position:0% seamlessly have all our broader full 00:45:14.560 --> 00:45:16.870 align:start position:0% seamlessly have all our broader full feature<00:45:15.040> architectural<00:45:15.839> options<00:45:16.319> carefully 00:45:16.870 --> 00:45:16.880 align:start position:0% feature architectural options carefully 00:45:16.880 --> 00:45:18.630 align:start position:0% feature architectural options carefully documented. 00:45:18.630 --> 00:45:18.640 align:start position:0% documented. 00:45:18.640 --> 00:45:20.550 align:start position:0% documented. This<00:45:18.880> is<00:45:19.119> essentially<00:45:19.599> exactly<00:45:20.079> what<00:45:20.319> we 00:45:20.550 --> 00:45:20.560 align:start position:0% This is essentially exactly what we 00:45:20.560 --> 00:45:23.270 align:start position:0% This is essentially exactly what we traditionally<00:45:21.040> call<00:45:21.599> a<00:45:21.920> comprehensive<00:45:22.960> well 00:45:23.270 --> 00:45:23.280 align:start position:0% traditionally call a comprehensive well 00:45:23.280 --> 00:45:25.349 align:start position:0% traditionally call a comprehensive well ststructured<00:45:23.839> readme<00:45:24.319> file<00:45:24.640> in<00:45:24.960> standard 00:45:25.349 --> 00:45:25.359 align:start position:0% ststructured readme file in standard 00:45:25.359 --> 00:45:26.870 align:start position:0% ststructured readme file in standard development. 00:45:26.870 --> 00:45:26.880 align:start position:0% development. 00:45:26.880 --> 00:45:29.510 align:start position:0% development. It<00:45:27.200> practically<00:45:27.760> has<00:45:28.160> all<00:45:28.480> our<00:45:28.880> complete 00:45:29.510 --> 00:45:29.520 align:start position:0% It practically has all our complete 00:45:29.520 --> 00:45:32.069 align:start position:0% It practically has all our complete strict<00:45:29.920> baseline<00:45:30.480> instructions<00:45:31.599> deeply 00:45:32.069 --> 00:45:32.079 align:start position:0% strict baseline instructions deeply 00:45:32.079 --> 00:45:34.390 align:start position:0% strict baseline instructions deeply hardcoded<00:45:32.800> and<00:45:33.040> built<00:45:33.359> directly<00:45:33.839> right<00:45:34.079> into 00:45:34.390 --> 00:45:34.400 align:start position:0% hardcoded and built directly right into 00:45:34.400 --> 00:45:37.589 align:start position:0% hardcoded and built directly right into it.<00:45:35.839> After<00:45:36.160> this<00:45:36.400> section<00:45:36.720> is<00:45:36.960> successfully 00:45:37.589 --> 00:45:37.599 align:start position:0% it. After this section is successfully 00:45:37.599 --> 00:45:40.309 align:start position:0% it. After this section is successfully completed,<00:45:38.640> the<00:45:38.880> very<00:45:39.200> next<00:45:39.760> essential 00:45:40.309 --> 00:45:40.319 align:start position:0% completed, the very next essential 00:45:40.319 --> 00:45:43.109 align:start position:0% completed, the very next essential technical<00:45:40.880> thing<00:45:41.280> dynamically<00:45:41.920> available<00:45:42.800> is 00:45:43.109 --> 00:45:43.119 align:start position:0% technical thing dynamically available is 00:45:43.119 --> 00:45:44.950 align:start position:0% technical thing dynamically available is dealing<00:45:43.440> with<00:45:43.599> our<00:45:43.839> sensitive<00:45:44.400> backend 00:45:44.950 --> 00:45:44.960 align:start position:0% dealing with our sensitive backend 00:45:44.960 --> 00:45:47.190 align:start position:0% dealing with our sensitive backend environment<00:45:45.520> variables. 00:45:47.190 --> 00:45:47.200 align:start position:0% environment variables. 00:45:47.200 --> 00:45:49.750 align:start position:0% environment variables. We<00:45:47.359> will<00:45:47.599> deeply<00:45:48.079> see<00:45:48.400> precisely<00:45:49.119> how<00:45:49.359> we<00:45:49.520> can 00:45:49.750 --> 00:45:49.760 align:start position:0% We will deeply see precisely how we can 00:45:49.760 --> 00:45:52.550 align:start position:0% We will deeply see precisely how we can effectively<00:45:50.880> securely<00:45:51.440> manage<00:45:51.760> these<00:45:52.160> highly 00:45:52.550 --> 00:45:52.560 align:start position:0% effectively securely manage these highly 00:45:52.560 --> 00:45:57.750 align:start position:0% effectively securely manage these highly critical<00:45:53.040> system<00:45:53.359> environment<00:45:53.920> variables. 00:45:57.750 --> 00:45:57.760 align:start position:0% 00:45:57.760 --> 00:46:00.390 align:start position:0% Now<00:45:58.319> our<00:45:58.640> next<00:45:59.119> incredibly<00:45:59.839> critical 00:46:00.390 --> 00:46:00.400 align:start position:0% Now our next incredibly critical 00:46:00.400 --> 00:46:02.790 align:start position:0% Now our next incredibly critical technical<00:46:00.880> discussion<00:46:01.680> is<00:46:02.000> primarily<00:46:02.560> about 00:46:02.790 --> 00:46:02.800 align:start position:0% technical discussion is primarily about 00:46:02.800 --> 00:46:05.109 align:start position:0% technical discussion is primarily about handling<00:46:03.359> robust<00:46:03.920> backend<00:46:04.480> environment 00:46:05.109 --> 00:46:05.119 align:start position:0% handling robust backend environment 00:46:05.119 --> 00:46:06.950 align:start position:0% handling robust backend environment variables. 00:46:06.950 --> 00:46:06.960 align:start position:0% variables. 00:46:06.960 --> 00:46:09.589 align:start position:0% variables. These<00:46:07.280> are<00:46:07.520> essentially<00:46:08.160> highly<00:46:08.640> dynamic 00:46:09.589 --> 00:46:09.599 align:start position:0% These are essentially highly dynamic 00:46:09.599 --> 00:46:11.910 align:start position:0% These are essentially highly dynamic configurable<00:46:10.319> key<00:46:10.640> values<00:46:11.119> operating<00:46:11.599> in<00:46:11.760> the 00:46:11.910 --> 00:46:11.920 align:start position:0% configurable key values operating in the 00:46:11.920 --> 00:46:14.630 align:start position:0% configurable key values operating in the background.<00:46:13.280> We<00:46:13.520> can<00:46:13.680> actively<00:46:14.160> store<00:46:14.400> them 00:46:14.630 --> 00:46:14.640 align:start position:0% background. We can actively store them 00:46:14.640 --> 00:46:17.190 align:start position:0% background. We can actively store them either<00:46:15.040> directly<00:46:15.599> or<00:46:15.920> indirectly<00:46:16.960> deep 00:46:17.190 --> 00:46:17.200 align:start position:0% either directly or indirectly deep 00:46:17.200 --> 00:46:19.190 align:start position:0% either directly or indirectly deep within<00:46:17.520> our<00:46:17.760> underlying<00:46:18.319> operating<00:46:18.800> system 00:46:19.190 --> 00:46:19.200 align:start position:0% within our underlying operating system 00:46:19.200 --> 00:46:21.190 align:start position:0% within our underlying operating system infrastructure. 00:46:21.190 --> 00:46:21.200 align:start position:0% infrastructure. 00:46:21.200 --> 00:46:23.430 align:start position:0% infrastructure. we<00:46:21.440> can<00:46:21.680> comfortably<00:46:22.160> and<00:46:22.480> securely<00:46:23.119> utilize 00:46:23.430 --> 00:46:23.440 align:start position:0% we can comfortably and securely utilize 00:46:23.440 --> 00:46:25.670 align:start position:0% we can comfortably and securely utilize them<00:46:23.680> later<00:46:24.079> for<00:46:24.319> absolutely<00:46:25.119> all<00:46:25.359> of<00:46:25.520> our 00:46:25.670 --> 00:46:25.680 align:start position:0% them later for absolutely all of our 00:46:25.680 --> 00:46:29.109 align:start position:0% them later for absolutely all of our other<00:46:26.000> automated<00:46:26.720> complex<00:46:27.200> coding<00:46:27.599> tasks. 00:46:29.109 --> 00:46:29.119 align:start position:0% other automated complex coding tasks. 00:46:29.119 --> 00:46:32.390 align:start position:0% other automated complex coding tasks. Usually<00:46:30.079> we<00:46:30.400> deeply<00:46:30.800> involve<00:46:31.200> our<00:46:31.520> complete 00:46:32.390 --> 00:46:32.400 align:start position:0% Usually we deeply involve our complete 00:46:32.400 --> 00:46:34.710 align:start position:0% Usually we deeply involve our complete highly<00:46:32.880> systematic<00:46:33.680> overall<00:46:34.160> workflow 00:46:34.710 --> 00:46:34.720 align:start position:0% highly systematic overall workflow 00:46:34.720 --> 00:46:37.910 align:start position:0% highly systematic overall workflow process<00:46:35.359> directly<00:46:35.920> here<00:46:36.720> to<00:46:37.040> explicitly<00:46:37.680> see 00:46:37.910 --> 00:46:37.920 align:start position:0% process directly here to explicitly see 00:46:37.920 --> 00:46:40.790 align:start position:0% process directly here to explicitly see exactly<00:46:38.400> how<00:46:38.720> a<00:46:38.960> full<00:46:39.680> robust<00:46:40.319> software 00:46:40.790 --> 00:46:40.800 align:start position:0% exactly how a full robust software 00:46:40.800 --> 00:46:43.910 align:start position:0% exactly how a full robust software system<00:46:41.119> is<00:46:41.440> successfully<00:46:42.079> constructed. 00:46:43.910 --> 00:46:43.920 align:start position:0% system is successfully constructed. 00:46:43.920 --> 00:46:46.230 align:start position:0% system is successfully constructed. These<00:46:44.240> are<00:46:44.400> highly<00:46:44.800> dynamic<00:46:45.359> backend<00:46:45.920> key 00:46:46.230 --> 00:46:46.240 align:start position:0% These are highly dynamic backend key 00:46:46.240 --> 00:46:48.630 align:start position:0% These are highly dynamic backend key values<00:46:46.960> that<00:46:47.200> are<00:46:47.359> stored<00:46:47.760> strictly<00:46:48.319> and 00:46:48.630 --> 00:46:48.640 align:start position:0% values that are stored strictly and 00:46:48.640 --> 00:46:50.710 align:start position:0% values that are stored strictly and directly<00:46:49.200> inside<00:46:49.520> the<00:46:49.760> native<00:46:50.160> operating 00:46:50.710 --> 00:46:50.720 align:start position:0% directly inside the native operating 00:46:50.720 --> 00:46:54.069 align:start position:0% directly inside the native operating system,<00:46:51.760> kept<00:46:52.240> entirely<00:46:52.880> safely<00:46:53.440> outside<00:46:53.920> of 00:46:54.069 --> 00:46:54.079 align:start position:0% system, kept entirely safely outside of 00:46:54.079 --> 00:46:57.510 align:start position:0% system, kept entirely safely outside of our<00:46:54.319> vulnerable<00:46:55.040> raw<00:46:55.440> source<00:46:55.760> code<00:46:56.079> files. 00:46:57.510 --> 00:46:57.520 align:start position:0% our vulnerable raw source code files. 00:46:57.520 --> 00:47:00.309 align:start position:0% our vulnerable raw source code files. They<00:46:57.839> heavily<00:46:58.319> detect<00:46:59.040> and<00:46:59.359> dictate 00:47:00.309 --> 00:47:00.319 align:start position:0% They heavily detect and dictate 00:47:00.319 --> 00:47:02.230 align:start position:0% They heavily detect and dictate precisely<00:47:00.880> how<00:47:01.119> the<00:47:01.359> running<00:47:01.680> process 00:47:02.230 --> 00:47:02.240 align:start position:0% precisely how the running process 00:47:02.240 --> 00:47:04.630 align:start position:0% precisely how the running process fundamentally<00:47:03.040> behaves. 00:47:04.630 --> 00:47:04.640 align:start position:0% fundamentally behaves. 00:47:04.640 --> 00:47:06.630 align:start position:0% fundamentally behaves. This<00:47:04.960> brilliant<00:47:05.440> system<00:47:05.920> effortlessly 00:47:06.630 --> 00:47:06.640 align:start position:0% This brilliant system effortlessly 00:47:06.640 --> 00:47:09.349 align:start position:0% This brilliant system effortlessly allows<00:47:07.040> developers<00:47:07.839> to<00:47:08.160> incredibly<00:47:08.800> safely 00:47:09.349 --> 00:47:09.359 align:start position:0% allows developers to incredibly safely 00:47:09.359 --> 00:47:11.510 align:start position:0% allows developers to incredibly safely store<00:47:10.079> highly<00:47:10.480> sensitive<00:47:11.040> security 00:47:11.510 --> 00:47:11.520 align:start position:0% store highly sensitive security 00:47:11.520 --> 00:47:13.270 align:start position:0% store highly sensitive security credentials. 00:47:13.270 --> 00:47:13.280 align:start position:0% credentials. 00:47:13.280 --> 00:47:16.630 align:start position:0% credentials. What<00:47:13.599> exactly<00:47:14.079> are<00:47:14.400> sensitive<00:47:14.960> credentials? 00:47:16.630 --> 00:47:16.640 align:start position:0% What exactly are sensitive credentials? 00:47:16.640 --> 00:47:19.670 align:start position:0% What exactly are sensitive credentials? It<00:47:16.880> is<00:47:17.040> highly<00:47:17.440> vital<00:47:17.760> to<00:47:18.000> see<00:47:18.160> this<00:47:18.400> clearly. 00:47:19.670 --> 00:47:19.680 align:start position:0% It is highly vital to see this clearly. 00:47:19.680 --> 00:47:21.990 align:start position:0% It is highly vital to see this clearly. If<00:47:19.839> we<00:47:20.079> fail<00:47:20.319> to<00:47:20.560> understand<00:47:20.960> this,<00:47:21.440> our<00:47:21.680> work 00:47:21.990 --> 00:47:22.000 align:start position:0% If we fail to understand this, our work 00:47:22.000 --> 00:47:23.750 align:start position:0% If we fail to understand this, our work suffers. 00:47:23.750 --> 00:47:23.760 align:start position:0% suffers. 00:47:23.760 --> 00:47:26.150 align:start position:0% suffers. Sometimes<00:47:24.400> developers<00:47:24.960> are<00:47:25.200> understandably 00:47:26.150 --> 00:47:26.160 align:start position:0% Sometimes developers are understandably 00:47:26.160 --> 00:47:28.470 align:start position:0% Sometimes developers are understandably incredibly<00:47:26.880> afraid<00:47:27.440> that<00:47:27.760> their<00:47:28.079> highly 00:47:28.470 --> 00:47:28.480 align:start position:0% incredibly afraid that their highly 00:47:28.480 --> 00:47:30.470 align:start position:0% incredibly afraid that their highly sensitive<00:47:29.200> personal<00:47:29.680> or<00:47:30.000> corporate 00:47:30.470 --> 00:47:30.480 align:start position:0% sensitive personal or corporate 00:47:30.480 --> 00:47:33.030 align:start position:0% sensitive personal or corporate information<00:47:31.440> will<00:47:31.760> eventually<00:47:32.480> accidentally 00:47:33.030 --> 00:47:33.040 align:start position:0% information will eventually accidentally 00:47:33.040 --> 00:47:36.390 align:start position:0% information will eventually accidentally leak<00:47:33.359> to<00:47:33.520> the<00:47:33.680> dangerous<00:47:34.160> public<00:47:34.640> internet. 00:47:36.390 --> 00:47:36.400 align:start position:0% leak to the dangerous public internet. 00:47:36.400 --> 00:47:38.630 align:start position:0% leak to the dangerous public internet. Why<00:47:36.720> exactly<00:47:37.280> does<00:47:37.440> this<00:47:37.760> enormous<00:47:38.319> fear 00:47:38.630 --> 00:47:38.640 align:start position:0% Why exactly does this enormous fear 00:47:38.640 --> 00:47:40.550 align:start position:0% Why exactly does this enormous fear exist? 00:47:40.550 --> 00:47:40.560 align:start position:0% exist? 00:47:40.560 --> 00:47:42.230 align:start position:0% exist? basically<00:47:41.119> because<00:47:41.440> our<00:47:41.760> complete 00:47:42.230 --> 00:47:42.240 align:start position:0% basically because our complete 00:47:42.240 --> 00:47:44.790 align:start position:0% basically because our complete interconnected<00:47:43.119> development<00:47:43.680> environment 00:47:44.790 --> 00:47:44.800 align:start position:0% interconnected development environment 00:47:44.800 --> 00:47:46.870 align:start position:0% interconnected development environment inherently<00:47:45.520> has<00:47:45.760> some<00:47:46.000> deeply<00:47:46.480> guarded 00:47:46.870 --> 00:47:46.880 align:start position:0% inherently has some deeply guarded 00:47:46.880 --> 00:47:48.710 align:start position:0% inherently has some deeply guarded secrets. 00:47:48.710 --> 00:47:48.720 align:start position:0% secrets. 00:47:48.720 --> 00:47:50.790 align:start position:0% secrets. These<00:47:49.119> highly<00:47:49.599> confidential<00:47:50.160> items 00:47:50.790 --> 00:47:50.800 align:start position:0% These highly confidential items 00:47:50.800 --> 00:47:52.870 align:start position:0% These highly confidential items definitely<00:47:51.280> include<00:47:51.760> things<00:47:52.000> like<00:47:52.400> private 00:47:52.870 --> 00:47:52.880 align:start position:0% definitely include things like private 00:47:52.880 --> 00:47:55.510 align:start position:0% definitely include things like private API<00:47:53.359> keys,<00:47:54.319> secure<00:47:54.800> admin<00:47:55.200> account 00:47:55.510 --> 00:47:55.520 align:start position:0% API keys, secure admin account 00:47:55.520 --> 00:47:58.069 align:start position:0% API keys, secure admin account usernames,<00:47:56.480> and<00:47:56.800> highly<00:47:57.200> encrypted<00:47:57.680> user 00:47:58.069 --> 00:47:58.079 align:start position:0% usernames, and highly encrypted user 00:47:58.079 --> 00:47:59.829 align:start position:0% usernames, and highly encrypted user passwords. 00:47:59.829 --> 00:47:59.839 align:start position:0% passwords. 00:47:59.839 --> 00:48:02.069 align:start position:0% passwords. We<00:48:00.240> absolutely<00:48:00.960> have<00:48:01.200> to<00:48:01.359> carefully<00:48:01.920> look 00:48:02.069 --> 00:48:02.079 align:start position:0% We absolutely have to carefully look 00:48:02.079 --> 00:48:05.190 align:start position:0% We absolutely have to carefully look closely<00:48:02.480> at<00:48:02.640> them<00:48:02.800> and<00:48:03.119> protect<00:48:03.440> them. 00:48:05.190 --> 00:48:05.200 align:start position:0% closely at them and protect them. 00:48:05.200 --> 00:48:07.510 align:start position:0% closely at them and protect them. Now<00:48:05.520> we<00:48:05.760> officially<00:48:06.240> pivot<00:48:06.640> to<00:48:06.880> selectively 00:48:07.510 --> 00:48:07.520 align:start position:0% Now we officially pivot to selectively 00:48:07.520 --> 00:48:09.910 align:start position:0% Now we officially pivot to selectively talk<00:48:07.760> about<00:48:07.920> the<00:48:08.160> massive<00:48:09.040> overarching 00:48:09.910 --> 00:48:09.920 align:start position:0% talk about the massive overarching 00:48:09.920 --> 00:48:12.870 align:start position:0% talk about the massive overarching enterprise<00:48:10.560> operational<00:48:11.200> level. 00:48:12.870 --> 00:48:12.880 align:start position:0% enterprise operational level. 00:48:12.880 --> 00:48:14.790 align:start position:0% enterprise operational level. What<00:48:13.200> exactly<00:48:13.680> inherently<00:48:14.319> happens 00:48:14.790 --> 00:48:14.800 align:start position:0% What exactly inherently happens 00:48:14.800 --> 00:48:16.630 align:start position:0% What exactly inherently happens operating<00:48:15.280> at<00:48:15.440> the<00:48:15.599> massive<00:48:16.079> enterprise 00:48:16.630 --> 00:48:16.640 align:start position:0% operating at the massive enterprise 00:48:16.640 --> 00:48:18.710 align:start position:0% operating at the massive enterprise scale<00:48:16.960> level? 00:48:18.710 --> 00:48:18.720 align:start position:0% scale level? 00:48:18.720 --> 00:48:21.109 align:start position:0% scale level? Let<00:48:18.960> us<00:48:19.200> quickly<00:48:19.599> intentionally<00:48:20.400> open<00:48:20.720> up<00:48:20.880> a 00:48:21.109 --> 00:48:21.119 align:start position:0% Let us quickly intentionally open up a 00:48:21.119 --> 00:48:24.950 align:start position:0% Let us quickly intentionally open up a brand<00:48:21.359> new<00:48:21.920> fresh<00:48:22.480> isolated<00:48:23.119> chat<00:48:23.440> window 00:48:24.950 --> 00:48:24.960 align:start position:0% brand new fresh isolated chat window 00:48:24.960 --> 00:48:26.950 align:start position:0% brand new fresh isolated chat window at<00:48:25.200> the<00:48:25.359> highest<00:48:25.680> enterprise<00:48:26.240> level. 00:48:26.950 --> 00:48:26.960 align:start position:0% at the highest enterprise level. 00:48:26.960 --> 00:48:29.270 align:start position:0% at the highest enterprise level. Actively<00:48:27.599> managing<00:48:28.160> profound<00:48:28.720> structural 00:48:29.270 --> 00:48:29.280 align:start position:0% Actively managing profound structural 00:48:29.280 --> 00:48:32.069 align:start position:0% Actively managing profound structural secrets<00:48:29.760> properly<00:48:30.559> is<00:48:30.960> absolutely<00:48:31.599> critical 00:48:32.069 --> 00:48:32.079 align:start position:0% secrets properly is absolutely critical 00:48:32.079 --> 00:48:34.230 align:start position:0% secrets properly is absolutely critical for<00:48:32.319> safely<00:48:32.800> protecting<00:48:33.440> tremendously 00:48:34.230 --> 00:48:34.240 align:start position:0% for safely protecting tremendously 00:48:34.240 --> 00:48:37.589 align:start position:0% for safely protecting tremendously sensitive<00:48:34.800> proprietary<00:48:35.520> information. 00:48:37.589 --> 00:48:37.599 align:start position:0% sensitive proprietary information. 00:48:37.599 --> 00:48:39.750 align:start position:0% sensitive proprietary information. Secrets<00:48:38.160> routinely<00:48:38.720> may<00:48:38.960> include<00:48:39.440> remote 00:48:39.750 --> 00:48:39.760 align:start position:0% Secrets routinely may include remote 00:48:39.760 --> 00:48:42.470 align:start position:0% Secrets routinely may include remote cloud<00:48:40.160> access<00:48:40.480> keys,<00:48:41.440> massive<00:48:41.920> database 00:48:42.470 --> 00:48:42.480 align:start position:0% cloud access keys, massive database 00:48:42.480 --> 00:48:45.670 align:start position:0% cloud access keys, massive database passwords,<00:48:43.599> complex<00:48:44.160> encryption<00:48:44.720> keys, 00:48:45.670 --> 00:48:45.680 align:start position:0% passwords, complex encryption keys, 00:48:45.680 --> 00:48:48.870 align:start position:0% passwords, complex encryption keys, vital<00:48:46.240> third-party<00:48:46.880> API<00:48:47.440> credentials,<00:48:48.559> and 00:48:48.870 --> 00:48:48.880 align:start position:0% vital third-party API credentials, and 00:48:48.880 --> 00:48:52.470 align:start position:0% vital third-party API credentials, and various<00:48:49.440> access<00:48:49.839> authentication<00:48:50.720> tokens. 00:48:52.470 --> 00:48:52.480 align:start position:0% various access authentication tokens. 00:48:52.480 --> 00:48:54.710 align:start position:0% various access authentication tokens. Handling<00:48:53.040> environment<00:48:53.599> variables<00:48:54.240> securely 00:48:54.710 --> 00:48:54.720 align:start position:0% Handling environment variables securely 00:48:54.720 --> 00:48:57.670 align:start position:0% Handling environment variables securely with<00:48:54.960> codecs<00:48:55.440> is<00:48:55.680> important.<00:48:56.400> These<00:48:56.800> specific 00:48:57.670 --> 00:48:57.680 align:start position:0% with codecs is important. These specific 00:48:57.680 --> 00:49:00.710 align:start position:0% with codecs is important. These specific crucial<00:48:58.319> security<00:48:58.880> items<00:48:59.520> are<00:48:59.839> undeniably 00:49:00.710 --> 00:49:00.720 align:start position:0% crucial security items are undeniably 00:49:00.720 --> 00:49:02.790 align:start position:0% crucial security items are undeniably very<00:49:01.200> important<00:49:01.599> to<00:49:01.920> actively<00:49:02.400> manage 00:49:02.790 --> 00:49:02.800 align:start position:0% very important to actively manage 00:49:02.800 --> 00:49:05.510 align:start position:0% very important to actively manage appropriately<00:49:03.520> right<00:49:03.839> here. 00:49:05.510 --> 00:49:05.520 align:start position:0% appropriately right here. 00:49:05.520 --> 00:49:07.910 align:start position:0% appropriately right here. Usually<00:49:06.480> wildly<00:49:06.960> different<00:49:07.440> distinct 00:49:07.910 --> 00:49:07.920 align:start position:0% Usually wildly different distinct 00:49:07.920 --> 00:49:09.910 align:start position:0% Usually wildly different distinct deployment<00:49:08.400> environments<00:49:09.200> inherently 00:49:09.910 --> 00:49:09.920 align:start position:0% deployment environments inherently 00:49:09.920 --> 00:49:11.829 align:start position:0% deployment environments inherently fundamentally<00:49:10.720> require<00:49:11.280> completely 00:49:11.829 --> 00:49:11.839 align:start position:0% fundamentally require completely 00:49:11.839 --> 00:49:13.829 align:start position:0% fundamentally require completely different<00:49:12.160> sets<00:49:12.480> of<00:49:12.720> unique<00:49:13.200> configuration 00:49:13.829 --> 00:49:13.839 align:start position:0% different sets of unique configuration 00:49:13.839 --> 00:49:15.430 align:start position:0% different sets of unique configuration values. 00:49:15.430 --> 00:49:15.440 align:start position:0% values. 00:49:15.440 --> 00:49:17.990 align:start position:0% values. We<00:49:15.680> can<00:49:15.839> intelligently<00:49:16.480> deploy<00:49:17.040> and<00:49:17.359> actively 00:49:17.990 --> 00:49:18.000 align:start position:0% We can intelligently deploy and actively 00:49:18.000 --> 00:49:21.270 align:start position:0% We can intelligently deploy and actively utilize<00:49:18.400> them<00:49:18.640> safely<00:49:19.280> over<00:49:19.599> there. 00:49:21.270 --> 00:49:21.280 align:start position:0% utilize them safely over there. 00:49:21.280 --> 00:49:23.910 align:start position:0% utilize them safely over there. Let<00:49:21.520> me<00:49:21.680> clearly<00:49:22.160> tell<00:49:22.319> you<00:49:23.200> whenever<00:49:23.599> I 00:49:23.910 --> 00:49:23.920 align:start position:0% Let me clearly tell you whenever I 00:49:23.920 --> 00:49:26.309 align:start position:0% Let me clearly tell you whenever I actively<00:49:24.400> try<00:49:24.640> to<00:49:24.880> perform<00:49:25.200> a<00:49:25.440> direct<00:49:25.920> system 00:49:26.309 --> 00:49:26.319 align:start position:0% actively try to perform a direct system 00:49:26.319 --> 00:49:27.910 align:start position:0% actively try to perform a direct system search<00:49:26.640> for<00:49:26.960> standard<00:49:27.359> environment 00:49:27.910 --> 00:49:27.920 align:start position:0% search for standard environment 00:49:27.920 --> 00:49:30.710 align:start position:0% search for standard environment variables,<00:49:29.119> you<00:49:29.440> immediately<00:49:30.079> see<00:49:30.400> our 00:49:30.710 --> 00:49:30.720 align:start position:0% variables, you immediately see our 00:49:30.720 --> 00:49:33.030 align:start position:0% variables, you immediately see our primary<00:49:31.200> system<00:49:31.599> environment<00:49:32.079> variables<00:49:32.800> are 00:49:33.030 --> 00:49:33.040 align:start position:0% primary system environment variables are 00:49:33.040 --> 00:49:36.950 align:start position:0% primary system environment variables are visibly<00:49:33.520> available<00:49:34.240> precisely<00:49:34.960> right<00:49:35.280> here. 00:49:36.950 --> 00:49:36.960 align:start position:0% visibly available precisely right here. 00:49:36.960 --> 00:49:39.589 align:start position:0% visibly available precisely right here. You<00:49:37.200> will<00:49:37.359> undeniably<00:49:38.240> see<00:49:38.400> that<00:49:38.800> absolutely 00:49:39.589 --> 00:49:39.599 align:start position:0% You will undeniably see that absolutely 00:49:39.599 --> 00:49:41.990 align:start position:0% You will undeniably see that absolutely all<00:49:39.920> of<00:49:40.160> our<00:49:40.400> current<00:49:40.720> environment<00:49:41.280> variables 00:49:41.990 --> 00:49:42.000 align:start position:0% all of our current environment variables 00:49:42.000 --> 00:49:44.390 align:start position:0% all of our current environment variables are<00:49:42.240> entirely<00:49:42.880> accessible<00:49:43.359> and<00:49:43.680> available 00:49:44.390 --> 00:49:44.400 align:start position:0% are entirely accessible and available 00:49:44.400 --> 00:49:46.870 align:start position:0% are entirely accessible and available literally<00:49:45.040> right<00:49:45.359> now. 00:49:46.870 --> 00:49:46.880 align:start position:0% literally right now. 00:49:46.880 --> 00:49:49.270 align:start position:0% literally right now. Sometimes<00:49:47.839> it<00:49:48.079> happens<00:49:48.319> to<00:49:48.559> merely<00:49:48.880> be<00:49:49.040> the 00:49:49.270 --> 00:49:49.280 align:start position:0% Sometimes it happens to merely be the 00:49:49.280 --> 00:49:50.870 align:start position:0% Sometimes it happens to merely be the static<00:49:49.680> number<00:49:49.920> of<00:49:50.079> active<00:49:50.559> system 00:49:50.870 --> 00:49:50.880 align:start position:0% static number of active system 00:49:50.880 --> 00:49:52.710 align:start position:0% static number of active system processes. 00:49:52.710 --> 00:49:52.720 align:start position:0% processes. 00:49:52.720 --> 00:49:55.109 align:start position:0% processes. Sometimes<00:49:53.280> it<00:49:53.520> is<00:49:53.680> a<00:49:53.839> highly<00:49:54.319> confidential 00:49:55.109 --> 00:49:55.119 align:start position:0% Sometimes it is a highly confidential 00:49:55.119 --> 00:49:57.829 align:start position:0% Sometimes it is a highly confidential external<00:49:55.760> API<00:49:56.319> key. 00:49:57.829 --> 00:49:57.839 align:start position:0% external API key. 00:49:57.839 --> 00:50:00.710 align:start position:0% external API key. We<00:49:58.079> can<00:49:58.319> smoothly<00:49:58.880> dive<00:49:59.280> deep<00:49:59.760> directly<00:50:00.480> right 00:50:00.710 --> 00:50:00.720 align:start position:0% We can smoothly dive deep directly right 00:50:00.720 --> 00:50:03.750 align:start position:0% We can smoothly dive deep directly right into<00:50:01.040> the<00:50:01.200> backend<00:50:01.680> system<00:50:02.000> variables<00:50:02.559> menu 00:50:03.750 --> 00:50:03.760 align:start position:0% into the backend system variables menu 00:50:03.760 --> 00:50:05.990 align:start position:0% into the backend system variables menu carefully<00:50:04.319> enter<00:50:04.640> the<00:50:04.880> specific<00:50:05.520> custom 00:50:05.990 --> 00:50:06.000 align:start position:0% carefully enter the specific custom 00:50:06.000 --> 00:50:08.309 align:start position:0% carefully enter the specific custom variable<00:50:06.480> name<00:50:07.040> and<00:50:07.280> its<00:50:07.520> corresponding 00:50:08.309 --> 00:50:08.319 align:start position:0% variable name and its corresponding 00:50:08.319 --> 00:50:11.190 align:start position:0% variable name and its corresponding strict<00:50:08.720> value<00:50:09.200> directly<00:50:10.160> and<00:50:10.480> permanently 00:50:11.190 --> 00:50:11.200 align:start position:0% strict value directly and permanently 00:50:11.200 --> 00:50:13.750 align:start position:0% strict value directly and permanently safely<00:50:11.760> store<00:50:12.000> it. 00:50:13.750 --> 00:50:13.760 align:start position:0% safely store it. 00:50:13.760 --> 00:50:16.870 align:start position:0% safely store it. So<00:50:14.400> the<00:50:14.640> next<00:50:14.880> time<00:50:15.040> we<00:50:15.200> run<00:50:15.359> a<00:50:15.520> use<00:50:15.760> case,<00:50:16.559> all 00:50:16.870 --> 00:50:16.880 align:start position:0% So the next time we run a use case, all 00:50:16.880 --> 00:50:19.030 align:start position:0% So the next time we run a use case, all variables<00:50:17.520> are<00:50:17.839> automatically<00:50:18.559> set 00:50:19.030 --> 00:50:19.040 align:start position:0% variables are automatically set 00:50:19.040 --> 00:50:21.270 align:start position:0% variables are automatically set perfectly. 00:50:21.270 --> 00:50:21.280 align:start position:0% perfectly. 00:50:21.280 --> 00:50:23.190 align:start position:0% perfectly. How<00:50:21.520> exactly<00:50:21.920> is<00:50:22.160> this<00:50:22.400> properly<00:50:22.800> handled 00:50:23.190 --> 00:50:23.200 align:start position:0% How exactly is this properly handled 00:50:23.200 --> 00:50:25.510 align:start position:0% How exactly is this properly handled inside<00:50:23.520> a<00:50:23.839> secure<00:50:24.319> underlying<00:50:24.960> database 00:50:25.510 --> 00:50:25.520 align:start position:0% inside a secure underlying database 00:50:25.520 --> 00:50:27.670 align:start position:0% inside a secure underlying database architecture? 00:50:27.670 --> 00:50:27.680 align:start position:0% architecture? 00:50:27.680 --> 00:50:29.750 align:start position:0% architecture? As<00:50:27.920> you<00:50:28.079> can<00:50:28.240> visibly<00:50:28.640> observe<00:50:29.119> precisely 00:50:29.750 --> 00:50:29.760 align:start position:0% As you can visibly observe precisely 00:50:29.760 --> 00:50:32.630 align:start position:0% As you can visibly observe precisely here,<00:50:30.720> located<00:50:31.200> deep<00:50:31.520> inside<00:50:31.920> the<00:50:32.160> primary 00:50:32.630 --> 00:50:32.640 align:start position:0% here, located deep inside the primary 00:50:32.640 --> 00:50:35.750 align:start position:0% here, located deep inside the primary configuration<00:50:33.359> interface,<00:50:34.720> we<00:50:35.040> purposely 00:50:35.750 --> 00:50:35.760 align:start position:0% configuration interface, we purposely 00:50:35.760 --> 00:50:38.230 align:start position:0% configuration interface, we purposely actively<00:50:36.319> include<00:50:36.720> a<00:50:36.960> dedicated<00:50:37.760> corporate 00:50:38.230 --> 00:50:38.240 align:start position:0% actively include a dedicated corporate 00:50:38.240 --> 00:50:40.950 align:start position:0% actively include a dedicated corporate company<00:50:38.720> database<00:50:39.280> link. 00:50:40.950 --> 00:50:40.960 align:start position:0% company database link. 00:50:40.960 --> 00:50:42.710 align:start position:0% company database link. If<00:50:41.200> there<00:50:41.440> happens<00:50:41.680> to<00:50:41.920> clearly<00:50:42.319> be<00:50:42.480> a 00:50:42.710 --> 00:50:42.720 align:start position:0% If there happens to clearly be a 00:50:42.720 --> 00:50:45.109 align:start position:0% If there happens to clearly be a specific<00:50:43.200> network<00:50:43.680> port<00:50:44.000> required,<00:50:44.800> we 00:50:45.109 --> 00:50:45.119 align:start position:0% specific network port required, we 00:50:45.119 --> 00:50:48.549 align:start position:0% specific network port required, we firmly<00:50:45.599> include<00:50:46.000> it.<00:50:47.440> If<00:50:47.680> there<00:50:47.920> explicitly 00:50:48.549 --> 00:50:48.559 align:start position:0% firmly include it. If there explicitly 00:50:48.559 --> 00:50:51.030 align:start position:0% firmly include it. If there explicitly is<00:50:48.880> an<00:50:49.200> overarching<00:50:50.000> master<00:50:50.480> application 00:50:51.030 --> 00:50:51.040 align:start position:0% is an overarching master application 00:50:51.040 --> 00:50:54.150 align:start position:0% is an overarching master application configuration<00:50:51.839> requirement,<00:50:53.119> we<00:50:53.440> safely<00:50:53.920> add 00:50:54.150 --> 00:50:54.160 align:start position:0% configuration requirement, we safely add 00:50:54.160 --> 00:50:56.710 align:start position:0% configuration requirement, we safely add the<00:50:54.480> core<00:50:54.800> app<00:50:55.119> environment<00:50:55.680> variable 00:50:56.710 --> 00:50:56.720 align:start position:0% the core app environment variable 00:50:56.720 --> 00:50:59.109 align:start position:0% the core app environment variable alongside<00:50:57.359> the<00:50:57.680> specific<00:50:58.240> designated<00:50:58.880> app 00:50:59.109 --> 00:50:59.119 align:start position:0% alongside the specific designated app 00:50:59.119 --> 00:51:00.870 align:start position:0% alongside the specific designated app port. 00:51:00.870 --> 00:51:00.880 align:start position:0% port. 00:51:00.880 --> 00:51:03.670 align:start position:0% port. Secure,<00:51:01.760> highly<00:51:02.319> confidential<00:51:03.040> API 00:51:03.670 --> 00:51:03.680 align:start position:0% Secure, highly confidential API 00:51:03.680 --> 00:51:06.069 align:start position:0% Secure, highly confidential API credentials<00:51:04.640> will<00:51:04.960> absolutely<00:51:05.680> come 00:51:06.069 --> 00:51:06.079 align:start position:0% credentials will absolutely come 00:51:06.079 --> 00:51:08.630 align:start position:0% credentials will absolutely come directly<00:51:06.640> right<00:51:06.960> here. 00:51:08.630 --> 00:51:08.640 align:start position:0% directly right here. 00:51:08.640 --> 00:51:11.190 align:start position:0% directly right here. For<00:51:08.800> one<00:51:09.040> clear<00:51:09.280> example,<00:51:10.240> if<00:51:10.480> we<00:51:10.640> genuinely 00:51:11.190 --> 00:51:11.200 align:start position:0% For one clear example, if we genuinely 00:51:11.200 --> 00:51:13.510 align:start position:0% For one clear example, if we genuinely want<00:51:11.359> to<00:51:11.520> safely<00:51:12.160> utilize<00:51:12.559> an<00:51:12.880> external 00:51:13.510 --> 00:51:13.520 align:start position:0% want to safely utilize an external 00:51:13.520 --> 00:51:16.950 align:start position:0% want to safely utilize an external OpenAI<00:51:14.400> API<00:51:14.960> authentication<00:51:15.760> key,<00:51:16.640> we 00:51:16.950 --> 00:51:16.960 align:start position:0% OpenAI API authentication key, we 00:51:16.960 --> 00:51:20.150 align:start position:0% OpenAI API authentication key, we securely<00:51:17.440> do<00:51:17.599> it<00:51:17.839> precisely<00:51:18.480> here. 00:51:20.150 --> 00:51:20.160 align:start position:0% securely do it precisely here. 00:51:20.160 --> 00:51:22.870 align:start position:0% securely do it precisely here. We<00:51:20.480> can<00:51:20.640> undoubtedly<00:51:21.520> also<00:51:22.000> clearly<00:51:22.480> see 00:51:22.870 --> 00:51:22.880 align:start position:0% We can undoubtedly also clearly see 00:51:22.880 --> 00:51:25.430 align:start position:0% We can undoubtedly also clearly see secure<00:51:23.520> encrypted<00:51:24.160> payment<00:51:24.559> gateway<00:51:25.040> keys 00:51:25.430 --> 00:51:25.440 align:start position:0% secure encrypted payment gateway keys 00:51:25.440 --> 00:51:27.750 align:start position:0% secure encrypted payment gateway keys stored<00:51:25.760> right<00:51:26.079> here. 00:51:27.750 --> 00:51:27.760 align:start position:0% stored right here. 00:51:27.760 --> 00:51:30.150 align:start position:0% stored right here. Then<00:51:28.480> there<00:51:28.720> are<00:51:28.880> massive<00:51:29.359> authentication 00:51:30.150 --> 00:51:30.160 align:start position:0% Then there are massive authentication 00:51:30.160 --> 00:51:32.710 align:start position:0% Then there are massive authentication backend<00:51:30.720> settings<00:51:31.680> designed<00:51:32.079> purely<00:51:32.480> to 00:51:32.710 --> 00:51:32.720 align:start position:0% backend settings designed purely to 00:51:32.720 --> 00:51:35.829 align:start position:0% backend settings designed purely to store<00:51:33.040> multiple<00:51:33.520> dynamic<00:51:34.079> secrets. 00:51:35.829 --> 00:51:35.839 align:start position:0% store multiple dynamic secrets. 00:51:35.839 --> 00:51:38.069 align:start position:0% store multiple dynamic secrets. These<00:51:36.240> environment<00:51:36.720> variables<00:51:37.440> brilliantly 00:51:38.069 --> 00:51:38.079 align:start position:0% These environment variables brilliantly 00:51:38.079 --> 00:51:40.470 align:start position:0% These environment variables brilliantly enable<00:51:38.559> large<00:51:38.880> organizations<00:51:39.760> to<00:51:40.000> safely 00:51:40.470 --> 00:51:40.480 align:start position:0% enable large organizations to safely 00:51:40.480 --> 00:51:43.190 align:start position:0% enable large organizations to safely manage<00:51:40.880> app<00:51:41.200> configurations. 00:51:43.190 --> 00:51:43.200 align:start position:0% manage app configurations. 00:51:43.200 --> 00:51:45.030 align:start position:0% manage app configurations. It<00:51:43.520> prevents<00:51:43.920> leaking<00:51:44.400> sensitive 00:51:45.030 --> 00:51:45.040 align:start position:0% It prevents leaking sensitive 00:51:45.040 --> 00:51:47.190 align:start position:0% It prevents leaking sensitive information. 00:51:47.190 --> 00:51:47.200 align:start position:0% information. 00:51:47.200 --> 00:51:49.670 align:start position:0% information. Codeex<00:51:47.760> handles<00:51:48.160> keys<00:51:48.559> safely<00:51:49.040> too<00:51:49.280> without 00:51:49.670 --> 00:51:49.680 align:start position:0% Codeex handles keys safely too without 00:51:49.680 --> 00:51:53.349 align:start position:0% Codeex handles keys safely too without hard<00:51:50.000> coding.<00:51:51.280> I<00:51:51.599> will<00:51:51.839> definitively<00:51:52.800> also 00:51:53.349 --> 00:51:53.359 align:start position:0% hard coding. I will definitively also 00:51:53.359 --> 00:51:55.589 align:start position:0% hard coding. I will definitively also sincerely<00:51:54.000> tell<00:51:54.240> you<00:51:54.800> that<00:51:55.119> strict 00:51:55.589 --> 00:51:55.599 align:start position:0% sincerely tell you that strict 00:51:55.599 --> 00:51:57.829 align:start position:0% sincerely tell you that strict environment<00:51:56.240> variables<00:51:56.880> frankly<00:51:57.359> may<00:51:57.599> not 00:51:57.829 --> 00:51:57.839 align:start position:0% environment variables frankly may not 00:51:57.839 --> 00:52:00.309 align:start position:0% environment variables frankly may not initially<00:51:58.559> actively<00:51:59.040> seem<00:51:59.440> incredibly<00:52:00.000> very 00:52:00.309 --> 00:52:00.319 align:start position:0% initially actively seem incredibly very 00:52:00.319 --> 00:52:02.470 align:start position:0% initially actively seem incredibly very important<00:52:00.720> right<00:52:01.040> now<00:52:01.680> when<00:52:01.920> we<00:52:02.079> merely 00:52:02.470 --> 00:52:02.480 align:start position:0% important right now when we merely 00:52:02.480 --> 00:52:04.390 align:start position:0% important right now when we merely successfully<00:52:03.040> create<00:52:03.520> basic<00:52:04.000> simple 00:52:04.390 --> 00:52:04.400 align:start position:0% successfully create basic simple 00:52:04.400 --> 00:52:07.349 align:start position:0% successfully create basic simple software<00:52:05.680> absolutely<00:52:06.319> like<00:52:06.480> a<00:52:06.720> fundamental 00:52:07.349 --> 00:52:07.359 align:start position:0% software absolutely like a fundamental 00:52:07.359 --> 00:52:09.990 align:start position:0% software absolutely like a fundamental basic<00:52:07.839> calculator<00:52:08.640> or<00:52:09.040> standard<00:52:09.520> normal 00:52:09.990 --> 00:52:10.000 align:start position:0% basic calculator or standard normal 00:52:10.000 --> 00:52:12.150 align:start position:0% basic calculator or standard normal terminal<00:52:10.400> tools. 00:52:12.150 --> 00:52:12.160 align:start position:0% terminal tools. 00:52:12.160 --> 00:52:14.390 align:start position:0% terminal tools. However,<00:52:12.960> the<00:52:13.200> exact<00:52:13.599> moment<00:52:13.920> when<00:52:14.160> we 00:52:14.390 --> 00:52:14.400 align:start position:0% However, the exact moment when we 00:52:14.400 --> 00:52:17.030 align:start position:0% However, the exact moment when we actively<00:52:15.040> rigorously<00:52:15.760> try<00:52:16.000> to<00:52:16.240> fundamentally 00:52:17.030 --> 00:52:17.040 align:start position:0% actively rigorously try to fundamentally 00:52:17.040 --> 00:52:19.750 align:start position:0% actively rigorously try to fundamentally change<00:52:17.359> our<00:52:17.680> massive<00:52:18.160> software<00:52:18.559> architecture 00:52:19.750 --> 00:52:19.760 align:start position:0% change our massive software architecture 00:52:19.760 --> 00:52:22.470 align:start position:0% change our massive software architecture or<00:52:20.079> alter<00:52:20.480> major<00:52:20.960> things<00:52:21.280> safely<00:52:22.000> on<00:52:22.240> a 00:52:22.470 --> 00:52:22.480 align:start position:0% or alter major things safely on a 00:52:22.480 --> 00:52:25.030 align:start position:0% or alter major things safely on a significantly<00:52:23.280> much<00:52:23.680> larger,<00:52:24.240> incredibly 00:52:25.030 --> 00:52:25.040 align:start position:0% significantly much larger, incredibly 00:52:25.040 --> 00:52:28.390 align:start position:0% significantly much larger, incredibly massive<00:52:25.440> corporate<00:52:25.920> scale,<00:52:27.119> literally<00:52:27.920> many 00:52:28.390 --> 00:52:28.400 align:start position:0% massive corporate scale, literally many 00:52:28.400 --> 00:52:30.630 align:start position:0% massive corporate scale, literally many distinct<00:52:29.040> individual<00:52:29.599> things<00:52:30.079> wildly 00:52:30.630 --> 00:52:30.640 align:start position:0% distinct individual things wildly 00:52:30.640 --> 00:52:32.230 align:start position:0% distinct individual things wildly realistically<00:52:31.359> start<00:52:31.760> changing 00:52:32.230 --> 00:52:32.240 align:start position:0% realistically start changing 00:52:32.240 --> 00:52:33.750 align:start position:0% realistically start changing aggressively<00:52:32.960> side<00:52:33.200> by<00:52:33.440> side 00:52:33.750 --> 00:52:33.760 align:start position:0% aggressively side by side 00:52:33.760 --> 00:52:35.750 align:start position:0% aggressively side by side simultaneously. 00:52:35.750 --> 00:52:35.760 align:start position:0% simultaneously. 00:52:35.760 --> 00:52:38.710 align:start position:0% simultaneously. We<00:52:36.079> immediately<00:52:37.040> rapidly<00:52:37.680> actively<00:52:38.240> see 00:52:38.710 --> 00:52:38.720 align:start position:0% We immediately rapidly actively see 00:52:38.720 --> 00:52:41.829 align:start position:0% We immediately rapidly actively see literally<00:52:39.440> multiple<00:52:40.160> deep<00:52:40.640> cascading 00:52:41.829 --> 00:52:41.839 align:start position:0% literally multiple deep cascading 00:52:41.839 --> 00:52:43.990 align:start position:0% literally multiple deep cascading fundamental<00:52:42.640> code<00:52:43.040> structural<00:52:43.520> changes 00:52:43.990 --> 00:52:44.000 align:start position:0% fundamental code structural changes 00:52:44.000 --> 00:52:45.750 align:start position:0% fundamental code structural changes happening 00:52:45.750 --> 00:52:45.760 align:start position:0% happening 00:52:45.760 --> 00:52:48.069 align:start position:0% happening now<00:52:46.319> moving<00:52:46.720> confidently<00:52:47.359> right<00:52:47.680> forward 00:52:48.069 --> 00:52:48.079 align:start position:0% now moving confidently right forward 00:52:48.079 --> 00:52:51.030 align:start position:0% now moving confidently right forward seamlessly.<00:52:49.200> We<00:52:49.440> will<00:52:49.680> deeply<00:52:50.319> actively 00:52:51.030 --> 00:52:51.040 align:start position:0% seamlessly. We will deeply actively 00:52:51.040 --> 00:52:53.750 align:start position:0% seamlessly. We will deeply actively rigorously<00:52:52.000> explicitly<00:52:52.720> discuss<00:52:53.280> all<00:52:53.599> of 00:52:53.750 --> 00:52:53.760 align:start position:0% rigorously explicitly discuss all of 00:52:53.760 --> 00:52:56.069 align:start position:0% rigorously explicitly discuss all of these<00:52:54.079> major<00:52:54.559> systematic<00:52:55.440> fundamental 00:52:56.069 --> 00:52:56.079 align:start position:0% these major systematic fundamental 00:52:56.079 --> 00:52:58.870 align:start position:0% these major systematic fundamental software<00:52:56.559> changes<00:52:57.520> and<00:52:57.839> deeply<00:52:58.240> integrated 00:52:58.870 --> 00:52:58.880 align:start position:0% software changes and deeply integrated 00:52:58.880 --> 00:53:01.270 align:start position:0% software changes and deeply integrated highly<00:52:59.359> complex<00:52:59.839> AI<00:53:00.240> functions<00:53:00.800> directly 00:53:01.270 --> 00:53:01.280 align:start position:0% highly complex AI functions directly 00:53:01.280 --> 00:53:04.150 align:start position:0% highly complex AI functions directly later.<00:53:02.640> We<00:53:02.880> will<00:53:03.119> explore<00:53:03.440> this<00:53:03.599> in<00:53:03.839> the<00:53:04.000> next 00:53:04.150 --> 00:53:04.160 align:start position:0% later. We will explore this in the next 00:53:04.160 --> 00:53:08.549 align:start position:0% later. We will explore this in the next sections<00:53:04.720> perfectly. 00:53:08.549 --> 00:53:08.559 align:start position:0% 00:53:08.559 --> 00:53:10.950 align:start position:0% Authentication<00:53:09.359> and<00:53:09.680> access<00:53:10.160> configuration 00:53:10.950 --> 00:53:10.960 align:start position:0% Authentication and access configuration 00:53:10.960 --> 00:53:13.349 align:start position:0% Authentication and access configuration is<00:53:11.200> a<00:53:11.359> critical<00:53:11.839> part<00:53:12.079> of<00:53:12.319> using<00:53:12.640> open<00:53:13.040> AI 00:53:13.349 --> 00:53:13.359 align:start position:0% is a critical part of using open AI 00:53:13.359 --> 00:53:15.430 align:start position:0% is a critical part of using open AI codecs<00:53:13.920> in<00:53:14.079> an<00:53:14.319> enterprise<00:53:14.880> development 00:53:15.430 --> 00:53:15.440 align:start position:0% codecs in an enterprise development 00:53:15.440 --> 00:53:17.430 align:start position:0% codecs in an enterprise development environment. 00:53:17.430 --> 00:53:17.440 align:start position:0% environment. 00:53:17.440 --> 00:53:19.910 align:start position:0% environment. Authentication<00:53:18.400> verifies<00:53:18.960> the<00:53:19.280> identity<00:53:19.680> of 00:53:19.910 --> 00:53:19.920 align:start position:0% Authentication verifies the identity of 00:53:19.920 --> 00:53:22.150 align:start position:0% Authentication verifies the identity of the<00:53:20.079> user<00:53:20.480> or<00:53:20.800> system<00:53:21.200> attempting<00:53:21.680> to<00:53:21.920> use 00:53:22.150 --> 00:53:22.160 align:start position:0% the user or system attempting to use 00:53:22.160 --> 00:53:25.430 align:start position:0% the user or system attempting to use codecs<00:53:23.440> while<00:53:23.760> access<00:53:24.240> configuration 00:53:25.430 --> 00:53:25.440 align:start position:0% codecs while access configuration 00:53:25.440 --> 00:53:27.670 align:start position:0% codecs while access configuration defines<00:53:25.920> what<00:53:26.160> that<00:53:26.480> user<00:53:26.800> or<00:53:27.119> system<00:53:27.440> is 00:53:27.670 --> 00:53:27.680 align:start position:0% defines what that user or system is 00:53:27.680 --> 00:53:29.670 align:start position:0% defines what that user or system is allowed<00:53:28.000> to<00:53:28.160> do. 00:53:29.670 --> 00:53:29.680 align:start position:0% allowed to do. 00:53:29.680 --> 00:53:32.230 align:start position:0% allowed to do. Together,<00:53:30.640> these<00:53:31.040> controls<00:53:31.520> ensure<00:53:31.920> that 00:53:32.230 --> 00:53:32.240 align:start position:0% Together, these controls ensure that 00:53:32.240 --> 00:53:35.190 align:start position:0% Together, these controls ensure that only<00:53:32.559> authorized<00:53:33.200> developers,<00:53:34.240> teams,<00:53:34.960> and 00:53:35.190 --> 00:53:35.200 align:start position:0% only authorized developers, teams, and 00:53:35.200 --> 00:53:37.589 align:start position:0% only authorized developers, teams, and automation<00:53:35.839> tools<00:53:36.640> can<00:53:36.960> interact<00:53:37.359> with 00:53:37.589 --> 00:53:37.599 align:start position:0% automation tools can interact with 00:53:37.599 --> 00:53:41.270 align:start position:0% automation tools can interact with repositories,<00:53:38.800> environments,<00:53:40.079> APIs,<00:53:41.040> and 00:53:41.270 --> 00:53:41.280 align:start position:0% repositories, environments, APIs, and 00:53:41.280 --> 00:53:44.470 align:start position:0% repositories, environments, APIs, and sensitive<00:53:41.839> project<00:53:42.319> resources. 00:53:44.470 --> 00:53:44.480 align:start position:0% sensitive project resources. 00:53:44.480 --> 00:53:46.790 align:start position:0% sensitive project resources. In<00:53:44.720> enterprise<00:53:45.280> software<00:53:45.680> development, 00:53:46.790 --> 00:53:46.800 align:start position:0% In enterprise software development, 00:53:46.800 --> 00:53:48.950 align:start position:0% In enterprise software development, codeex<00:53:47.359> usually<00:53:47.760> works<00:53:48.000> with<00:53:48.240> cloud-based 00:53:48.950 --> 00:53:48.960 align:start position:0% codeex usually works with cloud-based 00:53:48.960 --> 00:53:51.030 align:start position:0% codeex usually works with cloud-based development<00:53:49.359> environments,<00:53:50.559> GitHub 00:53:51.030 --> 00:53:51.040 align:start position:0% development environments, GitHub 00:53:51.040 --> 00:53:54.870 align:start position:0% development environments, GitHub repositories,<00:53:52.400> CI/CD<00:53:53.680> pipelines,<00:53:54.640> and 00:53:54.870 --> 00:53:54.880 align:start position:0% repositories, CI/CD pipelines, and 00:53:54.880 --> 00:53:57.109 align:start position:0% repositories, CI/CD pipelines, and internal<00:53:55.440> tools. 00:53:57.109 --> 00:53:57.119 align:start position:0% internal tools. 00:53:57.119 --> 00:53:58.950 align:start position:0% internal tools. Because<00:53:57.440> these<00:53:57.760> systems<00:53:58.240> may<00:53:58.480> contain 00:53:58.950 --> 00:53:58.960 align:start position:0% Because these systems may contain 00:53:58.960 --> 00:54:01.829 align:start position:0% Because these systems may contain confidential<00:53:59.599> source<00:54:00.000> code,<00:54:00.640> credentials, 00:54:01.829 --> 00:54:01.839 align:start position:0% confidential source code, credentials, 00:54:01.839 --> 00:54:03.670 align:start position:0% confidential source code, credentials, customer<00:54:02.319> data,<00:54:02.880> and<00:54:03.200> deployment 00:54:03.670 --> 00:54:03.680 align:start position:0% customer data, and deployment 00:54:03.680 --> 00:54:05.270 align:start position:0% customer data, and deployment configurations, 00:54:05.270 --> 00:54:05.280 align:start position:0% configurations, 00:54:05.280 --> 00:54:08.390 align:start position:0% configurations, access<00:54:05.760> must<00:54:06.000> be<00:54:06.160> carefully<00:54:06.720> managed. 00:54:08.390 --> 00:54:08.400 align:start position:0% access must be carefully managed. 00:54:08.400 --> 00:54:10.950 align:start position:0% access must be carefully managed. A<00:54:08.559> weak<00:54:08.960> authentication<00:54:09.760> setup<00:54:10.319> can<00:54:10.559> expose 00:54:10.950 --> 00:54:10.960 align:start position:0% A weak authentication setup can expose 00:54:10.960 --> 00:54:13.270 align:start position:0% A weak authentication setup can expose the<00:54:11.200> organization<00:54:11.920> to<00:54:12.160> unauthorized<00:54:12.960> code 00:54:13.270 --> 00:54:13.280 align:start position:0% the organization to unauthorized code 00:54:13.280 --> 00:54:16.630 align:start position:0% the organization to unauthorized code access,<00:54:14.319> accidental<00:54:14.960> changes,<00:54:15.839> or<00:54:16.160> security 00:54:16.630 --> 00:54:16.640 align:start position:0% access, accidental changes, or security 00:54:16.640 --> 00:54:18.790 align:start position:0% access, accidental changes, or security breaches. 00:54:18.790 --> 00:54:18.800 align:start position:0% breaches. 00:54:18.800 --> 00:54:21.910 align:start position:0% breaches. Therefore,<00:54:20.000> enterprises<00:54:20.720> commonly<00:54:21.200> rely<00:54:21.520> on 00:54:21.910 --> 00:54:21.920 align:start position:0% Therefore, enterprises commonly rely on 00:54:21.920 --> 00:54:24.950 align:start position:0% Therefore, enterprises commonly rely on identity<00:54:22.319> providers,<00:54:23.440> single<00:54:23.839> sign<00:54:24.079> on, 00:54:24.950 --> 00:54:24.960 align:start position:0% identity providers, single sign on, 00:54:24.960 --> 00:54:27.589 align:start position:0% identity providers, single sign on, role-based<00:54:25.680> access<00:54:26.160> control,<00:54:26.960> and<00:54:27.200> audit 00:54:27.589 --> 00:54:27.599 align:start position:0% role-based access control, and audit 00:54:27.599 --> 00:54:29.349 align:start position:0% role-based access control, and audit logging. 00:54:29.349 --> 00:54:29.359 align:start position:0% logging. 00:54:29.359 --> 00:54:31.430 align:start position:0% logging. The<00:54:29.599> authentication<00:54:30.480> process<00:54:31.040> normally 00:54:31.430 --> 00:54:31.440 align:start position:0% The authentication process normally 00:54:31.440 --> 00:54:33.750 align:start position:0% The authentication process normally begins<00:54:31.839> when<00:54:32.079> a<00:54:32.319> developer<00:54:32.720> signs<00:54:33.119> in<00:54:33.440> using 00:54:33.750 --> 00:54:33.760 align:start position:0% begins when a developer signs in using 00:54:33.760 --> 00:54:36.549 align:start position:0% begins when a developer signs in using an<00:54:34.000> approved<00:54:34.559> identity<00:54:34.960> provider. 00:54:36.549 --> 00:54:36.559 align:start position:0% an approved identity provider. 00:54:36.559 --> 00:54:38.549 align:start position:0% an approved identity provider. This<00:54:36.800> may<00:54:37.040> include<00:54:37.520> enterprise<00:54:38.079> login 00:54:38.549 --> 00:54:38.559 align:start position:0% This may include enterprise login 00:54:38.559 --> 00:54:42.710 align:start position:0% This may include enterprise login systems<00:54:39.440> such<00:54:39.760> as<00:54:40.160> SSO,<00:54:41.440> OOTH,<00:54:42.400> or 00:54:42.710 --> 00:54:42.720 align:start position:0% systems such as SSO, OOTH, or 00:54:42.720 --> 00:54:45.829 align:start position:0% systems such as SSO, OOTH, or multiffactor<00:54:43.520> authentication. 00:54:45.829 --> 00:54:45.839 align:start position:0% multiffactor authentication. 00:54:45.839 --> 00:54:48.630 align:start position:0% multiffactor authentication. Once<00:54:46.160> the<00:54:46.319> user<00:54:46.800> identity<00:54:47.119> is<00:54:47.359> confirmed,<00:54:48.319> the 00:54:48.630 --> 00:54:48.640 align:start position:0% Once the user identity is confirmed, the 00:54:48.640 --> 00:54:50.309 align:start position:0% Once the user identity is confirmed, the system<00:54:48.960> checks<00:54:49.280> whether<00:54:49.599> the<00:54:49.839> user<00:54:50.160> has 00:54:50.309 --> 00:54:50.319 align:start position:0% system checks whether the user has 00:54:50.319 --> 00:54:52.470 align:start position:0% system checks whether the user has permission<00:54:50.720> to<00:54:50.960> access<00:54:51.359> codeex,<00:54:52.160> the 00:54:52.470 --> 00:54:52.480 align:start position:0% permission to access codeex, the 00:54:52.480 --> 00:54:54.710 align:start position:0% permission to access codeex, the development<00:54:52.880> workspace<00:54:53.920> and<00:54:54.079> the<00:54:54.319> connected 00:54:54.710 --> 00:54:54.720 align:start position:0% development workspace and the connected 00:54:54.720 --> 00:54:56.710 align:start position:0% development workspace and the connected repositories. 00:54:56.710 --> 00:54:56.720 align:start position:0% repositories. 00:54:56.720 --> 00:54:59.030 align:start position:0% repositories. This<00:54:56.960> ensures<00:54:57.359> that<00:54:57.599> codeex<00:54:58.240> activities<00:54:58.800> are 00:54:59.030 --> 00:54:59.040 align:start position:0% This ensures that codeex activities are 00:54:59.040 --> 00:55:01.349 align:start position:0% This ensures that codeex activities are tied<00:54:59.359> to<00:54:59.520> a<00:54:59.680> verified<00:55:00.240> user<00:55:00.800> and<00:55:01.040> can<00:55:01.200> be 00:55:01.349 --> 00:55:01.359 align:start position:0% tied to a verified user and can be 00:55:01.359 --> 00:55:04.470 align:start position:0% tied to a verified user and can be tracked<00:55:01.680> for<00:55:01.920> accountability. 00:55:04.470 --> 00:55:04.480 align:start position:0% tracked for accountability. 00:55:04.480 --> 00:55:06.630 align:start position:0% tracked for accountability. Access<00:55:04.960> configuration<00:55:05.839> determines<00:55:06.400> the 00:55:06.630 --> 00:55:06.640 align:start position:0% Access configuration determines the 00:55:06.640 --> 00:55:09.349 align:start position:0% Access configuration determines the scope<00:55:06.880> of<00:55:07.119> codeex's<00:55:07.839> permissions. 00:55:09.349 --> 00:55:09.359 align:start position:0% scope of codeex's permissions. 00:55:09.359 --> 00:55:11.990 align:start position:0% scope of codeex's permissions. For<00:55:09.520> example,<00:55:10.640> codecs<00:55:11.200> may<00:55:11.440> be<00:55:11.520> allowed<00:55:11.839> to 00:55:11.990 --> 00:55:12.000 align:start position:0% For example, codecs may be allowed to 00:55:12.000 --> 00:55:15.190 align:start position:0% For example, codecs may be allowed to read<00:55:12.240> a<00:55:12.400> repository,<00:55:13.440> analyze<00:55:14.000> code,<00:55:14.960> create 00:55:15.190 --> 00:55:15.200 align:start position:0% read a repository, analyze code, create 00:55:15.200 --> 00:55:18.549 align:start position:0% read a repository, analyze code, create a<00:55:15.440> branch,<00:55:16.319> run<00:55:16.640> tests,<00:55:17.520> or<00:55:17.760> open<00:55:18.079> a<00:55:18.240> pull 00:55:18.549 --> 00:55:18.559 align:start position:0% a branch, run tests, or open a pull 00:55:18.559 --> 00:55:20.069 align:start position:0% a branch, run tests, or open a pull request. 00:55:20.069 --> 00:55:20.079 align:start position:0% request. 00:55:20.079 --> 00:55:22.710 align:start position:0% request. In<00:55:20.319> some<00:55:20.559> cases,<00:55:21.520> it<00:55:21.760> may<00:55:21.920> not<00:55:22.079> be<00:55:22.240> allowed<00:55:22.559> to 00:55:22.710 --> 00:55:22.720 align:start position:0% In some cases, it may not be allowed to 00:55:22.720 --> 00:55:25.349 align:start position:0% In some cases, it may not be allowed to directly<00:55:23.280> merge<00:55:23.680> code<00:55:24.079> or<00:55:24.400> access<00:55:24.880> production 00:55:25.349 --> 00:55:25.359 align:start position:0% directly merge code or access production 00:55:25.359 --> 00:55:27.109 align:start position:0% directly merge code or access production secrets. 00:55:27.109 --> 00:55:27.119 align:start position:0% secrets. 00:55:27.119 --> 00:55:28.630 align:start position:0% secrets. These<00:55:27.440> permissions<00:55:28.000> should<00:55:28.160> follow<00:55:28.480> the 00:55:28.630 --> 00:55:28.640 align:start position:0% These permissions should follow the 00:55:28.640 --> 00:55:31.030 align:start position:0% These permissions should follow the principle<00:55:29.040> of<00:55:29.200> least<00:55:29.599> privilege,<00:55:30.640> meaning 00:55:31.030 --> 00:55:31.040 align:start position:0% principle of least privilege, meaning 00:55:31.040 --> 00:55:33.510 align:start position:0% principle of least privilege, meaning codecs<00:55:31.599> and<00:55:31.839> users<00:55:32.319> should<00:55:32.559> receive<00:55:32.960> only<00:55:33.200> the 00:55:33.510 --> 00:55:33.520 align:start position:0% codecs and users should receive only the 00:55:33.520 --> 00:55:35.109 align:start position:0% codecs and users should receive only the access<00:55:33.920> required<00:55:34.400> to<00:55:34.559> complete<00:55:34.880> their 00:55:35.109 --> 00:55:35.119 align:start position:0% access required to complete their 00:55:35.119 --> 00:55:37.670 align:start position:0% access required to complete their assigned<00:55:35.599> tasks. 00:55:37.670 --> 00:55:37.680 align:start position:0% assigned tasks. 00:55:37.680 --> 00:55:39.589 align:start position:0% assigned tasks. Repository<00:55:38.319> access<00:55:38.800> is<00:55:39.040> especially 00:55:39.589 --> 00:55:39.599 align:start position:0% Repository access is especially 00:55:39.599 --> 00:55:42.790 align:start position:0% Repository access is especially important.<00:55:41.040> Codecex<00:55:41.680> must<00:55:41.920> often<00:55:42.240> inspect 00:55:42.790 --> 00:55:42.800 align:start position:0% important. Codecex must often inspect 00:55:42.800 --> 00:55:45.670 align:start position:0% important. Codecex must often inspect project<00:55:43.200> files,<00:55:44.079> understand<00:55:44.640> dependencies, 00:55:45.670 --> 00:55:45.680 align:start position:0% project files, understand dependencies, 00:55:45.680 --> 00:55:49.430 align:start position:0% project files, understand dependencies, and<00:55:46.000> modify<00:55:46.480> code.<00:55:47.760> However,<00:55:48.799> not<00:55:49.119> every 00:55:49.430 --> 00:55:49.440 align:start position:0% and modify code. However, not every 00:55:49.440 --> 00:55:51.510 align:start position:0% and modify code. However, not every repository<00:55:50.079> should<00:55:50.319> be<00:55:50.480> accessible<00:55:50.960> to<00:55:51.200> every 00:55:51.510 --> 00:55:51.520 align:start position:0% repository should be accessible to every 00:55:51.520 --> 00:55:54.549 align:start position:0% repository should be accessible to every user<00:55:51.920> or<00:55:52.160> AI<00:55:52.640> workflow. 00:55:54.549 --> 00:55:54.559 align:start position:0% user or AI workflow. 00:55:54.559 --> 00:55:56.549 align:start position:0% user or AI workflow. Enterprises<00:55:55.280> should<00:55:55.520> configure<00:55:56.000> repository 00:55:56.549 --> 00:55:56.559 align:start position:0% Enterprises should configure repository 00:55:56.559 --> 00:55:59.349 align:start position:0% Enterprises should configure repository permissions<00:55:57.040> based<00:55:57.359> on<00:55:57.599> teams,<00:55:58.559> projects, 00:55:59.349 --> 00:55:59.359 align:start position:0% permissions based on teams, projects, 00:55:59.359 --> 00:56:01.829 align:start position:0% permissions based on teams, projects, and<00:55:59.599> business<00:56:00.000> sensitivity. 00:56:01.829 --> 00:56:01.839 align:start position:0% and business sensitivity. 00:56:01.839 --> 00:56:04.549 align:start position:0% and business sensitivity. For<00:56:02.000> example,<00:56:02.960> a<00:56:03.200> front-end<00:56:03.760> developer<00:56:04.319> may 00:56:04.549 --> 00:56:04.559 align:start position:0% For example, a front-end developer may 00:56:04.559 --> 00:56:07.430 align:start position:0% For example, a front-end developer may receive<00:56:04.960> access<00:56:05.359> to<00:56:05.599> UI<00:56:06.079> repositories,<00:56:07.119> but 00:56:07.430 --> 00:56:07.440 align:start position:0% receive access to UI repositories, but 00:56:07.440 --> 00:56:09.589 align:start position:0% receive access to UI repositories, but not<00:56:07.599> to<00:56:07.839> payment<00:56:08.240> infrastructure<00:56:09.119> or 00:56:09.589 --> 00:56:09.599 align:start position:0% not to payment infrastructure or 00:56:09.599 --> 00:56:12.390 align:start position:0% not to payment infrastructure or identity<00:56:10.000> management<00:56:10.480> services. 00:56:12.390 --> 00:56:12.400 align:start position:0% identity management services. 00:56:12.400 --> 00:56:14.789 align:start position:0% identity management services. Environment<00:56:13.040> variables<00:56:13.520> and<00:56:13.839> secrets<00:56:14.400> also 00:56:14.789 --> 00:56:14.799 align:start position:0% Environment variables and secrets also 00:56:14.799 --> 00:56:17.190 align:start position:0% Environment variables and secrets also require<00:56:15.280> strict<00:56:15.680> control. 00:56:17.190 --> 00:56:17.200 align:start position:0% require strict control. 00:56:17.200 --> 00:56:19.349 align:start position:0% require strict control. Codeex<00:56:17.839> may<00:56:18.079> need<00:56:18.240> to<00:56:18.400> understand<00:56:18.880> variable 00:56:19.349 --> 00:56:19.359 align:start position:0% Codeex may need to understand variable 00:56:19.359 --> 00:56:21.910 align:start position:0% Codeex may need to understand variable names,<00:56:20.079> configuration<00:56:20.799> patterns,<00:56:21.680> or 00:56:21.910 --> 00:56:21.920 align:start position:0% names, configuration patterns, or 00:56:21.920 --> 00:56:24.630 align:start position:0% names, configuration patterns, or runtime<00:56:22.480> requirements,<00:56:23.680> but<00:56:24.000> it<00:56:24.160> should<00:56:24.319> not 00:56:24.630 --> 00:56:24.640 align:start position:0% runtime requirements, but it should not 00:56:24.640 --> 00:56:28.150 align:start position:0% runtime requirements, but it should not expose<00:56:25.119> or<00:56:25.359> hardcode<00:56:26.079> secret<00:56:26.559> values. 00:56:28.150 --> 00:56:28.160 align:start position:0% expose or hardcode secret values. 00:56:28.160 --> 00:56:29.990 align:start position:0% expose or hardcode secret values. Sensitive<00:56:28.720> credentials<00:56:29.280> should<00:56:29.599> be<00:56:29.760> stored 00:56:29.990 --> 00:56:30.000 align:start position:0% Sensitive credentials should be stored 00:56:30.000 --> 00:56:32.870 align:start position:0% Sensitive credentials should be stored in<00:56:30.319> secure<00:56:30.799> secret<00:56:31.200> managers<00:56:32.000> and<00:56:32.319> injected 00:56:32.870 --> 00:56:32.880 align:start position:0% in secure secret managers and injected 00:56:32.880 --> 00:56:35.109 align:start position:0% in secure secret managers and injected only<00:56:33.200> when<00:56:33.520> required. 00:56:35.109 --> 00:56:35.119 align:start position:0% only when required. 00:56:35.119 --> 00:56:37.829 align:start position:0% only when required. This<00:56:35.359> prevents<00:56:35.920> accidental<00:56:36.480> leakage<00:56:36.960> of<00:56:37.200> API 00:56:37.829 --> 00:56:37.839 align:start position:0% This prevents accidental leakage of API 00:56:37.839 --> 00:56:41.589 align:start position:0% This prevents accidental leakage of API keys,<00:56:38.720> tokens,<00:56:39.760> database<00:56:40.319> passwords<00:56:41.280> or 00:56:41.589 --> 00:56:41.599 align:start position:0% keys, tokens, database passwords or 00:56:41.599 --> 00:56:45.030 align:start position:0% keys, tokens, database passwords or cloud<00:56:41.920> credentials<00:56:42.559> into<00:56:42.880> source<00:56:43.280> code. 00:56:45.030 --> 00:56:45.040 align:start position:0% cloud credentials into source code. 00:56:45.040 --> 00:56:46.870 align:start position:0% cloud credentials into source code. Auditability<00:56:45.839> is<00:56:46.160> another<00:56:46.480> major 00:56:46.870 --> 00:56:46.880 align:start position:0% Auditability is another major 00:56:46.880 --> 00:56:48.549 align:start position:0% Auditability is another major requirement<00:56:47.280> in<00:56:47.599> enterprise<00:56:48.160> access 00:56:48.549 --> 00:56:48.559 align:start position:0% requirement in enterprise access 00:56:48.559 --> 00:56:50.630 align:start position:0% requirement in enterprise access configuration. 00:56:50.630 --> 00:56:50.640 align:start position:0% configuration. 00:56:50.640 --> 00:56:52.710 align:start position:0% configuration. Organizations<00:56:51.520> should<00:56:51.760> be<00:56:51.920> able<00:56:52.160> to<00:56:52.319> review 00:56:52.710 --> 00:56:52.720 align:start position:0% Organizations should be able to review 00:56:52.720 --> 00:56:55.589 align:start position:0% Organizations should be able to review who<00:56:53.040> accessed<00:56:53.599> codecs,<00:56:54.640> which<00:56:54.960> repositories 00:56:55.589 --> 00:56:55.599 align:start position:0% who accessed codecs, which repositories 00:56:55.599 --> 00:56:58.390 align:start position:0% who accessed codecs, which repositories were<00:56:55.839> used,<00:56:56.559> what<00:56:56.880> tasks<00:56:57.280> were<00:56:57.520> performed, 00:56:58.390 --> 00:56:58.400 align:start position:0% were used, what tasks were performed, 00:56:58.400 --> 00:57:01.270 align:start position:0% were used, what tasks were performed, and<00:56:58.559> what<00:56:58.880> changes<00:56:59.280> were<00:56:59.440> generated. 00:57:01.270 --> 00:57:01.280 align:start position:0% and what changes were generated. 00:57:01.280 --> 00:57:03.190 align:start position:0% and what changes were generated. Audit<00:57:01.680> logs<00:57:02.000> help<00:57:02.319> security<00:57:02.799> teams 00:57:03.190 --> 00:57:03.200 align:start position:0% Audit logs help security teams 00:57:03.200 --> 00:57:05.430 align:start position:0% Audit logs help security teams investigate<00:57:03.839> incidents,<00:57:04.880> enforce 00:57:05.430 --> 00:57:05.440 align:start position:0% investigate incidents, enforce 00:57:05.440 --> 00:57:07.750 align:start position:0% investigate incidents, enforce governance<00:57:05.920> policies,<00:57:06.880> and<00:57:07.119> demonstrate 00:57:07.750 --> 00:57:07.760 align:start position:0% governance policies, and demonstrate 00:57:07.760 --> 00:57:09.910 align:start position:0% governance policies, and demonstrate compliance<00:57:08.240> with<00:57:08.480> internal<00:57:09.040> or<00:57:09.280> regulatory 00:57:09.910 --> 00:57:09.920 align:start position:0% compliance with internal or regulatory 00:57:09.920 --> 00:57:11.670 align:start position:0% compliance with internal or regulatory standards. 00:57:11.670 --> 00:57:11.680 align:start position:0% standards. 00:57:11.680 --> 00:57:13.750 align:start position:0% standards. A<00:57:11.920> well-designed<00:57:12.640> authentication<00:57:13.440> and 00:57:13.750 --> 00:57:13.760 align:start position:0% A well-designed authentication and 00:57:13.760 --> 00:57:16.150 align:start position:0% A well-designed authentication and access<00:57:14.240> configuration<00:57:14.880> model<00:57:15.680> allows 00:57:16.150 --> 00:57:16.160 align:start position:0% access configuration model allows 00:57:16.160 --> 00:57:18.549 align:start position:0% access configuration model allows enterprises<00:57:16.799> to<00:57:16.960> use<00:57:17.280> codec<00:57:17.839> safely<00:57:18.240> and 00:57:18.549 --> 00:57:18.559 align:start position:0% enterprises to use codec safely and 00:57:18.559 --> 00:57:20.150 align:start position:0% enterprises to use codec safely and efficiently. 00:57:20.150 --> 00:57:20.160 align:start position:0% efficiently. 00:57:20.160 --> 00:57:22.309 align:start position:0% efficiently. It<00:57:20.400> protects<00:57:20.880> sensitive<00:57:21.359> assets<00:57:21.760> while<00:57:22.079> still 00:57:22.309 --> 00:57:22.319 align:start position:0% It protects sensitive assets while still 00:57:22.319 --> 00:57:24.710 align:start position:0% It protects sensitive assets while still enabling<00:57:22.799> developers<00:57:23.359> to<00:57:23.599> benefit<00:57:23.920> from<00:57:24.240> AI 00:57:24.710 --> 00:57:24.720 align:start position:0% enabling developers to benefit from AI 00:57:24.720 --> 00:57:26.710 align:start position:0% enabling developers to benefit from AI assisted<00:57:25.200> coding. 00:57:26.710 --> 00:57:26.720 align:start position:0% assisted coding. 00:57:26.720 --> 00:57:28.470 align:start position:0% assisted coding. By<00:57:27.040> combining<00:57:27.599> strong<00:57:28.079> identity 00:57:28.470 --> 00:57:28.480 align:start position:0% By combining strong identity 00:57:28.480 --> 00:57:31.829 align:start position:0% By combining strong identity verification,<00:57:29.839> scoped<00:57:30.319> permissions,<00:57:31.359> secure 00:57:31.829 --> 00:57:31.839 align:start position:0% verification, scoped permissions, secure 00:57:31.839 --> 00:57:33.910 align:start position:0% verification, scoped permissions, secure secret<00:57:32.240> handling,<00:57:33.040> and<00:57:33.359> continuous 00:57:33.910 --> 00:57:33.920 align:start position:0% secret handling, and continuous 00:57:33.920 --> 00:57:36.870 align:start position:0% secret handling, and continuous monitoring,<00:57:35.200> organizations<00:57:36.079> can<00:57:36.319> create<00:57:36.640> a 00:57:36.870 --> 00:57:36.880 align:start position:0% monitoring, organizations can create a 00:57:36.880 --> 00:57:39.109 align:start position:0% monitoring, organizations can create a controlled<00:57:37.359> environment<00:57:38.160> where<00:57:38.559> codeex 00:57:39.109 --> 00:57:39.119 align:start position:0% controlled environment where codeex 00:57:39.119 --> 00:57:41.910 align:start position:0% controlled environment where codeex improves<00:57:39.680> productivity<00:57:40.799> without<00:57:41.280> increasing 00:57:41.910 --> 00:57:41.920 align:start position:0% improves productivity without increasing 00:57:41.920 --> 00:57:44.390 align:start position:0% improves productivity without increasing operational<00:57:42.559> risk.<00:57:43.119> We<00:57:43.359> discuss<00:57:43.839> codeex 00:57:44.390 --> 00:57:44.400 align:start position:0% operational risk. We discuss codeex 00:57:44.400 --> 00:57:47.510 align:start position:0% operational risk. We discuss codeex workflows.<00:57:45.119> Now<00:57:46.079> we<00:57:46.319> want<00:57:46.480> to<00:57:46.640> see<00:57:46.720> how<00:57:46.960> codeex 00:57:47.510 --> 00:57:47.520 align:start position:0% workflows. Now we want to see how codeex 00:57:47.520 --> 00:57:50.230 align:start position:0% workflows. Now we want to see how codeex uses<00:57:47.920> large<00:57:48.240> workflows.<00:57:49.599> We<00:57:49.839> look<00:57:50.000> at 00:57:50.230 --> 00:57:50.240 align:start position:0% uses large workflows. We look at 00:57:50.240 --> 00:57:51.750 align:start position:0% uses large workflows. We look at complete<00:57:50.640> software<00:57:51.119> solutions<00:57:51.520> and 00:57:51.750 --> 00:57:51.760 align:start position:0% complete software solutions and 00:57:51.760 --> 00:57:53.750 align:start position:0% complete software solutions and workability. 00:57:53.750 --> 00:57:53.760 align:start position:0% workability. 00:57:53.760 --> 00:57:55.670 align:start position:0% workability. Sometimes<00:57:54.400> we<00:57:54.640> must<00:57:54.880> see<00:57:55.040> how<00:57:55.200> the<00:57:55.440> whole 00:57:55.670 --> 00:57:55.680 align:start position:0% Sometimes we must see how the whole 00:57:55.680 --> 00:57:58.390 align:start position:0% Sometimes we must see how the whole process<00:57:56.160> grows<00:57:56.480> over<00:57:56.799> time.<00:57:57.599> For<00:57:57.839> this<00:57:58.160> we 00:57:58.390 --> 00:57:58.400 align:start position:0% process grows over time. For this we 00:57:58.400 --> 00:58:00.390 align:start position:0% process grows over time. For this we change<00:57:58.720> and<00:57:58.960> improve<00:57:59.359> code<00:57:59.680> on<00:57:59.839> a<00:58:00.079> large 00:58:00.390 --> 00:58:00.400 align:start position:0% change and improve code on a large 00:58:00.400 --> 00:58:03.589 align:start position:0% change and improve code on a large scale.<00:58:01.839> After<00:58:02.079> these<00:58:02.400> changes<00:58:02.880> we<00:58:03.119> check<00:58:03.359> the 00:58:03.589 --> 00:58:03.599 align:start position:0% scale. After these changes we check the 00:58:03.599 --> 00:58:06.069 align:start position:0% scale. After these changes we check the overall<00:58:04.000> process<00:58:04.480> understanding. 00:58:06.069 --> 00:58:06.079 align:start position:0% overall process understanding. 00:58:06.079 --> 00:58:09.270 align:start position:0% overall process understanding. I<00:58:06.400> will<00:58:06.559> tell<00:58:06.720> you<00:58:06.960> about<00:58:07.200> codeex<00:58:07.839> workflows. 00:58:09.270 --> 00:58:09.280 align:start position:0% I will tell you about codeex workflows. 00:58:09.280 --> 00:58:11.430 align:start position:0% I will tell you about codeex workflows. Codeex<00:58:09.839> helps<00:58:10.079> developers<00:58:10.640> in<00:58:10.799> the<00:58:10.960> software 00:58:11.430 --> 00:58:11.440 align:start position:0% Codeex helps developers in the software 00:58:11.440 --> 00:58:13.670 align:start position:0% Codeex helps developers in the software development<00:58:11.920> life<00:58:12.160> cycle.<00:58:13.200> It<00:58:13.440> does 00:58:13.670 --> 00:58:13.680 align:start position:0% development life cycle. It does 00:58:13.680 --> 00:58:16.230 align:start position:0% development life cycle. It does repeating<00:58:14.160> tasks.<00:58:15.280> It<00:58:15.440> makes<00:58:15.680> the<00:58:15.839> coding 00:58:16.230 --> 00:58:16.240 align:start position:0% repeating tasks. It makes the coding 00:58:16.240 --> 00:58:19.109 align:start position:0% repeating tasks. It makes the coding environment<00:58:16.799> fast.<00:58:18.000> It<00:58:18.240> helps<00:58:18.480> us<00:58:18.720> understand 00:58:19.109 --> 00:58:19.119 align:start position:0% environment fast. It helps us understand 00:58:19.119 --> 00:58:21.990 align:start position:0% environment fast. It helps us understand how<00:58:19.359> to<00:58:19.520> fix<00:58:19.760> different<00:58:20.160> problems.<00:58:21.520> It<00:58:21.760> helps 00:58:21.990 --> 00:58:22.000 align:start position:0% how to fix different problems. It helps 00:58:22.000 --> 00:58:25.030 align:start position:0% how to fix different problems. It helps us<00:58:22.160> understand<00:58:22.640> different<00:58:23.040> work<00:58:23.359> processes. 00:58:25.030 --> 00:58:25.040 align:start position:0% us understand different work processes. 00:58:25.040 --> 00:58:27.430 align:start position:0% us understand different work processes. The<00:58:25.359> most<00:58:25.680> important<00:58:26.079> discussion<00:58:26.640> is<00:58:26.960> how<00:58:27.200> we 00:58:27.430 --> 00:58:27.440 align:start position:0% The most important discussion is how we 00:58:27.440 --> 00:58:31.109 align:start position:0% The most important discussion is how we use<00:58:27.760> codecs.<00:58:29.200> We<00:58:29.440> start<00:58:29.599> with<00:58:29.760> a<00:58:30.000> prompt.<00:58:30.960> We 00:58:31.109 --> 00:58:31.119 align:start position:0% use codecs. We start with a prompt. We 00:58:31.119 --> 00:58:33.430 align:start position:0% use codecs. We start with a prompt. We can<00:58:31.280> add<00:58:31.520> details<00:58:31.920> in<00:58:32.160> the<00:58:32.240> prompt.<00:58:33.280> This 00:58:33.430 --> 00:58:33.440 align:start position:0% can add details in the prompt. This 00:58:33.440 --> 00:58:36.549 align:start position:0% can add details in the prompt. This helps<00:58:33.760> software<00:58:34.240> work<00:58:34.559> well.<00:58:35.599> We<00:58:35.920> use<00:58:36.160> prompts 00:58:36.549 --> 00:58:36.559 align:start position:0% helps software work well. We use prompts 00:58:36.559 --> 00:58:40.390 align:start position:0% helps software work well. We use prompts to<00:58:36.720> make<00:58:36.960> software<00:58:37.440> processes<00:58:38.079> easy,<00:58:38.799> fast. 00:58:40.390 --> 00:58:40.400 align:start position:0% to make software processes easy, fast. 00:58:40.400 --> 00:58:42.549 align:start position:0% to make software processes easy, fast. We<00:58:40.640> start<00:58:40.880> with<00:58:41.040> the<00:58:41.200> prompt.<00:58:42.000> We<00:58:42.240> can<00:58:42.400> add 00:58:42.549 --> 00:58:42.559 align:start position:0% We start with the prompt. We can add 00:58:42.559 --> 00:58:45.190 align:start position:0% We start with the prompt. We can add details<00:58:42.960> in<00:58:43.119> the<00:58:43.280> prompt.<00:58:44.480> The<00:58:44.799> important 00:58:45.190 --> 00:58:45.200 align:start position:0% details in the prompt. The important 00:58:45.200 --> 00:58:46.789 align:start position:0% details in the prompt. The important thing<00:58:45.359> in<00:58:45.520> the<00:58:45.680> prompt<00:58:46.000> is<00:58:46.160> a<00:58:46.319> defined 00:58:46.789 --> 00:58:46.799 align:start position:0% thing in the prompt is a defined 00:58:46.799 --> 00:58:49.430 align:start position:0% thing in the prompt is a defined objective.<00:58:48.079> We<00:58:48.400> must<00:58:48.640> have<00:58:48.799> a<00:58:49.040> defined 00:58:49.430 --> 00:58:49.440 align:start position:0% objective. We must have a defined 00:58:49.440 --> 00:58:51.030 align:start position:0% objective. We must have a defined objective. 00:58:51.030 --> 00:58:51.040 align:start position:0% objective. 00:58:51.040 --> 00:58:52.710 align:start position:0% objective. We<00:58:51.280> bring<00:58:51.440> this<00:58:51.680> objective<00:58:52.240> into<00:58:52.480> our 00:58:52.710 --> 00:58:52.720 align:start position:0% We bring this objective into our 00:58:52.720 --> 00:58:55.270 align:start position:0% We bring this objective into our software<00:58:53.119> and<00:58:53.359> working<00:58:53.760> process. 00:58:55.270 --> 00:58:55.280 align:start position:0% software and working process. 00:58:55.280 --> 00:58:58.069 align:start position:0% software and working process. First,<00:58:55.760> we<00:58:56.000> take<00:58:56.160> the<00:58:56.319> generation<00:58:56.880> process. 00:58:58.069 --> 00:58:58.079 align:start position:0% First, we take the generation process. 00:58:58.079 --> 00:59:00.150 align:start position:0% First, we take the generation process. We<00:58:58.400> understand<00:58:58.799> the<00:58:59.040> process<00:58:59.440> on<00:58:59.599> a<00:58:59.839> large 00:59:00.150 --> 00:59:00.160 align:start position:0% We understand the process on a large 00:59:00.160 --> 00:59:02.630 align:start position:0% We understand the process on a large scale.<00:59:01.280> We<00:59:01.520> see<00:59:01.760> how<00:59:02.000> we<00:59:02.160> generate 00:59:02.630 --> 00:59:02.640 align:start position:0% scale. We see how we generate 00:59:02.640 --> 00:59:04.230 align:start position:0% scale. We see how we generate everything. 00:59:04.230 --> 00:59:04.240 align:start position:0% everything. 00:59:04.240 --> 00:59:07.430 align:start position:0% everything. We<00:59:04.559> have<00:59:04.799> one<00:59:05.119> big<00:59:05.440> question.<00:59:06.799> The<00:59:07.119> question 00:59:07.430 --> 00:59:07.440 align:start position:0% We have one big question. The question 00:59:07.440 --> 00:59:10.309 align:start position:0% We have one big question. The question is<00:59:07.760> how<00:59:07.920> to<00:59:08.160> define<00:59:08.480> the<00:59:08.720> objective. 00:59:10.309 --> 00:59:10.319 align:start position:0% is how to define the objective. 00:59:10.319 --> 00:59:12.950 align:start position:0% is how to define the objective. We<00:59:10.559> look<00:59:10.720> at<00:59:10.880> things<00:59:11.040> to<00:59:11.280> define<00:59:11.599> it.<00:59:12.559> We<00:59:12.720> will 00:59:12.950 --> 00:59:12.960 align:start position:0% We look at things to define it. We will 00:59:12.960 --> 00:59:15.829 align:start position:0% We look at things to define it. We will see<00:59:13.119> how<00:59:13.280> these<00:59:13.599> things<00:59:13.920> work<00:59:14.240> together. 00:59:15.829 --> 00:59:15.839 align:start position:0% see how these things work together. 00:59:15.839 --> 00:59:17.910 align:start position:0% see how these things work together. This<00:59:16.079> is<00:59:16.160> a<00:59:16.480> very<00:59:16.720> strong<00:59:17.119> and<00:59:17.359> important 00:59:17.910 --> 00:59:17.920 align:start position:0% This is a very strong and important 00:59:17.920 --> 00:59:20.549 align:start position:0% This is a very strong and important point.<00:59:18.880> We<00:59:19.200> must<00:59:19.520> know<00:59:19.760> how<00:59:20.000> to<00:59:20.160> set<00:59:20.319> up 00:59:20.549 --> 00:59:20.559 align:start position:0% point. We must know how to set up 00:59:20.559 --> 00:59:23.510 align:start position:0% point. We must know how to set up objectives<00:59:21.040> for<00:59:21.359> large<00:59:21.680> generation. 00:59:23.510 --> 00:59:23.520 align:start position:0% objectives for large generation. 00:59:23.520 --> 00:59:25.510 align:start position:0% objectives for large generation. After<00:59:23.839> we<00:59:24.079> set<00:59:24.240> the<00:59:24.400> objective,<00:59:25.040> we<00:59:25.280> look<00:59:25.359> at 00:59:25.510 --> 00:59:25.520 align:start position:0% After we set the objective, we look at 00:59:25.520 --> 00:59:28.470 align:start position:0% After we set the objective, we look at the<00:59:25.680> next<00:59:25.920> steps.<00:59:27.119> The<00:59:27.359> next<00:59:27.599> step<00:59:27.839> is<00:59:28.079> feature 00:59:28.470 --> 00:59:28.480 align:start position:0% the next steps. The next step is feature 00:59:28.480 --> 00:59:31.190 align:start position:0% the next steps. The next step is feature development.<00:59:29.920> Feature<00:59:30.319> development<00:59:30.799> is<00:59:31.040> a 00:59:31.190 --> 00:59:31.200 align:start position:0% development. Feature development is a 00:59:31.200 --> 00:59:33.750 align:start position:0% development. Feature development is a process<00:59:31.520> in<00:59:31.760> our<00:59:32.000> pipeline. 00:59:33.750 --> 00:59:33.760 align:start position:0% process in our pipeline. 00:59:33.760 --> 00:59:35.910 align:start position:0% process in our pipeline. After<00:59:34.160> development,<00:59:34.960> the<00:59:35.200> next<00:59:35.440> thing<00:59:35.599> is 00:59:35.910 --> 00:59:35.920 align:start position:0% After development, the next thing is 00:59:35.920 --> 00:59:38.630 align:start position:0% After development, the next thing is software<00:59:36.400> defect<00:59:37.040> identification. 00:59:38.630 --> 00:59:38.640 align:start position:0% software defect identification. 00:59:38.640 --> 00:59:40.950 align:start position:0% software defect identification. We<00:59:38.960> must<00:59:39.200> make<00:59:39.440> this<00:59:39.680> defect<00:59:40.319> identification 00:59:40.950 --> 00:59:40.960 align:start position:0% We must make this defect identification 00:59:40.960 --> 00:59:43.190 align:start position:0% We must make this defect identification process<00:59:41.520> strong. 00:59:43.190 --> 00:59:43.200 align:start position:0% process strong. 00:59:43.200 --> 00:59:45.430 align:start position:0% process strong. After<00:59:43.440> we<00:59:43.680> find<00:59:43.920> defects,<00:59:44.559> we<00:59:44.799> move<00:59:44.960> to<00:59:45.200> next 00:59:45.430 --> 00:59:45.440 align:start position:0% After we find defects, we move to next 00:59:45.440 --> 00:59:48.549 align:start position:0% After we find defects, we move to next steps.<00:59:46.799> The<00:59:47.040> next<00:59:47.280> steps<00:59:47.680> are<00:59:47.920> refactoring 00:59:48.549 --> 00:59:48.559 align:start position:0% steps. The next steps are refactoring 00:59:48.559 --> 00:59:50.789 align:start position:0% steps. The next steps are refactoring and<00:59:48.799> optimization. 00:59:50.789 --> 00:59:50.799 align:start position:0% and optimization. 00:59:50.799 --> 00:59:54.069 align:start position:0% and optimization. First,<00:59:51.359> we<00:59:51.599> must<00:59:51.839> define<00:59:52.160> a<00:59:52.400> task.<00:59:53.520> We<00:59:53.839> must 00:59:54.069 --> 00:59:54.079 align:start position:0% First, we must define a task. We must 00:59:54.079 --> 00:59:56.950 align:start position:0% First, we must define a task. We must have<00:59:54.240> a<00:59:54.480> clear<00:59:54.799> task<00:59:55.200> definition. 00:59:56.950 --> 00:59:56.960 align:start position:0% have a clear task definition. 00:59:56.960 --> 00:59:59.030 align:start position:0% have a clear task definition. After<00:59:57.280> we<00:59:57.440> define<00:59:57.760> the<00:59:58.000> task,<00:59:58.400> we<00:59:58.640> provide 00:59:59.030 --> 00:59:59.040 align:start position:0% After we define the task, we provide 00:59:59.040 --> 01:00:01.750 align:start position:0% After we define the task, we provide background<00:59:59.599> context.<01:00:00.960> We<01:00:01.200> provide<01:00:01.520> this 01:00:01.750 --> 01:00:01.760 align:start position:0% background context. We provide this 01:00:01.760 --> 01:00:04.630 align:start position:0% background context. We provide this context<01:00:02.240> on<01:00:02.400> a<01:00:02.640> large<01:00:02.960> scale. 01:00:04.630 --> 01:00:04.640 align:start position:0% context on a large scale. 01:00:04.640 --> 01:00:07.270 align:start position:0% context on a large scale. I<01:00:04.880> will<01:00:05.040> explain<01:00:05.359> this<01:00:05.599> process<01:00:06.000> to<01:00:06.160> you.<01:00:07.040> I 01:00:07.270 --> 01:00:07.280 align:start position:0% I will explain this process to you. I 01:00:07.280 --> 01:00:09.190 align:start position:0% I will explain this process to you. I will<01:00:07.440> use<01:00:07.599> a<01:00:07.760> flow<01:00:08.079> diagram<01:00:08.559> to<01:00:08.799> show<01:00:08.960> how 01:00:09.190 --> 01:00:09.200 align:start position:0% will use a flow diagram to show how 01:00:09.200 --> 01:00:11.030 align:start position:0% will use a flow diagram to show how things<01:00:09.520> work. 01:00:11.030 --> 01:00:11.040 align:start position:0% things work. 01:00:11.040 --> 01:00:14.309 align:start position:0% things work. First,<01:00:11.520> we<01:00:11.760> have<01:00:11.839> the<01:00:12.079> task<01:00:12.559> definition. 01:00:14.309 --> 01:00:14.319 align:start position:0% First, we have the task definition. 01:00:14.319 --> 01:00:17.910 align:start position:0% First, we have the task definition. Next,<01:00:14.720> we<01:00:14.960> have<01:00:15.200> task<01:00:15.760> context.<01:00:17.119> We<01:00:17.359> must<01:00:17.680> know 01:00:17.910 --> 01:00:17.920 align:start position:0% Next, we have task context. We must know 01:00:17.920 --> 01:00:20.549 align:start position:0% Next, we have task context. We must know how<01:00:18.160> to<01:00:18.319> add<01:00:18.559> the<01:00:18.720> context. 01:00:20.549 --> 01:00:20.559 align:start position:0% how to add the context. 01:00:20.559 --> 01:00:22.710 align:start position:0% how to add the context. After<01:00:20.799> the<01:00:21.040> context,<01:00:21.599> we<01:00:21.839> need<01:00:22.000> a<01:00:22.160> detailed 01:00:22.710 --> 01:00:22.720 align:start position:0% After the context, we need a detailed 01:00:22.720 --> 01:00:25.670 align:start position:0% After the context, we need a detailed prompt.<01:00:24.160> Then,<01:00:24.480> we<01:00:24.720> connect<01:00:25.040> our<01:00:25.280> main 01:00:25.670 --> 01:00:25.680 align:start position:0% prompt. Then, we connect our main 01:00:25.680 --> 01:00:27.190 align:start position:0% prompt. Then, we connect our main codeex. 01:00:27.190 --> 01:00:27.200 align:start position:0% codeex. 01:00:27.200 --> 01:00:29.190 align:start position:0% codeex. We<01:00:27.440> connect<01:00:27.839> codeex<01:00:28.319> with<01:00:28.480> our<01:00:28.640> own<01:00:28.880> code 01:00:29.190 --> 01:00:29.200 align:start position:0% We connect codeex with our own code 01:00:29.200 --> 01:00:32.309 align:start position:0% We connect codeex with our own code bases.<01:00:30.640> We<01:00:30.880> connect<01:00:31.280> codeex<01:00:31.760> with<01:00:31.920> our<01:00:32.079> code 01:00:32.309 --> 01:00:32.319 align:start position:0% bases. We connect codeex with our code 01:00:32.319 --> 01:00:35.670 align:start position:0% bases. We connect codeex with our code bases<01:00:32.799> to<01:00:33.040> show<01:00:33.280> complete<01:00:33.760> analysis. 01:00:35.670 --> 01:00:35.680 align:start position:0% bases to show complete analysis. 01:00:35.680 --> 01:00:37.990 align:start position:0% bases to show complete analysis. After<01:00:36.079> analysis,<01:00:36.799> we<01:00:37.040> must<01:00:37.280> have<01:00:37.520> solution 01:00:37.990 --> 01:00:38.000 align:start position:0% After analysis, we must have solution 01:00:38.000 --> 01:00:39.589 align:start position:0% After analysis, we must have solution generation. 01:00:39.589 --> 01:00:39.599 align:start position:0% generation. 01:00:39.599 --> 01:00:42.710 align:start position:0% generation. Solution<01:00:40.079> generation<01:00:40.640> must<01:00:41.040> be<01:00:41.200> available. 01:00:42.710 --> 01:00:42.720 align:start position:0% Solution generation must be available. 01:00:42.720 --> 01:00:45.109 align:start position:0% Solution generation must be available. After<01:00:43.119> solution<01:00:43.599> generation,<01:00:44.400> the<01:00:44.640> next<01:00:44.880> step 01:00:45.109 --> 01:00:45.119 align:start position:0% After solution generation, the next step 01:00:45.119 --> 01:00:47.190 align:start position:0% After solution generation, the next step is<01:00:45.440> review. 01:00:47.190 --> 01:00:47.200 align:start position:0% is review. 01:00:47.200 --> 01:00:48.950 align:start position:0% is review. I<01:00:47.440> tell<01:00:47.599> you<01:00:47.839> we<01:00:48.000> need<01:00:48.160> these<01:00:48.480> things<01:00:48.640> in<01:00:48.799> our 01:00:48.950 --> 01:00:48.960 align:start position:0% I tell you we need these things in our 01:00:48.960 --> 01:00:51.670 align:start position:0% I tell you we need these things in our prompt.<01:00:50.079> When<01:00:50.319> we<01:00:50.559> have<01:00:50.640> these<01:00:50.960> things,<01:00:51.359> our 01:00:51.670 --> 01:00:51.680 align:start position:0% prompt. When we have these things, our 01:00:51.680 --> 01:00:53.670 align:start position:0% prompt. When we have these things, our prompt<01:00:52.079> starts. 01:00:53.670 --> 01:00:53.680 align:start position:0% prompt starts. 01:00:53.680 --> 01:00:55.510 align:start position:0% prompt starts. Inside<01:00:54.079> this<01:00:54.400> prompt,<01:00:54.799> our<01:00:55.040> solution 01:00:55.510 --> 01:00:55.520 align:start position:0% Inside this prompt, our solution 01:00:55.520 --> 01:00:58.630 align:start position:0% Inside this prompt, our solution generation<01:00:56.160> process<01:00:56.640> starts.<01:00:58.000> Here<01:00:58.240> we<01:00:58.480> have 01:00:58.630 --> 01:00:58.640 align:start position:0% generation process starts. Here we have 01:00:58.640 --> 01:01:00.950 align:start position:0% generation process starts. Here we have our<01:00:58.880> solution<01:00:59.280> generation. 01:01:00.950 --> 01:01:00.960 align:start position:0% our solution generation. 01:01:00.960 --> 01:01:02.789 align:start position:0% our solution generation. After<01:01:01.280> we<01:01:01.440> generate<01:01:01.839> the<01:01:02.000> solution,<01:01:02.559> we 01:01:02.789 --> 01:01:02.799 align:start position:0% After we generate the solution, we 01:01:02.799 --> 01:01:05.430 align:start position:0% After we generate the solution, we review<01:01:03.119> it.<01:01:04.160> We<01:01:04.400> check<01:01:04.720> everything<01:01:05.040> in<01:01:05.280> the 01:01:05.430 --> 01:01:05.440 align:start position:0% review it. We check everything in the 01:01:05.440 --> 01:01:07.270 align:start position:0% review it. We check everything in the review<01:01:05.760> step. 01:01:07.270 --> 01:01:07.280 align:start position:0% review step. 01:01:07.280 --> 01:01:09.109 align:start position:0% review step. After<01:01:07.599> the<01:01:07.839> review,<01:01:08.319> another<01:01:08.720> process 01:01:09.109 --> 01:01:09.119 align:start position:0% After the review, another process 01:01:09.119 --> 01:01:11.750 align:start position:0% After the review, another process starts.<01:01:10.240> We<01:01:10.480> call<01:01:10.640> this<01:01:10.960> new<01:01:11.200> process 01:01:11.750 --> 01:01:11.760 align:start position:0% starts. We call this new process 01:01:11.760 --> 01:01:13.430 align:start position:0% starts. We call this new process testing. 01:01:13.430 --> 01:01:13.440 align:start position:0% testing. 01:01:13.440 --> 01:01:16.390 align:start position:0% testing. Testing<01:01:14.000> is<01:01:14.240> very<01:01:14.640> important<01:01:15.040> here.<01:01:16.079> In 01:01:16.390 --> 01:01:16.400 align:start position:0% Testing is very important here. In 01:01:16.400 --> 01:01:19.190 align:start position:0% Testing is very important here. In testing,<01:01:16.880> we<01:01:17.040> include<01:01:17.440> debugging.<01:01:18.880> Both 01:01:19.190 --> 01:01:19.200 align:start position:0% testing, we include debugging. Both 01:01:19.200 --> 01:01:21.270 align:start position:0% testing, we include debugging. Both testing<01:01:19.680> and<01:01:20.000> debugging<01:01:20.640> must<01:01:20.960> happen 01:01:21.270 --> 01:01:21.280 align:start position:0% testing and debugging must happen 01:01:21.280 --> 01:01:25.109 align:start position:0% testing and debugging must happen together.<01:01:22.480> We<01:01:22.720> need<01:01:22.960> both<01:01:23.280> in<01:01:23.520> our<01:01:23.680> workflow. 01:01:25.109 --> 01:01:25.119 align:start position:0% together. We need both in our workflow. 01:01:25.119 --> 01:01:28.230 align:start position:0% together. We need both in our workflow. They<01:01:25.359> help<01:01:25.599> us<01:01:25.839> find<01:01:26.079> and<01:01:26.400> fix<01:01:26.799> problems. 01:01:28.230 --> 01:01:28.240 align:start position:0% They help us find and fix problems. 01:01:28.240 --> 01:01:30.470 align:start position:0% They help us find and fix problems. These<01:01:28.559> steps<01:01:28.960> make<01:01:29.119> the<01:01:29.359> software<01:01:29.839> better<01:01:30.160> and 01:01:30.470 --> 01:01:30.480 align:start position:0% These steps make the software better and 01:01:30.480 --> 01:01:32.870 align:start position:0% These steps make the software better and ready<01:01:30.640> for<01:01:30.880> final<01:01:31.280> stages. 01:01:32.870 --> 01:01:32.880 align:start position:0% ready for final stages. 01:01:32.880 --> 01:01:35.190 align:start position:0% ready for final stages. Both<01:01:33.280> testing<01:01:33.680> and<01:01:34.000> debugging<01:01:34.640> must<01:01:35.040> be 01:01:35.190 --> 01:01:35.200 align:start position:0% Both testing and debugging must be 01:01:35.200 --> 01:01:38.309 align:start position:0% Both testing and debugging must be present.<01:01:36.640> The<01:01:36.960> last<01:01:37.119> step<01:01:37.359> available<01:01:37.839> here<01:01:38.079> is 01:01:38.309 --> 01:01:38.319 align:start position:0% present. The last step available here is 01:01:38.319 --> 01:01:41.030 align:start position:0% present. The last step available here is refinement.<01:01:39.760> We<01:01:40.000> call<01:01:40.240> this<01:01:40.480> refinement 01:01:41.030 --> 01:01:41.040 align:start position:0% refinement. We call this refinement 01:01:41.040 --> 01:01:43.190 align:start position:0% refinement. We call this refinement process<01:01:41.599> iteration. 01:01:43.190 --> 01:01:43.200 align:start position:0% process iteration. 01:01:43.200 --> 01:01:45.030 align:start position:0% process iteration. We<01:01:43.440> do<01:01:43.680> refinement<01:01:44.160> to<01:01:44.400> make<01:01:44.559> software 01:01:45.030 --> 01:01:45.040 align:start position:0% We do refinement to make software 01:01:45.040 --> 01:01:48.150 align:start position:0% We do refinement to make software better.<01:01:46.480> After<01:01:46.799> the<01:01:46.960> refinement<01:01:47.520> step,<01:01:47.920> we 01:01:48.150 --> 01:01:48.160 align:start position:0% better. After the refinement step, we 01:01:48.160 --> 01:01:51.109 align:start position:0% better. After the refinement step, we commit<01:01:48.480> changes.<01:01:49.839> We<01:01:50.079> save<01:01:50.319> all<01:01:50.559> the<01:01:50.799> changes 01:01:51.109 --> 01:01:51.119 align:start position:0% commit changes. We save all the changes 01:01:51.119 --> 01:01:55.190 align:start position:0% commit changes. We save all the changes we<01:01:51.359> made.<01:01:52.640> This<01:01:52.960> is<01:01:53.119> the<01:01:53.359> complete<01:01:53.760> process. 01:01:55.190 --> 01:01:55.200 align:start position:0% we made. This is the complete process. 01:01:55.200 --> 01:01:58.150 align:start position:0% we made. This is the complete process. At<01:01:55.440> the<01:01:55.599> end,<01:01:55.920> our<01:01:56.160> workflow<01:01:56.640> closes.<01:01:57.920> It 01:01:58.150 --> 01:01:58.160 align:start position:0% At the end, our workflow closes. It 01:01:58.160 --> 01:02:01.349 align:start position:0% At the end, our workflow closes. It closes<01:01:58.640> at<01:01:58.880> the<01:01:59.040> deployment<01:01:59.520> stage.<01:02:00.720> We<01:02:00.960> go<01:02:01.119> to 01:02:01.349 --> 01:02:01.359 align:start position:0% closes at the deployment stage. We go to 01:02:01.359 --> 01:02:02.630 align:start position:0% closes at the deployment stage. We go to deployment. 01:02:02.630 --> 01:02:02.640 align:start position:0% deployment. 01:02:02.640 --> 01:02:05.829 align:start position:0% deployment. We<01:02:02.880> deploy<01:02:03.200> our<01:02:03.440> project<01:02:03.839> into<01:02:04.160> our<01:02:04.480> system. 01:02:05.829 --> 01:02:05.839 align:start position:0% We deploy our project into our system. 01:02:05.839 --> 01:02:07.670 align:start position:0% We deploy our project into our system. These<01:02:06.160> steps<01:02:06.480> are<01:02:06.720> helpful<01:02:07.040> on<01:02:07.200> a<01:02:07.440> large 01:02:07.670 --> 01:02:07.680 align:start position:0% These steps are helpful on a large 01:02:07.680 --> 01:02:10.150 align:start position:0% These steps are helpful on a large scale.<01:02:08.799> They<01:02:09.040> help<01:02:09.280> us<01:02:09.440> create<01:02:09.680> a<01:02:09.920> better 01:02:10.150 --> 01:02:10.160 align:start position:0% scale. They help us create a better 01:02:10.160 --> 01:02:12.549 align:start position:0% scale. They help us create a better score.<01:02:11.200> They<01:02:11.440> help<01:02:11.599> us<01:02:11.839> create<01:02:12.079> a<01:02:12.319> better 01:02:12.549 --> 01:02:12.559 align:start position:0% score. They help us create a better 01:02:12.559 --> 01:02:15.589 align:start position:0% score. They help us create a better decision<01:02:12.960> tree<01:02:13.200> for<01:02:13.440> work.<01:02:14.880> This<01:02:15.040> is<01:02:15.200> how<01:02:15.359> the 01:02:15.589 --> 01:02:15.599 align:start position:0% decision tree for work. This is how the 01:02:15.599 --> 01:02:17.750 align:start position:0% decision tree for work. This is how the complete<01:02:16.000> workflow<01:02:16.559> operates<01:02:17.040> from<01:02:17.280> start<01:02:17.440> to 01:02:17.750 --> 01:02:17.760 align:start position:0% complete workflow operates from start to 01:02:17.760 --> 01:02:20.390 align:start position:0% complete workflow operates from start to finish.<01:02:18.720> We<01:02:18.960> follow<01:02:19.200> these<01:02:19.599> simple<01:02:19.839> rules<01:02:20.160> to 01:02:20.390 --> 01:02:20.400 align:start position:0% finish. We follow these simple rules to 01:02:20.400 --> 01:02:23.109 align:start position:0% finish. We follow these simple rules to make<01:02:20.559> good<01:02:20.799> software.<01:02:22.160> Every<01:02:22.559> step<01:02:22.880> is 01:02:23.109 --> 01:02:23.119 align:start position:0% make good software. Every step is 01:02:23.119 --> 01:02:25.430 align:start position:0% make good software. Every step is important<01:02:23.440> for<01:02:23.680> the<01:02:23.839> final<01:02:24.160> product. 01:02:25.430 --> 01:02:25.440 align:start position:0% important for the final product. 01:02:25.440 --> 01:02:27.430 align:start position:0% important for the final product. Deployment<01:02:26.000> is<01:02:26.240> the<01:02:26.400> final<01:02:26.720> goal<01:02:26.960> of<01:02:27.200> this 01:02:27.430 --> 01:02:27.440 align:start position:0% Deployment is the final goal of this 01:02:27.440 --> 01:02:30.950 align:start position:0% Deployment is the final goal of this journey.<01:02:28.160> Our<01:02:28.480> next<01:02:28.720> talk<01:02:29.040> is<01:02:29.280> about<01:02:29.680> codecs. 01:02:30.950 --> 01:02:30.960 align:start position:0% journey. Our next talk is about codecs. 01:02:30.960 --> 01:02:32.710 align:start position:0% journey. Our next talk is about codecs. We<01:02:31.200> will<01:02:31.440> learn<01:02:31.599> about<01:02:31.839> our<01:02:32.079> projects<01:02:32.480> in 01:02:32.710 --> 01:02:32.720 align:start position:0% We will learn about our projects in 01:02:32.720 --> 01:02:35.750 align:start position:0% We will learn about our projects in codecs.<01:02:34.000> Project<01:02:34.400> navigation<01:02:35.040> is<01:02:35.200> a<01:02:35.440> very 01:02:35.750 --> 01:02:35.760 align:start position:0% codecs. Project navigation is a very 01:02:35.760 --> 01:02:37.990 align:start position:0% codecs. Project navigation is a very important<01:02:36.240> AI<01:02:36.720> skill<01:02:36.960> in<01:02:37.200> modern<01:02:37.520> software 01:02:37.990 --> 01:02:38.000 align:start position:0% important AI skill in modern software 01:02:38.000 --> 01:02:41.190 align:start position:0% important AI skill in modern software development.<01:02:39.359> In<01:02:39.599> big<01:02:39.920> business<01:02:40.319> places, 01:02:41.190 --> 01:02:41.200 align:start position:0% development. In big business places, 01:02:41.200 --> 01:02:43.270 align:start position:0% development. In big business places, developers<01:02:41.839> work<01:02:42.000> with<01:02:42.319> big<01:02:42.640> repositories. 01:02:43.270 --> 01:02:43.280 align:start position:0% developers work with big repositories. 01:02:43.280 --> 01:02:46.309 align:start position:0% developers work with big repositories. Often<01:02:44.480> these<01:02:44.880> repositories<01:02:45.520> have<01:02:45.839> thousands 01:02:46.309 --> 01:02:46.319 align:start position:0% Often these repositories have thousands 01:02:46.319 --> 01:02:48.870 align:start position:0% Often these repositories have thousands of<01:02:46.480> files.<01:02:47.680> We<01:02:47.920> can<01:02:48.079> see<01:02:48.240> our<01:02:48.480> multiple 01:02:48.870 --> 01:02:48.880 align:start position:0% of files. We can see our multiple 01:02:48.880 --> 01:02:52.069 align:start position:0% of files. We can see our multiple services<01:02:49.440> directly.<01:02:50.880> It<01:02:51.119> also<01:02:51.440> sees<01:02:51.760> big 01:02:52.069 --> 01:02:52.079 align:start position:0% services directly. It also sees big 01:02:52.079 --> 01:02:55.190 align:start position:0% services directly. It also sees big documentation,<01:02:53.359> complex<01:02:53.839> dependencies,<01:02:54.880> and 01:02:55.190 --> 01:02:55.200 align:start position:0% documentation, complex dependencies, and 01:02:55.200 --> 01:02:58.309 align:start position:0% documentation, complex dependencies, and multiple<01:02:55.680> servers.<01:02:56.799> Understanding<01:02:58.000> these 01:02:58.309 --> 01:02:58.319 align:start position:0% multiple servers. Understanding these 01:02:58.319 --> 01:03:00.390 align:start position:0% multiple servers. Understanding these projects<01:02:58.720> by<01:02:58.960> hand<01:02:59.280> needs<01:02:59.680> much<01:03:00.000> time<01:03:00.160> and 01:03:00.390 --> 01:03:00.400 align:start position:0% projects by hand needs much time and 01:03:00.400 --> 01:03:03.349 align:start position:0% projects by hand needs much time and effort.<01:03:01.760> Codeex<01:03:02.480> helps<01:03:02.799> developers 01:03:03.349 --> 01:03:03.359 align:start position:0% effort. Codeex helps developers 01:03:03.359 --> 01:03:06.069 align:start position:0% effort. Codeex helps developers understand<01:03:03.760> the<01:03:04.079> project<01:03:04.400> structures<01:03:04.960> well. 01:03:06.069 --> 01:03:06.079 align:start position:0% understand the project structures well. 01:03:06.079 --> 01:03:08.549 align:start position:0% understand the project structures well. It<01:03:06.400> finds<01:03:06.720> correct<01:03:07.119> files,<01:03:08.079> traces 01:03:08.549 --> 01:03:08.559 align:start position:0% It finds correct files, traces 01:03:08.559 --> 01:03:10.630 align:start position:0% It finds correct files, traces dependencies,<01:03:09.680> and<01:03:09.920> locates<01:03:10.400> our 01:03:10.630 --> 01:03:10.640 align:start position:0% dependencies, and locates our 01:03:10.640 --> 01:03:13.109 align:start position:0% dependencies, and locates our implementation<01:03:11.359> details. 01:03:13.109 --> 01:03:13.119 align:start position:0% implementation details. 01:03:13.119 --> 01:03:15.829 align:start position:0% implementation details. I<01:03:13.359> go<01:03:13.520> to<01:03:13.599> the<01:03:13.839> project<01:03:14.160> menu<01:03:14.480> directly.<01:03:15.599> I 01:03:15.829 --> 01:03:15.839 align:start position:0% I go to the project menu directly. I 01:03:15.839 --> 01:03:18.870 align:start position:0% I go to the project menu directly. I click<01:03:16.240> start<01:03:16.480> from<01:03:16.720> scratch.<01:03:18.000> I<01:03:18.240> name<01:03:18.480> the<01:03:18.720> new 01:03:18.870 --> 01:03:18.880 align:start position:0% click start from scratch. I name the new 01:03:18.880 --> 01:03:21.190 align:start position:0% click start from scratch. I name the new project<01:03:19.520> Metabrains. 01:03:21.190 --> 01:03:21.200 align:start position:0% project Metabrains. 01:03:21.200 --> 01:03:24.390 align:start position:0% project Metabrains. I<01:03:21.520> start<01:03:21.839> one<01:03:22.160> project<01:03:22.640> directly<01:03:23.200> here.<01:03:24.079> I 01:03:24.390 --> 01:03:24.400 align:start position:0% I start one project directly here. I 01:03:24.400 --> 01:03:28.069 align:start position:0% I start one project directly here. I save<01:03:24.640> it.<01:03:25.839> Now<01:03:26.079> we<01:03:26.319> have<01:03:26.400> a<01:03:26.559> new<01:03:26.799> project. 01:03:28.069 --> 01:03:28.079 align:start position:0% save it. Now we have a new project. 01:03:28.079 --> 01:03:29.990 align:start position:0% save it. Now we have a new project. There<01:03:28.319> is<01:03:28.480> no<01:03:28.720> chat<01:03:29.039> available<01:03:29.440> yet<01:03:29.680> in<01:03:29.839> the 01:03:29.990 --> 01:03:30.000 align:start position:0% There is no chat available yet in the 01:03:30.000 --> 01:03:32.950 align:start position:0% There is no chat available yet in the project.<01:03:31.200> You<01:03:31.440> see<01:03:31.599> our<01:03:31.839> explorer<01:03:32.319> and<01:03:32.559> object 01:03:32.950 --> 01:03:32.960 align:start position:0% project. You see our explorer and object 01:03:32.960 --> 01:03:34.470 align:start position:0% project. You see our explorer and object options. 01:03:34.470 --> 01:03:34.480 align:start position:0% options. 01:03:34.480 --> 01:03:36.950 align:start position:0% options. If<01:03:34.720> we<01:03:34.880> turn<01:03:35.039> on<01:03:35.280> the<01:03:35.440> explorer,<01:03:36.319> our<01:03:36.640> file 01:03:36.950 --> 01:03:36.960 align:start position:0% If we turn on the explorer, our file 01:03:36.960 --> 01:03:39.029 align:start position:0% If we turn on the explorer, our file opens<01:03:37.359> automatically. 01:03:39.029 --> 01:03:39.039 align:start position:0% opens automatically. 01:03:39.039 --> 01:03:40.630 align:start position:0% opens automatically. You<01:03:39.280> can<01:03:39.359> see<01:03:39.520> we<01:03:39.839> have<01:03:39.920> no<01:03:40.240> document 01:03:40.630 --> 01:03:40.640 align:start position:0% You can see we have no document 01:03:40.640 --> 01:03:43.910 align:start position:0% You can see we have no document available<01:03:41.119> yet.<01:03:42.240> With<01:03:42.559> time<01:03:43.280> we<01:03:43.520> will<01:03:43.680> make 01:03:43.910 --> 01:03:43.920 align:start position:0% available yet. With time we will make 01:03:43.920 --> 01:03:46.230 align:start position:0% available yet. With time we will make many<01:03:44.240> additions<01:03:44.640> and<01:03:44.880> changes. 01:03:46.230 --> 01:03:46.240 align:start position:0% many additions and changes. 01:03:46.240 --> 01:03:48.470 align:start position:0% many additions and changes. Automatically<01:03:47.119> our<01:03:47.359> response<01:03:47.839> and<01:03:48.079> style 01:03:48.470 --> 01:03:48.480 align:start position:0% Automatically our response and style 01:03:48.480 --> 01:03:50.390 align:start position:0% Automatically our response and style will<01:03:48.720> change. 01:03:50.390 --> 01:03:50.400 align:start position:0% will change. 01:03:50.400 --> 01:03:52.870 align:start position:0% will change. I<01:03:50.640> will<01:03:50.799> start<01:03:51.039> from<01:03:51.280> the<01:03:51.440> beginning.<01:03:52.480> We<01:03:52.720> will 01:03:52.870 --> 01:03:52.880 align:start position:0% I will start from the beginning. We will 01:03:52.880 --> 01:03:54.549 align:start position:0% I will start from the beginning. We will look<01:03:52.960> at<01:03:53.200> all<01:03:53.359> the<01:03:53.520> changes<01:03:53.839> we<01:03:54.160> make<01:03:54.319> from 01:03:54.549 --> 01:03:54.559 align:start position:0% look at all the changes we make from 01:03:54.559 --> 01:03:57.910 align:start position:0% look at all the changes we make from start<01:03:54.880> to<01:03:55.119> now.<01:03:56.400> Along<01:03:56.720> with<01:03:56.960> changes,<01:03:57.680> we 01:03:57.910 --> 01:03:57.920 align:start position:0% start to now. Along with changes, we 01:03:57.920 --> 01:04:00.950 align:start position:0% start to now. Along with changes, we will<01:03:58.079> also<01:03:58.400> see<01:03:58.559> the<01:03:58.880> time.<01:04:00.079> We<01:04:00.319> will<01:04:00.480> see<01:04:00.640> how 01:04:00.950 --> 01:04:00.960 align:start position:0% will also see the time. We will see how 01:04:00.960 --> 01:04:04.390 align:start position:0% will also see the time. We will see how much<01:04:01.200> time<01:04:01.520> one<01:04:01.839> full<01:04:02.160> cycle<01:04:02.559> takes.<01:04:04.000> We<01:04:04.240> can 01:04:04.390 --> 01:04:04.400 align:start position:0% much time one full cycle takes. We can 01:04:04.400 --> 01:04:07.349 align:start position:0% much time one full cycle takes. We can look<01:04:04.559> at<01:04:04.720> the<01:04:04.960> complete<01:04:05.359> process<01:04:05.839> directly. 01:04:07.349 --> 01:04:07.359 align:start position:0% look at the complete process directly. 01:04:07.359 --> 01:04:09.029 align:start position:0% look at the complete process directly. Sometimes<01:04:07.920> we<01:04:08.160> must<01:04:08.319> approve<01:04:08.720> things 01:04:09.029 --> 01:04:09.039 align:start position:0% Sometimes we must approve things 01:04:09.039 --> 01:04:11.589 align:start position:0% Sometimes we must approve things directly<01:04:09.520> to<01:04:09.760> understand<01:04:10.160> them.<01:04:11.039> I<01:04:11.280> will<01:04:11.440> tell 01:04:11.589 --> 01:04:11.599 align:start position:0% directly to understand them. I will tell 01:04:11.599 --> 01:04:14.390 align:start position:0% directly to understand them. I will tell you.<01:04:12.799> I<01:04:13.039> will<01:04:13.200> type<01:04:13.520> what<01:04:13.760> things<01:04:14.079> should<01:04:14.240> be 01:04:14.390 --> 01:04:14.400 align:start position:0% you. I will type what things should be 01:04:14.400 --> 01:04:18.789 align:start position:0% you. I will type what things should be in<01:04:14.559> our<01:04:14.720> project.<01:04:15.839> I<01:04:16.160> write<01:04:17.039> create<01:04:17.359> an<01:04:17.680> agent 01:04:18.789 --> 01:04:18.799 align:start position:0% in our project. I write create an agent 01:04:18.799 --> 01:04:20.710 align:start position:0% in our project. I write create an agent MD<01:04:19.280> file. 01:04:20.710 --> 01:04:20.720 align:start position:0% MD file. 01:04:20.720 --> 01:04:24.390 align:start position:0% MD file. We<01:04:20.960> will<01:04:21.200> create<01:04:21.440> the<01:04:21.680> agent.mmd<01:04:22.880> file<01:04:23.200> here. 01:04:24.390 --> 01:04:24.400 align:start position:0% We will create the agent.mmd file here. 01:04:24.400 --> 01:04:26.309 align:start position:0% We will create the agent.mmd file here. This<01:04:24.640> makes<01:04:24.880> our<01:04:25.039> agent<01:04:25.520> work<01:04:25.680> in<01:04:25.839> a<01:04:26.079> much 01:04:26.309 --> 01:04:26.319 align:start position:0% This makes our agent work in a much 01:04:26.319 --> 01:04:29.750 align:start position:0% This makes our agent work in a much better<01:04:26.640> way.<01:04:27.920> I<01:04:28.240> type<01:04:28.960> because<01:04:29.200> this<01:04:29.440> is<01:04:29.599> a 01:04:29.750 --> 01:04:29.760 align:start position:0% better way. I type because this is a 01:04:29.760 --> 01:04:31.750 align:start position:0% better way. I type because this is a corporate<01:04:30.240> sales<01:04:30.640> manager<01:04:30.960> and<01:04:31.280> content 01:04:31.750 --> 01:04:31.760 align:start position:0% corporate sales manager and content 01:04:31.760 --> 01:04:34.549 align:start position:0% corporate sales manager and content creator<01:04:32.240> project.<01:04:33.520> It<01:04:33.760> will<01:04:33.920> do<01:04:34.079> the<01:04:34.319> first 01:04:34.549 --> 01:04:34.559 align:start position:0% creator project. It will do the first 01:04:34.559 --> 01:04:37.029 align:start position:0% creator project. It will do the first step<01:04:34.720> of<01:04:34.880> our<01:04:35.119> project<01:04:35.520> here. 01:04:37.029 --> 01:04:37.039 align:start position:0% step of our project here. 01:04:37.039 --> 01:04:39.430 align:start position:0% step of our project here. First<01:04:37.280> of<01:04:37.440> all,<01:04:37.920> we<01:04:38.160> give<01:04:38.319> it<01:04:38.480> the<01:04:38.720> context<01:04:39.119> and 01:04:39.430 --> 01:04:39.440 align:start position:0% First of all, we give it the context and 01:04:39.440 --> 01:04:41.190 align:start position:0% First of all, we give it the context and our<01:04:39.680> details. 01:04:41.190 --> 01:04:41.200 align:start position:0% our details. 01:04:41.200 --> 01:04:43.190 align:start position:0% our details. We<01:04:41.440> are<01:04:41.599> making<01:04:41.839> the<01:04:42.160> employee<01:04:42.720> do<01:04:42.880> these 01:04:43.190 --> 01:04:43.200 align:start position:0% We are making the employee do these 01:04:43.200 --> 01:04:45.670 align:start position:0% We are making the employee do these things<01:04:43.520> here.<01:04:44.640> We<01:04:44.880> will<01:04:45.039> include<01:04:45.359> this 01:04:45.670 --> 01:04:45.680 align:start position:0% things here. We will include this 01:04:45.680 --> 01:04:48.309 align:start position:0% things here. We will include this directly<01:04:46.160> for<01:04:46.400> our<01:04:46.640> approval. 01:04:48.309 --> 01:04:48.319 align:start position:0% directly for our approval. 01:04:48.319 --> 01:04:50.470 align:start position:0% directly for our approval. I<01:04:48.640> tell<01:04:48.799> you<01:04:49.039> that<01:04:49.280> a<01:04:49.520> complete<01:04:50.000> process 01:04:50.470 --> 01:04:50.480 align:start position:0% I tell you that a complete process 01:04:50.480 --> 01:04:53.510 align:start position:0% I tell you that a complete process discussion<01:04:50.960> is<01:04:51.200> very<01:04:51.599> important<01:04:52.000> here.<01:04:53.200> In 01:04:53.510 --> 01:04:53.520 align:start position:0% discussion is very important here. In 01:04:53.520 --> 01:04:57.190 align:start position:0% discussion is very important here. In this<01:04:54.160> we<01:04:54.400> have<01:04:54.559> to<01:04:54.799> involve<01:04:55.280> all<01:04:55.520> our<01:04:55.760> details. 01:04:57.190 --> 01:04:57.200 align:start position:0% this we have to involve all our details. 01:04:57.200 --> 01:04:59.349 align:start position:0% this we have to involve all our details. We<01:04:57.440> must<01:04:57.760> involve<01:04:58.160> our<01:04:58.480> full<01:04:58.880> working 01:04:59.349 --> 01:04:59.359 align:start position:0% We must involve our full working 01:04:59.359 --> 01:05:02.390 align:start position:0% We must involve our full working process.<01:04:59.839> Here<01:05:01.280> you<01:05:01.520> can<01:05:01.680> see<01:05:01.839> it<01:05:02.000> will<01:05:02.160> take 01:05:02.390 --> 01:05:02.400 align:start position:0% process. Here you can see it will take 01:05:02.400 --> 01:05:05.270 align:start position:0% process. Here you can see it will take some<01:05:02.640> time.<01:05:02.880> Obviously<01:05:04.319> it<01:05:04.559> is<01:05:04.720> working<01:05:05.039> in 01:05:05.270 --> 01:05:05.280 align:start position:0% some time. Obviously it is working in 01:05:05.280 --> 01:05:08.230 align:start position:0% some time. Obviously it is working in our<01:05:05.520> exact<01:05:05.920> folder.<01:05:07.280> If<01:05:07.520> I<01:05:07.680> refresh<01:05:08.000> our 01:05:08.230 --> 01:05:08.240 align:start position:0% our exact folder. If I refresh our 01:05:08.240 --> 01:05:11.430 align:start position:0% our exact folder. If I refresh our folder<01:05:08.640> here<01:05:09.359> you<01:05:09.599> will<01:05:09.760> see<01:05:09.920> the<01:05:10.079> agent<01:05:11.039> ND 01:05:11.430 --> 01:05:11.440 align:start position:0% folder here you will see the agent ND 01:05:11.440 --> 01:05:13.750 align:start position:0% folder here you will see the agent ND file<01:05:11.760> is<01:05:12.000> created. 01:05:13.750 --> 01:05:13.760 align:start position:0% file is created. 01:05:13.760 --> 01:05:16.710 align:start position:0% file is created. We<01:05:14.000> can<01:05:14.079> directly<01:05:14.640> review<01:05:14.960> it<01:05:15.119> here.<01:05:16.400> It 01:05:16.710 --> 01:05:16.720 align:start position:0% We can directly review it here. It 01:05:16.720 --> 01:05:19.510 align:start position:0% We can directly review it here. It created<01:05:17.039> the<01:05:17.280> agent.mmd<01:05:18.640> file<01:05:19.119> with<01:05:19.359> a 01:05:19.510 --> 01:05:19.520 align:start position:0% created the agent.mmd file with a 01:05:19.520 --> 01:05:22.230 align:start position:0% created the agent.mmd file with a tailored<01:05:20.000> operating<01:05:20.480> brief.<01:05:21.760> This<01:05:21.920> is<01:05:22.079> for 01:05:22.230 --> 01:05:22.240 align:start position:0% tailored operating brief. This is for 01:05:22.240 --> 01:05:24.390 align:start position:0% tailored operating brief. This is for the<01:05:22.480> corporate<01:05:22.880> sales<01:05:23.359> manager<01:05:23.680> and<01:05:24.000> content 01:05:24.390 --> 01:05:24.400 align:start position:0% the corporate sales manager and content 01:05:24.400 --> 01:05:25.910 align:start position:0% the corporate sales manager and content project. 01:05:25.910 --> 01:05:25.920 align:start position:0% project. 01:05:25.920 --> 01:05:30.069 align:start position:0% project. The<01:05:26.160> agent.md<01:05:27.440> file<01:05:27.760> is<01:05:28.000> made<01:05:28.240> here.<01:05:29.680> You<01:05:29.920> can 01:05:30.069 --> 01:05:30.079 align:start position:0% The agent.md file is made here. You can 01:05:30.079 --> 01:05:32.230 align:start position:0% The agent.md file is made here. You can see<01:05:30.319> our<01:05:30.640> exact<01:05:31.119> source<01:05:31.520> code<01:05:31.760> and<01:05:32.000> other 01:05:32.230 --> 01:05:32.240 align:start position:0% see our exact source code and other 01:05:32.240 --> 01:05:34.870 align:start position:0% see our exact source code and other things<01:05:32.480> are<01:05:32.720> available.<01:05:34.079> We<01:05:34.319> can<01:05:34.480> open<01:05:34.720> it 01:05:34.870 --> 01:05:34.880 align:start position:0% things are available. We can open it 01:05:34.880 --> 01:05:38.309 align:start position:0% things are available. We can open it directly<01:05:35.280> in<01:05:35.520> our<01:05:35.680> VS<01:05:36.079> code.<01:05:37.520> We<01:05:37.760> can<01:05:37.920> open<01:05:38.160> it 01:05:38.309 --> 01:05:38.319 align:start position:0% directly in our VS code. We can open it 01:05:38.319 --> 01:05:40.549 align:start position:0% directly in our VS code. We can open it in<01:05:38.480> the<01:05:38.640> default<01:05:39.039> application. 01:05:40.549 --> 01:05:40.559 align:start position:0% in the default application. 01:05:40.559 --> 01:05:43.670 align:start position:0% in the default application. We<01:05:40.799> can<01:05:40.960> also<01:05:41.280> open<01:05:41.520> it<01:05:41.680> in<01:05:41.839> our<01:05:42.000> terminal. 01:05:43.670 --> 01:05:43.680 align:start position:0% We can also open it in our terminal. 01:05:43.680 --> 01:05:46.470 align:start position:0% We can also open it in our terminal. These<01:05:44.079> things<01:05:44.400> are<01:05:44.640> much<01:05:45.039> better<01:05:45.359> here.<01:05:46.240> We 01:05:46.470 --> 01:05:46.480 align:start position:0% These things are much better here. We 01:05:46.480 --> 01:05:49.750 align:start position:0% These things are much better here. We have<01:05:46.640> a<01:05:46.880> complete<01:05:47.359> system<01:05:47.760> environment. 01:05:49.750 --> 01:05:49.760 align:start position:0% have a complete system environment. 01:05:49.760 --> 01:05:52.309 align:start position:0% have a complete system environment. Automatically<01:05:50.799> we<01:05:51.119> see<01:05:51.280> all<01:05:51.599> divisions<01:05:52.079> and 01:05:52.309 --> 01:05:52.319 align:start position:0% Automatically we see all divisions and 01:05:52.319 --> 01:05:55.589 align:start position:0% Automatically we see all divisions and working<01:05:52.640> ability<01:05:53.119> here.<01:05:54.400> Sometimes<01:05:55.280> this 01:05:55.589 --> 01:05:55.599 align:start position:0% working ability here. Sometimes this 01:05:55.599 --> 01:05:57.670 align:start position:0% working ability here. Sometimes this working<01:05:55.920> ability<01:05:56.400> or<01:05:56.720> complete<01:05:57.200> process 01:05:57.670 --> 01:05:57.680 align:start position:0% working ability or complete process 01:05:57.680 --> 01:06:00.950 align:start position:0% working ability or complete process causes<01:05:58.160> problems.<01:05:59.440> It<01:05:59.680> causes<01:06:00.079> problems<01:06:00.480> on<01:06:00.720> a 01:06:00.950 --> 01:06:00.960 align:start position:0% causes problems. It causes problems on a 01:06:00.960 --> 01:06:03.990 align:start position:0% causes problems. It causes problems on a big<01:06:01.200> scale.<01:06:02.480> We<01:06:02.720> see<01:06:02.960> many<01:06:03.280> issues<01:06:03.599> in<01:06:03.760> our 01:06:03.990 --> 01:06:04.000 align:start position:0% big scale. We see many issues in our 01:06:04.000 --> 01:06:05.510 align:start position:0% big scale. We see many issues in our work. 01:06:05.510 --> 01:06:05.520 align:start position:0% work. 01:06:05.520 --> 01:06:08.390 align:start position:0% work. We<01:06:05.839> usually<01:06:06.319> create<01:06:06.640> our<01:06:06.960> complete<01:06:07.520> empty<01:06:07.920> MD 01:06:08.390 --> 01:06:08.400 align:start position:0% We usually create our complete empty MD 01:06:08.400 --> 01:06:10.309 align:start position:0% We usually create our complete empty MD file<01:06:08.720> at<01:06:08.960> the<01:06:09.119> very<01:06:09.440> start<01:06:09.599> of<01:06:09.760> the<01:06:10.000> project 01:06:10.309 --> 01:06:10.319 align:start position:0% file at the very start of the project 01:06:10.319 --> 01:06:14.390 align:start position:0% file at the very start of the project setup.<01:06:11.680> So<01:06:12.240> on<01:06:12.480> a<01:06:12.640> big<01:06:12.880> scale<01:06:13.520> if<01:06:13.760> any<01:06:14.079> issue 01:06:14.390 --> 01:06:14.400 align:start position:0% setup. So on a big scale if any issue 01:06:14.400 --> 01:06:16.630 align:start position:0% setup. So on a big scale if any issue happens<01:06:14.799> later<01:06:15.520> we<01:06:15.760> can<01:06:16.000> understand<01:06:16.400> it 01:06:16.630 --> 01:06:16.640 align:start position:0% happens later we can understand it 01:06:16.640 --> 01:06:19.589 align:start position:0% happens later we can understand it early.<01:06:18.000> We<01:06:18.319> can<01:06:18.480> do<01:06:18.640> things<01:06:18.880> early<01:06:19.280> according 01:06:19.589 --> 01:06:19.599 align:start position:0% early. We can do things early according 01:06:19.599 --> 01:06:22.309 align:start position:0% early. We can do things early according to<01:06:19.760> our<01:06:20.000> system.<01:06:21.280> This<01:06:21.520> is<01:06:21.680> a<01:06:21.920> basic 01:06:22.309 --> 01:06:22.319 align:start position:0% to our system. This is a basic 01:06:22.319 --> 01:06:25.190 align:start position:0% to our system. This is a basic discussion.<01:06:22.880> Now<01:06:24.000> we<01:06:24.319> see<01:06:24.480> how<01:06:24.799> complete 01:06:25.190 --> 01:06:25.200 align:start position:0% discussion. Now we see how complete 01:06:25.200 --> 01:06:28.309 align:start position:0% discussion. Now we see how complete generation<01:06:25.839> happens.<01:06:27.039> We<01:06:27.280> see<01:06:27.440> how<01:06:27.680> we<01:06:27.839> take<01:06:28.000> a 01:06:28.309 --> 01:06:28.319 align:start position:0% generation happens. We see how we take a 01:06:28.319 --> 01:06:30.309 align:start position:0% generation happens. We see how we take a complete<01:06:28.720> process<01:06:29.119> or<01:06:29.440> understanding<01:06:30.079> with 01:06:30.309 --> 01:06:30.319 align:start position:0% complete process or understanding with 01:06:30.319 --> 01:06:34.549 align:start position:0% complete process or understanding with us.<01:06:31.760> After<01:06:32.000> the<01:06:32.240> agent<01:06:33.039> MD<01:06:33.440> file<01:06:34.160> we<01:06:34.400> will 01:06:34.549 --> 01:06:34.559 align:start position:0% us. After the agent MD file we will 01:06:34.559 --> 01:06:37.430 align:start position:0% us. After the agent MD file we will directly<01:06:35.039> look<01:06:35.200> at<01:06:35.359> our<01:06:35.599> project<01:06:35.920> structure. 01:06:37.430 --> 01:06:37.440 align:start position:0% directly look at our project structure. 01:06:37.440 --> 01:06:39.990 align:start position:0% directly look at our project structure. I<01:06:37.680> will<01:06:37.760> go<01:06:37.920> into<01:06:38.160> the<01:06:38.400> exact<01:06:38.720> same<01:06:39.039> folder.<01:06:39.760> I 01:06:39.990 --> 01:06:40.000 align:start position:0% I will go into the exact same folder. I 01:06:40.000 --> 01:06:43.109 align:start position:0% I will go into the exact same folder. I will<01:06:40.160> include<01:06:40.480> a<01:06:40.720> new<01:06:40.880> folder<01:06:41.440> here.<01:06:42.799> This<01:06:42.960> is 01:06:43.109 --> 01:06:43.119 align:start position:0% will include a new folder here. This is 01:06:43.119 --> 01:06:45.829 align:start position:0% will include a new folder here. This is from<01:06:43.280> a<01:06:43.520> previously<01:06:44.000> created<01:06:44.400> section.<01:06:45.680> You 01:06:45.829 --> 01:06:45.839 align:start position:0% from a previously created section. You 01:06:45.839 --> 01:06:47.589 align:start position:0% from a previously created section. You can<01:06:46.000> see<01:06:46.079> our<01:06:46.400> portfolios<01:06:46.960> are<01:06:47.200> available 01:06:47.589 --> 01:06:47.599 align:start position:0% can see our portfolios are available 01:06:47.599 --> 01:06:50.309 align:start position:0% can see our portfolios are available here.<01:06:48.799> I<01:06:49.039> will<01:06:49.200> do<01:06:49.359> all<01:06:49.520> the<01:06:49.760> portfolio 01:06:50.309 --> 01:06:50.319 align:start position:0% here. I will do all the portfolio 01:06:50.319 --> 01:06:53.670 align:start position:0% here. I will do all the portfolio discussion<01:06:50.880> here.<01:06:52.319> I<01:06:52.559> will<01:06:52.720> now<01:06:52.960> analyze<01:06:53.440> our 01:06:53.670 --> 01:06:53.680 align:start position:0% discussion here. I will now analyze our 01:06:53.680 --> 01:06:55.349 align:start position:0% discussion here. I will now analyze our repository. 01:06:55.349 --> 01:06:55.359 align:start position:0% repository. 01:06:55.359 --> 01:06:58.150 align:start position:0% repository. I<01:06:55.680> write<01:06:56.160> analyze<01:06:56.720> this<01:06:56.960> repository<01:06:57.920> and 01:06:58.150 --> 01:06:58.160 align:start position:0% I write analyze this repository and 01:06:58.160 --> 01:07:00.150 align:start position:0% I write analyze this repository and provide<01:06:58.480> a<01:06:58.720> comprehensive<01:06:59.359> overview<01:06:59.760> of<01:06:59.920> the 01:07:00.150 --> 01:07:00.160 align:start position:0% provide a comprehensive overview of the 01:07:00.160 --> 01:07:03.029 align:start position:0% provide a comprehensive overview of the project<01:07:00.480> structure.<01:07:01.920> It<01:07:02.160> includes<01:07:02.559> the<01:07:02.799> main 01:07:03.029 --> 01:07:03.039 align:start position:0% project structure. It includes the main 01:07:03.039 --> 01:07:05.190 align:start position:0% project structure. It includes the main purpose<01:07:03.359> of<01:07:03.520> the<01:07:03.680> application. 01:07:05.190 --> 01:07:05.200 align:start position:0% purpose of the application. 01:07:05.200 --> 01:07:08.230 align:start position:0% purpose of the application. Then<01:07:05.440> we<01:07:05.680> have<01:07:06.000> highlevel<01:07:06.640> architecture. 01:07:08.230 --> 01:07:08.240 align:start position:0% Then we have highlevel architecture. 01:07:08.240 --> 01:07:11.270 align:start position:0% Then we have highlevel architecture. Then<01:07:08.480> we<01:07:08.720> have<01:07:09.039> important<01:07:09.520> directories. 01:07:11.270 --> 01:07:11.280 align:start position:0% Then we have important directories. 01:07:11.280 --> 01:07:13.510 align:start position:0% Then we have important directories. Then<01:07:11.520> we<01:07:11.760> have<01:07:12.000> all<01:07:12.319> options<01:07:12.720> for<01:07:13.039> important 01:07:13.510 --> 01:07:13.520 align:start position:0% Then we have all options for important 01:07:13.520 --> 01:07:16.789 align:start position:0% Then we have all options for important directories<01:07:14.079> on<01:07:14.319> a<01:07:14.480> big<01:07:14.720> scale.<01:07:16.079> After<01:07:16.400> major 01:07:16.789 --> 01:07:16.799 align:start position:0% directories on a big scale. After major 01:07:16.799 --> 01:07:19.990 align:start position:0% directories on a big scale. After major frameworks,<01:07:17.520> we<01:07:17.760> have<01:07:18.000> entry<01:07:18.400> points.<01:07:19.680> After 01:07:19.990 --> 01:07:20.000 align:start position:0% frameworks, we have entry points. After 01:07:20.000 --> 01:07:21.910 align:start position:0% frameworks, we have entry points. After entry<01:07:20.400> points,<01:07:20.720> we<01:07:20.960> have<01:07:21.200> configuration 01:07:21.910 --> 01:07:21.920 align:start position:0% entry points, we have configuration 01:07:21.920 --> 01:07:25.029 align:start position:0% entry points, we have configuration files.<01:07:23.359> Then<01:07:23.599> we<01:07:23.760> have<01:07:24.000> deployment<01:07:24.640> related 01:07:25.029 --> 01:07:25.039 align:start position:0% files. Then we have deployment related 01:07:25.039 --> 01:07:26.549 align:start position:0% files. Then we have deployment related files. 01:07:26.549 --> 01:07:26.559 align:start position:0% files. 01:07:26.559 --> 01:07:29.430 align:start position:0% files. Then<01:07:26.799> we<01:07:27.039> have<01:07:27.280> testing<01:07:27.760> structure. 01:07:29.430 --> 01:07:29.440 align:start position:0% Then we have testing structure. 01:07:29.440 --> 01:07:31.670 align:start position:0% Then we have testing structure. Then<01:07:29.680> it<01:07:29.920> says<01:07:30.319> present<01:07:30.720> the<01:07:30.960> information<01:07:31.440> in 01:07:31.670 --> 01:07:31.680 align:start position:0% Then it says present the information in 01:07:31.680 --> 01:07:33.589 align:start position:0% Then it says present the information in a<01:07:31.920> structured<01:07:32.319> format<01:07:32.960> suitable<01:07:33.440> for 01:07:33.589 --> 01:07:33.599 align:start position:0% a structured format suitable for 01:07:33.599 --> 01:07:36.630 align:start position:0% a structured format suitable for onboarding<01:07:34.240> a<01:07:34.480> new<01:07:34.720> developer.<01:07:36.000> We<01:07:36.319> can<01:07:36.400> take 01:07:36.630 --> 01:07:36.640 align:start position:0% onboarding a new developer. We can take 01:07:36.640 --> 01:07:38.150 align:start position:0% onboarding a new developer. We can take our<01:07:36.799> things<01:07:37.119> directly<01:07:37.520> in<01:07:37.760> developer 01:07:38.150 --> 01:07:38.160 align:start position:0% our things directly in developer 01:07:38.160 --> 01:07:41.670 align:start position:0% our things directly in developer onboarding<01:07:38.799> too.<01:07:39.680> We<01:07:39.920> can<01:07:40.079> involve<01:07:40.480> them. 01:07:41.670 --> 01:07:41.680 align:start position:0% onboarding too. We can involve them. 01:07:41.680 --> 01:07:43.750 align:start position:0% onboarding too. We can involve them. This<01:07:41.920> is<01:07:42.000> a<01:07:42.240> complete<01:07:42.640> structured<01:07:43.119> repository 01:07:43.750 --> 01:07:43.760 align:start position:0% This is a complete structured repository 01:07:43.760 --> 01:07:46.069 align:start position:0% This is a complete structured repository layout<01:07:44.000> that<01:07:44.160> we<01:07:44.319> use<01:07:44.559> here. 01:07:46.069 --> 01:07:46.079 align:start position:0% layout that we use here. 01:07:46.079 --> 01:07:47.990 align:start position:0% layout that we use here. Sometimes<01:07:46.559> we<01:07:46.799> must<01:07:47.039> see<01:07:47.200> some<01:07:47.440> changes<01:07:47.760> in 01:07:47.990 --> 01:07:48.000 align:start position:0% Sometimes we must see some changes in 01:07:48.000 --> 01:07:51.029 align:start position:0% Sometimes we must see some changes in this<01:07:48.240> too.<01:07:49.440> In<01:07:49.760> this<01:07:50.000> we<01:07:50.240> also<01:07:50.559> involve 01:07:51.029 --> 01:07:51.039 align:start position:0% this too. In this we also involve 01:07:51.039 --> 01:07:52.870 align:start position:0% this too. In this we also involve multiple<01:07:51.520> repositories<01:07:52.160> and<01:07:52.480> options 01:07:52.870 --> 01:07:52.880 align:start position:0% multiple repositories and options 01:07:52.880 --> 01:07:54.470 align:start position:0% multiple repositories and options directly. 01:07:54.470 --> 01:07:54.480 align:start position:0% directly. 01:07:54.480 --> 01:07:56.710 align:start position:0% directly. When<01:07:54.720> I<01:07:54.880> enter<01:07:55.200> this<01:07:55.520> it<01:07:55.680> will<01:07:55.920> directly<01:07:56.319> go<01:07:56.480> to 01:07:56.710 --> 01:07:56.720 align:start position:0% When I enter this it will directly go to 01:07:56.720 --> 01:08:00.549 align:start position:0% When I enter this it will directly go to our<01:07:56.880> folder.<01:07:58.079> The<01:07:58.319> index<01:07:58.720> file<01:07:59.039> is<01:07:59.200> inside. 01:08:00.549 --> 01:08:00.559 align:start position:0% our folder. The index file is inside. 01:08:00.559 --> 01:08:03.510 align:start position:0% our folder. The index file is inside. You<01:08:00.799> can<01:08:00.880> see<01:08:01.119> this<01:08:01.280> is<01:08:01.440> like<01:08:01.599> our<01:08:01.839> index<01:08:02.240> file. 01:08:03.510 --> 01:08:03.520 align:start position:0% You can see this is like our index file. 01:08:03.520 --> 01:08:05.910 align:start position:0% You can see this is like our index file. When<01:08:03.760> the<01:08:03.920> index<01:08:04.319> file<01:08:04.640> opens,<01:08:05.280> a<01:08:05.520> complete 01:08:05.910 --> 01:08:05.920 align:start position:0% When the index file opens, a complete 01:08:05.920 --> 01:08:08.789 align:start position:0% When the index file opens, a complete portfolio<01:08:06.559> website<01:08:06.960> is<01:08:07.200> available. 01:08:08.789 --> 01:08:08.799 align:start position:0% portfolio website is available. 01:08:08.799 --> 01:08:10.789 align:start position:0% portfolio website is available. Now<01:08:09.039> we<01:08:09.280> will<01:08:09.440> see<01:08:09.680> how<01:08:09.920> to<01:08:10.079> enhance<01:08:10.480> and 01:08:10.789 --> 01:08:10.799 align:start position:0% Now we will see how to enhance and 01:08:10.799 --> 01:08:12.950 align:start position:0% Now we will see how to enhance and understand<01:08:11.280> this<01:08:11.520> portfolio<01:08:12.240> website<01:08:12.640> on<01:08:12.799> a 01:08:12.950 --> 01:08:12.960 align:start position:0% understand this portfolio website on a 01:08:12.960 --> 01:08:15.589 align:start position:0% understand this portfolio website on a big<01:08:13.200> scale.<01:08:14.480> This<01:08:14.720> will<01:08:14.880> happen<01:08:15.119> in<01:08:15.359> our 01:08:15.589 --> 01:08:15.599 align:start position:0% big scale. This will happen in our 01:08:15.599 --> 01:08:18.470 align:start position:0% big scale. This will happen in our codeex<01:08:16.159> here.<01:08:17.279> It<01:08:17.520> understood<01:08:18.000> the<01:08:18.159> child 01:08:18.470 --> 01:08:18.480 align:start position:0% codeex here. It understood the child 01:08:18.480 --> 01:08:21.749 align:start position:0% codeex here. It understood the child item<01:08:18.960> here.<01:08:20.319> After<01:08:20.640> that<01:08:20.960> it<01:08:21.199> showed<01:08:21.520> our 01:08:21.749 --> 01:08:21.759 align:start position:0% item here. After that it showed our 01:08:21.759 --> 01:08:25.749 align:start position:0% item here. After that it showed our files.<01:08:22.880> It<01:08:23.120> has<01:08:23.279> shown<01:08:23.520> the<01:08:23.679> key<01:08:23.920> pattern<01:08:24.400> too. 01:08:25.749 --> 01:08:25.759 align:start position:0% files. It has shown the key pattern too. 01:08:25.759 --> 01:08:29.189 align:start position:0% files. It has shown the key pattern too. We<01:08:26.000> have<01:08:26.159> one<01:08:26.640> HTML<01:08:27.440> document.<01:08:28.480> We<01:08:28.719> have<01:08:28.880> one 01:08:29.189 --> 01:08:29.199 align:start position:0% We have one HTML document. We have one 01:08:29.199 --> 01:08:33.189 align:start position:0% We have one HTML document. We have one stylesheet.<01:08:30.640> We<01:08:30.960> have<01:08:31.120> one<01:08:31.359> script<01:08:31.759> bundle. 01:08:33.189 --> 01:08:33.199 align:start position:0% stylesheet. We have one script bundle. 01:08:33.199 --> 01:08:36.070 align:start position:0% stylesheet. We have one script bundle. Then<01:08:33.440> we<01:08:33.679> have<01:08:33.839> some<01:08:34.080> static<01:08:34.560> assets. 01:08:36.070 --> 01:08:36.080 align:start position:0% Then we have some static assets. 01:08:36.080 --> 01:08:38.229 align:start position:0% Then we have some static assets. We<01:08:36.319> also<01:08:36.719> have<01:08:36.960> all<01:08:37.199> other<01:08:37.520> things<01:08:37.839> available 01:08:38.229 --> 01:08:38.239 align:start position:0% We also have all other things available 01:08:38.239 --> 01:08:40.630 align:start position:0% We also have all other things available to<01:08:38.480> use<01:08:38.719> directly. 01:08:40.630 --> 01:08:40.640 align:start position:0% to use directly. 01:08:40.640 --> 01:08:43.590 align:start position:0% to use directly. Now<01:08:40.880> I<01:08:41.120> will<01:08:41.279> take<01:08:41.520> our<01:08:41.759> details.<01:08:43.040> I<01:08:43.279> will<01:08:43.520> see 01:08:43.590 --> 01:08:43.600 align:start position:0% Now I will take our details. I will see 01:08:43.600 --> 01:08:46.789 align:start position:0% Now I will take our details. I will see how<01:08:43.839> our<01:08:44.080> process<01:08:44.480> runs.<01:08:45.679> I<01:08:45.920> will<01:08:46.080> see<01:08:46.239> how<01:08:46.560> all 01:08:46.789 --> 01:08:46.799 align:start position:0% how our process runs. I will see how all 01:08:46.799 --> 01:08:50.149 align:start position:0% how our process runs. I will see how all direct<01:08:47.199> discussions<01:08:47.759> and<01:08:48.000> details<01:08:48.480> run.<01:08:49.920> With 01:08:50.149 --> 01:08:50.159 align:start position:0% direct discussions and details run. With 01:08:50.159 --> 01:08:53.269 align:start position:0% direct discussions and details run. With this<01:08:50.560> we<01:08:50.799> will<01:08:50.960> take<01:08:51.120> our<01:08:51.359> setup.<01:08:52.799> Usually 01:08:53.269 --> 01:08:53.279 align:start position:0% this we will take our setup. Usually 01:08:53.279 --> 01:08:55.030 align:start position:0% this we will take our setup. Usually this<01:08:53.520> needs<01:08:53.839> a<01:08:54.000> lot<01:08:54.159> of<01:08:54.319> time<01:08:54.480> if<01:08:54.719> we<01:08:54.880> take 01:08:55.030 --> 01:08:55.040 align:start position:0% this needs a lot of time if we take 01:08:55.040 --> 01:08:57.510 align:start position:0% this needs a lot of time if we take these<01:08:55.279> things<01:08:55.520> in<01:08:55.679> another<01:08:56.000> environment.<01:08:57.359> But 01:08:57.510 --> 01:08:57.520 align:start position:0% these things in another environment. But 01:08:57.520 --> 01:09:00.550 align:start position:0% these things in another environment. But here<01:08:57.839> our<01:08:58.159> things<01:08:58.400> are<01:08:58.560> much<01:08:58.799> simpler<01:08:59.199> now. 01:09:00.550 --> 01:09:00.560 align:start position:0% here our things are much simpler now. 01:09:00.560 --> 01:09:02.470 align:start position:0% here our things are much simpler now. We<01:09:00.799> can<01:09:00.960> include<01:09:01.359> much<01:09:01.679> better<01:09:02.000> things<01:09:02.319> and 01:09:02.470 --> 01:09:02.480 align:start position:0% We can include much better things and 01:09:02.480 --> 01:09:05.269 align:start position:0% We can include much better things and accounts<01:09:02.880> here.<01:09:04.080> I<01:09:04.319> will<01:09:04.400> look<01:09:04.560> at<01:09:04.719> our<01:09:04.960> direct 01:09:05.269 --> 01:09:05.279 align:start position:0% accounts here. I will look at our direct 01:09:05.279 --> 01:09:08.390 align:start position:0% accounts here. I will look at our direct use<01:09:05.520> case<01:09:05.920> now.<01:09:07.199> It<01:09:07.440> read<01:09:07.679> out<01:09:07.839> our<01:09:08.159> whole 01:09:08.390 --> 01:09:08.400 align:start position:0% use case now. It read out our whole 01:09:08.400 --> 01:09:11.349 align:start position:0% use case now. It read out our whole folder<01:09:08.799> here.<01:09:09.920> After<01:09:10.239> that<01:09:10.560> it<01:09:10.799> told<01:09:11.040> us<01:09:11.199> there 01:09:11.349 --> 01:09:11.359 align:start position:0% folder here. After that it told us there 01:09:11.359 --> 01:09:13.269 align:start position:0% folder here. After that it told us there are<01:09:11.520> no<01:09:11.839> platform<01:09:12.400> specific<01:09:12.799> deployment 01:09:13.269 --> 01:09:13.279 align:start position:0% are no platform specific deployment 01:09:13.279 --> 01:09:16.149 align:start position:0% are no platform specific deployment manifests<01:09:14.000> checked<01:09:14.319> into<01:09:14.560> the<01:09:14.799> repository. 01:09:16.149 --> 01:09:16.159 align:start position:0% manifests checked into the repository. 01:09:16.159 --> 01:09:18.070 align:start position:0% manifests checked into the repository. The<01:09:16.400> deployment<01:09:16.880> guidance<01:09:17.279> is<01:09:17.520> document 01:09:18.070 --> 01:09:18.080 align:start position:0% The deployment guidance is document 01:09:18.080 --> 01:09:19.590 align:start position:0% The deployment guidance is document only. 01:09:19.590 --> 01:09:19.600 align:start position:0% only. 01:09:19.600 --> 01:09:22.229 align:start position:0% only. After<01:09:19.920> that<01:09:20.159> we<01:09:20.319> have<01:09:20.400> a<01:09:20.640> testing<01:09:21.040> structure. 01:09:22.229 --> 01:09:22.239 align:start position:0% After that we have a testing structure. 01:09:22.239 --> 01:09:25.110 align:start position:0% After that we have a testing structure. Then<01:09:22.560> all<01:09:22.880> other<01:09:23.120> things<01:09:23.359> have<01:09:23.600> come. 01:09:25.110 --> 01:09:25.120 align:start position:0% Then all other things have come. 01:09:25.120 --> 01:09:27.749 align:start position:0% Then all other things have come. Now<01:09:25.279> we<01:09:25.520> have<01:09:25.679> gone<01:09:25.839> inside<01:09:26.159> our<01:09:26.480> project.<01:09:27.520> We 01:09:27.749 --> 01:09:27.759 align:start position:0% Now we have gone inside our project. We 01:09:27.759 --> 01:09:29.269 align:start position:0% Now we have gone inside our project. We have<01:09:27.920> seen<01:09:28.159> how<01:09:28.319> we<01:09:28.480> will<01:09:28.640> include<01:09:28.960> our 01:09:29.269 --> 01:09:29.279 align:start position:0% have seen how we will include our 01:09:29.279 --> 01:09:32.229 align:start position:0% have seen how we will include our system.<01:09:30.560> Now<01:09:30.799> I<01:09:31.040> will<01:09:31.199> see<01:09:31.359> what<01:09:31.600> entry<01:09:32.000> points 01:09:32.229 --> 01:09:32.239 align:start position:0% system. Now I will see what entry points 01:09:32.239 --> 01:09:34.789 align:start position:0% system. Now I will see what entry points are<01:09:32.480> available<01:09:32.880> there.<01:09:33.920> I<01:09:34.159> will<01:09:34.319> write<01:09:34.640> to 01:09:34.789 --> 01:09:34.799 align:start position:0% are available there. I will write to 01:09:34.799 --> 01:09:37.590 align:start position:0% are available there. I will write to find<01:09:34.960> the<01:09:35.120> entry<01:09:35.440> points.<01:09:36.880> If<01:09:37.120> we<01:09:37.279> want<01:09:37.440> to 01:09:37.590 --> 01:09:37.600 align:start position:0% find the entry points. If we want to 01:09:37.600 --> 01:09:39.030 align:start position:0% find the entry points. If we want to look<01:09:37.679> at<01:09:37.920> something<01:09:38.159> other<01:09:38.480> than<01:09:38.640> entry 01:09:39.030 --> 01:09:39.040 align:start position:0% look at something other than entry 01:09:39.040 --> 01:09:41.349 align:start position:0% look at something other than entry points,<01:09:39.759> we<01:09:40.000> will<01:09:40.159> involve<01:09:40.640> all<01:09:40.960> user 01:09:41.349 --> 01:09:41.359 align:start position:0% points, we will involve all user 01:09:41.359 --> 01:09:43.990 align:start position:0% points, we will involve all user authentication<01:09:42.080> features.<01:09:42.560> Here<01:09:43.600> we<01:09:43.839> will 01:09:43.990 --> 01:09:44.000 align:start position:0% authentication features. Here we will 01:09:44.000 --> 01:09:46.550 align:start position:0% authentication features. Here we will see<01:09:44.159> how<01:09:44.319> we<01:09:44.560> can<01:09:44.640> look<01:09:44.799> at<01:09:44.960> them.<01:09:46.000> Along<01:09:46.319> with 01:09:46.550 --> 01:09:46.560 align:start position:0% see how we can look at them. Along with 01:09:46.560 --> 01:09:48.789 align:start position:0% see how we can look at them. Along with this,<01:09:47.120> we<01:09:47.359> will<01:09:47.520> get<01:09:47.679> a<01:09:47.839> direct<01:09:48.159> response<01:09:48.560> from 01:09:48.789 --> 01:09:48.799 align:start position:0% this, we will get a direct response from 01:09:48.799 --> 01:09:51.749 align:start position:0% this, we will get a direct response from the<01:09:48.960> complete<01:09:49.359> system.<01:09:50.799> We<01:09:51.040> will<01:09:51.199> see<01:09:51.359> how<01:09:51.520> we 01:09:51.749 --> 01:09:51.759 align:start position:0% the complete system. We will see how we 01:09:51.759 --> 01:09:53.590 align:start position:0% the complete system. We will see how we take<01:09:52.000> things<01:09:52.239> directly<01:09:52.719> in<01:09:52.960> our<01:09:53.199> system. 01:09:53.590 --> 01:09:53.600 align:start position:0% take things directly in our system. 01:09:53.600 --> 01:09:56.709 align:start position:0% take things directly in our system. First<01:09:54.880> I<01:09:55.120> will<01:09:55.280> type<01:09:55.520> to<01:09:55.760> locate<01:09:56.080> and<01:09:56.400> explain 01:09:56.709 --> 01:09:56.719 align:start position:0% First I will type to locate and explain 01:09:56.719 --> 01:09:58.310 align:start position:0% First I will type to locate and explain the<01:09:56.960> implementation<01:09:57.600> of<01:09:57.760> the<01:09:58.000> user 01:09:58.310 --> 01:09:58.320 align:start position:0% the implementation of the user 01:09:58.320 --> 01:10:01.430 align:start position:0% the implementation of the user authentication<01:09:59.040> feature.<01:10:00.400> I<01:10:00.640> will<01:10:00.960> identify 01:10:01.430 --> 01:10:01.440 align:start position:0% authentication feature. I will identify 01:10:01.440 --> 01:10:04.470 align:start position:0% authentication feature. I will identify all<01:10:01.679> the<01:10:01.920> components<01:10:02.400> involved<01:10:02.800> here.<01:10:04.000> Then<01:10:04.239> I 01:10:04.470 --> 01:10:04.480 align:start position:0% all the components involved here. Then I 01:10:04.480 --> 01:10:07.189 align:start position:0% all the components involved here. Then I will<01:10:04.640> look<01:10:04.719> at<01:10:04.880> the<01:10:05.040> authentication<01:10:05.760> flow. 01:10:07.189 --> 01:10:07.199 align:start position:0% will look at the authentication flow. 01:10:07.199 --> 01:10:09.030 align:start position:0% will look at the authentication flow. Then<01:10:07.440> I<01:10:07.679> will<01:10:07.840> look<01:10:08.000> at<01:10:08.080> the<01:10:08.320> authentication 01:10:09.030 --> 01:10:09.040 align:start position:0% Then I will look at the authentication 01:10:09.040 --> 01:10:10.550 align:start position:0% Then I will look at the authentication middleware. 01:10:10.550 --> 01:10:10.560 align:start position:0% middleware. 01:10:10.560 --> 01:10:13.430 align:start position:0% middleware. Then<01:10:10.800> I<01:10:11.040> will<01:10:11.199> look<01:10:11.360> at<01:10:11.520> password<01:10:12.000> handling. 01:10:13.430 --> 01:10:13.440 align:start position:0% Then I will look at password handling. 01:10:13.440 --> 01:10:15.430 align:start position:0% Then I will look at password handling. Then<01:10:13.760> I<01:10:14.000> will<01:10:14.080> look<01:10:14.239> at<01:10:14.320> the<01:10:14.480> token<01:10:14.880> generation 01:10:15.430 --> 01:10:15.440 align:start position:0% Then I will look at the token generation 01:10:15.440 --> 01:10:17.110 align:start position:0% Then I will look at the token generation process. 01:10:17.110 --> 01:10:17.120 align:start position:0% process. 01:10:17.120 --> 01:10:19.189 align:start position:0% process. Then<01:10:17.440> I<01:10:17.679> will<01:10:17.760> look<01:10:17.920> at<01:10:18.000> the<01:10:18.239> session<01:10:18.560> or<01:10:18.800> token 01:10:19.189 --> 01:10:19.199 align:start position:0% Then I will look at the session or token 01:10:19.199 --> 01:10:20.709 align:start position:0% Then I will look at the session or token management. 01:10:20.709 --> 01:10:20.719 align:start position:0% management. 01:10:20.719 --> 01:10:22.709 align:start position:0% management. Then<01:10:21.040> I<01:10:21.280> will<01:10:21.440> provide<01:10:21.679> a<01:10:21.920> step-by-step 01:10:22.709 --> 01:10:22.719 align:start position:0% Then I will provide a step-by-step 01:10:22.719 --> 01:10:25.030 align:start position:0% Then I will provide a step-by-step explanation<01:10:23.760> of<01:10:24.000> how<01:10:24.159> the<01:10:24.400> application 01:10:25.030 --> 01:10:25.040 align:start position:0% explanation of how the application 01:10:25.040 --> 01:10:26.630 align:start position:0% explanation of how the application starts. 01:10:26.630 --> 01:10:26.640 align:start position:0% starts. 01:10:26.640 --> 01:10:28.630 align:start position:0% starts. Then<01:10:26.960> I<01:10:27.199> will<01:10:27.360> process<01:10:27.760> the<01:10:27.920> requests<01:10:28.400> from 01:10:28.630 --> 01:10:28.640 align:start position:0% Then I will process the requests from 01:10:28.640 --> 01:10:31.830 align:start position:0% Then I will process the requests from login<01:10:29.199> to<01:10:29.520> successful<01:10:30.080> authentication. 01:10:31.830 --> 01:10:31.840 align:start position:0% login to successful authentication. 01:10:31.840 --> 01:10:34.790 align:start position:0% login to successful authentication. These<01:10:32.159> things<01:10:32.480> bring<01:10:32.800> all<01:10:32.960> our<01:10:33.280> details<01:10:33.679> here. 01:10:34.790 --> 01:10:34.800 align:start position:0% These things bring all our details here. 01:10:34.800 --> 01:10:37.669 align:start position:0% These things bring all our details here. All<01:10:35.040> our<01:10:35.360> handling<01:10:35.760> has<01:10:35.920> come<01:10:36.159> here.<01:10:36.400> Now 01:10:37.669 --> 01:10:37.679 align:start position:0% All our handling has come here. Now 01:10:37.679 --> 01:10:39.750 align:start position:0% All our handling has come here. Now generating<01:10:38.320> code<01:10:38.560> from<01:10:38.880> requirements<01:10:39.360> is<01:10:39.600> one 01:10:39.750 --> 01:10:39.760 align:start position:0% generating code from requirements is one 01:10:39.760 --> 01:10:41.830 align:start position:0% generating code from requirements is one of<01:10:39.840> the<01:10:40.000> most<01:10:40.159> practical<01:10:40.640> uses<01:10:40.960> of<01:10:41.199> OpenAI 01:10:41.830 --> 01:10:41.840 align:start position:0% of the most practical uses of OpenAI 01:10:41.840 --> 01:10:44.630 align:start position:0% of the most practical uses of OpenAI codeex<01:10:42.320> in<01:10:42.480> everyday<01:10:42.960> development.<01:10:44.320> Instead 01:10:44.630 --> 01:10:44.640 align:start position:0% codeex in everyday development. Instead 01:10:44.640 --> 01:10:46.790 align:start position:0% codeex in everyday development. Instead of<01:10:44.880> translating<01:10:45.600> every<01:10:46.000> single<01:10:46.400> business 01:10:46.790 --> 01:10:46.800 align:start position:0% of translating every single business 01:10:46.800 --> 01:10:49.750 align:start position:0% of translating every single business requirement<01:10:47.520> into<01:10:47.920> working<01:10:48.320> code<01:10:48.640> by<01:10:48.880> hand, 01:10:49.750 --> 01:10:49.760 align:start position:0% requirement into working code by hand, 01:10:49.760 --> 01:10:51.590 align:start position:0% requirement into working code by hand, developers<01:10:50.320> can<01:10:50.480> provide<01:10:50.800> codecs<01:10:51.280> with<01:10:51.440> a 01:10:51.590 --> 01:10:51.600 align:start position:0% developers can provide codecs with a 01:10:51.600 --> 01:10:54.790 align:start position:0% developers can provide codecs with a vast<01:10:51.920> amount<01:10:52.159> of<01:10:52.400> information<01:10:52.880> or<01:10:53.199> context. 01:10:54.790 --> 01:10:54.800 align:start position:0% vast amount of information or context. 01:10:54.800 --> 01:10:57.110 align:start position:0% vast amount of information or context. We<01:10:55.040> can<01:10:55.199> include<01:10:55.760> clear<01:10:56.080> instructions, 01:10:57.110 --> 01:10:57.120 align:start position:0% We can include clear instructions, 01:10:57.120 --> 01:10:59.510 align:start position:0% We can include clear instructions, behaviors,<01:10:57.760> and<01:10:58.000> context. 01:10:59.510 --> 01:10:59.520 align:start position:0% behaviors, and context. 01:10:59.520 --> 01:11:01.189 align:start position:0% behaviors, and context. We<01:10:59.679> have<01:10:59.840> multiple<01:11:00.239> forms<01:11:00.560> of<01:11:00.719> languages 01:11:01.189 --> 01:11:01.199 align:start position:0% We have multiple forms of languages 01:11:01.199 --> 01:11:04.550 align:start position:0% We have multiple forms of languages available<01:11:01.520> to<01:11:01.840> use.<01:11:03.040> Let<01:11:03.280> me<01:11:03.440> open<01:11:03.760> Excaladraw 01:11:04.550 --> 01:11:04.560 align:start position:0% available to use. Let me open Excaladraw 01:11:04.560 --> 01:11:07.430 align:start position:0% available to use. Let me open Excaladraw here.<01:11:05.840> As<01:11:06.080> you<01:11:06.239> can<01:11:06.400> see,<01:11:06.800> we<01:11:07.120> have<01:11:07.199> some 01:11:07.430 --> 01:11:07.440 align:start position:0% here. As you can see, we have some 01:11:07.440 --> 01:11:10.470 align:start position:0% here. As you can see, we have some business<01:11:07.760> languages.<01:11:09.040> For<01:11:09.199> example,<01:11:10.080> we<01:11:10.320> can 01:11:10.470 --> 01:11:10.480 align:start position:0% business languages. For example, we can 01:11:10.480 --> 01:11:13.830 align:start position:0% business languages. For example, we can allow<01:11:10.800> users<01:11:11.199> to<01:11:11.360> export<01:11:11.840> reports<01:11:12.239> as<01:11:12.480> CSV<01:11:13.520> or 01:11:13.830 --> 01:11:13.840 align:start position:0% allow users to export reports as CSV or 01:11:13.840 --> 01:11:16.790 align:start position:0% allow users to export reports as CSV or involve<01:11:14.400> RO<01:11:14.800> based<01:11:15.120> access<01:11:15.600> control,<01:11:16.480> also 01:11:16.790 --> 01:11:16.800 align:start position:0% involve RO based access control, also 01:11:16.800 --> 01:11:19.510 align:start position:0% involve RO based access control, also known<01:11:17.120> as<01:11:17.440> RBAC. 01:11:19.510 --> 01:11:19.520 align:start position:0% known as RBAC. 01:11:19.520 --> 01:11:21.270 align:start position:0% known as RBAC. Codeex<01:11:20.080> helps<01:11:20.400> bridge<01:11:20.640> the<01:11:20.800> gap<01:11:21.040> between 01:11:21.270 --> 01:11:21.280 align:start position:0% Codeex helps bridge the gap between 01:11:21.280 --> 01:11:23.510 align:start position:0% Codeex helps bridge the gap between these<01:11:21.600> requirements<01:11:22.159> and<01:11:22.400> implementations 01:11:23.510 --> 01:11:23.520 align:start position:0% these requirements and implementations 01:11:23.520 --> 01:11:25.750 align:start position:0% these requirements and implementations by<01:11:24.000> identifying<01:11:24.480> relevant<01:11:24.880> files, 01:11:25.750 --> 01:11:25.760 align:start position:0% by identifying relevant files, 01:11:25.760 --> 01:11:28.149 align:start position:0% by identifying relevant files, suggesting<01:11:26.320> changes,<01:11:27.440> creating<01:11:27.840> new 01:11:28.149 --> 01:11:28.159 align:start position:0% suggesting changes, creating new 01:11:28.159 --> 01:11:31.510 align:start position:0% suggesting changes, creating new components,<01:11:29.360> updating<01:11:29.920> APIs,<01:11:30.960> and<01:11:31.199> adding 01:11:31.510 --> 01:11:31.520 align:start position:0% components, updating APIs, and adding 01:11:31.520 --> 01:11:34.870 align:start position:0% components, updating APIs, and adding tests<01:11:31.840> where<01:11:32.080> needed.<01:11:33.360> However,<01:11:34.320> codeex 01:11:34.870 --> 01:11:34.880 align:start position:0% tests where needed. However, codeex 01:11:34.880 --> 01:11:36.630 align:start position:0% tests where needed. However, codeex works<01:11:35.199> best<01:11:35.440> when<01:11:35.760> the<01:11:35.920> requirements<01:11:36.400> are 01:11:36.630 --> 01:11:36.640 align:start position:0% works best when the requirements are 01:11:36.640 --> 01:11:39.350 align:start position:0% works best when the requirements are very<01:11:37.040> specific<01:11:37.520> in<01:11:37.760> nature. 01:11:39.350 --> 01:11:39.360 align:start position:0% very specific in nature. 01:11:39.360 --> 01:11:41.430 align:start position:0% very specific in nature. Let<01:11:39.600> me<01:11:39.760> show<01:11:39.920> you<01:11:40.080> how<01:11:40.239> to<01:11:40.400> include<01:11:40.800> basics<01:11:41.199> in 01:11:41.430 --> 01:11:41.440 align:start position:0% Let me show you how to include basics in 01:11:41.440 --> 01:11:44.390 align:start position:0% Let me show you how to include basics in codeex<01:11:42.000> right<01:11:42.239> from<01:11:42.400> the<01:11:42.640> start.<01:11:43.840> Suppose<01:11:44.239> you 01:11:44.390 --> 01:11:44.400 align:start position:0% codeex right from the start. Suppose you 01:11:44.400 --> 01:11:47.110 align:start position:0% codeex right from the start. Suppose you want<01:11:44.560> a<01:11:44.719> plan<01:11:45.040> mode<01:11:45.679> and<01:11:46.000> after<01:11:46.239> that<01:11:46.719> you<01:11:46.960> want 01:11:47.110 --> 01:11:47.120 align:start position:0% want a plan mode and after that you want 01:11:47.120 --> 01:11:50.070 align:start position:0% want a plan mode and after that you want to<01:11:47.280> pursue<01:11:47.600> a<01:11:47.760> goal.<01:11:48.880> Then<01:11:49.280> you<01:11:49.520> might<01:11:49.760> want<01:11:49.920> to 01:11:50.070 --> 01:11:50.080 align:start position:0% to pursue a goal. Then you might want to 01:11:50.080 --> 01:11:52.790 align:start position:0% to pursue a goal. Then you might want to create<01:11:50.320> a<01:11:50.560> document.<01:11:51.920> After<01:11:52.320> document 01:11:52.790 --> 01:11:52.800 align:start position:0% create a document. After document 01:11:52.800 --> 01:11:54.790 align:start position:0% create a document. After document creation,<01:11:53.600> you<01:11:53.840> might<01:11:54.080> want<01:11:54.239> to<01:11:54.400> include 01:11:54.790 --> 01:11:54.800 align:start position:0% creation, you might want to include 01:11:54.800 --> 01:11:57.669 align:start position:0% creation, you might want to include photos.<01:11:56.239> You<01:11:56.480> have<01:11:56.640> multiple<01:11:57.120> plugins<01:11:57.520> that 01:11:57.669 --> 01:11:57.679 align:start position:0% photos. You have multiple plugins that 01:11:57.679 --> 01:12:00.550 align:start position:0% photos. You have multiple plugins that you<01:11:57.840> can<01:11:58.000> use<01:11:58.239> side<01:11:58.480> by<01:11:58.719> side.<01:12:00.000> Even<01:12:00.239> if<01:12:00.400> you 01:12:00.550 --> 01:12:00.560 align:start position:0% you can use side by side. Even if you 01:12:00.560 --> 01:12:02.470 align:start position:0% you can use side by side. Even if you need<01:12:00.640> a<01:12:00.880> browser<01:12:01.199> plugin,<01:12:01.760> you<01:12:01.920> can<01:12:02.080> use<01:12:02.239> that 01:12:02.470 --> 01:12:02.480 align:start position:0% need a browser plugin, you can use that 01:12:02.480 --> 01:12:05.590 align:start position:0% need a browser plugin, you can use that one<01:12:02.719> too.<01:12:03.840> If<01:12:04.080> you<01:12:04.320> have<01:12:04.480> specific<01:12:05.040> content<01:12:05.360> to 01:12:05.590 --> 01:12:05.600 align:start position:0% one too. If you have specific content to 01:12:05.600 --> 01:12:08.550 align:start position:0% one too. If you have specific content to use,<01:12:06.159> that<01:12:06.400> can<01:12:06.560> be<01:12:06.719> utilized<01:12:07.199> as<01:12:07.360> well. 01:12:08.550 --> 01:12:08.560 align:start position:0% use, that can be utilized as well. 01:12:08.560 --> 01:12:11.270 align:start position:0% use, that can be utilized as well. For<01:12:08.800> instance,<01:12:09.679> we<01:12:09.920> can<01:12:10.080> go<01:12:10.239> to<01:12:10.400> documents<01:12:10.960> or 01:12:11.270 --> 01:12:11.280 align:start position:0% For instance, we can go to documents or 01:12:11.280 --> 01:12:13.830 align:start position:0% For instance, we can go to documents or downloads,<01:12:12.239> select<01:12:12.480> an<01:12:12.800> available<01:12:13.199> document 01:12:13.830 --> 01:12:13.840 align:start position:0% downloads, select an available document 01:12:13.840 --> 01:12:16.870 align:start position:0% downloads, select an available document and<01:12:14.080> use<01:12:14.320> it.<01:12:15.440> After<01:12:15.760> that,<01:12:16.080> we<01:12:16.320> select<01:12:16.640> our 01:12:16.870 --> 01:12:16.880 align:start position:0% and use it. After that, we select our 01:12:16.880 --> 01:12:20.950 align:start position:0% and use it. After that, we select our model.<01:12:18.320> This<01:12:18.560> latency<01:12:19.120> is<01:12:19.440> quite<01:12:19.760> important. 01:12:20.950 --> 01:12:20.960 align:start position:0% model. This latency is quite important. 01:12:20.960 --> 01:12:22.950 align:start position:0% model. This latency is quite important. Therefore,<01:12:21.440> I<01:12:21.679> will<01:12:21.840> use<01:12:22.000> a<01:12:22.239> latest<01:12:22.640> model 01:12:22.950 --> 01:12:22.960 align:start position:0% Therefore, I will use a latest model 01:12:22.960 --> 01:12:26.070 align:start position:0% Therefore, I will use a latest model here.<01:12:24.080> With<01:12:24.320> that<01:12:24.560> latest<01:12:24.960> model,<01:12:25.520> we<01:12:25.840> can 01:12:26.070 --> 01:12:26.080 align:start position:0% here. With that latest model, we can 01:12:26.080 --> 01:12:29.270 align:start position:0% here. With that latest model, we can increase<01:12:26.400> speed<01:12:26.719> and<01:12:26.960> manage<01:12:27.280> latency.<01:12:27.920> Well, 01:12:29.270 --> 01:12:29.280 align:start position:0% increase speed and manage latency. Well, 01:12:29.280 --> 01:12:31.590 align:start position:0% increase speed and manage latency. Well, after<01:12:29.679> this,<01:12:30.239> our<01:12:30.480> prompt<01:12:30.880> should<01:12:31.120> contain 01:12:31.590 --> 01:12:31.600 align:start position:0% after this, our prompt should contain 01:12:31.600 --> 01:12:34.790 align:start position:0% after this, our prompt should contain very<01:12:31.920> detailed<01:12:32.400> options.<01:12:33.760> First<01:12:34.000> of<01:12:34.159> all,<01:12:34.560> a 01:12:34.790 --> 01:12:34.800 align:start position:0% very detailed options. First of all, a 01:12:34.800 --> 01:12:36.550 align:start position:0% very detailed options. First of all, a well-<01:12:35.040> set<01:12:35.280> prompt<01:12:35.679> has<01:12:35.840> some<01:12:36.080> specific 01:12:36.550 --> 01:12:36.560 align:start position:0% well- set prompt has some specific 01:12:36.560 --> 01:12:39.189 align:start position:0% well- set prompt has some specific elements<01:12:36.960> available<01:12:37.440> within<01:12:37.760> it.<01:12:38.719> I<01:12:39.040> will 01:12:39.189 --> 01:12:39.199 align:start position:0% elements available within it. I will 01:12:39.199 --> 01:12:41.750 align:start position:0% elements available within it. I will explain<01:12:39.440> these<01:12:39.760> elements<01:12:40.080> to<01:12:40.320> you.<01:12:41.360> A<01:12:41.600> good 01:12:41.750 --> 01:12:41.760 align:start position:0% explain these elements to you. A good 01:12:41.760 --> 01:12:43.830 align:start position:0% explain these elements to you. A good prompt<01:12:42.239> includes<01:12:42.719> all<01:12:42.880> these<01:12:43.199> necessary 01:12:43.830 --> 01:12:43.840 align:start position:0% prompt includes all these necessary 01:12:43.840 --> 01:12:46.550 align:start position:0% prompt includes all these necessary components.<01:12:45.280> The<01:12:45.520> very<01:12:45.840> first<01:12:46.080> thing<01:12:46.239> is 01:12:46.550 --> 01:12:46.560 align:start position:0% components. The very first thing is 01:12:46.560 --> 01:12:50.070 align:start position:0% components. The very first thing is context<01:12:47.520> followed<01:12:47.840> by<01:12:48.000> the<01:12:48.239> role<01:12:49.120> details<01:12:49.920> and 01:12:50.070 --> 01:12:50.080 align:start position:0% context followed by the role details and 01:12:50.080 --> 01:12:52.390 align:start position:0% context followed by the role details and then<01:12:50.320> the<01:12:50.560> requirements. 01:12:52.390 --> 01:12:52.400 align:start position:0% then the requirements. 01:12:52.400 --> 01:12:54.790 align:start position:0% then the requirements. When<01:12:52.719> discussing<01:12:53.199> requirements,<01:12:54.239> it<01:12:54.400> is<01:12:54.560> a 01:12:54.790 --> 01:12:54.800 align:start position:0% When discussing requirements, it is a 01:12:54.800 --> 01:12:57.110 align:start position:0% When discussing requirements, it is a crucial<01:12:55.199> point<01:12:55.920> because<01:12:56.320> codeex<01:12:56.800> works 01:12:57.110 --> 01:12:57.120 align:start position:0% crucial point because codeex works 01:12:57.120 --> 01:12:58.390 align:start position:0% crucial point because codeex works better<01:12:57.280> when<01:12:57.520> the<01:12:57.760> requirements<01:12:58.159> are 01:12:58.390 --> 01:12:58.400 align:start position:0% better when the requirements are 01:12:58.400 --> 01:13:01.430 align:start position:0% better when the requirements are specific.<01:12:59.760> A<01:13:00.000> vague<01:13:00.400> prompt<01:13:00.800> may<01:13:01.040> produce 01:13:01.430 --> 01:13:01.440 align:start position:0% specific. A vague prompt may produce 01:13:01.440 --> 01:13:04.870 align:start position:0% specific. A vague prompt may produce incomplete<01:13:02.080> or<01:13:02.320> misaligned<01:13:03.040> code.<01:13:04.320> A<01:13:04.560> strong 01:13:04.870 --> 01:13:04.880 align:start position:0% incomplete or misaligned code. A strong 01:13:04.880 --> 01:13:06.950 align:start position:0% incomplete or misaligned code. A strong prompt<01:13:05.280> includes<01:13:05.679> the<01:13:05.920> feature<01:13:06.239> goal, 01:13:06.950 --> 01:13:06.960 align:start position:0% prompt includes the feature goal, 01:13:06.960 --> 01:13:09.510 align:start position:0% prompt includes the feature goal, affected<01:13:07.520> users,<01:13:08.400> input<01:13:08.880> and<01:13:09.120> output 01:13:09.510 --> 01:13:09.520 align:start position:0% affected users, input and output 01:13:09.520 --> 01:13:12.630 align:start position:0% affected users, input and output behavior,<01:13:10.560> files<01:13:10.960> or<01:13:11.199> modules<01:13:11.600> to<01:13:11.840> consider, 01:13:12.630 --> 01:13:12.640 align:start position:0% behavior, files or modules to consider, 01:13:12.640 --> 01:13:15.830 align:start position:0% behavior, files or modules to consider, coding<01:13:13.120> standards,<01:13:14.000> test<01:13:14.400> expectations,<01:13:15.600> and 01:13:15.830 --> 01:13:15.840 align:start position:0% coding standards, test expectations, and 01:13:15.840 --> 01:13:18.790 align:start position:0% coding standards, test expectations, and what<01:13:16.000> our<01:13:16.239> codec<01:13:16.719> should<01:13:16.880> avoid<01:13:17.280> changing. 01:13:18.790 --> 01:13:18.800 align:start position:0% what our codec should avoid changing. 01:13:18.800 --> 01:13:20.390 align:start position:0% what our codec should avoid changing. Developers<01:13:19.280> should<01:13:19.520> treat<01:13:19.679> the<01:13:19.920> codeex 01:13:20.390 --> 01:13:20.400 align:start position:0% Developers should treat the codeex 01:13:20.400 --> 01:13:22.870 align:start position:0% Developers should treat the codeex generated<01:13:20.960> code<01:13:21.199> as<01:13:21.360> a<01:13:21.600> first<01:13:21.840> draft<01:13:22.480> so<01:13:22.640> we 01:13:22.870 --> 01:13:22.880 align:start position:0% generated code as a first draft so we 01:13:22.880 --> 01:13:24.709 align:start position:0% generated code as a first draft so we get<01:13:22.960> a<01:13:23.199> complete<01:13:23.600> response<01:13:24.080> right<01:13:24.320> from<01:13:24.560> the 01:13:24.709 --> 01:13:24.719 align:start position:0% get a complete response right from the 01:13:24.719 --> 01:13:26.709 align:start position:0% get a complete response right from the very<01:13:24.960> start<01:13:25.120> of<01:13:25.360> it. 01:13:26.709 --> 01:13:26.719 align:start position:0% very start of it. 01:13:26.719 --> 01:13:29.189 align:start position:0% very start of it. Next,<01:13:27.280> after<01:13:27.520> the<01:13:27.760> requirements,<01:13:28.640> we<01:13:28.880> need<01:13:29.040> to 01:13:29.189 --> 01:13:29.199 align:start position:0% Next, after the requirements, we need to 01:13:29.199 --> 01:13:31.990 align:start position:0% Next, after the requirements, we need to establish<01:13:29.679> our<01:13:29.920> acceptance<01:13:30.480> criteria. 01:13:31.990 --> 01:13:32.000 align:start position:0% establish our acceptance criteria. 01:13:32.000 --> 01:13:33.830 align:start position:0% establish our acceptance criteria. This<01:13:32.239> defines<01:13:32.640> the<01:13:32.880> standard<01:13:33.199> our<01:13:33.520> response 01:13:33.830 --> 01:13:33.840 align:start position:0% This defines the standard our response 01:13:33.840 --> 01:13:36.870 align:start position:0% This defines the standard our response must<01:13:34.159> maintain<01:13:34.560> when<01:13:34.800> we<01:13:34.960> receive<01:13:35.280> it.<01:13:36.400> At<01:13:36.640> the 01:13:36.870 --> 01:13:36.880 align:start position:0% must maintain when we receive it. At the 01:13:36.880 --> 01:13:40.070 align:start position:0% must maintain when we receive it. At the end,<01:13:37.360> we<01:13:37.600> sometimes<01:13:38.080> use<01:13:38.320> a<01:13:38.560> negative<01:13:38.960> prompt. 01:13:40.070 --> 01:13:40.080 align:start position:0% end, we sometimes use a negative prompt. 01:13:40.080 --> 01:13:42.470 align:start position:0% end, we sometimes use a negative prompt. In<01:13:40.320> a<01:13:40.480> negative<01:13:40.880> prompt,<01:13:41.520> we<01:13:41.760> specify<01:13:42.239> the 01:13:42.470 --> 01:13:42.480 align:start position:0% In a negative prompt, we specify the 01:13:42.480 --> 01:13:45.110 align:start position:0% In a negative prompt, we specify the things<01:13:42.640> that<01:13:42.880> we<01:13:43.040> do<01:13:43.280> not<01:13:43.440> need.<01:13:44.640> In<01:13:44.800> the<01:13:44.960> rest 01:13:45.110 --> 01:13:45.120 align:start position:0% things that we do not need. In the rest 01:13:45.120 --> 01:13:47.430 align:start position:0% things that we do not need. In the rest of<01:13:45.280> the<01:13:45.440> prompt,<01:13:46.000> we<01:13:46.239> list<01:13:46.480> all<01:13:46.719> the<01:13:46.880> necessary 01:13:47.430 --> 01:13:47.440 align:start position:0% of the prompt, we list all the necessary 01:13:47.440 --> 01:13:50.310 align:start position:0% of the prompt, we list all the necessary things<01:13:47.679> that<01:13:47.920> we<01:13:48.080> want.<01:13:49.199> However,<01:13:50.000> in<01:13:50.159> a 01:13:50.310 --> 01:13:50.320 align:start position:0% things that we want. However, in a 01:13:50.320 --> 01:13:52.630 align:start position:0% things that we want. However, in a negative<01:13:50.800> prompt,<01:13:51.440> we<01:13:51.679> mention<01:13:52.080> all<01:13:52.400> those 01:13:52.630 --> 01:13:52.640 align:start position:0% negative prompt, we mention all those 01:13:52.640 --> 01:13:54.550 align:start position:0% negative prompt, we mention all those exact<01:13:53.120> things<01:13:53.360> that<01:13:53.600> are<01:13:53.760> not<01:13:54.000> required<01:13:54.400> for 01:13:54.550 --> 01:13:54.560 align:start position:0% exact things that are not required for 01:13:54.560 --> 01:13:57.910 align:start position:0% exact things that are not required for our<01:13:54.800> output<01:13:55.120> at<01:13:55.360> all.<01:13:56.480> For<01:13:56.640> example,<01:13:57.600> let<01:13:57.760> me 01:13:57.910 --> 01:13:57.920 align:start position:0% our output at all. For example, let me 01:13:57.920 --> 01:13:59.830 align:start position:0% our output at all. For example, let me show<01:13:58.080> you<01:13:58.239> a<01:13:58.480> sample<01:13:58.800> prompt<01:13:59.199> right<01:13:59.440> here<01:13:59.600> in 01:13:59.830 --> 01:13:59.840 align:start position:0% show you a sample prompt right here in 01:13:59.840 --> 01:14:02.709 align:start position:0% show you a sample prompt right here in this<01:14:00.000> section.<01:14:01.280> We<01:14:01.520> can<01:14:01.679> go<01:14:01.840> into<01:14:02.080> codeex<01:14:02.560> and 01:14:02.709 --> 01:14:02.719 align:start position:0% this section. We can go into codeex and 01:14:02.719 --> 01:14:05.270 align:start position:0% this section. We can go into codeex and type<01:14:02.960> out<01:14:03.199> our<01:14:03.360> prompt.<01:14:04.480> We<01:14:04.719> will<01:14:04.880> write<01:14:05.120> that 01:14:05.270 --> 01:14:05.280 align:start position:0% type out our prompt. We will write that 01:14:05.280 --> 01:14:07.270 align:start position:0% type out our prompt. We will write that you<01:14:05.520> are<01:14:05.679> working<01:14:05.840> in<01:14:06.080> this<01:14:06.320> repository<01:14:06.880> as<01:14:07.120> a 01:14:07.270 --> 01:14:07.280 align:start position:0% you are working in this repository as a 01:14:07.280 --> 01:14:09.590 align:start position:0% you are working in this repository as a senior<01:14:07.600> software<01:14:08.080> engineer<01:14:08.800> with<01:14:09.040> a<01:14:09.280> lot<01:14:09.360> of 01:14:09.590 --> 01:14:09.600 align:start position:0% senior software engineer with a lot of 01:14:09.600 --> 01:14:11.270 align:start position:0% senior software engineer with a lot of experience<01:14:10.080> and<01:14:10.400> solid<01:14:10.800> technical 01:14:11.270 --> 01:14:11.280 align:start position:0% experience and solid technical 01:14:11.280 --> 01:14:14.229 align:start position:0% experience and solid technical background<01:14:11.679> knowledge<01:14:12.080> today.<01:14:13.520> This<01:14:13.840> defines 01:14:14.229 --> 01:14:14.239 align:start position:0% background knowledge today. This defines 01:14:14.239 --> 01:14:16.950 align:start position:0% background knowledge today. This defines our<01:14:14.480> role.<01:14:15.360> The<01:14:15.600> complete<01:14:16.000> task<01:14:16.320> is<01:14:16.560> outlined 01:14:16.950 --> 01:14:16.960 align:start position:0% our role. The complete task is outlined 01:14:16.960 --> 01:14:20.229 align:start position:0% our role. The complete task is outlined in<01:14:17.199> plain<01:14:17.520> words.<01:14:18.719> After<01:14:19.040> the<01:14:19.199> task,<01:14:19.840> you<01:14:20.080> can 01:14:20.229 --> 01:14:20.239 align:start position:0% in plain words. After the task, you can 01:14:20.239 --> 01:14:21.750 align:start position:0% in plain words. After the task, you can see<01:14:20.400> our<01:14:20.640> functional<01:14:21.040> requirements<01:14:21.600> are 01:14:21.750 --> 01:14:21.760 align:start position:0% see our functional requirements are 01:14:21.760 --> 01:14:24.550 align:start position:0% see our functional requirements are discussed<01:14:22.560> such<01:14:22.800> as<01:14:22.960> adding<01:14:23.280> an<01:14:23.520> export<01:14:24.000> CSV 01:14:24.550 --> 01:14:24.560 align:start position:0% discussed such as adding an export CSV 01:14:24.560 --> 01:14:27.270 align:start position:0% discussed such as adding an export CSV button<01:14:24.880> near<01:14:25.040> the<01:14:25.280> reports<01:14:25.679> table.<01:14:26.800> Towards 01:14:27.270 --> 01:14:27.280 align:start position:0% button near the reports table. Towards 01:14:27.280 --> 01:14:29.590 align:start position:0% button near the reports table. Towards the<01:14:27.440> end,<01:14:28.080> all<01:14:28.320> the<01:14:28.480> detailed<01:14:28.960> steps<01:14:29.280> we<01:14:29.520> need 01:14:29.590 --> 01:14:29.600 align:start position:0% the end, all the detailed steps we need 01:14:29.600 --> 01:14:32.310 align:start position:0% the end, all the detailed steps we need to<01:14:29.760> perform<01:14:30.000> are<01:14:30.320> available.<01:14:31.600> This<01:14:31.840> is<01:14:32.000> our 01:14:32.310 --> 01:14:32.320 align:start position:0% to perform are available. This is our 01:14:32.320 --> 01:14:35.110 align:start position:0% to perform are available. This is our acceptance<01:14:32.880> criteria.<01:14:34.080> The<01:14:34.320> export<01:14:34.719> button 01:14:35.110 --> 01:14:35.120 align:start position:0% acceptance criteria. The export button 01:14:35.120 --> 01:14:37.350 align:start position:0% acceptance criteria. The export button appears<01:14:35.440> on<01:14:35.600> the<01:14:35.760> report<01:14:36.080> page.<01:14:36.880> Clicking<01:14:37.199> the 01:14:37.350 --> 01:14:37.360 align:start position:0% appears on the report page. Clicking the 01:14:37.360 --> 01:14:40.229 align:start position:0% appears on the report page. Clicking the button<01:14:37.760> downloads<01:14:38.159> a<01:14:38.400> valid<01:14:38.719> CSV<01:14:39.360> file<01:14:40.000> and 01:14:40.229 --> 01:14:40.239 align:start position:0% button downloads a valid CSV file and 01:14:40.239 --> 01:14:42.709 align:start position:0% button downloads a valid CSV file and the<01:14:40.400> CSV<01:14:41.120> contains<01:14:41.520> the<01:14:41.760> same<01:14:42.080> rows<01:14:42.320> displayed 01:14:42.709 --> 01:14:42.719 align:start position:0% the CSV contains the same rows displayed 01:14:42.719 --> 01:14:45.430 align:start position:0% the CSV contains the same rows displayed on<01:14:42.880> the<01:14:43.040> table.<01:14:44.159> It<01:14:44.320> will<01:14:44.480> take<01:14:44.719> data<01:14:45.120> straight 01:14:45.430 --> 01:14:45.440 align:start position:0% on the table. It will take data straight 01:14:45.440 --> 01:14:47.430 align:start position:0% on the table. It will take data straight from<01:14:45.600> the<01:14:45.760> browser.<01:14:46.480> Commit<01:14:46.800> the<01:14:47.040> repository 01:14:47.430 --> 01:14:47.440 align:start position:0% from the browser. Commit the repository 01:14:47.440 --> 01:14:49.750 align:start position:0% from the browser. Commit the repository in<01:14:47.679> GitHub<01:14:48.320> and<01:14:48.640> provide<01:14:48.960> the<01:14:49.199> response<01:14:49.520> in 01:14:49.750 --> 01:14:49.760 align:start position:0% in GitHub and provide the response in 01:14:49.760 --> 01:14:51.910 align:start position:0% in GitHub and provide the response in document<01:14:50.239> form. 01:14:51.910 --> 01:14:51.920 align:start position:0% document form. 01:14:51.920 --> 01:14:53.750 align:start position:0% document form. Generating<01:14:52.480> code<01:14:52.800> from<01:14:53.040> requirements<01:14:53.520> with 01:14:53.750 --> 01:14:53.760 align:start position:0% Generating code from requirements with 01:14:53.760 --> 01:14:55.910 align:start position:0% Generating code from requirements with codeex<01:14:54.400> improves<01:14:54.960> overall<01:14:55.440> development 01:14:55.910 --> 01:14:55.920 align:start position:0% codeex improves overall development 01:14:55.920 --> 01:14:58.950 align:start position:0% codeex improves overall development speed.<01:14:57.120> When<01:14:57.360> our<01:14:57.600> prompts<01:14:57.920> are<01:14:58.080> better,<01:14:58.640> the 01:14:58.950 --> 01:14:58.960 align:start position:0% speed. When our prompts are better, the 01:14:58.960 --> 01:15:00.950 align:start position:0% speed. When our prompts are better, the final<01:14:59.280> results<01:14:59.600> we<01:14:59.840> get<01:15:00.000> will<01:15:00.239> also<01:15:00.480> be<01:15:00.640> much 01:15:00.950 --> 01:15:00.960 align:start position:0% final results we get will also be much 01:15:00.960 --> 01:15:04.550 align:start position:0% final results we get will also be much better,<01:15:01.600> which<01:15:01.840> we<01:15:02.000> can<01:15:02.159> then<01:15:02.480> utilize<01:15:02.960> today. 01:15:04.550 --> 01:15:04.560 align:start position:0% better, which we can then utilize today. 01:15:04.560 --> 01:15:07.350 align:start position:0% better, which we can then utilize today. Clear<01:15:04.880> requirements,<01:15:05.760> a<01:15:06.000> defined<01:15:06.400> scope,<01:15:07.040> and 01:15:07.350 --> 01:15:07.360 align:start position:0% Clear requirements, a defined scope, and 01:15:07.360 --> 01:15:10.070 align:start position:0% Clear requirements, a defined scope, and strong<01:15:07.679> acceptance<01:15:08.320> criteria<01:15:09.199> help<01:15:09.600> codeex 01:15:10.070 --> 01:15:10.080 align:start position:0% strong acceptance criteria help codeex 01:15:10.080 --> 01:15:12.470 align:start position:0% strong acceptance criteria help codeex produce<01:15:10.400> code<01:15:10.640> that<01:15:10.880> is<01:15:11.040> easier<01:15:11.360> to<01:15:11.600> review, 01:15:12.470 --> 01:15:12.480 align:start position:0% produce code that is easier to review, 01:15:12.480 --> 01:15:16.149 align:start position:0% produce code that is easier to review, test,<01:15:13.120> and<01:15:13.360> merge<01:15:13.679> in<01:15:13.920> big<01:15:14.159> enterprise<01:15:14.719> teams. 01:15:16.149 --> 01:15:16.159 align:start position:0% test, and merge in big enterprise teams. 01:15:16.159 --> 01:15:18.070 align:start position:0% test, and merge in big enterprise teams. We<01:15:16.400> are<01:15:16.560> discussing<01:15:16.960> how<01:15:17.199> big<01:15:17.520> enterprise 01:15:18.070 --> 01:15:18.080 align:start position:0% We are discussing how big enterprise 01:15:18.080 --> 01:15:20.149 align:start position:0% We are discussing how big enterprise teams<01:15:18.800> can<01:15:19.040> incorporate<01:15:19.520> these<01:15:19.840> modern 01:15:20.149 --> 01:15:20.159 align:start position:0% teams can incorporate these modern 01:15:20.159 --> 01:15:23.189 align:start position:0% teams can incorporate these modern features<01:15:20.480> on<01:15:20.719> a<01:15:20.880> larger<01:15:21.199> scale.<01:15:21.520> Today<01:15:22.960> our 01:15:23.189 --> 01:15:23.199 align:start position:0% features on a larger scale. Today our 01:15:23.199 --> 01:15:24.790 align:start position:0% features on a larger scale. Today our next<01:15:23.440> discussion<01:15:23.920> will<01:15:24.159> be<01:15:24.320> related<01:15:24.640> to 01:15:24.790 --> 01:15:24.800 align:start position:0% next discussion will be related to 01:15:24.800 --> 01:15:26.950 align:start position:0% next discussion will be related to editing<01:15:25.199> and<01:15:25.440> refactoring<01:15:26.159> existing<01:15:26.719> code 01:15:26.950 --> 01:15:26.960 align:start position:0% editing and refactoring existing code 01:15:26.960 --> 01:15:30.070 align:start position:0% editing and refactoring existing code bases.<01:15:28.239> We<01:15:28.480> have<01:15:28.640> generated<01:15:29.120> this<01:15:29.360> exact<01:15:29.840> code 01:15:30.070 --> 01:15:30.080 align:start position:0% bases. We have generated this exact code 01:15:30.080 --> 01:15:32.229 align:start position:0% bases. We have generated this exact code as<01:15:30.320> an<01:15:30.560> example<01:15:30.960> project<01:15:31.600> where<01:15:31.840> we<01:15:32.000> are 01:15:32.229 --> 01:15:32.239 align:start position:0% as an example project where we are 01:15:32.239 --> 01:15:34.229 align:start position:0% as an example project where we are utilizing<01:15:32.800> all<01:15:33.040> these<01:15:33.280> core<01:15:33.600> elements<01:15:34.000> in 01:15:34.229 --> 01:15:34.239 align:start position:0% utilizing all these core elements in 01:15:34.239 --> 01:15:36.149 align:start position:0% utilizing all these core elements in real<01:15:34.480> time. 01:15:36.149 --> 01:15:36.159 align:start position:0% real time. 01:15:36.159 --> 01:15:38.310 align:start position:0% real time. Now<01:15:36.880> suppose<01:15:37.280> our<01:15:37.520> initial<01:15:37.840> code<01:15:38.080> is 01:15:38.310 --> 01:15:38.320 align:start position:0% Now suppose our initial code is 01:15:38.320 --> 01:15:41.189 align:start position:0% Now suppose our initial code is generated<01:15:38.800> and<01:15:39.120> ready.<01:15:40.239> To<01:15:40.480> demonstrate<01:15:40.960> this 01:15:41.189 --> 01:15:41.199 align:start position:0% generated and ready. To demonstrate this 01:15:41.199 --> 01:15:43.350 align:start position:0% generated and ready. To demonstrate this point,<01:15:41.440> well,<01:15:42.000> I<01:15:42.320> will<01:15:42.400> show<01:15:42.560> you<01:15:42.719> a<01:15:42.960> custom 01:15:43.350 --> 01:15:43.360 align:start position:0% point, well, I will show you a custom 01:15:43.360 --> 01:15:45.350 align:start position:0% point, well, I will show you a custom calculator<01:15:43.920> code<01:15:44.159> from<01:15:44.400> our<01:15:44.640> older<01:15:44.960> previous 01:15:45.350 --> 01:15:45.360 align:start position:0% calculator code from our older previous 01:15:45.360 --> 01:15:46.950 align:start position:0% calculator code from our older previous generations. 01:15:46.950 --> 01:15:46.960 align:start position:0% generations. 01:15:46.960 --> 01:15:49.430 align:start position:0% generations. In<01:15:47.199> that<01:15:47.520> existing<01:15:48.000> code,<01:15:48.640> we<01:15:48.880> will<01:15:49.120> perform 01:15:49.430 --> 01:15:49.440 align:start position:0% In that existing code, we will perform 01:15:49.440 --> 01:15:51.669 align:start position:0% In that existing code, we will perform and<01:15:49.760> showcase<01:15:50.239> our<01:15:50.560> past<01:15:50.800> iterations<01:15:51.440> and 01:15:51.669 --> 01:15:51.679 align:start position:0% and showcase our past iterations and 01:15:51.679 --> 01:15:54.550 align:start position:0% and showcase our past iterations and refactoring<01:15:52.400> processes<01:15:53.440> step<01:15:53.760> by<01:15:54.000> step<01:15:54.320> for 01:15:54.550 --> 01:15:54.560 align:start position:0% refactoring processes step by step for 01:15:54.560 --> 01:15:57.030 align:start position:0% refactoring processes step by step for all<01:15:54.800> of<01:15:54.880> you<01:15:55.040> to<01:15:55.280> see<01:15:55.440> right<01:15:55.679> here<01:15:56.000> today.<01:15:56.800> Now, 01:15:57.030 --> 01:15:57.040 align:start position:0% all of you to see right here today. Now, 01:15:57.040 --> 01:15:59.510 align:start position:0% all of you to see right here today. Now, we<01:15:57.280> will<01:15:57.440> discuss<01:15:57.920> editing<01:15:58.480> or<01:15:58.800> refactoring 01:15:59.510 --> 01:15:59.520 align:start position:0% we will discuss editing or refactoring 01:15:59.520 --> 01:16:01.510 align:start position:0% we will discuss editing or refactoring the<01:15:59.760> code. 01:16:01.510 --> 01:16:01.520 align:start position:0% the code. 01:16:01.520 --> 01:16:03.430 align:start position:0% the code. Here<01:16:01.760> you<01:16:02.000> can<01:16:02.159> see<01:16:02.239> that<01:16:02.480> we<01:16:02.719> asked<01:16:02.960> to<01:16:03.120> create 01:16:03.430 --> 01:16:03.440 align:start position:0% Here you can see that we asked to create 01:16:03.440 --> 01:16:06.229 align:start position:0% Here you can see that we asked to create a<01:16:03.679> calculator<01:16:04.239> code.<01:16:05.280> It<01:16:05.440> took<01:16:05.679> a<01:16:05.840> quick<01:16:06.080> look 01:16:06.229 --> 01:16:06.239 align:start position:0% a calculator code. It took a quick look 01:16:06.239 --> 01:16:09.270 align:start position:0% a calculator code. It took a quick look and<01:16:06.560> made<01:16:06.719> a<01:16:06.880> plan<01:16:07.040> for<01:16:07.280> us.<01:16:08.480> After<01:16:08.880> making<01:16:09.120> the 01:16:09.270 --> 01:16:09.280 align:start position:0% and made a plan for us. After making the 01:16:09.280 --> 01:16:11.590 align:start position:0% and made a plan for us. After making the plan,<01:16:09.760> it<01:16:10.000> implemented<01:16:10.480> the<01:16:10.719> calculator<01:16:11.360> in 01:16:11.590 --> 01:16:11.600 align:start position:0% plan, it implemented the calculator in 01:16:11.600 --> 01:16:14.550 align:start position:0% plan, it implemented the calculator in the<01:16:11.840> calculator.py<01:16:13.040> file. 01:16:14.550 --> 01:16:14.560 align:start position:0% the calculator.py file. 01:16:14.560 --> 01:16:16.950 align:start position:0% the calculator.py file. This<01:16:14.800> is<01:16:14.960> our<01:16:15.199> calculator. 01:16:16.950 --> 01:16:16.960 align:start position:0% This is our calculator. 01:16:16.960 --> 01:16:18.709 align:start position:0% This is our calculator. Everything<01:16:17.280> in<01:16:17.520> it<01:16:17.679> is<01:16:17.920> functional<01:16:18.400> from 01:16:18.709 --> 01:16:18.719 align:start position:0% Everything in it is functional from 01:16:18.719 --> 01:16:21.669 align:start position:0% Everything in it is functional from start<01:16:18.960> to<01:16:19.199> finish.<01:16:20.320> If<01:16:20.480> we<01:16:20.719> want<01:16:20.800> to<01:16:20.960> run<01:16:21.199> it, 01:16:21.669 --> 01:16:21.679 align:start position:0% start to finish. If we want to run it, 01:16:21.679 --> 01:16:23.830 align:start position:0% start to finish. If we want to run it, we<01:16:21.920> will<01:16:22.080> see<01:16:22.159> that<01:16:22.400> the<01:16:22.560> verification<01:16:23.360> passed 01:16:23.830 --> 01:16:23.840 align:start position:0% we will see that the verification passed 01:16:23.840 --> 01:16:26.870 align:start position:0% we will see that the verification passed using<01:16:24.080> the<01:16:24.239> bundled<01:16:24.719> Python<01:16:25.199> runtime. 01:16:26.870 --> 01:16:26.880 align:start position:0% using the bundled Python runtime. 01:16:26.880 --> 01:16:29.590 align:start position:0% using the bundled Python runtime. Note<01:16:27.199> that<01:16:27.440> Python<01:16:27.920> and<01:16:28.159> py<01:16:28.719> are<01:16:28.960> not<01:16:29.199> on<01:16:29.440> our 01:16:29.590 --> 01:16:29.600 align:start position:0% Note that Python and py are not on our 01:16:29.600 --> 01:16:32.790 align:start position:0% Note that Python and py are not on our system<01:16:30.000> path.<01:16:31.280> So<01:16:31.600> if<01:16:31.840> we<01:16:32.000> want<01:16:32.080> to<01:16:32.239> use<01:16:32.400> it<01:16:32.560> in 01:16:32.790 --> 01:16:32.800 align:start position:0% system path. So if we want to use it in 01:16:32.800 --> 01:16:34.870 align:start position:0% system path. So if we want to use it in our<01:16:32.960> environment,<01:16:33.840> we<01:16:34.080> need<01:16:34.320> all<01:16:34.560> these 01:16:34.870 --> 01:16:34.880 align:start position:0% our environment, we need all these 01:16:34.880 --> 01:16:36.709 align:start position:0% our environment, we need all these requirements. 01:16:36.709 --> 01:16:36.719 align:start position:0% requirements. 01:16:36.719 --> 01:16:39.910 align:start position:0% requirements. I<01:16:36.960> will<01:16:37.120> open<01:16:37.440> PowerShell<01:16:38.159> here<01:16:39.120> or<01:16:39.520> I<01:16:39.760> will 01:16:39.910 --> 01:16:39.920 align:start position:0% I will open PowerShell here or I will 01:16:39.920 --> 01:16:42.709 align:start position:0% I will open PowerShell here or I will just<01:16:40.159> open<01:16:40.400> the<01:16:40.560> command<01:16:40.880> prompt.<01:16:42.320> In<01:16:42.560> the 01:16:42.709 --> 01:16:42.719 align:start position:0% just open the command prompt. In the 01:16:42.719 --> 01:16:44.470 align:start position:0% just open the command prompt. In the command<01:16:43.120> prompt,<01:16:43.600> we<01:16:43.840> will<01:16:44.000> give<01:16:44.239> this 01:16:44.470 --> 01:16:44.480 align:start position:0% command prompt, we will give this 01:16:44.480 --> 01:16:47.590 align:start position:0% command prompt, we will give this command.<01:16:45.840> When<01:16:46.080> I<01:16:46.239> press<01:16:46.480> enter,<01:16:47.280> you<01:16:47.520> will 01:16:47.590 --> 01:16:47.600 align:start position:0% command. When I press enter, you will 01:16:47.600 --> 01:16:49.350 align:start position:0% command. When I press enter, you will see<01:16:47.760> that<01:16:47.920> we<01:16:48.159> have<01:16:48.239> a<01:16:48.480> complete<01:16:48.880> response 01:16:49.350 --> 01:16:49.360 align:start position:0% see that we have a complete response 01:16:49.360 --> 01:16:52.550 align:start position:0% see that we have a complete response included<01:16:49.920> here.<01:16:51.360> Now,<01:16:51.679> I<01:16:51.920> will<01:16:52.000> include<01:16:52.320> it 01:16:52.550 --> 01:16:52.560 align:start position:0% included here. Now, I will include it 01:16:52.560 --> 01:16:55.189 align:start position:0% included here. Now, I will include it here.<01:16:53.760> There<01:16:53.920> is<01:16:54.080> an<01:16:54.239> issue<01:16:54.560> in<01:16:54.800> the<01:16:54.960> first 01:16:55.189 --> 01:16:55.199 align:start position:0% here. There is an issue in the first 01:16:55.199 --> 01:16:57.350 align:start position:0% here. There is an issue in the first line<01:16:55.440> of<01:16:55.600> our<01:16:55.840> code. 01:16:57.350 --> 01:16:57.360 align:start position:0% line of our code. 01:16:57.360 --> 01:17:00.630 align:start position:0% line of our code. So,<01:16:57.679> we<01:16:57.920> will<01:16:58.080> run<01:16:58.239> it<01:16:58.400> from<01:16:58.640> here<01:16:59.040> to<01:16:59.360> here.<01:17:00.480> I 01:17:00.630 --> 01:17:00.640 align:start position:0% So, we will run it from here to here. I 01:17:00.640 --> 01:17:04.149 align:start position:0% So, we will run it from here to here. I will<01:17:00.800> copy<01:17:01.120> this.<01:17:02.480> After<01:17:02.800> copying,<01:17:03.600> I<01:17:03.840> will<01:17:04.000> go 01:17:04.149 --> 01:17:04.159 align:start position:0% will copy this. After copying, I will go 01:17:04.159 --> 01:17:06.870 align:start position:0% will copy this. After copying, I will go back<01:17:04.320> to<01:17:04.480> the<01:17:04.640> command<01:17:04.960> prompt.<01:17:05.520> Here<01:17:06.560> is<01:17:06.719> the 01:17:06.870 --> 01:17:06.880 align:start position:0% back to the command prompt. Here is the 01:17:06.880 --> 01:17:08.870 align:start position:0% back to the command prompt. Here is the command<01:17:07.280> prompt. 01:17:08.870 --> 01:17:08.880 align:start position:0% command prompt. 01:17:08.880 --> 01:17:10.550 align:start position:0% command prompt. Now<01:17:09.120> we<01:17:09.280> will<01:17:09.440> include<01:17:09.760> it<01:17:09.920> in<01:17:10.080> the<01:17:10.239> command 01:17:10.550 --> 01:17:10.560 align:start position:0% Now we will include it in the command 01:17:10.560 --> 01:17:12.149 align:start position:0% Now we will include it in the command prompt. 01:17:12.149 --> 01:17:12.159 align:start position:0% prompt. 01:17:12.159 --> 01:17:14.229 align:start position:0% prompt. When<01:17:12.400> we<01:17:12.560> include<01:17:12.880> it,<01:17:13.520> you<01:17:13.760> can<01:17:13.920> see<01:17:14.000> that 01:17:14.229 --> 01:17:14.239 align:start position:0% When we include it, you can see that 01:17:14.239 --> 01:17:17.030 align:start position:0% When we include it, you can see that because<01:17:14.560> this<01:17:14.800> file<01:17:15.120> is<01:17:15.360> very<01:17:15.679> old,<01:17:16.400> our<01:17:16.719> file 01:17:17.030 --> 01:17:17.040 align:start position:0% because this file is very old, our file 01:17:17.040 --> 01:17:20.070 align:start position:0% because this file is very old, our file is<01:17:17.280> not<01:17:17.520> available<01:17:17.920> here.<01:17:19.360> But<01:17:19.440> we<01:17:19.679> can<01:17:19.840> still 01:17:20.070 --> 01:17:20.080 align:start position:0% is not available here. But we can still 01:17:20.080 --> 01:17:22.470 align:start position:0% is not available here. But we can still run<01:17:20.239> it<01:17:20.400> in<01:17:20.560> our<01:17:20.719> browser. 01:17:22.470 --> 01:17:22.480 align:start position:0% run it in our browser. 01:17:22.480 --> 01:17:24.229 align:start position:0% run it in our browser. Now<01:17:22.719> we<01:17:22.880> will<01:17:23.120> look<01:17:23.199> at<01:17:23.360> our<01:17:23.600> editing<01:17:24.000> and 01:17:24.229 --> 01:17:24.239 align:start position:0% Now we will look at our editing and 01:17:24.239 --> 01:17:27.510 align:start position:0% Now we will look at our editing and refactoring<01:17:24.960> here.<01:17:26.320> Usually<01:17:26.960> this<01:17:27.199> is<01:17:27.280> the 01:17:27.510 --> 01:17:27.520 align:start position:0% refactoring here. Usually this is the 01:17:27.520 --> 01:17:30.149 align:start position:0% refactoring here. Usually this is the most<01:17:27.840> valuable<01:17:28.400> capability<01:17:29.040> of<01:17:29.280> our<01:17:29.440> OpenAI 01:17:30.149 --> 01:17:30.159 align:start position:0% most valuable capability of our OpenAI 01:17:30.159 --> 01:17:31.990 align:start position:0% most valuable capability of our OpenAI codeex<01:17:30.719> for<01:17:30.960> enterprise<01:17:31.440> software 01:17:31.990 --> 01:17:32.000 align:start position:0% codeex for enterprise software 01:17:32.000 --> 01:17:33.590 align:start position:0% codeex for enterprise software development. 01:17:33.590 --> 01:17:33.600 align:start position:0% development. 01:17:33.600 --> 01:17:36.310 align:start position:0% development. While<01:17:33.920> generating<01:17:34.560> new<01:17:34.800> code<01:17:35.120> is<01:17:35.440> useful, 01:17:36.310 --> 01:17:36.320 align:start position:0% While generating new code is useful, 01:17:36.320 --> 01:17:38.310 align:start position:0% While generating new code is useful, developers<01:17:36.960> spend<01:17:37.280> a<01:17:37.520> lot<01:17:37.679> of<01:17:37.840> time 01:17:38.310 --> 01:17:38.320 align:start position:0% developers spend a lot of time 01:17:38.320 --> 01:17:41.350 align:start position:0% developers spend a lot of time improving,<01:17:39.360> maintaining,<01:17:40.239> and<01:17:40.560> modernizing 01:17:41.350 --> 01:17:41.360 align:start position:0% improving, maintaining, and modernizing 01:17:41.360 --> 01:17:43.750 align:start position:0% improving, maintaining, and modernizing existing<01:17:41.840> applications. 01:17:43.750 --> 01:17:43.760 align:start position:0% existing applications. 01:17:43.760 --> 01:17:45.910 align:start position:0% existing applications. Codeex<01:17:44.400> can<01:17:44.560> analyze<01:17:44.960> the<01:17:45.280> current<01:17:45.600> code 01:17:45.910 --> 01:17:45.920 align:start position:0% Codeex can analyze the current code 01:17:45.920 --> 01:17:48.550 align:start position:0% Codeex can analyze the current code base.<01:17:46.880> It<01:17:47.120> can<01:17:47.280> understand<01:17:47.840> relationships 01:17:48.550 --> 01:17:48.560 align:start position:0% base. It can understand relationships 01:17:48.560 --> 01:17:51.830 align:start position:0% base. It can understand relationships between<01:17:48.960> files,<01:17:50.000> identify<01:17:50.560> code<01:17:50.800> smells,<01:17:51.520> and 01:17:51.830 --> 01:17:51.840 align:start position:0% between files, identify code smells, and 01:17:51.840 --> 01:17:53.430 align:start position:0% between files, identify code smells, and suggest<01:17:52.239> improvements<01:17:52.880> for<01:17:53.120> better 01:17:53.430 --> 01:17:53.440 align:start position:0% suggest improvements for better 01:17:53.440 --> 01:17:55.350 align:start position:0% suggest improvements for better readability. 01:17:55.350 --> 01:17:55.360 align:start position:0% readability. 01:17:55.360 --> 01:17:58.229 align:start position:0% readability. First,<01:17:55.679> I<01:17:55.920> will<01:17:56.080> explain<01:17:56.400> the<01:17:56.640> first<01:17:56.880> thing. 01:17:58.229 --> 01:17:58.239 align:start position:0% First, I will explain the first thing. 01:17:58.239 --> 01:18:01.510 align:start position:0% First, I will explain the first thing. This<01:17:58.480> is<01:17:58.560> what<01:17:58.800> we<01:17:58.960> call<01:17:59.360> refactoring<01:18:00.159> code. 01:18:01.510 --> 01:18:01.520 align:start position:0% This is what we call refactoring code. 01:18:01.520 --> 01:18:03.750 align:start position:0% This is what we call refactoring code. This<01:18:01.760> is<01:18:01.840> a<01:18:02.080> process<01:18:02.400> of<01:18:02.719> restructuring<01:18:03.440> the 01:18:03.750 --> 01:18:03.760 align:start position:0% This is a process of restructuring the 01:18:03.760 --> 01:18:07.350 align:start position:0% This is a process of restructuring the existing<01:18:04.239> code.<01:18:05.600> It<01:18:05.840> improves<01:18:06.320> readability, 01:18:07.350 --> 01:18:07.360 align:start position:0% existing code. It improves readability, 01:18:07.360 --> 01:18:09.990 align:start position:0% existing code. It improves readability, maintainability<01:18:08.640> and<01:18:08.960> internal<01:18:09.520> design 01:18:09.990 --> 01:18:10.000 align:start position:0% maintainability and internal design 01:18:10.000 --> 01:18:13.350 align:start position:0% maintainability and internal design without<01:18:10.480> changing<01:18:10.880> its<01:18:11.199> external<01:18:11.760> behavior. 01:18:13.350 --> 01:18:13.360 align:start position:0% without changing its external behavior. 01:18:13.360 --> 01:18:15.510 align:start position:0% without changing its external behavior. We<01:18:13.600> primarily<01:18:14.159> involve<01:18:14.560> this<01:18:14.800> in<01:18:15.040> our<01:18:15.199> code 01:18:15.510 --> 01:18:15.520 align:start position:0% We primarily involve this in our code 01:18:15.520 --> 01:18:18.950 align:start position:0% We primarily involve this in our code review.<01:18:16.800> If<01:18:17.040> I<01:18:17.199> go<01:18:17.280> to<01:18:17.440> Excaladraw,<01:18:18.560> I<01:18:18.800> can 01:18:18.950 --> 01:18:18.960 align:start position:0% review. If I go to Excaladraw, I can 01:18:18.960 --> 01:18:21.110 align:start position:0% review. If I go to Excaladraw, I can tell<01:18:19.120> you<01:18:19.280> that<01:18:19.440> after<01:18:19.840> refactoring,<01:18:20.880> the 01:18:21.110 --> 01:18:21.120 align:start position:0% tell you that after refactoring, the 01:18:21.120 --> 01:18:24.070 align:start position:0% tell you that after refactoring, the next<01:18:21.360> thing<01:18:21.520> is<01:18:21.840> restructuring<01:18:22.560> or<01:18:22.880> editing. 01:18:24.070 --> 01:18:24.080 align:start position:0% next thing is restructuring or editing. 01:18:24.080 --> 01:18:26.229 align:start position:0% next thing is restructuring or editing. That<01:18:24.320> is<01:18:24.480> very<01:18:24.800> simple. 01:18:26.229 --> 01:18:26.239 align:start position:0% That is very simple. 01:18:26.239 --> 01:18:27.990 align:start position:0% That is very simple. It<01:18:26.480> is<01:18:26.640> simple<01:18:27.040> because<01:18:27.280> we<01:18:27.520> can<01:18:27.600> come<01:18:27.760> into 01:18:27.990 --> 01:18:28.000 align:start position:0% It is simple because we can come into 01:18:28.000 --> 01:18:30.870 align:start position:0% It is simple because we can come into our<01:18:28.239> code<01:18:28.960> include<01:18:29.440> any<01:18:29.679> line<01:18:30.000> here<01:18:30.560> and 01:18:30.870 --> 01:18:30.880 align:start position:0% our code include any line here and 01:18:30.880 --> 01:18:33.750 align:start position:0% our code include any line here and include<01:18:31.280> things<01:18:31.440> by<01:18:31.679> giving<01:18:31.920> a<01:18:32.159> local<01:18:32.480> comment 01:18:33.750 --> 01:18:33.760 align:start position:0% include things by giving a local comment 01:18:33.760 --> 01:18:36.630 align:start position:0% include things by giving a local comment or<01:18:34.239> if<01:18:34.400> we<01:18:34.640> want<01:18:34.719> to<01:18:34.880> do<01:18:35.040> overall<01:18:35.600> refactoring 01:18:36.630 --> 01:18:36.640 align:start position:0% or if we want to do overall refactoring 01:18:36.640 --> 01:18:39.590 align:start position:0% or if we want to do overall refactoring I<01:18:36.880> can<01:18:37.040> say<01:18:37.199> to<01:18:37.440> make<01:18:37.600> this<01:18:37.840> into<01:18:38.080> an<01:18:38.320> HTML<01:18:39.280> file 01:18:39.590 --> 01:18:39.600 align:start position:0% I can say to make this into an HTML file 01:18:39.600 --> 01:18:43.030 align:start position:0% I can say to make this into an HTML file that<01:18:39.840> I<01:18:40.000> can<01:18:40.159> run<01:18:40.320> in<01:18:40.560> VS<01:18:40.960> code<01:18:42.320> here<01:18:42.640> you<01:18:42.880> can 01:18:43.030 --> 01:18:43.040 align:start position:0% that I can run in VS code here you can 01:18:43.040 --> 01:18:45.110 align:start position:0% that I can run in VS code here you can see<01:18:43.199> that<01:18:43.440> now<01:18:43.760> it<01:18:44.000> will<01:18:44.159> directly<01:18:44.640> take<01:18:44.880> our 01:18:45.110 --> 01:18:45.120 align:start position:0% see that now it will directly take our 01:18:45.120 --> 01:18:49.350 align:start position:0% see that now it will directly take our prompt<01:18:46.400> the<01:18:46.640> code<01:18:46.960> was<01:18:47.199> previously<01:18:47.679> available 01:18:49.350 --> 01:18:49.360 align:start position:0% prompt the code was previously available 01:18:49.360 --> 01:18:51.030 align:start position:0% prompt the code was previously available now<01:18:49.679> it<01:18:49.920> will<01:18:50.080> connect<01:18:50.320> our<01:18:50.560> Python 01:18:51.030 --> 01:18:51.040 align:start position:0% now it will connect our Python 01:18:51.040 --> 01:18:54.390 align:start position:0% now it will connect our Python calculator<01:18:51.679> into<01:18:52.000> a<01:18:52.159> browserfriendly<01:18:53.280> HTML 01:18:54.390 --> 01:18:54.400 align:start position:0% calculator into a browserfriendly HTML 01:18:54.400 --> 01:18:55.990 align:start position:0% calculator into a browserfriendly HTML version. 01:18:55.990 --> 01:18:56.000 align:start position:0% version. 01:18:56.000 --> 01:18:59.590 align:start position:0% version. Alternatively,<01:18:57.120> I<01:18:57.280> will<01:18:57.440> open<01:18:57.679> our<01:18:57.920> VS<01:18:58.320> Code. 01:18:59.590 --> 01:18:59.600 align:start position:0% Alternatively, I will open our VS Code. 01:18:59.600 --> 01:19:01.110 align:start position:0% Alternatively, I will open our VS Code. You<01:18:59.760> might<01:19:00.000> remember<01:19:00.239> that<01:19:00.480> we<01:19:00.800> already 01:19:01.110 --> 01:19:01.120 align:start position:0% You might remember that we already 01:19:01.120 --> 01:19:03.669 align:start position:0% You might remember that we already included<01:19:01.679> codecs<01:19:02.239> in<01:19:02.480> Visual<01:19:02.880> Studio<01:19:03.360> Code 01:19:03.669 --> 01:19:03.679 align:start position:0% included codecs in Visual Studio Code 01:19:03.679 --> 01:19:06.630 align:start position:0% included codecs in Visual Studio Code before.<01:19:05.040> So,<01:19:05.360> this<01:19:05.600> will<01:19:05.840> also<01:19:06.080> be<01:19:06.320> available 01:19:06.630 --> 01:19:06.640 align:start position:0% before. So, this will also be available 01:19:06.640 --> 01:19:09.910 align:start position:0% before. So, this will also be available for<01:19:06.880> us<01:19:07.040> to<01:19:07.280> use<01:19:07.440> in<01:19:07.679> a<01:19:07.920> much<01:19:08.159> easier<01:19:08.640> way. 01:19:09.910 --> 01:19:09.920 align:start position:0% for us to use in a much easier way. 01:19:09.920 --> 01:19:12.550 align:start position:0% for us to use in a much easier way. Along<01:19:10.239> with<01:19:10.480> this,<01:19:11.040> in<01:19:11.280> Visual<01:19:11.679> Studio<01:19:12.239> Code, 01:19:12.550 --> 01:19:12.560 align:start position:0% Along with this, in Visual Studio Code, 01:19:12.560 --> 01:19:14.470 align:start position:0% Along with this, in Visual Studio Code, where<01:19:12.880> everything<01:19:13.120> else<01:19:13.440> is,<01:19:14.080> we<01:19:14.320> will 01:19:14.470 --> 01:19:14.480 align:start position:0% where everything else is, we will 01:19:14.480 --> 01:19:16.550 align:start position:0% where everything else is, we will automatically<01:19:15.199> include<01:19:15.679> our<01:19:16.000> calculator 01:19:16.550 --> 01:19:16.560 align:start position:0% automatically include our calculator 01:19:16.560 --> 01:19:18.070 align:start position:0% automatically include our calculator file. 01:19:18.070 --> 01:19:18.080 align:start position:0% file. 01:19:18.080 --> 01:19:21.189 align:start position:0% file. Codeex<01:19:18.640> is<01:19:18.880> open.<01:19:19.840> All<01:19:20.080> our<01:19:20.320> generations<01:19:20.960> and 01:19:21.189 --> 01:19:21.199 align:start position:0% Codeex is open. All our generations and 01:19:21.199 --> 01:19:24.070 align:start position:0% Codeex is open. All our generations and things<01:19:21.520> are<01:19:21.760> available<01:19:22.080> in<01:19:22.320> it.<01:19:23.440> Now<01:19:23.679> you<01:19:23.920> will 01:19:24.070 --> 01:19:24.080 align:start position:0% things are available in it. Now you will 01:19:24.080 --> 01:19:25.990 align:start position:0% things are available in it. Now you will see<01:19:24.239> that<01:19:24.400> our<01:19:24.640> codeex<01:19:25.199> file<01:19:25.440> has<01:19:25.600> arrived 01:19:25.990 --> 01:19:26.000 align:start position:0% see that our codeex file has arrived 01:19:26.000 --> 01:19:29.510 align:start position:0% see that our codeex file has arrived here<01:19:27.199> in<01:19:27.360> the<01:19:27.520> codeex<01:19:28.080> file.<01:19:28.800> All<01:19:29.040> our<01:19:29.280> things 01:19:29.510 --> 01:19:29.520 align:start position:0% here in the codeex file. All our things 01:19:29.520 --> 01:19:31.750 align:start position:0% here in the codeex file. All our things are<01:19:29.760> directly<01:19:30.239> included. 01:19:31.750 --> 01:19:31.760 align:start position:0% are directly included. 01:19:31.760 --> 01:19:34.070 align:start position:0% are directly included. Now<01:19:31.920> you<01:19:32.159> can<01:19:32.320> see<01:19:32.480> that<01:19:32.640> if<01:19:32.880> we<01:19:33.120> want<01:19:33.600> we<01:19:33.920> can 01:19:34.070 --> 01:19:34.080 align:start position:0% Now you can see that if we want we can 01:19:34.080 --> 01:19:35.910 align:start position:0% Now you can see that if we want we can directly<01:19:34.560> open<01:19:34.800> the<01:19:35.040> calculator<01:19:35.520> in<01:19:35.760> the 01:19:35.910 --> 01:19:35.920 align:start position:0% directly open the calculator in the 01:19:35.920 --> 01:19:38.310 align:start position:0% directly open the calculator in the browser<01:19:36.480> or<01:19:36.719> we<01:19:36.960> can<01:19:37.040> copy<01:19:37.360> its<01:19:37.600> link<01:19:37.920> and<01:19:38.159> go 01:19:38.310 --> 01:19:38.320 align:start position:0% browser or we can copy its link and go 01:19:38.320 --> 01:19:40.390 align:start position:0% browser or we can copy its link and go to<01:19:38.480> another<01:19:38.800> browser. 01:19:40.390 --> 01:19:40.400 align:start position:0% to another browser. 01:19:40.400 --> 01:19:42.950 align:start position:0% to another browser. If<01:19:40.640> we<01:19:40.800> copy<01:19:41.120> its<01:19:41.360> link<01:19:41.760> we<01:19:42.000> just<01:19:42.159> have<01:19:42.320> to<01:19:42.480> go 01:19:42.950 --> 01:19:42.960 align:start position:0% If we copy its link we just have to go 01:19:42.960 --> 01:19:44.470 align:start position:0% If we copy its link we just have to go here. 01:19:44.470 --> 01:19:44.480 align:start position:0% here. 01:19:44.480 --> 01:19:46.870 align:start position:0% here. When<01:19:44.640> we<01:19:44.880> open<01:19:45.040> it<01:19:45.280> here<01:19:45.840> the<01:19:46.080> calculator<01:19:46.640> will 01:19:46.870 --> 01:19:46.880 align:start position:0% When we open it here the calculator will 01:19:46.880 --> 01:19:49.350 align:start position:0% When we open it here the calculator will open<01:19:47.040> in<01:19:47.280> our<01:19:47.440> browser. 01:19:49.350 --> 01:19:49.360 align:start position:0% open in our browser. 01:19:49.360 --> 01:19:52.310 align:start position:0% open in our browser. This<01:19:49.520> is<01:19:49.600> a<01:19:49.840> very<01:19:50.159> simple<01:19:50.560> calculator.<01:19:51.920> If<01:19:52.080> we 01:19:52.310 --> 01:19:52.320 align:start position:0% This is a very simple calculator. If we 01:19:52.320 --> 01:19:53.990 align:start position:0% This is a very simple calculator. If we want<01:19:52.400> to<01:19:52.560> open<01:19:52.800> it<01:19:52.960> in<01:19:53.120> the<01:19:53.280> internal<01:19:53.679> browser 01:19:53.990 --> 01:19:54.000 align:start position:0% want to open it in the internal browser 01:19:54.000 --> 01:19:57.270 align:start position:0% want to open it in the internal browser of<01:19:54.239> codeex,<01:19:55.040> that<01:19:55.360> is<01:19:55.520> also<01:19:55.840> possible.<01:19:57.040> It 01:19:57.270 --> 01:19:57.280 align:start position:0% of codeex, that is also possible. It 01:19:57.280 --> 01:19:59.189 align:start position:0% of codeex, that is also possible. It will<01:19:57.440> load<01:19:57.679> and<01:19:57.920> run<01:19:58.080> our<01:19:58.239> calculator<01:19:58.800> in<01:19:59.040> the 01:19:59.189 --> 01:19:59.199 align:start position:0% will load and run our calculator in the 01:19:59.199 --> 01:20:01.350 align:start position:0% will load and run our calculator in the codeex<01:19:59.760> browser. 01:20:01.350 --> 01:20:01.360 align:start position:0% codeex browser. 01:20:01.360 --> 01:20:03.830 align:start position:0% codeex browser. Here<01:20:01.600> you<01:20:01.920> can<01:20:02.000> see<01:20:02.159> that<01:20:02.400> if<01:20:02.640> we<01:20:02.880> want<01:20:03.440> we<01:20:03.679> can 01:20:03.830 --> 01:20:03.840 align:start position:0% Here you can see that if we want we can 01:20:03.840 --> 01:20:05.990 align:start position:0% Here you can see that if we want we can directly<01:20:04.320> use<01:20:04.560> this<01:20:04.800> file<01:20:05.040> in<01:20:05.199> our<01:20:05.360> VS<01:20:05.760> code 01:20:05.990 --> 01:20:06.000 align:start position:0% directly use this file in our VS code 01:20:06.000 --> 01:20:08.550 align:start position:0% directly use this file in our VS code from<01:20:06.239> the<01:20:06.400> options.<01:20:07.840> We<01:20:08.080> can<01:20:08.159> include 01:20:08.550 --> 01:20:08.560 align:start position:0% from the options. We can include 01:20:08.560 --> 01:20:10.229 align:start position:0% from the options. We can include annotations. 01:20:10.229 --> 01:20:10.239 align:start position:0% annotations. 01:20:10.239 --> 01:20:12.470 align:start position:0% annotations. If<01:20:10.480> we<01:20:10.640> want<01:20:11.199> we<01:20:11.440> can<01:20:11.520> save<01:20:11.760> a<01:20:12.000> screenshot 01:20:12.470 --> 01:20:12.480 align:start position:0% If we want we can save a screenshot 01:20:12.480 --> 01:20:13.990 align:start position:0% If we want we can save a screenshot here. 01:20:13.990 --> 01:20:14.000 align:start position:0% here. 01:20:14.000 --> 01:20:16.470 align:start position:0% here. After<01:20:14.320> saving<01:20:14.719> the<01:20:14.880> screenshot<01:20:15.440> here,<01:20:16.080> we<01:20:16.320> can 01:20:16.470 --> 01:20:16.480 align:start position:0% After saving the screenshot here, we can 01:20:16.480 --> 01:20:19.270 align:start position:0% After saving the screenshot here, we can also<01:20:16.800> use<01:20:17.040> it<01:20:17.199> in<01:20:17.440> another<01:20:17.760> browser. 01:20:19.270 --> 01:20:19.280 align:start position:0% also use it in another browser. 01:20:19.280 --> 01:20:22.709 align:start position:0% also use it in another browser. We<01:20:19.440> can<01:20:19.600> come<01:20:19.840> here<01:20:20.080> and<01:20:20.320> use<01:20:20.480> it<01:20:20.640> here<01:20:20.960> too.<01:20:22.400> So 01:20:22.709 --> 01:20:22.719 align:start position:0% We can come here and use it here too. So 01:20:22.719 --> 01:20:25.189 align:start position:0% We can come here and use it here too. So if<01:20:22.960> we<01:20:23.199> want<01:20:23.280> to<01:20:23.520> make<01:20:23.679> any<01:20:23.920> design<01:20:24.320> changes, 01:20:25.189 --> 01:20:25.199 align:start position:0% if we want to make any design changes, 01:20:25.199 --> 01:20:27.750 align:start position:0% if we want to make any design changes, we<01:20:25.440> can<01:20:25.600> do<01:20:25.679> that<01:20:25.920> directly. 01:20:27.750 --> 01:20:27.760 align:start position:0% we can do that directly. 01:20:27.760 --> 01:20:29.910 align:start position:0% we can do that directly. When<01:20:28.080> working<01:20:28.320> with<01:20:28.560> legacy<01:20:29.040> systems, 01:20:29.910 --> 01:20:29.920 align:start position:0% When working with legacy systems, 01:20:29.920 --> 01:20:32.070 align:start position:0% When working with legacy systems, developers<01:20:30.480> often<01:20:30.880> face<01:20:31.120> challenges<01:20:31.679> such<01:20:31.920> as 01:20:32.070 --> 01:20:32.080 align:start position:0% developers often face challenges such as 01:20:32.080 --> 01:20:35.350 align:start position:0% developers often face challenges such as inconsistent<01:20:32.880> coding<01:20:33.280> styles.<01:20:34.719> Here<01:20:35.040> the 01:20:35.350 --> 01:20:35.360 align:start position:0% inconsistent coding styles. Here the 01:20:35.360 --> 01:20:38.470 align:start position:0% inconsistent coding styles. Here the coding<01:20:35.679> we<01:20:35.920> have<01:20:36.080> is<01:20:36.320> AI<01:20:36.800> based<01:20:37.120> coding. 01:20:38.470 --> 01:20:38.480 align:start position:0% coding we have is AI based coding. 01:20:38.480 --> 01:20:40.229 align:start position:0% coding we have is AI based coding. However,<01:20:38.880> if<01:20:39.120> we<01:20:39.360> talk<01:20:39.520> about<01:20:39.760> legacy 01:20:40.229 --> 01:20:40.239 align:start position:0% However, if we talk about legacy 01:20:40.239 --> 01:20:42.390 align:start position:0% However, if we talk about legacy systems,<01:20:41.199> they<01:20:41.440> are<01:20:41.600> systems<01:20:42.000> where<01:20:42.239> we 01:20:42.390 --> 01:20:42.400 align:start position:0% systems, they are systems where we 01:20:42.400 --> 01:20:45.430 align:start position:0% systems, they are systems where we manually<01:20:42.800> write<01:20:43.120> all<01:20:43.360> the<01:20:43.600> code.<01:20:44.800> We<01:20:45.040> make<01:20:45.280> all 01:20:45.430 --> 01:20:45.440 align:start position:0% manually write all the code. We make all 01:20:45.440 --> 01:20:47.669 align:start position:0% manually write all the code. We make all the<01:20:45.679> changes<01:20:46.080> and<01:20:46.320> alterations<01:20:46.960> in<01:20:47.199> that<01:20:47.440> code 01:20:47.669 --> 01:20:47.679 align:start position:0% the changes and alterations in that code 01:20:47.679 --> 01:20:49.510 align:start position:0% the changes and alterations in that code ourselves. 01:20:49.510 --> 01:20:49.520 align:start position:0% ourselves. 01:20:49.520 --> 01:20:51.430 align:start position:0% ourselves. there.<01:20:50.000> Sometimes<01:20:50.480> there<01:20:50.719> are<01:20:50.880> outdated 01:20:51.430 --> 01:20:51.440 align:start position:0% there. Sometimes there are outdated 01:20:51.440 --> 01:20:54.149 align:start position:0% there. Sometimes there are outdated frameworks,<01:20:52.400> poor<01:20:52.719> documentation,<01:20:53.920> and 01:20:54.149 --> 01:20:54.159 align:start position:0% frameworks, poor documentation, and 01:20:54.159 --> 01:20:56.630 align:start position:0% frameworks, poor documentation, and tightly<01:20:54.560> coupled<01:20:55.040> components. 01:20:56.630 --> 01:20:56.640 align:start position:0% tightly coupled components. 01:20:56.640 --> 01:20:58.630 align:start position:0% tightly coupled components. Codeex<01:20:57.199> can<01:20:57.360> help<01:20:57.600> developers<01:20:58.159> understand 01:20:58.630 --> 01:20:58.640 align:start position:0% Codeex can help developers understand 01:20:58.640 --> 01:21:01.030 align:start position:0% Codeex can help developers understand the<01:20:58.880> purpose<01:20:59.199> of<01:20:59.440> existing<01:20:59.920> code<01:21:00.640> before 01:21:01.030 --> 01:21:01.040 align:start position:0% the purpose of existing code before 01:21:01.040 --> 01:21:03.189 align:start position:0% the purpose of existing code before making<01:21:01.360> modifications. 01:21:03.189 --> 01:21:03.199 align:start position:0% making modifications. 01:21:03.199 --> 01:21:05.350 align:start position:0% making modifications. It<01:21:03.440> does<01:21:03.679> this<01:21:03.920> by<01:21:04.239> analyzing<01:21:04.719> the<01:21:04.960> related 01:21:05.350 --> 01:21:05.360 align:start position:0% It does this by analyzing the related 01:21:05.360 --> 01:21:07.590 align:start position:0% It does this by analyzing the related files<01:21:05.760> and<01:21:06.000> dependencies. 01:21:07.590 --> 01:21:07.600 align:start position:0% files and dependencies. 01:21:07.600 --> 01:21:09.669 align:start position:0% files and dependencies. It<01:21:07.840> can<01:21:08.000> recommend<01:21:08.560> safer<01:21:09.040> refactoring 01:21:09.669 --> 01:21:09.679 align:start position:0% It can recommend safer refactoring 01:21:09.679 --> 01:21:12.229 align:start position:0% It can recommend safer refactoring strategies<01:21:10.640> and<01:21:11.120> identify<01:21:11.600> areas<01:21:12.000> where 01:21:12.229 --> 01:21:12.239 align:start position:0% strategies and identify areas where 01:21:12.239 --> 01:21:15.110 align:start position:0% strategies and identify areas where changes<01:21:12.719> may<01:21:12.960> have<01:21:13.199> downstream<01:21:13.760> effects. 01:21:15.110 --> 01:21:15.120 align:start position:0% changes may have downstream effects. 01:21:15.120 --> 01:21:17.110 align:start position:0% changes may have downstream effects. This<01:21:15.440> significantly<01:21:16.159> reduces<01:21:16.640> the<01:21:16.880> time 01:21:17.110 --> 01:21:17.120 align:start position:0% This significantly reduces the time 01:21:17.120 --> 01:21:19.750 align:start position:0% This significantly reduces the time required<01:21:17.840> to<01:21:18.159> understand<01:21:18.719> unfamiliar<01:21:19.440> code 01:21:19.750 --> 01:21:19.760 align:start position:0% required to understand unfamiliar code 01:21:19.760 --> 01:21:21.430 align:start position:0% required to understand unfamiliar code bases. 01:21:21.430 --> 01:21:21.440 align:start position:0% bases. 01:21:21.440 --> 01:21:23.830 align:start position:0% bases. Despite<01:21:21.840> these<01:21:22.159> advantages,<01:21:23.199> developers 01:21:23.830 --> 01:21:23.840 align:start position:0% Despite these advantages, developers 01:21:23.840 --> 01:21:25.990 align:start position:0% Despite these advantages, developers should<01:21:24.080> carefully<01:21:24.560> review<01:21:24.960> all<01:21:25.360> refactoring 01:21:25.990 --> 01:21:26.000 align:start position:0% should carefully review all refactoring 01:21:26.000 --> 01:21:28.310 align:start position:0% should carefully review all refactoring changes<01:21:26.960> before<01:21:27.280> merging<01:21:27.760> them<01:21:27.920> into<01:21:28.080> the 01:21:28.310 --> 01:21:28.320 align:start position:0% changes before merging them into the 01:21:28.320 --> 01:21:30.229 align:start position:0% changes before merging them into the production<01:21:28.719> branches. 01:21:30.229 --> 01:21:30.239 align:start position:0% production branches. 01:21:30.239 --> 01:21:31.830 align:start position:0% production branches. Even<01:21:30.480> when<01:21:30.800> functionality<01:21:31.440> appears 01:21:31.830 --> 01:21:31.840 align:start position:0% Even when functionality appears 01:21:31.840 --> 01:21:34.550 align:start position:0% Even when functionality appears unchanged,<01:21:32.880> modifications<01:21:33.679> can<01:21:34.000> introduce 01:21:34.550 --> 01:21:34.560 align:start position:0% unchanged, modifications can introduce 01:21:34.560 --> 01:21:38.149 align:start position:0% unchanged, modifications can introduce unintended<01:21:35.280> side<01:21:35.600> effects.<01:21:37.040> Now<01:21:37.600> I<01:21:37.840> will<01:21:38.000> work 01:21:38.149 --> 01:21:38.159 align:start position:0% unintended side effects. Now I will work 01:21:38.159 --> 01:21:40.709 align:start position:0% unintended side effects. Now I will work on<01:21:38.400> our<01:21:38.560> code<01:21:38.880> here.<01:21:39.840> I<01:21:40.080> will<01:21:40.239> go<01:21:40.400> to<01:21:40.560> our 01:21:40.709 --> 01:21:40.719 align:start position:0% on our code here. I will go to our 01:21:40.719 --> 01:21:43.910 align:start position:0% on our code here. I will go to our codeex.<01:21:42.000> In<01:21:42.239> codeex,<01:21:43.120> we<01:21:43.360> will<01:21:43.520> write<01:21:43.760> a 01:21:43.910 --> 01:21:43.920 align:start position:0% codeex. In codeex, we will write a 01:21:43.920 --> 01:21:45.669 align:start position:0% codeex. In codeex, we will write a prompt<01:21:44.159> that<01:21:44.400> you<01:21:44.560> are<01:21:44.719> working<01:21:44.880> as<01:21:45.120> a<01:21:45.360> senior 01:21:45.669 --> 01:21:45.679 align:start position:0% prompt that you are working as a senior 01:21:45.679 --> 01:21:48.310 align:start position:0% prompt that you are working as a senior software<01:21:46.159> engineer<01:21:46.560> in<01:21:46.800> this<01:21:46.960> repository. 01:21:48.310 --> 01:21:48.320 align:start position:0% software engineer in this repository. 01:21:48.320 --> 01:21:50.390 align:start position:0% software engineer in this repository. The<01:21:48.560> task<01:21:48.800> is<01:21:49.040> to<01:21:49.199> refactor<01:21:49.760> the<01:21:50.000> existing 01:21:50.390 --> 01:21:50.400 align:start position:0% The task is to refactor the existing 01:21:50.400 --> 01:21:53.270 align:start position:0% The task is to refactor the existing code<01:21:50.719> without<01:21:51.120> changing<01:21:51.440> its<01:21:51.679> functionality. 01:21:53.270 --> 01:21:53.280 align:start position:0% code without changing its functionality. 01:21:53.280 --> 01:21:55.430 align:start position:0% code without changing its functionality. We<01:21:53.520> will<01:21:53.679> improve<01:21:54.000> the<01:21:54.159> code<01:21:54.480> readability<01:21:55.120> and 01:21:55.430 --> 01:21:55.440 align:start position:0% We will improve the code readability and 01:21:55.440 --> 01:21:57.830 align:start position:0% We will improve the code readability and maintainability<01:21:56.639> and<01:21:56.960> remove<01:21:57.280> duplicate 01:21:57.830 --> 01:21:57.840 align:start position:0% maintainability and remove duplicate 01:21:57.840 --> 01:22:00.950 align:start position:0% maintainability and remove duplicate logic<01:21:58.239> with<01:21:58.480> simple<01:21:58.880> complex<01:21:59.360> methods.<01:22:00.719> There 01:22:00.950 --> 01:22:00.960 align:start position:0% logic with simple complex methods. There 01:22:00.960 --> 01:22:03.669 align:start position:0% logic with simple complex methods. There is<01:22:01.120> a<01:22:01.280> lot<01:22:01.440> of<01:22:01.600> detail<01:22:02.000> here.<01:22:03.120> The<01:22:03.360> general 01:22:03.669 --> 01:22:03.679 align:start position:0% is a lot of detail here. The general 01:22:03.679 --> 01:22:05.510 align:start position:0% is a lot of detail here. The general overview<01:22:04.080> of<01:22:04.239> this<01:22:04.480> detail<01:22:04.960> is<01:22:05.120> that<01:22:05.360> we 01:22:05.510 --> 01:22:05.520 align:start position:0% overview of this detail is that we 01:22:05.520 --> 01:22:07.430 align:start position:0% overview of this detail is that we should<01:22:05.679> make<01:22:05.840> our<01:22:06.080> code<01:22:06.400> readability<01:22:07.120> and 01:22:07.430 --> 01:22:07.440 align:start position:0% should make our code readability and 01:22:07.440 --> 01:22:10.149 align:start position:0% should make our code readability and maintainability<01:22:08.320> better.<01:22:09.520> As<01:22:09.760> soon<01:22:09.920> as<01:22:10.000> I 01:22:10.149 --> 01:22:10.159 align:start position:0% maintainability better. As soon as I 01:22:10.159 --> 01:22:12.149 align:start position:0% maintainability better. As soon as I improve<01:22:10.560> this,<01:22:11.120> we<01:22:11.440> start<01:22:11.600> getting<01:22:11.920> our 01:22:12.149 --> 01:22:12.159 align:start position:0% improve this, we start getting our 01:22:12.159 --> 01:22:14.950 align:start position:0% improve this, we start getting our response.<01:22:13.440> We<01:22:13.679> can<01:22:13.840> directly<01:22:14.320> include<01:22:14.719> this 01:22:14.950 --> 01:22:14.960 align:start position:0% response. We can directly include this 01:22:14.960 --> 01:22:17.590 align:start position:0% response. We can directly include this response.<01:22:16.400> First,<01:22:16.800> it<01:22:17.040> will<01:22:17.120> look<01:22:17.280> at<01:22:17.440> the 01:22:17.590 --> 01:22:17.600 align:start position:0% response. First, it will look at the 01:22:17.600 --> 01:22:20.870 align:start position:0% response. First, it will look at the current<01:22:17.840> state.<01:22:19.040> The<01:22:19.280> main<01:22:19.600> refactor<01:22:20.159> target 01:22:20.870 --> 01:22:20.880 align:start position:0% current state. The main refactor target 01:22:20.880 --> 01:22:23.350 align:start position:0% current state. The main refactor target is<01:22:21.120> that<01:22:21.280> we<01:22:21.520> will<01:22:21.679> slightly<01:22:22.080> change<01:22:22.400> the<01:22:22.639> HTML 01:22:23.350 --> 01:22:23.360 align:start position:0% is that we will slightly change the HTML 01:22:23.360 --> 01:22:26.550 align:start position:0% is that we will slightly change the HTML file.<01:22:24.800> First<01:22:25.040> of<01:22:25.199> all,<01:22:25.679> we<01:22:25.920> will<01:22:26.080> include<01:22:26.400> the 01:22:26.550 --> 01:22:26.560 align:start position:0% file. First of all, we will include the 01:22:26.560 --> 01:22:29.750 align:start position:0% file. First of all, we will include the keyboard<01:22:27.040> handling.<01:22:28.480> After<01:22:28.800> that,<01:22:29.440> we<01:22:29.600> will 01:22:29.750 --> 01:22:29.760 align:start position:0% keyboard handling. After that, we will 01:22:29.760 --> 01:22:33.189 align:start position:0% keyboard handling. After that, we will see<01:22:30.000> multiple<01:22:30.480> changes<01:22:30.800> in<01:22:31.040> this<01:22:31.199> HTML<01:22:31.920> file. 01:22:33.189 --> 01:22:33.199 align:start position:0% see multiple changes in this HTML file. 01:22:33.199 --> 01:22:35.270 align:start position:0% see multiple changes in this HTML file. If<01:22:33.360> we<01:22:33.600> want<01:22:33.679> to<01:22:33.840> review<01:22:34.159> it,<01:22:34.639> our<01:22:34.960> changes 01:22:35.270 --> 01:22:35.280 align:start position:0% If we want to review it, our changes 01:22:35.280 --> 01:22:36.950 align:start position:0% If we want to review it, our changes will<01:22:35.600> automatically<01:22:36.159> appear<01:22:36.560> wherever 01:22:36.950 --> 01:22:36.960 align:start position:0% will automatically appear wherever 01:22:36.960 --> 01:22:39.510 align:start position:0% will automatically appear wherever changes<01:22:37.360> are<01:22:37.520> being<01:22:37.679> made<01:22:37.920> in<01:22:38.080> our<01:22:38.320> file. 01:22:39.510 --> 01:22:39.520 align:start position:0% changes are being made in our file. 01:22:39.520 --> 01:22:41.270 align:start position:0% changes are being made in our file. You<01:22:39.760> will<01:22:39.920> see<01:22:40.000> that<01:22:40.239> the<01:22:40.400> refactor<01:22:40.880> is<01:22:41.120> done 01:22:41.270 --> 01:22:41.280 align:start position:0% You will see that the refactor is done 01:22:41.280 --> 01:22:44.629 align:start position:0% You will see that the refactor is done in<01:22:41.600> one<01:22:41.920> focused<01:22:42.480> pass.<01:22:43.600> I<01:22:43.920> am<01:22:44.080> validating 01:22:44.629 --> 01:22:44.639 align:start position:0% in one focused pass. I am validating 01:22:44.639 --> 01:22:47.430 align:start position:0% in one focused pass. I am validating both<01:22:44.960> sides.<01:22:45.360> Now,<01:22:46.320> Python<01:22:46.800> behavior<01:22:47.199> should 01:22:47.430 --> 01:22:47.440 align:start position:0% both sides. Now, Python behavior should 01:22:47.440 --> 01:22:50.229 align:start position:0% both sides. Now, Python behavior should still<01:22:47.760> pass<01:22:48.400> and<01:22:48.639> the<01:22:48.880> HTML<01:22:49.600> script<01:22:49.920> should 01:22:50.229 --> 01:22:50.239 align:start position:0% still pass and the HTML script should 01:22:50.239 --> 01:22:51.910 align:start position:0% still pass and the HTML script should still<01:22:50.480> calculate<01:22:50.960> and<01:22:51.280> respond<01:22:51.600> to<01:22:51.760> the 01:22:51.910 --> 01:22:51.920 align:start position:0% still calculate and respond to the 01:22:51.920 --> 01:22:54.229 align:start position:0% still calculate and respond to the button<01:22:52.159> and<01:22:52.400> keyboard<01:22:52.800> actions.<01:22:53.600> Here,<01:22:53.920> our 01:22:54.229 --> 01:22:54.239 align:start position:0% button and keyboard actions. Here, our 01:22:54.239 --> 01:22:57.189 align:start position:0% button and keyboard actions. Here, our checks<01:22:54.560> have<01:22:54.719> passed.<01:22:56.080> Now,<01:22:56.400> if<01:22:56.639> we<01:22:56.800> reload 01:22:57.189 --> 01:22:57.199 align:start position:0% checks have passed. Now, if we reload 01:22:57.199 --> 01:22:59.669 align:start position:0% checks have passed. Now, if we reload our<01:22:57.520> calculator,<01:22:58.560> many<01:22:58.960> changes<01:22:59.360> will<01:22:59.600> be 01:22:59.669 --> 01:22:59.679 align:start position:0% our calculator, many changes will be 01:22:59.679 --> 01:23:02.629 align:start position:0% our calculator, many changes will be included<01:23:00.080> in<01:23:00.320> our<01:23:00.480> calculator. 01:23:02.629 --> 01:23:02.639 align:start position:0% included in our calculator. 01:23:02.639 --> 01:23:04.629 align:start position:0% included in our calculator. Now,<01:23:02.880> we<01:23:03.040> have<01:23:03.280> another<01:23:03.679> very<01:23:04.159> important 01:23:04.629 --> 01:23:04.639 align:start position:0% Now, we have another very important 01:23:04.639 --> 01:23:07.430 align:start position:0% Now, we have another very important thing.<01:23:05.679> It<01:23:05.920> is<01:23:06.080> not<01:23:06.320> just<01:23:06.639> doing<01:23:06.880> a<01:23:07.120> simple 01:23:07.430 --> 01:23:07.440 align:start position:0% thing. It is not just doing a simple 01:23:07.440 --> 01:23:11.750 align:start position:0% thing. It is not just doing a simple check.<01:23:08.480> It<01:23:08.800> also<01:23:09.120> performed<01:23:09.600> a<01:23:09.840> Python<01:23:10.320> check. 01:23:11.750 --> 01:23:11.760 align:start position:0% check. It also performed a Python check. 01:23:11.760 --> 01:23:13.990 align:start position:0% check. It also performed a Python check. If<01:23:11.920> I<01:23:12.080> show<01:23:12.239> you<01:23:12.400> the<01:23:12.639> working<01:23:13.520> after<01:23:13.840> the 01:23:13.990 --> 01:23:14.000 align:start position:0% If I show you the working after the 01:23:14.000 --> 01:23:16.950 align:start position:0% If I show you the working after the Python<01:23:14.400> check,<01:23:14.880> it<01:23:15.199> also<01:23:15.520> included<01:23:16.159> HTML 01:23:16.950 --> 01:23:16.960 align:start position:0% Python check, it also included HTML 01:23:16.960 --> 01:23:20.950 align:start position:0% Python check, it also included HTML behavior<01:23:17.440> checks.<01:23:18.880> The<01:23:19.199> refactored<01:23:19.920> HTML<01:23:20.719> is 01:23:20.950 --> 01:23:20.960 align:start position:0% behavior checks. The refactored HTML is 01:23:20.960 --> 01:23:25.830 align:start position:0% behavior checks. The refactored HTML is built<01:23:21.280> here.<01:23:22.320> It<01:23:22.560> has<01:23:22.800> only<01:23:23.760> 123<01:23:24.320> lines.<01:23:25.440> I<01:23:25.679> can 01:23:25.830 --> 01:23:25.840 align:start position:0% built here. It has only 123 lines. I can 01:23:25.840 --> 01:23:28.149 align:start position:0% built here. It has only 123 lines. I can say<01:23:26.000> that<01:23:26.159> our<01:23:26.400> workability<01:23:27.120> is<01:23:27.360> much<01:23:27.679> easier. 01:23:28.149 --> 01:23:28.159 align:start position:0% say that our workability is much easier. 01:23:28.159 --> 01:23:31.430 align:start position:0% say that our workability is much easier. Now,<01:23:29.520> if<01:23:29.760> we<01:23:29.840> look<01:23:30.000> at<01:23:30.080> the<01:23:30.239> code<01:23:30.480> review,<01:23:31.199> it 01:23:31.430 --> 01:23:31.440 align:start position:0% Now, if we look at the code review, it 01:23:31.440 --> 01:23:34.070 align:start position:0% Now, if we look at the code review, it changed<01:23:31.840> many<01:23:32.159> lines<01:23:32.480> in<01:23:32.719> the<01:23:32.880> code.<01:23:33.920> For 01:23:34.070 --> 01:23:34.080 align:start position:0% changed many lines in the code. For 01:23:34.080 --> 01:23:37.510 align:start position:0% changed many lines in the code. For example,<01:23:35.120> instead<01:23:35.440> of<01:23:35.679> display<01:23:36.159> value<01:23:36.639> zero, 01:23:37.510 --> 01:23:37.520 align:start position:0% example, instead of display value zero, 01:23:37.520 --> 01:23:39.350 align:start position:0% example, instead of display value zero, it<01:23:37.679> has<01:23:37.840> set<01:23:38.080> the<01:23:38.239> display<01:23:38.560> value<01:23:38.960> to<01:23:39.120> the 01:23:39.350 --> 01:23:39.360 align:start position:0% it has set the display value to the 01:23:39.360 --> 01:23:41.270 align:start position:0% it has set the display value to the default<01:23:39.760> value. 01:23:41.270 --> 01:23:41.280 align:start position:0% default value. 01:23:41.280 --> 01:23:43.669 align:start position:0% default value. Overall,<01:23:42.000> it<01:23:42.239> showed<01:23:42.480> our<01:23:42.719> functionality<01:23:43.440> in 01:23:43.669 --> 01:23:43.679 align:start position:0% Overall, it showed our functionality in 01:23:43.679 --> 01:23:46.390 align:start position:0% Overall, it showed our functionality in depth.<01:23:44.719> It<01:23:45.040> directly<01:23:45.520> changed<01:23:45.840> the<01:23:46.159> error 01:23:46.390 --> 01:23:46.400 align:start position:0% depth. It directly changed the error 01:23:46.400 --> 01:23:49.510 align:start position:0% depth. It directly changed the error coming<01:23:46.639> in<01:23:46.880> the<01:23:47.040> display<01:23:47.440> into<01:23:47.840> show<01:23:48.320> error. 01:23:49.510 --> 01:23:49.520 align:start position:0% coming in the display into show error. 01:23:49.520 --> 01:23:52.629 align:start position:0% coming in the display into show error. Here<01:23:49.840> too,<01:23:50.480> it<01:23:50.719> changed<01:23:51.440> set<01:23:51.760> display<01:23:52.320> error 01:23:52.629 --> 01:23:52.639 align:start position:0% Here too, it changed set display error 01:23:52.639 --> 01:23:56.310 align:start position:0% Here too, it changed set display error to<01:23:52.960> show<01:23:53.440> error.<01:23:54.639> In<01:23:54.960> simple<01:23:55.280> words,<01:23:56.080> it 01:23:56.310 --> 01:23:56.320 align:start position:0% to show error. In simple words, it 01:23:56.320 --> 01:23:58.709 align:start position:0% to show error. In simple words, it improved<01:23:56.800> our<01:23:57.040> code<01:23:57.360> maintainability<01:23:58.400> and 01:23:58.709 --> 01:23:58.719 align:start position:0% improved our code maintainability and 01:23:58.719 --> 01:24:01.189 align:start position:0% improved our code maintainability and nullified<01:23:59.360> the<01:23:59.679> error-causing<01:24:00.400> paths<01:24:00.800> on<01:24:01.040> a 01:24:01.189 --> 01:24:01.199 align:start position:0% nullified the error-causing paths on a 01:24:01.199 --> 01:24:04.310 align:start position:0% nullified the error-causing paths on a large<01:24:01.520> scale.<01:24:02.880> It<01:24:03.120> manipulated<01:24:03.679> the<01:24:04.000> errors 01:24:04.310 --> 01:24:04.320 align:start position:0% large scale. It manipulated the errors 01:24:04.320 --> 01:24:07.350 align:start position:0% large scale. It manipulated the errors into<01:24:04.560> the<01:24:04.719> show<01:24:05.199> error<01:24:05.440> function.<01:24:06.880> Exactly 01:24:07.350 --> 01:24:07.360 align:start position:0% into the show error function. Exactly 01:24:07.360 --> 01:24:09.750 align:start position:0% into the show error function. Exactly here<01:24:07.600> too<01:24:08.239> the<01:24:08.480> set<01:24:08.800> display<01:24:09.360> error<01:24:09.600> was 01:24:09.750 --> 01:24:09.760 align:start position:0% here too the set display error was 01:24:09.760 --> 01:24:13.350 align:start position:0% here too the set display error was changed<01:24:10.239> to<01:24:10.480> show<01:24:11.120> error.<01:24:12.480> This<01:24:12.719> means<01:24:13.120> in 01:24:13.350 --> 01:24:13.360 align:start position:0% changed to show error. This means in 01:24:13.360 --> 01:24:15.910 align:start position:0% changed to show error. This means in simple<01:24:13.679> words<01:24:14.480> our<01:24:14.719> code<01:24:15.120> maintainability 01:24:15.910 --> 01:24:15.920 align:start position:0% simple words our code maintainability 01:24:15.920 --> 01:24:18.870 align:start position:0% simple words our code maintainability has<01:24:16.159> improved.<01:24:17.520> It<01:24:17.760> has<01:24:17.920> removed<01:24:18.239> the<01:24:18.480> paths 01:24:18.870 --> 01:24:18.880 align:start position:0% has improved. It has removed the paths 01:24:18.880 --> 01:24:21.430 align:start position:0% has improved. It has removed the paths that<01:24:19.120> cause<01:24:19.520> errors<01:24:19.760> on<01:24:19.920> a<01:24:20.159> large<01:24:20.400> scale.<01:24:21.120> Next 01:24:21.430 --> 01:24:21.440 align:start position:0% that cause errors on a large scale. Next 01:24:21.440 --> 01:24:23.590 align:start position:0% that cause errors on a large scale. Next we<01:24:21.679> will<01:24:21.840> discuss<01:24:22.320> context<01:24:22.880> windows<01:24:23.280> and 01:24:23.590 --> 01:24:23.600 align:start position:0% we will discuss context windows and 01:24:23.600 --> 01:24:27.270 align:start position:0% we will discuss context windows and scope.<01:24:24.880> Context<01:24:25.360> window<01:24:25.760> is<01:24:25.920> a<01:24:26.159> new<01:24:26.320> topic. 01:24:27.270 --> 01:24:27.280 align:start position:0% scope. Context window is a new topic. 01:24:27.280 --> 01:24:29.910 align:start position:0% scope. Context window is a new topic. People<01:24:27.520> do<01:24:27.760> not<01:24:27.920> discuss<01:24:28.239> it<01:24:28.400> much.<01:24:29.440> I<01:24:29.679> will 01:24:29.910 --> 01:24:29.920 align:start position:0% People do not discuss it much. I will 01:24:29.920 --> 01:24:32.870 align:start position:0% People do not discuss it much. I will tell<01:24:30.000> you<01:24:30.159> what<01:24:30.400> a<01:24:30.560> context<01:24:31.040> window<01:24:31.440> is. 01:24:32.870 --> 01:24:32.880 align:start position:0% tell you what a context window is. 01:24:32.880 --> 01:24:35.590 align:start position:0% tell you what a context window is. A<01:24:33.199> context<01:24:33.679> window<01:24:34.000> is<01:24:34.239> the<01:24:34.480> maximum<01:24:35.040> text<01:24:35.360> an 01:24:35.590 --> 01:24:35.600 align:start position:0% A context window is the maximum text an 01:24:35.600 --> 01:24:39.110 align:start position:0% A context window is the maximum text an AI<01:24:36.080> model<01:24:36.400> can<01:24:36.560> hold<01:24:36.800> at<01:24:37.040> one<01:24:37.280> time.<01:24:38.560> It<01:24:38.800> works 01:24:39.110 --> 01:24:39.120 align:start position:0% AI model can hold at one time. It works 01:24:39.120 --> 01:24:42.310 align:start position:0% AI model can hold at one time. It works as<01:24:39.360> the<01:24:39.520> AI's<01:24:40.080> memory.<01:24:41.520> Everything<01:24:41.920> inside 01:24:42.310 --> 01:24:42.320 align:start position:0% as the AI's memory. Everything inside 01:24:42.320 --> 01:24:45.270 align:start position:0% as the AI's memory. Everything inside this<01:24:42.560> window<01:24:43.280> like<01:24:43.679> prompts,<01:24:44.400> history<01:24:45.040> or 01:24:45.270 --> 01:24:45.280 align:start position:0% this window like prompts, history or 01:24:45.280 --> 01:24:48.550 align:start position:0% this window like prompts, history or files<01:24:46.000> is<01:24:46.239> seen<01:24:46.480> by<01:24:46.719> the<01:24:46.880> model.<01:24:48.159> Before 01:24:48.550 --> 01:24:48.560 align:start position:0% files is seen by the model. Before 01:24:48.560 --> 01:24:50.470 align:start position:0% files is seen by the model. Before explaining<01:24:49.040> how<01:24:49.199> it<01:24:49.440> works,<01:24:49.840> I<01:24:50.080> will<01:24:50.239> give<01:24:50.320> you 01:24:50.470 --> 01:24:50.480 align:start position:0% explaining how it works, I will give you 01:24:50.480 --> 01:24:52.550 align:start position:0% explaining how it works, I will give you a<01:24:50.639> simple<01:24:50.960> example. 01:24:52.550 --> 01:24:52.560 align:start position:0% a simple example. 01:24:52.560 --> 01:24:55.030 align:start position:0% a simple example. For<01:24:52.719> a<01:24:52.960> simple<01:24:53.199> example,<01:24:54.080> I<01:24:54.239> will<01:24:54.400> go<01:24:54.480> to<01:24:54.639> chat 01:24:55.030 --> 01:24:55.040 align:start position:0% For a simple example, I will go to chat 01:24:55.040 --> 01:24:56.629 align:start position:0% For a simple example, I will go to chat GPT. 01:24:56.629 --> 01:24:56.639 align:start position:0% GPT. 01:24:56.639 --> 01:25:00.070 align:start position:0% GPT. First,<01:24:57.040> I<01:24:57.280> write<01:24:57.520> a<01:24:57.760> message<01:24:57.920> in<01:24:58.080> chat<01:24:58.400> GPT.<01:24:59.760> I 01:25:00.070 --> 01:25:00.080 align:start position:0% First, I write a message in chat GPT. I 01:25:00.080 --> 01:25:05.110 align:start position:0% First, I write a message in chat GPT. I say<01:25:01.120> hi,<01:25:01.679> I<01:25:02.000> want<01:25:02.080> to<01:25:02.239> work<01:25:02.480> with<01:25:02.719> AI<01:25:03.040> and<01:25:03.360> HTML. 01:25:05.110 --> 01:25:05.120 align:start position:0% say hi, I want to work with AI and HTML. 01:25:05.120 --> 01:25:07.510 align:start position:0% say hi, I want to work with AI and HTML. If<01:25:05.360> I<01:25:05.520> continue<01:25:05.920> this<01:25:06.159> conversation,<01:25:07.120> it<01:25:07.360> will 01:25:07.510 --> 01:25:07.520 align:start position:0% If I continue this conversation, it will 01:25:07.520 --> 01:25:10.149 align:start position:0% If I continue this conversation, it will write<01:25:07.679> the<01:25:07.920> code.<01:25:09.280> This<01:25:09.520> is<01:25:09.760> simple 01:25:10.149 --> 01:25:10.159 align:start position:0% write the code. This is simple 01:25:10.159 --> 01:25:14.149 align:start position:0% write the code. This is simple prompting.<01:25:11.600> We<01:25:11.840> get<01:25:12.000> our<01:25:12.239> answer<01:25:12.560> through<01:25:12.800> it. 01:25:14.149 --> 01:25:14.159 align:start position:0% prompting. We get our answer through it. 01:25:14.159 --> 01:25:17.030 align:start position:0% prompting. We get our answer through it. But<01:25:14.400> if<01:25:14.560> we<01:25:14.719> do<01:25:14.880> something<01:25:15.199> else,<01:25:16.400> if<01:25:16.639> we<01:25:16.800> give 01:25:17.030 --> 01:25:17.040 align:start position:0% But if we do something else, if we give 01:25:17.040 --> 01:25:20.070 align:start position:0% But if we do something else, if we give a<01:25:17.280> very<01:25:17.520> long<01:25:17.840> prompt<01:25:18.239> again<01:25:18.400> and<01:25:18.719> again,<01:25:19.840> you 01:25:20.070 --> 01:25:20.080 align:start position:0% a very long prompt again and again, you 01:25:20.080 --> 01:25:23.110 align:start position:0% a very long prompt again and again, you will<01:25:20.239> see<01:25:20.400> a<01:25:20.560> message.<01:25:21.840> The<01:25:22.159> message<01:25:22.480> says<01:25:22.880> it 01:25:23.110 --> 01:25:23.120 align:start position:0% will see a message. The message says it 01:25:23.120 --> 01:25:26.070 align:start position:0% will see a message. The message says it is<01:25:23.280> too<01:25:23.600> long.<01:25:24.880> Let<01:25:25.120> us<01:25:25.280> see<01:25:25.440> the<01:25:25.600> size<01:25:25.840> of<01:25:25.920> the 01:25:26.070 --> 01:25:26.080 align:start position:0% is too long. Let us see the size of the 01:25:26.080 --> 01:25:29.030 align:start position:0% is too long. Let us see the size of the context<01:25:26.560> window<01:25:26.800> in<01:25:26.960> chat<01:25:27.280> GPT.<01:25:28.560> I<01:25:28.880> will 01:25:29.030 --> 01:25:29.040 align:start position:0% context window in chat GPT. I will 01:25:29.040 --> 01:25:30.790 align:start position:0% context window in chat GPT. I will search<01:25:29.199> for<01:25:29.360> the<01:25:29.600> context<01:25:30.000> window<01:25:30.239> of<01:25:30.480> chat 01:25:30.790 --> 01:25:30.800 align:start position:0% search for the context window of chat 01:25:30.800 --> 01:25:33.750 align:start position:0% search for the context window of chat GPT.<01:25:32.239> It<01:25:32.480> will<01:25:32.560> show<01:25:32.800> the<01:25:32.960> context<01:25:33.360> window 01:25:33.750 --> 01:25:33.760 align:start position:0% GPT. It will show the context window 01:25:33.760 --> 01:25:38.229 align:start position:0% GPT. It will show the context window size.<01:25:35.120> Usually<01:25:35.600> the<01:25:35.840> model<01:25:36.080> has<01:25:36.239> a<01:25:37.199> 128,000 01:25:38.229 --> 01:25:38.239 align:start position:0% size. Usually the model has a 128,000 01:25:38.239 --> 01:25:42.070 align:start position:0% size. Usually the model has a 128,000 token<01:25:38.719> window.<01:25:39.920> This<01:25:40.159> means<01:25:40.400> it<01:25:40.639> takes<01:25:41.040> 96,000 01:25:42.070 --> 01:25:42.080 align:start position:0% token window. This means it takes 96,000 01:25:42.080 --> 01:25:47.189 align:start position:0% token window. This means it takes 96,000 words<01:25:42.719> or<01:25:43.120> 250<01:25:44.080> to<01:25:44.400> 300<01:25:44.880> pages<01:25:45.280> of<01:25:45.520> text.<01:25:46.960> I 01:25:47.189 --> 01:25:47.199 align:start position:0% words or 250 to 300 pages of text. I 01:25:47.199 --> 01:25:49.110 align:start position:0% words or 250 to 300 pages of text. I will<01:25:47.280> copy<01:25:47.600> this<01:25:47.840> text<01:25:48.080> and<01:25:48.320> paste<01:25:48.639> it<01:25:48.800> many 01:25:49.110 --> 01:25:49.120 align:start position:0% will copy this text and paste it many 01:25:49.120 --> 01:25:52.149 align:start position:0% will copy this text and paste it many times.<01:25:50.560> I<01:25:50.800> will<01:25:50.960> do<01:25:51.120> this<01:25:51.360> until<01:25:51.600> the<01:25:51.840> prompt 01:25:52.149 --> 01:25:52.159 align:start position:0% times. I will do this until the prompt 01:25:52.159 --> 01:25:55.830 align:start position:0% times. I will do this until the prompt becomes<01:25:52.480> too<01:25:52.719> long.<01:25:53.920> I<01:25:54.159> will<01:25:54.320> copy<01:25:54.639> it<01:25:55.360> and<01:25:55.679> go 01:25:55.830 --> 01:25:55.840 align:start position:0% becomes too long. I will copy it and go 01:25:55.840 --> 01:25:58.149 align:start position:0% becomes too long. I will copy it and go to<01:25:56.000> a<01:25:56.159> word<01:25:56.400> counter<01:25:56.880> website. 01:25:58.149 --> 01:25:58.159 align:start position:0% to a word counter website. 01:25:58.159 --> 01:26:00.790 align:start position:0% to a word counter website. It<01:25:58.400> is<01:25:58.480> a<01:25:58.719> famous<01:25:59.040> word<01:25:59.280> counter.<01:26:00.400> When<01:26:00.639> I 01:26:00.790 --> 01:26:00.800 align:start position:0% It is a famous word counter. When I 01:26:00.800 --> 01:26:02.950 align:start position:0% It is a famous word counter. When I paste<01:26:01.040> the<01:26:01.199> words<01:26:01.520> here,<01:26:02.159> you<01:26:02.400> will<01:26:02.560> see<01:26:02.639> the 01:26:02.950 --> 01:26:02.960 align:start position:0% paste the words here, you will see the 01:26:02.960 --> 01:26:05.270 align:start position:0% paste the words here, you will see the website<01:26:03.280> becomes<01:26:03.679> slow. 01:26:05.270 --> 01:26:05.280 align:start position:0% website becomes slow. 01:26:05.280 --> 01:26:08.870 align:start position:0% website becomes slow. This<01:26:05.440> is<01:26:05.600> because<01:26:05.920> there<01:26:06.159> are<01:26:06.400> 9,776 01:26:08.870 --> 01:26:08.880 align:start position:0% This is because there are 9,776 01:26:08.880 --> 01:26:11.350 align:start position:0% This is because there are 9,776 words<01:26:09.199> in<01:26:09.360> total.<01:26:10.480> We<01:26:10.719> put<01:26:10.880> this<01:26:11.040> in<01:26:11.199> our 01:26:11.350 --> 01:26:11.360 align:start position:0% words in total. We put this in our 01:26:11.360 --> 01:26:15.990 align:start position:0% words in total. We put this in our prompt.<01:26:12.719> It<01:26:12.960> has<01:26:13.280> 76,000<01:26:14.480> characters. 01:26:15.990 --> 01:26:16.000 align:start position:0% prompt. It has 76,000 characters. 01:26:16.000 --> 01:26:18.950 align:start position:0% prompt. It has 76,000 characters. Now<01:26:16.320> suppose<01:26:16.639> I<01:26:16.880> paste<01:26:17.120> the<01:26:17.360> last<01:26:17.520> text<01:26:17.920> here. 01:26:18.950 --> 01:26:18.960 align:start position:0% Now suppose I paste the last text here. 01:26:18.960 --> 01:26:21.669 align:start position:0% Now suppose I paste the last text here. You<01:26:19.199> will<01:26:19.280> see<01:26:19.440> a<01:26:19.679> message.<01:26:20.800> It<01:26:21.040> says<01:26:21.280> the<01:26:21.440> long 01:26:21.669 --> 01:26:21.679 align:start position:0% You will see a message. It says the long 01:26:21.679 --> 01:26:24.629 align:start position:0% You will see a message. It says the long text<01:26:22.000> is<01:26:22.159> added<01:26:22.400> as<01:26:22.639> a<01:26:22.800> file.<01:26:24.000> The<01:26:24.239> text<01:26:24.480> will 01:26:24.629 --> 01:26:24.639 align:start position:0% text is added as a file. The text will 01:26:24.639 --> 01:26:27.510 align:start position:0% text is added as a file. The text will show<01:26:24.800> up<01:26:25.040> here.<01:26:26.159> I<01:26:26.480> will<01:26:26.639> write<01:26:26.800> that<01:26:27.040> if<01:26:27.199> I<01:26:27.360> put 01:26:27.510 --> 01:26:27.520 align:start position:0% show up here. I will write that if I put 01:26:27.520 --> 01:26:29.510 align:start position:0% show up here. I will write that if I put this<01:26:27.679> file<01:26:27.920> in<01:26:28.080> the<01:26:28.159> chat,<01:26:28.560> it<01:26:28.800> cannot<01:26:29.120> process 01:26:29.510 --> 01:26:29.520 align:start position:0% this file in the chat, it cannot process 01:26:29.520 --> 01:26:33.110 align:start position:0% this file in the chat, it cannot process it.<01:26:30.239> The<01:26:30.480> message<01:26:30.800> is<01:26:31.040> too<01:26:31.280> long.<01:26:32.639> We<01:26:32.880> want<01:26:33.040> to 01:26:33.110 --> 01:26:33.120 align:start position:0% it. The message is too long. We want to 01:26:33.120 --> 01:26:36.550 align:start position:0% it. The message is too long. We want to see<01:26:33.280> the<01:26:33.520> context<01:26:33.920> window<01:26:34.239> size<01:26:34.480> of<01:26:34.639> chat<01:26:34.960> GPT. 01:26:36.550 --> 01:26:36.560 align:start position:0% see the context window size of chat GPT. 01:26:36.560 --> 01:26:39.189 align:start position:0% see the context window size of chat GPT. It<01:26:36.800> will<01:26:36.960> take<01:26:37.199> time.<01:26:38.320> You<01:26:38.480> will<01:26:38.639> see<01:26:38.800> that<01:26:38.960> the 01:26:39.189 --> 01:26:39.199 align:start position:0% It will take time. You will see that the 01:26:39.199 --> 01:26:41.830 align:start position:0% It will take time. You will see that the context<01:26:39.679> window<01:26:40.000> depends<01:26:40.400> on<01:26:40.560> the<01:26:40.719> model. 01:26:41.830 --> 01:26:41.840 align:start position:0% context window depends on the model. 01:26:41.840 --> 01:26:44.229 align:start position:0% context window depends on the model. Open<01:26:42.239> AI<01:26:42.719> does<01:26:42.960> not<01:26:43.120> always<01:26:43.440> show<01:26:43.600> the<01:26:43.920> exact 01:26:44.229 --> 01:26:44.239 align:start position:0% Open AI does not always show the exact 01:26:44.239 --> 01:26:46.709 align:start position:0% Open AI does not always show the exact limit.<01:26:45.280> But<01:26:45.360> if<01:26:45.600> you<01:26:45.679> see<01:26:45.840> the<01:26:46.080> message,<01:26:46.480> it 01:26:46.709 --> 01:26:46.719 align:start position:0% limit. But if you see the message, it 01:26:46.719 --> 01:26:48.550 align:start position:0% limit. But if you see the message, it means<01:26:46.880> the<01:26:47.120> text<01:26:47.360> is<01:26:47.600> too<01:26:47.840> long<01:26:48.080> for<01:26:48.320> one 01:26:48.550 --> 01:26:48.560 align:start position:0% means the text is too long for one 01:26:48.560 --> 01:26:52.790 align:start position:0% means the text is too long for one input,<01:26:49.679> the<01:26:49.920> file<01:26:50.239> is<01:26:50.480> too<01:26:50.719> big,<01:26:51.920> or<01:26:52.239> the<01:26:52.480> user 01:26:52.790 --> 01:26:52.800 align:start position:0% input, the file is too big, or the user 01:26:52.800 --> 01:26:55.430 align:start position:0% input, the file is too big, or the user interface<01:26:53.280> has<01:26:53.520> strict<01:26:53.840> limits. 01:26:55.430 --> 01:26:55.440 align:start position:0% interface has strict limits. 01:26:55.440 --> 01:26:57.910 align:start position:0% interface has strict limits. If<01:26:55.679> we<01:26:55.840> use<01:26:56.080> fewer<01:26:56.480> words,<01:26:57.120> we<01:26:57.280> will<01:26:57.440> get<01:26:57.600> our 01:26:57.910 --> 01:26:57.920 align:start position:0% If we use fewer words, we will get our 01:26:57.920 --> 01:26:59.430 align:start position:0% If we use fewer words, we will get our answer. 01:26:59.430 --> 01:26:59.440 align:start position:0% answer. 01:26:59.440 --> 01:27:01.350 align:start position:0% answer. In<01:26:59.679> the<01:26:59.840> same<01:27:00.000> way,<01:27:00.239> when<01:27:00.400> we<01:27:00.560> go<01:27:00.639> to<01:27:00.880> codeex, 01:27:01.350 --> 01:27:01.360 align:start position:0% In the same way, when we go to codeex, 01:27:01.360 --> 01:27:04.229 align:start position:0% In the same way, when we go to codeex, we<01:27:01.600> can<01:27:01.679> see<01:27:01.840> limits.<01:27:03.199> In<01:27:03.440> the<01:27:03.600> new<01:27:03.760> chat,<01:27:04.080> we 01:27:04.229 --> 01:27:04.239 align:start position:0% we can see limits. In the new chat, we 01:27:04.239 --> 01:27:06.870 align:start position:0% we can see limits. In the new chat, we have<01:27:04.400> limits.<01:27:05.679> Wait<01:27:05.920> a<01:27:06.159> minute.<01:27:06.320> I<01:27:06.560> will<01:27:06.719> open 01:27:06.870 --> 01:27:06.880 align:start position:0% have limits. Wait a minute. I will open 01:27:06.880 --> 01:27:09.830 align:start position:0% have limits. Wait a minute. I will open it<01:27:07.120> here.<01:27:08.320> We<01:27:08.560> know<01:27:08.719> that<01:27:08.960> codeex<01:27:09.520> has<01:27:09.679> some 01:27:09.830 --> 01:27:09.840 align:start position:0% it here. We know that codeex has some 01:27:09.840 --> 01:27:12.709 align:start position:0% it here. We know that codeex has some limits.<01:27:11.040> Even<01:27:11.280> if<01:27:11.440> we<01:27:11.600> add<01:27:11.840> many<01:27:12.159> images, 01:27:12.709 --> 01:27:12.719 align:start position:0% limits. Even if we add many images, 01:27:12.719 --> 01:27:14.390 align:start position:0% limits. Even if we add many images, files,<01:27:13.120> and<01:27:13.360> documents,<01:27:13.840> there<01:27:14.000> are<01:27:14.159> still 01:27:14.390 --> 01:27:14.400 align:start position:0% files, and documents, there are still 01:27:14.400 --> 01:27:18.149 align:start position:0% files, and documents, there are still limits.<01:27:15.840> In<01:27:16.080> real<01:27:16.400> business<01:27:16.800> projects,<01:27:17.840> apps 01:27:18.149 --> 01:27:18.159 align:start position:0% limits. In real business projects, apps 01:27:18.159 --> 01:27:20.390 align:start position:0% limits. In real business projects, apps have<01:27:18.480> thousands<01:27:18.960> of<01:27:19.120> files<01:27:19.520> and<01:27:19.840> millions<01:27:20.239> of 01:27:20.390 --> 01:27:20.400 align:start position:0% have thousands of files and millions of 01:27:20.400 --> 01:27:23.990 align:start position:0% have thousands of files and millions of lines<01:27:20.719> of<01:27:20.880> code.<01:27:22.239> No<01:27:22.560> AI<01:27:23.120> can<01:27:23.360> read<01:27:23.600> all<01:27:23.760> the 01:27:23.990 --> 01:27:24.000 align:start position:0% lines of code. No AI can read all the 01:27:24.000 --> 01:27:26.950 align:start position:0% lines of code. No AI can read all the code<01:27:24.159> at<01:27:24.400> once.<01:27:25.679> Developers<01:27:26.320> must<01:27:26.639> help 01:27:26.950 --> 01:27:26.960 align:start position:0% code at once. Developers must help 01:27:26.960 --> 01:27:30.149 align:start position:0% code at once. Developers must help codecs<01:27:27.520> focus<01:27:27.840> on<01:27:28.080> important<01:27:28.639> information. 01:27:30.149 --> 01:27:30.159 align:start position:0% codecs focus on important information. 01:27:30.159 --> 01:27:32.950 align:start position:0% codecs focus on important information. Scope<01:27:30.560> sets<01:27:30.800> the<01:27:31.040> limits<01:27:31.199> of<01:27:31.360> a<01:27:31.600> task.<01:27:32.719> It 01:27:32.950 --> 01:27:32.960 align:start position:0% Scope sets the limits of a task. It 01:27:32.960 --> 01:27:36.470 align:start position:0% Scope sets the limits of a task. It includes<01:27:33.360> files,<01:27:34.159> modules,<01:27:34.639> and<01:27:34.880> features. 01:27:36.470 --> 01:27:36.480 align:start position:0% includes files, modules, and features. 01:27:36.480 --> 01:27:38.310 align:start position:0% includes files, modules, and features. Setting<01:27:36.800> the<01:27:36.960> right<01:27:37.199> scope<01:27:37.600> stops<01:27:38.000> bad 01:27:38.310 --> 01:27:38.320 align:start position:0% Setting the right scope stops bad 01:27:38.320 --> 01:27:41.270 align:start position:0% Setting the right scope stops bad changes.<01:27:39.520> It<01:27:39.760> helps<01:27:40.080> codeex<01:27:40.639> focus<01:27:40.880> on<01:27:41.040> the 01:27:41.270 --> 01:27:41.280 align:start position:0% changes. It helps codeex focus on the 01:27:41.280 --> 01:27:42.950 align:start position:0% changes. It helps codeex focus on the right<01:27:41.440> parts. 01:27:42.950 --> 01:27:42.960 align:start position:0% right parts. 01:27:42.960 --> 01:27:45.750 align:start position:0% right parts. Now<01:27:43.280> I<01:27:43.440> will<01:27:43.600> tell<01:27:43.760> you<01:27:44.000> directly.<01:27:45.280> Suppose<01:27:45.600> we 01:27:45.750 --> 01:27:45.760 align:start position:0% Now I will tell you directly. Suppose we 01:27:45.760 --> 01:27:48.550 align:start position:0% Now I will tell you directly. Suppose we get<01:27:45.920> an<01:27:46.159> answer.<01:27:47.280> How<01:27:47.440> will<01:27:47.600> a<01:27:47.840> full<01:27:48.080> developer 01:27:48.550 --> 01:27:48.560 align:start position:0% get an answer. How will a full developer 01:27:48.560 --> 01:27:51.430 align:start position:0% get an answer. How will a full developer work?<01:27:49.760> For<01:27:49.920> example,<01:27:50.719> we<01:27:50.960> will<01:27:51.120> take<01:27:51.280> an 01:27:51.430 --> 01:27:51.440 align:start position:0% work? For example, we will take an 01:27:51.440 --> 01:27:54.390 align:start position:0% work? For example, we will take an e-commerce<01:27:52.080> store.<01:27:53.280> In<01:27:53.520> our<01:27:53.760> example,<01:27:54.159> we 01:27:54.390 --> 01:27:54.400 align:start position:0% e-commerce store. In our example, we 01:27:54.400 --> 01:27:56.870 align:start position:0% e-commerce store. In our example, we have<01:27:54.480> an<01:27:54.639> e-commerce<01:27:55.199> store.<01:27:56.239> A<01:27:56.480> developer 01:27:56.870 --> 01:27:56.880 align:start position:0% have an e-commerce store. A developer 01:27:56.880 --> 01:27:58.870 align:start position:0% have an e-commerce store. A developer wants<01:27:57.120> to<01:27:57.199> add<01:27:57.360> a<01:27:57.520> discount<01:27:57.920> box<01:27:58.159> to<01:27:58.320> a<01:27:58.560> product 01:27:58.870 --> 01:27:58.880 align:start position:0% wants to add a discount box to a product 01:27:58.880 --> 01:28:01.590 align:start position:0% wants to add a discount box to a product page.<01:28:00.080> The<01:28:00.320> developer<01:28:00.719> does<01:28:00.960> not<01:28:01.120> share<01:28:01.440> all 01:28:01.590 --> 01:28:01.600 align:start position:0% page. The developer does not share all 01:28:01.600 --> 01:28:04.390 align:start position:0% page. The developer does not share all the<01:28:01.760> code<01:28:02.000> with<01:28:02.159> Codeex.<01:28:03.440> He<01:28:03.679> only<01:28:03.920> shares<01:28:04.239> the 01:28:04.390 --> 01:28:04.400 align:start position:0% the code with Codeex. He only shares the 01:28:04.400 --> 01:28:07.189 align:start position:0% the code with Codeex. He only shares the product<01:28:04.719> model,<01:28:05.440> service,<01:28:06.239> controller, 01:28:07.189 --> 01:28:07.199 align:start position:0% product model, service, controller, 01:28:07.199 --> 01:28:09.590 align:start position:0% product model, service, controller, form,<01:28:07.760> and<01:28:08.080> tests. 01:28:09.590 --> 01:28:09.600 align:start position:0% form, and tests. 01:28:09.600 --> 01:28:11.990 align:start position:0% form, and tests. This<01:28:09.840> limits<01:28:10.239> the<01:28:10.480> context.<01:28:11.280> Codeex<01:28:11.840> can 01:28:11.990 --> 01:28:12.000 align:start position:0% This limits the context. Codeex can 01:28:12.000 --> 01:28:14.390 align:start position:0% This limits the context. Codeex can focus<01:28:12.239> on<01:28:12.400> the<01:28:12.560> updates.<01:28:13.360> It<01:28:13.600> will<01:28:13.840> not<01:28:14.159> make 01:28:14.390 --> 01:28:14.400 align:start position:0% focus on the updates. It will not make 01:28:14.400 --> 01:28:17.430 align:start position:0% focus on the updates. It will not make bad<01:28:14.719> changes<01:28:15.199> in<01:28:15.520> other<01:28:15.760> places. 01:28:17.430 --> 01:28:17.440 align:start position:0% bad changes in other places. 01:28:17.440 --> 01:28:20.229 align:start position:0% bad changes in other places. Where<01:28:17.679> do<01:28:17.840> we<01:28:18.080> use<01:28:18.239> this?<01:28:19.600> When<01:28:19.840> we<01:28:20.000> make 01:28:20.229 --> 01:28:20.239 align:start position:0% Where do we use this? When we make 01:28:20.239 --> 01:28:22.950 align:start position:0% Where do we use this? When we make changes,<01:28:20.800> this<01:28:21.040> is<01:28:21.199> very<01:28:21.520> helpful.<01:28:22.560> We<01:28:22.800> can 01:28:22.950 --> 01:28:22.960 align:start position:0% changes, this is very helpful. We can 01:28:22.960 --> 01:28:25.669 align:start position:0% changes, this is very helpful. We can modify<01:28:23.360> things<01:28:23.679> easily.<01:28:24.800> You<01:28:25.040> will<01:28:25.199> see<01:28:25.440> two 01:28:25.669 --> 01:28:25.679 align:start position:0% modify things easily. You will see two 01:28:25.679 --> 01:28:28.629 align:start position:0% modify things easily. You will see two or<01:28:25.920> three<01:28:26.239> options<01:28:26.639> here.<01:28:27.520> We<01:28:27.760> can<01:28:27.920> open<01:28:28.159> it<01:28:28.320> in 01:28:28.629 --> 01:28:28.639 align:start position:0% or three options here. We can open it in 01:28:28.639 --> 01:28:31.830 align:start position:0% or three options here. We can open it in VS<01:28:29.120> Code.<01:28:30.239> We<01:28:30.480> have<01:28:30.560> a<01:28:30.800> full<01:28:31.120> Metabrains 01:28:31.830 --> 01:28:31.840 align:start position:0% VS Code. We have a full Metabrains 01:28:31.840 --> 01:28:35.590 align:start position:0% VS Code. We have a full Metabrains project.<01:28:32.239> Here<01:28:33.120> it<01:28:33.440> has<01:28:33.600> all<01:28:33.760> our<01:28:34.000> files.<01:28:35.360> We 01:28:35.590 --> 01:28:35.600 align:start position:0% project. Here it has all our files. We 01:28:35.600 --> 01:28:38.629 align:start position:0% project. Here it has all our files. We can<01:28:35.760> run<01:28:35.920> the<01:28:36.159> index<01:28:36.560> file.<01:28:36.880> Here<01:28:38.239> on<01:28:38.480> the 01:28:38.629 --> 01:28:38.639 align:start position:0% can run the index file. Here on the 01:28:38.639 --> 01:28:41.590 align:start position:0% can run the index file. Here on the side,<01:28:38.880> we<01:28:39.120> have<01:28:39.199> our<01:28:39.440> chat.<01:28:40.639> Our<01:28:40.880> codeex<01:28:41.360> is 01:28:41.590 --> 01:28:41.600 align:start position:0% side, we have our chat. Our codeex is 01:28:41.600 --> 01:28:43.750 align:start position:0% side, we have our chat. Our codeex is also<01:28:41.920> running<01:28:42.239> directly. 01:28:43.750 --> 01:28:43.760 align:start position:0% also running directly. 01:28:43.760 --> 01:28:45.830 align:start position:0% also running directly. Besides<01:28:44.239> codeex,<01:28:44.880> we<01:28:45.040> have<01:28:45.199> an<01:28:45.360> agents 01:28:45.830 --> 01:28:45.840 align:start position:0% Besides codeex, we have an agents 01:28:45.840 --> 01:28:48.950 align:start position:0% Besides codeex, we have an agents option.<01:28:47.120> We<01:28:47.360> can<01:28:47.440> use<01:28:47.679> agents<01:28:48.159> to<01:28:48.400> do<01:28:48.480> our<01:28:48.719> work 01:28:48.950 --> 01:28:48.960 align:start position:0% option. We can use agents to do our work 01:28:48.960 --> 01:28:50.950 align:start position:0% option. We can use agents to do our work directly. 01:28:50.950 --> 01:28:50.960 align:start position:0% directly. 01:28:50.960 --> 01:28:53.910 align:start position:0% directly. Now<01:28:51.120> we<01:28:51.360> will<01:28:51.520> verify<01:28:51.920> our<01:28:52.159> GitHub<01:28:52.719> account. 01:28:53.910 --> 01:28:53.920 align:start position:0% Now we will verify our GitHub account. 01:28:53.920 --> 01:28:55.510 align:start position:0% Now we will verify our GitHub account. Do<01:28:54.159> you<01:28:54.320> remember<01:28:54.480> how<01:28:54.639> I<01:28:54.880> did<01:28:55.040> GitHub 01:28:55.510 --> 01:28:55.520 align:start position:0% Do you remember how I did GitHub 01:28:55.520 --> 01:28:57.430 align:start position:0% Do you remember how I did GitHub authentication? 01:28:57.430 --> 01:28:57.440 align:start position:0% authentication? 01:28:57.440 --> 01:29:00.950 align:start position:0% authentication? We<01:28:57.679> will<01:28:57.840> authorize<01:28:58.560> VS<01:28:58.960> Code<01:28:59.360> directly. 01:29:00.950 --> 01:29:00.960 align:start position:0% We will authorize VS Code directly. 01:29:00.960 --> 01:29:03.110 align:start position:0% We will authorize VS Code directly. Our<01:29:01.280> workflow<01:29:01.760> and<01:29:02.080> personal<01:29:02.480> details<01:29:02.880> will 01:29:03.110 --> 01:29:03.120 align:start position:0% Our workflow and personal details will 01:29:03.120 --> 01:29:06.390 align:start position:0% Our workflow and personal details will be<01:29:03.280> added<01:29:03.520> here.<01:29:04.880> This<01:29:05.120> works<01:29:05.440> for<01:29:05.679> public<01:29:06.000> and 01:29:06.390 --> 01:29:06.400 align:start position:0% be added here. This works for public and 01:29:06.400 --> 01:29:08.310 align:start position:0% be added here. This works for public and private<01:29:06.800> projects. 01:29:08.310 --> 01:29:08.320 align:start position:0% private projects. 01:29:08.320 --> 01:29:10.790 align:start position:0% private projects. We<01:29:08.560> can<01:29:08.719> include<01:29:09.040> this<01:29:09.280> directly. 01:29:10.790 --> 01:29:10.800 align:start position:0% We can include this directly. 01:29:10.800 --> 01:29:12.870 align:start position:0% We can include this directly. If<01:29:11.040> I<01:29:11.199> show<01:29:11.360> you<01:29:11.440> the<01:29:11.679> signin<01:29:12.159> again, 01:29:12.870 --> 01:29:12.880 align:start position:0% If I show you the signin again, 01:29:12.880 --> 01:29:15.910 align:start position:0% If I show you the signin again, authorization<01:29:13.760> comes<01:29:14.080> directly.<01:29:15.440> We<01:29:15.760> can 01:29:15.910 --> 01:29:15.920 align:start position:0% authorization comes directly. We can 01:29:15.920 --> 01:29:18.950 align:start position:0% authorization comes directly. We can confirm<01:29:16.239> it.<01:29:17.600> Suppose<01:29:17.920> we<01:29:18.159> want<01:29:18.320> to<01:29:18.480> verify 01:29:18.950 --> 01:29:18.960 align:start position:0% confirm it. Suppose we want to verify 01:29:18.960 --> 01:29:21.750 align:start position:0% confirm it. Suppose we want to verify using<01:29:19.360> email.<01:29:20.639> The<01:29:20.960> email<01:29:21.280> will<01:29:21.520> come 01:29:21.750 --> 01:29:21.760 align:start position:0% using email. The email will come 01:29:21.760 --> 01:29:23.510 align:start position:0% using email. The email will come automatically. 01:29:23.510 --> 01:29:23.520 align:start position:0% automatically. 01:29:23.520 --> 01:29:26.709 align:start position:0% automatically. We<01:29:23.760> will<01:29:24.000> confirm<01:29:24.320> the<01:29:24.639> email<01:29:24.960> here.<01:29:26.400> These 01:29:26.709 --> 01:29:26.719 align:start position:0% We will confirm the email here. These 01:29:26.719 --> 01:29:29.830 align:start position:0% We will confirm the email here. These emails<01:29:27.120> run<01:29:27.360> through<01:29:27.520> a<01:29:27.760> base<01:29:28.080> setup.<01:29:29.440> We<01:29:29.679> got 01:29:29.830 --> 01:29:29.840 align:start position:0% emails run through a base setup. We got 01:29:29.840 --> 01:29:33.990 align:start position:0% emails run through a base setup. We got the<01:29:30.000> code<01:29:30.320> here.<01:29:31.679> Then<01:29:31.920> we<01:29:32.159> will<01:29:32.320> verify<01:29:32.719> it. 01:29:33.990 --> 01:29:34.000 align:start position:0% the code here. Then we will verify it. 01:29:34.000 --> 01:29:36.390 align:start position:0% the code here. Then we will verify it. Our<01:29:34.239> VS<01:29:34.639> Code<01:29:34.960> will<01:29:35.199> sign<01:29:35.440> in<01:29:35.679> and<01:29:36.000> connect 01:29:36.390 --> 01:29:36.400 align:start position:0% Our VS Code will sign in and connect 01:29:36.400 --> 01:29:38.310 align:start position:0% Our VS Code will sign in and connect automatically. 01:29:38.310 --> 01:29:38.320 align:start position:0% automatically. 01:29:38.320 --> 01:29:40.870 align:start position:0% automatically. After<01:29:38.719> signing<01:29:39.040> in,<01:29:39.840> Metabrains<01:29:40.560> connects 01:29:40.870 --> 01:29:40.880 align:start position:0% After signing in, Metabrains connects 01:29:40.880 --> 01:29:42.870 align:start position:0% After signing in, Metabrains connects with<01:29:41.040> our<01:29:41.280> co-pilot. 01:29:42.870 --> 01:29:42.880 align:start position:0% with our co-pilot. 01:29:42.880 --> 01:29:45.669 align:start position:0% with our co-pilot. We<01:29:43.040> are<01:29:43.280> running<01:29:43.520> many<01:29:43.920> windows.<01:29:45.120> In<01:29:45.440> one 01:29:45.669 --> 01:29:45.679 align:start position:0% We are running many windows. In one 01:29:45.679 --> 01:29:48.629 align:start position:0% We are running many windows. In one place,<01:29:46.080> we<01:29:46.320> run<01:29:46.480> the<01:29:46.719> agent.<01:29:48.000> In<01:29:48.239> another 01:29:48.629 --> 01:29:48.639 align:start position:0% place, we run the agent. In another 01:29:48.639 --> 01:29:51.189 align:start position:0% place, we run the agent. In another place,<01:29:49.040> we<01:29:49.280> use<01:29:49.440> our<01:29:49.679> IDE. 01:29:51.189 --> 01:29:51.199 align:start position:0% place, we use our IDE. 01:29:51.199 --> 01:29:53.430 align:start position:0% place, we use our IDE. In<01:29:51.440> a<01:29:51.600> third<01:29:51.920> place,<01:29:52.400> we<01:29:52.719> use<01:29:52.880> it<01:29:53.120> as<01:29:53.280> a 01:29:53.430 --> 01:29:53.440 align:start position:0% In a third place, we use it as a 01:29:53.440 --> 01:29:55.030 align:start position:0% In a third place, we use it as a chatbot. 01:29:55.030 --> 01:29:55.040 align:start position:0% chatbot. 01:29:55.040 --> 01:29:57.189 align:start position:0% chatbot. So,<01:29:55.520> we<01:29:55.760> must<01:29:56.080> manage<01:29:56.400> our<01:29:56.639> context 01:29:57.189 --> 01:29:57.199 align:start position:0% So, we must manage our context 01:29:57.199 --> 01:29:58.790 align:start position:0% So, we must manage our context carefully. 01:29:58.790 --> 01:29:58.800 align:start position:0% carefully. 01:29:58.800 --> 01:30:01.110 align:start position:0% carefully. Context<01:29:59.360> window<01:29:59.679> and<01:30:00.000> scope<01:30:00.400> management<01:30:00.880> are 01:30:01.110 --> 01:30:01.120 align:start position:0% Context window and scope management are 01:30:01.120 --> 01:30:02.950 align:start position:0% Context window and scope management are very<01:30:01.440> important<01:30:01.840> for<01:30:02.080> AI<01:30:02.480> software 01:30:02.950 --> 01:30:02.960 align:start position:0% very important for AI software 01:30:02.960 --> 01:30:04.629 align:start position:0% very important for AI software development. 01:30:04.629 --> 01:30:04.639 align:start position:0% development. 01:30:04.639 --> 01:30:06.550 align:start position:0% development. By<01:30:04.880> giving<01:30:05.199> the<01:30:05.440> right<01:30:05.679> information<01:30:06.239> and 01:30:06.550 --> 01:30:06.560 align:start position:0% By giving the right information and 01:30:06.560 --> 01:30:08.790 align:start position:0% By giving the right information and clear<01:30:06.880> boundaries,<01:30:07.920> developers<01:30:08.560> help 01:30:08.790 --> 01:30:08.800 align:start position:0% clear boundaries, developers help 01:30:08.800 --> 01:30:10.310 align:start position:0% clear boundaries, developers help codeex. 01:30:10.310 --> 01:30:10.320 align:start position:0% codeex. 01:30:10.320 --> 01:30:13.350 align:start position:0% codeex. It<01:30:10.639> creates<01:30:11.040> accurate,<01:30:12.000> good<01:30:12.480> and<01:30:12.800> reliable 01:30:13.350 --> 01:30:13.360 align:start position:0% It creates accurate, good and reliable 01:30:13.360 --> 01:30:16.310 align:start position:0% It creates accurate, good and reliable code.<01:30:14.800> We<01:30:15.040> must<01:30:15.280> look<01:30:15.440> at<01:30:15.600> these<01:30:15.840> important 01:30:16.310 --> 01:30:16.320 align:start position:0% code. We must look at these important 01:30:16.320 --> 01:30:18.950 align:start position:0% code. We must look at these important things<01:30:16.800> carefully.<01:30:17.679> Now,<01:30:18.000> our<01:30:18.320> discussion<01:30:18.719> is 01:30:18.950 --> 01:30:18.960 align:start position:0% things carefully. Now, our discussion is 01:30:18.960 --> 01:30:22.149 align:start position:0% things carefully. Now, our discussion is about<01:30:19.199> reviewing<01:30:19.760> our<01:30:20.000> AI<01:30:20.560> generated<01:30:21.120> code. 01:30:22.149 --> 01:30:22.159 align:start position:0% about reviewing our AI generated code. 01:30:22.159 --> 01:30:25.110 align:start position:0% about reviewing our AI generated code. In<01:30:22.400> the<01:30:22.560> AI<01:30:22.960> generated<01:30:23.520> code,<01:30:24.320> we<01:30:24.560> want<01:30:24.719> to<01:30:24.960> see 01:30:25.110 --> 01:30:25.120 align:start position:0% In the AI generated code, we want to see 01:30:25.120 --> 01:30:28.070 align:start position:0% In the AI generated code, we want to see how<01:30:25.360> we<01:30:25.600> previously<01:30:26.239> used<01:30:26.560> codes<01:30:26.960> like<01:30:27.600> create 01:30:28.070 --> 01:30:28.080 align:start position:0% how we previously used codes like create 01:30:28.080 --> 01:30:31.030 align:start position:0% how we previously used codes like create calculator<01:30:29.199> multiple<01:30:29.760> times.<01:30:30.480> As<01:30:30.719> you<01:30:30.960> can 01:30:31.030 --> 01:30:31.040 align:start position:0% calculator multiple times. As you can 01:30:31.040 --> 01:30:34.709 align:start position:0% calculator multiple times. As you can see,<01:30:32.400> we<01:30:32.639> have<01:30:32.800> created<01:30:33.199> the<01:30:33.440> calculator<01:30:34.000> here 01:30:34.709 --> 01:30:34.719 align:start position:0% see, we have created the calculator here 01:30:34.719 --> 01:30:36.870 align:start position:0% see, we have created the calculator here and<01:30:34.960> you<01:30:35.199> can<01:30:35.280> see<01:30:35.440> that<01:30:35.679> all<01:30:35.840> our<01:30:36.080> changes<01:30:36.639> are 01:30:36.870 --> 01:30:36.880 align:start position:0% and you can see that all our changes are 01:30:36.880 --> 01:30:40.229 align:start position:0% and you can see that all our changes are also<01:30:37.199> available<01:30:37.679> here.<01:30:39.120> For<01:30:39.360> these<01:30:39.760> AI 01:30:40.229 --> 01:30:40.239 align:start position:0% also available here. For these AI 01:30:40.239 --> 01:30:42.709 align:start position:0% also available here. For these AI generated<01:30:40.800> changes,<01:30:41.760> we<01:30:42.080> first<01:30:42.320> need<01:30:42.560> to 01:30:42.709 --> 01:30:42.719 align:start position:0% generated changes, we first need to 01:30:42.719 --> 01:30:45.510 align:start position:0% generated changes, we first need to understand<01:30:43.199> two<01:30:43.520> or<01:30:43.760> three<01:30:44.000> things. 01:30:45.510 --> 01:30:45.520 align:start position:0% understand two or three things. 01:30:45.520 --> 01:30:47.990 align:start position:0% understand two or three things. First,<01:30:46.320> in<01:30:46.560> this<01:30:46.800> complete<01:30:47.199> software<01:30:47.679> we<01:30:47.840> are 01:30:47.990 --> 01:30:48.000 align:start position:0% First, in this complete software we are 01:30:48.000 --> 01:30:50.629 align:start position:0% First, in this complete software we are using,<01:30:48.800> whenever<01:30:49.199> there<01:30:49.360> are<01:30:49.600> changes,<01:30:50.320> the 01:30:50.629 --> 01:30:50.639 align:start position:0% using, whenever there are changes, the 01:30:50.639 --> 01:30:52.550 align:start position:0% using, whenever there are changes, the red<01:30:50.880> values<01:30:51.280> will<01:30:51.520> be<01:30:51.679> all<01:30:51.840> our<01:30:52.159> previous 01:30:52.550 --> 01:30:52.560 align:start position:0% red values will be all our previous 01:30:52.560 --> 01:30:55.030 align:start position:0% red values will be all our previous values<01:30:53.280> and<01:30:53.520> the<01:30:53.760> green<01:30:54.080> values<01:30:54.480> will<01:30:54.719> be<01:30:54.800> our 01:30:55.030 --> 01:30:55.040 align:start position:0% values and the green values will be our 01:30:55.040 --> 01:30:57.030 align:start position:0% values and the green values will be our new<01:30:55.360> possible<01:30:55.760> changes<01:30:56.239> that<01:30:56.480> we<01:30:56.639> have<01:30:56.800> used 01:30:57.030 --> 01:30:57.040 align:start position:0% new possible changes that we have used 01:30:57.040 --> 01:30:58.550 align:start position:0% new possible changes that we have used here. 01:30:58.550 --> 01:30:58.560 align:start position:0% here. 01:30:58.560 --> 01:31:01.030 align:start position:0% here. If<01:30:58.800> you<01:30:58.960> look<01:30:59.199> here,<01:30:59.760> you<01:31:00.000> can<01:31:00.159> first<01:31:00.560> see<01:31:00.719> the 01:31:01.030 --> 01:31:01.040 align:start position:0% If you look here, you can first see the 01:31:01.040 --> 01:31:04.229 align:start position:0% If you look here, you can first see the set<01:31:01.440> display<01:31:02.080> error.<01:31:03.040> But<01:31:03.280> now<01:31:03.520> in<01:31:03.760> our<01:31:04.000> new 01:31:04.229 --> 01:31:04.239 align:start position:0% set display error. But now in our new 01:31:04.239 --> 01:31:07.270 align:start position:0% set display error. But now in our new code,<01:31:04.880> some<01:31:05.120> things<01:31:05.440> have<01:31:05.600> expanded. 01:31:07.270 --> 01:31:07.280 align:start position:0% code, some things have expanded. 01:31:07.280 --> 01:31:09.350 align:start position:0% code, some things have expanded. Let<01:31:07.520> us<01:31:07.760> suppose<01:31:08.080> I<01:31:08.400> directly<01:31:08.880> include<01:31:09.199> a 01:31:09.350 --> 01:31:09.360 align:start position:0% Let us suppose I directly include a 01:31:09.360 --> 01:31:12.070 align:start position:0% Let us suppose I directly include a prompt<01:31:09.679> here<01:31:10.000> saying<01:31:10.800> I<01:31:11.040> want<01:31:11.199> a<01:31:11.440> scientific 01:31:12.070 --> 01:31:12.080 align:start position:0% prompt here saying I want a scientific 01:31:12.080 --> 01:31:13.990 align:start position:0% prompt here saying I want a scientific calculator. 01:31:13.990 --> 01:31:14.000 align:start position:0% calculator. 01:31:14.000 --> 01:31:16.390 align:start position:0% calculator. Now<01:31:14.560> a<01:31:14.800> scientific<01:31:15.440> calculator<01:31:16.000> will<01:31:16.239> be 01:31:16.390 --> 01:31:16.400 align:start position:0% Now a scientific calculator will be 01:31:16.400 --> 01:31:19.669 align:start position:0% Now a scientific calculator will be created<01:31:16.880> here.<01:31:18.239> Usually<01:31:18.719> we<01:31:18.960> had<01:31:19.199> this<01:31:19.440> one 01:31:19.669 --> 01:31:19.679 align:start position:0% created here. Usually we had this one 01:31:19.679 --> 01:31:23.110 align:start position:0% created here. Usually we had this one code<01:31:20.239> and<01:31:20.480> we<01:31:20.639> can<01:31:20.800> call<01:31:21.040> it<01:31:21.360> version<01:31:21.760> one. 01:31:23.110 --> 01:31:23.120 align:start position:0% code and we can call it version one. 01:31:23.120 --> 01:31:25.510 align:start position:0% code and we can call it version one. Automatically<01:31:24.320> this<01:31:24.560> version<01:31:24.880> of<01:31:25.040> ours<01:31:25.360> will 01:31:25.510 --> 01:31:25.520 align:start position:0% Automatically this version of ours will 01:31:25.520 --> 01:31:27.830 align:start position:0% Automatically this version of ours will be<01:31:25.600> applied<01:31:26.000> here.<01:31:26.880> And<01:31:27.120> along<01:31:27.440> with<01:31:27.600> this 01:31:27.830 --> 01:31:27.840 align:start position:0% be applied here. And along with this 01:31:27.840 --> 01:31:30.229 align:start position:0% be applied here. And along with this version,<01:31:28.639> if<01:31:28.880> we<01:31:29.120> have<01:31:29.280> any<01:31:29.520> other<01:31:29.840> versions 01:31:30.229 --> 01:31:30.239 align:start position:0% version, if we have any other versions 01:31:30.239 --> 01:31:33.430 align:start position:0% version, if we have any other versions available<01:31:30.719> here,<01:31:31.360> they<01:31:31.600> will<01:31:31.760> be<01:31:31.920> used. 01:31:33.430 --> 01:31:33.440 align:start position:0% available here, they will be used. 01:31:33.440 --> 01:31:35.669 align:start position:0% available here, they will be used. First<01:31:33.679> of<01:31:33.840> all,<01:31:34.400> it<01:31:34.639> will<01:31:34.800> take<01:31:35.040> some<01:31:35.280> time<01:31:35.440> to 01:31:35.669 --> 01:31:35.679 align:start position:0% First of all, it will take some time to 01:31:35.679 --> 01:31:37.430 align:start position:0% First of all, it will take some time to think<01:31:35.920> about<01:31:36.159> what<01:31:36.480> things<01:31:36.800> were<01:31:37.040> discussed 01:31:37.430 --> 01:31:37.440 align:start position:0% think about what things were discussed 01:31:37.440 --> 01:31:39.910 align:start position:0% think about what things were discussed in<01:31:37.600> the<01:31:37.840> previous<01:31:38.159> context. 01:31:39.910 --> 01:31:39.920 align:start position:0% in the previous context. 01:31:39.920 --> 01:31:41.910 align:start position:0% in the previous context. It<01:31:40.159> will<01:31:40.320> review<01:31:40.719> what<01:31:41.040> discussions<01:31:41.520> we<01:31:41.760> were 01:31:41.910 --> 01:31:41.920 align:start position:0% It will review what discussions we were 01:31:41.920 --> 01:31:43.830 align:start position:0% It will review what discussions we were having<01:31:42.159> previously. 01:31:43.830 --> 01:31:43.840 align:start position:0% having previously. 01:31:43.840 --> 01:31:46.310 align:start position:0% having previously. After<01:31:44.159> all<01:31:44.400> those<01:31:44.639> discussions,<01:31:45.679> our<01:31:46.000> code 01:31:46.310 --> 01:31:46.320 align:start position:0% After all those discussions, our code 01:31:46.320 --> 01:31:48.149 align:start position:0% After all those discussions, our code will<01:31:46.560> automatically<01:31:47.280> start<01:31:47.600> generating 01:31:48.149 --> 01:31:48.159 align:start position:0% will automatically start generating 01:31:48.159 --> 01:31:49.750 align:start position:0% will automatically start generating here. 01:31:49.750 --> 01:31:49.760 align:start position:0% here. 01:31:49.760 --> 01:31:51.910 align:start position:0% here. All<01:31:49.920> right,<01:31:50.480> it<01:31:50.800> is<01:31:50.960> reconnecting<01:31:51.440> with<01:31:51.679> our 01:31:51.910 --> 01:31:51.920 align:start position:0% All right, it is reconnecting with our 01:31:51.920 --> 01:31:54.550 align:start position:0% All right, it is reconnecting with our work.<01:31:52.880> Our<01:31:53.360> connection<01:31:53.679> with<01:31:53.840> the<01:31:54.080> model<01:31:54.320> is 01:31:54.550 --> 01:31:54.560 align:start position:0% work. Our connection with the model is 01:31:54.560 --> 01:31:56.550 align:start position:0% work. Our connection with the model is being<01:31:54.800> created<01:31:55.280> to<01:31:55.520> see<01:31:55.760> how<01:31:55.920> a<01:31:56.159> complete 01:31:56.550 --> 01:31:56.560 align:start position:0% being created to see how a complete 01:31:56.560 --> 01:31:58.950 align:start position:0% being created to see how a complete connection<01:31:56.960> will<01:31:57.199> be<01:31:57.360> generated<01:31:58.239> and<01:31:58.480> how<01:31:58.639> our 01:31:58.950 --> 01:31:58.960 align:start position:0% connection will be generated and how our 01:31:58.960 --> 01:32:02.070 align:start position:0% connection will be generated and how our thinking<01:31:59.280> will<01:31:59.600> work<01:31:59.760> on<01:31:59.920> a<01:32:00.159> larger<01:32:00.480> scale. 01:32:02.070 --> 01:32:02.080 align:start position:0% thinking will work on a larger scale. 01:32:02.080 --> 01:32:04.070 align:start position:0% thinking will work on a larger scale. Usually<01:32:02.800> when<01:32:03.040> we<01:32:03.199> are<01:32:03.360> looking<01:32:03.520> at<01:32:03.679> such<01:32:03.920> a 01:32:04.070 --> 01:32:04.080 align:start position:0% Usually when we are looking at such a 01:32:04.080 --> 01:32:07.189 align:start position:0% Usually when we are looking at such a code<01:32:04.560> we<01:32:04.800> have<01:32:04.960> to<01:32:05.120> do<01:32:05.280> validation.<01:32:06.719> We<01:32:06.960> can 01:32:07.189 --> 01:32:07.199 align:start position:0% code we have to do validation. We can 01:32:07.199 --> 01:32:09.030 align:start position:0% code we have to do validation. We can separate<01:32:07.600> our<01:32:07.920> unified<01:32:08.400> difference<01:32:08.800> from 01:32:09.030 --> 01:32:09.040 align:start position:0% separate our unified difference from 01:32:09.040 --> 01:32:12.390 align:start position:0% separate our unified difference from here.<01:32:10.159> We<01:32:10.400> call<01:32:10.639> this<01:32:10.960> split<01:32:11.600> and<01:32:11.840> we<01:32:12.000> call<01:32:12.239> the 01:32:12.390 --> 01:32:12.400 align:start position:0% here. We call this split and we call the 01:32:12.400 --> 01:32:14.470 align:start position:0% here. We call this split and we call the other<01:32:12.560> one<01:32:12.960> unified. 01:32:14.470 --> 01:32:14.480 align:start position:0% other one unified. 01:32:14.480 --> 01:32:17.030 align:start position:0% other one unified. In<01:32:14.639> the<01:32:14.800> split<01:32:15.199> view<01:32:15.840> our<01:32:16.159> complete<01:32:16.639> previous 01:32:17.030 --> 01:32:17.040 align:start position:0% In the split view our complete previous 01:32:17.040 --> 01:32:19.510 align:start position:0% In the split view our complete previous code<01:32:17.360> base<01:32:17.600> is<01:32:17.840> on<01:32:18.000> one<01:32:18.239> side<01:32:18.800> and<01:32:19.120> our<01:32:19.360> new 01:32:19.510 --> 01:32:19.520 align:start position:0% code base is on one side and our new 01:32:19.520 --> 01:32:22.390 align:start position:0% code base is on one side and our new code<01:32:19.840> is<01:32:20.000> included<01:32:20.480> on<01:32:20.639> the<01:32:20.800> other<01:32:20.960> side.<01:32:22.239> In 01:32:22.390 --> 01:32:22.400 align:start position:0% code is included on the other side. In 01:32:22.400 --> 01:32:24.790 align:start position:0% code is included on the other side. In the<01:32:22.639> previous<01:32:22.960> one<01:32:23.520> you<01:32:23.760> can<01:32:23.920> see<01:32:24.000> the<01:32:24.239> display 01:32:24.790 --> 01:32:24.800 align:start position:0% the previous one you can see the display 01:32:24.800 --> 01:32:27.350 align:start position:0% the previous one you can see the display error<01:32:25.520> and<01:32:25.760> here<01:32:26.000> you<01:32:26.239> can<01:32:26.400> see<01:32:26.560> how<01:32:26.800> much<01:32:27.040> our 01:32:27.350 --> 01:32:27.360 align:start position:0% error and here you can see how much our 01:32:27.360 --> 01:32:30.229 align:start position:0% error and here you can see how much our error<01:32:27.600> evaluation<01:32:28.159> is<01:32:28.400> available<01:32:28.880> now. 01:32:30.229 --> 01:32:30.239 align:start position:0% error evaluation is available now. 01:32:30.239 --> 01:32:32.790 align:start position:0% error evaluation is available now. Similarly<01:32:31.120> our<01:32:31.440> if<01:32:31.760> action<01:32:32.239> is<01:32:32.480> also 01:32:32.790 --> 01:32:32.800 align:start position:0% Similarly our if action is also 01:32:32.800 --> 01:32:35.750 align:start position:0% Similarly our if action is also available<01:32:33.280> here.<01:32:34.239> We<01:32:34.480> can<01:32:34.639> see<01:32:34.800> how<01:32:35.120> much<01:32:35.440> if 01:32:35.750 --> 01:32:35.760 align:start position:0% available here. We can see how much if 01:32:35.760 --> 01:32:38.629 align:start position:0% available here. We can see how much if action<01:32:36.159> we<01:32:36.320> had<01:32:36.560> previously<01:32:37.520> and<01:32:37.840> after<01:32:38.080> that 01:32:38.629 --> 01:32:38.639 align:start position:0% action we had previously and after that 01:32:38.639 --> 01:32:40.790 align:start position:0% action we had previously and after that how<01:32:38.960> many<01:32:39.120> evaluations<01:32:39.840> are<01:32:40.080> coming<01:32:40.239> in<01:32:40.480> our 01:32:40.790 --> 01:32:40.800 align:start position:0% how many evaluations are coming in our 01:32:40.800 --> 01:32:44.149 align:start position:0% how many evaluations are coming in our run<01:32:41.120> action.<01:32:42.480> All<01:32:42.560> right.<01:32:43.440> So<01:32:43.679> all<01:32:43.920> these 01:32:44.149 --> 01:32:44.159 align:start position:0% run action. All right. So all these 01:32:44.159 --> 01:32:45.910 align:start position:0% run action. All right. So all these things<01:32:44.400> are<01:32:44.560> being<01:32:44.800> directly<01:32:45.280> included<01:32:45.679> in 01:32:45.910 --> 01:32:45.920 align:start position:0% things are being directly included in 01:32:45.920 --> 01:32:48.550 align:start position:0% things are being directly included in our<01:32:46.159> system.<01:32:47.360> We<01:32:47.600> are<01:32:47.760> looking<01:32:47.920> at<01:32:48.159> multiple 01:32:48.550 --> 01:32:48.560 align:start position:0% our system. We are looking at multiple 01:32:48.560 --> 01:32:51.110 align:start position:0% our system. We are looking at multiple changes<01:32:49.040> here.<01:32:50.159> You<01:32:50.400> can<01:32:50.560> see<01:32:50.639> that<01:32:50.880> our 01:32:51.110 --> 01:32:51.120 align:start position:0% changes here. You can see that our 01:32:51.120 --> 01:32:53.030 align:start position:0% changes here. You can see that our connection<01:32:51.520> is<01:32:51.760> being<01:32:52.000> created<01:32:52.480> once<01:32:52.719> again. 01:32:53.030 --> 01:32:53.040 align:start position:0% connection is being created once again. 01:32:53.040 --> 01:32:55.669 align:start position:0% connection is being created once again. Here<01:32:53.920> we<01:32:54.239> can<01:32:54.400> change<01:32:54.639> the<01:32:54.800> model<01:32:55.040> to<01:32:55.280> a<01:32:55.440> very 01:32:55.669 --> 01:32:55.679 align:start position:0% Here we can change the model to a very 01:32:55.679 --> 01:32:58.709 align:start position:0% Here we can change the model to a very simple<01:32:56.000> one.<01:32:56.639> Make<01:32:56.880> the<01:32:57.040> speed<01:32:57.360> fast<01:32:58.080> and<01:32:58.400> also 01:32:58.709 --> 01:32:58.719 align:start position:0% simple one. Make the speed fast and also 01:32:58.719 --> 01:33:02.070 align:start position:0% simple one. Make the speed fast and also change<01:32:59.040> the<01:32:59.199> reasoning<01:32:59.679> here.<01:33:01.040> Now<01:33:01.600> besides 01:33:02.070 --> 01:33:02.080 align:start position:0% change the reasoning here. Now besides 01:33:02.080 --> 01:33:04.149 align:start position:0% change the reasoning here. Now besides all<01:33:02.239> these<01:33:02.480> things,<01:33:03.040> we<01:33:03.280> have<01:33:03.520> two<01:33:03.760> options 01:33:04.149 --> 01:33:04.159 align:start position:0% all these things, we have two options 01:33:04.159 --> 01:33:07.910 align:start position:0% all these things, we have two options available<01:33:04.639> here.<01:33:05.600> Review<01:33:06.080> and<01:33:06.400> undo. 01:33:07.910 --> 01:33:07.920 align:start position:0% available here. Review and undo. 01:33:07.920 --> 01:33:10.310 align:start position:0% available here. Review and undo. In<01:33:08.080> the<01:33:08.320> review<01:33:08.639> option,<01:33:09.440> we<01:33:09.679> can<01:33:09.840> directly 01:33:10.310 --> 01:33:10.320 align:start position:0% In the review option, we can directly 01:33:10.320 --> 01:33:12.070 align:start position:0% In the review option, we can directly review<01:33:10.639> our<01:33:10.880> code<01:33:11.199> once<01:33:11.520> in<01:33:11.679> the<01:33:11.840> first 01:33:12.070 --> 01:33:12.080 align:start position:0% review our code once in the first 01:33:12.080 --> 01:33:15.350 align:start position:0% review our code once in the first scenario.<01:33:13.520> And<01:33:13.760> undo<01:33:14.320> works<01:33:14.719> exactly<01:33:15.120> like 01:33:15.350 --> 01:33:15.360 align:start position:0% scenario. And undo works exactly like 01:33:15.360 --> 01:33:18.149 align:start position:0% scenario. And undo works exactly like our<01:33:15.600> version<01:33:16.000> control<01:33:16.400> system.<01:33:17.520> It<01:33:17.760> keeps 01:33:18.149 --> 01:33:18.159 align:start position:0% our version control system. It keeps 01:33:18.159 --> 01:33:21.350 align:start position:0% our version control system. It keeps multiple<01:33:18.639> versions<01:33:19.040> in<01:33:19.280> our<01:33:19.440> adopted<01:33:19.920> system. 01:33:21.350 --> 01:33:21.360 align:start position:0% multiple versions in our adopted system. 01:33:21.360 --> 01:33:23.270 align:start position:0% multiple versions in our adopted system. Here<01:33:21.600> you<01:33:21.840> can<01:33:21.920> see<01:33:22.080> that<01:33:22.320> our<01:33:22.560> system<01:33:22.800> is<01:33:23.040> now 01:33:23.270 --> 01:33:23.280 align:start position:0% Here you can see that our system is now 01:33:23.280 --> 01:33:25.590 align:start position:0% Here you can see that our system is now running<01:33:24.000> and<01:33:24.239> it<01:33:24.480> is<01:33:24.639> telling<01:33:24.880> us<01:33:25.040> that<01:33:25.199> it<01:33:25.440> is 01:33:25.590 --> 01:33:25.600 align:start position:0% running and it is telling us that it is 01:33:25.600 --> 01:33:29.110 align:start position:0% running and it is telling us that it is upgrading<01:33:26.159> the<01:33:26.400> existing<01:33:27.040> HTML. 01:33:29.110 --> 01:33:29.120 align:start position:0% upgrading the existing HTML. 01:33:29.120 --> 01:33:31.510 align:start position:0% upgrading the existing HTML. Now<01:33:29.760> let<01:33:30.000> us<01:33:30.159> suppose<01:33:30.560> I<01:33:30.800> take<01:33:30.960> you<01:33:31.120> to<01:33:31.280> this 01:33:31.510 --> 01:33:31.520 align:start position:0% Now let us suppose I take you to this 01:33:31.520 --> 01:33:34.550 align:start position:0% Now let us suppose I take you to this HTML<01:33:32.320> file.<01:33:33.440> I<01:33:33.679> will<01:33:33.840> show<01:33:34.159> all<01:33:34.320> the 01:33:34.550 --> 01:33:34.560 align:start position:0% HTML file. I will show all the 01:33:34.560 --> 01:33:37.430 align:start position:0% HTML file. I will show all the differences<01:33:35.040> here.<01:33:36.159> They<01:33:36.400> are<01:33:36.560> here<01:33:36.800> now<01:33:37.199> and 01:33:37.430 --> 01:33:37.440 align:start position:0% differences here. They are here now and 01:33:37.440 --> 01:33:40.629 align:start position:0% differences here. They are here now and we<01:33:37.679> will<01:33:37.840> also<01:33:38.080> enable<01:33:38.400> the<01:33:38.639> rich<01:33:38.960> preview. 01:33:40.629 --> 01:33:40.639 align:start position:0% we will also enable the rich preview. 01:33:40.639 --> 01:33:42.709 align:start position:0% we will also enable the rich preview. Now<01:33:40.880> you<01:33:41.120> can<01:33:41.280> see<01:33:41.440> that<01:33:41.679> this<01:33:41.920> is<01:33:42.080> our<01:33:42.320> newer 01:33:42.709 --> 01:33:42.719 align:start position:0% Now you can see that this is our newer 01:33:42.719 --> 01:33:45.990 align:start position:0% Now you can see that this is our newer file.<01:33:44.000> Even<01:33:44.320> after<01:33:44.560> the<01:33:44.719> newer<01:33:45.120> file<01:33:45.600> when<01:33:45.840> we 01:33:45.990 --> 01:33:46.000 align:start position:0% file. Even after the newer file when we 01:33:46.000 --> 01:33:48.390 align:start position:0% file. Even after the newer file when we make<01:33:46.159> changes<01:33:46.639> again<01:33:47.440> those<01:33:47.760> changes<01:33:48.159> will 01:33:48.390 --> 01:33:48.400 align:start position:0% make changes again those changes will 01:33:48.400 --> 01:33:51.430 align:start position:0% make changes again those changes will also<01:33:48.639> be<01:33:48.800> visible<01:33:49.199> here.<01:33:50.320> You<01:33:50.560> will<01:33:50.719> see<01:33:51.040> plus 01:33:51.430 --> 01:33:51.440 align:start position:0% also be visible here. You will see plus 01:33:51.440 --> 01:33:55.510 align:start position:0% also be visible here. You will see plus 32<01:33:52.239> and<01:33:52.560> minus<01:33:53.120> 21.<01:33:54.560> This<01:33:54.800> shows<01:33:55.120> how<01:33:55.360> many 01:33:55.510 --> 01:33:55.520 align:start position:0% 32 and minus 21. This shows how many 01:33:55.520 --> 01:33:57.750 align:start position:0% 32 and minus 21. This shows how many lines<01:33:55.840> of<01:33:56.000> code<01:33:56.239> were<01:33:56.480> removed<01:33:57.120> and<01:33:57.360> how<01:33:57.600> many 01:33:57.750 --> 01:33:57.760 align:start position:0% lines of code were removed and how many 01:33:57.760 --> 01:33:59.590 align:start position:0% lines of code were removed and how many lines<01:33:58.000> of<01:33:58.159> code<01:33:58.400> were<01:33:58.639> added<01:33:58.880> to<01:33:59.040> our<01:33:59.199> total 01:33:59.590 --> 01:33:59.600 align:start position:0% lines of code were added to our total 01:33:59.600 --> 01:34:02.390 align:start position:0% lines of code were added to our total system.<01:34:00.960> When<01:34:01.280> both<01:34:01.520> these<01:34:01.840> things<01:34:02.080> work 01:34:02.390 --> 01:34:02.400 align:start position:0% system. When both these things work 01:34:02.400 --> 01:34:04.709 align:start position:0% system. When both these things work together<01:34:03.199> we<01:34:03.440> automatically<01:34:04.239> start<01:34:04.480> getting 01:34:04.709 --> 01:34:04.719 align:start position:0% together we automatically start getting 01:34:04.719 --> 01:34:07.350 align:start position:0% together we automatically start getting our<01:34:04.960> response<01:34:05.280> and<01:34:05.520> work<01:34:05.840> results.<01:34:06.800> It<01:34:07.040> shows 01:34:07.350 --> 01:34:07.360 align:start position:0% our response and work results. It shows 01:34:07.360 --> 01:34:09.750 align:start position:0% our response and work results. It shows how<01:34:07.520> we<01:34:07.679> are<01:34:07.840> managing<01:34:08.239> things. 01:34:09.750 --> 01:34:09.760 align:start position:0% how we are managing things. 01:34:09.760 --> 01:34:12.390 align:start position:0% how we are managing things. All<01:34:09.840> right.<01:34:10.639> So<01:34:10.880> this<01:34:11.199> is<01:34:11.280> our<01:34:11.600> very<01:34:11.840> detailed 01:34:12.390 --> 01:34:12.400 align:start position:0% All right. So this is our very detailed 01:34:12.400 --> 01:34:14.310 align:start position:0% All right. So this is our very detailed working<01:34:12.800> process. 01:34:14.310 --> 01:34:14.320 align:start position:0% working process. 01:34:14.320 --> 01:34:17.430 align:start position:0% working process. Here<01:34:14.560> you<01:34:14.800> can<01:34:14.960> see<01:34:15.199> all<01:34:15.440> the<01:34:15.600> changes.<01:34:17.040> For<01:34:17.199> a 01:34:17.430 --> 01:34:17.440 align:start position:0% Here you can see all the changes. For a 01:34:17.440 --> 01:34:19.910 align:start position:0% Here you can see all the changes. For a simple<01:34:17.679> example<01:34:18.320> as<01:34:18.560> we<01:34:18.719> are<01:34:18.880> reviewing<01:34:19.280> now 01:34:19.910 --> 01:34:19.920 align:start position:0% simple example as we are reviewing now 01:34:19.920 --> 01:34:23.110 align:start position:0% simple example as we are reviewing now the<01:34:20.159> title<01:34:20.560> was<01:34:20.800> previously<01:34:21.679> calculator<01:34:22.880> but 01:34:23.110 --> 01:34:23.120 align:start position:0% the title was previously calculator but 01:34:23.120 --> 01:34:25.830 align:start position:0% the title was previously calculator but now<01:34:23.360> our<01:34:23.600> new<01:34:23.840> title<01:34:24.159> has<01:34:24.400> become<01:34:25.120> scientific 01:34:25.830 --> 01:34:25.840 align:start position:0% now our new title has become scientific 01:34:25.840 --> 01:34:27.669 align:start position:0% now our new title has become scientific calculator. 01:34:27.669 --> 01:34:27.679 align:start position:0% calculator. 01:34:27.679 --> 01:34:30.470 align:start position:0% calculator. All<01:34:27.760> right.<01:34:28.719> If<01:34:28.960> we<01:34:29.120> look<01:34:29.280> here<01:34:29.520> now<01:34:30.080> all<01:34:30.239> the 01:34:30.470 --> 01:34:30.480 align:start position:0% All right. If we look here now all the 01:34:30.480 --> 01:34:32.310 align:start position:0% All right. If we look here now all the design<01:34:30.800> changes<01:34:31.199> of<01:34:31.360> our<01:34:31.600> calculator<01:34:32.080> are 01:34:32.310 --> 01:34:32.320 align:start position:0% design changes of our calculator are 01:34:32.320 --> 01:34:35.510 align:start position:0% design changes of our calculator are shown<01:34:32.560> here<01:34:32.880> with<01:34:33.199> plus<01:34:33.520> and<01:34:33.760> minus<01:34:34.159> signs. 01:34:35.510 --> 01:34:35.520 align:start position:0% shown here with plus and minus signs. 01:34:35.520 --> 01:34:37.590 align:start position:0% shown here with plus and minus signs. Also<01:34:36.080> you<01:34:36.320> can<01:34:36.400> see<01:34:36.480> that<01:34:36.639> if<01:34:36.880> we<01:34:37.040> want<01:34:37.120> to<01:34:37.360> add 01:34:37.590 --> 01:34:37.600 align:start position:0% Also you can see that if we want to add 01:34:37.600 --> 01:34:40.070 align:start position:0% Also you can see that if we want to add something<01:34:37.920> here<01:34:38.560> we<01:34:38.800> can<01:34:38.960> directly<01:34:39.440> include<01:34:39.840> a 01:34:40.070 --> 01:34:40.080 align:start position:0% something here we can directly include a 01:34:40.080 --> 01:34:43.270 align:start position:0% something here we can directly include a local<01:34:40.400> comment.<01:34:41.679> For<01:34:41.760> example<01:34:42.639> I<01:34:42.960> can<01:34:43.040> say 01:34:43.270 --> 01:34:43.280 align:start position:0% local comment. For example I can say 01:34:43.280 --> 01:34:47.110 align:start position:0% local comment. For example I can say here<01:34:44.000> I<01:34:44.320> want<01:34:44.560> round<01:34:44.960> buttons.<01:34:46.320> Okay.<01:34:46.800> So<01:34:46.960> now 01:34:47.110 --> 01:34:47.120 align:start position:0% here I want round buttons. Okay. So now 01:34:47.120 --> 01:34:50.229 align:start position:0% here I want round buttons. Okay. So now we<01:34:47.360> want<01:34:47.520> our<01:34:47.760> round<01:34:48.159> buttons.<01:34:49.520> As<01:34:49.760> soon<01:34:49.920> as<01:34:50.000> I 01:34:50.229 --> 01:34:50.239 align:start position:0% we want our round buttons. As soon as I 01:34:50.239 --> 01:34:52.229 align:start position:0% we want our round buttons. As soon as I post<01:34:50.480> this<01:34:50.719> comment<01:34:51.360> you<01:34:51.600> can<01:34:51.679> see<01:34:51.840> it<01:34:52.080> is 01:34:52.229 --> 01:34:52.239 align:start position:0% post this comment you can see it is 01:34:52.239 --> 01:34:54.709 align:start position:0% post this comment you can see it is included<01:34:52.639> here.<01:34:53.760> Now<01:34:54.000> this<01:34:54.239> comment<01:34:54.560> is 01:34:54.709 --> 01:34:54.719 align:start position:0% included here. Now this comment is 01:34:54.719 --> 01:34:57.830 align:start position:0% included here. Now this comment is added.<01:34:55.199> All<01:34:55.280> right.<01:34:56.400> Similarly<01:34:57.199> if<01:34:57.440> we<01:34:57.600> go 01:34:57.830 --> 01:34:57.840 align:start position:0% added. All right. Similarly if we go 01:34:57.840 --> 01:35:01.590 align:start position:0% added. All right. Similarly if we go here<01:34:58.159> I<01:34:58.400> will<01:34:58.560> say<01:34:59.280> I<01:34:59.520> want<01:34:59.760> more<01:35:00.000> buttons.<01:35:01.360> I 01:35:01.590 --> 01:35:01.600 align:start position:0% here I will say I want more buttons. I 01:35:01.600 --> 01:35:03.590 align:start position:0% here I will say I want more buttons. I am<01:35:01.760> making<01:35:02.080> very<01:35:02.480> simple<01:35:02.880> changes<01:35:03.280> in<01:35:03.520> front 01:35:03.590 --> 01:35:03.600 align:start position:0% am making very simple changes in front 01:35:03.600 --> 01:35:06.950 align:start position:0% am making very simple changes in front of<01:35:03.760> you.<01:35:04.800> I<01:35:05.040> will<01:35:05.199> add<01:35:05.360> the<01:35:05.520> comment.<01:35:06.719> Now 01:35:06.950 --> 01:35:06.960 align:start position:0% of you. I will add the comment. Now 01:35:06.960 --> 01:35:09.750 align:start position:0% of you. I will add the comment. Now there<01:35:07.199> are<01:35:07.360> two<01:35:07.600> comments<01:35:08.000> here.<01:35:08.320> All<01:35:08.400> right. 01:35:09.750 --> 01:35:09.760 align:start position:0% there are two comments here. All right. 01:35:09.760 --> 01:35:12.070 align:start position:0% there are two comments here. All right. In<01:35:10.000> the<01:35:10.159> same<01:35:10.400> way<01:35:10.960> at<01:35:11.199> the<01:35:11.360> end<01:35:11.440> of<01:35:11.600> this<01:35:11.760> file 01:35:12.070 --> 01:35:12.080 align:start position:0% In the same way at the end of this file 01:35:12.080 --> 01:35:13.590 align:start position:0% In the same way at the end of this file I<01:35:12.320> will<01:35:12.400> say<01:35:12.560> that<01:35:12.719> we<01:35:12.880> need<01:35:13.120> simpler 01:35:13.590 --> 01:35:13.600 align:start position:0% I will say that we need simpler 01:35:13.600 --> 01:35:17.350 align:start position:0% I will say that we need simpler functionality<01:35:14.320> here.<01:35:15.520> Okay.<01:35:16.000> I<01:35:16.320> will<01:35:16.480> say 01:35:17.350 --> 01:35:17.360 align:start position:0% functionality here. Okay. I will say 01:35:17.360 --> 01:35:20.310 align:start position:0% functionality here. Okay. I will say simple<01:35:17.840> functionality<01:35:18.719> please. 01:35:20.310 --> 01:35:20.320 align:start position:0% simple functionality please. 01:35:20.320 --> 01:35:23.510 align:start position:0% simple functionality please. All<01:35:20.400> right.<01:35:21.280> This<01:35:21.520> comment<01:35:21.840> is<01:35:22.000> added<01:35:22.320> here. 01:35:23.510 --> 01:35:23.520 align:start position:0% All right. This comment is added here. 01:35:23.520 --> 01:35:26.070 align:start position:0% All right. This comment is added here. After<01:35:23.840> that<01:35:24.400> we<01:35:24.639> can<01:35:24.800> go<01:35:24.880> to<01:35:25.040> the<01:35:25.280> end<01:35:25.520> or<01:35:25.840> just 01:35:26.070 --> 01:35:26.080 align:start position:0% After that we can go to the end or just 01:35:26.080 --> 01:35:29.030 align:start position:0% After that we can go to the end or just go<01:35:26.239> to<01:35:26.400> the<01:35:26.560> start.<01:35:27.760> In<01:35:28.000> the<01:35:28.239> start<01:35:28.560> I<01:35:28.880> will 01:35:29.030 --> 01:35:29.040 align:start position:0% go to the start. In the start I will 01:35:29.040 --> 01:35:32.070 align:start position:0% go to the start. In the start I will change<01:35:29.280> our<01:35:29.520> name<01:35:29.760> here.<01:35:30.800> Change<01:35:31.120> the<01:35:31.360> name<01:35:31.760> as 01:35:32.070 --> 01:35:32.080 align:start position:0% change our name here. Change the name as 01:35:32.080 --> 01:35:37.350 align:start position:0% change our name here. Change the name as metabrains<01:35:32.960> cal.<01:35:34.320> Okay.<01:35:34.880> Metabrains<01:35:35.760> cal. 01:35:37.350 --> 01:35:37.360 align:start position:0% metabrains cal. Okay. Metabrains cal. 01:35:37.360 --> 01:35:40.709 align:start position:0% metabrains cal. Okay. Metabrains cal. All<01:35:37.440> right.<01:35:38.320> Now<01:35:38.560> our<01:35:38.880> comment<01:35:39.120> is<01:35:39.360> added.<01:35:40.480> You 01:35:40.709 --> 01:35:40.719 align:start position:0% All right. Now our comment is added. You 01:35:40.719 --> 01:35:42.709 align:start position:0% All right. Now our comment is added. You can<01:35:40.800> see<01:35:40.960> that<01:35:41.280> three<01:35:41.600> or<01:35:41.920> four<01:35:42.159> comments<01:35:42.560> are 01:35:42.709 --> 01:35:42.719 align:start position:0% can see that three or four comments are 01:35:42.719 --> 01:35:45.910 align:start position:0% can see that three or four comments are here.<01:35:42.960> Now<01:35:44.000> in<01:35:44.320> our<01:35:44.560> calculator<01:35:45.440> we<01:35:45.679> have<01:35:45.760> a 01:35:45.910 --> 01:35:45.920 align:start position:0% here. Now in our calculator we have a 01:35:45.920 --> 01:35:48.709 align:start position:0% here. Now in our calculator we have a comment<01:35:46.239> in<01:35:46.639> row<01:35:46.719> number<01:35:47.040> 46<01:35:47.920> and<01:35:48.239> a<01:35:48.400> comment 01:35:48.709 --> 01:35:48.719 align:start position:0% comment in row number 46 and a comment 01:35:48.719 --> 01:35:51.350 align:start position:0% comment in row number 46 and a comment in<01:35:49.120> row<01:35:49.199> number<01:35:49.679> 102. 01:35:51.350 --> 01:35:51.360 align:start position:0% in row number 102. 01:35:51.360 --> 01:35:53.189 align:start position:0% in row number 102. After<01:35:51.600> that<01:35:51.920> there<01:35:52.159> is<01:35:52.239> a<01:35:52.400> comment<01:35:52.719> in<01:35:53.040> row 01:35:53.189 --> 01:35:53.199 align:start position:0% After that there is a comment in row 01:35:53.199 --> 01:35:55.750 align:start position:0% After that there is a comment in row number<01:35:53.520> 200<01:35:54.400> and<01:35:54.639> then<01:35:54.800> a<01:35:54.960> comment<01:35:55.280> in<01:35:55.679> row 01:35:55.750 --> 01:35:55.760 align:start position:0% number 200 and then a comment in row 01:35:55.760 --> 01:35:57.350 align:start position:0% number 200 and then a comment in row number<01:35:56.000> six. 01:35:57.350 --> 01:35:57.360 align:start position:0% number six. 01:35:57.360 --> 01:36:00.470 align:start position:0% number six. Now<01:35:57.600> what<01:35:57.840> we<01:35:58.000> have<01:35:58.159> to<01:35:58.320> do<01:35:58.480> here<01:35:58.719> is<01:35:59.199> I<01:35:59.440> can<01:35:59.679> say 01:36:00.470 --> 01:36:00.480 align:start position:0% Now what we have to do here is I can say 01:36:00.480 --> 01:36:03.750 align:start position:0% Now what we have to do here is I can say make<01:36:00.800> the<01:36:01.040> possible<01:36:01.520> changes<01:36:02.080> asked. 01:36:03.750 --> 01:36:03.760 align:start position:0% make the possible changes asked. 01:36:03.760 --> 01:36:05.430 align:start position:0% make the possible changes asked. Okay.<01:36:04.159> What<01:36:04.400> will<01:36:04.560> happen<01:36:04.800> here<01:36:05.040> is<01:36:05.280> that 01:36:05.430 --> 01:36:05.440 align:start position:0% Okay. What will happen here is that 01:36:05.440 --> 01:36:07.110 align:start position:0% Okay. What will happen here is that based<01:36:05.760> on<01:36:05.840> the<01:36:06.080> changes<01:36:06.320> we<01:36:06.560> included<01:36:06.960> in 01:36:07.110 --> 01:36:07.120 align:start position:0% based on the changes we included in 01:36:07.120 --> 01:36:09.270 align:start position:0% based on the changes we included in these<01:36:07.360> comments,<01:36:08.159> the<01:36:08.400> changes<01:36:08.800> will<01:36:09.040> happen 01:36:09.270 --> 01:36:09.280 align:start position:0% these comments, the changes will happen 01:36:09.280 --> 01:36:12.550 align:start position:0% these comments, the changes will happen at<01:36:09.600> those<01:36:09.920> exact<01:36:10.400> points.<01:36:11.679> I<01:36:11.920> will<01:36:12.080> only<01:36:12.400> show 01:36:12.550 --> 01:36:12.560 align:start position:0% at those exact points. I will only show 01:36:12.560 --> 01:36:14.550 align:start position:0% at those exact points. I will only show you<01:36:12.800> this<01:36:13.040> one<01:36:13.280> change<01:36:13.600> that<01:36:13.760> we<01:36:13.920> demanded<01:36:14.400> at 01:36:14.550 --> 01:36:14.560 align:start position:0% you this one change that we demanded at 01:36:14.560 --> 01:36:17.030 align:start position:0% you this one change that we demanded at the<01:36:14.719> end<01:36:14.800> in<01:36:14.960> the<01:36:15.120> comments.<01:36:16.239> We<01:36:16.480> will<01:36:16.639> see<01:36:16.880> how 01:36:17.030 --> 01:36:17.040 align:start position:0% the end in the comments. We will see how 01:36:17.040 --> 01:36:19.030 align:start position:0% the end in the comments. We will see how it<01:36:17.280> changes<01:36:17.600> the<01:36:17.840> name<01:36:18.000> of<01:36:18.159> our<01:36:18.400> scientific 01:36:19.030 --> 01:36:19.040 align:start position:0% it changes the name of our scientific 01:36:19.040 --> 01:36:21.750 align:start position:0% it changes the name of our scientific calculator<01:36:19.600> here.<01:36:20.480> And<01:36:20.719> this<01:36:21.040> is<01:36:21.199> a<01:36:21.440> very 01:36:21.750 --> 01:36:21.760 align:start position:0% calculator here. And this is a very 01:36:21.760 --> 01:36:24.629 align:start position:0% calculator here. And this is a very advanced<01:36:22.320> feature.<01:36:23.600> We<01:36:23.760> are<01:36:23.920> reviewing<01:36:24.320> our 01:36:24.629 --> 01:36:24.639 align:start position:0% advanced feature. We are reviewing our 01:36:24.639 --> 01:36:27.510 align:start position:0% advanced feature. We are reviewing our complete<01:36:25.199> AI<01:36:25.679> generated<01:36:26.239> changes<01:36:26.960> to<01:36:27.199> see<01:36:27.360> how 01:36:27.510 --> 01:36:27.520 align:start position:0% complete AI generated changes to see how 01:36:27.520 --> 01:36:29.510 align:start position:0% complete AI generated changes to see how our<01:36:27.760> reviews<01:36:28.159> can<01:36:28.320> be<01:36:28.400> applied<01:36:28.800> on<01:36:28.960> a<01:36:29.199> larger 01:36:29.510 --> 01:36:29.520 align:start position:0% our reviews can be applied on a larger 01:36:29.520 --> 01:36:32.790 align:start position:0% our reviews can be applied on a larger scale<01:36:30.159> and<01:36:30.400> how<01:36:30.639> we<01:36:30.800> can<01:36:30.960> include<01:36:31.280> them.<01:36:32.560> It 01:36:32.790 --> 01:36:32.800 align:start position:0% scale and how we can include them. It 01:36:32.800 --> 01:36:35.510 align:start position:0% scale and how we can include them. It will<01:36:32.960> take<01:36:33.120> some<01:36:33.360> time<01:36:33.520> to<01:36:33.760> think.<01:36:35.040> Obviously 01:36:35.510 --> 01:36:35.520 align:start position:0% will take some time to think. Obviously 01:36:35.520 --> 01:36:37.590 align:start position:0% will take some time to think. Obviously you<01:36:35.679> can<01:36:35.840> see<01:36:35.920> that<01:36:36.159> it<01:36:36.320> is<01:36:36.480> thinking<01:36:36.800> here<01:36:37.360> and 01:36:37.590 --> 01:36:37.600 align:start position:0% you can see that it is thinking here and 01:36:37.600 --> 01:36:39.990 align:start position:0% you can see that it is thinking here and after<01:36:37.840> that<01:36:38.159> it<01:36:38.400> says<01:36:39.120> I<01:36:39.360> will<01:36:39.520> apply<01:36:39.840> the 01:36:39.990 --> 01:36:40.000 align:start position:0% after that it says I will apply the 01:36:40.000 --> 01:36:42.470 align:start position:0% after that it says I will apply the review<01:36:40.320> comments<01:36:40.800> directly. 01:36:42.470 --> 01:36:42.480 align:start position:0% review comments directly. 01:36:42.480 --> 01:36:44.229 align:start position:0% review comments directly. First<01:36:42.719> of<01:36:42.800> all<01:36:43.040> our<01:36:43.280> name<01:36:43.520> will<01:36:43.679> be<01:36:43.840> changed<01:36:44.080> to 01:36:44.229 --> 01:36:44.239 align:start position:0% First of all our name will be changed to 01:36:44.239 --> 01:36:45.830 align:start position:0% First of all our name will be changed to metabrains. 01:36:45.830 --> 01:36:45.840 align:start position:0% metabrains. 01:36:45.840 --> 01:36:47.669 align:start position:0% metabrains. After<01:36:46.080> that<01:36:46.400> the<01:36:46.639> calculator<01:36:47.119> buttons<01:36:47.520> will 01:36:47.669 --> 01:36:47.679 align:start position:0% After that the calculator buttons will 01:36:47.679 --> 01:36:50.390 align:start position:0% After that the calculator buttons will be<01:36:47.760> made<01:36:48.000> circular.<01:36:49.280> A<01:36:49.600> few<01:36:49.760> practical 01:36:50.390 --> 01:36:50.400 align:start position:0% be made circular. A few practical 01:36:50.400 --> 01:36:53.189 align:start position:0% be made circular. A few practical scientific<01:36:51.040> buttons<01:36:51.440> will<01:36:51.679> be<01:36:51.760> included. 01:36:53.189 --> 01:36:53.199 align:start position:0% scientific buttons will be included. 01:36:53.199 --> 01:36:55.669 align:start position:0% scientific buttons will be included. Here<01:36:53.520> you<01:36:53.760> can<01:36:53.840> see<01:36:54.000> our<01:36:54.239> calculation. 01:36:55.669 --> 01:36:55.679 align:start position:0% Here you can see our calculation. 01:36:55.679 --> 01:36:58.950 align:start position:0% Here you can see our calculation. Metabrains<01:36:56.560> cal<01:36:56.960> is<01:36:57.199> written<01:36:57.440> here.<01:36:58.639> After 01:36:58.950 --> 01:36:58.960 align:start position:0% Metabrains cal is written here. After 01:36:58.960 --> 01:37:01.270 align:start position:0% Metabrains cal is written here. After that<01:36:59.600> we<01:36:59.840> also<01:37:00.159> included<01:37:00.560> a<01:37:00.800> comment<01:37:01.119> here 01:37:01.270 --> 01:37:01.280 align:start position:0% that we also included a comment here 01:37:01.280 --> 01:37:03.910 align:start position:0% that we also included a comment here that<01:37:01.520> we<01:37:01.679> want<01:37:01.840> our<01:37:02.000> buttons<01:37:02.400> to<01:37:02.560> be<01:37:02.719> rounded. 01:37:03.910 --> 01:37:03.920 align:start position:0% that we want our buttons to be rounded. 01:37:03.920 --> 01:37:06.709 align:start position:0% that we want our buttons to be rounded. So<01:37:04.400> you<01:37:04.719> can<01:37:04.800> see<01:37:04.960> that<01:37:05.119> by<01:37:05.440> including<01:37:05.920> height, 01:37:06.709 --> 01:37:06.719 align:start position:0% So you can see that by including height, 01:37:06.719 --> 01:37:09.430 align:start position:0% So you can see that by including height, aspect<01:37:07.199> ratio,<01:37:08.080> border<01:37:08.560> radius<01:37:09.040> and<01:37:09.280> all 01:37:09.430 --> 01:37:09.440 align:start position:0% aspect ratio, border radius and all 01:37:09.440 --> 01:37:11.510 align:start position:0% aspect ratio, border radius and all these<01:37:09.679> things.<01:37:10.400> It<01:37:10.560> has<01:37:10.800> provided<01:37:11.119> us<01:37:11.360> with 01:37:11.510 --> 01:37:11.520 align:start position:0% these things. It has provided us with 01:37:11.520 --> 01:37:13.109 align:start position:0% these things. It has provided us with some<01:37:11.679> rounded<01:37:12.159> buttons<01:37:12.560> that<01:37:12.719> we<01:37:12.960> can 01:37:13.109 --> 01:37:13.119 align:start position:0% some rounded buttons that we can 01:37:13.119 --> 01:37:16.390 align:start position:0% some rounded buttons that we can directly<01:37:13.520> see<01:37:13.840> here.<01:37:15.199> All<01:37:15.280> right.<01:37:16.000> So<01:37:16.239> all 01:37:16.390 --> 01:37:16.400 align:start position:0% directly see here. All right. So all 01:37:16.400 --> 01:37:18.229 align:start position:0% directly see here. All right. So all these<01:37:16.719> things<01:37:16.880> are<01:37:17.119> greatly<01:37:17.440> included<01:37:17.840> in<01:37:18.080> our 01:37:18.229 --> 01:37:18.239 align:start position:0% these things are greatly included in our 01:37:18.239 --> 01:37:21.270 align:start position:0% these things are greatly included in our working<01:37:18.639> process<01:37:19.040> here<01:37:19.920> and<01:37:20.239> through<01:37:20.480> this<01:37:21.040> we 01:37:21.270 --> 01:37:21.280 align:start position:0% working process here and through this we 01:37:21.280 --> 01:37:23.270 align:start position:0% working process here and through this we can<01:37:21.440> include<01:37:21.760> it<01:37:21.920> in<01:37:22.080> our<01:37:22.239> system<01:37:22.719> and<01:37:22.960> it<01:37:23.119> will 01:37:23.270 --> 01:37:23.280 align:start position:0% can include it in our system and it will 01:37:23.280 --> 01:37:26.149 align:start position:0% can include it in our system and it will work<01:37:23.520> here.<01:37:24.960> Now<01:37:25.199> we<01:37:25.440> will<01:37:25.600> get<01:37:25.760> all<01:37:25.920> our 01:37:26.149 --> 01:37:26.159 align:start position:0% work here. Now we will get all our 01:37:26.159 --> 01:37:28.790 align:start position:0% work here. Now we will get all our changes<01:37:26.560> here.<01:37:27.600> You<01:37:27.840> can<01:37:28.000> see<01:37:28.080> that<01:37:28.320> whatever 01:37:28.790 --> 01:37:28.800 align:start position:0% changes here. You can see that whatever 01:37:28.800 --> 01:37:31.109 align:start position:0% changes here. You can see that whatever visual<01:37:29.119> changes<01:37:29.520> we<01:37:29.760> have<01:37:30.320> it<01:37:30.560> has<01:37:30.719> included 01:37:31.109 --> 01:37:31.119 align:start position:0% visual changes we have it has included 01:37:31.119 --> 01:37:33.109 align:start position:0% visual changes we have it has included some<01:37:31.360> lines<01:37:31.679> in<01:37:31.840> a<01:37:32.000> file<01:37:32.239> and<01:37:32.480> showed<01:37:32.719> us<01:37:32.880> the 01:37:33.109 --> 01:37:33.119 align:start position:0% some lines in a file and showed us the 01:37:33.119 --> 01:37:35.830 align:start position:0% some lines in a file and showed us the changes<01:37:33.440> here.<01:37:34.560> We<01:37:34.800> can<01:37:34.960> also<01:37:35.280> open<01:37:35.520> that 01:37:35.830 --> 01:37:35.840 align:start position:0% changes here. We can also open that 01:37:35.840 --> 01:37:39.189 align:start position:0% changes here. We can also open that here.<01:37:37.040> Okay.<01:37:37.679> After<01:37:38.000> that<01:37:38.560> for<01:37:38.800> the<01:37:38.960> next 01:37:39.189 --> 01:37:39.199 align:start position:0% here. Okay. After that for the next 01:37:39.199 --> 01:37:41.189 align:start position:0% here. Okay. After that for the next changes<01:37:39.600> it<01:37:39.840> makes<01:37:40.400> you<01:37:40.639> can<01:37:40.800> see<01:37:40.960> our 01:37:41.189 --> 01:37:41.199 align:start position:0% changes it makes you can see our 01:37:41.199 --> 01:37:43.830 align:start position:0% changes it makes you can see our thinking<01:37:41.600> process<01:37:42.000> here.<01:37:43.119> In<01:37:43.360> the<01:37:43.520> thinking 01:37:43.830 --> 01:37:43.840 align:start position:0% thinking process here. In the thinking 01:37:43.840 --> 01:37:46.390 align:start position:0% thinking process here. In the thinking process<01:37:44.719> as<01:37:44.880> it<01:37:45.119> is<01:37:45.280> including<01:37:45.679> our<01:37:45.920> constants 01:37:46.390 --> 01:37:46.400 align:start position:0% process as it is including our constants 01:37:46.400 --> 01:37:48.709 align:start position:0% process as it is including our constants and<01:37:46.639> other<01:37:46.880> values<01:37:47.679> these<01:37:48.080> files<01:37:48.480> will 01:37:48.709 --> 01:37:48.719 align:start position:0% and other values these files will 01:37:48.719 --> 01:37:51.750 align:start position:0% and other values these files will automatically<01:37:49.360> come<01:37:49.600> here<01:37:49.840> side<01:37:50.080> by<01:37:50.320> side. 01:37:51.750 --> 01:37:51.760 align:start position:0% automatically come here side by side. 01:37:51.760 --> 01:37:54.470 align:start position:0% automatically come here side by side. Now<01:37:52.000> it<01:37:52.159> has<01:37:52.320> updated<01:37:52.719> our<01:37:52.960> file.<01:37:53.920> We<01:37:54.159> have<01:37:54.320> all 01:37:54.470 --> 01:37:54.480 align:start position:0% Now it has updated our file. We have all 01:37:54.480 --> 01:37:56.870 align:start position:0% Now it has updated our file. We have all the<01:37:54.719> commands<01:37:55.119> here.<01:37:55.920> As<01:37:56.159> soon<01:37:56.320> as<01:37:56.480> we<01:37:56.639> open 01:37:56.870 --> 01:37:56.880 align:start position:0% the commands here. As soon as we open 01:37:56.880 --> 01:37:59.030 align:start position:0% the commands here. As soon as we open this<01:37:57.040> in<01:37:57.199> our<01:37:57.440> browser<01:37:58.159> all<01:37:58.320> our<01:37:58.560> discussed 01:37:59.030 --> 01:37:59.040 align:start position:0% this in our browser all our discussed 01:37:59.040 --> 01:38:02.470 align:start position:0% this in our browser all our discussed changes<01:37:59.360> are<01:37:59.600> here<01:38:00.159> like<01:38:00.480> metabrains<01:38:01.280> cal<01:38:02.239> our 01:38:02.470 --> 01:38:02.480 align:start position:0% changes are here like metabrains cal our 01:38:02.480 --> 01:38:05.669 align:start position:0% changes are here like metabrains cal our buttons<01:38:02.880> have<01:38:03.040> become<01:38:03.360> rounded<01:38:04.719> and<01:38:04.960> now<01:38:05.440> if 01:38:05.669 --> 01:38:05.679 align:start position:0% buttons have become rounded and now if 01:38:05.679 --> 01:38:08.070 align:start position:0% buttons have become rounded and now if we<01:38:05.840> include<01:38:06.239> anything<01:38:06.639> here<01:38:07.280> that<01:38:07.600> thing<01:38:07.760> will 01:38:08.070 --> 01:38:08.080 align:start position:0% we include anything here that thing will 01:38:08.080 --> 01:38:11.189 align:start position:0% we include anything here that thing will automatically<01:38:08.639> be<01:38:08.880> directly<01:38:09.360> included<01:38:09.840> here. 01:38:11.189 --> 01:38:11.199 align:start position:0% automatically be directly included here. 01:38:11.199 --> 01:38:13.590 align:start position:0% automatically be directly included here. Okay,<01:38:11.520> our<01:38:11.920> error<01:38:12.159> came<01:38:12.400> here.<01:38:12.880> We<01:38:13.119> are<01:38:13.280> seeing 01:38:13.590 --> 01:38:13.600 align:start position:0% Okay, our error came here. We are seeing 01:38:13.600 --> 01:38:16.229 align:start position:0% Okay, our error came here. We are seeing everything<01:38:14.000> working.<01:38:15.199> All<01:38:15.280> right.<01:38:15.840> If<01:38:16.080> we 01:38:16.229 --> 01:38:16.239 align:start position:0% everything working. All right. If we 01:38:16.239 --> 01:38:18.709 align:start position:0% everything working. All right. If we suppose<01:38:16.560> we<01:38:16.800> need<01:38:16.960> the<01:38:17.199> value<01:38:17.360> of<01:38:17.520> pi<01:38:17.920> here,<01:38:18.480> we 01:38:18.709 --> 01:38:18.719 align:start position:0% suppose we need the value of pi here, we 01:38:18.719 --> 01:38:20.870 align:start position:0% suppose we need the value of pi here, we get<01:38:18.800> our<01:38:19.040> pi<01:38:19.360> value.<01:38:20.000> If<01:38:20.159> we<01:38:20.320> need<01:38:20.480> the<01:38:20.719> value 01:38:20.870 --> 01:38:20.880 align:start position:0% get our pi value. If we need the value 01:38:20.880 --> 01:38:24.470 align:start position:0% get our pi value. If we need the value of<01:38:21.040> log<01:38:21.440> 8,<01:38:21.840> we<01:38:22.080> can<01:38:22.239> directly<01:38:22.719> input<01:38:23.040> it<01:38:23.280> here. 01:38:24.470 --> 01:38:24.480 align:start position:0% of log 8, we can directly input it here. 01:38:24.480 --> 01:38:26.149 align:start position:0% of log 8, we can directly input it here. Also,<01:38:24.880> you<01:38:25.119> can<01:38:25.199> see<01:38:25.360> that<01:38:25.520> this<01:38:25.760> delete 01:38:26.149 --> 01:38:26.159 align:start position:0% Also, you can see that this delete 01:38:26.159 --> 01:38:29.510 align:start position:0% Also, you can see that this delete option<01:38:26.480> is<01:38:26.719> working<01:38:27.040> directly<01:38:27.440> here<01:38:27.840> too. 01:38:29.510 --> 01:38:29.520 align:start position:0% option is working directly here too. 01:38:29.520 --> 01:38:31.910 align:start position:0% option is working directly here too. If<01:38:29.679> we<01:38:29.840> look<01:38:30.000> at<01:38:30.159> all<01:38:30.239> the<01:38:30.400> signs<01:38:30.800> here,<01:38:31.679> every 01:38:31.910 --> 01:38:31.920 align:start position:0% If we look at all the signs here, every 01:38:31.920 --> 01:38:33.750 align:start position:0% If we look at all the signs here, every sign<01:38:32.239> that<01:38:32.400> we<01:38:32.560> have<01:38:32.719> is<01:38:33.040> working<01:38:33.360> very 01:38:33.750 --> 01:38:33.760 align:start position:0% sign that we have is working very 01:38:33.760 --> 01:38:36.790 align:start position:0% sign that we have is working very easily.<01:38:35.119> We<01:38:35.360> can<01:38:35.520> directly<01:38:36.000> enter<01:38:36.400> all<01:38:36.560> our 01:38:36.790 --> 01:38:36.800 align:start position:0% easily. We can directly enter all our 01:38:36.800 --> 01:38:38.950 align:start position:0% easily. We can directly enter all our values<01:38:37.199> here. 01:38:38.950 --> 01:38:38.960 align:start position:0% values here. 01:38:38.960 --> 01:38:41.350 align:start position:0% values here. If<01:38:39.199> there<01:38:39.360> is<01:38:39.520> no<01:38:39.679> responsiveness,<01:38:40.880> we<01:38:41.119> can<01:38:41.199> go 01:38:41.350 --> 01:38:41.360 align:start position:0% If there is no responsiveness, we can go 01:38:41.360 --> 01:38:42.790 align:start position:0% If there is no responsiveness, we can go ahead<01:38:41.679> and<01:38:41.920> directly<01:38:42.400> include 01:38:42.790 --> 01:38:42.800 align:start position:0% ahead and directly include 01:38:42.800 --> 01:38:45.910 align:start position:0% ahead and directly include responsiveness<01:38:43.520> in<01:38:43.760> our<01:38:43.920> code<01:38:44.239> later.<01:38:45.679> But 01:38:45.910 --> 01:38:45.920 align:start position:0% responsiveness in our code later. But 01:38:45.920 --> 01:38:47.830 align:start position:0% responsiveness in our code later. But code<01:38:46.239> review<01:38:46.639> is<01:38:46.800> the<01:38:47.040> main<01:38:47.280> thing<01:38:47.440> that<01:38:47.679> I 01:38:47.830 --> 01:38:47.840 align:start position:0% code review is the main thing that I 01:38:47.840 --> 01:38:51.350 align:start position:0% code review is the main thing that I have<01:38:48.000> discussed<01:38:48.320> with<01:38:48.560> you.<01:38:50.000> After<01:38:50.400> this,<01:38:51.119> our 01:38:51.350 --> 01:38:51.360 align:start position:0% have discussed with you. After this, our 01:38:51.360 --> 01:38:53.350 align:start position:0% have discussed with you. After this, our next<01:38:51.600> discussion<01:38:52.080> is<01:38:52.320> related<01:38:52.639> to<01:38:52.800> our<01:38:53.040> prompt 01:38:53.350 --> 01:38:53.360 align:start position:0% next discussion is related to our prompt 01:38:53.360 --> 01:38:55.910 align:start position:0% next discussion is related to our prompt hints.<01:38:54.159> Next,<01:38:54.480> we<01:38:54.719> discuss<01:38:55.040> the<01:38:55.280> main<01:38:55.520> usage 01:38:55.910 --> 01:38:55.920 align:start position:0% hints. Next, we discuss the main usage 01:38:55.920 --> 01:38:59.030 align:start position:0% hints. Next, we discuss the main usage of<01:38:56.080> a<01:38:56.239> prompt<01:38:56.639> library.<01:38:58.080> We<01:38:58.239> will<01:38:58.480> see<01:38:58.639> how<01:38:58.800> we 01:38:59.030 --> 01:38:59.040 align:start position:0% of a prompt library. We will see how we 01:38:59.040 --> 01:39:00.950 align:start position:0% of a prompt library. We will see how we can<01:38:59.119> use<01:38:59.360> it<01:38:59.600> and<01:38:59.840> where<01:39:00.080> more<01:39:00.400> options<01:39:00.719> are 01:39:00.950 --> 01:39:00.960 align:start position:0% can use it and where more options are 01:39:00.960 --> 01:39:02.470 align:start position:0% can use it and where more options are included. 01:39:02.470 --> 01:39:02.480 align:start position:0% included. 01:39:02.480 --> 01:39:05.350 align:start position:0% included. First,<01:39:02.800> I<01:39:03.040> come<01:39:03.280> here.<01:39:04.400> Instead<01:39:04.719> of<01:39:04.960> using 01:39:05.350 --> 01:39:05.360 align:start position:0% First, I come here. Instead of using 01:39:05.360 --> 01:39:07.350 align:start position:0% First, I come here. Instead of using everything,<01:39:06.159> I<01:39:06.400> will<01:39:06.560> search<01:39:06.800> the<01:39:06.960> prompt 01:39:07.350 --> 01:39:07.360 align:start position:0% everything, I will search the prompt 01:39:07.360 --> 01:39:09.750 align:start position:0% everything, I will search the prompt library<01:39:07.679> in<01:39:07.920> codeex. 01:39:09.750 --> 01:39:09.760 align:start position:0% library in codeex. 01:39:09.760 --> 01:39:12.550 align:start position:0% library in codeex. Here<01:39:10.000> you<01:39:10.239> see<01:39:10.560> codeex<01:39:11.040> prompting. 01:39:12.550 --> 01:39:12.560 align:start position:0% Here you see codeex prompting. 01:39:12.560 --> 01:39:14.470 align:start position:0% Here you see codeex prompting. First,<01:39:12.880> I<01:39:13.119> tell<01:39:13.280> you<01:39:13.520> this<01:39:13.679> is<01:39:13.760> a<01:39:13.920> built-in 01:39:14.470 --> 01:39:14.480 align:start position:0% First, I tell you this is a built-in 01:39:14.480 --> 01:39:16.790 align:start position:0% First, I tell you this is a built-in collection<01:39:15.199> of<01:39:15.440> reusable<01:39:16.080> workflows, 01:39:16.790 --> 01:39:16.800 align:start position:0% collection of reusable workflows, 01:39:16.800 --> 01:39:19.830 align:start position:0% collection of reusable workflows, templates,<01:39:17.360> and<01:39:17.600> skills<01:39:18.320> in<01:39:18.560> OpenAI<01:39:19.280> codeex 01:39:19.830 --> 01:39:19.840 align:start position:0% templates, and skills in OpenAI codeex 01:39:19.840 --> 01:39:22.310 align:start position:0% templates, and skills in OpenAI codeex and<01:39:20.000> Agentic<01:39:20.639> CLI. 01:39:22.310 --> 01:39:22.320 align:start position:0% and Agentic CLI. 01:39:22.320 --> 01:39:24.790 align:start position:0% and Agentic CLI. When<01:39:22.560> I<01:39:22.719> go<01:39:22.800> to<01:39:23.040> prompting,<01:39:23.920> you<01:39:24.080> see<01:39:24.239> we<01:39:24.480> often 01:39:24.790 --> 01:39:24.800 align:start position:0% When I go to prompting, you see we often 01:39:24.800 --> 01:39:26.709 align:start position:0% When I go to prompting, you see we often use<01:39:25.119> prompts. 01:39:26.709 --> 01:39:26.719 align:start position:0% use prompts. 01:39:26.719 --> 01:39:28.790 align:start position:0% use prompts. You<01:39:26.960> interact<01:39:27.360> with<01:39:27.520> the<01:39:27.679> codeex<01:39:28.239> by<01:39:28.400> sending 01:39:28.790 --> 01:39:28.800 align:start position:0% You interact with the codeex by sending 01:39:28.800 --> 01:39:31.590 align:start position:0% You interact with the codeex by sending prompts<01:39:29.119> that<01:39:29.440> describe<01:39:29.840> what<01:39:30.080> you<01:39:30.239> want. 01:39:31.590 --> 01:39:31.600 align:start position:0% prompts that describe what you want. 01:39:31.600 --> 01:39:34.310 align:start position:0% prompts that describe what you want. Example<01:39:32.080> prompts<01:39:32.480> are<01:39:32.639> shown<01:39:32.880> here. 01:39:34.310 --> 01:39:34.320 align:start position:0% Example prompts are shown here. 01:39:34.320 --> 01:39:37.189 align:start position:0% Example prompts are shown here. Thread<01:39:34.719> is<01:39:34.880> a<01:39:35.119> single<01:39:35.360> session.<01:39:36.560> It<01:39:36.800> has<01:39:36.960> your 01:39:37.189 --> 01:39:37.199 align:start position:0% Thread is a single session. It has your 01:39:37.199 --> 01:39:39.590 align:start position:0% Thread is a single session. It has your prompt<01:39:37.760> plus<01:39:38.080> the<01:39:38.239> model<01:39:38.560> outputs<01:39:39.040> and<01:39:39.280> tool 01:39:39.590 --> 01:39:39.600 align:start position:0% prompt plus the model outputs and tool 01:39:39.600 --> 01:39:42.790 align:start position:0% prompt plus the model outputs and tool calls<01:39:39.920> that<01:39:40.159> follow.<01:39:41.600> A<01:39:41.840> thread<01:39:42.159> can<01:39:42.400> include 01:39:42.790 --> 01:39:42.800 align:start position:0% calls that follow. A thread can include 01:39:42.800 --> 01:39:45.590 align:start position:0% calls that follow. A thread can include multiple<01:39:43.199> prompts.<01:39:44.480> We<01:39:44.719> use<01:39:44.880> a<01:39:45.119> chain<01:39:45.360> of 01:39:45.590 --> 01:39:45.600 align:start position:0% multiple prompts. We use a chain of 01:39:45.600 --> 01:39:48.550 align:start position:0% multiple prompts. We use a chain of process<01:39:46.000> to<01:39:46.239> take<01:39:46.400> things<01:39:46.639> forward.<01:39:48.080> I<01:39:48.320> will 01:39:48.550 --> 01:39:48.560 align:start position:0% process to take things forward. I will 01:39:48.560 --> 01:39:50.790 align:start position:0% process to take things forward. I will explain<01:39:48.880> this<01:39:49.119> exact<01:39:49.600> process<01:39:50.159> right<01:39:50.400> here<01:39:50.560> in 01:39:50.790 --> 01:39:50.800 align:start position:0% explain this exact process right here in 01:39:50.800 --> 01:39:52.470 align:start position:0% explain this exact process right here in our<01:39:50.960> codeex. 01:39:52.470 --> 01:39:52.480 align:start position:0% our codeex. 01:39:52.480 --> 01:39:54.950 align:start position:0% our codeex. In<01:39:52.800> codeex,<01:39:53.440> we<01:39:53.679> go<01:39:53.760> to<01:39:53.920> our<01:39:54.159> main<01:39:54.480> user 01:39:54.950 --> 01:39:54.960 align:start position:0% In codeex, we go to our main user 01:39:54.960 --> 01:39:56.629 align:start position:0% In codeex, we go to our main user settings. 01:39:56.629 --> 01:39:56.639 align:start position:0% settings. 01:39:56.639 --> 01:39:58.229 align:start position:0% settings. Inside<01:39:57.040> these<01:39:57.360> settings,<01:39:57.760> we<01:39:58.000> have 01:39:58.229 --> 01:39:58.239 align:start position:0% Inside these settings, we have 01:39:58.239 --> 01:40:00.390 align:start position:0% Inside these settings, we have personalization. 01:40:00.390 --> 01:40:00.400 align:start position:0% personalization. 01:40:00.400 --> 01:40:02.790 align:start position:0% personalization. In<01:40:00.639> personalization,<01:40:01.840> our<01:40:02.159> own<01:40:02.400> custom 01:40:02.790 --> 01:40:02.800 align:start position:0% In personalization, our own custom 01:40:02.800 --> 01:40:05.109 align:start position:0% In personalization, our own custom instructions<01:40:03.440> are<01:40:03.600> included. 01:40:05.109 --> 01:40:05.119 align:start position:0% instructions are included. 01:40:05.119 --> 01:40:07.590 align:start position:0% instructions are included. We<01:40:05.440> can<01:40:05.520> also<01:40:05.840> switch<01:40:06.159> our<01:40:06.400> AI<01:40:06.800> personality 01:40:07.590 --> 01:40:07.600 align:start position:0% We can also switch our AI personality 01:40:07.600 --> 01:40:10.390 align:start position:0% We can also switch our AI personality from<01:40:07.840> pragmatic<01:40:08.560> to<01:40:08.800> friendly. 01:40:10.390 --> 01:40:10.400 align:start position:0% from pragmatic to friendly. 01:40:10.400 --> 01:40:12.310 align:start position:0% from pragmatic to friendly. Both<01:40:10.719> of<01:40:10.800> these<01:40:11.119> personalization<01:40:11.920> options 01:40:12.310 --> 01:40:12.320 align:start position:0% Both of these personalization options 01:40:12.320 --> 01:40:16.070 align:start position:0% Both of these personalization options are<01:40:12.560> here.<01:40:13.920> In<01:40:14.239> custom<01:40:14.639> instructions,<01:40:15.679> we<01:40:15.920> can 01:40:16.070 --> 01:40:16.080 align:start position:0% are here. In custom instructions, we can 01:40:16.080 --> 01:40:18.470 align:start position:0% are here. In custom instructions, we can include<01:40:16.560> all<01:40:16.880> custommade<01:40:17.760> personalized 01:40:18.470 --> 01:40:18.480 align:start position:0% include all custommade personalized 01:40:18.480 --> 01:40:21.669 align:start position:0% include all custommade personalized instructions<01:40:19.280> that<01:40:19.520> we<01:40:19.760> want<01:40:19.920> in<01:40:20.159> our<01:40:20.320> tool. 01:40:21.669 --> 01:40:21.679 align:start position:0% instructions that we want in our tool. 01:40:21.679 --> 01:40:23.590 align:start position:0% instructions that we want in our tool. It<01:40:21.920> is<01:40:22.080> quite<01:40:22.320> simple<01:40:22.560> to<01:40:22.800> include<01:40:23.040> our<01:40:23.280> text 01:40:23.590 --> 01:40:23.600 align:start position:0% It is quite simple to include our text 01:40:23.600 --> 01:40:25.270 align:start position:0% It is quite simple to include our text responses. 01:40:25.270 --> 01:40:25.280 align:start position:0% responses. 01:40:25.280 --> 01:40:27.750 align:start position:0% responses. But<01:40:25.520> sometimes<01:40:26.480> we<01:40:26.719> must<01:40:27.040> see<01:40:27.199> our<01:40:27.440> clear 01:40:27.750 --> 01:40:27.760 align:start position:0% But sometimes we must see our clear 01:40:27.760 --> 01:40:29.910 align:start position:0% But sometimes we must see our clear deviation<01:40:28.639> and<01:40:28.960> how<01:40:29.119> we<01:40:29.280> are<01:40:29.440> working<01:40:29.679> on 01:40:29.910 --> 01:40:29.920 align:start position:0% deviation and how we are working on 01:40:29.920 --> 01:40:32.229 align:start position:0% deviation and how we are working on stuff<01:40:30.560> and<01:40:30.800> how<01:40:30.960> these<01:40:31.280> custom<01:40:31.679> instructions 01:40:32.229 --> 01:40:32.239 align:start position:0% stuff and how these custom instructions 01:40:32.239 --> 01:40:35.350 align:start position:0% stuff and how these custom instructions work.<01:40:33.679> We<01:40:33.920> have<01:40:34.080> our<01:40:34.320> memory<01:40:34.800> which<01:40:35.040> we<01:40:35.199> can 01:40:35.350 --> 01:40:35.360 align:start position:0% work. We have our memory which we can 01:40:35.360 --> 01:40:37.430 align:start position:0% work. We have our memory which we can induce<01:40:35.840> right<01:40:36.080> here<01:40:36.320> in<01:40:36.560> our<01:40:36.719> experimental 01:40:37.430 --> 01:40:37.440 align:start position:0% induce right here in our experimental 01:40:37.440 --> 01:40:39.030 align:start position:0% induce right here in our experimental form. 01:40:39.030 --> 01:40:39.040 align:start position:0% form. 01:40:39.040 --> 01:40:41.430 align:start position:0% form. We<01:40:39.280> see<01:40:39.440> how<01:40:39.679> our<01:40:39.920> things<01:40:40.239> can<01:40:40.400> be<01:40:40.560> included 01:40:41.430 --> 01:40:41.440 align:start position:0% We see how our things can be included 01:40:41.440 --> 01:40:43.590 align:start position:0% We see how our things can be included and<01:40:41.679> how<01:40:41.920> we<01:40:42.080> can<01:40:42.239> take<01:40:42.480> our<01:40:42.719> many<01:40:43.040> processes 01:40:43.590 --> 01:40:43.600 align:start position:0% and how we can take our many processes 01:40:43.600 --> 01:40:45.270 align:start position:0% and how we can take our many processes forward. 01:40:45.270 --> 01:40:45.280 align:start position:0% forward. 01:40:45.280 --> 01:40:47.189 align:start position:0% forward. Our<01:40:45.520> standard<01:40:45.920> options<01:40:46.400> show<01:40:46.639> how<01:40:46.800> we<01:40:47.040> will 01:40:47.189 --> 01:40:47.199 align:start position:0% Our standard options show how we will 01:40:47.199 --> 01:40:49.830 align:start position:0% Our standard options show how we will best<01:40:47.440> include<01:40:47.840> our<01:40:48.080> own<01:40:48.239> memory. 01:40:49.830 --> 01:40:49.840 align:start position:0% best include our own memory. 01:40:49.840 --> 01:40:53.189 align:start position:0% best include our own memory. First<01:40:50.159> is<01:40:50.400> the<01:40:50.560> main<01:40:50.960> enable<01:40:51.440> memories. 01:40:53.189 --> 01:40:53.199 align:start position:0% First is the main enable memories. 01:40:53.199 --> 01:40:55.109 align:start position:0% First is the main enable memories. Second<01:40:53.520> is<01:40:53.760> our<01:40:54.000> good<01:40:54.239> tool<01:40:54.719> assisted 01:40:55.109 --> 01:40:55.119 align:start position:0% Second is our good tool assisted 01:40:55.119 --> 01:40:56.709 align:start position:0% Second is our good tool assisted memories. 01:40:56.709 --> 01:40:56.719 align:start position:0% memories. 01:40:56.719 --> 01:40:58.709 align:start position:0% memories. We<01:40:56.960> can<01:40:57.119> also<01:40:57.440> involve<01:40:57.920> tool<01:40:58.320> assisted 01:40:58.709 --> 01:40:58.719 align:start position:0% We can also involve tool assisted 01:40:58.719 --> 01:41:01.590 align:start position:0% We can also involve tool assisted memories<01:40:59.520> and<01:40:59.840> involve<01:41:00.320> all<01:41:00.560> our<01:41:00.880> process<01:41:01.360> or 01:41:01.590 --> 01:41:01.600 align:start position:0% memories and involve all our process or 01:41:01.600 --> 01:41:03.990 align:start position:0% memories and involve all our process or workability<01:41:02.239> in<01:41:02.480> it. 01:41:03.990 --> 01:41:04.000 align:start position:0% workability in it. 01:41:04.000 --> 01:41:05.990 align:start position:0% workability in it. Next<01:41:04.320> thing<01:41:04.560> is<01:41:04.800> our<01:41:05.040> own<01:41:05.199> custom<01:41:05.679> prompt 01:41:05.990 --> 01:41:06.000 align:start position:0% Next thing is our own custom prompt 01:41:06.000 --> 01:41:07.510 align:start position:0% Next thing is our own custom prompt libraries. 01:41:07.510 --> 01:41:07.520 align:start position:0% libraries. 01:41:07.520 --> 01:41:10.070 align:start position:0% libraries. What<01:41:07.679> is<01:41:07.840> a<01:41:08.000> good<01:41:08.239> prompt<01:41:08.560> library? 01:41:10.070 --> 01:41:10.080 align:start position:0% What is a good prompt library? 01:41:10.080 --> 01:41:11.910 align:start position:0% What is a good prompt library? I<01:41:10.320> will<01:41:10.480> tell<01:41:10.639> you<01:41:10.880> first<01:41:11.119> that<01:41:11.360> our<01:41:11.520> prompt 01:41:11.910 --> 01:41:11.920 align:start position:0% I will tell you first that our prompt 01:41:11.920 --> 01:41:15.430 align:start position:0% I will tell you first that our prompt library<01:41:12.320> is<01:41:12.480> a<01:41:12.719> great<01:41:13.119> reusable<01:41:13.760> prompt<01:41:14.159> hub. 01:41:15.430 --> 01:41:15.440 align:start position:0% library is a great reusable prompt hub. 01:41:15.440 --> 01:41:17.510 align:start position:0% library is a great reusable prompt hub. In<01:41:15.679> this<01:41:15.920> we<01:41:16.159> can<01:41:16.320> do<01:41:16.400> our<01:41:16.639> text<01:41:16.960> discussion 01:41:17.510 --> 01:41:17.520 align:start position:0% In this we can do our text discussion 01:41:17.520 --> 01:41:19.350 align:start position:0% In this we can do our text discussion multiple<01:41:18.080> times. 01:41:19.350 --> 01:41:19.360 align:start position:0% multiple times. 01:41:19.360 --> 01:41:21.270 align:start position:0% multiple times. We<01:41:19.600> can<01:41:19.760> do<01:41:19.920> multiple<01:41:20.400> workings<01:41:20.880> for<01:41:21.040> our 01:41:21.270 --> 01:41:21.280 align:start position:0% We can do multiple workings for our 01:41:21.280 --> 01:41:24.550 align:start position:0% We can do multiple workings for our single<01:41:21.600> tool.<01:41:22.880> We<01:41:23.199> must<01:41:23.440> see<01:41:23.760> one<01:41:24.080> more<01:41:24.320> thing 01:41:24.550 --> 01:41:24.560 align:start position:0% single tool. We must see one more thing 01:41:24.560 --> 01:41:28.470 align:start position:0% single tool. We must see one more thing here<01:41:25.920> from<01:41:26.159> the<01:41:26.320> chat<01:41:26.639> GPT<01:41:27.199> side.<01:41:27.920> There<01:41:28.080> is<01:41:28.239> no 01:41:28.470 --> 01:41:28.480 align:start position:0% here from the chat GPT side. There is no 01:41:28.480 --> 01:41:31.430 align:start position:0% here from the chat GPT side. There is no prompt<01:41:28.880> library<01:41:29.199> available<01:41:29.679> here<01:41:30.000> yet.<01:41:31.199> We 01:41:31.430 --> 01:41:31.440 align:start position:0% prompt library available here yet. We 01:41:31.440 --> 01:41:33.189 align:start position:0% prompt library available here yet. We have<01:41:31.600> clear<01:41:32.000> information<01:41:32.480> about<01:41:32.800> basic 01:41:33.189 --> 01:41:33.199 align:start position:0% have clear information about basic 01:41:33.199 --> 01:41:35.669 align:start position:0% have clear information about basic prompting.<01:41:34.639> But<01:41:34.800> if<01:41:34.960> I<01:41:35.119> talk<01:41:35.360> about<01:41:35.520> the 01:41:35.669 --> 01:41:35.679 align:start position:0% prompting. But if I talk about the 01:41:35.679 --> 01:41:37.990 align:start position:0% prompting. But if I talk about the claude<01:41:36.159> code,<01:41:36.800> there<01:41:36.960> is<01:41:37.040> a<01:41:37.280> distinct<01:41:37.679> prompt 01:41:37.990 --> 01:41:38.000 align:start position:0% claude code, there is a distinct prompt 01:41:38.000 --> 01:41:40.149 align:start position:0% claude code, there is a distinct prompt library<01:41:38.400> available.<01:41:39.119> We<01:41:39.360> can<01:41:39.520> go<01:41:39.679> there<01:41:39.920> and 01:41:40.149 --> 01:41:40.159 align:start position:0% library available. We can go there and 01:41:40.159 --> 01:41:41.990 align:start position:0% library available. We can go there and see<01:41:40.320> the<01:41:40.560> many<01:41:40.800> prompts<01:41:41.199> are<01:41:41.360> collected<01:41:41.760> from 01:41:41.990 --> 01:41:42.000 align:start position:0% see the many prompts are collected from 01:41:42.000 --> 01:41:45.189 align:start position:0% see the many prompts are collected from the<01:41:42.239> various<01:41:42.639> anthropic<01:41:43.280> guides. 01:41:45.189 --> 01:41:45.199 align:start position:0% the various anthropic guides. 01:41:45.199 --> 01:41:47.510 align:start position:0% the various anthropic guides. This<01:41:45.520> includes<01:41:46.000> our<01:41:46.320> common<01:41:46.639> workflows<01:41:47.199> and 01:41:47.510 --> 01:41:47.520 align:start position:0% This includes our common workflows and 01:41:47.520 --> 01:41:50.390 align:start position:0% This includes our common workflows and best<01:41:47.840> practices<01:41:48.880> and<01:41:49.119> how<01:41:49.520> anthropic<01:41:50.000> teams 01:41:50.390 --> 01:41:50.400 align:start position:0% best practices and how anthropic teams 01:41:50.400 --> 01:41:53.270 align:start position:0% best practices and how anthropic teams take<01:41:50.719> clawed<01:41:51.119> code<01:41:51.440> forward. 01:41:53.270 --> 01:41:53.280 align:start position:0% take clawed code forward. 01:41:53.280 --> 01:41:55.910 align:start position:0% take clawed code forward. If<01:41:53.520> I<01:41:53.760> want,<01:41:54.239> we<01:41:54.480> can<01:41:54.639> also<01:41:54.960> see<01:41:55.119> the<01:41:55.440> core 01:41:55.910 --> 01:41:55.920 align:start position:0% If I want, we can also see the core 01:41:55.920 --> 01:41:58.870 align:start position:0% If I want, we can also see the core understand<01:41:56.560> prompts.<01:41:57.920> We<01:41:58.159> see<01:41:58.320> how<01:41:58.560> we<01:41:58.719> can 01:41:58.870 --> 01:41:58.880 align:start position:0% understand prompts. We see how we can 01:41:58.880 --> 01:42:01.350 align:start position:0% understand prompts. We see how we can use<01:41:59.119> our<01:41:59.360> own<01:41:59.600> prompts<01:42:00.400> if<01:42:00.639> we<01:42:00.800> need<01:42:00.960> a<01:42:01.119> new 01:42:01.350 --> 01:42:01.360 align:start position:0% use our own prompts if we need a new 01:42:01.360 --> 01:42:05.109 align:start position:0% use our own prompts if we need a new prompt<01:42:01.679> for<01:42:01.920> git,<01:42:02.639> release,<01:42:03.600> data,<01:42:04.480> automate 01:42:05.109 --> 01:42:05.119 align:start position:0% prompt for git, release, data, automate 01:42:05.119 --> 01:42:06.950 align:start position:0% prompt for git, release, data, automate or<01:42:05.440> product. 01:42:06.950 --> 01:42:06.960 align:start position:0% or product. 01:42:06.960 --> 01:42:09.109 align:start position:0% or product. A<01:42:07.199> set<01:42:07.520> number<01:42:07.760> of<01:42:08.080> proper<01:42:08.480> prompts<01:42:08.880> are 01:42:09.109 --> 01:42:09.119 align:start position:0% A set number of proper prompts are 01:42:09.119 --> 01:42:12.070 align:start position:0% A set number of proper prompts are available<01:42:09.520> for<01:42:09.840> every<01:42:10.239> single<01:42:10.639> thing.<01:42:11.679> we<01:42:11.920> can 01:42:12.070 --> 01:42:12.080 align:start position:0% available for every single thing. we can 01:42:12.080 --> 01:42:15.270 align:start position:0% available for every single thing. we can reuse<01:42:12.480> them<01:42:12.800> multiple<01:42:13.280> times<01:42:13.600> over.<01:42:14.800> We<01:42:15.040> can 01:42:15.270 --> 01:42:15.280 align:start position:0% reuse them multiple times over. We can 01:42:15.280 --> 01:42:18.310 align:start position:0% reuse them multiple times over. We can utilize<01:42:15.760> multiple<01:42:16.239> variations<01:42:17.360> or<01:42:17.679> our<01:42:17.920> many 01:42:18.310 --> 01:42:18.320 align:start position:0% utilize multiple variations or our many 01:42:18.320 --> 01:42:20.070 align:start position:0% utilize multiple variations or our many functions. 01:42:20.070 --> 01:42:20.080 align:start position:0% functions. 01:42:20.080 --> 01:42:22.229 align:start position:0% functions. This<01:42:20.400> very<01:42:20.719> same<01:42:21.040> thing<01:42:21.360> is<01:42:21.600> available<01:42:22.080> here 01:42:22.229 --> 01:42:22.239 align:start position:0% This very same thing is available here 01:42:22.239 --> 01:42:24.870 align:start position:0% This very same thing is available here in<01:42:22.480> our<01:42:22.639> claude.<01:42:23.840> But<01:42:24.000> if<01:42:24.159> we<01:42:24.320> go<01:42:24.480> to<01:42:24.639> our 01:42:24.870 --> 01:42:24.880 align:start position:0% in our claude. But if we go to our 01:42:24.880 --> 01:42:28.229 align:start position:0% in our claude. But if we go to our codeex<01:42:26.080> then<01:42:26.480> until<01:42:26.960> now<01:42:27.360> we<01:42:27.600> do<01:42:27.840> not<01:42:28.080> have 01:42:28.229 --> 01:42:28.239 align:start position:0% codeex then until now we do not have 01:42:28.239 --> 01:42:31.669 align:start position:0% codeex then until now we do not have these<01:42:28.639> full<01:42:28.960> prompt<01:42:29.360> libraries<01:42:29.920> available. 01:42:31.669 --> 01:42:31.679 align:start position:0% these full prompt libraries available. 01:42:31.679 --> 01:42:34.550 align:start position:0% these full prompt libraries available. We<01:42:31.920> can<01:42:32.080> do<01:42:32.320> one<01:42:32.560> other<01:42:32.800> good<01:42:33.040> thing<01:42:33.280> here.<01:42:34.320> We 01:42:34.550 --> 01:42:34.560 align:start position:0% We can do one other good thing here. We 01:42:34.560 --> 01:42:36.709 align:start position:0% We can do one other good thing here. We can<01:42:34.719> come<01:42:34.960> right<01:42:35.280> here<01:42:35.520> and<01:42:35.840> ask<01:42:36.080> a<01:42:36.320> prompt 01:42:36.709 --> 01:42:36.719 align:start position:0% can come right here and ask a prompt 01:42:36.719 --> 01:42:40.470 align:start position:0% can come right here and ask a prompt question.<01:42:38.080> If<01:42:38.320> we<01:42:38.480> go<01:42:38.560> into<01:42:38.800> chat<01:42:39.199> GPT<01:42:40.080> and<01:42:40.320> for 01:42:40.470 --> 01:42:40.480 align:start position:0% question. If we go into chat GPT and for 01:42:40.480 --> 01:42:42.709 align:start position:0% question. If we go into chat GPT and for our<01:42:40.719> codeex<01:42:41.280> we<01:42:41.520> include<01:42:41.840> our<01:42:42.159> own<01:42:42.400> best 01:42:42.709 --> 01:42:42.719 align:start position:0% our codeex we include our own best 01:42:42.719 --> 01:42:45.830 align:start position:0% our codeex we include our own best prompts.<01:42:43.840> I<01:42:44.080> can<01:42:44.239> say<01:42:44.560> I<01:42:44.800> want<01:42:44.960> a<01:42:45.199> whole<01:42:45.440> new 01:42:45.830 --> 01:42:45.840 align:start position:0% prompts. I can say I want a whole new 01:42:45.840 --> 01:42:48.629 align:start position:0% prompts. I can say I want a whole new prompt<01:42:46.239> library<01:42:46.560> for<01:42:46.800> my<01:42:46.960> codeex. 01:42:48.629 --> 01:42:48.639 align:start position:0% prompt library for my codeex. 01:42:48.639 --> 01:42:51.590 align:start position:0% prompt library for my codeex. It<01:42:48.880> will<01:42:49.040> then<01:42:49.280> give<01:42:49.520> a<01:42:49.760> good<01:42:50.159> reusable<01:42:51.199> clean 01:42:51.590 --> 01:42:51.600 align:start position:0% It will then give a good reusable clean 01:42:51.600 --> 01:42:54.229 align:start position:0% It will then give a good reusable clean codeex<01:42:52.239> prompt<01:42:52.639> library. 01:42:54.229 --> 01:42:54.239 align:start position:0% codeex prompt library. 01:42:54.239 --> 01:42:56.709 align:start position:0% codeex prompt library. Inside<01:42:54.639> it<01:42:55.040> we<01:42:55.199> have<01:42:55.360> all<01:42:55.600> our<01:42:55.840> good<01:42:56.239> useful 01:42:56.709 --> 01:42:56.719 align:start position:0% Inside it we have all our good useful 01:42:56.719 --> 01:43:00.070 align:start position:0% Inside it we have all our good useful prompts.<01:42:58.000> We<01:42:58.159> have<01:42:58.320> our<01:42:58.480> bug<01:42:58.800> fixes,<01:42:59.679> text 01:43:00.070 --> 01:43:00.080 align:start position:0% prompts. We have our bug fixes, text 01:43:00.080 --> 01:43:02.709 align:start position:0% prompts. We have our bug fixes, text test<01:43:00.400> generator,<01:43:01.520> code<01:43:01.840> review, 01:43:02.709 --> 01:43:02.719 align:start position:0% test generator, code review, 01:43:02.719 --> 01:43:06.310 align:start position:0% test generator, code review, refactoring,<01:43:04.159> feature<01:43:04.639> builder,<01:43:05.679> API 01:43:06.310 --> 01:43:06.320 align:start position:0% refactoring, feature builder, API 01:43:06.320 --> 01:43:09.750 align:start position:0% refactoring, feature builder, API design,<01:43:07.440> performance<01:43:08.080> optimization<01:43:09.440> and 01:43:09.750 --> 01:43:09.760 align:start position:0% design, performance optimization and 01:43:09.760 --> 01:43:12.229 align:start position:0% design, performance optimization and security<01:43:10.320> audit<01:43:10.719> prompt. 01:43:12.229 --> 01:43:12.239 align:start position:0% security audit prompt. 01:43:12.239 --> 01:43:14.070 align:start position:0% security audit prompt. All<01:43:12.400> these<01:43:12.719> things<01:43:12.960> will<01:43:13.280> involve<01:43:13.600> in<01:43:13.840> that 01:43:14.070 --> 01:43:14.080 align:start position:0% All these things will involve in that 01:43:14.080 --> 01:43:15.990 align:start position:0% All these things will involve in that exact<01:43:14.480> thing. 01:43:15.990 --> 01:43:16.000 align:start position:0% exact thing. 01:43:16.000 --> 01:43:18.950 align:start position:0% exact thing. From<01:43:16.239> there<01:43:16.639> we<01:43:16.960> will<01:43:17.119> take<01:43:17.360> and<01:43:17.600> use<01:43:17.760> it<01:43:18.000> well. 01:43:18.950 --> 01:43:18.960 align:start position:0% From there we will take and use it well. 01:43:18.960 --> 01:43:21.350 align:start position:0% From there we will take and use it well. These<01:43:19.360> various<01:43:19.840> things<01:43:20.159> are<01:43:20.400> included<01:43:20.880> in<01:43:21.119> our 01:43:21.350 --> 01:43:21.360 align:start position:0% These various things are included in our 01:43:21.360 --> 01:43:24.870 align:start position:0% These various things are included in our entire<01:43:21.920> core<01:43:22.320> system<01:43:22.719> on<01:43:22.960> a<01:43:23.119> large<01:43:23.440> scale. 01:43:24.870 --> 01:43:24.880 align:start position:0% entire core system on a large scale. 01:43:24.880 --> 01:43:27.350 align:start position:0% entire core system on a large scale. We<01:43:25.199> must<01:43:25.520> look<01:43:25.760> at<01:43:26.000> all<01:43:26.239> these<01:43:26.560> many<01:43:26.880> things<01:43:27.119> on 01:43:27.350 --> 01:43:27.360 align:start position:0% We must look at all these many things on 01:43:27.360 --> 01:43:29.750 align:start position:0% We must look at all these many things on a<01:43:27.600> large<01:43:27.920> scale<01:43:28.320> to<01:43:28.560> see<01:43:28.719> how<01:43:28.960> we<01:43:29.199> can<01:43:29.360> reuse 01:43:29.750 --> 01:43:29.760 align:start position:0% a large scale to see how we can reuse 01:43:29.760 --> 01:43:32.950 align:start position:0% a large scale to see how we can reuse them.<01:43:31.119> We<01:43:31.360> will<01:43:31.520> copy<01:43:31.840> it<01:43:32.080> and<01:43:32.320> come<01:43:32.560> inside 01:43:32.950 --> 01:43:32.960 align:start position:0% them. We will copy it and come inside 01:43:32.960 --> 01:43:35.270 align:start position:0% them. We will copy it and come inside this<01:43:33.199> main<01:43:33.600> system<01:43:33.920> to<01:43:34.239> use<01:43:34.480> all<01:43:34.719> our<01:43:34.960> many 01:43:35.270 --> 01:43:35.280 align:start position:0% this main system to use all our many 01:43:35.280 --> 01:43:36.790 align:start position:0% this main system to use all our many prompts. 01:43:36.790 --> 01:43:36.800 align:start position:0% prompts. 01:43:36.800 --> 01:43:39.750 align:start position:0% prompts. We<01:43:37.040> will<01:43:37.280> not<01:43:37.440> use<01:43:37.679> these<01:43:38.000> exact<01:43:38.400> things.<01:43:39.600> But 01:43:39.750 --> 01:43:39.760 align:start position:0% We will not use these exact things. But 01:43:39.760 --> 01:43:42.550 align:start position:0% We will not use these exact things. But besides<01:43:40.320> this,<01:43:40.719> we<01:43:40.960> have<01:43:41.119> all<01:43:41.360> our<01:43:41.760> 12<01:43:42.159> core 01:43:42.550 --> 01:43:42.560 align:start position:0% besides this, we have all our 12 core 01:43:42.560 --> 01:43:44.149 align:start position:0% besides this, we have all our 12 core prompts. 01:43:44.149 --> 01:43:44.159 align:start position:0% prompts. 01:43:44.159 --> 01:43:46.390 align:start position:0% prompts. As<01:43:44.400> we<01:43:44.639> go<01:43:44.800> forward,<01:43:45.280> our<01:43:45.600> prompt<01:43:46.000> library 01:43:46.390 --> 01:43:46.400 align:start position:0% As we go forward, our prompt library 01:43:46.400 --> 01:43:50.149 align:start position:0% As we go forward, our prompt library will<01:43:46.719> increase<01:43:47.119> even<01:43:47.520> more.<01:43:48.719> From<01:43:49.119> 1<01:43:49.360> to<01:43:49.600> 12 01:43:50.149 --> 01:43:50.159 align:start position:0% will increase even more. From 1 to 12 01:43:50.159 --> 01:43:52.470 align:start position:0% will increase even more. From 1 to 12 are<01:43:50.400> many<01:43:50.719> different<01:43:51.040> options<01:43:51.520> will<01:43:51.760> be<01:43:51.920> used 01:43:52.470 --> 01:43:52.480 align:start position:0% are many different options will be used 01:43:52.480 --> 01:43:55.669 align:start position:0% are many different options will be used and<01:43:52.800> we<01:43:52.960> will<01:43:53.119> include<01:43:53.520> them.<01:43:54.960> These<01:43:55.360> things 01:43:55.669 --> 01:43:55.679 align:start position:0% and we will include them. These things 01:43:55.679 --> 01:43:58.070 align:start position:0% and we will include them. These things are<01:43:55.920> used<01:43:56.239> very<01:43:56.560> much<01:43:56.880> inside<01:43:57.280> the<01:43:57.600> entire 01:43:58.070 --> 01:43:58.080 align:start position:0% are used very much inside the entire 01:43:58.080 --> 01:43:59.750 align:start position:0% are used very much inside the entire system 01:43:59.750 --> 01:43:59.760 align:start position:0% system 01:43:59.760 --> 01:44:01.750 align:start position:0% system with<01:44:00.080> this.<01:44:00.480> We<01:44:00.719> have<01:44:00.800> a<01:44:01.040> lot<01:44:01.199> of<01:44:01.360> great 01:44:01.750 --> 01:44:01.760 align:start position:0% with this. We have a lot of great 01:44:01.760 --> 01:44:05.030 align:start position:0% with this. We have a lot of great automation<01:44:02.320> in<01:44:02.639> our<01:44:02.800> work<01:44:03.040> on<01:44:03.199> a<01:44:03.440> large<01:44:03.760> scale. 01:44:05.030 --> 01:44:05.040 align:start position:0% automation in our work on a large scale. 01:44:05.040 --> 01:44:08.709 align:start position:0% automation in our work on a large scale. We<01:44:05.280> can<01:44:05.440> use<01:44:05.679> that<01:44:05.920> well.<01:44:07.280> I<01:44:07.600> will<01:44:07.760> tell<01:44:07.920> you<01:44:08.400> we 01:44:08.709 --> 01:44:08.719 align:start position:0% We can use that well. I will tell you we 01:44:08.719 --> 01:44:10.950 align:start position:0% We can use that well. I will tell you we also<01:44:09.040> have<01:44:09.280> cool<01:44:09.679> automations<01:44:10.400> here<01:44:10.560> on<01:44:10.719> the 01:44:10.950 --> 01:44:10.960 align:start position:0% also have cool automations here on the 01:44:10.960 --> 01:44:14.310 align:start position:0% also have cool automations here on the side.<01:44:12.159> We<01:44:12.400> can<01:44:12.560> run<01:44:12.719> our<01:44:12.960> day<01:44:13.199> brief,<01:44:14.000> week 01:44:14.310 --> 01:44:14.320 align:start position:0% side. We can run our day brief, week 01:44:14.320 --> 01:44:17.830 align:start position:0% side. We can run our day brief, week review<01:44:15.119> or<01:44:15.440> smart<01:44:15.920> project<01:44:16.320> monitor. 01:44:17.830 --> 01:44:17.840 align:start position:0% review or smart project monitor. 01:44:17.840 --> 01:44:20.390 align:start position:0% review or smart project monitor. But<01:44:18.080> besides<01:44:18.560> that<01:44:19.119> if<01:44:19.360> we<01:44:19.520> look<01:44:19.600> at<01:44:19.760> our<01:44:20.000> cool 01:44:20.390 --> 01:44:20.400 align:start position:0% But besides that if we look at our cool 01:44:20.400 --> 01:44:23.189 align:start position:0% But besides that if we look at our cool templates<01:44:21.360> we<01:44:21.600> have<01:44:21.760> very<01:44:22.159> many.<01:44:22.719> Now<01:44:22.960> our 01:44:23.189 --> 01:44:23.199 align:start position:0% templates we have very many. Now our 01:44:23.199 --> 01:44:25.830 align:start position:0% templates we have very many. Now our next<01:44:23.440> discussion<01:44:24.000> relates<01:44:24.320> to<01:44:24.480> integration 01:44:25.830 --> 01:44:25.840 align:start position:0% next discussion relates to integration 01:44:25.840 --> 01:44:28.790 align:start position:0% next discussion relates to integration we<01:44:26.080> will<01:44:26.239> see<01:44:26.400> how<01:44:26.639> to<01:44:26.800> perform<01:44:27.440> AI<01:44:28.000> enhanced 01:44:28.790 --> 01:44:28.800 align:start position:0% we will see how to perform AI enhanced 01:44:28.800 --> 01:44:31.350 align:start position:0% we will see how to perform AI enhanced CI/CD. 01:44:31.350 --> 01:44:31.360 align:start position:0% CI/CD. 01:44:31.360 --> 01:44:33.669 align:start position:0% CI/CD. First<01:44:32.000> I<01:44:32.239> will<01:44:32.480> explain<01:44:32.719> the<01:44:32.960> full<01:44:33.280> definition 01:44:33.669 --> 01:44:33.679 align:start position:0% First I will explain the full definition 01:44:33.679 --> 01:44:36.550 align:start position:0% First I will explain the full definition of<01:44:34.000> CI/CD. 01:44:36.550 --> 01:44:36.560 align:start position:0% of CI/CD. 01:44:36.560 --> 01:44:40.070 align:start position:0% of CI/CD. CI<01:44:37.280> stands<01:44:37.600> for<01:44:37.840> continuous<01:44:38.400> integration. 01:44:40.070 --> 01:44:40.080 align:start position:0% CI stands for continuous integration. 01:44:40.080 --> 01:44:42.629 align:start position:0% CI stands for continuous integration. CD<01:44:40.800> stands<01:44:41.119> for<01:44:41.360> continuous<01:44:41.920> delivery<01:44:42.400> and 01:44:42.629 --> 01:44:42.639 align:start position:0% CD stands for continuous delivery and 01:44:42.639 --> 01:44:44.310 align:start position:0% CD stands for continuous delivery and deployment. 01:44:44.310 --> 01:44:44.320 align:start position:0% deployment. 01:44:44.320 --> 01:44:46.709 align:start position:0% deployment. Usually<01:44:44.960> when<01:44:45.280> enterprise<01:44:45.840> level<01:44:46.239> workflow 01:44:46.709 --> 01:44:46.719 align:start position:0% Usually when enterprise level workflow 01:44:46.719 --> 01:44:50.149 align:start position:0% Usually when enterprise level workflow loops<01:44:47.119> run,<01:44:47.760> we<01:44:48.000> have<01:44:48.159> multiple<01:44:48.719> projects.<01:44:49.920> We 01:44:50.149 --> 01:44:50.159 align:start position:0% loops run, we have multiple projects. We 01:44:50.159 --> 01:44:52.229 align:start position:0% loops run, we have multiple projects. We have<01:44:50.320> standalone<01:44:50.960> projects,<01:44:51.679> collaborative 01:44:52.229 --> 01:44:52.239 align:start position:0% have standalone projects, collaborative 01:44:52.239 --> 01:44:54.390 align:start position:0% have standalone projects, collaborative projects<01:44:52.960> or<01:44:53.280> autonomous<01:44:53.920> projects 01:44:54.390 --> 01:44:54.400 align:start position:0% projects or autonomous projects 01:44:54.400 --> 01:44:56.310 align:start position:0% projects or autonomous projects connected<01:44:54.719> to<01:44:54.960> multiple<01:44:55.440> companies, 01:44:56.310 --> 01:44:56.320 align:start position:0% connected to multiple companies, 01:44:56.320 --> 01:44:59.750 align:start position:0% connected to multiple companies, industries<01:44:56.960> and<01:44:57.280> businesses.<01:44:58.719> For<01:44:59.040> them,<01:44:59.520> we 01:44:59.750 --> 01:44:59.760 align:start position:0% industries and businesses. For them, we 01:44:59.760 --> 01:45:02.550 align:start position:0% industries and businesses. For them, we must<01:44:59.920> look<01:45:00.080> at<01:45:00.320> integration<01:45:00.880> and<01:45:01.199> deployment. 01:45:02.550 --> 01:45:02.560 align:start position:0% must look at integration and deployment. 01:45:02.560 --> 01:45:04.470 align:start position:0% must look at integration and deployment. This<01:45:02.800> is<01:45:02.880> a<01:45:03.040> DevOps<01:45:03.600> methodology<01:45:04.159> that 01:45:04.470 --> 01:45:04.480 align:start position:0% This is a DevOps methodology that 01:45:04.480 --> 01:45:06.790 align:start position:0% This is a DevOps methodology that automates<01:45:05.119> building,<01:45:06.000> testing<01:45:06.480> and 01:45:06.790 --> 01:45:06.800 align:start position:0% automates building, testing and 01:45:06.800 --> 01:45:09.669 align:start position:0% automates building, testing and releasing<01:45:07.280> software.<01:45:08.719> We<01:45:08.960> can<01:45:09.119> discuss<01:45:09.440> this 01:45:09.669 --> 01:45:09.679 align:start position:0% releasing software. We can discuss this 01:45:09.679 --> 01:45:12.550 align:start position:0% releasing software. We can discuss this as<01:45:10.000> automation.<01:45:11.360> This<01:45:11.679> pipeline<01:45:12.159> allows 01:45:12.550 --> 01:45:12.560 align:start position:0% as automation. This pipeline allows 01:45:12.560 --> 01:45:14.709 align:start position:0% as automation. This pipeline allows development<01:45:13.040> teams<01:45:13.360> to<01:45:13.600> ship<01:45:13.920> code<01:45:14.239> updates 01:45:14.709 --> 01:45:14.719 align:start position:0% development teams to ship code updates 01:45:14.719 --> 01:45:17.830 align:start position:0% development teams to ship code updates frequently,<01:45:15.679> safely,<01:45:16.400> and<01:45:16.719> reliably<01:45:17.520> while 01:45:17.830 --> 01:45:17.840 align:start position:0% frequently, safely, and reliably while 01:45:17.840 --> 01:45:19.669 align:start position:0% frequently, safely, and reliably while catching<01:45:18.239> bugs<01:45:18.560> early<01:45:18.880> in<01:45:19.040> the<01:45:19.199> development 01:45:19.669 --> 01:45:19.679 align:start position:0% catching bugs early in the development 01:45:19.679 --> 01:45:24.070 align:start position:0% catching bugs early in the development cycle.<01:45:21.119> Usually,<01:45:21.600> we<01:45:21.840> do<01:45:22.159> CI/CD<01:45:23.600> at<01:45:23.840> an 01:45:24.070 --> 01:45:24.080 align:start position:0% cycle. Usually, we do CI/CD at an 01:45:24.080 --> 01:45:26.229 align:start position:0% cycle. Usually, we do CI/CD at an industrial<01:45:24.560> or<01:45:24.880> enterprise<01:45:25.440> level<01:45:25.840> where<01:45:26.080> we 01:45:26.229 --> 01:45:26.239 align:start position:0% industrial or enterprise level where we 01:45:26.239 --> 01:45:28.470 align:start position:0% industrial or enterprise level where we need<01:45:26.480> automation. 01:45:28.470 --> 01:45:28.480 align:start position:0% need automation. 01:45:28.480 --> 01:45:31.270 align:start position:0% need automation. First,<01:45:28.800> we<01:45:29.040> have<01:45:29.199> continuous<01:45:29.840> integration. 01:45:31.270 --> 01:45:31.280 align:start position:0% First, we have continuous integration. 01:45:31.280 --> 01:45:32.950 align:start position:0% First, we have continuous integration. It<01:45:31.520> is<01:45:31.600> a<01:45:31.760> practice<01:45:32.159> where<01:45:32.400> developers 01:45:32.950 --> 01:45:32.960 align:start position:0% It is a practice where developers 01:45:32.960 --> 01:45:34.709 align:start position:0% It is a practice where developers regularly<01:45:33.440> merge<01:45:33.760> their<01:45:34.000> code<01:45:34.239> into<01:45:34.560> a 01:45:34.709 --> 01:45:34.719 align:start position:0% regularly merge their code into a 01:45:34.719 --> 01:45:36.709 align:start position:0% regularly merge their code into a central<01:45:35.119> repository<01:45:35.840> like<01:45:36.080> GitHub<01:45:36.560> or 01:45:36.709 --> 01:45:36.719 align:start position:0% central repository like GitHub or 01:45:36.719 --> 01:45:40.149 align:start position:0% central repository like GitHub or GitLab.<01:45:38.080> Every<01:45:38.480> time<01:45:38.719> code<01:45:39.040> is<01:45:39.199> merged,<01:45:39.920> an 01:45:40.149 --> 01:45:40.159 align:start position:0% GitLab. Every time code is merged, an 01:45:40.159 --> 01:45:42.229 align:start position:0% GitLab. Every time code is merged, an automated<01:45:40.719> system<01:45:41.119> builds<01:45:41.440> the<01:45:41.679> application 01:45:42.229 --> 01:45:42.239 align:start position:0% automated system builds the application 01:45:42.239 --> 01:45:44.470 align:start position:0% automated system builds the application and<01:45:42.560> runs<01:45:42.880> tests<01:45:43.360> until<01:45:43.679> the<01:45:43.840> integration 01:45:44.470 --> 01:45:44.480 align:start position:0% and runs tests until the integration 01:45:44.480 --> 01:45:45.990 align:start position:0% and runs tests until the integration finishes. 01:45:45.990 --> 01:45:46.000 align:start position:0% finishes. 01:45:46.000 --> 01:45:48.070 align:start position:0% finishes. This<01:45:46.239> ensures<01:45:46.639> that<01:45:46.880> the<01:45:47.119> new<01:45:47.280> code<01:45:47.679> does<01:45:47.920> not 01:45:48.070 --> 01:45:48.080 align:start position:0% This ensures that the new code does not 01:45:48.080 --> 01:45:51.030 align:start position:0% This ensures that the new code does not break<01:45:48.320> the<01:45:48.560> existing<01:45:49.040> code<01:45:49.360> base.<01:45:50.480> It<01:45:50.719> allows 01:45:51.030 --> 01:45:51.040 align:start position:0% break the existing code base. It allows 01:45:51.040 --> 01:45:54.070 align:start position:0% break the existing code base. It allows teams<01:45:51.440> to<01:45:51.600> catch<01:45:52.000> errors<01:45:52.239> instantly. 01:45:54.070 --> 01:45:54.080 align:start position:0% teams to catch errors instantly. 01:45:54.080 --> 01:45:56.470 align:start position:0% teams to catch errors instantly. Then<01:45:54.400> we<01:45:54.639> have<01:45:54.800> continuous<01:45:55.440> delivery<01:45:56.000> versus 01:45:56.470 --> 01:45:56.480 align:start position:0% Then we have continuous delivery versus 01:45:56.480 --> 01:45:59.430 align:start position:0% Then we have continuous delivery versus continuous<01:45:57.040> deployment.<01:45:58.480> How<01:45:58.719> can<01:45:58.880> we<01:45:59.119> use 01:45:59.430 --> 01:45:59.440 align:start position:0% continuous deployment. How can we use 01:45:59.440 --> 01:46:01.830 align:start position:0% continuous deployment. How can we use CI/CD? 01:46:01.830 --> 01:46:01.840 align:start position:0% CI/CD? 01:46:01.840 --> 01:46:05.270 align:start position:0% CI/CD? First,<01:46:02.400> it<01:46:02.639> gives<01:46:02.880> a<01:46:03.040> faster<01:46:03.520> time<01:46:03.760> to<01:46:04.000> market. 01:46:05.270 --> 01:46:05.280 align:start position:0% First, it gives a faster time to market. 01:46:05.280 --> 01:46:07.669 align:start position:0% First, it gives a faster time to market. New<01:46:05.600> features<01:46:05.920> and<01:46:06.159> bug<01:46:06.480> fixes<01:46:06.960> reach<01:46:07.280> users 01:46:07.669 --> 01:46:07.679 align:start position:0% New features and bug fixes reach users 01:46:07.679 --> 01:46:10.629 align:start position:0% New features and bug fixes reach users in<01:46:07.920> hours<01:46:08.320> instead<01:46:08.719> of<01:46:08.880> weeks<01:46:09.199> or<01:46:09.440> months. 01:46:10.629 --> 01:46:10.639 align:start position:0% in hours instead of weeks or months. 01:46:10.639 --> 01:46:13.350 align:start position:0% in hours instead of weeks or months. There<01:46:10.880> are<01:46:11.040> fewer<01:46:11.360> bugs,<01:46:12.239> easier<01:46:12.639> rollbacks, 01:46:13.350 --> 01:46:13.360 align:start position:0% There are fewer bugs, easier rollbacks, 01:46:13.360 --> 01:46:16.229 align:start position:0% There are fewer bugs, easier rollbacks, and<01:46:13.600> better<01:46:13.920> developer<01:46:14.400> productivity. 01:46:16.229 --> 01:46:16.239 align:start position:0% and better developer productivity. 01:46:16.239 --> 01:46:19.430 align:start position:0% and better developer productivity. CI/CD<01:46:17.600> pipelines<01:46:18.239> can<01:46:18.480> be<01:46:18.560> used<01:46:18.719> in<01:46:18.960> GitHub 01:46:19.430 --> 01:46:19.440 align:start position:0% CI/CD pipelines can be used in GitHub 01:46:19.440 --> 01:46:22.870 align:start position:0% CI/CD pipelines can be used in GitHub actions,<01:46:20.400> GitLab<01:46:21.119> CI,<01:46:21.840> Jenkins,<01:46:22.639> and 01:46:22.870 --> 01:46:22.880 align:start position:0% actions, GitLab CI, Jenkins, and 01:46:22.880 --> 01:46:25.030 align:start position:0% actions, GitLab CI, Jenkins, and CircleCI. 01:46:25.030 --> 01:46:25.040 align:start position:0% CircleCI. 01:46:25.040 --> 01:46:28.070 align:start position:0% CircleCI. I<01:46:25.280> will<01:46:25.520> search<01:46:25.679> for<01:46:25.920> codeex<01:46:26.480> on<01:46:26.639> Google.<01:46:27.040> Now, 01:46:28.070 --> 01:46:28.080 align:start position:0% I will search for codeex on Google. Now, 01:46:28.080 --> 01:46:30.709 align:start position:0% I will search for codeex on Google. Now, for<01:46:28.159> example,<01:46:29.280> if<01:46:29.520> I<01:46:29.679> share<01:46:30.000> here<01:46:30.159> that<01:46:30.400> I<01:46:30.560> want 01:46:30.709 --> 01:46:30.719 align:start position:0% for example, if I share here that I want 01:46:30.719 --> 01:46:33.030 align:start position:0% for example, if I share here that I want this<01:46:30.880> in<01:46:31.119> codeex,<01:46:32.000> then<01:46:32.239> we<01:46:32.400> can<01:46:32.560> also<01:46:32.880> do 01:46:33.030 --> 01:46:33.040 align:start position:0% this in codeex, then we can also do 01:46:33.040 --> 01:46:35.910 align:start position:0% this in codeex, then we can also do that.<01:46:33.600> how<01:46:33.840> it<01:46:34.000> becomes<01:46:34.320> possible. 01:46:35.910 --> 01:46:35.920 align:start position:0% that. how it becomes possible. 01:46:35.920 --> 01:46:38.149 align:start position:0% that. how it becomes possible. Integrating<01:46:36.480> the<01:46:36.719> codeex<01:46:37.280> command<01:46:37.679> line<01:46:37.920> into 01:46:38.149 --> 01:46:38.159 align:start position:0% Integrating the codeex command line into 01:46:38.159 --> 01:46:40.950 align:start position:0% Integrating the codeex command line into the<01:46:38.320> pipeline<01:46:38.880> enables<01:46:39.440> open<01:46:39.840> AI<01:46:40.239> codeex<01:46:40.800> to 01:46:40.950 --> 01:46:40.960 align:start position:0% the pipeline enables open AI codeex to 01:46:40.960 --> 01:46:43.910 align:start position:0% the pipeline enables open AI codeex to automatically<01:46:41.679> evaluate<01:46:42.320> build<01:46:42.639> failures. 01:46:43.910 --> 01:46:43.920 align:start position:0% automatically evaluate build failures. 01:46:43.920 --> 01:46:46.470 align:start position:0% automatically evaluate build failures. It<01:46:44.159> analyzes<01:46:44.800> vulnerability<01:46:45.520> scans<01:46:46.159> and 01:46:46.470 --> 01:46:46.480 align:start position:0% It analyzes vulnerability scans and 01:46:46.480 --> 01:46:48.470 align:start position:0% It analyzes vulnerability scans and proposes<01:46:47.040> minimal<01:46:47.440> changes<01:46:47.920> required<01:46:48.320> to 01:46:48.470 --> 01:46:48.480 align:start position:0% proposes minimal changes required to 01:46:48.480 --> 01:46:51.510 align:start position:0% proposes minimal changes required to make<01:46:48.639> the<01:46:48.800> tests<01:46:49.199> pass.<01:46:50.400> It<01:46:50.639> executes<01:46:51.199> code 01:46:51.510 --> 01:46:51.520 align:start position:0% make the tests pass. It executes code 01:46:51.520 --> 01:46:53.990 align:start position:0% make the tests pass. It executes code quality<01:46:51.920> checks<01:46:52.320> directly.<01:46:53.520> It<01:46:53.760> also 01:46:53.990 --> 01:46:54.000 align:start position:0% quality checks directly. It also 01:46:54.000 --> 01:46:56.149 align:start position:0% quality checks directly. It also generates<01:46:54.480> remediation<01:46:55.199> patches<01:46:55.600> or<01:46:55.920> pull 01:46:56.149 --> 01:46:56.159 align:start position:0% generates remediation patches or pull 01:46:56.159 --> 01:46:57.669 align:start position:0% generates remediation patches or pull requests. 01:46:57.669 --> 01:46:57.679 align:start position:0% requests. 01:46:57.679 --> 01:47:00.310 align:start position:0% requests. Usually<01:46:58.320> when<01:46:58.639> we<01:46:58.800> talk<01:46:59.040> about<01:46:59.199> our<01:46:59.520> process, 01:47:00.310 --> 01:47:00.320 align:start position:0% Usually when we talk about our process, 01:47:00.320 --> 01:47:02.870 align:start position:0% Usually when we talk about our process, we<01:47:00.639> can<01:47:00.719> perform<01:47:01.280> CI/CD 01:47:02.870 --> 01:47:02.880 align:start position:0% we can perform CI/CD 01:47:02.880 --> 01:47:05.910 align:start position:0% we can perform CI/CD in<01:47:03.199> multiple<01:47:03.600> forms<01:47:04.000> inside<01:47:04.320> our<01:47:04.560> projects. 01:47:05.910 --> 01:47:05.920 align:start position:0% in multiple forms inside our projects. 01:47:05.920 --> 01:47:08.470 align:start position:0% in multiple forms inside our projects. Here<01:47:06.159> in<01:47:06.400> this<01:47:06.560> interface<01:47:07.119> and<01:47:07.360> outside<01:47:07.840> it, 01:47:08.470 --> 01:47:08.480 align:start position:0% Here in this interface and outside it, 01:47:08.480 --> 01:47:10.950 align:start position:0% Here in this interface and outside it, if<01:47:08.719> I<01:47:08.880> go<01:47:09.040> directly<01:47:09.440> to<01:47:09.600> the<01:47:09.760> terminal,<01:47:10.560> I<01:47:10.800> can 01:47:10.950 --> 01:47:10.960 align:start position:0% if I go directly to the terminal, I can 01:47:10.960 --> 01:47:14.470 align:start position:0% if I go directly to the terminal, I can run<01:47:11.119> the<01:47:11.440> CI/CD<01:47:12.800> pipeline. 01:47:14.470 --> 01:47:14.480 align:start position:0% run the CI/CD pipeline. 01:47:14.480 --> 01:47:17.350 align:start position:0% run the CI/CD pipeline. How<01:47:14.719> can<01:47:14.880> I<01:47:15.040> do<01:47:15.199> this?<01:47:16.159> First,<01:47:16.719> I<01:47:16.960> will<01:47:17.119> search 01:47:17.350 --> 01:47:17.360 align:start position:0% How can I do this? First, I will search 01:47:17.360 --> 01:47:19.910 align:start position:0% How can I do this? First, I will search for<01:47:17.520> codeex<01:47:18.400> CLI. 01:47:19.910 --> 01:47:19.920 align:start position:0% for codeex CLI. 01:47:19.920 --> 01:47:21.830 align:start position:0% for codeex CLI. The<01:47:20.159> developer<01:47:20.639> platform<01:47:20.960> will<01:47:21.280> open<01:47:21.679> which 01:47:21.830 --> 01:47:21.840 align:start position:0% The developer platform will open which 01:47:21.840 --> 01:47:24.790 align:start position:0% The developer platform will open which we<01:47:22.080> can<01:47:22.239> access<01:47:22.639> directly.<01:47:23.920> Here<01:47:24.239> we<01:47:24.560> must 01:47:24.790 --> 01:47:24.800 align:start position:0% we can access directly. Here we must 01:47:24.800 --> 01:47:27.270 align:start position:0% we can access directly. Here we must install<01:47:25.119> it.<01:47:26.000> I<01:47:26.239> will<01:47:26.400> come<01:47:26.560> here<01:47:26.800> and<01:47:26.960> command 01:47:27.270 --> 01:47:27.280 align:start position:0% install it. I will come here and command 01:47:27.280 --> 01:47:29.830 align:start position:0% install it. I will come here and command the<01:47:27.520> system<01:47:27.760> to<01:47:28.000> install<01:47:28.400> codeex.<01:47:29.520> We<01:47:29.679> will 01:47:29.830 --> 01:47:29.840 align:start position:0% the system to install codeex. We will 01:47:29.840 --> 01:47:32.550 align:start position:0% the system to install codeex. We will copy<01:47:30.159> and<01:47:30.400> paste<01:47:30.639> the<01:47:30.880> required<01:47:31.280> command.<01:47:32.400> You 01:47:32.550 --> 01:47:32.560 align:start position:0% copy and paste the required command. You 01:47:32.560 --> 01:47:34.550 align:start position:0% copy and paste the required command. You will<01:47:32.719> see<01:47:32.880> that<01:47:33.119> codeex<01:47:33.679> is<01:47:33.920> already<01:47:34.159> set<01:47:34.400> up 01:47:34.550 --> 01:47:34.560 align:start position:0% will see that codeex is already set up 01:47:34.560 --> 01:47:37.109 align:start position:0% will see that codeex is already set up here.<01:47:35.440> Because<01:47:35.760> of<01:47:35.920> this,<01:47:36.239> we<01:47:36.480> do<01:47:36.639> not<01:47:36.800> need<01:47:36.960> to 01:47:37.109 --> 01:47:37.119 align:start position:0% here. Because of this, we do not need to 01:47:37.119 --> 01:47:40.070 align:start position:0% here. Because of this, we do not need to install<01:47:37.520> it<01:47:37.679> again.<01:47:38.960> We<01:47:39.199> simply<01:47:39.520> type<01:47:39.840> our 01:47:40.070 --> 01:47:40.080 align:start position:0% install it again. We simply type our 01:47:40.080 --> 01:47:41.990 align:start position:0% install it again. We simply type our codeex<01:47:40.560> command<01:47:41.199> and<01:47:41.440> it<01:47:41.600> will<01:47:41.760> start 01:47:41.990 --> 01:47:42.000 align:start position:0% codeex command and it will start 01:47:42.000 --> 01:47:45.109 align:start position:0% codeex command and it will start running.<01:47:43.040> You<01:47:43.199> have<01:47:43.360> seen<01:47:43.600> this<01:47:43.760> here<01:47:44.080> too. 01:47:45.109 --> 01:47:45.119 align:start position:0% running. You have seen this here too. 01:47:45.119 --> 01:47:47.030 align:start position:0% running. You have seen this here too. Whenever<01:47:45.440> we<01:47:45.600> give<01:47:45.760> a<01:47:46.000> command,<01:47:46.560> we<01:47:46.800> have<01:47:46.880> a 01:47:47.030 --> 01:47:47.040 align:start position:0% Whenever we give a command, we have a 01:47:47.040 --> 01:47:49.750 align:start position:0% Whenever we give a command, we have a terminal<01:47:47.520> option<01:47:47.840> available<01:47:48.239> on<01:47:48.480> the<01:47:48.639> side. 01:47:49.750 --> 01:47:49.760 align:start position:0% terminal option available on the side. 01:47:49.760 --> 01:47:51.910 align:start position:0% terminal option available on the side. Inside<01:47:50.159> this,<01:47:50.800> we<01:47:51.040> can<01:47:51.280> automatically 01:47:51.910 --> 01:47:51.920 align:start position:0% Inside this, we can automatically 01:47:51.920 --> 01:47:54.870 align:start position:0% Inside this, we can automatically initiate<01:47:52.400> our<01:47:52.719> working<01:47:53.040> process.<01:47:54.400> We<01:47:54.719> also 01:47:54.870 --> 01:47:54.880 align:start position:0% initiate our working process. We also 01:47:54.880 --> 01:47:58.070 align:start position:0% initiate our working process. We also have<01:47:55.040> a<01:47:55.199> browser<01:47:55.600> option<01:47:55.920> to<01:47:56.080> run<01:47:56.480> CI/CD 01:47:58.070 --> 01:47:58.080 align:start position:0% have a browser option to run CI/CD 01:47:58.080 --> 01:47:59.669 align:start position:0% have a browser option to run CI/CD pipelines. 01:47:59.669 --> 01:47:59.679 align:start position:0% pipelines. 01:47:59.679 --> 01:48:02.229 align:start position:0% pipelines. Usually,<01:48:00.639> continuous<01:48:01.280> integration<01:48:01.920> and 01:48:02.229 --> 01:48:02.239 align:start position:0% Usually, continuous integration and 01:48:02.239 --> 01:48:04.310 align:start position:0% Usually, continuous integration and continuous<01:48:02.800> deployment<01:48:03.600> have<01:48:03.920> become<01:48:04.159> a 01:48:04.310 --> 01:48:04.320 align:start position:0% continuous deployment have become a 01:48:04.320 --> 01:48:05.830 align:start position:0% continuous deployment have become a foundation<01:48:04.800> of<01:48:05.040> modern<01:48:05.440> software 01:48:05.830 --> 01:48:05.840 align:start position:0% foundation of modern software 01:48:05.840 --> 01:48:09.590 align:start position:0% foundation of modern software engineering.<01:48:07.280> Traditional<01:48:08.000> CI/CD 01:48:09.590 --> 01:48:09.600 align:start position:0% engineering. Traditional CI/CD 01:48:09.600 --> 01:48:11.990 align:start position:0% engineering. Traditional CI/CD pipelines<01:48:10.639> automate<01:48:11.119> the<01:48:11.360> building, 01:48:11.990 --> 01:48:12.000 align:start position:0% pipelines automate the building, 01:48:12.000 --> 01:48:14.950 align:start position:0% pipelines automate the building, testing,<01:48:12.560> and<01:48:12.800> deployment<01:48:13.360> processes.<01:48:14.719> This 01:48:14.950 --> 01:48:14.960 align:start position:0% testing, and deployment processes. This 01:48:14.960 --> 01:48:16.870 align:start position:0% testing, and deployment processes. This reduces<01:48:15.440> manual<01:48:15.840> effort<01:48:16.159> and<01:48:16.400> ensures 01:48:16.870 --> 01:48:16.880 align:start position:0% reduces manual effort and ensures 01:48:16.880 --> 01:48:19.510 align:start position:0% reduces manual effort and ensures consistent<01:48:17.440> software<01:48:17.920> delivery. 01:48:19.510 --> 01:48:19.520 align:start position:0% consistent software delivery. 01:48:19.520 --> 01:48:21.510 align:start position:0% consistent software delivery. With<01:48:19.760> the<01:48:19.920> introduction<01:48:20.320> of<01:48:20.639> AI<01:48:21.119> powered 01:48:21.510 --> 01:48:21.520 align:start position:0% With the introduction of AI powered 01:48:21.520 --> 01:48:24.870 align:start position:0% With the introduction of AI powered development<01:48:22.000> tools<01:48:22.320> like<01:48:22.560> Open<01:48:22.960> AI,<01:48:24.080> enhanced 01:48:24.870 --> 01:48:24.880 align:start position:0% development tools like Open AI, enhanced 01:48:24.880 --> 01:48:27.990 align:start position:0% development tools like Open AI, enhanced CI<01:48:25.360> and<01:48:25.600> CD<01:48:26.560> introduces<01:48:27.199> a<01:48:27.440> new<01:48:27.760> layer<01:48:27.840> of 01:48:27.990 --> 01:48:28.000 align:start position:0% CI and CD introduces a new layer of 01:48:28.000 --> 01:48:29.910 align:start position:0% CI and CD introduces a new layer of intelligence<01:48:28.560> into<01:48:28.800> the<01:48:29.040> software<01:48:29.440> delivery 01:48:29.910 --> 01:48:29.920 align:start position:0% intelligence into the software delivery 01:48:29.920 --> 01:48:32.629 align:start position:0% intelligence into the software delivery life<01:48:30.159> cycle.<01:48:31.280> Instead<01:48:31.679> of<01:48:31.840> merely<01:48:32.159> reporting 01:48:32.629 --> 01:48:32.639 align:start position:0% life cycle. Instead of merely reporting 01:48:32.639 --> 01:48:35.590 align:start position:0% life cycle. Instead of merely reporting failures,<01:48:33.760> AI<01:48:34.239> systems<01:48:34.719> can<01:48:34.960> investigate<01:48:35.440> the 01:48:35.590 --> 01:48:35.600 align:start position:0% failures, AI systems can investigate the 01:48:35.600 --> 01:48:38.790 align:start position:0% failures, AI systems can investigate the root<01:48:35.840> cause.<01:48:36.960> They<01:48:37.280> propose<01:48:37.760> correlations 01:48:38.790 --> 01:48:38.800 align:start position:0% root cause. They propose correlations 01:48:38.800 --> 01:48:40.790 align:start position:0% root cause. They propose correlations and<01:48:39.040> create<01:48:39.360> pull<01:48:39.679> requests<01:48:40.239> containing 01:48:40.790 --> 01:48:40.800 align:start position:0% and create pull requests containing 01:48:40.800 --> 01:48:43.830 align:start position:0% and create pull requests containing fixes.<01:48:42.239> This<01:48:42.480> dramatically<01:48:43.119> reduces<01:48:43.520> the 01:48:43.830 --> 01:48:43.840 align:start position:0% fixes. This dramatically reduces the 01:48:43.840 --> 01:48:45.830 align:start position:0% fixes. This dramatically reduces the time<01:48:44.080> developers<01:48:44.639> spend<01:48:45.040> troubleshooting 01:48:45.830 --> 01:48:45.840 align:start position:0% time developers spend troubleshooting 01:48:45.840 --> 01:48:48.229 align:start position:0% time developers spend troubleshooting failed<01:48:46.320> builds.<01:48:47.040> It<01:48:47.280> allows<01:48:47.760> engineering 01:48:48.229 --> 01:48:48.239 align:start position:0% failed builds. It allows engineering 01:48:48.239 --> 01:48:50.629 align:start position:0% failed builds. It allows engineering teams<01:48:48.560> to<01:48:48.800> focus<01:48:49.040> on<01:48:49.360> high<01:48:49.679> value<01:48:50.000> work<01:48:50.400> such 01:48:50.629 --> 01:48:50.639 align:start position:0% teams to focus on high value work such 01:48:50.639 --> 01:48:52.870 align:start position:0% teams to focus on high value work such as<01:48:50.800> feature<01:48:51.199> development<01:48:51.840> and<01:48:52.159> architectural 01:48:52.870 --> 01:48:52.880 align:start position:0% as feature development and architectural 01:48:52.880 --> 01:48:54.470 align:start position:0% as feature development and architectural improvement. 01:48:54.470 --> 01:48:54.480 align:start position:0% improvement. 01:48:54.480 --> 01:48:57.270 align:start position:0% improvement. Let<01:48:54.639> me<01:48:54.800> show<01:48:54.960> you<01:48:55.119> a<01:48:55.360> simple<01:48:55.679> example.<01:48:56.960> We<01:48:57.199> can 01:48:57.270 --> 01:48:57.280 align:start position:0% Let me show you a simple example. We can 01:48:57.280 --> 01:48:59.910 align:start position:0% Let me show you a simple example. We can take<01:48:57.520> any<01:48:57.840> system<01:48:58.159> here.<01:48:59.199> When<01:48:59.440> we<01:48:59.600> give<01:48:59.760> a 01:48:59.910 --> 01:48:59.920 align:start position:0% take any system here. When we give a 01:48:59.920 --> 01:49:02.070 align:start position:0% take any system here. When we give a prompt,<01:49:00.480> you<01:49:00.719> can<01:49:00.880> see<01:49:01.040> our<01:49:01.280> working<01:49:01.600> process 01:49:02.070 --> 01:49:02.080 align:start position:0% prompt, you can see our working process 01:49:02.080 --> 01:49:05.109 align:start position:0% prompt, you can see our working process begins.<01:49:03.199> We<01:49:03.440> get<01:49:03.679> options<01:49:04.000> to<01:49:04.239> debug<01:49:04.639> an<01:49:04.800> issue 01:49:05.109 --> 01:49:05.119 align:start position:0% begins. We get options to debug an issue 01:49:05.119 --> 01:49:08.629 align:start position:0% begins. We get options to debug an issue or<01:49:05.360> review<01:49:05.679> a<01:49:05.920> plan.<01:49:07.199> I<01:49:07.440> will<01:49:07.600> select<01:49:08.000> GitHub 01:49:08.629 --> 01:49:08.639 align:start position:0% or review a plan. I will select GitHub 01:49:08.639 --> 01:49:10.310 align:start position:0% or review a plan. I will select GitHub and<01:49:08.880> ask<01:49:09.119> it<01:49:09.360> to<01:49:09.520> review<01:49:09.760> the<01:49:10.000> newest 01:49:10.310 --> 01:49:10.320 align:start position:0% and ask it to review the newest 01:49:10.320 --> 01:49:11.910 align:start position:0% and ask it to review the newest repository. 01:49:11.910 --> 01:49:11.920 align:start position:0% repository. 01:49:11.920 --> 01:49:14.709 align:start position:0% repository. The<01:49:12.080> newest<01:49:12.400> repository<01:49:12.960> will<01:49:13.119> appear.<01:49:14.320> Then 01:49:14.709 --> 01:49:14.719 align:start position:0% The newest repository will appear. Then 01:49:14.719 --> 01:49:16.709 align:start position:0% The newest repository will appear. Then I<01:49:14.960> will<01:49:15.119> command<01:49:15.440> it<01:49:15.600> to<01:49:15.760> analyze<01:49:16.239> the<01:49:16.400> latest 01:49:16.709 --> 01:49:16.719 align:start position:0% I will command it to analyze the latest 01:49:16.719 --> 01:49:19.669 align:start position:0% I will command it to analyze the latest pull<01:49:17.040> request.<01:49:18.400> It<01:49:18.639> must<01:49:18.880> generate<01:49:19.280> unit 01:49:19.669 --> 01:49:19.679 align:start position:0% pull request. It must generate unit 01:49:19.679 --> 01:49:21.669 align:start position:0% pull request. It must generate unit tests<01:49:19.920> for<01:49:20.159> newly<01:49:20.480> added<01:49:20.800> functions, 01:49:21.669 --> 01:49:21.679 align:start position:0% tests for newly added functions, 01:49:21.679 --> 01:49:24.149 align:start position:0% tests for newly added functions, modified<01:49:22.239> business<01:49:22.560> logic<01:49:23.119> and<01:49:23.360> edge<01:49:23.760> cases 01:49:24.149 --> 01:49:24.159 align:start position:0% modified business logic and edge cases 01:49:24.159 --> 01:49:25.750 align:start position:0% modified business logic and edge cases to<01:49:24.400> improve<01:49:24.719> our<01:49:25.040> error<01:49:25.280> handling 01:49:25.750 --> 01:49:25.760 align:start position:0% to improve our error handling 01:49:25.760 --> 01:49:27.350 align:start position:0% to improve our error handling completely. 01:49:27.350 --> 01:49:27.360 align:start position:0% completely. 01:49:27.360 --> 01:49:29.430 align:start position:0% completely. As<01:49:27.600> soon<01:49:27.760> as<01:49:27.840> I<01:49:28.080> include<01:49:28.400> this,<01:49:28.880> the<01:49:29.280> error 01:49:29.430 --> 01:49:29.440 align:start position:0% As soon as I include this, the error 01:49:29.440 --> 01:49:31.189 align:start position:0% As soon as I include this, the error handling<01:49:29.840> scenarios<01:49:30.400> will<01:49:30.560> become<01:49:30.880> much 01:49:31.189 --> 01:49:31.199 align:start position:0% handling scenarios will become much 01:49:31.199 --> 01:49:34.149 align:start position:0% handling scenarios will become much better.<01:49:32.639> The<01:49:32.880> other<01:49:33.119> responses<01:49:33.600> will<01:49:33.840> also 01:49:34.149 --> 01:49:34.159 align:start position:0% better. The other responses will also 01:49:34.159 --> 01:49:37.189 align:start position:0% better. The other responses will also appear<01:49:34.480> here<01:49:34.639> for<01:49:34.880> us<01:49:34.960> to<01:49:35.119> analyze<01:49:35.600> directly. 01:49:37.189 --> 01:49:37.199 align:start position:0% appear here for us to analyze directly. 01:49:37.199 --> 01:49:39.510 align:start position:0% appear here for us to analyze directly. Usually<01:49:37.679> the<01:49:37.920> GitHub<01:49:38.480> workflow<01:49:38.880> is<01:49:39.040> infused 01:49:39.510 --> 01:49:39.520 align:start position:0% Usually the GitHub workflow is infused 01:49:39.520 --> 01:49:43.030 align:start position:0% Usually the GitHub workflow is infused here.<01:49:40.480> Inside<01:49:41.040> the<01:49:41.280> GitHub<01:49:41.760> workflow,<01:49:42.560> we<01:49:42.800> can 01:49:43.030 --> 01:49:43.040 align:start position:0% here. Inside the GitHub workflow, we can 01:49:43.040 --> 01:49:45.270 align:start position:0% here. Inside the GitHub workflow, we can directly<01:49:43.520> use<01:49:43.760> our<01:49:44.080> other<01:49:44.320> generations<01:49:44.960> or 01:49:45.270 --> 01:49:45.280 align:start position:0% directly use our other generations or 01:49:45.280 --> 01:49:46.790 align:start position:0% directly use our other generations or processes. 01:49:46.790 --> 01:49:46.800 align:start position:0% processes. 01:49:46.800 --> 01:49:48.709 align:start position:0% processes. Our<01:49:47.040> other<01:49:47.280> regions<01:49:47.760> and<01:49:47.920> our<01:49:48.159> understanding 01:49:48.709 --> 01:49:48.719 align:start position:0% Our other regions and our understanding 01:49:48.719 --> 01:49:52.070 align:start position:0% Our other regions and our understanding will<01:49:49.040> also<01:49:49.280> appear<01:49:50.639> side<01:49:50.960> by<01:49:51.199> side.<01:49:51.600> I<01:49:51.840> must 01:49:52.070 --> 01:49:52.080 align:start position:0% will also appear side by side. I must 01:49:52.080 --> 01:49:54.709 align:start position:0% will also appear side by side. I must tell<01:49:52.239> you<01:49:52.480> another<01:49:52.800> thing.<01:49:53.760> We<01:49:54.080> usually<01:49:54.480> face 01:49:54.709 --> 01:49:54.719 align:start position:0% tell you another thing. We usually face 01:49:54.719 --> 01:49:56.550 align:start position:0% tell you another thing. We usually face a<01:49:54.960> concern<01:49:55.360> about<01:49:55.679> how<01:49:55.840> to<01:49:56.080> check<01:49:56.320> our 01:49:56.550 --> 01:49:56.560 align:start position:0% a concern about how to check our 01:49:56.560 --> 01:49:59.590 align:start position:0% a concern about how to check our processes<01:49:57.119> inside<01:49:57.520> out<01:49:57.760> on<01:49:57.920> a<01:49:58.080> larger<01:49:58.400> scale. 01:49:59.590 --> 01:49:59.600 align:start position:0% processes inside out on a larger scale. 01:49:59.600 --> 01:50:01.669 align:start position:0% processes inside out on a larger scale. We<01:49:59.840> will<01:50:00.000> see<01:50:00.159> that<01:50:00.400> in<01:50:00.639> a<01:50:00.800> much<01:50:01.040> better<01:50:01.280> form. 01:50:01.669 --> 01:50:01.679 align:start position:0% We will see that in a much better form. 01:50:01.679 --> 01:50:06.070 align:start position:0% We will see that in a much better form. Now<01:50:03.040> in<01:50:03.199> the<01:50:03.440> CI/CD<01:50:04.639> pipeline,<01:50:05.520> you<01:50:05.760> can<01:50:05.920> see 01:50:06.070 --> 01:50:06.080 align:start position:0% Now in the CI/CD pipeline, you can see 01:50:06.080 --> 01:50:09.189 align:start position:0% Now in the CI/CD pipeline, you can see the<01:50:06.320> local<01:50:06.639> workspace<01:50:07.199> is<01:50:07.440> empty.<01:50:08.480> The<01:50:08.719> GitHub 01:50:09.189 --> 01:50:09.199 align:start position:0% the local workspace is empty. The GitHub 01:50:09.199 --> 01:50:11.669 align:start position:0% the local workspace is empty. The GitHub account<01:50:09.440> is<01:50:09.600> authenticated<01:50:10.639> but<01:50:10.960> git<01:50:11.280> is<01:50:11.440> not 01:50:11.669 --> 01:50:11.679 align:start position:0% account is authenticated but git is not 01:50:11.679 --> 01:50:14.950 align:start position:0% account is authenticated but git is not available.<01:50:13.040> If<01:50:13.280> we<01:50:13.440> set<01:50:13.679> up<01:50:13.840> these<01:50:14.159> things,<01:50:14.719> we 01:50:14.950 --> 01:50:14.960 align:start position:0% available. If we set up these things, we 01:50:14.960 --> 01:50:18.629 align:start position:0% available. If we set up these things, we can<01:50:15.119> cross-check<01:50:15.679> our<01:50:16.000> CI/CD<01:50:17.119> pipelines. 01:50:18.629 --> 01:50:18.639 align:start position:0% can cross-check our CI/CD pipelines. 01:50:18.639 --> 01:50:21.109 align:start position:0% can cross-check our CI/CD pipelines. We<01:50:18.960> prepare<01:50:19.199> a<01:50:19.440> repository<01:50:20.320> and<01:50:20.639> use<01:50:20.880> the 01:50:21.109 --> 01:50:21.119 align:start position:0% We prepare a repository and use the 01:50:21.119 --> 01:50:24.629 align:start position:0% We prepare a repository and use the CI/CD<01:50:22.320> pipeline<01:50:23.040> perfectly. 01:50:24.629 --> 01:50:24.639 align:start position:0% CI/CD pipeline perfectly. 01:50:24.639 --> 01:50:26.470 align:start position:0% CI/CD pipeline perfectly. Here<01:50:24.960> I<01:50:25.199> will<01:50:25.360> give<01:50:25.520> you<01:50:25.600> the<01:50:25.840> example<01:50:26.159> of<01:50:26.320> a 01:50:26.470 --> 01:50:26.480 align:start position:0% Here I will give you the example of a 01:50:26.480 --> 01:50:29.430 align:start position:0% Here I will give you the example of a pipeline.<01:50:27.920> If<01:50:28.159> you<01:50:28.320> prepare<01:50:28.639> a<01:50:28.800> pipeline<01:50:29.280> of 01:50:29.430 --> 01:50:29.440 align:start position:0% pipeline. If you prepare a pipeline of 01:50:29.440 --> 01:50:32.310 align:start position:0% pipeline. If you prepare a pipeline of build<01:50:30.000> which<01:50:30.239> have<01:50:30.400> a<01:50:30.639> request,<01:50:31.520> it<01:50:31.760> has<01:50:32.000> many 01:50:32.310 --> 01:50:32.320 align:start position:0% build which have a request, it has many 01:50:32.320 --> 01:50:34.629 align:start position:0% build which have a request, it has many stage<01:50:32.800> such<01:50:33.040> as<01:50:33.199> names<01:50:33.679> and<01:50:33.920> tests<01:50:34.400> will 01:50:34.629 --> 01:50:34.639 align:start position:0% stage such as names and tests will 01:50:34.639 --> 01:50:38.229 align:start position:0% stage such as names and tests will appear<01:50:34.960> here.<01:50:36.320> If<01:50:36.560> you<01:50:36.719> connect<01:50:37.199> codecs<01:50:37.760> here, 01:50:38.229 --> 01:50:38.239 align:start position:0% appear here. If you connect codecs here, 01:50:38.239 --> 01:50:40.950 align:start position:0% appear here. If you connect codecs here, then<01:50:38.560> our<01:50:38.719> AI<01:50:39.119> tasks<01:50:39.679> can<01:50:39.920> work<01:50:40.239> side<01:50:40.560> by<01:50:40.719> side 01:50:40.950 --> 01:50:40.960 align:start position:0% then our AI tasks can work side by side 01:50:40.960 --> 01:50:43.590 align:start position:0% then our AI tasks can work side by side with<01:50:41.119> it.<01:50:41.760> Our<01:50:42.080> next<01:50:42.400> topic<01:50:42.880> is<01:50:43.199> putting 01:50:43.590 --> 01:50:43.600 align:start position:0% with it. Our next topic is putting 01:50:43.600 --> 01:50:47.030 align:start position:0% with it. Our next topic is putting codeex<01:50:44.239> into<01:50:44.560> our<01:50:44.800> work<01:50:45.119> process.<01:50:46.480> This<01:50:46.800> means 01:50:47.030 --> 01:50:47.040 align:start position:0% codeex into our work process. This means 01:50:47.040 --> 01:50:50.070 align:start position:0% codeex into our work process. This means adding<01:50:47.440> codecs<01:50:47.920> to<01:50:48.080> our<01:50:48.239> build<01:50:48.560> system.<01:50:49.840> When 01:50:50.070 --> 01:50:50.080 align:start position:0% adding codecs to our build system. When 01:50:50.080 --> 01:50:52.470 align:start position:0% adding codecs to our build system. When we<01:50:50.320> do<01:50:50.480> this,<01:50:51.119> the<01:50:51.360> system<01:50:51.679> helps<01:50:52.000> us<01:50:52.159> find 01:50:52.470 --> 01:50:52.480 align:start position:0% we do this, the system helps us find 01:50:52.480 --> 01:50:55.750 align:start position:0% we do this, the system helps us find problems.<01:50:53.760> If<01:50:54.000> a<01:50:54.159> build<01:50:54.480> stops<01:50:54.880> working<01:50:55.280> or<01:50:55.520> a 01:50:55.750 --> 01:50:55.760 align:start position:0% problems. If a build stops working or a 01:50:55.760 --> 01:50:58.390 align:start position:0% problems. If a build stops working or a task<01:50:56.159> breaks,<01:50:57.040> the<01:50:57.280> tool<01:50:57.600> sees<01:50:57.920> the<01:50:58.159> code 01:50:58.390 --> 01:50:58.400 align:start position:0% task breaks, the tool sees the code 01:50:58.400 --> 01:51:01.830 align:start position:0% task breaks, the tool sees the code quality<01:50:58.800> issues.<01:51:00.239> Before,<01:51:01.199> people<01:51:01.440> had<01:51:01.679> to 01:51:01.830 --> 01:51:01.840 align:start position:0% quality issues. Before, people had to 01:51:01.840 --> 01:51:04.870 align:start position:0% quality issues. Before, people had to look<01:51:02.000> at<01:51:02.239> every<01:51:02.639> single<01:51:03.040> problem<01:51:03.360> by<01:51:03.679> hand. 01:51:04.870 --> 01:51:04.880 align:start position:0% look at every single problem by hand. 01:51:04.880 --> 01:51:07.270 align:start position:0% look at every single problem by hand. Now<01:51:05.440> the<01:51:05.760> system<01:51:06.080> looks<01:51:06.320> at<01:51:06.400> the<01:51:06.639> failures<01:51:07.040> for 01:51:07.270 --> 01:51:07.280 align:start position:0% Now the system looks at the failures for 01:51:07.280 --> 01:51:10.550 align:start position:0% Now the system looks at the failures for us.<01:51:08.480> It<01:51:08.719> gives<01:51:09.040> ideas<01:51:09.440> to<01:51:09.679> fix<01:51:09.920> them<01:51:10.239> and 01:51:10.550 --> 01:51:10.560 align:start position:0% us. It gives ideas to fix them and 01:51:10.560 --> 01:51:13.590 align:start position:0% us. It gives ideas to fix them and creates<01:51:11.040> tests.<01:51:12.400> It<01:51:12.639> can<01:51:12.800> even<01:51:13.040> make<01:51:13.280> pull 01:51:13.590 --> 01:51:13.600 align:start position:0% creates tests. It can even make pull 01:51:13.600 --> 01:51:16.709 align:start position:0% creates tests. It can even make pull requests<01:51:14.000> with<01:51:14.239> good<01:51:14.480> answers.<01:51:15.920> In<01:51:16.159> a<01:51:16.400> normal 01:51:16.709 --> 01:51:16.719 align:start position:0% requests with good answers. In a normal 01:51:16.719 --> 01:51:20.310 align:start position:0% requests with good answers. In a normal process,<01:51:17.520> a<01:51:17.760> person<01:51:18.159> sends<01:51:18.480> code<01:51:18.719> to<01:51:18.960> GitHub. 01:51:20.310 --> 01:51:20.320 align:start position:0% process, a person sends code to GitHub. 01:51:20.320 --> 01:51:22.790 align:start position:0% process, a person sends code to GitHub. Then<01:51:20.880> our<01:51:21.119> complete<01:51:21.600> system<01:51:22.080> starts<01:51:22.400> running 01:51:22.790 --> 01:51:22.800 align:start position:0% Then our complete system starts running 01:51:22.800 --> 01:51:24.629 align:start position:0% Then our complete system starts running automatically. 01:51:24.629 --> 01:51:24.639 align:start position:0% automatically. 01:51:24.639 --> 01:51:27.590 align:start position:0% automatically. Things<01:51:24.960> begin<01:51:25.280> to<01:51:25.520> work<01:51:25.679> on<01:51:25.920> their<01:51:26.159> own.<01:51:27.360> We 01:51:27.590 --> 01:51:27.600 align:start position:0% Things begin to work on their own. We 01:51:27.600 --> 01:51:29.189 align:start position:0% Things begin to work on their own. We usually<01:51:28.000> watch<01:51:28.239> these<01:51:28.480> actions<01:51:28.800> in<01:51:29.040> our 01:51:29.189 --> 01:51:29.199 align:start position:0% usually watch these actions in our 01:51:29.199 --> 01:51:32.229 align:start position:0% usually watch these actions in our deployment<01:51:29.679> area.<01:51:30.719> For<01:51:31.040> enterprises,<01:51:32.000> this 01:51:32.229 --> 01:51:32.239 align:start position:0% deployment area. For enterprises, this 01:51:32.239 --> 01:51:35.510 align:start position:0% deployment area. For enterprises, this saves<01:51:32.560> a<01:51:32.880> lot<01:51:33.040> of<01:51:33.280> time.<01:51:33.760> People<01:51:34.880> do<01:51:35.119> not<01:51:35.360> have 01:51:35.510 --> 01:51:35.520 align:start position:0% saves a lot of time. People do not have 01:51:35.520 --> 01:51:38.709 align:start position:0% saves a lot of time. People do not have to<01:51:35.679> fix<01:51:36.000> the<01:51:36.320> same<01:51:36.560> small<01:51:36.960> problems<01:51:37.360> again. 01:51:38.709 --> 01:51:38.719 align:start position:0% to fix the same small problems again. 01:51:38.719 --> 01:51:41.109 align:start position:0% to fix the same small problems again. The<01:51:38.960> codeex<01:51:39.520> assistant<01:51:40.080> helps<01:51:40.400> keep<01:51:40.639> the<01:51:40.880> work 01:51:41.109 --> 01:51:41.119 align:start position:0% The codeex assistant helps keep the work 01:51:41.119 --> 01:51:43.990 align:start position:0% The codeex assistant helps keep the work active.<01:51:42.400> It<01:51:42.639> understands<01:51:43.199> the<01:51:43.440> whole<01:51:43.679> process 01:51:43.990 --> 01:51:44.000 align:start position:0% active. It understands the whole process 01:51:44.000 --> 01:51:46.950 align:start position:0% active. It understands the whole process of<01:51:44.239> how<01:51:44.480> things<01:51:44.800> run.<01:51:46.080> We<01:51:46.320> like<01:51:46.560> having<01:51:46.800> a 01:51:46.950 --> 01:51:46.960 align:start position:0% of how things run. We like having a 01:51:46.960 --> 01:51:49.510 align:start position:0% of how things run. We like having a place<01:51:47.280> without<01:51:47.599> mistakes. 01:51:49.510 --> 01:51:49.520 align:start position:0% place without mistakes. 01:51:49.520 --> 01:51:52.550 align:start position:0% place without mistakes. Now<01:51:50.000> let<01:51:50.239> us<01:51:50.400> look<01:51:50.560> at<01:51:50.800> consistency. 01:51:52.550 --> 01:51:52.560 align:start position:0% Now let us look at consistency. 01:51:52.560 --> 01:51:55.830 align:start position:0% Now let us look at consistency. This<01:51:52.800> is<01:51:52.960> a<01:51:53.280> very<01:51:53.599> important<01:51:54.159> benefit. 01:51:55.830 --> 01:51:55.840 align:start position:0% This is a very important benefit. 01:51:55.840 --> 01:51:58.070 align:start position:0% This is a very important benefit. Sometimes<01:51:56.800> working<01:51:57.199> directly<01:51:57.679> with<01:51:57.840> these 01:51:58.070 --> 01:51:58.080 align:start position:0% Sometimes working directly with these 01:51:58.080 --> 01:52:01.109 align:start position:0% Sometimes working directly with these pipelines<01:51:58.639> can<01:51:58.880> be<01:51:59.040> hard.<01:52:00.080> The<01:52:00.320> steps<01:52:00.719> become 01:52:01.109 --> 01:52:01.119 align:start position:0% pipelines can be hard. The steps become 01:52:01.119 --> 01:52:03.189 align:start position:0% pipelines can be hard. The steps become difficult<01:52:01.440> to<01:52:01.679> manage. 01:52:03.189 --> 01:52:03.199 align:start position:0% difficult to manage. 01:52:03.199 --> 01:52:06.470 align:start position:0% difficult to manage. First<01:52:03.760> I<01:52:04.000> will<01:52:04.159> go<01:52:04.320> to<01:52:04.400> our<01:52:04.639> plug-in<01:52:05.119> section. 01:52:06.470 --> 01:52:06.480 align:start position:0% First I will go to our plug-in section. 01:52:06.480 --> 01:52:09.990 align:start position:0% First I will go to our plug-in section. We<01:52:06.719> can<01:52:06.880> see<01:52:07.040> the<01:52:07.199> GitHub<01:52:07.760> plugin<01:52:08.159> here.<01:52:09.440> Next 01:52:09.990 --> 01:52:10.000 align:start position:0% We can see the GitHub plugin here. Next 01:52:10.000 --> 01:52:13.350 align:start position:0% We can see the GitHub plugin here. Next I<01:52:10.239> will<01:52:10.480> search<01:52:10.639> for<01:52:10.880> codeex<01:52:11.440> in<01:52:11.599> the<01:52:11.760> bar.<01:52:13.119> We 01:52:13.350 --> 01:52:13.360 align:start position:0% I will search for codeex in the bar. We 01:52:13.360 --> 01:52:15.910 align:start position:0% I will search for codeex in the bar. We see<01:52:13.599> many<01:52:13.920> results<01:52:14.800> but<01:52:15.040> I<01:52:15.280> want<01:52:15.360> to<01:52:15.520> find<01:52:15.760> it 01:52:15.910 --> 01:52:15.920 align:start position:0% see many results but I want to find it 01:52:15.920 --> 01:52:18.870 align:start position:0% see many results but I want to find it in<01:52:16.080> the<01:52:16.239> profile<01:52:16.719> settings.<01:52:18.159> I<01:52:18.400> look<01:52:18.560> at<01:52:18.719> the 01:52:18.870 --> 01:52:18.880 align:start position:0% in the profile settings. I look at the 01:52:18.880 --> 01:52:22.070 align:start position:0% in the profile settings. I look at the list<01:52:19.040> of<01:52:19.280> options<01:52:19.599> like<01:52:20.000> packages<01:52:20.960> copilot 01:52:22.070 --> 01:52:22.080 align:start position:0% list of options like packages copilot 01:52:22.080 --> 01:52:24.709 align:start position:0% list of options like packages copilot pages<01:52:22.719> and<01:52:23.040> security. 01:52:24.709 --> 01:52:24.719 align:start position:0% pages and security. 01:52:24.719 --> 01:52:27.510 align:start position:0% pages and security. Here<01:52:25.040> I<01:52:25.280> will<01:52:25.520> search<01:52:25.679> for<01:52:25.840> the<01:52:26.000> codeex. 01:52:27.510 --> 01:52:27.520 align:start position:0% Here I will search for the codeex. 01:52:27.520 --> 01:52:30.629 align:start position:0% Here I will search for the codeex. And<01:52:27.760> here<01:52:28.000> we<01:52:28.239> have<01:52:28.320> our<01:52:28.560> codeex.<01:52:29.920> We<01:52:30.159> can<01:52:30.320> also 01:52:30.629 --> 01:52:30.639 align:start position:0% And here we have our codeex. We can also 01:52:30.639 --> 01:52:33.510 align:start position:0% And here we have our codeex. We can also search<01:52:30.880> in<01:52:31.119> GitHub<01:52:31.679> or<01:52:31.920> settings. 01:52:33.510 --> 01:52:33.520 align:start position:0% search in GitHub or settings. 01:52:33.520 --> 01:52:36.790 align:start position:0% search in GitHub or settings. Then<01:52:34.000> I<01:52:34.239> decide<01:52:34.560> to<01:52:34.719> grant<01:52:35.119> access.<01:52:36.400> To<01:52:36.639> do 01:52:36.790 --> 01:52:36.800 align:start position:0% Then I decide to grant access. To do 01:52:36.800 --> 01:52:39.669 align:start position:0% Then I decide to grant access. To do this,<01:52:37.280> I<01:52:37.599> open<01:52:37.840> our<01:52:38.080> repository. 01:52:39.669 --> 01:52:39.679 align:start position:0% this, I open our repository. 01:52:39.679 --> 01:52:41.830 align:start position:0% this, I open our repository. I<01:52:39.920> click<01:52:40.080> on<01:52:40.239> the<01:52:40.480> code<01:52:40.719> button<01:52:41.040> and<01:52:41.360> copy<01:52:41.679> the 01:52:41.830 --> 01:52:41.840 align:start position:0% I click on the code button and copy the 01:52:41.840 --> 01:52:45.589 align:start position:0% I click on the code button and copy the link.<01:52:43.199> I<01:52:43.440> will<01:52:43.599> ask<01:52:43.760> the<01:52:44.000> chat,<01:52:45.040> do<01:52:45.280> you<01:52:45.440> have 01:52:45.589 --> 01:52:45.599 align:start position:0% link. I will ask the chat, do you have 01:52:45.599 --> 01:52:48.070 align:start position:0% link. I will ask the chat, do you have access<01:52:45.920> to<01:52:46.159> this<01:52:46.400> project? 01:52:48.070 --> 01:52:48.080 align:start position:0% access to this project? 01:52:48.080 --> 01:52:49.910 align:start position:0% access to this project? The<01:52:48.400> system<01:52:48.639> will<01:52:48.880> now<01:52:49.119> check<01:52:49.360> if<01:52:49.599> it<01:52:49.760> can 01:52:49.910 --> 01:52:49.920 align:start position:0% The system will now check if it can 01:52:49.920 --> 01:52:52.229 align:start position:0% The system will now check if it can reach<01:52:50.159> the<01:52:50.400> repository<01:52:51.199> and<01:52:51.520> provide<01:52:51.840> us<01:52:52.000> with 01:52:52.229 --> 01:52:52.239 align:start position:0% reach the repository and provide us with 01:52:52.239 --> 01:52:55.589 align:start position:0% reach the repository and provide us with it<01:52:53.440> and<01:52:53.760> how<01:52:54.000> we<01:52:54.159> can<01:52:54.320> initiate<01:52:54.880> our<01:52:55.199> working 01:52:55.589 --> 01:52:55.599 align:start position:0% it and how we can initiate our working 01:52:55.599 --> 01:52:57.750 align:start position:0% it and how we can initiate our working or<01:52:55.840> a<01:52:56.000> larger<01:52:56.400> scale. 01:52:57.750 --> 01:52:57.760 align:start position:0% or a larger scale. 01:52:57.760 --> 01:52:59.510 align:start position:0% or a larger scale. Sometimes<01:52:58.480> we<01:52:58.719> have<01:52:58.880> to<01:52:59.040> look<01:52:59.119> at<01:52:59.280> these 01:52:59.510 --> 01:52:59.520 align:start position:0% Sometimes we have to look at these 01:52:59.520 --> 01:53:01.750 align:start position:0% Sometimes we have to look at these details<01:53:00.000> ourselves 01:53:01.750 --> 01:53:01.760 align:start position:0% details ourselves 01:53:01.760 --> 01:53:04.390 align:start position:0% details ourselves also.<01:53:02.480> We<01:53:02.719> can<01:53:02.880> take<01:53:03.040> a<01:53:03.280> complete<01:53:03.679> process<01:53:04.080> out 01:53:04.390 --> 01:53:04.400 align:start position:0% also. We can take a complete process out 01:53:04.400 --> 01:53:06.229 align:start position:0% also. We can take a complete process out here<01:53:04.880> and<01:53:05.119> our<01:53:05.360> generation<01:53:05.840> will<01:53:06.080> be 01:53:06.229 --> 01:53:06.239 align:start position:0% here and our generation will be 01:53:06.239 --> 01:53:08.870 align:start position:0% here and our generation will be completed<01:53:06.639> in<01:53:06.800> that.<01:53:08.080> This<01:53:08.320> is<01:53:08.480> usually 01:53:08.870 --> 01:53:08.880 align:start position:0% completed in that. This is usually 01:53:08.880 --> 01:53:12.149 align:start position:0% completed in that. This is usually present<01:53:09.199> at<01:53:09.440> a<01:53:09.520> lesser<01:53:09.920> extent.<01:53:11.360> But<01:53:11.599> now<01:53:11.920> we 01:53:12.149 --> 01:53:12.159 align:start position:0% present at a lesser extent. But now we 01:53:12.159 --> 01:53:14.310 align:start position:0% present at a lesser extent. But now we will<01:53:12.320> initiate<01:53:12.800> a<01:53:13.040> full-fledged<01:53:13.840> process 01:53:14.310 --> 01:53:14.320 align:start position:0% will initiate a full-fledged process 01:53:14.320 --> 01:53:17.109 align:start position:0% will initiate a full-fledged process here.<01:53:15.599> You<01:53:15.840> will<01:53:16.000> see<01:53:16.159> that<01:53:16.320> it<01:53:16.560> has<01:53:16.719> told<01:53:16.960> us 01:53:17.109 --> 01:53:17.119 align:start position:0% here. You will see that it has told us 01:53:17.119 --> 01:53:19.270 align:start position:0% here. You will see that it has told us here<01:53:17.360> that<01:53:17.679> yes,<01:53:18.320> I<01:53:18.560> can<01:53:18.719> access<01:53:19.040> the 01:53:19.270 --> 01:53:19.280 align:start position:0% here that yes, I can access the 01:53:19.280 --> 01:53:22.390 align:start position:0% here that yes, I can access the repository.<01:53:20.719> The<01:53:20.960> access<01:53:21.280> to<01:53:21.520> our<01:53:21.760> repository 01:53:22.390 --> 01:53:22.400 align:start position:0% repository. The access to our repository 01:53:22.400 --> 01:53:24.629 align:start position:0% repository. The access to our repository has<01:53:22.639> also<01:53:22.960> arrived<01:53:23.360> here. 01:53:24.629 --> 01:53:24.639 align:start position:0% has also arrived here. 01:53:24.639 --> 01:53:26.470 align:start position:0% has also arrived here. The<01:53:24.880> second<01:53:25.119> thing<01:53:25.280> it<01:53:25.599> said<01:53:25.840> is<01:53:26.000> that<01:53:26.239> our 01:53:26.470 --> 01:53:26.480 align:start position:0% The second thing it said is that our 01:53:26.480 --> 01:53:29.350 align:start position:0% The second thing it said is that our default<01:53:26.880> branch<01:53:27.280> is<01:53:27.520> main.<01:53:28.400> Visibility<01:53:29.040> is 01:53:29.350 --> 01:53:29.360 align:start position:0% default branch is main. Visibility is 01:53:29.360 --> 01:53:31.830 align:start position:0% default branch is main. Visibility is public<01:53:30.159> and<01:53:30.560> effective<01:53:31.040> permissions<01:53:31.440> in<01:53:31.679> the 01:53:31.830 --> 01:53:31.840 align:start position:0% public and effective permissions in the 01:53:31.840 --> 01:53:35.910 align:start position:0% public and effective permissions in the session<01:53:32.239> are<01:53:32.560> admin,<01:53:33.440> maintain,<01:53:34.480> push,<01:53:35.280> pull 01:53:35.910 --> 01:53:35.920 align:start position:0% session are admin, maintain, push, pull 01:53:35.920 --> 01:53:37.830 align:start position:0% session are admin, maintain, push, pull and<01:53:36.239> triage. 01:53:37.830 --> 01:53:37.840 align:start position:0% and triage. 01:53:37.840 --> 01:53:39.910 align:start position:0% and triage. I<01:53:38.080> can<01:53:38.239> simply<01:53:38.639> say<01:53:38.880> here<01:53:39.040> that<01:53:39.280> we<01:53:39.520> now<01:53:39.760> have 01:53:39.910 --> 01:53:39.920 align:start position:0% I can simply say here that we now have 01:53:39.920 --> 01:53:43.030 align:start position:0% I can simply say here that we now have to<01:53:40.080> include<01:53:40.480> an<01:53:40.800> agents.md<01:53:42.239> file<01:53:42.560> inside 01:53:43.030 --> 01:53:43.040 align:start position:0% to include an agents.md file inside 01:53:43.040 --> 01:53:46.149 align:start position:0% to include an agents.md file inside this.<01:53:44.400> This<01:53:44.639> will<01:53:44.880> directly<01:53:45.360> include<01:53:45.760> it<01:53:45.920> and 01:53:46.149 --> 01:53:46.159 align:start position:0% this. This will directly include it and 01:53:46.159 --> 01:53:49.189 align:start position:0% this. This will directly include it and give<01:53:46.320> it<01:53:46.480> to<01:53:46.639> us.<01:53:47.760> But<01:53:47.920> the<01:53:48.159> thing<01:53:48.320> is<01:53:48.960> we 01:53:49.189 --> 01:53:49.199 align:start position:0% give it to us. But the thing is we 01:53:49.199 --> 01:53:52.070 align:start position:0% give it to us. But the thing is we cannot<01:53:49.599> create<01:53:49.920> things<01:53:50.239> inside<01:53:50.639> this.<01:53:51.760> So 01:53:52.070 --> 01:53:52.080 align:start position:0% cannot create things inside this. So 01:53:52.080 --> 01:53:53.910 align:start position:0% cannot create things inside this. So right<01:53:52.320> now<01:53:52.639> we<01:53:52.880> will<01:53:53.040> only<01:53:53.360> cross-ch<01:53:53.760> checkck 01:53:53.910 --> 01:53:53.920 align:start position:0% right now we will only cross-ch checkck 01:53:53.920 --> 01:53:57.030 align:start position:0% right now we will only cross-ch checkck our<01:53:54.159> agents.mmd<01:53:55.360> file<01:53:55.679> here<01:53:56.159> to<01:53:56.400> see<01:53:56.480> if<01:53:56.639> it<01:53:56.880> is 01:53:57.030 --> 01:53:57.040 align:start position:0% our agents.mmd file here to see if it is 01:53:57.040 --> 01:53:59.990 align:start position:0% our agents.mmd file here to see if it is directly<01:53:57.440> available<01:53:57.840> to<01:53:58.080> us<01:53:58.239> or<01:53:58.480> not.<01:53:59.599> These 01:53:59.990 --> 01:54:00.000 align:start position:0% directly available to us or not. These 01:54:00.000 --> 01:54:03.430 align:start position:0% directly available to us or not. These are<01:54:00.080> our<01:54:00.400> things.<01:54:01.840> I<01:54:02.080> will<01:54:02.239> now<01:54:02.560> take<01:54:02.800> our<01:54:03.119> full 01:54:03.430 --> 01:54:03.440 align:start position:0% are our things. I will now take our full 01:54:03.440 --> 01:54:06.149 align:start position:0% are our things. I will now take our full detailed<01:54:04.000> discussion.<01:54:05.360> You<01:54:05.599> will<01:54:05.760> see<01:54:05.920> that 01:54:06.149 --> 01:54:06.159 align:start position:0% detailed discussion. You will see that 01:54:06.159 --> 01:54:08.709 align:start position:0% detailed discussion. You will see that directly<01:54:06.719> after<01:54:07.040> just<01:54:07.360> 1<01:54:07.599> second<01:54:08.400> our 01:54:08.709 --> 01:54:08.719 align:start position:0% directly after just 1 second our 01:54:08.719 --> 01:54:12.390 align:start position:0% directly after just 1 second our agents.md<01:54:10.000> file<01:54:10.320> has<01:54:10.560> been<01:54:10.639> included<01:54:11.199> here 01:54:12.390 --> 01:54:12.400 align:start position:0% agents.md file has been included here 01:54:12.400 --> 01:54:14.870 align:start position:0% agents.md file has been included here inside<01:54:12.800> it.<01:54:13.280> As<01:54:13.440> you<01:54:13.599> see<01:54:14.159> git<01:54:14.560> isn't 01:54:14.870 --> 01:54:14.880 align:start position:0% inside it. As you see git isn't 01:54:14.880 --> 01:54:18.229 align:start position:0% inside it. As you see git isn't available.<01:54:16.159> So<01:54:16.400> here<01:54:16.800> after<01:54:17.119> inspecting<01:54:18.080> it 01:54:18.229 --> 01:54:18.239 align:start position:0% available. So here after inspecting it 01:54:18.239 --> 01:54:20.470 align:start position:0% available. So here after inspecting it has<01:54:18.480> directly<01:54:18.960> arrived. 01:54:20.470 --> 01:54:20.480 align:start position:0% has directly arrived. 01:54:20.480 --> 01:54:22.709 align:start position:0% has directly arrived. I<01:54:20.719> can<01:54:20.880> give<01:54:21.119> access<01:54:21.440> here<01:54:21.760> to<01:54:22.000> directly<01:54:22.400> push 01:54:22.709 --> 01:54:22.719 align:start position:0% I can give access here to directly push 01:54:22.719 --> 01:54:25.109 align:start position:0% I can give access here to directly push the<01:54:22.960> code<01:54:23.440> to<01:54:23.679> see<01:54:23.840> how<01:54:24.080> we<01:54:24.239> can<01:54:24.400> improve<01:54:24.880> or 01:54:25.109 --> 01:54:25.119 align:start position:0% the code to see how we can improve or 01:54:25.119 --> 01:54:27.830 align:start position:0% the code to see how we can improve or include<01:54:25.520> things<01:54:25.760> on<01:54:25.920> a<01:54:26.080> large<01:54:26.320> scale 01:54:27.830 --> 01:54:27.840 align:start position:0% include things on a large scale 01:54:27.840 --> 01:54:30.149 align:start position:0% include things on a large scale side<01:54:28.159> by<01:54:28.480> side.<01:54:28.960> Another<01:54:29.360> very<01:54:29.760> important 01:54:30.149 --> 01:54:30.159 align:start position:0% side by side. Another very important 01:54:30.159 --> 01:54:33.189 align:start position:0% side by side. Another very important thing<01:54:30.400> is<01:54:30.639> running<01:54:30.880> here.<01:54:32.080> Usually<01:54:32.560> in<01:54:32.719> a<01:54:32.880> base 01:54:33.189 --> 01:54:33.199 align:start position:0% thing is running here. Usually in a base 01:54:33.199 --> 01:54:36.149 align:start position:0% thing is running here. Usually in a base pipeline<01:54:34.080> I<01:54:34.320> could<01:54:34.480> not<01:54:34.639> run<01:54:34.960> git<01:54:35.360> push<01:54:35.679> origin 01:54:36.149 --> 01:54:36.159 align:start position:0% pipeline I could not run git push origin 01:54:36.159 --> 01:54:38.470 align:start position:0% pipeline I could not run git push origin here<01:54:36.639> because<01:54:36.960> the<01:54:37.199> directory<01:54:37.679> is<01:54:37.840> not<01:54:38.000> a<01:54:38.159> git 01:54:38.470 --> 01:54:38.480 align:start position:0% here because the directory is not a git 01:54:38.480 --> 01:54:41.430 align:start position:0% here because the directory is not a git repository.<01:54:39.920> Git<01:54:40.320> is<01:54:40.480> not<01:54:40.639> installed<01:54:41.040> in<01:54:41.280> our 01:54:41.430 --> 01:54:41.440 align:start position:0% repository. Git is not installed in our 01:54:41.440 --> 01:54:44.470 align:start position:0% repository. Git is not installed in our current<01:54:41.760> shell.<01:54:43.119> Let<01:54:43.360> us<01:54:43.599> suppose<01:54:43.920> we<01:54:44.159> want<01:54:44.320> to 01:54:44.470 --> 01:54:44.480 align:start position:0% current shell. Let us suppose we want to 01:54:44.480 --> 01:54:47.750 align:start position:0% current shell. Let us suppose we want to install<01:54:44.880> git.<01:54:45.679> How<01:54:45.920> can<01:54:46.080> we<01:54:46.239> do<01:54:46.400> that? 01:54:47.750 --> 01:54:47.760 align:start position:0% install git. How can we do that? 01:54:47.760 --> 01:54:49.189 align:start position:0% install git. How can we do that? First<01:54:48.000> of<01:54:48.159> all,<01:54:48.400> we<01:54:48.639> will<01:54:48.800> open<01:54:48.960> our 01:54:49.189 --> 01:54:49.199 align:start position:0% First of all, we will open our 01:54:49.199 --> 01:54:51.830 align:start position:0% First of all, we will open our PowerShell.<01:54:49.840> Here<01:54:50.719> we<01:54:51.040> come<01:54:51.199> inside<01:54:51.599> this 01:54:51.830 --> 01:54:51.840 align:start position:0% PowerShell. Here we come inside this 01:54:51.840 --> 01:54:55.669 align:start position:0% PowerShell. Here we come inside this one.<01:54:52.719> Here<01:54:53.040> I<01:54:53.360> say<01:54:53.679> our<01:54:53.920> PowerShell.<01:54:55.360> This<01:54:55.599> is 01:54:55.669 --> 01:54:55.679 align:start position:0% one. Here I say our PowerShell. This is 01:54:55.679 --> 01:54:58.790 align:start position:0% one. Here I say our PowerShell. This is our<01:54:55.920> PowerShell<01:54:56.480> window.<01:54:57.920> Coming<01:54:58.239> directly 01:54:58.790 --> 01:54:58.800 align:start position:0% our PowerShell window. Coming directly 01:54:58.800 --> 01:55:01.270 align:start position:0% our PowerShell window. Coming directly inside<01:54:59.199> PowerShell,<01:55:00.080> we<01:55:00.320> will<01:55:00.480> state<01:55:00.800> our<01:55:00.960> git 01:55:01.270 --> 01:55:01.280 align:start position:0% inside PowerShell, we will state our git 01:55:01.280 --> 01:55:03.830 align:start position:0% inside PowerShell, we will state our git version.<01:55:01.679> Here<01:55:02.800> you<01:55:03.040> are<01:55:03.199> seeing<01:55:03.440> that<01:55:03.679> the 01:55:03.830 --> 01:55:03.840 align:start position:0% version. Here you are seeing that the 01:55:03.840 --> 01:55:06.870 align:start position:0% version. Here you are seeing that the git<01:55:04.159> version<01:55:04.400> is<01:55:04.639> available<01:55:05.040> to<01:55:05.199> us<01:55:05.440> here.<01:55:06.639> Let 01:55:06.870 --> 01:55:06.880 align:start position:0% git version is available to us here. Let 01:55:06.880 --> 01:55:09.669 align:start position:0% git version is available to us here. Let us<01:55:07.119> suppose<01:55:07.440> we<01:55:07.679> want<01:55:07.840> to<01:55:08.000> install<01:55:08.320> our<01:55:08.560> git. 01:55:09.669 --> 01:55:09.679 align:start position:0% us suppose we want to install our git. 01:55:09.679 --> 01:55:11.990 align:start position:0% us suppose we want to install our git. If<01:55:09.920> we<01:55:10.080> use<01:55:10.239> this<01:55:10.560> directly,<01:55:11.440> you<01:55:11.679> are<01:55:11.840> seeing 01:55:11.990 --> 01:55:12.000 align:start position:0% If we use this directly, you are seeing 01:55:12.000 --> 01:55:14.070 align:start position:0% If we use this directly, you are seeing that<01:55:12.320> now<01:55:12.480> we<01:55:12.719> will<01:55:12.880> say<01:55:13.119> we<01:55:13.360> want<01:55:13.520> to<01:55:13.679> install 01:55:14.070 --> 01:55:14.080 align:start position:0% that now we will say we want to install 01:55:14.080 --> 01:55:16.709 align:start position:0% that now we will say we want to install git<01:55:14.480> with<01:55:14.639> our<01:55:14.800> basic<01:55:15.199> widget. 01:55:16.709 --> 01:55:16.719 align:start position:0% git with our basic widget. 01:55:16.719 --> 01:55:18.390 align:start position:0% git with our basic widget. Automatically<01:55:17.440> our<01:55:17.679> widget<01:55:18.080> will<01:55:18.239> be 01:55:18.390 --> 01:55:18.400 align:start position:0% Automatically our widget will be 01:55:18.400 --> 01:55:21.030 align:start position:0% Automatically our widget will be installed<01:55:18.800> here.<01:55:20.000> On<01:55:20.239> the<01:55:20.400> basis<01:55:20.639> of<01:55:20.800> that 01:55:21.030 --> 01:55:21.040 align:start position:0% installed here. On the basis of that 01:55:21.040 --> 01:55:23.350 align:start position:0% installed here. On the basis of that widget,<01:55:21.760> we<01:55:22.000> will<01:55:22.159> take<01:55:22.400> our<01:55:22.639> things<01:55:22.880> inside 01:55:23.350 --> 01:55:23.360 align:start position:0% widget, we will take our things inside 01:55:23.360 --> 01:55:26.149 align:start position:0% widget, we will take our things inside running.<01:55:24.719> Usually<01:55:25.280> these<01:55:25.599> things<01:55:25.760> are<01:55:26.000> not 01:55:26.149 --> 01:55:26.159 align:start position:0% running. Usually these things are not 01:55:26.159 --> 01:55:28.709 align:start position:0% running. Usually these things are not explained<01:55:26.560> to<01:55:26.719> us.<01:55:27.599> We<01:55:27.840> are<01:55:28.000> just<01:55:28.159> initiating 01:55:28.709 --> 01:55:28.719 align:start position:0% explained to us. We are just initiating 01:55:28.719 --> 01:55:30.550 align:start position:0% explained to us. We are just initiating our<01:55:28.960> production<01:55:29.360> and<01:55:29.679> working<01:55:29.840> on<01:55:30.080> a<01:55:30.239> large 01:55:30.550 --> 01:55:30.560 align:start position:0% our production and working on a large 01:55:30.560 --> 01:55:33.430 align:start position:0% our production and working on a large scale.<01:55:31.920> Here<01:55:32.239> it<01:55:32.480> will<01:55:32.639> take<01:55:32.880> some<01:55:33.119> time<01:55:33.280> to 01:55:33.430 --> 01:55:33.440 align:start position:0% scale. Here it will take some time to 01:55:33.440 --> 01:55:34.950 align:start position:0% scale. Here it will take some time to install. 01:55:34.950 --> 01:55:34.960 align:start position:0% install. 01:55:34.960 --> 01:55:37.990 align:start position:0% install. Until<01:55:35.280> it<01:55:35.520> installs,<01:55:36.080> we<01:55:36.320> will<01:55:36.480> wait<01:55:36.719> here. 01:55:37.990 --> 01:55:38.000 align:start position:0% Until it installs, we will wait here. 01:55:38.000 --> 01:55:40.629 align:start position:0% Until it installs, we will wait here. Now<01:55:38.320> due<01:55:38.560> to<01:55:38.719> some<01:55:38.880> issues<01:55:39.599> our<01:55:39.840> git<01:55:40.239> is<01:55:40.400> not 01:55:40.629 --> 01:55:40.639 align:start position:0% Now due to some issues our git is not 01:55:40.639 --> 01:55:43.350 align:start position:0% Now due to some issues our git is not becoming<01:55:41.040> active.<01:55:42.320> I<01:55:42.560> tried<01:55:42.800> a<01:55:42.960> lot<01:55:43.119> to 01:55:43.350 --> 01:55:43.360 align:start position:0% becoming active. I tried a lot to 01:55:43.360 --> 01:55:45.830 align:start position:0% becoming active. I tried a lot to activate<01:55:43.760> our<01:55:43.920> git.<01:55:45.040> You<01:55:45.199> are<01:55:45.360> seeing<01:55:45.599> the 01:55:45.830 --> 01:55:45.840 align:start position:0% activate our git. You are seeing the 01:55:45.840 --> 01:55:49.030 align:start position:0% activate our git. You are seeing the prefix<01:55:47.040> branch<01:55:47.440> prefix<01:55:47.920> is<01:55:48.159> working. 01:55:49.030 --> 01:55:49.040 align:start position:0% prefix branch prefix is working. 01:55:49.040 --> 01:55:51.750 align:start position:0% prefix branch prefix is working. Everything<01:55:49.440> is<01:55:49.679> working.<01:55:50.880> We<01:55:51.119> usually<01:55:51.520> did 01:55:51.750 --> 01:55:51.760 align:start position:0% Everything is working. We usually did 01:55:51.760 --> 01:55:54.390 align:start position:0% Everything is working. We usually did not<01:55:51.920> include<01:55:52.239> our<01:55:52.480> commit<01:55:52.880> instructions.<01:55:54.239> But 01:55:54.390 --> 01:55:54.400 align:start position:0% not include our commit instructions. But 01:55:54.400 --> 01:55:56.550 align:start position:0% not include our commit instructions. But still<01:55:55.040> it<01:55:55.280> is<01:55:55.440> possible<01:55:55.760> that<01:55:56.000> by<01:55:56.239> opening 01:55:56.550 --> 01:55:56.560 align:start position:0% still it is possible that by opening 01:55:56.560 --> 01:55:59.109 align:start position:0% still it is possible that by opening these<01:55:56.880> things<01:55:57.599> all<01:55:57.840> these<01:55:58.159> items<01:55:58.639> come<01:55:58.800> into 01:55:59.109 --> 01:55:59.119 align:start position:0% these things all these items come into 01:55:59.119 --> 01:56:00.790 align:start position:0% these things all these items come into working. 01:56:00.790 --> 01:56:00.800 align:start position:0% working. 01:56:00.800 --> 01:56:03.109 align:start position:0% working. But<01:56:01.040> still,<01:56:01.360> as<01:56:01.599> a<01:56:01.760> matter<01:56:01.920> of<01:56:02.159> fact,<01:56:02.800> the 01:56:03.109 --> 01:56:03.119 align:start position:0% But still, as a matter of fact, the 01:56:03.119 --> 01:56:05.030 align:start position:0% But still, as a matter of fact, the discussion<01:56:03.520> here<01:56:03.760> is<01:56:04.000> that<01:56:04.159> when<01:56:04.400> integrating 01:56:05.030 --> 01:56:05.040 align:start position:0% discussion here is that when integrating 01:56:05.040 --> 01:56:07.510 align:start position:0% discussion here is that when integrating codeex,<01:56:06.080> organizations<01:56:06.960> start<01:56:07.280> in 01:56:07.510 --> 01:56:07.520 align:start position:0% codeex, organizations start in 01:56:07.520 --> 01:56:09.830 align:start position:0% codeex, organizations start in non-production<01:56:08.320> environments. 01:56:09.830 --> 01:56:09.840 align:start position:0% non-production environments. 01:56:09.840 --> 01:56:12.070 align:start position:0% non-production environments. This<01:56:10.080> allows<01:56:10.480> codeex<01:56:11.040> to<01:56:11.199> analyze<01:56:11.599> failures 01:56:12.070 --> 01:56:12.080 align:start position:0% This allows codeex to analyze failures 01:56:12.080 --> 01:56:14.550 align:start position:0% This allows codeex to analyze failures and<01:56:12.400> generate<01:56:12.800> suggestions. 01:56:14.550 --> 01:56:14.560 align:start position:0% and generate suggestions. 01:56:14.560 --> 01:56:16.550 align:start position:0% and generate suggestions. Once<01:56:14.880> the<01:56:15.040> team<01:56:15.280> gains<01:56:15.679> confidence<01:56:16.159> in<01:56:16.320> the 01:56:16.550 --> 01:56:16.560 align:start position:0% Once the team gains confidence in the 01:56:16.560 --> 01:56:18.709 align:start position:0% Once the team gains confidence in the results,<01:56:17.280> they<01:56:17.520> can<01:56:17.679> gradually<01:56:18.159> introduce 01:56:18.709 --> 01:56:18.719 align:start position:0% results, they can gradually introduce 01:56:18.719 --> 01:56:21.270 align:start position:0% results, they can gradually introduce more<01:56:18.960> advanced<01:56:19.520> workflows. 01:56:21.270 --> 01:56:21.280 align:start position:0% more advanced workflows. 01:56:21.280 --> 01:56:23.430 align:start position:0% more advanced workflows. These<01:56:21.599> include<01:56:22.159> automated<01:56:22.719> pull<01:56:23.040> request 01:56:23.430 --> 01:56:23.440 align:start position:0% These include automated pull request 01:56:23.440 --> 01:56:26.149 align:start position:0% These include automated pull request generations<01:56:24.400> and<01:56:24.639> our<01:56:24.880> AI<01:56:25.360> assisted<01:56:25.840> bug 01:56:26.149 --> 01:56:26.159 align:start position:0% generations and our AI assisted bug 01:56:26.159 --> 01:56:29.510 align:start position:0% generations and our AI assisted bug fixing.<01:56:27.440> Overall,<01:56:28.320> codeex<01:56:28.880> acts<01:56:29.199> as<01:56:29.360> an 01:56:29.510 --> 01:56:29.520 align:start position:0% fixing. Overall, codeex acts as an 01:56:29.520 --> 01:56:32.070 align:start position:0% fixing. Overall, codeex acts as an intelligent<01:56:30.159> engineering<01:56:30.719> assistant<01:56:31.599> inside 01:56:32.070 --> 01:56:32.080 align:start position:0% intelligent engineering assistant inside 01:56:32.080 --> 01:56:36.229 align:start position:0% intelligent engineering assistant inside our<01:56:32.400> CI/CD<01:56:33.679> pipeline.<01:56:35.119> It<01:56:35.360> will<01:56:35.520> overall<01:56:36.000> help 01:56:36.229 --> 01:56:36.239 align:start position:0% our CI/CD pipeline. It will overall help 01:56:36.239 --> 01:56:39.189 align:start position:0% our CI/CD pipeline. It will overall help us<01:56:36.400> in<01:56:36.639> building<01:56:36.960> all<01:56:37.199> our<01:56:37.440> things.<01:56:38.800> These 01:56:39.189 --> 01:56:39.199 align:start position:0% us in building all our things. These 01:56:39.199 --> 01:56:41.430 align:start position:0% us in building all our things. These entire<01:56:39.679> matters<01:56:40.000> have<01:56:40.239> been<01:56:40.400> discussed<01:56:40.800> here. 01:56:41.430 --> 01:56:41.440 align:start position:0% entire matters have been discussed here. 01:56:41.440 --> 01:56:43.910 align:start position:0% entire matters have been discussed here. An<01:56:41.760> autofix<01:56:42.400> workflow<01:56:42.800> begins<01:56:43.119> the<01:56:43.360> moment<01:56:43.599> a 01:56:43.910 --> 01:56:43.920 align:start position:0% An autofix workflow begins the moment a 01:56:43.920 --> 01:56:46.550 align:start position:0% An autofix workflow begins the moment a developer<01:56:44.320> pushes<01:56:44.719> code<01:56:44.960> to<01:56:45.119> a<01:56:45.360> repository<01:56:46.239> or 01:56:46.550 --> 01:56:46.560 align:start position:0% developer pushes code to a repository or 01:56:46.560 --> 01:56:49.270 align:start position:0% developer pushes code to a repository or submits<01:56:46.960> a<01:56:47.119> pull<01:56:47.360> request<01:56:47.679> for<01:56:47.920> review. 01:56:49.270 --> 01:56:49.280 align:start position:0% submits a pull request for review. 01:56:49.280 --> 01:56:52.629 align:start position:0% submits a pull request for review. The<01:56:49.599> CI/CD<01:56:50.880> pipeline<01:56:51.520> automatically<01:56:52.239> starts 01:56:52.629 --> 01:56:52.639 align:start position:0% The CI/CD pipeline automatically starts 01:56:52.639 --> 01:56:55.430 align:start position:0% The CI/CD pipeline automatically starts a<01:56:52.880> series<01:56:53.199> of<01:56:53.360> validation<01:56:54.000> processes<01:56:55.040> such<01:56:55.280> as 01:56:55.430 --> 01:56:55.440 align:start position:0% a series of validation processes such as 01:56:55.440 --> 01:56:57.669 align:start position:0% a series of validation processes such as compiling<01:56:55.920> the<01:56:56.159> application,<01:56:57.280> running 01:56:57.669 --> 01:56:57.679 align:start position:0% compiling the application, running 01:56:57.679 --> 01:56:59.990 align:start position:0% compiling the application, running automated<01:56:58.320> tests,<01:56:59.280> checking<01:56:59.760> code 01:56:59.990 --> 01:57:00.000 align:start position:0% automated tests, checking code 01:57:00.000 --> 01:57:02.709 align:start position:0% automated tests, checking code formatting<01:57:00.560> standards,<01:57:01.679> verifying<01:57:02.320> linting 01:57:02.709 --> 01:57:02.719 align:start position:0% formatting standards, verifying linting 01:57:02.719 --> 01:57:06.709 align:start position:0% formatting standards, verifying linting rules,<01:57:03.520> and<01:57:03.840> executing<01:57:04.480> security<01:57:05.040> scans. 01:57:06.709 --> 01:57:06.719 align:start position:0% rules, and executing security scans. 01:57:06.719 --> 01:57:08.390 align:start position:0% rules, and executing security scans. In<01:57:06.960> traditional<01:57:07.520> software<01:57:07.920> development 01:57:08.390 --> 01:57:08.400 align:start position:0% In traditional software development 01:57:08.400 --> 01:57:10.790 align:start position:0% In traditional software development environments,<01:57:09.599> any<01:57:10.000> failure<01:57:10.320> in<01:57:10.560> these 01:57:10.790 --> 01:57:10.800 align:start position:0% environments, any failure in these 01:57:10.800 --> 01:57:12.629 align:start position:0% environments, any failure in these checks<01:57:11.119> would<01:57:11.360> require<01:57:11.679> a<01:57:11.920> developer<01:57:12.400> to 01:57:12.629 --> 01:57:12.639 align:start position:0% checks would require a developer to 01:57:12.639 --> 01:57:15.510 align:start position:0% checks would require a developer to manually<01:57:13.199> investigate<01:57:13.840> logs,<01:57:14.880> identify<01:57:15.280> the 01:57:15.510 --> 01:57:15.520 align:start position:0% manually investigate logs, identify the 01:57:15.520 --> 01:57:17.589 align:start position:0% manually investigate logs, identify the source<01:57:15.679> of<01:57:15.840> the<01:57:16.000> issue,<01:57:16.639> and<01:57:16.960> implement<01:57:17.360> a 01:57:17.589 --> 01:57:17.599 align:start position:0% source of the issue, and implement a 01:57:17.599 --> 01:57:18.870 align:start position:0% source of the issue, and implement a fix. 01:57:18.870 --> 01:57:18.880 align:start position:0% fix. 01:57:18.880 --> 01:57:21.589 align:start position:0% fix. With<01:57:19.199> codeex<01:57:19.760> powered<01:57:20.080> autofix<01:57:20.719> workflows, 01:57:21.589 --> 01:57:21.599 align:start position:0% With codeex powered autofix workflows, 01:57:21.599 --> 01:57:23.750 align:start position:0% With codeex powered autofix workflows, the<01:57:21.920> process<01:57:22.320> becomes<01:57:22.800> significantly<01:57:23.520> more 01:57:23.750 --> 01:57:23.760 align:start position:0% the process becomes significantly more 01:57:23.760 --> 01:57:26.629 align:start position:0% the process becomes significantly more efficient.<01:57:25.199> Instead<01:57:25.599> of<01:57:25.840> merely<01:57:26.239> reporting 01:57:26.629 --> 01:57:26.639 align:start position:0% efficient. Instead of merely reporting 01:57:26.639 --> 01:57:29.109 align:start position:0% efficient. Instead of merely reporting that<01:57:26.880> something<01:57:27.280> failed,<01:57:28.159> the<01:57:28.400> workflow<01:57:28.880> can 01:57:29.109 --> 01:57:29.119 align:start position:0% that something failed, the workflow can 01:57:29.119 --> 01:57:31.270 align:start position:0% that something failed, the workflow can immediately<01:57:29.679> begin<01:57:30.000> analyzing<01:57:30.560> the<01:57:30.800> problem 01:57:31.270 --> 01:57:31.280 align:start position:0% immediately begin analyzing the problem 01:57:31.280 --> 01:57:34.390 align:start position:0% immediately begin analyzing the problem and<01:57:31.599> preparing<01:57:32.000> a<01:57:32.239> potential<01:57:32.639> solution. 01:57:34.390 --> 01:57:34.400 align:start position:0% and preparing a potential solution. 01:57:34.400 --> 01:57:37.030 align:start position:0% and preparing a potential solution. This<01:57:34.719> transforms<01:57:35.520> CI/CD 01:57:37.030 --> 01:57:37.040 align:start position:0% This transforms CI/CD 01:57:37.040 --> 01:57:39.750 align:start position:0% This transforms CI/CD from<01:57:37.280> a<01:57:37.440> passive<01:57:37.920> validation<01:57:38.480> system<01:57:39.199> into<01:57:39.520> an 01:57:39.750 --> 01:57:39.760 align:start position:0% from a passive validation system into an 01:57:39.760 --> 01:57:41.589 align:start position:0% from a passive validation system into an active<01:57:40.239> participant<01:57:40.880> in<01:57:41.119> software 01:57:41.589 --> 01:57:41.599 align:start position:0% active participant in software 01:57:41.599 --> 01:57:44.550 align:start position:0% active participant in software maintenance<01:57:42.080> and<01:57:42.400> quality<01:57:42.800> assurance. 01:57:44.550 --> 01:57:44.560 align:start position:0% maintenance and quality assurance. 01:57:44.560 --> 01:57:47.030 align:start position:0% maintenance and quality assurance. Once<01:57:44.880> a<01:57:45.040> failure<01:57:45.360> is<01:57:45.520> detected,<01:57:46.480> Codeex 01:57:47.030 --> 01:57:47.040 align:start position:0% Once a failure is detected, Codeex 01:57:47.040 --> 01:57:48.790 align:start position:0% Once a failure is detected, Codeex examines<01:57:47.520> all<01:57:47.760> available<01:57:48.320> information 01:57:48.790 --> 01:57:48.800 align:start position:0% examines all available information 01:57:48.800 --> 01:57:51.510 align:start position:0% examines all available information related<01:57:49.119> to<01:57:49.280> the<01:57:49.520> problem.<01:57:50.719> This<01:57:50.960> includes 01:57:51.510 --> 01:57:51.520 align:start position:0% related to the problem. This includes 01:57:51.520 --> 01:57:54.390 align:start position:0% related to the problem. This includes error<01:57:51.760> messages,<01:57:52.800> build<01:57:53.119> logs,<01:57:54.000> test 01:57:54.390 --> 01:57:54.400 align:start position:0% error messages, build logs, test 01:57:54.400 --> 01:57:57.589 align:start position:0% error messages, build logs, test outputs,<01:57:55.599> recently<01:57:56.080> modified<01:57:56.639> files, 01:57:57.589 --> 01:57:57.599 align:start position:0% outputs, recently modified files, 01:57:57.599 --> 01:57:59.990 align:start position:0% outputs, recently modified files, project<01:57:58.000> documentation,<01:57:59.360> repository 01:57:59.990 --> 01:58:00.000 align:start position:0% project documentation, repository 01:58:00.000 --> 01:58:02.229 align:start position:0% project documentation, repository instructions,<01:58:01.199> and<01:58:01.440> any<01:58:01.760> development 01:58:02.229 --> 01:58:02.239 align:start position:0% instructions, and any development 01:58:02.239 --> 01:58:05.750 align:start position:0% instructions, and any development guidelines<01:58:02.800> defined<01:58:03.199> in<01:58:03.520> agents.mmd. 01:58:05.750 --> 01:58:05.760 align:start position:0% guidelines defined in agents.mmd. 01:58:05.760 --> 01:58:07.990 align:start position:0% guidelines defined in agents.mmd. By<01:58:06.000> reviewing<01:58:06.400> these<01:58:06.719> sources<01:58:07.119> together, 01:58:07.990 --> 01:58:08.000 align:start position:0% By reviewing these sources together, 01:58:08.000 --> 01:58:09.669 align:start position:0% By reviewing these sources together, Codeex<01:58:08.480> gains<01:58:08.800> a<01:58:09.040> much<01:58:09.280> broader 01:58:09.669 --> 01:58:09.679 align:start position:0% Codeex gains a much broader 01:58:09.679 --> 01:58:11.669 align:start position:0% Codeex gains a much broader understanding<01:58:10.159> of<01:58:10.320> the<01:58:10.560> issue<01:58:10.880> than<01:58:11.119> a<01:58:11.280> simple 01:58:11.669 --> 01:58:11.679 align:start position:0% understanding of the issue than a simple 01:58:11.679 --> 01:58:14.229 align:start position:0% understanding of the issue than a simple rule-based<01:58:12.320> automation<01:58:12.880> tool. 01:58:14.229 --> 01:58:14.239 align:start position:0% rule-based automation tool. 01:58:14.239 --> 01:58:16.870 align:start position:0% rule-based automation tool. For<01:58:14.480> example,<01:58:15.360> if<01:58:15.599> a<01:58:15.760> login<01:58:16.159> related<01:58:16.560> test 01:58:16.870 --> 01:58:16.880 align:start position:0% For example, if a login related test 01:58:16.880 --> 01:58:19.510 align:start position:0% For example, if a login related test starts<01:58:17.280> failing<01:58:17.679> after<01:58:17.920> a<01:58:18.159> recent<01:58:18.400> update, 01:58:19.510 --> 01:58:19.520 align:start position:0% starts failing after a recent update, 01:58:19.520 --> 01:58:21.510 align:start position:0% starts failing after a recent update, Codeex<01:58:20.080> can<01:58:20.239> inspect<01:58:20.560> the<01:58:20.800> authentication 01:58:21.510 --> 01:58:21.520 align:start position:0% Codeex can inspect the authentication 01:58:21.520 --> 01:58:24.870 align:start position:0% Codeex can inspect the authentication logic,<01:58:22.560> compare<01:58:22.880> the<01:58:23.119> recent<01:58:23.440> code<01:58:23.760> changes, 01:58:24.870 --> 01:58:24.880 align:start position:0% logic, compare the recent code changes, 01:58:24.880 --> 01:58:27.430 align:start position:0% logic, compare the recent code changes, review<01:58:25.199> the<01:58:25.440> affected<01:58:25.920> test<01:58:26.239> cases,<01:58:27.119> and 01:58:27.430 --> 01:58:27.440 align:start position:0% review the affected test cases, and 01:58:27.440 --> 01:58:29.350 align:start position:0% review the affected test cases, and determine<01:58:27.840> where<01:58:28.080> the<01:58:28.320> behavior<01:58:28.800> diverged 01:58:29.350 --> 01:58:29.360 align:start position:0% determine where the behavior diverged 01:58:29.360 --> 01:58:31.430 align:start position:0% determine where the behavior diverged from<01:58:29.599> expectations. 01:58:31.430 --> 01:58:31.440 align:start position:0% from expectations. 01:58:31.440 --> 01:58:33.430 align:start position:0% from expectations. This<01:58:31.760> contextual<01:58:32.400> understanding<01:58:32.960> is<01:58:33.199> one<01:58:33.360> of 01:58:33.430 --> 01:58:33.440 align:start position:0% This contextual understanding is one of 01:58:33.440 --> 01:58:35.750 align:start position:0% This contextual understanding is one of the<01:58:33.679> major<01:58:34.000> advantages<01:58:34.560> of<01:58:34.880> AI<01:58:35.280> assisted 01:58:35.750 --> 01:58:35.760 align:start position:0% the major advantages of AI assisted 01:58:35.760 --> 01:58:37.910 align:start position:0% the major advantages of AI assisted development<01:58:36.239> workflows. 01:58:37.910 --> 01:58:37.920 align:start position:0% development workflows. 01:58:37.920 --> 01:58:39.350 align:start position:0% development workflows. After<01:58:38.239> gathering<01:58:38.639> the<01:58:38.880> necessary 01:58:39.350 --> 01:58:39.360 align:start position:0% After gathering the necessary 01:58:39.360 --> 01:58:42.070 align:start position:0% After gathering the necessary information,<01:58:40.400> Codeex<01:58:40.960> performs<01:58:41.440> root<01:58:41.760> cause 01:58:42.070 --> 01:58:42.080 align:start position:0% information, Codeex performs root cause 01:58:42.080 --> 01:58:43.589 align:start position:0% information, Codeex performs root cause analysis. 01:58:43.589 --> 01:58:43.599 align:start position:0% analysis. 01:58:43.599 --> 01:58:45.189 align:start position:0% analysis. Rather<01:58:44.000> than<01:58:44.159> attempting<01:58:44.719> random 01:58:45.189 --> 01:58:45.199 align:start position:0% Rather than attempting random 01:58:45.199 --> 01:58:47.990 align:start position:0% Rather than attempting random modifications<01:58:46.000> until<01:58:46.320> a<01:58:46.480> test<01:58:46.719> passes,<01:58:47.760> it 01:58:47.990 --> 01:58:48.000 align:start position:0% modifications until a test passes, it 01:58:48.000 --> 01:58:49.830 align:start position:0% modifications until a test passes, it tries<01:58:48.239> to<01:58:48.480> determine<01:58:48.960> why<01:58:49.199> the<01:58:49.440> failure 01:58:49.830 --> 01:58:49.840 align:start position:0% tries to determine why the failure 01:58:49.840 --> 01:58:51.990 align:start position:0% tries to determine why the failure occurred<01:58:50.159> in<01:58:50.400> the<01:58:50.560> first<01:58:50.719> place. 01:58:51.990 --> 01:58:52.000 align:start position:0% occurred in the first place. 01:58:52.000 --> 01:58:53.990 align:start position:0% occurred in the first place. The<01:58:52.320> underlying<01:58:52.800> issue<01:58:53.199> could<01:58:53.360> be<01:58:53.520> a<01:58:53.679> missing 01:58:53.990 --> 01:58:54.000 align:start position:0% The underlying issue could be a missing 01:58:54.000 --> 01:58:56.470 align:start position:0% The underlying issue could be a missing import<01:58:54.400> statement,<01:58:55.360> a<01:58:55.599> renamed<01:58:56.080> function 01:58:56.470 --> 01:58:56.480 align:start position:0% import statement, a renamed function 01:58:56.480 --> 01:58:58.790 align:start position:0% import statement, a renamed function that<01:58:56.800> was<01:58:56.960> not<01:58:57.119> updated<01:58:57.599> everywhere,<01:58:58.560> a 01:58:58.790 --> 01:58:58.800 align:start position:0% that was not updated everywhere, a 01:58:58.800 --> 01:59:01.350 align:start position:0% that was not updated everywhere, a changed<01:58:59.280> API<01:58:59.840> response<01:59:00.239> structure,<01:59:01.199> an 01:59:01.350 --> 01:59:01.360 align:start position:0% changed API response structure, an 01:59:01.360 --> 01:59:03.750 align:start position:0% changed API response structure, an incorrect<01:59:02.000> configuration<01:59:02.639> value,<01:59:03.520> a 01:59:03.750 --> 01:59:03.760 align:start position:0% incorrect configuration value, a 01:59:03.760 --> 01:59:05.510 align:start position:0% incorrect configuration value, a dependency<01:59:04.320> upgrade<01:59:04.719> that<01:59:05.040> introduced 01:59:05.510 --> 01:59:05.520 align:start position:0% dependency upgrade that introduced 01:59:05.520 --> 01:59:08.550 align:start position:0% dependency upgrade that introduced breaking<01:59:06.000> changes,<01:59:07.119> or<01:59:07.360> a<01:59:07.520> test<01:59:07.840> case<01:59:08.080> that<01:59:08.400> no 01:59:08.550 --> 01:59:08.560 align:start position:0% breaking changes, or a test case that no 01:59:08.560 --> 01:59:10.550 align:start position:0% breaking changes, or a test case that no longer<01:59:08.880> reflects<01:59:09.280> the<01:59:09.520> intended<01:59:10.000> application 01:59:10.550 --> 01:59:10.560 align:start position:0% longer reflects the intended application 01:59:10.560 --> 01:59:12.070 align:start position:0% longer reflects the intended application behavior. 01:59:12.070 --> 01:59:12.080 align:start position:0% behavior. 01:59:12.080 --> 01:59:14.310 align:start position:0% behavior. By<01:59:12.560> identifying<01:59:13.040> the<01:59:13.280> actual<01:59:13.679> source<01:59:13.920> of<01:59:14.080> the 01:59:14.310 --> 01:59:14.320 align:start position:0% By identifying the actual source of the 01:59:14.320 --> 01:59:16.950 align:start position:0% By identifying the actual source of the problem,<01:59:15.199> codecs<01:59:15.760> can<01:59:15.920> generate<01:59:16.320> fixes<01:59:16.719> that 01:59:16.950 --> 01:59:16.960 align:start position:0% problem, codecs can generate fixes that 01:59:16.960 --> 01:59:19.510 align:start position:0% problem, codecs can generate fixes that are<01:59:17.119> more<01:59:17.360> accurate,<01:59:18.239> maintainable,<01:59:19.280> and 01:59:19.510 --> 01:59:19.520 align:start position:0% are more accurate, maintainable, and 01:59:19.520 --> 01:59:21.589 align:start position:0% are more accurate, maintainable, and less<01:59:19.840> likely<01:59:20.159> to<01:59:20.320> introduce<01:59:20.880> new<01:59:21.119> defects 01:59:21.589 --> 01:59:21.599 align:start position:0% less likely to introduce new defects 01:59:21.599 --> 01:59:24.550 align:start position:0% less likely to introduce new defects elsewhere<01:59:22.000> in<01:59:22.239> the<01:59:22.400> system.<01:59:23.840> Once<01:59:24.159> the<01:59:24.320> root 01:59:24.550 --> 01:59:24.560 align:start position:0% elsewhere in the system. Once the root 01:59:24.560 --> 01:59:26.950 align:start position:0% elsewhere in the system. Once the root cause<01:59:24.880> has<01:59:25.119> been<01:59:25.440> identified,<01:59:26.400> Codeex 01:59:26.950 --> 01:59:26.960 align:start position:0% cause has been identified, Codeex 01:59:26.960 --> 01:59:29.589 align:start position:0% cause has been identified, Codeex generates<01:59:27.360> a<01:59:27.599> proposed<01:59:28.000> solution.<01:59:29.360> A 01:59:29.589 --> 01:59:29.599 align:start position:0% generates a proposed solution. A 01:59:29.599 --> 01:59:31.510 align:start position:0% generates a proposed solution. A well-designed<01:59:30.320> autofix<01:59:30.960> workflow 01:59:31.510 --> 01:59:31.520 align:start position:0% well-designed autofix workflow 01:59:31.520 --> 01:59:34.950 align:start position:0% well-designed autofix workflow emphasizes<01:59:32.239> minimal<01:59:32.719> and<01:59:33.040> focused<01:59:33.520> changes. 01:59:34.950 --> 01:59:34.960 align:start position:0% emphasizes minimal and focused changes. 01:59:34.960 --> 01:59:36.790 align:start position:0% emphasizes minimal and focused changes. The<01:59:35.199> goal<01:59:35.440> is<01:59:35.599> not<01:59:35.760> to<01:59:36.000> rewrite<01:59:36.400> large 01:59:36.790 --> 01:59:36.800 align:start position:0% The goal is not to rewrite large 01:59:36.800 --> 01:59:38.950 align:start position:0% The goal is not to rewrite large portions<01:59:37.119> of<01:59:37.280> the<01:59:37.440> application,<01:59:38.320> but<01:59:38.639> to<01:59:38.800> make 01:59:38.950 --> 01:59:38.960 align:start position:0% portions of the application, but to make 01:59:38.960 --> 01:59:41.030 align:start position:0% portions of the application, but to make the<01:59:39.199> smallest<01:59:39.679> possible<01:59:40.080> modification<01:59:40.719> that 01:59:41.030 --> 01:59:41.040 align:start position:0% the smallest possible modification that 01:59:41.040 --> 01:59:43.109 align:start position:0% the smallest possible modification that resolves<01:59:41.440> the<01:59:41.599> failure. 01:59:43.109 --> 01:59:43.119 align:start position:0% resolves the failure. 01:59:43.119 --> 01:59:45.589 align:start position:0% resolves the failure. This<01:59:43.360> approach<01:59:43.760> reduces<01:59:44.320> risk<01:59:44.880> and<01:59:45.199> makes<01:59:45.440> the 01:59:45.589 --> 01:59:45.599 align:start position:0% This approach reduces risk and makes the 01:59:45.599 --> 01:59:47.669 align:start position:0% This approach reduces risk and makes the resulting<01:59:46.080> changes<01:59:46.639> easier<01:59:47.040> for<01:59:47.280> developers 01:59:47.669 --> 01:59:47.679 align:start position:0% resulting changes easier for developers 01:59:47.679 --> 01:59:49.430 align:start position:0% resulting changes easier for developers to<01:59:47.920> review. 01:59:49.430 --> 01:59:49.440 align:start position:0% to review. 01:59:49.440 --> 01:59:51.910 align:start position:0% to review. For<01:59:49.599> example,<01:59:50.480> if<01:59:50.639> a<01:59:50.880> build<01:59:51.119> fails<01:59:51.520> because<01:59:51.760> of 01:59:51.910 --> 01:59:51.920 align:start position:0% For example, if a build fails because of 01:59:51.920 --> 01:59:54.550 align:start position:0% For example, if a build fails because of an<01:59:52.080> incorrect<01:59:52.560> import<01:59:52.960> path,<01:59:53.840> codec<01:59:54.400> should 01:59:54.550 --> 01:59:54.560 align:start position:0% an incorrect import path, codec should 01:59:54.560 --> 01:59:56.470 align:start position:0% an incorrect import path, codec should update<01:59:55.040> only<01:59:55.360> the<01:59:55.599> affected<01:59:56.080> import 01:59:56.470 --> 01:59:56.480 align:start position:0% update only the affected import 01:59:56.480 --> 01:59:58.709 align:start position:0% update only the affected import statement<01:59:57.360> rather<01:59:57.760> than<01:59:58.000> refactoring 01:59:58.709 --> 01:59:58.719 align:start position:0% statement rather than refactoring 01:59:58.719 --> 02:00:02.070 align:start position:0% statement rather than refactoring multiple<01:59:59.199> unrelated<01:59:59.840> files.<02:00:01.199> Developers<02:00:01.840> can 02:00:02.070 --> 02:00:02.080 align:start position:0% multiple unrelated files. Developers can 02:00:02.080 --> 02:00:04.149 align:start position:0% multiple unrelated files. Developers can also<02:00:02.320> provide<02:00:02.719> explicit<02:00:03.280> instructions<02:00:03.920> to 02:00:04.149 --> 02:00:04.159 align:start position:0% also provide explicit instructions to 02:00:04.159 --> 02:00:06.629 align:start position:0% also provide explicit instructions to guide<02:00:04.400> this<02:00:04.719> process,<02:00:05.679> such<02:00:05.920> as<02:00:06.080> requesting 02:00:06.629 --> 02:00:06.639 align:start position:0% guide this process, such as requesting 02:00:06.639 --> 02:00:09.350 align:start position:0% guide this process, such as requesting that<02:00:06.880> only<02:00:07.280> necessary<02:00:07.840> files<02:00:08.239> be<02:00:08.400> modified, 02:00:09.350 --> 02:00:09.360 align:start position:0% that only necessary files be modified, 02:00:09.360 --> 02:00:11.910 align:start position:0% that only necessary files be modified, preserving<02:00:10.000> existing<02:00:10.480> coding<02:00:10.880> conventions, 02:00:11.910 --> 02:00:11.920 align:start position:0% preserving existing coding conventions, 02:00:11.920 --> 02:00:14.470 align:start position:0% preserving existing coding conventions, and<02:00:12.239> updating<02:00:12.800> tests<02:00:13.280> only<02:00:13.520> when<02:00:13.840> required<02:00:14.239> to 02:00:14.470 --> 02:00:14.480 align:start position:0% and updating tests only when required to 02:00:14.480 --> 02:00:17.430 align:start position:0% and updating tests only when required to reflect<02:00:14.800> legitimate<02:00:15.360> behavior<02:00:15.840> changes. 02:00:17.430 --> 02:00:17.440 align:start position:0% reflect legitimate behavior changes. 02:00:17.440 --> 02:00:19.910 align:start position:0% reflect legitimate behavior changes. Following<02:00:17.920> fix<02:00:18.239> generation,<02:00:19.199> validation 02:00:19.910 --> 02:00:19.920 align:start position:0% Following fix generation, validation 02:00:19.920 --> 02:00:22.790 align:start position:0% Following fix generation, validation becomes<02:00:20.239> the<02:00:20.480> next<02:00:20.880> critical<02:00:21.360> step.<02:00:22.560> The 02:00:22.790 --> 02:00:22.800 align:start position:0% becomes the next critical step. The 02:00:22.800 --> 02:00:24.870 align:start position:0% becomes the next critical step. The proposed<02:00:23.280> solution<02:00:23.599> is<02:00:23.840> tested<02:00:24.320> using<02:00:24.560> the 02:00:24.870 --> 02:00:24.880 align:start position:0% proposed solution is tested using the 02:00:24.880 --> 02:00:26.629 align:start position:0% proposed solution is tested using the same<02:00:25.040> pipeline<02:00:25.599> checks<02:00:25.920> that<02:00:26.159> originally 02:00:26.629 --> 02:00:26.639 align:start position:0% same pipeline checks that originally 02:00:26.639 --> 02:00:30.070 align:start position:0% same pipeline checks that originally detected<02:00:27.119> the<02:00:27.360> problem.<02:00:28.719> Automated<02:00:29.280> builds, 02:00:30.070 --> 02:00:30.080 align:start position:0% detected the problem. Automated builds, 02:00:30.080 --> 02:00:33.189 align:start position:0% detected the problem. Automated builds, unit<02:00:30.400> tests,<02:00:31.199> integration<02:00:31.840> tests,<02:00:32.639> linting 02:00:33.189 --> 02:00:33.199 align:start position:0% unit tests, integration tests, linting 02:00:33.199 --> 02:00:35.750 align:start position:0% unit tests, integration tests, linting tools,<02:00:33.840> and<02:00:34.080> security<02:00:34.560> scans<02:00:34.960> are<02:00:35.199> executed 02:00:35.750 --> 02:00:35.760 align:start position:0% tools, and security scans are executed 02:00:35.760 --> 02:00:37.990 align:start position:0% tools, and security scans are executed again<02:00:36.320> to<02:00:36.639> confirm<02:00:36.960> that<02:00:37.119> the<02:00:37.360> issue<02:00:37.599> has<02:00:37.840> been 02:00:37.990 --> 02:00:38.000 align:start position:0% again to confirm that the issue has been 02:00:38.000 --> 02:00:40.149 align:start position:0% again to confirm that the issue has been resolved<02:00:38.480> successfully. 02:00:40.149 --> 02:00:40.159 align:start position:0% resolved successfully. 02:00:40.159 --> 02:00:42.390 align:start position:0% resolved successfully. If<02:00:40.400> the<02:00:40.639> validation<02:00:41.199> process<02:00:41.679> still<02:00:42.000> detects 02:00:42.390 --> 02:00:42.400 align:start position:0% If the validation process still detects 02:00:42.400 --> 02:00:44.470 align:start position:0% If the validation process still detects failures,<02:00:43.360> developers<02:00:43.840> can<02:00:44.080> provide 02:00:44.470 --> 02:00:44.480 align:start position:0% failures, developers can provide 02:00:44.480 --> 02:00:46.310 align:start position:0% failures, developers can provide additional<02:00:44.960> context<02:00:45.520> or<02:00:45.840> refined 02:00:46.310 --> 02:00:46.320 align:start position:0% additional context or refined 02:00:46.320 --> 02:00:49.030 align:start position:0% additional context or refined instructions<02:00:47.360> and<02:00:47.679> allow<02:00:48.000> codeex<02:00:48.560> to<02:00:48.719> perform 02:00:49.030 --> 02:00:49.040 align:start position:0% instructions and allow codeex to perform 02:00:49.040 --> 02:00:51.189 align:start position:0% instructions and allow codeex to perform another<02:00:49.440> iteration. 02:00:51.189 --> 02:00:51.199 align:start position:0% another iteration. 02:00:51.199 --> 02:00:53.030 align:start position:0% another iteration. This<02:00:51.520> feedback<02:00:52.000> loop<02:00:52.320> helps<02:00:52.639> improve 02:00:53.030 --> 02:00:53.040 align:start position:0% This feedback loop helps improve 02:00:53.040 --> 02:00:55.189 align:start position:0% This feedback loop helps improve solution<02:00:53.440> quality<02:00:54.239> while<02:00:54.560> ensuring<02:00:54.960> that 02:00:55.189 --> 02:00:55.199 align:start position:0% solution quality while ensuring that 02:00:55.199 --> 02:00:57.430 align:start position:0% solution quality while ensuring that every<02:00:55.520> proposed<02:00:56.080> change<02:00:56.320> is<02:00:56.560> verified<02:00:57.119> before 02:00:57.430 --> 02:00:57.440 align:start position:0% every proposed change is verified before 02:00:57.440 --> 02:00:59.350 align:start position:0% every proposed change is verified before moving<02:00:57.760> forward. 02:00:59.350 --> 02:00:59.360 align:start position:0% moving forward. 02:00:59.360 --> 02:01:02.149 align:start position:0% moving forward. Even<02:00:59.679> when<02:00:59.920> automated<02:01:00.480> validation<02:01:01.119> succeeds, 02:01:02.149 --> 02:01:02.159 align:start position:0% Even when automated validation succeeds, 02:01:02.159 --> 02:01:04.310 align:start position:0% Even when automated validation succeeds, human<02:01:02.560> review<02:01:03.040> remains<02:01:03.360> an<02:01:03.679> essential<02:01:04.080> part 02:01:04.310 --> 02:01:04.320 align:start position:0% human review remains an essential part 02:01:04.320 --> 02:01:06.229 align:start position:0% human review remains an essential part of<02:01:04.480> the<02:01:04.639> workflow. 02:01:06.229 --> 02:01:06.239 align:start position:0% of the workflow. 02:01:06.239 --> 02:01:08.470 align:start position:0% of the workflow. Developers<02:01:06.800> examine<02:01:07.280> the<02:01:07.520> AI<02:01:07.920> generated 02:01:08.470 --> 02:01:08.480 align:start position:0% Developers examine the AI generated 02:01:08.480 --> 02:01:10.709 align:start position:0% Developers examine the AI generated modifications<02:01:09.679> to<02:01:10.000> confirm<02:01:10.320> that<02:01:10.480> the 02:01:10.709 --> 02:01:10.719 align:start position:0% modifications to confirm that the 02:01:10.719 --> 02:01:13.350 align:start position:0% modifications to confirm that the solution<02:01:11.119> is<02:01:11.360> technically<02:01:11.920> correct,<02:01:12.880> aligns 02:01:13.350 --> 02:01:13.360 align:start position:0% solution is technically correct, aligns 02:01:13.360 --> 02:01:15.589 align:start position:0% solution is technically correct, aligns with<02:01:13.599> business<02:01:14.000> requirements,<02:01:15.119> follows 02:01:15.589 --> 02:01:15.599 align:start position:0% with business requirements, follows 02:01:15.599 --> 02:01:17.910 align:start position:0% with business requirements, follows architectural<02:01:16.320> standards,<02:01:17.199> and<02:01:17.440> does<02:01:17.679> not 02:01:17.910 --> 02:01:17.920 align:start position:0% architectural standards, and does not 02:01:17.920 --> 02:01:20.950 align:start position:0% architectural standards, and does not introduce<02:01:18.480> unintended<02:01:19.199> side<02:01:19.520> effects. 02:01:20.950 --> 02:01:20.960 align:start position:0% introduce unintended side effects. 02:01:20.960 --> 02:01:22.950 align:start position:0% introduce unintended side effects. This<02:01:21.280> review<02:01:21.679> process<02:01:22.159> also<02:01:22.480> provides 02:01:22.950 --> 02:01:22.960 align:start position:0% This review process also provides 02:01:22.960 --> 02:01:25.270 align:start position:0% This review process also provides accountability<02:01:23.679> and<02:01:23.920> governance<02:01:24.880> which<02:01:25.119> are 02:01:25.270 --> 02:01:25.280 align:start position:0% accountability and governance which are 02:01:25.280 --> 02:01:27.030 align:start position:0% accountability and governance which are especially<02:01:25.840> important<02:01:26.239> in<02:01:26.480> enterprise 02:01:27.030 --> 02:01:27.040 align:start position:0% especially important in enterprise 02:01:27.040 --> 02:01:29.510 align:start position:0% especially important in enterprise environments<02:01:27.599> where<02:01:27.920> compliance,<02:01:28.880> security 02:01:29.510 --> 02:01:29.520 align:start position:0% environments where compliance, security 02:01:29.520 --> 02:01:31.589 align:start position:0% environments where compliance, security and<02:01:29.760> maintainability<02:01:30.560> requirements<02:01:31.199> must<02:01:31.440> be 02:01:31.589 --> 02:01:31.599 align:start position:0% and maintainability requirements must be 02:01:31.599 --> 02:01:33.669 align:start position:0% and maintainability requirements must be carefully<02:01:32.080> enforced. 02:01:33.669 --> 02:01:33.679 align:start position:0% carefully enforced. 02:01:33.679 --> 02:01:35.750 align:start position:0% carefully enforced. Once<02:01:34.000> the<02:01:34.239> fix<02:01:34.480> has<02:01:34.639> been<02:01:34.800> approved,<02:01:35.520> the 02:01:35.750 --> 02:01:35.760 align:start position:0% Once the fix has been approved, the 02:01:35.760 --> 02:01:37.510 align:start position:0% Once the fix has been approved, the changes<02:01:36.159> can<02:01:36.320> be<02:01:36.480> merged<02:01:36.880> into<02:01:37.119> the<02:01:37.280> main 02:01:37.510 --> 02:01:37.520 align:start position:0% changes can be merged into the main 02:01:37.520 --> 02:01:39.510 align:start position:0% changes can be merged into the main branch<02:01:38.159> and<02:01:38.480> included<02:01:38.960> in<02:01:39.199> future 02:01:39.510 --> 02:01:39.520 align:start position:0% branch and included in future 02:01:39.520 --> 02:01:41.109 align:start position:0% branch and included in future deployments. 02:01:41.109 --> 02:01:41.119 align:start position:0% deployments. 02:01:41.119 --> 02:01:43.750 align:start position:0% deployments. Over<02:01:41.520> time,<02:01:42.159> teams<02:01:42.560> can<02:01:42.719> analyze<02:01:43.199> recurring 02:01:43.750 --> 02:01:43.760 align:start position:0% Over time, teams can analyze recurring 02:01:43.760 --> 02:01:45.750 align:start position:0% Over time, teams can analyze recurring issues<02:01:44.400> and<02:01:44.639> improve<02:01:45.040> their<02:01:45.360> development 02:01:45.750 --> 02:01:45.760 align:start position:0% issues and improve their development 02:01:45.760 --> 02:01:48.070 align:start position:0% issues and improve their development processes<02:01:46.400> accordingly. 02:01:48.070 --> 02:01:48.080 align:start position:0% processes accordingly. 02:01:48.080 --> 02:01:50.149 align:start position:0% processes accordingly. Repository<02:01:48.639> instructions,<02:01:49.760> testing 02:01:50.149 --> 02:01:50.159 align:start position:0% Repository instructions, testing 02:01:50.159 --> 02:01:53.669 align:start position:0% Repository instructions, testing strategies,<02:01:51.199> agents.mmd<02:01:52.400> guidelines,<02:01:53.360> and 02:01:53.669 --> 02:01:53.679 align:start position:0% strategies, agents.mmd guidelines, and 02:01:53.679 --> 02:01:57.270 align:start position:0% strategies, agents.mmd guidelines, and CI/CD<02:01:55.040> configurations<02:01:56.239> can<02:01:56.480> be<02:01:56.639> updated<02:01:57.040> to 02:01:57.270 --> 02:01:57.280 align:start position:0% CI/CD configurations can be updated to 02:01:57.280 --> 02:01:59.430 align:start position:0% CI/CD configurations can be updated to help<02:01:57.520> codeex<02:01:58.080> handle<02:01:58.400> similar<02:01:58.800> situations 02:01:59.430 --> 02:01:59.440 align:start position:0% help codeex handle similar situations 02:01:59.440 --> 02:02:01.830 align:start position:0% help codeex handle similar situations more<02:01:59.679> effectively<02:02:00.159> in<02:02:00.320> the<02:02:00.480> future. 02:02:01.830 --> 02:02:01.840 align:start position:0% more effectively in the future. 02:02:01.840 --> 02:02:04.709 align:start position:0% more effectively in the future. As<02:02:02.080> a<02:02:02.320> result,<02:02:03.040> autofix<02:02:03.760> workflows<02:02:04.320> not<02:02:04.560> only 02:02:04.709 --> 02:02:04.719 align:start position:0% As a result, autofix workflows not only 02:02:04.719 --> 02:02:06.950 align:start position:0% As a result, autofix workflows not only resolve<02:02:05.119> immediate<02:02:05.599> problems,<02:02:06.400> but<02:02:06.639> also 02:02:06.950 --> 02:02:06.960 align:start position:0% resolve immediate problems, but also 02:02:06.960 --> 02:02:08.790 align:start position:0% resolve immediate problems, but also contribute<02:02:07.440> to<02:02:07.679> continuous<02:02:08.239> improvement 02:02:08.790 --> 02:02:08.800 align:start position:0% contribute to continuous improvement 02:02:08.800 --> 02:02:10.179 align:start position:0% contribute to continuous improvement across<02:02:09.119> the<02:02:09.280> software<02:02:09.760> development 02:02:10.179 --> 02:02:10.189 align:start position:0% across the software development 02:02:10.189 --> 02:02:12.070 align:start position:0% across the software development [clears throat]<02:02:10.239> life<02:02:10.480> cycle,<02:02:11.520> enabling 02:02:12.070 --> 02:02:12.080 align:start position:0% [clears throat] life cycle, enabling 02:02:12.080 --> 02:02:14.310 align:start position:0% [clears throat] life cycle, enabling teams<02:02:12.480> to<02:02:12.639> deliver<02:02:13.040> higher<02:02:13.440> quality<02:02:13.840> software 02:02:14.310 --> 02:02:14.320 align:start position:0% teams to deliver higher quality software 02:02:14.320 --> 02:02:16.950 align:start position:0% teams to deliver higher quality software faster<02:02:15.280> while<02:02:15.599> reducing<02:02:16.000> the<02:02:16.239> manual<02:02:16.560> effort 02:02:16.950 --> 02:02:16.960 align:start position:0% faster while reducing the manual effort 02:02:16.960 --> 02:02:19.750 align:start position:0% faster while reducing the manual effort required<02:02:17.360> to<02:02:17.599> maintain<02:02:18.080> complex<02:02:18.639> systems. 02:02:19.750 --> 02:02:19.760 align:start position:0% required to maintain complex systems. 02:02:19.760 --> 02:02:21.990 align:start position:0% required to maintain complex systems. Now<02:02:20.159> the<02:02:20.400> discussion<02:02:20.800> we<02:02:21.040> have<02:02:21.199> is<02:02:21.520> related<02:02:21.840> to 02:02:21.990 --> 02:02:22.000 align:start position:0% Now the discussion we have is related to 02:02:22.000 --> 02:02:25.189 align:start position:0% Now the discussion we have is related to configuring<02:02:22.719> automated<02:02:23.280> bug<02:02:23.599> resolution.<02:02:24.960> We 02:02:25.189 --> 02:02:25.199 align:start position:0% configuring automated bug resolution. We 02:02:25.199 --> 02:02:27.830 align:start position:0% configuring automated bug resolution. We can<02:02:25.360> say<02:02:25.520> this<02:02:25.760> on<02:02:26.000> a<02:02:26.159> large<02:02:26.480> scale<02:02:27.440> in<02:02:27.679> our 02:02:27.830 --> 02:02:27.840 align:start position:0% can say this on a large scale in our 02:02:27.840 --> 02:02:30.390 align:start position:0% can say this on a large scale in our codeex<02:02:28.639> along<02:02:28.960> with<02:02:29.119> other<02:02:29.440> things.<02:02:30.080> a 02:02:30.390 --> 02:02:30.400 align:start position:0% codeex along with other things. a 02:02:30.400 --> 02:02:32.950 align:start position:0% codeex along with other things. a discussion<02:02:30.800> was<02:02:31.040> going<02:02:31.199> on.<02:02:32.239> This<02:02:32.480> is<02:02:32.639> most 02:02:32.950 --> 02:02:32.960 align:start position:0% discussion was going on. This is most 02:02:32.960 --> 02:02:35.910 align:start position:0% discussion was going on. This is most valuable<02:02:33.280> for<02:02:33.520> enterprise<02:02:34.080> use<02:02:34.320> cases<02:02:35.599> for 02:02:35.910 --> 02:02:35.920 align:start position:0% valuable for enterprise use cases for 02:02:35.920 --> 02:02:38.709 align:start position:0% valuable for enterprise use cases for open<02:02:36.239> AI<02:02:36.639> codecs.<02:02:37.599> Instead<02:02:37.920> of<02:02:38.159> developers 02:02:38.709 --> 02:02:38.719 align:start position:0% open AI codecs. Instead of developers 02:02:38.719 --> 02:02:41.350 align:start position:0% open AI codecs. Instead of developers manually<02:02:39.199> investigating<02:02:40.000> every<02:02:40.320> test<02:02:40.639> field, 02:02:41.350 --> 02:02:41.360 align:start position:0% manually investigating every test field, 02:02:41.360 --> 02:02:43.750 align:start position:0% manually investigating every test field, linting<02:02:42.000> error,<02:02:42.480> securing<02:02:42.960> warnings,<02:02:43.440> or 02:02:43.750 --> 02:02:43.760 align:start position:0% linting error, securing warnings, or 02:02:43.760 --> 02:02:46.470 align:start position:0% linting error, securing warnings, or production<02:02:44.159> defects,<02:02:45.360> codeex<02:02:45.920> can<02:02:46.080> analyze 02:02:46.470 --> 02:02:46.480 align:start position:0% production defects, codeex can analyze 02:02:46.480 --> 02:02:49.910 align:start position:0% production defects, codeex can analyze the<02:02:46.719> issue,<02:02:47.760> identify<02:02:48.159> the<02:02:48.400> affected<02:02:48.880> files, 02:02:49.910 --> 02:02:49.920 align:start position:0% the issue, identify the affected files, 02:02:49.920 --> 02:02:52.550 align:start position:0% the issue, identify the affected files, generate<02:02:50.400> a<02:02:50.560> proposed<02:02:51.040> fix,<02:02:51.840> and<02:02:52.159> create<02:02:52.400> a 02:02:52.550 --> 02:02:52.560 align:start position:0% generate a proposed fix, and create a 02:02:52.560 --> 02:02:55.430 align:start position:0% generate a proposed fix, and create a pull<02:02:52.880> request<02:02:53.199> for<02:02:53.440> human<02:02:53.760> review.<02:02:55.119> This 02:02:55.430 --> 02:02:55.440 align:start position:0% pull request for human review. This 02:02:55.440 --> 02:02:57.589 align:start position:0% pull request for human review. This significantly<02:02:56.239> reduces<02:02:56.639> the<02:02:56.880> time<02:02:57.119> spent<02:02:57.440> on 02:02:57.589 --> 02:02:57.599 align:start position:0% significantly reduces the time spent on 02:02:57.599 --> 02:02:59.750 align:start position:0% significantly reduces the time spent on repetitive<02:02:58.159> maintenance<02:02:58.719> tasks<02:02:59.440> while 02:02:59.750 --> 02:02:59.760 align:start position:0% repetitive maintenance tasks while 02:02:59.760 --> 02:03:01.510 align:start position:0% repetitive maintenance tasks while allowing<02:03:00.239> focus<02:03:00.560> for<02:03:00.800> engineers<02:03:01.280> to 02:03:01.510 --> 02:03:01.520 align:start position:0% allowing focus for engineers to 02:03:01.520 --> 02:03:03.589 align:start position:0% allowing focus for engineers to concentrate<02:03:02.000> on<02:03:02.239> high-level<02:03:02.880> architectural 02:03:03.589 --> 02:03:03.599 align:start position:0% concentrate on high-level architectural 02:03:03.599 --> 02:03:05.510 align:start position:0% concentrate on high-level architectural business<02:03:04.000> problems. 02:03:05.510 --> 02:03:05.520 align:start position:0% business problems. 02:03:05.520 --> 02:03:08.149 align:start position:0% business problems. In<02:03:05.760> modern<02:03:06.159> software<02:03:06.560> teams,<02:03:07.360> bugs<02:03:07.679> are<02:03:07.840> often 02:03:08.149 --> 02:03:08.159 align:start position:0% In modern software teams, bugs are often 02:03:08.159 --> 02:03:11.510 align:start position:0% In modern software teams, bugs are often discovered<02:03:08.639> through<02:03:08.960> CI/CD<02:03:10.320> pipelines, 02:03:11.510 --> 02:03:11.520 align:start position:0% discovered through CI/CD pipelines, 02:03:11.520 --> 02:03:14.470 align:start position:0% discovered through CI/CD pipelines, monitoring<02:03:12.080> systems,<02:03:13.040> issue<02:03:13.440> trackers,<02:03:14.159> and 02:03:14.470 --> 02:03:14.480 align:start position:0% monitoring systems, issue trackers, and 02:03:14.480 --> 02:03:16.470 align:start position:0% monitoring systems, issue trackers, and security<02:03:14.960> scanners. 02:03:16.470 --> 02:03:16.480 align:start position:0% security scanners. 02:03:16.480 --> 02:03:18.070 align:start position:0% security scanners. Codeex<02:03:17.040> can<02:03:17.199> integrate<02:03:17.520> into<02:03:17.760> these 02:03:18.070 --> 02:03:18.080 align:start position:0% Codeex can integrate into these 02:03:18.080 --> 02:03:20.470 align:start position:0% Codeex can integrate into these workflows<02:03:18.639> so<02:03:18.800> that<02:03:19.040> when<02:03:19.199> an<02:03:19.360> issue<02:03:19.679> occurs, 02:03:20.470 --> 02:03:20.480 align:start position:0% workflows so that when an issue occurs, 02:03:20.480 --> 02:03:22.470 align:start position:0% workflows so that when an issue occurs, the<02:03:20.719> AI<02:03:21.280> automatically<02:03:21.920> receives<02:03:22.320> the 02:03:22.470 --> 02:03:22.480 align:start position:0% the AI automatically receives the 02:03:22.480 --> 02:03:25.589 align:start position:0% the AI automatically receives the failure<02:03:22.800> logs,<02:03:23.520> repository<02:03:24.159> context,<02:03:25.119> coding 02:03:25.589 --> 02:03:25.599 align:start position:0% failure logs, repository context, coding 02:03:25.599 --> 02:03:29.270 align:start position:0% failure logs, repository context, coding standards,<02:03:26.480> and<02:03:26.800> our<02:03:27.040> project<02:03:27.440> instructions. 02:03:29.270 --> 02:03:29.280 align:start position:0% standards, and our project instructions. 02:03:29.280 --> 02:03:31.669 align:start position:0% standards, and our project instructions. All<02:03:29.360> right.<02:03:30.239> The<02:03:30.480> critical<02:03:30.880> aspect<02:03:31.280> we<02:03:31.520> have 02:03:31.669 --> 02:03:31.679 align:start position:0% All right. The critical aspect we have 02:03:31.679 --> 02:03:34.550 align:start position:0% All right. The critical aspect we have for<02:03:31.920> automated<02:03:32.480> bug<02:03:32.800> resolution<02:03:33.599> is<02:03:33.920> defining 02:03:34.550 --> 02:03:34.560 align:start position:0% for automated bug resolution is defining 02:03:34.560 --> 02:03:36.550 align:start position:0% for automated bug resolution is defining clear<02:03:34.880> boundaries. 02:03:36.550 --> 02:03:36.560 align:start position:0% clear boundaries. 02:03:36.560 --> 02:03:38.550 align:start position:0% clear boundaries. Enterprise<02:03:37.119> organizations<02:03:37.920> should<02:03:38.239> never 02:03:38.550 --> 02:03:38.560 align:start position:0% Enterprise organizations should never 02:03:38.560 --> 02:03:41.109 align:start position:0% Enterprise organizations should never allow<02:03:38.960> AI<02:03:39.360> to<02:03:39.599> directly<02:03:40.080> deploy<02:03:40.480> files<02:03:40.800> into 02:03:41.109 --> 02:03:41.119 align:start position:0% allow AI to directly deploy files into 02:03:41.119 --> 02:03:44.070 align:start position:0% allow AI to directly deploy files into production.<02:03:42.400> Instead,<02:03:43.360> codec<02:03:43.840> should 02:03:44.070 --> 02:03:44.080 align:start position:0% production. Instead, codec should 02:03:44.080 --> 02:03:47.109 align:start position:0% production. Instead, codec should generate<02:03:44.480> code<02:03:44.800> changes,<02:03:45.760> execute<02:03:46.320> tests, 02:03:47.109 --> 02:03:47.119 align:start position:0% generate code changes, execute tests, 02:03:47.119 --> 02:03:49.109 align:start position:0% generate code changes, execute tests, and<02:03:47.360> create<02:03:47.679> pull<02:03:48.000> requests<02:03:48.400> that<02:03:48.639> require 02:03:49.109 --> 02:03:49.119 align:start position:0% and create pull requests that require 02:03:49.119 --> 02:03:51.750 align:start position:0% and create pull requests that require developer<02:03:49.599> approval.<02:03:50.960> This<02:03:51.199> maintains 02:03:51.750 --> 02:03:51.760 align:start position:0% developer approval. This maintains 02:03:51.760 --> 02:03:53.830 align:start position:0% developer approval. This maintains governance<02:03:52.159> and<02:03:52.480> accountability<02:03:53.520> while 02:03:53.830 --> 02:03:53.840 align:start position:0% governance and accountability while 02:03:53.840 --> 02:03:56.550 align:start position:0% governance and accountability while still<02:03:54.159> benefiting<02:03:54.639> from<02:03:54.880> automation. 02:03:56.550 --> 02:03:56.560 align:start position:0% still benefiting from automation. 02:03:56.560 --> 02:03:58.390 align:start position:0% still benefiting from automation. Human<02:03:56.960> reviewers<02:03:57.520> can<02:03:57.679> remain<02:03:58.000> fully 02:03:58.390 --> 02:03:58.400 align:start position:0% Human reviewers can remain fully 02:03:58.400 --> 02:04:00.310 align:start position:0% Human reviewers can remain fully responsible<02:03:58.960> for<02:03:59.199> validating<02:03:59.760> the<02:04:00.000> basic 02:04:00.310 --> 02:04:00.320 align:start position:0% responsible for validating the basic 02:04:00.320 --> 02:04:01.990 align:start position:0% responsible for validating the basic logic. 02:04:01.990 --> 02:04:02.000 align:start position:0% logic. 02:04:02.000 --> 02:04:04.390 align:start position:0% logic. Now,<02:04:02.639> let<02:04:02.880> me<02:04:03.040> tell<02:04:03.199> you<02:04:03.360> a<02:04:03.679> very<02:04:04.000> important 02:04:04.390 --> 02:04:04.400 align:start position:0% Now, let me tell you a very important 02:04:04.400 --> 02:04:07.669 align:start position:0% Now, let me tell you a very important thing.<02:04:05.440> Our<02:04:05.679> agents.mmd<02:04:06.880> file<02:04:07.199> plays<02:04:07.440> a 02:04:07.669 --> 02:04:07.679 align:start position:0% thing. Our agents.mmd file plays a 02:04:07.679 --> 02:04:10.229 align:start position:0% thing. Our agents.mmd file plays a crucial<02:04:07.920> role<02:04:08.159> in<02:04:08.400> the<02:04:08.560> process.<02:04:09.920> What 02:04:10.229 --> 02:04:10.239 align:start position:0% crucial role in the process. What 02:04:10.239 --> 02:04:11.830 align:start position:0% crucial role in the process. What happens<02:04:10.480> is<02:04:10.719> they<02:04:10.880> provide<02:04:11.199> our<02:04:11.440> project 02:04:11.830 --> 02:04:11.840 align:start position:0% happens is they provide our project 02:04:11.840 --> 02:04:13.910 align:start position:0% happens is they provide our project specifications<02:04:12.719> and<02:04:13.040> instructions<02:04:13.599> that 02:04:13.910 --> 02:04:13.920 align:start position:0% specifications and instructions that 02:04:13.920 --> 02:04:15.990 align:start position:0% specifications and instructions that guide<02:04:14.239> codeex's<02:04:14.960> decision-making<02:04:15.679> during 02:04:15.990 --> 02:04:16.000 align:start position:0% guide codeex's decision-making during 02:04:16.000 --> 02:04:17.830 align:start position:0% guide codeex's decision-making during bug<02:04:16.320> resolution. 02:04:17.830 --> 02:04:17.840 align:start position:0% bug resolution. 02:04:17.840 --> 02:04:19.669 align:start position:0% bug resolution. These<02:04:18.159> instructions<02:04:18.719> define<02:04:19.119> the<02:04:19.280> coding 02:04:19.669 --> 02:04:19.679 align:start position:0% These instructions define the coding 02:04:19.679 --> 02:04:22.390 align:start position:0% These instructions define the coding conventions,<02:04:20.800> testing<02:04:21.280> requirements, 02:04:22.390 --> 02:04:22.400 align:start position:0% conventions, testing requirements, 02:04:22.400 --> 02:04:24.629 align:start position:0% conventions, testing requirements, security<02:04:22.960> constraints,<02:04:24.000> dependency 02:04:24.629 --> 02:04:24.639 align:start position:0% security constraints, dependency 02:04:24.639 --> 02:04:26.950 align:start position:0% security constraints, dependency policies,<02:04:25.679> and<02:04:26.000> our<02:04:26.239> architectural 02:04:26.950 --> 02:04:26.960 align:start position:0% policies, and our architectural 02:04:26.960 --> 02:04:29.430 align:start position:0% policies, and our architectural patterns.<02:04:28.320> The<02:04:28.560> more<02:04:28.800> structured<02:04:29.199> the 02:04:29.430 --> 02:04:29.440 align:start position:0% patterns. The more structured the 02:04:29.440 --> 02:04:32.390 align:start position:0% patterns. The more structured the agents.mmd<02:04:30.639> file<02:04:30.880> is,<02:04:31.520> the<02:04:31.760> more<02:04:32.000> accurate 02:04:32.390 --> 02:04:32.400 align:start position:0% agents.mmd file is, the more accurate 02:04:32.400 --> 02:04:34.950 align:start position:0% agents.mmd file is, the more accurate and<02:04:32.639> reliable<02:04:33.040> the<02:04:33.280> fixes<02:04:33.679> become. 02:04:34.950 --> 02:04:34.960 align:start position:0% and reliable the fixes become. 02:04:34.960 --> 02:04:36.870 align:start position:0% and reliable the fixes become. Organizations<02:04:35.760> must<02:04:36.080> look<02:04:36.239> at<02:04:36.400> another<02:04:36.639> thing 02:04:36.870 --> 02:04:36.880 align:start position:0% Organizations must look at another thing 02:04:36.880 --> 02:04:39.350 align:start position:0% Organizations must look at another thing alongside<02:04:37.520> agents.mmd 02:04:39.350 --> 02:04:39.360 align:start position:0% alongside agents.mmd 02:04:39.360 --> 02:04:42.470 align:start position:0% alongside agents.mmd confidence<02:04:39.920> thresholds.<02:04:41.360> For<02:04:41.440> example, 02:04:42.470 --> 02:04:42.480 align:start position:0% confidence thresholds. For example, 02:04:42.480 --> 02:04:44.790 align:start position:0% confidence thresholds. For example, codecs<02:04:43.040> may<02:04:43.280> automatically<02:04:43.920> fix<02:04:44.239> linting 02:04:44.790 --> 02:04:44.800 align:start position:0% codecs may automatically fix linting 02:04:44.800 --> 02:04:46.950 align:start position:0% codecs may automatically fix linting errors<02:04:44.960> and<02:04:45.199> formatting<02:04:45.679> issues<02:04:46.639> while 02:04:46.950 --> 02:04:46.960 align:start position:0% errors and formatting issues while 02:04:46.960 --> 02:04:49.109 align:start position:0% errors and formatting issues while security<02:04:47.440> vulnerabilities<02:04:48.239> or<02:04:48.560> database 02:04:49.109 --> 02:04:49.119 align:start position:0% security vulnerabilities or database 02:04:49.119 --> 02:04:51.910 align:start position:0% security vulnerabilities or database related<02:04:49.440> bugs<02:04:50.239> require<02:04:50.639> a<02:04:50.880> mandatory<02:04:51.440> senior 02:04:51.910 --> 02:04:51.920 align:start position:0% related bugs require a mandatory senior 02:04:51.920 --> 02:04:54.870 align:start position:0% related bugs require a mandatory senior engineer<02:04:52.400> review.<02:04:53.679> An<02:04:53.920> example<02:04:54.239> of<02:04:54.480> this<02:04:54.719> is 02:04:54.870 --> 02:04:54.880 align:start position:0% engineer review. An example of this is 02:04:54.880 --> 02:04:57.270 align:start position:0% engineer review. An example of this is that<02:04:55.199> first<02:04:55.440> of<02:04:55.599> all<02:04:56.080> we<02:04:56.400> have<02:04:56.480> to<02:04:56.719> do<02:04:56.880> this 02:04:57.270 --> 02:04:57.280 align:start position:0% that first of all we have to do this 02:04:57.280 --> 02:04:59.910 align:start position:0% that first of all we have to do this step<02:04:57.599> by<02:04:57.840> step.<02:04:58.800> The<02:04:59.119> first<02:04:59.360> part<02:04:59.520> of<02:04:59.760> our 02:04:59.910 --> 02:04:59.920 align:start position:0% step by step. The first part of our 02:04:59.920 --> 02:05:02.229 align:start position:0% step by step. The first part of our process<02:05:00.320> is<02:05:00.560> to<02:05:00.960> identify<02:05:01.360> our<02:05:01.599> bug<02:05:01.840> trigger 02:05:02.229 --> 02:05:02.239 align:start position:0% process is to identify our bug trigger 02:05:02.239 --> 02:05:04.470 align:start position:0% process is to identify our bug trigger resources<02:05:03.119> and<02:05:03.440> define<02:05:03.840> where<02:05:04.000> the<02:05:04.239> bug 02:05:04.470 --> 02:05:04.480 align:start position:0% resources and define where the bug 02:05:04.480 --> 02:05:06.390 align:start position:0% resources and define where the bug reports<02:05:04.880> originate. 02:05:06.390 --> 02:05:06.400 align:start position:0% reports originate. 02:05:06.400 --> 02:05:08.629 align:start position:0% reports originate. Usually<02:05:06.960> what<02:05:07.280> happens<02:05:07.520> is<02:05:07.760> we<02:05:08.080> see<02:05:08.239> this<02:05:08.400> in 02:05:08.629 --> 02:05:08.639 align:start position:0% Usually what happens is we see this in 02:05:08.639 --> 02:05:12.550 align:start position:0% Usually what happens is we see this in our<02:05:08.880> CI/CD<02:05:10.239> builds<02:05:11.119> or<02:05:11.679> we<02:05:11.920> can<02:05:12.000> see<02:05:12.159> this<02:05:12.400> in 02:05:12.550 --> 02:05:12.560 align:start position:0% our CI/CD builds or we can see this in 02:05:12.560 --> 02:05:15.830 align:start position:0% our CI/CD builds or we can see this in our<02:05:12.719> unit<02:05:13.040> tests<02:05:13.440> we<02:05:13.679> perform<02:05:14.639> or<02:05:15.280> we<02:05:15.520> can<02:05:15.679> see 02:05:15.830 --> 02:05:15.840 align:start position:0% our unit tests we perform or we can see 02:05:15.840 --> 02:05:18.629 align:start position:0% our unit tests we perform or we can see this<02:05:16.000> in<02:05:16.239> our<02:05:16.400> integration<02:05:16.960> test<02:05:17.199> failures. 02:05:18.629 --> 02:05:18.639 align:start position:0% this in our integration test failures. 02:05:18.639 --> 02:05:21.430 align:start position:0% this in our integration test failures. Sometimes<02:05:19.280> issues<02:05:19.679> can<02:05:19.920> arise<02:05:20.159> in<02:05:20.320> GitHub<02:05:21.199> or 02:05:21.430 --> 02:05:21.440 align:start position:0% Sometimes issues can arise in GitHub or 02:05:21.440 --> 02:05:24.229 align:start position:0% Sometimes issues can arise in GitHub or our<02:05:21.679> security<02:05:22.159> scans<02:05:22.560> can<02:05:22.719> cause<02:05:22.960> an<02:05:23.119> issue. 02:05:24.229 --> 02:05:24.239 align:start position:0% our security scans can cause an issue. 02:05:24.239 --> 02:05:26.470 align:start position:0% our security scans can cause an issue. All<02:05:24.320> right.<02:05:25.199> After<02:05:25.520> that,<02:05:25.840> we<02:05:26.080> have<02:05:26.159> to 02:05:26.470 --> 02:05:26.480 align:start position:0% All right. After that, we have to 02:05:26.480 --> 02:05:28.870 align:start position:0% All right. After that, we have to identify<02:05:26.800> the<02:05:27.040> AI<02:05:27.440> and<02:05:27.679> look<02:05:27.840> at<02:05:27.920> the<02:05:28.080> AI's<02:05:28.560> fix 02:05:28.870 --> 02:05:28.880 align:start position:0% identify the AI and look at the AI's fix 02:05:28.880 --> 02:05:32.070 align:start position:0% identify the AI and look at the AI's fix permissions.<02:05:30.159> If<02:05:30.719> let's<02:05:30.960> suppose<02:05:31.679> there's<02:05:31.920> a 02:05:32.070 --> 02:05:32.080 align:start position:0% permissions. If let's suppose there's a 02:05:32.080 --> 02:05:34.870 align:start position:0% permissions. If let's suppose there's a formatting<02:05:32.560> issue,<02:05:33.280> a<02:05:33.440> linting<02:05:33.840> issue<02:05:34.480> or<02:05:34.719> a 02:05:34.870 --> 02:05:34.880 align:start position:0% formatting issue, a linting issue or a 02:05:34.880 --> 02:05:37.189 align:start position:0% formatting issue, a linting issue or a unit<02:05:35.199> test<02:05:35.520> failure,<02:05:36.320> we'll<02:05:36.639> automatically 02:05:37.189 --> 02:05:37.199 align:start position:0% unit test failure, we'll automatically 02:05:37.199 --> 02:05:39.270 align:start position:0% unit test failure, we'll automatically look<02:05:37.360> at<02:05:37.599> all<02:05:37.679> of<02:05:37.840> them<02:05:38.320> and<02:05:38.639> a<02:05:38.880> detailed 02:05:39.270 --> 02:05:39.280 align:start position:0% look at all of them and a detailed 02:05:39.280 --> 02:05:40.870 align:start position:0% look at all of them and a detailed discussion<02:05:39.760> will<02:05:40.000> take<02:05:40.159> place<02:05:40.400> regarding 02:05:40.870 --> 02:05:40.880 align:start position:0% discussion will take place regarding 02:05:40.880 --> 02:05:43.510 align:start position:0% discussion will take place regarding production<02:05:41.280> incidents<02:05:41.760> and<02:05:42.000> everything. 02:05:43.510 --> 02:05:43.520 align:start position:0% production incidents and everything. 02:05:43.520 --> 02:05:46.229 align:start position:0% production incidents and everything. Agents.md<02:05:44.719> is<02:05:44.880> our<02:05:45.119> most<02:05:45.360> important<02:05:45.840> file 02:05:46.229 --> 02:05:46.239 align:start position:0% Agents.md is our most important file 02:05:46.239 --> 02:05:48.790 align:start position:0% Agents.md is our most important file which<02:05:46.480> I<02:05:46.719> mentioned<02:05:47.040> here.<02:05:48.080> What<02:05:48.320> happens<02:05:48.560> in 02:05:48.790 --> 02:05:48.800 align:start position:0% which I mentioned here. What happens in 02:05:48.800 --> 02:05:51.510 align:start position:0% which I mentioned here. What happens in agents.md<02:05:50.080> is<02:05:50.400> we<02:05:50.560> can<02:05:50.719> see<02:05:50.800> the<02:05:51.040> automated 02:05:51.510 --> 02:05:51.520 align:start position:0% agents.md is we can see the automated 02:05:51.520 --> 02:05:54.390 align:start position:0% agents.md is we can see the automated bug<02:05:51.840> resolution<02:05:52.400> rules.<02:05:53.440> Whenever<02:05:53.840> we<02:05:54.000> fix<02:05:54.159> a 02:05:54.390 --> 02:05:54.400 align:start position:0% bug resolution rules. Whenever we fix a 02:05:54.400 --> 02:05:56.229 align:start position:0% bug resolution rules. Whenever we fix a bug,<02:05:54.880> we<02:05:55.119> should<02:05:55.280> minimize<02:05:55.760> the<02:05:55.920> code 02:05:56.229 --> 02:05:56.239 align:start position:0% bug, we should minimize the code 02:05:56.239 --> 02:05:58.470 align:start position:0% bug, we should minimize the code changes.<02:05:57.119> We<02:05:57.360> should<02:05:57.520> never<02:05:57.840> modify<02:05:58.239> the 02:05:58.470 --> 02:05:58.480 align:start position:0% changes. We should never modify the 02:05:58.480 --> 02:06:00.870 align:start position:0% changes. We should never modify the database<02:05:58.960> schemas.<02:05:59.840> We<02:06:00.080> should<02:06:00.239> preserve<02:06:00.639> the 02:06:00.870 --> 02:06:00.880 align:start position:0% database schemas. We should preserve the 02:06:00.880 --> 02:06:03.350 align:start position:0% database schemas. We should preserve the API<02:06:01.520> contracts,<02:06:02.400> add<02:06:02.639> our<02:06:02.880> tests<02:06:03.119> for 02:06:03.350 --> 02:06:03.360 align:start position:0% API contracts, add our tests for 02:06:03.360 --> 02:06:05.589 align:start position:0% API contracts, add our tests for everyone,<02:06:04.159> and<02:06:04.480> run<02:06:04.719> all<02:06:04.880> of<02:06:05.040> the<02:06:05.199> affected 02:06:05.589 --> 02:06:05.599 align:start position:0% everyone, and run all of the affected 02:06:05.599 --> 02:06:08.709 align:start position:0% everyone, and run all of the affected test<02:06:05.920> suites.<02:06:07.280> We<02:06:07.599> must<02:06:07.840> explain<02:06:08.159> the<02:06:08.400> root 02:06:08.709 --> 02:06:08.719 align:start position:0% test suites. We must explain the root 02:06:08.719 --> 02:06:10.790 align:start position:0% test suites. We must explain the root cause<02:06:09.040> and<02:06:09.360> also<02:06:09.679> create<02:06:09.920> a<02:06:10.080> pull<02:06:10.400> request 02:06:10.790 --> 02:06:10.800 align:start position:0% cause and also create a pull request 02:06:10.800 --> 02:06:13.109 align:start position:0% cause and also create a pull request summary.<02:06:11.840> You<02:06:12.080> can<02:06:12.239> see<02:06:12.400> all<02:06:12.639> of<02:06:12.719> this<02:06:12.880> in 02:06:13.109 --> 02:06:13.119 align:start position:0% summary. You can see all of this in 02:06:13.119 --> 02:06:14.629 align:start position:0% summary. You can see all of this in agents.md 02:06:14.629 --> 02:06:14.639 align:start position:0% agents.md 02:06:14.639 --> 02:06:16.870 align:start position:0% agents.md where<02:06:14.880> we<02:06:15.040> address<02:06:15.360> the<02:06:15.520> bugs<02:06:16.159> and<02:06:16.480> multiple 02:06:16.870 --> 02:06:16.880 align:start position:0% where we address the bugs and multiple 02:06:16.880 --> 02:06:20.229 align:start position:0% where we address the bugs and multiple things<02:06:17.119> are<02:06:17.360> included.<02:06:18.800> Then<02:06:19.199> if<02:06:19.520> I<02:06:19.920> let's 02:06:20.229 --> 02:06:20.239 align:start position:0% things are included. Then if I let's 02:06:20.239 --> 02:06:24.550 align:start position:0% things are included. Then if I let's suppose<02:06:21.040> perform<02:06:21.520> proper<02:06:22.000> CI/CD<02:06:23.280> integration 02:06:24.550 --> 02:06:24.560 align:start position:0% suppose perform proper CI/CD integration 02:06:24.560 --> 02:06:26.390 align:start position:0% suppose perform proper CI/CD integration meaning<02:06:24.960> after<02:06:25.440> identifying<02:06:25.840> the<02:06:26.080> trigger 02:06:26.390 --> 02:06:26.400 align:start position:0% meaning after identifying the trigger 02:06:26.400 --> 02:06:29.990 align:start position:0% meaning after identifying the trigger sources<02:06:27.119> we've<02:06:27.440> defined<02:06:27.760> our<02:06:28.000> AI<02:06:29.280> then<02:06:29.599> if<02:06:29.840> I 02:06:29.990 --> 02:06:30.000 align:start position:0% sources we've defined our AI then if I 02:06:30.000 --> 02:06:33.430 align:start position:0% sources we've defined our AI then if I say<02:06:30.159> we<02:06:30.400> want<02:06:30.480> to<02:06:30.639> configure<02:06:31.119> CI/CD<02:06:32.480> here<02:06:33.199> what 02:06:33.430 --> 02:06:33.440 align:start position:0% say we want to configure CI/CD here what 02:06:33.440 --> 02:06:35.030 align:start position:0% say we want to configure CI/CD here what I'll<02:06:33.679> do<02:06:33.840> first<02:06:34.079> is<02:06:34.320> take<02:06:34.560> you<02:06:34.719> to<02:06:34.880> the 02:06:35.030 --> 02:06:35.040 align:start position:0% I'll do first is take you to the 02:06:35.040 --> 02:06:36.790 align:start position:0% I'll do first is take you to the configuration 02:06:36.790 --> 02:06:36.800 align:start position:0% configuration 02:06:36.800 --> 02:06:39.430 align:start position:0% configuration in<02:06:37.040> the<02:06:37.280> configuration<02:06:37.920> workflow<02:06:38.880> we<02:06:39.119> first 02:06:39.430 --> 02:06:39.440 align:start position:0% in the configuration workflow we first 02:06:39.440 --> 02:06:41.669 align:start position:0% in the configuration workflow we first discuss<02:06:39.760> the<02:06:40.000> build<02:06:40.239> failure<02:06:41.280> then<02:06:41.520> we 02:06:41.669 --> 02:06:41.679 align:start position:0% discuss the build failure then we 02:06:41.679 --> 02:06:44.069 align:start position:0% discuss the build failure then we understand<02:06:42.079> our<02:06:42.320> codeex<02:06:42.800> investigation 02:06:44.069 --> 02:06:44.079 align:start position:0% understand our codeex investigation 02:06:44.079 --> 02:06:47.030 align:start position:0% understand our codeex investigation generate<02:06:44.480> the<02:06:44.719> fix<02:06:45.520> run<02:06:45.760> the<02:06:45.920> tests<02:06:46.800> create 02:06:47.030 --> 02:06:47.040 align:start position:0% generate the fix run the tests create 02:06:47.040 --> 02:06:49.030 align:start position:0% generate the fix run the tests create the<02:06:47.280> pull<02:06:47.520> request<02:06:47.760> test<02:06:48.480> develop<02:06:48.800> our 02:06:49.030 --> 02:06:49.040 align:start position:0% the pull request test develop our 02:06:49.040 --> 02:06:51.270 align:start position:0% the pull request test develop our reviews<02:06:49.840> and<02:06:50.159> also<02:06:50.480> then<02:06:50.719> merge<02:06:51.040> our 02:06:51.270 --> 02:06:51.280 align:start position:0% reviews and also then merge our 02:06:51.280 --> 02:06:55.189 align:start position:0% reviews and also then merge our workings.<02:06:52.639> So<02:06:52.880> this<02:06:53.119> will<02:06:53.280> come<02:06:53.520> here.<02:06:54.639> Then 02:06:55.189 --> 02:06:55.199 align:start position:0% workings. So this will come here. Then 02:06:55.199 --> 02:06:57.510 align:start position:0% workings. So this will come here. Then the<02:06:55.520> next<02:06:55.760> and<02:06:56.000> most<02:06:56.239> important<02:06:56.719> process 02:06:57.510 --> 02:06:57.520 align:start position:0% the next and most important process 02:06:57.520 --> 02:06:59.270 align:start position:0% the next and most important process which<02:06:57.840> will<02:06:58.000> be<02:06:58.159> discussed<02:06:58.480> in<02:06:58.639> our<02:06:58.880> setup 02:06:59.270 --> 02:06:59.280 align:start position:0% which will be discussed in our setup 02:06:59.280 --> 02:07:02.550 align:start position:0% which will be discussed in our setup here<02:06:59.920> will<02:07:00.159> be<02:07:00.320> our<02:07:00.480> validation<02:07:00.960> of<02:07:01.199> fixes. 02:07:02.550 --> 02:07:02.560 align:start position:0% here will be our validation of fixes. 02:07:02.560 --> 02:07:05.189 align:start position:0% here will be our validation of fixes. Here<02:07:02.880> we<02:07:03.119> will<02:07:03.360> require<02:07:03.760> our<02:07:04.000> unit<02:07:04.320> tests, 02:07:05.189 --> 02:07:05.199 align:start position:0% Here we will require our unit tests, 02:07:05.199 --> 02:07:08.550 align:start position:0% Here we will require our unit tests, integration<02:07:05.840> tests,<02:07:06.800> security<02:07:07.360> scans,<02:07:08.239> code 02:07:08.550 --> 02:07:08.560 align:start position:0% integration tests, security scans, code 02:07:08.560 --> 02:07:11.830 align:start position:0% integration tests, security scans, code reviews<02:07:09.360> and<02:07:09.599> our<02:07:09.840> build<02:07:10.079> verifications. 02:07:11.830 --> 02:07:11.840 align:start position:0% reviews and our build verifications. 02:07:11.840 --> 02:07:13.830 align:start position:0% reviews and our build verifications. These<02:07:12.159> will<02:07:12.400> directly<02:07:12.880> be<02:07:13.040> used<02:07:13.280> to<02:07:13.520> approve 02:07:13.830 --> 02:07:13.840 align:start position:0% These will directly be used to approve 02:07:13.840 --> 02:07:17.109 align:start position:0% These will directly be used to approve our<02:07:14.159> process.<02:07:15.520> All<02:07:15.599> right.<02:07:16.480> Now<02:07:16.800> as<02:07:17.040> an 02:07:17.109 --> 02:07:17.119 align:start position:0% our process. All right. Now as an 02:07:17.119 --> 02:07:19.669 align:start position:0% our process. All right. Now as an example,<02:07:17.920> if<02:07:18.079> I<02:07:18.239> go<02:07:18.400> into<02:07:18.639> codeex<02:07:19.119> and<02:07:19.280> open<02:07:19.520> a 02:07:19.669 --> 02:07:19.679 align:start position:0% example, if I go into codeex and open a 02:07:19.679 --> 02:07:21.750 align:start position:0% example, if I go into codeex and open a new<02:07:19.840> chat,<02:07:20.560> what<02:07:20.800> will<02:07:21.040> happen<02:07:21.199> in<02:07:21.360> our<02:07:21.520> chat 02:07:21.750 --> 02:07:21.760 align:start position:0% new chat, what will happen in our chat 02:07:21.760 --> 02:07:23.669 align:start position:0% new chat, what will happen in our chat is<02:07:22.000> I'll<02:07:22.239> say<02:07:22.400> directly<02:07:22.880> that<02:07:23.040> a<02:07:23.280> GitHub 02:07:23.669 --> 02:07:23.679 align:start position:0% is I'll say directly that a GitHub 02:07:23.679 --> 02:07:25.990 align:start position:0% is I'll say directly that a GitHub action<02:07:24.000> has<02:07:24.159> failed.<02:07:25.199> We'll<02:07:25.520> include<02:07:25.760> the 02:07:25.990 --> 02:07:26.000 align:start position:0% action has failed. We'll include the 02:07:26.000 --> 02:07:28.390 align:start position:0% action has failed. We'll include the repository<02:07:26.480> name<02:07:26.800> directly.<02:07:27.920> We<02:07:28.079> have<02:07:28.239> our 02:07:28.390 --> 02:07:28.400 align:start position:0% repository name directly. We have our 02:07:28.400 --> 02:07:30.629 align:start position:0% repository name directly. We have our failure<02:07:28.800> logs<02:07:29.199> here<02:07:29.599> and<02:07:29.840> the<02:07:30.079> tasks<02:07:30.480> are 02:07:30.629 --> 02:07:30.639 align:start position:0% failure logs here and the tasks are 02:07:30.639 --> 02:07:33.030 align:start position:0% failure logs here and the tasks are being<02:07:30.800> discussed<02:07:31.199> the<02:07:31.440> most<02:07:31.679> here.<02:07:32.960> All 02:07:33.030 --> 02:07:33.040 align:start position:0% being discussed the most here. All 02:07:33.040 --> 02:07:35.669 align:start position:0% being discussed the most here. All right.<02:07:33.920> After<02:07:34.239> that,<02:07:34.480> we<02:07:34.719> have<02:07:34.800> our<02:07:35.040> unit<02:07:35.440> test 02:07:35.669 --> 02:07:35.679 align:start position:0% right. After that, we have our unit test 02:07:35.679 --> 02:07:38.550 align:start position:0% right. After that, we have our unit test failure<02:07:36.079> which<02:07:36.320> we<02:07:36.480> will<02:07:36.639> use.<02:07:37.599> After<02:07:37.920> that, 02:07:38.550 --> 02:07:38.560 align:start position:0% failure which we will use. After that, 02:07:38.560 --> 02:07:40.550 align:start position:0% failure which we will use. After that, whatever<02:07:39.040> automated<02:07:39.599> bug<02:07:39.920> resolution<02:07:40.400> we 02:07:40.550 --> 02:07:40.560 align:start position:0% whatever automated bug resolution we 02:07:40.560 --> 02:07:42.790 align:start position:0% whatever automated bug resolution we have<02:07:40.800> directly,<02:07:41.280> we<02:07:41.520> will<02:07:41.679> configure<02:07:42.079> it.<02:07:42.560> We 02:07:42.790 --> 02:07:42.800 align:start position:0% have directly, we will configure it. We 02:07:42.800 --> 02:07:45.669 align:start position:0% have directly, we will configure it. We will<02:07:43.040> discuss<02:07:43.360> a<02:07:43.679> onego<02:07:44.159> project<02:07:44.560> today.<02:07:45.440> We 02:07:45.669 --> 02:07:45.679 align:start position:0% will discuss a onego project today. We 02:07:45.679 --> 02:07:47.669 align:start position:0% will discuss a onego project today. We will<02:07:45.840> direct<02:07:46.239> a<02:07:46.480> full<02:07:46.719> repository<02:07:47.280> in<02:07:47.440> our 02:07:47.669 --> 02:07:47.679 align:start position:0% will direct a full repository in our 02:07:47.679 --> 02:07:49.669 align:start position:0% will direct a full repository in our onego<02:07:48.159> project. 02:07:49.669 --> 02:07:49.679 align:start position:0% onego project. 02:07:49.679 --> 02:07:51.830 align:start position:0% onego project. First<02:07:50.079> we<02:07:50.320> will<02:07:50.560> create<02:07:50.880> all<02:07:51.199> project<02:07:51.599> code 02:07:51.830 --> 02:07:51.840 align:start position:0% First we will create all project code 02:07:51.840 --> 02:07:54.709 align:start position:0% First we will create all project code and<02:07:52.159> details.<02:07:53.440> After<02:07:53.760> that<02:07:54.159> we<02:07:54.320> will<02:07:54.480> check 02:07:54.709 --> 02:07:54.719 align:start position:0% and details. After that we will check 02:07:54.719 --> 02:07:56.310 align:start position:0% and details. After that we will check our<02:07:54.960> iterations<02:07:55.520> and<02:07:55.840> possible 02:07:56.310 --> 02:07:56.320 align:start position:0% our iterations and possible 02:07:56.320 --> 02:07:57.830 align:start position:0% our iterations and possible improvements. 02:07:57.830 --> 02:07:57.840 align:start position:0% improvements. 02:07:57.840 --> 02:08:01.510 align:start position:0% improvements. Then<02:07:58.159> we<02:07:58.400> will<02:07:58.560> use<02:07:58.800> GitHub<02:07:59.280> and<02:07:59.520> codeex. 02:08:01.510 --> 02:08:01.520 align:start position:0% Then we will use GitHub and codeex. 02:08:01.520 --> 02:08:05.430 align:start position:0% Then we will use GitHub and codeex. Here<02:08:01.760> is<02:08:01.920> our<02:08:02.159> codeex.<02:08:03.360> We<02:08:03.599> open<02:08:04.000> codeex. 02:08:05.430 --> 02:08:05.440 align:start position:0% Here is our codeex. We open codeex. 02:08:05.440 --> 02:08:08.310 align:start position:0% Here is our codeex. We open codeex. Inside<02:08:05.920> codeex<02:08:06.639> we<02:08:06.800> generate<02:08:07.199> a<02:08:07.440> full<02:08:07.760> project 02:08:08.310 --> 02:08:08.320 align:start position:0% Inside codeex we generate a full project 02:08:08.320 --> 02:08:11.830 align:start position:0% Inside codeex we generate a full project before<02:08:08.639> using<02:08:09.040> prompts.<02:08:10.480> In<02:08:10.719> codeex<02:08:11.360> we<02:08:11.599> must 02:08:11.830 --> 02:08:11.840 align:start position:0% before using prompts. In codeex we must 02:08:11.840 --> 02:08:15.350 align:start position:0% before using prompts. In codeex we must include<02:08:12.239> the<02:08:12.480> set<02:08:12.800> agents<02:08:13.360> file<02:08:14.719> but<02:08:14.960> we<02:08:15.119> will 02:08:15.350 --> 02:08:15.360 align:start position:0% include the set agents file but we will 02:08:15.360 --> 02:08:18.550 align:start position:0% include the set agents file but we will first<02:08:15.760> exit<02:08:16.159> this<02:08:16.480> project.<02:08:17.840> Then<02:08:18.159> we<02:08:18.320> will 02:08:18.550 --> 02:08:18.560 align:start position:0% first exit this project. Then we will 02:08:18.560 --> 02:08:21.510 align:start position:0% first exit this project. Then we will build<02:08:18.719> a<02:08:18.960> new<02:08:19.119> project<02:08:19.599> here.<02:08:20.800> I<02:08:21.119> will<02:08:21.280> close 02:08:21.510 --> 02:08:21.520 align:start position:0% build a new project here. I will close 02:08:21.520 --> 02:08:24.629 align:start position:0% build a new project here. I will close this<02:08:21.840> one.<02:08:23.040> We<02:08:23.280> close<02:08:23.520> it<02:08:23.760> and<02:08:24.079> build<02:08:24.320> a<02:08:24.480> new 02:08:24.629 --> 02:08:24.639 align:start position:0% this one. We close it and build a new 02:08:24.639 --> 02:08:27.589 align:start position:0% this one. We close it and build a new project<02:08:25.119> again.<02:08:26.480> You<02:08:26.719> see<02:08:26.960> projects<02:08:27.360> are 02:08:27.589 --> 02:08:27.599 align:start position:0% project again. You see projects are 02:08:27.599 --> 02:08:30.390 align:start position:0% project again. You see projects are available<02:08:28.000> here.<02:08:28.960> I<02:08:29.199> can<02:08:29.440> organize<02:08:29.920> them<02:08:30.159> or 02:08:30.390 --> 02:08:30.400 align:start position:0% available here. I can organize them or 02:08:30.400 --> 02:08:32.390 align:start position:0% available here. I can organize them or start<02:08:30.639> from<02:08:30.880> scratch. 02:08:32.390 --> 02:08:32.400 align:start position:0% start from scratch. 02:08:32.400 --> 02:08:36.149 align:start position:0% start from scratch. We<02:08:32.639> will<02:08:32.800> name<02:08:32.960> our<02:08:33.199> project<02:08:33.920> one<02:08:34.320> go.<02:08:35.760> In<02:08:36.000> this 02:08:36.149 --> 02:08:36.159 align:start position:0% We will name our project one go. In this 02:08:36.159 --> 02:08:37.990 align:start position:0% We will name our project one go. In this project,<02:08:36.639> we<02:08:36.880> will<02:08:37.040> build<02:08:37.280> a<02:08:37.599> complete 02:08:37.990 --> 02:08:38.000 align:start position:0% project, we will build a complete 02:08:38.000 --> 02:08:41.109 align:start position:0% project, we will build a complete application<02:08:38.719> with<02:08:39.040> everything.<02:08:40.480> First,<02:08:40.960> we 02:08:41.109 --> 02:08:41.119 align:start position:0% application with everything. First, we 02:08:41.119 --> 02:08:43.430 align:start position:0% application with everything. First, we will<02:08:41.280> pin<02:08:41.599> this<02:08:41.840> project. 02:08:43.430 --> 02:08:43.440 align:start position:0% will pin this project. 02:08:43.440 --> 02:08:45.430 align:start position:0% will pin this project. After<02:08:43.840> pinning,<02:08:44.320> we<02:08:44.560> open<02:08:44.800> it<02:08:45.040> in<02:08:45.199> our 02:08:45.430 --> 02:08:45.440 align:start position:0% After pinning, we open it in our 02:08:45.440 --> 02:08:46.950 align:start position:0% After pinning, we open it in our explorer. 02:08:46.950 --> 02:08:46.960 align:start position:0% explorer. 02:08:46.960 --> 02:08:50.390 align:start position:0% explorer. Our<02:08:47.199> explorer<02:08:47.840> has<02:08:48.000> no<02:08:48.320> file<02:08:48.639> inside. 02:08:50.390 --> 02:08:50.400 align:start position:0% Our explorer has no file inside. 02:08:50.400 --> 02:08:52.550 align:start position:0% Our explorer has no file inside. Later,<02:08:50.960> all<02:08:51.280> generations<02:08:51.840> will<02:08:52.079> come<02:08:52.239> into 02:08:52.550 --> 02:08:52.560 align:start position:0% Later, all generations will come into 02:08:52.560 --> 02:08:54.310 align:start position:0% Later, all generations will come into this<02:08:52.800> file. 02:08:54.310 --> 02:08:54.320 align:start position:0% this file. 02:08:54.320 --> 02:08:57.750 align:start position:0% this file. We<02:08:54.560> have<02:08:54.719> our<02:08:54.960> VS<02:08:55.440> code<02:08:55.760> and<02:08:56.000> terminal.<02:08:57.280> I<02:08:57.599> told 02:08:57.750 --> 02:08:57.760 align:start position:0% We have our VS code and terminal. I told 02:08:57.760 --> 02:08:59.750 align:start position:0% We have our VS code and terminal. I told you<02:08:57.920> before<02:08:58.320> we<02:08:58.560> can<02:08:58.719> use<02:08:58.960> codecs<02:08:59.440> in<02:08:59.599> our 02:08:59.750 --> 02:08:59.760 align:start position:0% you before we can use codecs in our 02:08:59.760 --> 02:09:01.430 align:start position:0% you before we can use codecs in our terminal. 02:09:01.430 --> 02:09:01.440 align:start position:0% terminal. 02:09:01.440 --> 02:09:05.109 align:start position:0% terminal. In<02:09:01.760> VS<02:09:02.239> Code,<02:09:02.560> our<02:09:02.800> cursor<02:09:03.280> is<02:09:03.440> available.<02:09:04.800> I 02:09:05.109 --> 02:09:05.119 align:start position:0% In VS Code, our cursor is available. I 02:09:05.119 --> 02:09:07.669 align:start position:0% In VS Code, our cursor is available. I will<02:09:05.280> first<02:09:05.599> tell<02:09:05.760> you<02:09:05.920> the<02:09:06.159> plan.<02:09:07.280> We<02:09:07.440> will 02:09:07.669 --> 02:09:07.679 align:start position:0% will first tell you the plan. We will 02:09:07.679 --> 02:09:11.109 align:start position:0% will first tell you the plan. We will open<02:09:08.000> our<02:09:08.239> plan<02:09:08.639> mode.<02:09:09.920> We<02:09:10.159> have<02:09:10.320> no<02:09:10.639> plugins 02:09:11.109 --> 02:09:11.119 align:start position:0% open our plan mode. We have no plugins 02:09:11.119 --> 02:09:14.790 align:start position:0% open our plan mode. We have no plugins yet.<02:09:12.159> We<02:09:12.400> will<02:09:12.560> not<02:09:12.800> use<02:09:12.960> the<02:09:13.199> browser<02:09:13.599> much. 02:09:14.790 --> 02:09:14.800 align:start position:0% yet. We will not use the browser much. 02:09:14.800 --> 02:09:18.790 align:start position:0% yet. We will not use the browser much. We<02:09:15.040> will<02:09:15.280> use<02:09:15.440> the<02:09:15.760> 5.4<02:09:16.560> model<02:09:16.880> in<02:09:17.119> our<02:09:17.280> GPT. 02:09:18.790 --> 02:09:18.800 align:start position:0% We will use the 5.4 model in our GPT. 02:09:18.800 --> 02:09:22.550 align:start position:0% We will use the 5.4 model in our GPT. We<02:09:19.040> will<02:09:19.199> use<02:09:19.440> the<02:09:19.679> medium<02:09:20.239> 5.4<02:09:20.960> model.<02:09:22.320> We 02:09:22.550 --> 02:09:22.560 align:start position:0% We will use the medium 5.4 model. We 02:09:22.560 --> 02:09:25.109 align:start position:0% We will use the medium 5.4 model. We will<02:09:22.719> use<02:09:23.119> fast<02:09:23.520> speed<02:09:23.840> here.<02:09:24.320> Not<02:09:24.639> default 02:09:25.109 --> 02:09:25.119 align:start position:0% will use fast speed here. Not default 02:09:25.119 --> 02:09:28.550 align:start position:0% will use fast speed here. Not default speed.<02:09:26.239> It<02:09:26.480> will<02:09:26.639> be<02:09:26.719> used<02:09:27.040> here. 02:09:28.550 --> 02:09:28.560 align:start position:0% speed. It will be used here. 02:09:28.560 --> 02:09:31.669 align:start position:0% speed. It will be used here. We<02:09:28.800> will<02:09:28.960> not<02:09:29.199> connect<02:09:29.520> GitHub<02:09:30.000> for<02:09:30.159> now.<02:09:31.360> I 02:09:31.669 --> 02:09:31.679 align:start position:0% We will not connect GitHub for now. I 02:09:31.679 --> 02:09:34.149 align:start position:0% We will not connect GitHub for now. I will<02:09:31.840> say<02:09:32.079> in<02:09:32.320> one<02:09:32.639> go<02:09:33.199> that<02:09:33.440> I'm<02:09:33.760> going<02:09:33.920> to 02:09:34.149 --> 02:09:34.159 align:start position:0% will say in one go that I'm going to 02:09:34.159 --> 02:09:35.990 align:start position:0% will say in one go that I'm going to make<02:09:34.239> a<02:09:34.480> project<02:09:34.880> about<02:09:35.199> a<02:09:35.440> healthcare 02:09:35.990 --> 02:09:36.000 align:start position:0% make a project about a healthcare 02:09:36.000 --> 02:09:37.669 align:start position:0% make a project about a healthcare application. 02:09:37.669 --> 02:09:37.679 align:start position:0% application. 02:09:37.679 --> 02:09:40.629 align:start position:0% application. Can<02:09:37.920> you<02:09:38.079> plan<02:09:38.320> a<02:09:38.560> project<02:09:38.880> for<02:09:39.119> me? 02:09:40.629 --> 02:09:40.639 align:start position:0% Can you plan a project for me? 02:09:40.639 --> 02:09:43.589 align:start position:0% Can you plan a project for me? Project<02:09:41.040> planning<02:09:41.440> will<02:09:41.760> start<02:09:42.000> here.<02:09:43.280> First 02:09:43.589 --> 02:09:43.599 align:start position:0% Project planning will start here. First 02:09:43.599 --> 02:09:46.470 align:start position:0% Project planning will start here. First it<02:09:43.920> will<02:09:44.079> settle<02:09:44.480> output<02:09:44.960> resources. 02:09:46.470 --> 02:09:46.480 align:start position:0% it will settle output resources. 02:09:46.480 --> 02:09:49.830 align:start position:0% it will settle output resources. I<02:09:46.719> will<02:09:46.880> not<02:09:47.119> include<02:09:47.360> them.<02:09:47.679> Now<02:09:49.040> we<02:09:49.280> look<02:09:49.520> at 02:09:49.830 --> 02:09:49.840 align:start position:0% I will not include them. Now we look at 02:09:49.840 --> 02:09:51.830 align:start position:0% I will not include them. Now we look at current<02:09:50.239> workspace. 02:09:51.830 --> 02:09:51.840 align:start position:0% current workspace. 02:09:51.840 --> 02:09:55.189 align:start position:0% current workspace. You<02:09:52.079> see<02:09:52.320> nothing<02:09:52.639> is<02:09:52.800> there<02:09:53.040> in<02:09:53.280> workspace. 02:09:55.189 --> 02:09:55.199 align:start position:0% You see nothing is there in workspace. 02:09:55.199 --> 02:09:57.350 align:start position:0% You see nothing is there in workspace. Who<02:09:55.440> is<02:09:55.599> the<02:09:55.760> primary<02:09:56.239> user<02:09:56.639> for<02:09:56.880> the<02:09:57.119> first 02:09:57.350 --> 02:09:57.360 align:start position:0% Who is the primary user for the first 02:09:57.360 --> 02:10:00.229 align:start position:0% Who is the primary user for the first version<02:09:57.679> of<02:09:57.840> the<02:09:58.000> healthcare<02:09:58.480> app?<02:09:59.760> We<02:10:00.079> have 02:10:00.229 --> 02:10:00.239 align:start position:0% version of the healthcare app? We have 02:10:00.239 --> 02:10:02.550 align:start position:0% version of the healthcare app? We have patients<02:10:00.719> and<02:10:01.040> doctors. 02:10:02.550 --> 02:10:02.560 align:start position:0% patients and doctors. 02:10:02.560 --> 02:10:05.030 align:start position:0% patients and doctors. I<02:10:02.800> will<02:10:03.040> say<02:10:03.679> this<02:10:04.000> application<02:10:04.560> is<02:10:04.880> for 02:10:05.030 --> 02:10:05.040 align:start position:0% I will say this application is for 02:10:05.040 --> 02:10:06.709 align:start position:0% I will say this application is for patients. 02:10:06.709 --> 02:10:06.719 align:start position:0% patients. 02:10:06.719 --> 02:10:08.629 align:start position:0% patients. We<02:10:06.960> want<02:10:07.119> to<02:10:07.280> build<02:10:07.440> an<02:10:07.679> application<02:10:08.239> for<02:10:08.400> our 02:10:08.629 --> 02:10:08.639 align:start position:0% We want to build an application for our 02:10:08.639 --> 02:10:11.109 align:start position:0% We want to build an application for our patients.<02:10:09.760> What<02:10:10.000> kind<02:10:10.159> of<02:10:10.320> first<02:10:10.639> release<02:10:10.960> do 02:10:11.109 --> 02:10:11.119 align:start position:0% patients. What kind of first release do 02:10:11.119 --> 02:10:15.109 align:start position:0% patients. What kind of first release do you<02:10:11.280> want<02:10:11.360> to<02:10:11.520> plan?<02:10:12.639> MVP<02:10:13.679> or<02:10:13.920> balanced<02:10:14.800> or 02:10:15.109 --> 02:10:15.119 align:start position:0% you want to plan? MVP or balanced or 02:10:15.119 --> 02:10:16.709 align:start position:0% you want to plan? MVP or balanced or ambitious? 02:10:16.709 --> 02:10:16.719 align:start position:0% ambitious? 02:10:16.719 --> 02:10:19.270 align:start position:0% ambitious? I<02:10:17.040> will<02:10:17.199> choose<02:10:17.520> MVP. 02:10:19.270 --> 02:10:19.280 align:start position:0% I will choose MVP. 02:10:19.280 --> 02:10:21.750 align:start position:0% I will choose MVP. What<02:10:19.520> is<02:10:19.599> our<02:10:19.840> delivery<02:10:20.239> target? 02:10:21.750 --> 02:10:21.760 align:start position:0% What is our delivery target? 02:10:21.760 --> 02:10:24.229 align:start position:0% What is our delivery target? We<02:10:22.000> want<02:10:22.159> to<02:10:22.320> build<02:10:22.480> a<02:10:22.639> web<02:10:22.880> application<02:10:23.440> here. 02:10:24.229 --> 02:10:24.239 align:start position:0% We want to build a web application here. 02:10:24.239 --> 02:10:27.270 align:start position:0% We want to build a web application here. I<02:10:24.480> will<02:10:24.639> not<02:10:24.880> build<02:10:25.119> a<02:10:25.360> mobile<02:10:25.760> application.<02:10:27.040> I 02:10:27.270 --> 02:10:27.280 align:start position:0% I will not build a mobile application. I 02:10:27.280 --> 02:10:29.669 align:start position:0% I will not build a mobile application. I will<02:10:27.440> build<02:10:27.679> a<02:10:27.920> web<02:10:28.159> app<02:10:28.400> here. 02:10:29.669 --> 02:10:29.679 align:start position:0% will build a web app here. 02:10:29.679 --> 02:10:31.990 align:start position:0% will build a web app here. The<02:10:29.920> current<02:10:30.239> decision<02:10:30.560> is<02:10:30.880> clear. 02:10:31.990 --> 02:10:32.000 align:start position:0% The current decision is clear. 02:10:32.000 --> 02:10:34.870 align:start position:0% The current decision is clear. Patientfacing,<02:10:33.040> MVP<02:10:33.679> sized<02:10:34.079> and<02:10:34.320> optimized 02:10:34.870 --> 02:10:34.880 align:start position:0% Patientfacing, MVP sized and optimized 02:10:34.880 --> 02:10:36.950 align:start position:0% Patientfacing, MVP sized and optimized for<02:10:35.040> a<02:10:35.199> web<02:10:35.440> app. 02:10:36.950 --> 02:10:36.960 align:start position:0% for a web app. 02:10:36.960 --> 02:10:39.990 align:start position:0% for a web app. I<02:10:37.199> still<02:10:37.520> need<02:10:37.679> to<02:10:37.840> lock<02:10:38.079> the<02:10:38.239> feature<02:10:38.560> set. 02:10:39.990 --> 02:10:40.000 align:start position:0% I still need to lock the feature set. 02:10:40.000 --> 02:10:42.470 align:start position:0% I still need to lock the feature set. Now<02:10:40.239> we<02:10:40.480> have<02:10:40.560> our<02:10:40.800> feature<02:10:41.119> sets.<02:10:42.159> Which 02:10:42.470 --> 02:10:42.480 align:start position:0% Now we have our feature sets. Which 02:10:42.480 --> 02:10:45.589 align:start position:0% Now we have our feature sets. Which feature<02:10:42.800> bundle<02:10:43.199> should<02:10:43.440> define<02:10:43.760> the<02:10:44.000> MVP 02:10:45.589 --> 02:10:45.599 align:start position:0% feature bundle should define the MVP 02:10:45.599 --> 02:10:48.629 align:start position:0% feature bundle should define the MVP booking<02:10:46.000> and<02:10:46.320> records?<02:10:47.679> We<02:10:47.920> will<02:10:48.079> use<02:10:48.320> this 02:10:48.629 --> 02:10:48.639 align:start position:0% booking and records? We will use this 02:10:48.639 --> 02:10:50.790 align:start position:0% booking and records? We will use this simple<02:10:48.960> option. 02:10:50.790 --> 02:10:50.800 align:start position:0% simple option. 02:10:50.800 --> 02:10:52.550 align:start position:0% simple option. How<02:10:51.040> should<02:10:51.199> the<02:10:51.360> plan<02:10:51.679> treat<02:10:52.000> healthcare 02:10:52.550 --> 02:10:52.560 align:start position:0% How should the plan treat healthcare 02:10:52.560 --> 02:10:55.270 align:start position:0% How should the plan treat healthcare compliance<02:10:53.119> in<02:10:53.280> the<02:10:53.440> first<02:10:53.679> version? 02:10:55.270 --> 02:10:55.280 align:start position:0% compliance in the first version? 02:10:55.280 --> 02:10:57.830 align:start position:0% compliance in the first version? We<02:10:55.599> will<02:10:55.760> use<02:10:56.159> HIPPA<02:10:56.639> ready<02:10:56.960> design<02:10:57.360> which<02:10:57.679> is 02:10:57.830 --> 02:10:57.840 align:start position:0% We will use HIPPA ready design which is 02:10:57.840 --> 02:10:59.510 align:start position:0% We will use HIPPA ready design which is recommended. 02:10:59.510 --> 02:10:59.520 align:start position:0% recommended. 02:10:59.520 --> 02:11:02.069 align:start position:0% recommended. We<02:10:59.760> can<02:10:59.920> also<02:11:00.239> use<02:11:00.560> full<02:11:00.880> compliance<02:11:01.360> track<02:11:01.760> or 02:11:02.069 --> 02:11:02.079 align:start position:0% We can also use full compliance track or 02:11:02.079 --> 02:11:04.390 align:start position:0% We can also use full compliance track or lightweight<02:11:02.639> prototype. 02:11:04.390 --> 02:11:04.400 align:start position:0% lightweight prototype. 02:11:04.400 --> 02:11:06.550 align:start position:0% lightweight prototype. How<02:11:04.719> much<02:11:04.960> external<02:11:05.599> integration<02:11:06.159> should<02:11:06.400> the 02:11:06.550 --> 02:11:06.560 align:start position:0% How much external integration should the 02:11:06.560 --> 02:11:08.709 align:start position:0% How much external integration should the first<02:11:06.800> plan<02:11:07.119> include? 02:11:08.709 --> 02:11:08.719 align:start position:0% first plan include? 02:11:08.719 --> 02:11:10.950 align:start position:0% first plan include? I<02:11:09.040> will<02:11:09.199> say<02:11:09.599> minimal<02:11:10.079> integration<02:11:10.560> will<02:11:10.800> be 02:11:10.950 --> 02:11:10.960 align:start position:0% I will say minimal integration will be 02:11:10.960 --> 02:11:13.350 align:start position:0% I will say minimal integration will be included.<02:11:12.079> These<02:11:12.400> things<02:11:12.639> are<02:11:12.880> recommended 02:11:13.350 --> 02:11:13.360 align:start position:0% included. These things are recommended 02:11:13.360 --> 02:11:16.229 align:start position:0% included. These things are recommended here.<02:11:14.320> Through<02:11:14.639> them<02:11:14.960> our<02:11:15.280> entire<02:11:15.760> process 02:11:16.229 --> 02:11:16.239 align:start position:0% here. Through them our entire process 02:11:16.239 --> 02:11:17.910 align:start position:0% here. Through them our entire process comes. 02:11:17.910 --> 02:11:17.920 align:start position:0% comes. 02:11:17.920 --> 02:11:20.790 align:start position:0% comes. What<02:11:18.159> will<02:11:18.320> be<02:11:18.480> the<02:11:18.639> delivery<02:11:19.040> timeline? 02:11:20.790 --> 02:11:20.800 align:start position:0% What will be the delivery timeline? 02:11:20.800 --> 02:11:22.470 align:start position:0% What will be the delivery timeline? What<02:11:21.040> will<02:11:21.199> be<02:11:21.280> the<02:11:21.440> delivery<02:11:21.840> timeline<02:11:22.320> for 02:11:22.470 --> 02:11:22.480 align:start position:0% What will be the delivery timeline for 02:11:22.480 --> 02:11:24.390 align:start position:0% What will be the delivery timeline for our<02:11:22.719> project? 02:11:24.390 --> 02:11:24.400 align:start position:0% our project? 02:11:24.400 --> 02:11:26.629 align:start position:0% our project? I<02:11:24.719> will<02:11:24.880> say<02:11:25.199> I<02:11:25.440> want<02:11:25.599> it<02:11:25.840> in<02:11:26.000> an<02:11:26.239> urgent 02:11:26.629 --> 02:11:26.639 align:start position:0% I will say I want it in an urgent 02:11:26.639 --> 02:11:29.830 align:start position:0% I will say I want it in an urgent manner.<02:11:28.079> This<02:11:28.320> is<02:11:28.400> a<02:11:28.639> fourth<02:11:28.960> part<02:11:29.440> where<02:11:29.679> we 02:11:29.830 --> 02:11:29.840 align:start position:0% manner. This is a fourth part where we 02:11:29.840 --> 02:11:32.709 align:start position:0% manner. This is a fourth part where we can<02:11:30.000> include<02:11:30.320> what<02:11:30.560> we<02:11:30.800> want.<02:11:32.159> What<02:11:32.400> team 02:11:32.709 --> 02:11:32.719 align:start position:0% can include what we want. What team 02:11:32.719 --> 02:11:34.950 align:start position:0% can include what we want. What team should<02:11:32.960> this<02:11:33.119> plan<02:11:33.440> assume? 02:11:34.950 --> 02:11:34.960 align:start position:0% should this plan assume? 02:11:34.960 --> 02:11:37.750 align:start position:0% should this plan assume? Our<02:11:35.280> small<02:11:35.599> team<02:11:35.840> is<02:11:36.079> here.<02:11:37.119> Instead<02:11:37.440> of<02:11:37.599> a 02:11:37.750 --> 02:11:37.760 align:start position:0% Our small team is here. Instead of a 02:11:37.760 --> 02:11:41.350 align:start position:0% Our small team is here. Instead of a small<02:11:38.079> team,<02:11:38.560> we<02:11:38.880> can<02:11:39.040> choose<02:11:39.520> solo<02:11:40.000> builder. 02:11:41.350 --> 02:11:41.360 align:start position:0% small team, we can choose solo builder. 02:11:41.360 --> 02:11:44.310 align:start position:0% small team, we can choose solo builder. Our<02:11:41.679> solo<02:11:42.079> builder<02:11:42.400> is<02:11:42.560> here.<02:11:42.800> Now, 02:11:44.310 --> 02:11:44.320 align:start position:0% Our solo builder is here. Now, 02:11:44.320 --> 02:11:46.470 align:start position:0% Our solo builder is here. Now, what<02:11:44.560> kind<02:11:44.719> of<02:11:44.880> plan<02:11:45.119> do<02:11:45.360> you<02:11:45.440> need?<02:11:46.079> Build 02:11:46.470 --> 02:11:46.480 align:start position:0% what kind of plan do you need? Build 02:11:46.480 --> 02:11:49.750 align:start position:0% what kind of plan do you need? Build plan<02:11:46.960> or<02:11:47.280> business<02:11:47.760> build.<02:11:49.119> We<02:11:49.360> will<02:11:49.599> work 02:11:49.750 --> 02:11:49.760 align:start position:0% plan or business build. We will work 02:11:49.760 --> 02:11:53.030 align:start position:0% plan or business build. We will work with<02:11:49.920> a<02:11:50.159> simple<02:11:50.560> build<02:11:50.880> plan.<02:11:52.159> Now<02:11:52.400> it<02:11:52.639> reduces 02:11:53.030 --> 02:11:53.040 align:start position:0% with a simple build plan. Now it reduces 02:11:53.040 --> 02:11:55.990 align:start position:0% with a simple build plan. Now it reduces the<02:11:53.280> project<02:11:53.599> scope<02:11:53.920> and<02:11:54.239> other<02:11:54.400> things. 02:11:55.990 --> 02:11:56.000 align:start position:0% the project scope and other things. 02:11:56.000 --> 02:11:57.990 align:start position:0% the project scope and other things. You<02:11:56.239> see<02:11:56.639> multiple<02:11:57.119> questions<02:11:57.520> are<02:11:57.679> asked 02:11:57.990 --> 02:11:58.000 align:start position:0% You see multiple questions are asked 02:11:58.000 --> 02:12:00.870 align:start position:0% You see multiple questions are asked here<02:11:58.960> for<02:11:59.199> a<02:11:59.360> solo<02:11:59.760> builder.<02:12:00.320> What<02:12:00.560> does 02:12:00.870 --> 02:12:00.880 align:start position:0% here for a solo builder. What does 02:12:00.880 --> 02:12:02.550 align:start position:0% here for a solo builder. What does urgent<02:12:01.199> mean<02:12:01.440> for<02:12:01.679> the<02:12:01.840> first<02:12:02.079> usable 02:12:02.550 --> 02:12:02.560 align:start position:0% urgent mean for the first usable 02:12:02.560 --> 02:12:06.550 align:start position:0% urgent mean for the first usable release?<02:12:03.920> We<02:12:04.159> will<02:12:04.320> answer<02:12:04.880> one<02:12:05.199> week.<02:12:06.320> We 02:12:06.550 --> 02:12:06.560 align:start position:0% release? We will answer one week. We 02:12:06.560 --> 02:12:09.270 align:start position:0% release? We will answer one week. We will<02:12:06.800> include<02:12:07.199> one<02:12:07.520> week<02:12:07.760> here. 02:12:09.270 --> 02:12:09.280 align:start position:0% will include one week here. 02:12:09.280 --> 02:12:12.069 align:start position:0% will include one week here. Our<02:12:09.520> plan<02:12:09.840> will<02:12:10.000> come<02:12:10.239> here.<02:12:11.520> Build<02:12:11.840> a 02:12:12.069 --> 02:12:12.079 align:start position:0% Our plan will come here. Build a 02:12:12.079 --> 02:12:15.030 align:start position:0% Our plan will come here. Build a patient-f<02:12:12.560> facing<02:12:13.119> web<02:12:13.520> MVP<02:12:14.159> for<02:12:14.400> a<02:12:14.639> solo 02:12:15.030 --> 02:12:15.040 align:start position:0% patient-f facing web MVP for a solo 02:12:15.040 --> 02:12:17.910 align:start position:0% patient-f facing web MVP for a solo builder<02:12:15.840> optimized<02:12:16.480> for<02:12:16.800> one<02:12:17.040> week<02:12:17.599> urgent 02:12:17.910 --> 02:12:17.920 align:start position:0% builder optimized for one week urgent 02:12:17.920 --> 02:12:20.229 align:start position:0% builder optimized for one week urgent prototype<02:12:18.960> while<02:12:19.280> keeping<02:12:19.520> the<02:12:19.760> design 02:12:20.229 --> 02:12:20.239 align:start position:0% prototype while keeping the design 02:12:20.239 --> 02:12:22.870 align:start position:0% prototype while keeping the design hippaware<02:12:21.199> and<02:12:21.520> future<02:12:21.920> ready<02:12:22.239> for<02:12:22.560> real 02:12:22.870 --> 02:12:22.880 align:start position:0% hippaware and future ready for real 02:12:22.880 --> 02:12:25.270 align:start position:0% hippaware and future ready for real healthcare<02:12:23.440> data<02:12:23.760> handling. 02:12:25.270 --> 02:12:25.280 align:start position:0% healthcare data handling. 02:12:25.280 --> 02:12:27.669 align:start position:0% healthcare data handling. I<02:12:25.599> will<02:12:25.760> read<02:12:25.920> the<02:12:26.079> plan<02:12:26.400> once<02:12:27.040> then<02:12:27.280> we<02:12:27.440> will 02:12:27.669 --> 02:12:27.679 align:start position:0% I will read the plan once then we will 02:12:27.679 --> 02:12:30.470 align:start position:0% I will read the plan once then we will implement<02:12:28.079> it.<02:12:29.280> I<02:12:29.520> am<02:12:29.679> saying<02:12:29.840> that<02:12:30.079> we<02:12:30.320> have 02:12:30.470 --> 02:12:30.480 align:start position:0% implement it. I am saying that we have 02:12:30.480 --> 02:12:33.589 align:start position:0% implement it. I am saying that we have the<02:12:30.719> entire<02:12:31.199> process.<02:12:32.560> We<02:12:32.800> say<02:12:33.040> our<02:12:33.280> product 02:12:33.589 --> 02:12:33.599 align:start position:0% the entire process. We say our product 02:12:33.599 --> 02:12:36.950 align:start position:0% the entire process. We say our product definition<02:12:34.079> is<02:12:34.400> also<02:12:34.719> happening<02:12:35.119> here.<02:12:36.560> After 02:12:36.950 --> 02:12:36.960 align:start position:0% definition is also happening here. After 02:12:36.960 --> 02:12:39.830 align:start position:0% definition is also happening here. After product<02:12:37.280> definition,<02:12:38.239> our<02:12:38.560> recommended<02:12:39.119> MVP 02:12:39.830 --> 02:12:39.840 align:start position:0% product definition, our recommended MVP 02:12:39.840 --> 02:12:42.709 align:start position:0% product definition, our recommended MVP features<02:12:40.239> have<02:12:40.480> also<02:12:40.800> arrived<02:12:41.199> here. 02:12:42.709 --> 02:12:42.719 align:start position:0% features have also arrived here. 02:12:42.719 --> 02:12:44.629 align:start position:0% features have also arrived here. Front<02:12:42.960> end<02:12:43.280> and<02:12:43.520> backend<02:12:44.000> have<02:12:44.159> come<02:12:44.320> in<02:12:44.480> our 02:12:44.629 --> 02:12:44.639 align:start position:0% Front end and backend have come in our 02:12:44.639 --> 02:12:46.629 align:start position:0% Front end and backend have come in our technical<02:12:45.040> approach. 02:12:46.629 --> 02:12:46.639 align:start position:0% technical approach. 02:12:46.639 --> 02:12:48.550 align:start position:0% technical approach. I<02:12:46.960> will<02:12:47.119> tell<02:12:47.199> it<02:12:47.440> that<02:12:47.599> I<02:12:47.840> want<02:12:48.079> just<02:12:48.320> a 02:12:48.550 --> 02:12:48.560 align:start position:0% I will tell it that I want just a 02:12:48.560 --> 02:12:51.910 align:start position:0% I will tell it that I want just a working<02:12:48.960> front<02:12:49.280> end<02:12:49.599> and<02:12:49.920> minimal<02:12:50.400> back<02:12:50.639> end. 02:12:51.910 --> 02:12:51.920 align:start position:0% working front end and minimal back end. 02:12:51.920 --> 02:12:55.189 align:start position:0% working front end and minimal back end. Also,<02:12:52.400> it<02:12:52.719> should<02:12:52.800> be<02:12:52.960> just<02:12:53.360> HTML<02:12:54.159> and<02:12:54.480> CSS 02:12:55.189 --> 02:12:55.199 align:start position:0% Also, it should be just HTML and CSS 02:12:55.199 --> 02:12:57.510 align:start position:0% Also, it should be just HTML and CSS with<02:12:55.440> JS<02:12:55.920> logics. 02:12:57.510 --> 02:12:57.520 align:start position:0% with JS logics. 02:12:57.520 --> 02:13:00.790 align:start position:0% with JS logics. We<02:12:57.760> want<02:12:57.920> our<02:12:58.239> product<02:12:58.480> in<02:12:58.719> a<02:12:58.880> simpler<02:12:59.280> way. 02:13:00.790 --> 02:13:00.800 align:start position:0% We want our product in a simpler way. 02:13:00.800 --> 02:13:03.109 align:start position:0% We want our product in a simpler way. All<02:13:00.960> these<02:13:01.280> things<02:13:01.440> will<02:13:01.760> come<02:13:01.920> here.<02:13:02.880> The 02:13:03.109 --> 02:13:03.119 align:start position:0% All these things will come here. The 02:13:03.119 --> 02:13:05.189 align:start position:0% All these things will come here. The stack<02:13:03.520> has<02:13:03.679> arrived. 02:13:05.189 --> 02:13:05.199 align:start position:0% stack has arrived. 02:13:05.199 --> 02:13:08.550 align:start position:0% stack has arrived. What<02:13:05.520> should<02:13:05.679> a<02:13:05.840> minimal<02:13:06.239> backend<02:13:06.800> do?<02:13:08.159> We<02:13:08.400> can 02:13:08.550 --> 02:13:08.560 align:start position:0% What should a minimal backend do? We can 02:13:08.560 --> 02:13:11.510 align:start position:0% What should a minimal backend do? We can use<02:13:08.800> a<02:13:09.040> tiny<02:13:09.440> mock<02:13:09.840> API. 02:13:11.510 --> 02:13:11.520 align:start position:0% use a tiny mock API. 02:13:11.520 --> 02:13:14.950 align:start position:0% use a tiny mock API. We<02:13:11.760> can<02:13:11.920> use<02:13:12.079> a<02:13:12.400> basic<02:13:12.800> form<02:13:13.119> back<02:13:13.360> end.<02:13:14.719> We 02:13:14.950 --> 02:13:14.960 align:start position:0% We can use a basic form back end. We 02:13:14.960 --> 02:13:18.310 align:start position:0% We can use a basic form back end. We will<02:13:15.199> not<02:13:15.520> use<02:13:15.840> any<02:13:16.159> real<02:13:16.480> backend. 02:13:18.310 --> 02:13:18.320 align:start position:0% will not use any real backend. 02:13:18.320 --> 02:13:21.109 align:start position:0% will not use any real backend. How<02:13:18.480> should<02:13:18.719> the<02:13:18.880> front<02:13:19.040> end<02:13:19.360> be<02:13:19.599> structured? 02:13:21.109 --> 02:13:21.119 align:start position:0% How should the front end be structured? 02:13:21.119 --> 02:13:23.669 align:start position:0% How should the front end be structured? I<02:13:21.440> can<02:13:21.599> say<02:13:21.840> a<02:13:22.159> multi-page<02:13:22.880> application<02:13:23.440> will 02:13:23.669 --> 02:13:23.679 align:start position:0% I can say a multi-page application will 02:13:23.679 --> 02:13:25.750 align:start position:0% I can say a multi-page application will be<02:13:23.840> required<02:13:24.239> here. 02:13:25.750 --> 02:13:25.760 align:start position:0% be required here. 02:13:25.760 --> 02:13:27.589 align:start position:0% be required here. What<02:13:26.000> level<02:13:26.239> of<02:13:26.400> front-end<02:13:26.960> quality<02:13:27.360> is 02:13:27.589 --> 02:13:27.599 align:start position:0% What level of front-end quality is 02:13:27.599 --> 02:13:29.109 align:start position:0% What level of front-end quality is needed? 02:13:29.109 --> 02:13:29.119 align:start position:0% needed? 02:13:29.119 --> 02:13:32.149 align:start position:0% needed? I<02:13:29.440> will<02:13:29.599> say<02:13:30.079> we<02:13:30.320> need<02:13:30.560> a<02:13:30.800> portfolio<02:13:31.679> quality 02:13:32.149 --> 02:13:32.159 align:start position:0% I will say we need a portfolio quality 02:13:32.159 --> 02:13:34.069 align:start position:0% I will say we need a portfolio quality user<02:13:32.560> interface. 02:13:34.069 --> 02:13:34.079 align:start position:0% user interface. 02:13:34.079 --> 02:13:36.629 align:start position:0% user interface. Our<02:13:34.400> plan<02:13:34.639> is<02:13:34.880> created. 02:13:36.629 --> 02:13:36.639 align:start position:0% Our plan is created. 02:13:36.639 --> 02:13:39.109 align:start position:0% Our plan is created. You<02:13:36.880> can<02:13:37.040> see<02:13:37.199> we<02:13:37.440> have<02:13:37.599> JSo<02:13:38.400> objects<02:13:38.800> and 02:13:39.109 --> 02:13:39.119 align:start position:0% You can see we have JSo objects and 02:13:39.119 --> 02:13:42.470 align:start position:0% You can see we have JSo objects and local<02:13:39.520> storage<02:13:39.920> here.<02:13:41.360> Key<02:13:41.679> changes<02:13:42.079> are<02:13:42.320> to 02:13:42.470 --> 02:13:42.480 align:start position:0% local storage here. Key changes are to 02:13:42.480 --> 02:13:44.390 align:start position:0% local storage here. Key changes are to reframe<02:13:42.960> the<02:13:43.199> project<02:13:43.520> as<02:13:43.760> a<02:13:43.920> front-end 02:13:44.390 --> 02:13:44.400 align:start position:0% reframe the project as a front-end 02:13:44.400 --> 02:13:46.870 align:start position:0% reframe the project as a front-end prototype,<02:13:45.599> not<02:13:45.920> a<02:13:46.159> production<02:13:46.560> ready 02:13:46.870 --> 02:13:46.880 align:start position:0% prototype, not a production ready 02:13:46.880 --> 02:13:51.030 align:start position:0% prototype, not a production ready option.<02:13:48.320> Now<02:13:48.480> we<02:13:48.719> can<02:13:48.880> implement<02:13:49.280> this<02:13:49.520> plan. 02:13:51.030 --> 02:13:51.040 align:start position:0% option. Now we can implement this plan. 02:13:51.040 --> 02:13:53.270 align:start position:0% option. Now we can implement this plan. During<02:13:51.440> implementation,<02:13:52.480> it<02:13:52.719> will<02:13:52.800> bring<02:13:53.040> our 02:13:53.270 --> 02:13:53.280 align:start position:0% During implementation, it will bring our 02:13:53.280 --> 02:13:55.830 align:start position:0% During implementation, it will bring our coding.<02:13:54.400> It<02:13:54.639> is<02:13:54.800> checking<02:13:55.119> the<02:13:55.280> workspace 02:13:55.830 --> 02:13:55.840 align:start position:0% coding. It is checking the workspace 02:13:55.840 --> 02:13:58.870 align:start position:0% coding. It is checking the workspace shape.<02:13:57.040> We<02:13:57.280> will<02:13:57.440> look<02:13:57.599> at<02:13:57.840> static<02:13:58.239> app<02:13:58.560> files 02:13:58.870 --> 02:13:58.880 align:start position:0% shape. We will look at static app files 02:13:58.880 --> 02:14:01.270 align:start position:0% shape. We will look at static app files and<02:13:59.199> shared<02:13:59.599> styles<02:14:00.079> and<02:14:00.320> JavaScript<02:14:01.119> layers. 02:14:01.270 --> 02:14:01.280 align:start position:0% and shared styles and JavaScript layers. 02:14:01.280 --> 02:14:05.189 align:start position:0% and shared styles and JavaScript layers. Here<02:14:02.560> we<02:14:02.800> will<02:14:03.040> also<02:14:03.360> check<02:14:03.599> the<02:14:03.840> open<02:14:04.239> file<02:14:04.880> to 02:14:05.189 --> 02:14:05.199 align:start position:0% Here we will also check the open file to 02:14:05.199 --> 02:14:07.910 align:start position:0% Here we will also check the open file to see<02:14:05.360> what<02:14:05.599> things<02:14:05.840> are<02:14:06.079> discussed<02:14:06.400> in<02:14:06.560> it. 02:14:07.910 --> 02:14:07.920 align:start position:0% see what things are discussed in it. 02:14:07.920 --> 02:14:11.669 align:start position:0% see what things are discussed in it. First<02:14:08.239> it<02:14:08.480> took<02:14:08.880> basic<02:14:09.360> index<02:14:09.920> html. 02:14:11.669 --> 02:14:11.679 align:start position:0% First it took basic index html. 02:14:11.679 --> 02:14:14.629 align:start position:0% First it took basic index html. We<02:14:11.920> will<02:14:12.079> open<02:14:12.320> our<02:14:12.560> file<02:14:12.880> explorer.<02:14:14.239> We<02:14:14.480> will 02:14:14.629 --> 02:14:14.639 align:start position:0% We will open our file explorer. We will 02:14:14.639 --> 02:14:17.669 align:start position:0% We will open our file explorer. We will open<02:14:15.119> one<02:14:15.440> go<02:14:15.760> from<02:14:16.000> documents. 02:14:17.669 --> 02:14:17.679 align:start position:0% open one go from documents. 02:14:17.679 --> 02:14:20.310 align:start position:0% open one go from documents. For<02:14:17.920> the<02:14:18.079> time<02:14:18.320> being<02:14:19.040> we<02:14:19.280> have<02:14:19.440> no<02:14:19.760> file<02:14:20.079> or 02:14:20.310 --> 02:14:20.320 align:start position:0% For the time being we have no file or 02:14:20.320 --> 02:14:23.510 align:start position:0% For the time being we have no file or format<02:14:20.800> available<02:14:21.199> in<02:14:21.440> one<02:14:21.679> go<02:14:22.639> but<02:14:22.960> later<02:14:23.280> our 02:14:23.510 --> 02:14:23.520 align:start position:0% format available in one go but later our 02:14:23.520 --> 02:14:26.470 align:start position:0% format available in one go but later our files<02:14:23.840> will<02:14:24.079> appear.<02:14:25.280> It<02:14:25.520> has<02:14:25.679> confirmed<02:14:26.159> our 02:14:26.470 --> 02:14:26.480 align:start position:0% files will appear. It has confirmed our 02:14:26.480 --> 02:14:30.229 align:start position:0% files will appear. It has confirmed our HTML<02:14:27.199> pages<02:14:27.920> and<02:14:28.320> state<02:14:28.639> stylesheet<02:14:29.280> and<02:14:29.599> JS 02:14:30.229 --> 02:14:30.239 align:start position:0% HTML pages and state stylesheet and JS 02:14:30.239 --> 02:14:31.510 align:start position:0% HTML pages and state stylesheet and JS layer. 02:14:31.510 --> 02:14:31.520 align:start position:0% layer. 02:14:31.520 --> 02:14:33.830 align:start position:0% layer. In<02:14:31.840> plugins,<02:14:32.400> our<02:14:32.639> GitHub<02:14:33.040> is<02:14:33.280> not<02:14:33.440> installed 02:14:33.830 --> 02:14:33.840 align:start position:0% In plugins, our GitHub is not installed 02:14:33.840 --> 02:14:37.030 align:start position:0% In plugins, our GitHub is not installed yet.<02:14:34.960> I<02:14:35.199> will<02:14:35.360> go<02:14:35.520> to<02:14:35.679> our<02:14:35.920> codec<02:14:36.400> settings<02:14:36.800> to 02:14:37.030 --> 02:14:37.040 align:start position:0% yet. I will go to our codec settings to 02:14:37.040 --> 02:14:40.149 align:start position:0% yet. I will go to our codec settings to install<02:14:37.360> GitHub<02:14:37.920> once.<02:14:39.280> We<02:14:39.440> will<02:14:39.599> go<02:14:39.760> to<02:14:39.920> our 02:14:40.149 --> 02:14:40.159 align:start position:0% install GitHub once. We will go to our 02:14:40.159 --> 02:14:42.550 align:start position:0% install GitHub once. We will go to our settings.<02:14:41.360> You<02:14:41.520> can<02:14:41.679> see<02:14:41.840> our<02:14:42.079> connections 02:14:42.550 --> 02:14:42.560 align:start position:0% settings. You can see our connections 02:14:42.560 --> 02:14:45.990 align:start position:0% settings. You can see our connections here.<02:14:43.840> In<02:14:44.159> settings,<02:14:45.040> you<02:14:45.280> can<02:14:45.440> see<02:14:45.599> we<02:14:45.840> have 02:14:45.990 --> 02:14:46.000 align:start position:0% here. In settings, you can see we have 02:14:46.000 --> 02:14:47.830 align:start position:0% here. In settings, you can see we have our<02:14:46.239> connections. 02:14:47.830 --> 02:14:47.840 align:start position:0% our connections. 02:14:47.840 --> 02:14:50.550 align:start position:0% our connections. Besides<02:14:48.400> connections,<02:14:49.199> we<02:14:49.440> have<02:14:49.599> our<02:14:49.840> MCP 02:14:50.550 --> 02:14:50.560 align:start position:0% Besides connections, we have our MCP 02:14:50.560 --> 02:14:53.589 align:start position:0% Besides connections, we have our MCP servers<02:14:50.960> here<02:14:51.199> which<02:14:51.440> we<02:14:51.599> can<02:14:51.840> use.<02:14:52.960> We<02:14:53.280> also 02:14:53.589 --> 02:14:53.599 align:start position:0% servers here which we can use. We also 02:14:53.599 --> 02:14:56.790 align:start position:0% servers here which we can use. We also use<02:14:53.840> plugins<02:14:54.320> here<02:14:54.560> which<02:14:54.800> we<02:14:54.960> can<02:14:55.119> connect.<02:14:56.560> I 02:14:56.790 --> 02:14:56.800 align:start position:0% use plugins here which we can connect. I 02:14:56.800 --> 02:14:59.510 align:start position:0% use plugins here which we can connect. I will<02:14:56.880> go<02:14:57.040> to<02:14:57.199> our<02:14:57.360> plugins.<02:14:58.800> You<02:14:59.040> can<02:14:59.119> see<02:14:59.280> our 02:14:59.510 --> 02:14:59.520 align:start position:0% will go to our plugins. You can see our 02:14:59.520 --> 02:15:02.069 align:start position:0% will go to our plugins. You can see our plugins<02:14:59.920> are<02:15:00.079> available<02:15:01.360> where<02:15:01.679> all<02:15:01.840> our 02:15:02.069 --> 02:15:02.079 align:start position:0% plugins are available where all our 02:15:02.079 --> 02:15:04.229 align:start position:0% plugins are available where all our other<02:15:02.320> details<02:15:02.800> are.<02:15:03.280> We<02:15:03.520> will<02:15:03.679> include<02:15:04.000> our 02:15:04.229 --> 02:15:04.239 align:start position:0% other details are. We will include our 02:15:04.239 --> 02:15:07.430 align:start position:0% other details are. We will include our direct<02:15:04.719> option<02:15:06.000> in<02:15:06.320> configuration.<02:15:07.119> We<02:15:07.280> have 02:15:07.430 --> 02:15:07.440 align:start position:0% direct option in configuration. We have 02:15:07.440 --> 02:15:10.069 align:start position:0% direct option in configuration. We have our<02:15:07.599> plugins.<02:15:08.960> We<02:15:09.199> can<02:15:09.360> use<02:15:09.679> user 02:15:10.069 --> 02:15:10.079 align:start position:0% our plugins. We can use user 02:15:10.079 --> 02:15:11.750 align:start position:0% our plugins. We can use user configuration. 02:15:11.750 --> 02:15:11.760 align:start position:0% configuration. 02:15:11.760 --> 02:15:14.229 align:start position:0% configuration. We<02:15:12.000> have<02:15:12.159> sandbox<02:15:12.800> settings<02:15:13.520> and<02:15:13.920> current 02:15:14.229 --> 02:15:14.239 align:start position:0% We have sandbox settings and current 02:15:14.239 --> 02:15:18.069 align:start position:0% We have sandbox settings and current version<02:15:14.639> and<02:15:14.960> everything<02:15:15.280> is<02:15:15.599> working<02:15:17.040> in<02:15:17.360> MCP 02:15:18.069 --> 02:15:18.079 align:start position:0% version and everything is working in MCP 02:15:18.079 --> 02:15:20.950 align:start position:0% version and everything is working in MCP servers.<02:15:18.639> Our<02:15:18.880> plugins<02:15:19.280> have<02:15:19.520> arrived.<02:15:20.719> We 02:15:20.950 --> 02:15:20.960 align:start position:0% servers. Our plugins have arrived. We 02:15:20.960 --> 02:15:23.430 align:start position:0% servers. Our plugins have arrived. We can<02:15:21.119> also<02:15:21.520> see<02:15:21.679> our<02:15:22.000> mostused<02:15:22.560> plug-in<02:15:23.040> here 02:15:23.430 --> 02:15:23.440 align:start position:0% can also see our mostused plug-in here 02:15:23.440 --> 02:15:26.310 align:start position:0% can also see our mostused plug-in here and<02:15:23.760> how<02:15:23.920> it<02:15:24.079> is<02:15:24.320> discussed.<02:15:25.679> Then<02:15:26.000> we<02:15:26.159> have 02:15:26.310 --> 02:15:26.320 align:start position:0% and how it is discussed. Then we have 02:15:26.320 --> 02:15:29.510 align:start position:0% and how it is discussed. Then we have plugins<02:15:26.880> inside<02:15:27.199> our<02:15:27.440> hooks<02:15:28.639> and<02:15:28.960> we<02:15:29.119> have<02:15:29.199> our 02:15:29.510 --> 02:15:29.520 align:start position:0% plugins inside our hooks and we have our 02:15:29.520 --> 02:15:32.310 align:start position:0% plugins inside our hooks and we have our computer<02:15:29.920> use<02:15:30.239> plugin.<02:15:31.119> So<02:15:31.360> any<02:15:31.679> app<02:15:31.840> and<02:15:32.079> our 02:15:32.310 --> 02:15:32.320 align:start position:0% computer use plugin. So any app and our 02:15:32.320 --> 02:15:34.470 align:start position:0% computer use plugin. So any app and our Google<02:15:32.719> Chrome<02:15:33.040> browser<02:15:33.520> has<02:15:33.760> also<02:15:34.079> arrived 02:15:34.470 --> 02:15:34.480 align:start position:0% Google Chrome browser has also arrived 02:15:34.480 --> 02:15:37.350 align:start position:0% Google Chrome browser has also arrived here.<02:15:35.760> I<02:15:36.000> will<02:15:36.079> bring<02:15:36.320> our<02:15:36.480> plugins<02:15:36.880> into<02:15:37.119> our 02:15:37.350 --> 02:15:37.360 align:start position:0% here. I will bring our plugins into our 02:15:37.360 --> 02:15:40.950 align:start position:0% here. I will bring our plugins into our settings<02:15:37.760> search.<02:15:38.880> These<02:15:39.280> are<02:15:39.440> our<02:15:39.679> plugins. 02:15:40.950 --> 02:15:40.960 align:start position:0% settings search. These are our plugins. 02:15:40.960 --> 02:15:44.149 align:start position:0% settings search. These are our plugins. I<02:15:41.280> will<02:15:41.440> use<02:15:41.679> GitHub<02:15:42.159> here.<02:15:43.440> When<02:15:43.679> I<02:15:43.840> connect 02:15:44.149 --> 02:15:44.159 align:start position:0% I will use GitHub here. When I connect 02:15:44.159 --> 02:15:46.310 align:start position:0% I will use GitHub here. When I connect GitHub,<02:15:44.880> you<02:15:45.119> can<02:15:45.280> see<02:15:45.440> all<02:15:45.760> details<02:15:46.159> have 02:15:46.310 --> 02:15:46.320 align:start position:0% GitHub, you can see all details have 02:15:46.320 --> 02:15:48.229 align:start position:0% GitHub, you can see all details have arrived<02:15:46.719> here.<02:15:47.280> Because<02:15:47.440> we<02:15:47.679> are<02:15:47.840> using<02:15:48.000> the 02:15:48.229 --> 02:15:48.239 align:start position:0% arrived here. Because we are using the 02:15:48.239 --> 02:15:50.470 align:start position:0% arrived here. Because we are using the Michael<02:15:48.560> Deont<02:15:49.040> account,<02:15:49.679> we<02:15:49.920> will<02:15:50.079> bring<02:15:50.239> the 02:15:50.470 --> 02:15:50.480 align:start position:0% Michael Deont account, we will bring the 02:15:50.480 --> 02:15:53.510 align:start position:0% Michael Deont account, we will bring the same<02:15:50.719> Michael<02:15:51.040> Deont<02:15:51.520> email<02:15:51.840> here.<02:15:53.119> We<02:15:53.360> click 02:15:53.510 --> 02:15:53.520 align:start position:0% same Michael Deont email here. We click 02:15:53.520 --> 02:15:56.629 align:start position:0% same Michael Deont email here. We click on<02:15:53.760> add<02:15:54.079> plugin.<02:15:55.520> Adding<02:15:55.920> GitHub<02:15:56.480> will 02:15:56.629 --> 02:15:56.639 align:start position:0% on add plugin. Adding GitHub will 02:15:56.639 --> 02:16:00.310 align:start position:0% on add plugin. Adding GitHub will appear.<02:15:57.679> It<02:15:57.840> is<02:15:58.000> approved<02:15:58.400> by<02:15:58.560> our<02:15:58.800> admin.<02:16:00.079> We 02:16:00.310 --> 02:16:00.320 align:start position:0% appear. It is approved by our admin. We 02:16:00.320 --> 02:16:02.149 align:start position:0% appear. It is approved by our admin. We will<02:16:00.480> go<02:16:00.639> to<02:16:00.880> connect<02:16:01.280> and<02:16:01.599> continue<02:16:01.920> to 02:16:02.149 --> 02:16:02.159 align:start position:0% will go to connect and continue to 02:16:02.159 --> 02:16:03.990 align:start position:0% will go to connect and continue to GitHub. 02:16:03.990 --> 02:16:04.000 align:start position:0% GitHub. 02:16:04.000 --> 02:16:05.910 align:start position:0% GitHub. We<02:16:04.159> will<02:16:04.320> get<02:16:04.480> our<02:16:04.719> detail<02:16:05.119> in<02:16:05.280> our<02:16:05.440> browser 02:16:05.910 --> 02:16:05.920 align:start position:0% We will get our detail in our browser 02:16:05.920 --> 02:16:08.069 align:start position:0% We will get our detail in our browser which<02:16:06.159> we<02:16:06.320> will<02:16:06.560> use. 02:16:08.069 --> 02:16:08.079 align:start position:0% which we will use. 02:16:08.079 --> 02:16:09.750 align:start position:0% which we will use. You<02:16:08.320> will<02:16:08.480> see<02:16:08.560> that<02:16:08.880> GitHub<02:16:09.360> is<02:16:09.520> now 02:16:09.750 --> 02:16:09.760 align:start position:0% You will see that GitHub is now 02:16:09.760 --> 02:16:12.470 align:start position:0% You will see that GitHub is now connected.<02:16:10.960> We<02:16:11.199> can<02:16:11.280> try<02:16:11.520> it<02:16:11.679> out<02:16:11.840> in<02:16:12.000> the<02:16:12.159> chat 02:16:12.470 --> 02:16:12.480 align:start position:0% connected. We can try it out in the chat 02:16:12.480 --> 02:16:13.990 align:start position:0% connected. We can try it out in the chat too. 02:16:13.990 --> 02:16:14.000 align:start position:0% too. 02:16:14.000 --> 02:16:16.390 align:start position:0% too. In<02:16:14.239> GitHub,<02:16:14.880> we<02:16:15.119> have<02:16:15.199> our<02:16:15.440> repositories<02:16:16.079> and 02:16:16.390 --> 02:16:16.400 align:start position:0% In GitHub, we have our repositories and 02:16:16.400 --> 02:16:18.550 align:start position:0% In GitHub, we have our repositories and pull<02:16:16.639> requests<02:16:17.520> and<02:16:17.840> all<02:16:18.079> things<02:16:18.400> have 02:16:18.550 --> 02:16:18.560 align:start position:0% pull requests and all things have 02:16:18.560 --> 02:16:21.589 align:start position:0% pull requests and all things have arrived.<02:16:19.920> Our<02:16:20.159> GitHub<02:16:20.639> access<02:16:21.040> is<02:16:21.280> now 02:16:21.589 --> 02:16:21.599 align:start position:0% arrived. Our GitHub access is now 02:16:21.599 --> 02:16:22.950 align:start position:0% arrived. Our GitHub access is now connected. 02:16:22.950 --> 02:16:22.960 align:start position:0% connected. 02:16:22.960 --> 02:16:25.270 align:start position:0% connected. We<02:16:23.199> have<02:16:23.280> our<02:16:23.520> repositories<02:16:24.159> and<02:16:24.400> issues<02:16:25.040> and 02:16:25.270 --> 02:16:25.280 align:start position:0% We have our repositories and issues and 02:16:25.280 --> 02:16:28.870 align:start position:0% We have our repositories and issues and pull<02:16:25.599> requests<02:16:26.079> inside<02:16:26.400> it.<02:16:27.679> We<02:16:27.920> have<02:16:28.239> 97 02:16:28.870 --> 02:16:28.880 align:start position:0% pull requests inside it. We have 97 02:16:28.880 --> 02:16:31.109 align:start position:0% pull requests inside it. We have 97 actions<02:16:29.440> available<02:16:29.920> in<02:16:30.079> the<02:16:30.239> GitHub<02:16:30.719> app 02:16:31.109 --> 02:16:31.119 align:start position:0% actions available in the GitHub app 02:16:31.119 --> 02:16:34.549 align:start position:0% actions available in the GitHub app related<02:16:31.599> to<02:16:31.840> read<02:16:32.160> and<02:16:32.559> write.<02:16:33.840> We<02:16:34.080> can<02:16:34.160> use<02:16:34.399> it 02:16:34.549 --> 02:16:34.559 align:start position:0% related to read and write. We can use it 02:16:34.559 --> 02:16:37.190 align:start position:0% related to read and write. We can use it for<02:16:34.800> read<02:16:35.040> and<02:16:35.359> write<02:16:35.679> functions. 02:16:37.190 --> 02:16:37.200 align:start position:0% for read and write functions. 02:16:37.200 --> 02:16:39.190 align:start position:0% for read and write functions. If<02:16:37.439> we<02:16:37.599> want<02:16:37.760> to<02:16:37.920> try<02:16:38.080> it<02:16:38.240> in<02:16:38.399> the<02:16:38.479> chat,<02:16:38.880> we<02:16:39.120> can 02:16:39.190 --> 02:16:39.200 align:start position:0% If we want to try it in the chat, we can 02:16:39.200 --> 02:16:41.349 align:start position:0% If we want to try it in the chat, we can do<02:16:39.359> that<02:16:39.599> too. 02:16:41.349 --> 02:16:41.359 align:start position:0% do that too. 02:16:41.359 --> 02:16:43.190 align:start position:0% do that too. After<02:16:41.679> this,<02:16:42.080> we<02:16:42.240> go<02:16:42.399> to<02:16:42.559> our<02:16:42.719> healthcare 02:16:43.190 --> 02:16:43.200 align:start position:0% After this, we go to our healthcare 02:16:43.200 --> 02:16:44.870 align:start position:0% After this, we go to our healthcare application. 02:16:44.870 --> 02:16:44.880 align:start position:0% application. 02:16:44.880 --> 02:16:47.190 align:start position:0% application. You<02:16:45.120> will<02:16:45.280> see<02:16:45.439> that<02:16:45.599> a<02:16:45.840> total<02:16:46.160> of<02:16:46.399> nine<02:16:46.800> files 02:16:47.190 --> 02:16:47.200 align:start position:0% You will see that a total of nine files 02:16:47.200 --> 02:16:50.150 align:start position:0% You will see that a total of nine files generated<02:16:47.760> here.<02:16:49.200> You<02:16:49.439> can<02:16:49.519> see<02:16:49.679> in<02:16:49.920> these 02:16:50.150 --> 02:16:50.160 align:start position:0% generated here. You can see in these 02:16:50.160 --> 02:16:53.270 align:start position:0% generated here. You can see in these files<02:16:50.559> we<02:16:50.800> have<02:16:50.880> our<02:16:51.040> app.js.<02:16:51.439> JS.<02:16:52.639> If<02:16:52.880> I<02:16:53.040> go 02:16:53.270 --> 02:16:53.280 align:start position:0% files we have our app.js. JS. If I go 02:16:53.280 --> 02:16:55.910 align:start position:0% files we have our app.js. JS. If I go here<02:16:53.439> and<02:16:53.760> reload<02:16:54.160> it,<02:16:54.880> our<02:16:55.120> file<02:16:55.519> structure 02:16:55.910 --> 02:16:55.920 align:start position:0% here and reload it, our file structure 02:16:55.920 --> 02:16:58.790 align:start position:0% here and reload it, our file structure is<02:16:56.160> still<02:16:56.479> not<02:16:56.719> very<02:16:57.040> strong.<02:16:58.399> But<02:16:58.479> you<02:16:58.639> will 02:16:58.790 --> 02:16:58.800 align:start position:0% is still not very strong. But you will 02:16:58.800 --> 02:17:00.629 align:start position:0% is still not very strong. But you will see<02:16:58.960> that<02:16:59.200> all<02:16:59.359> our<02:16:59.599> assets<02:17:00.000> are<02:17:00.240> available 02:17:00.629 --> 02:17:00.639 align:start position:0% see that all our assets are available 02:17:00.639 --> 02:17:04.469 align:start position:0% see that all our assets are available here<02:17:01.840> index<02:17:02.319> and<02:17:02.719> records<02:17:03.760> and<02:17:04.000> all<02:17:04.240> these 02:17:04.469 --> 02:17:04.479 align:start position:0% here index and records and all these 02:17:04.479 --> 02:17:07.429 align:start position:0% here index and records and all these files<02:17:04.880> are<02:17:05.040> generated<02:17:05.519> here<02:17:05.920> overall. 02:17:07.429 --> 02:17:07.439 align:start position:0% files are generated here overall. 02:17:07.439 --> 02:17:09.429 align:start position:0% files are generated here overall. Now<02:17:07.760> it<02:17:08.000> also<02:17:08.319> told<02:17:08.559> us<02:17:08.800> it<02:17:09.040> found<02:17:09.200> a 02:17:09.429 --> 02:17:09.439 align:start position:0% Now it also told us it found a 02:17:09.439 --> 02:17:12.549 align:start position:0% Now it also told us it found a portability<02:17:10.080> issue<02:17:10.399> in<02:17:10.559> the<02:17:10.719> static<02:17:11.120> assets. 02:17:12.549 --> 02:17:12.559 align:start position:0% portability issue in the static assets. 02:17:12.559 --> 02:17:15.110 align:start position:0% portability issue in the static assets. A<02:17:12.800> few<02:17:13.120> non-ASKY<02:17:14.000> characters<02:17:14.479> slipped<02:17:14.880> into 02:17:15.110 --> 02:17:15.120 align:start position:0% A few non-ASKY characters slipped into 02:17:15.120 --> 02:17:18.309 align:start position:0% A few non-ASKY characters slipped into the<02:17:15.280> labels.<02:17:16.479> It<02:17:16.639> will<02:17:16.800> run<02:17:17.040> them.<02:17:18.080> The 02:17:18.309 --> 02:17:18.319 align:start position:0% the labels. It will run them. The 02:17:18.319 --> 02:17:21.190 align:start position:0% the labels. It will run them. The command<02:17:18.639> is<02:17:18.880> normalized.<02:17:20.240> I<02:17:20.479> am<02:17:20.639> loading<02:17:20.960> the 02:17:21.190 --> 02:17:21.200 align:start position:0% command is normalized. I am loading the 02:17:21.200 --> 02:17:23.349 align:start position:0% command is normalized. I am loading the normal<02:17:21.519> browser. 02:17:23.349 --> 02:17:23.359 align:start position:0% normal browser. 02:17:23.359 --> 02:17:25.509 align:start position:0% normal browser. Now<02:17:23.599> we<02:17:23.760> will<02:17:24.000> connect<02:17:24.319> things<02:17:24.559> in<02:17:24.800> our<02:17:24.960> inapp 02:17:25.509 --> 02:17:25.519 align:start position:0% Now we will connect things in our inapp 02:17:25.519 --> 02:17:28.389 align:start position:0% Now we will connect things in our inapp browser.<02:17:26.880> You<02:17:27.040> will<02:17:27.200> see<02:17:27.439> I<02:17:27.679> did<02:17:27.840> not<02:17:28.000> give<02:17:28.160> any 02:17:28.389 --> 02:17:28.399 align:start position:0% browser. You will see I did not give any 02:17:28.399 --> 02:17:31.429 align:start position:0% browser. You will see I did not give any prompt.<02:17:29.679> I<02:17:29.920> did<02:17:30.080> not<02:17:30.240> give<02:17:30.479> any<02:17:30.719> prompt<02:17:31.040> on<02:17:31.280> a 02:17:31.429 --> 02:17:31.439 align:start position:0% prompt. I did not give any prompt on a 02:17:31.439 --> 02:17:34.309 align:start position:0% prompt. I did not give any prompt on a large<02:17:31.760> scale.<02:17:32.800> I<02:17:33.040> gave<02:17:33.280> a<02:17:33.439> basic<02:17:33.840> prompt<02:17:34.080> that 02:17:34.309 --> 02:17:34.319 align:start position:0% large scale. I gave a basic prompt that 02:17:34.319 --> 02:17:36.870 align:start position:0% large scale. I gave a basic prompt that I<02:17:34.479> need<02:17:34.639> a<02:17:34.800> healthcare<02:17:35.200> application. 02:17:36.870 --> 02:17:36.880 align:start position:0% I need a healthcare application. 02:17:36.880 --> 02:17:38.950 align:start position:0% I need a healthcare application. It<02:17:37.120> planned<02:17:37.519> it<02:17:37.840> and<02:17:38.080> took<02:17:38.399> multiple 02:17:38.950 --> 02:17:38.960 align:start position:0% It planned it and took multiple 02:17:38.960 --> 02:17:41.910 align:start position:0% It planned it and took multiple recommendations<02:17:39.679> from<02:17:39.920> me<02:17:40.160> during<02:17:40.479> planning. 02:17:41.910 --> 02:17:41.920 align:start position:0% recommendations from me during planning. 02:17:41.920 --> 02:17:44.230 align:start position:0% recommendations from me during planning. In<02:17:42.160> the<02:17:42.319> end,<02:17:42.559> it<02:17:42.800> generated<02:17:43.359> all<02:17:43.599> our<02:17:43.840> assets 02:17:44.230 --> 02:17:44.240 align:start position:0% In the end, it generated all our assets 02:17:44.240 --> 02:17:47.509 align:start position:0% In the end, it generated all our assets in<02:17:44.559> one<02:17:44.800> go.<02:17:46.000> Appointments<02:17:46.559> and<02:17:46.800> dashboard 02:17:47.509 --> 02:17:47.519 align:start position:0% in one go. Appointments and dashboard 02:17:47.519 --> 02:17:49.990 align:start position:0% in one go. Appointments and dashboard and<02:17:47.840> doctors<02:17:48.399> and<02:17:48.559> index<02:17:49.040> and<02:17:49.280> record<02:17:49.679> files 02:17:49.990 --> 02:17:50.000 align:start position:0% and doctors and index and record files 02:17:50.000 --> 02:17:51.830 align:start position:0% and doctors and index and record files are<02:17:50.160> generated. 02:17:51.830 --> 02:17:51.840 align:start position:0% are generated. 02:17:51.840 --> 02:17:55.110 align:start position:0% are generated. Now<02:17:52.160> browser<02:17:52.639> automation<02:17:53.200> has<02:17:53.439> also<02:17:53.840> arrived. 02:17:55.110 --> 02:17:55.120 align:start position:0% Now browser automation has also arrived. 02:17:55.120 --> 02:17:57.669 align:start position:0% Now browser automation has also arrived. We<02:17:55.359> have<02:17:55.519> all<02:17:55.840> files<02:17:56.160> for<02:17:56.399> implementation<02:17:57.439> and 02:17:57.669 --> 02:17:57.679 align:start position:0% We have all files for implementation and 02:17:57.679 --> 02:18:00.070 align:start position:0% We have all files for implementation and we<02:17:57.840> can<02:17:58.000> run<02:17:58.240> prototypes. 02:18:00.070 --> 02:18:00.080 align:start position:0% we can run prototypes. 02:18:00.080 --> 02:18:02.309 align:start position:0% we can run prototypes. Here<02:18:00.319> is<02:18:00.479> our<02:18:00.719> documentation. 02:18:02.309 --> 02:18:02.319 align:start position:0% Here is our documentation. 02:18:02.319 --> 02:18:04.709 align:start position:0% Here is our documentation. Now<02:18:02.639> if<02:18:02.800> I<02:18:02.960> open<02:18:03.200> our<02:18:03.439> file<02:18:03.760> explorer<02:18:04.319> and<02:18:04.559> go 02:18:04.709 --> 02:18:04.719 align:start position:0% Now if I open our file explorer and go 02:18:04.719 --> 02:18:07.990 align:start position:0% Now if I open our file explorer and go to<02:18:04.960> documents<02:18:05.760> and<02:18:06.080> one<02:18:06.399> go<02:18:07.200> our<02:18:07.439> folder<02:18:07.840> is 02:18:07.990 --> 02:18:08.000 align:start position:0% to documents and one go our folder is 02:18:08.000 --> 02:18:10.629 align:start position:0% to documents and one go our folder is empty<02:18:08.319> right<02:18:08.639> now.<02:18:09.599> But<02:18:09.840> if<02:18:10.000> I<02:18:10.160> look<02:18:10.240> at<02:18:10.399> our 02:18:10.629 --> 02:18:10.639 align:start position:0% empty right now. But if I look at our 02:18:10.639 --> 02:18:13.830 align:start position:0% empty right now. But if I look at our index<02:18:11.120> html<02:18:12.000> here<02:18:12.160> in<02:18:12.399> the<02:18:12.559> file<02:18:12.800> explorer, 02:18:13.830 --> 02:18:13.840 align:start position:0% index html here in the file explorer, 02:18:13.840 --> 02:18:15.270 align:start position:0% index html here in the file explorer, you<02:18:14.080> will<02:18:14.240> see<02:18:14.319> that<02:18:14.559> we<02:18:14.719> have<02:18:14.800> a<02:18:15.040> file 02:18:15.270 --> 02:18:15.280 align:start position:0% you will see that we have a file 02:18:15.280 --> 02:18:16.870 align:start position:0% you will see that we have a file available. 02:18:16.870 --> 02:18:16.880 align:start position:0% available. 02:18:16.880 --> 02:18:19.349 align:start position:0% available. If<02:18:17.120> I<02:18:17.280> open<02:18:17.519> this<02:18:17.760> file<02:18:18.000> in<02:18:18.160> our<02:18:18.319> browser,<02:18:19.200> you 02:18:19.349 --> 02:18:19.359 align:start position:0% If I open this file in our browser, you 02:18:19.359 --> 02:18:22.070 align:start position:0% If I open this file in our browser, you will<02:18:19.519> see<02:18:19.760> our<02:18:20.000> project<02:18:20.319> has<02:18:20.559> arrived.<02:18:21.760> It<02:18:22.000> is 02:18:22.070 --> 02:18:22.080 align:start position:0% will see our project has arrived. It is 02:18:22.080 --> 02:18:24.629 align:start position:0% will see our project has arrived. It is a<02:18:22.240> healthcare<02:18:22.800> app<02:18:23.120> prototype. 02:18:24.629 --> 02:18:24.639 align:start position:0% a healthcare app prototype. 02:18:24.639 --> 02:18:26.549 align:start position:0% a healthcare app prototype. We<02:18:24.880> are<02:18:25.040> accessing<02:18:25.599> healthcare<02:18:26.080> here<02:18:26.319> with 02:18:26.549 --> 02:18:26.559 align:start position:0% We are accessing healthcare here with 02:18:26.559 --> 02:18:29.589 align:start position:0% We are accessing healthcare here with appointments<02:18:27.040> and<02:18:27.359> records<02:18:27.760> and<02:18:28.000> reminders. 02:18:29.589 --> 02:18:29.599 align:start position:0% appointments and records and reminders. 02:18:29.599 --> 02:18:31.429 align:start position:0% appointments and records and reminders. When<02:18:29.840> we<02:18:30.080> want<02:18:30.160> to<02:18:30.319> enter<02:18:30.559> a<02:18:30.719> dashboard,<02:18:31.280> we 02:18:31.429 --> 02:18:31.439 align:start position:0% When we want to enter a dashboard, we 02:18:31.439 --> 02:18:33.990 align:start position:0% When we want to enter a dashboard, we sign<02:18:31.679> in<02:18:31.920> here.<02:18:32.960> Our<02:18:33.200> doctors<02:18:33.599> have<02:18:33.760> arrived 02:18:33.990 --> 02:18:34.000 align:start position:0% sign in here. Our doctors have arrived 02:18:34.000 --> 02:18:36.870 align:start position:0% sign in here. Our doctors have arrived in<02:18:34.240> it.<02:18:35.280> After<02:18:35.679> doctors,<02:18:36.160> our<02:18:36.479> appointments 02:18:36.870 --> 02:18:36.880 align:start position:0% in it. After doctors, our appointments 02:18:36.880 --> 02:18:39.110 align:start position:0% in it. After doctors, our appointments have<02:18:37.120> arrived<02:18:38.000> and<02:18:38.319> our<02:18:38.559> records<02:18:38.960> have 02:18:39.110 --> 02:18:39.120 align:start position:0% have arrived and our records have 02:18:39.120 --> 02:18:42.150 align:start position:0% have arrived and our records have arrived.<02:18:40.479> This<02:18:40.719> is<02:18:40.880> our<02:18:41.120> whole<02:18:41.439> process<02:18:42.000> as 02:18:42.150 --> 02:18:42.160 align:start position:0% arrived. This is our whole process as 02:18:42.160 --> 02:18:45.509 align:start position:0% arrived. This is our whole process as you<02:18:42.399> can<02:18:42.479> see.<02:18:43.840> If<02:18:44.080> we<02:18:44.319> want<02:18:44.639> we<02:18:44.880> can<02:18:45.040> confirm 02:18:45.509 --> 02:18:45.519 align:start position:0% you can see. If we want we can confirm 02:18:45.519 --> 02:18:48.150 align:start position:0% you can see. If we want we can confirm any<02:18:45.840> other<02:18:46.160> appointment<02:18:46.639> too.<02:18:47.760> I<02:18:48.000> will 02:18:48.150 --> 02:18:48.160 align:start position:0% any other appointment too. I will 02:18:48.160 --> 02:18:50.950 align:start position:0% any other appointment too. I will confirm<02:18:48.559> an<02:18:48.800> appointment.<02:18:50.080> I<02:18:50.319> will<02:18:50.479> say<02:18:50.719> I 02:18:50.950 --> 02:18:50.960 align:start position:0% confirm an appointment. I will say I 02:18:50.960 --> 02:18:53.750 align:start position:0% confirm an appointment. I will say I have<02:18:51.040> a<02:18:51.200> heart<02:18:51.439> pain.<02:18:52.479> I<02:18:52.719> will<02:18:52.960> just<02:18:53.200> include<02:18:53.519> a 02:18:53.750 --> 02:18:53.760 align:start position:0% have a heart pain. I will just include a 02:18:53.760 --> 02:18:56.230 align:start position:0% have a heart pain. I will just include a reason.<02:18:54.559> When<02:18:54.800> we<02:18:54.960> include<02:18:55.280> this<02:18:55.519> part,<02:18:55.920> our 02:18:56.230 --> 02:18:56.240 align:start position:0% reason. When we include this part, our 02:18:56.240 --> 02:18:58.709 align:start position:0% reason. When we include this part, our second<02:18:56.479> appointment<02:18:56.880> will<02:18:57.120> come.<02:18:58.160> This<02:18:58.479> means 02:18:58.709 --> 02:18:58.719 align:start position:0% second appointment will come. This means 02:18:58.719 --> 02:19:01.509 align:start position:0% second appointment will come. This means our<02:18:58.960> page<02:18:59.200> is<02:18:59.439> loading.<02:19:00.800> If<02:19:01.040> we<02:19:01.120> go<02:19:01.280> to 02:19:01.509 --> 02:19:01.519 align:start position:0% our page is loading. If we go to 02:19:01.519 --> 02:19:03.429 align:start position:0% our page is loading. If we go to records,<02:19:02.000> we<02:19:02.160> have<02:19:02.319> our<02:19:02.559> medications<02:19:03.200> and 02:19:03.429 --> 02:19:03.439 align:start position:0% records, we have our medications and 02:19:03.439 --> 02:19:06.870 align:start position:0% records, we have our medications and allergies<02:19:04.240> and<02:19:04.559> recent<02:19:04.960> visits<02:19:05.359> available. 02:19:06.870 --> 02:19:06.880 align:start position:0% allergies and recent visits available. 02:19:06.880 --> 02:19:09.750 align:start position:0% allergies and recent visits available. If<02:19:07.120> we<02:19:07.280> go<02:19:07.359> to<02:19:07.599> doctors,<02:19:08.639> all<02:19:08.960> doctors<02:19:09.359> we<02:19:09.599> have 02:19:09.750 --> 02:19:09.760 align:start position:0% If we go to doctors, all doctors we have 02:19:09.760 --> 02:19:12.309 align:start position:0% If we go to doctors, all doctors we have are<02:19:09.920> listed<02:19:10.319> here.<02:19:11.519> Then<02:19:11.760> comes<02:19:12.080> our 02:19:12.309 --> 02:19:12.319 align:start position:0% are listed here. Then comes our 02:19:12.319 --> 02:19:13.910 align:start position:0% are listed here. Then comes our dashboard. 02:19:13.910 --> 02:19:13.920 align:start position:0% dashboard. 02:19:13.920 --> 02:19:15.750 align:start position:0% dashboard. Inside<02:19:14.319> this<02:19:14.559> dashboard,<02:19:15.200> we<02:19:15.359> have<02:19:15.519> our 02:19:15.750 --> 02:19:15.760 align:start position:0% Inside this dashboard, we have our 02:19:15.760 --> 02:19:17.990 align:start position:0% Inside this dashboard, we have our current<02:19:16.080> summary<02:19:16.880> showing<02:19:17.200> the<02:19:17.439> plan<02:19:17.679> and 02:19:17.990 --> 02:19:18.000 align:start position:0% current summary showing the plan and 02:19:18.000 --> 02:19:20.709 align:start position:0% current summary showing the plan and conditions<02:19:18.479> and<02:19:18.800> recent<02:19:19.120> visits.<02:19:20.399> Our 02:19:20.709 --> 02:19:20.719 align:start position:0% conditions and recent visits. Our 02:19:20.719 --> 02:19:23.110 align:start position:0% conditions and recent visits. Our insurance<02:19:21.200> card<02:19:21.439> and<02:19:21.760> hydration<02:19:22.319> reminder 02:19:23.110 --> 02:19:23.120 align:start position:0% insurance card and hydration reminder 02:19:23.120 --> 02:19:26.389 align:start position:0% insurance card and hydration reminder and<02:19:23.359> medication<02:19:24.000> review<02:19:24.399> are<02:19:24.639> all<02:19:24.880> available. 02:19:26.389 --> 02:19:26.399 align:start position:0% and medication review are all available. 02:19:26.399 --> 02:19:28.469 align:start position:0% and medication review are all available. Active<02:19:26.719> members<02:19:27.120> and<02:19:27.439> unwanted<02:19:28.000> things<02:19:28.240> are 02:19:28.469 --> 02:19:28.479 align:start position:0% Active members and unwanted things are 02:19:28.479 --> 02:19:30.309 align:start position:0% Active members and unwanted things are available<02:19:28.880> here. 02:19:30.309 --> 02:19:30.319 align:start position:0% available here. 02:19:30.319 --> 02:19:32.389 align:start position:0% available here. If<02:19:30.559> we<02:19:30.800> want,<02:19:31.040> we<02:19:31.280> can<02:19:31.439> build<02:19:31.599> a<02:19:31.840> new<02:19:32.000> demo 02:19:32.389 --> 02:19:32.399 align:start position:0% If we want, we can build a new demo 02:19:32.399 --> 02:19:35.110 align:start position:0% If we want, we can build a new demo account<02:19:32.719> instead<02:19:33.040> of<02:19:33.200> demo<02:19:33.519> credentials.<02:19:34.880> I 02:19:35.110 --> 02:19:35.120 align:start position:0% account instead of demo credentials. I 02:19:35.120 --> 02:19:37.589 align:start position:0% account instead of demo credentials. I will<02:19:35.280> close<02:19:35.599> this<02:19:35.840> one.<02:19:36.960> I<02:19:37.200> will<02:19:37.280> give<02:19:37.439> a 02:19:37.589 --> 02:19:37.599 align:start position:0% will close this one. I will give a 02:19:37.599 --> 02:19:40.709 align:start position:0% will close this one. I will give a prompt<02:19:38.000> here.<02:19:39.120> I<02:19:39.359> liked<02:19:39.679> my<02:19:39.920> first<02:19:40.160> draft<02:19:40.479> and 02:19:40.709 --> 02:19:40.719 align:start position:0% prompt here. I liked my first draft and 02:19:40.719 --> 02:19:42.549 align:start position:0% prompt here. I liked my first draft and I<02:19:40.960> want<02:19:41.040> to<02:19:41.200> make<02:19:41.359> this<02:19:41.519> an<02:19:41.760> official<02:19:42.160> app<02:19:42.399> for 02:19:42.549 --> 02:19:42.559 align:start position:0% I want to make this an official app for 02:19:42.559 --> 02:19:45.190 align:start position:0% I want to make this an official app for the<02:19:42.800> patients.<02:19:44.160> Add<02:19:44.399> some<02:19:44.639> vibrant 02:19:45.190 --> 02:19:45.200 align:start position:0% the patients. Add some vibrant 02:19:45.200 --> 02:19:48.150 align:start position:0% the patients. Add some vibrant health-based<02:19:45.840> colors<02:19:46.160> in<02:19:46.319> the<02:19:46.559> website.<02:19:47.679> Also 02:19:48.150 --> 02:19:48.160 align:start position:0% health-based colors in the website. Also 02:19:48.160 --> 02:19:50.230 align:start position:0% health-based colors in the website. Also try<02:19:48.319> to<02:19:48.479> make<02:19:48.640> it<02:19:48.800> more<02:19:49.040> real.<02:19:49.439> Our<02:19:49.760> prototype 02:19:50.230 --> 02:19:50.240 align:start position:0% try to make it more real. Our prototype 02:19:50.240 --> 02:19:53.190 align:start position:0% try to make it more real. Our prototype is<02:19:50.479> very<02:19:50.720> much<02:19:50.960> liked.<02:19:52.080> In<02:19:52.319> the<02:19:52.560> prototype, 02:19:53.190 --> 02:19:53.200 align:start position:0% is very much liked. In the prototype, 02:19:53.200 --> 02:19:56.070 align:start position:0% is very much liked. In the prototype, our<02:19:53.439> login<02:19:53.840> and<02:19:54.080> doctors<02:19:54.479> are<02:19:54.640> very<02:19:54.960> real.<02:19:55.920> But 02:19:56.070 --> 02:19:56.080 align:start position:0% our login and doctors are very real. But 02:19:56.080 --> 02:19:58.710 align:start position:0% our login and doctors are very real. But this<02:19:56.240> dashboard<02:19:56.720> has<02:19:56.960> some<02:19:57.120> issues.<02:19:58.399> When<02:19:58.560> I 02:19:58.710 --> 02:19:58.720 align:start position:0% this dashboard has some issues. When I 02:19:58.720 --> 02:20:00.550 align:start position:0% this dashboard has some issues. When I bring<02:19:58.880> it<02:19:58.960> to<02:19:59.120> the<02:19:59.280> phone<02:19:59.520> view,<02:19:59.920> it<02:20:00.160> does<02:20:00.319> not 02:20:00.550 --> 02:20:00.560 align:start position:0% bring it to the phone view, it does not 02:20:00.560 --> 02:20:03.990 align:start position:0% bring it to the phone view, it does not look<02:20:00.800> special.<02:20:01.840> It<02:20:02.000> has<02:20:02.240> many<02:20:02.560> issues.<02:20:03.760> This 02:20:03.990 --> 02:20:04.000 align:start position:0% look special. It has many issues. This 02:20:04.000 --> 02:20:06.950 align:start position:0% look special. It has many issues. This dashboard<02:20:04.560> does<02:20:04.800> not<02:20:04.960> go<02:20:05.200> higher<02:20:05.520> from<02:20:05.680> here. 02:20:06.950 --> 02:20:06.960 align:start position:0% dashboard does not go higher from here. 02:20:06.960 --> 02:20:09.110 align:start position:0% dashboard does not go higher from here. The<02:20:07.200> second<02:20:07.520> thing<02:20:07.680> is<02:20:07.920> our<02:20:08.080> login<02:20:08.479> panel<02:20:08.800> goes 02:20:09.110 --> 02:20:09.120 align:start position:0% The second thing is our login panel goes 02:20:09.120 --> 02:20:11.910 align:start position:0% The second thing is our login panel goes too<02:20:09.359> far<02:20:09.600> back.<02:20:10.640> If<02:20:10.880> we<02:20:11.040> go<02:20:11.120> to<02:20:11.280> our<02:20:11.520> network 02:20:11.910 --> 02:20:11.920 align:start position:0% too far back. If we go to our network 02:20:11.920 --> 02:20:14.230 align:start position:0% too far back. If we go to our network inside<02:20:12.240> the<02:20:12.479> console,<02:20:13.280> nothing<02:20:13.680> special<02:20:14.000> is 02:20:14.230 --> 02:20:14.240 align:start position:0% inside the console, nothing special is 02:20:14.240 --> 02:20:18.230 align:start position:0% inside the console, nothing special is loading.<02:20:15.680> This<02:20:15.920> means<02:20:16.160> we<02:20:16.399> have<02:20:16.640> no<02:20:16.880> back<02:20:17.200> end. 02:20:18.230 --> 02:20:18.240 align:start position:0% loading. This means we have no back end. 02:20:18.240 --> 02:20:21.590 align:start position:0% loading. This means we have no back end. It<02:20:18.479> created<02:20:18.800> a<02:20:19.040> working<02:20:19.359> front<02:20:19.600> end<02:20:19.840> for<02:20:20.080> us.<02:20:21.359> I 02:20:21.590 --> 02:20:21.600 align:start position:0% It created a working front end for us. I 02:20:21.600 --> 02:20:23.270 align:start position:0% It created a working front end for us. I have<02:20:21.760> given<02:20:22.000> a<02:20:22.160> prompt<02:20:22.479> to<02:20:22.640> update<02:20:23.040> our 02:20:23.270 --> 02:20:23.280 align:start position:0% have given a prompt to update our 02:20:23.280 --> 02:20:26.070 align:start position:0% have given a prompt to update our prototype.<02:20:24.720> You<02:20:24.960> see<02:20:25.120> we<02:20:25.359> have<02:20:25.520> our<02:20:25.680> browser 02:20:26.070 --> 02:20:26.080 align:start position:0% prototype. You see we have our browser 02:20:26.080 --> 02:20:28.950 align:start position:0% prototype. You see we have our browser available<02:20:26.399> in<02:20:26.640> plugins.<02:20:28.000> Due<02:20:28.160> to<02:20:28.319> this<02:20:28.560> we<02:20:28.800> can 02:20:28.950 --> 02:20:28.960 align:start position:0% available in plugins. Due to this we can 02:20:28.960 --> 02:20:31.590 align:start position:0% available in plugins. Due to this we can use<02:20:29.120> it.<02:20:30.080> It<02:20:30.319> says<02:20:30.640> I<02:20:30.800> am<02:20:30.960> updating<02:20:31.439> the 02:20:31.590 --> 02:20:31.600 align:start position:0% use it. It says I am updating the 02:20:31.600 --> 02:20:33.510 align:start position:0% use it. It says I am updating the prototype. 02:20:33.510 --> 02:20:33.520 align:start position:0% prototype. 02:20:33.520 --> 02:20:35.670 align:start position:0% prototype. It<02:20:33.760> is<02:20:33.920> updating<02:20:34.319> the<02:20:34.560> prototype<02:20:35.120> towards<02:20:35.439> a 02:20:35.670 --> 02:20:35.680 align:start position:0% It is updating the prototype towards a 02:20:35.680 --> 02:20:39.110 align:start position:0% It is updating the prototype towards a more<02:20:35.920> launch<02:20:36.479> oriented<02:20:36.960> Alaska<02:20:37.439> patient<02:20:37.840> app. 02:20:39.110 --> 02:20:39.120 align:start position:0% more launch oriented Alaska patient app. 02:20:39.120 --> 02:20:40.870 align:start position:0% more launch oriented Alaska patient app. First<02:20:39.520> I<02:20:39.760> am<02:20:39.920> verifying<02:20:40.399> the<02:20:40.640> current 02:20:40.870 --> 02:20:40.880 align:start position:0% First I am verifying the current 02:20:40.880 --> 02:20:43.830 align:start position:0% First I am verifying the current frontend<02:20:41.439> structure.<02:20:42.800> Then<02:20:43.120> I<02:20:43.359> will<02:20:43.520> replace 02:20:43.830 --> 02:20:43.840 align:start position:0% frontend structure. Then I will replace 02:20:43.840 --> 02:20:46.070 align:start position:0% frontend structure. Then I will replace the<02:20:44.000> mock<02:20:44.399> positioning<02:20:44.880> with<02:20:45.200> real<02:20:45.520> Alaska 02:20:46.070 --> 02:20:46.080 align:start position:0% the mock positioning with real Alaska 02:20:46.080 --> 02:20:49.030 align:start position:0% the mock positioning with real Alaska provider<02:20:46.560> data.<02:20:48.000> It<02:20:48.160> will<02:20:48.319> shift<02:20:48.560> the<02:20:48.800> design 02:20:49.030 --> 02:20:49.040 align:start position:0% provider data. It will shift the design 02:20:49.040 --> 02:20:51.030 align:start position:0% provider data. It will shift the design towards<02:20:49.439> a<02:20:49.680> premium<02:20:50.240> Apple<02:20:50.560> adjacent 02:20:51.030 --> 02:20:51.040 align:start position:0% towards a premium Apple adjacent 02:20:51.040 --> 02:20:53.510 align:start position:0% towards a premium Apple adjacent aesthetic<02:20:52.000> without<02:20:52.399> copying<02:20:52.880> Apple<02:20:53.280> owned 02:20:53.510 --> 02:20:53.520 align:start position:0% aesthetic without copying Apple owned 02:20:53.520 --> 02:20:56.230 align:start position:0% aesthetic without copying Apple owned logos<02:20:53.840> or<02:20:54.160> icons<02:20:55.200> because<02:20:55.520> we<02:20:55.760> cannot<02:20:56.000> copy 02:20:56.230 --> 02:20:56.240 align:start position:0% logos or icons because we cannot copy 02:20:56.240 --> 02:20:59.349 align:start position:0% logos or icons because we cannot copy the<02:20:56.560> icons.<02:20:57.680> But<02:20:57.840> if<02:20:58.080> we<02:20:58.240> want<02:20:58.720> we<02:20:58.880> can<02:20:59.040> copy 02:20:59.349 --> 02:20:59.359 align:start position:0% the icons. But if we want we can copy 02:20:59.359 --> 02:21:02.389 align:start position:0% the icons. But if we want we can copy aesthetics<02:21:00.000> based<02:21:00.319> on<02:21:00.479> an<02:21:00.720> ecosystem<02:21:01.920> and<02:21:02.160> we 02:21:02.389 --> 02:21:02.399 align:start position:0% aesthetics based on an ecosystem and we 02:21:02.399 --> 02:21:04.950 align:start position:0% aesthetics based on an ecosystem and we are<02:21:02.560> going<02:21:02.720> to<02:21:02.880> do<02:21:02.960> the<02:21:03.200> same<02:21:03.359> thing<02:21:03.600> here. 02:21:04.950 --> 02:21:04.960 align:start position:0% are going to do the same thing here. 02:21:04.960 --> 02:21:07.910 align:start position:0% are going to do the same thing here. This<02:21:05.200> thing<02:21:05.439> will<02:21:05.680> be<02:21:05.760> induced<02:21:06.319> here<02:21:07.600> in 02:21:07.910 --> 02:21:07.920 align:start position:0% This thing will be induced here in 02:21:07.920 --> 02:21:11.030 align:start position:0% This thing will be induced here in styles.<02:21:08.479> You<02:21:08.640> see<02:21:08.800> we<02:21:09.040> have<02:21:09.200> many<02:21:09.600> changes.<02:21:10.880> It 02:21:11.030 --> 02:21:11.040 align:start position:0% styles. You see we have many changes. It 02:21:11.040 --> 02:21:12.950 align:start position:0% styles. You see we have many changes. It is<02:21:11.200> performing<02:21:11.680> enhancements<02:21:12.240> in<02:21:12.479> our<02:21:12.640> file. 02:21:12.950 --> 02:21:12.960 align:start position:0% is performing enhancements in our file. 02:21:12.960 --> 02:21:15.750 align:start position:0% is performing enhancements in our file. Overall,<02:21:14.240> I<02:21:14.479> have<02:21:14.640> included<02:21:15.120> one<02:21:15.439> thing<02:21:15.600> in 02:21:15.750 --> 02:21:15.760 align:start position:0% Overall, I have included one thing in 02:21:15.760 --> 02:21:18.790 align:start position:0% Overall, I have included one thing in the<02:21:16.000> one<02:21:16.240> go<02:21:16.560> project.<02:21:17.760> I<02:21:18.080> want<02:21:18.160> to<02:21:18.319> run<02:21:18.560> the 02:21:18.790 --> 02:21:18.800 align:start position:0% the one go project. I want to run the 02:21:18.800 --> 02:21:22.309 align:start position:0% the one go project. I want to run the Apple<02:21:19.120> ecosystem<02:21:19.840> here.<02:21:21.120> Apple<02:21:21.439> ecosystem 02:21:22.309 --> 02:21:22.319 align:start position:0% Apple ecosystem here. Apple ecosystem 02:21:22.319 --> 02:21:24.550 align:start position:0% Apple ecosystem here. Apple ecosystem means<02:21:22.640> the<02:21:22.880> user<02:21:23.200> interface<02:21:23.680> enhancements<02:21:24.319> in 02:21:24.550 --> 02:21:24.560 align:start position:0% means the user interface enhancements in 02:21:24.560 --> 02:21:27.750 align:start position:0% means the user interface enhancements in our<02:21:24.800> MacBook<02:21:25.280> or<02:21:25.600> iPhones.<02:21:26.880> I<02:21:27.120> want<02:21:27.280> to<02:21:27.439> adapt 02:21:27.750 --> 02:21:27.760 align:start position:0% our MacBook or iPhones. I want to adapt 02:21:27.760 --> 02:21:30.309 align:start position:0% our MacBook or iPhones. I want to adapt them<02:21:27.920> in<02:21:28.080> our<02:21:28.319> project.<02:21:29.680> All<02:21:29.920> those<02:21:30.160> things 02:21:30.309 --> 02:21:30.319 align:start position:0% them in our project. All those things 02:21:30.319 --> 02:21:32.950 align:start position:0% them in our project. All those things are<02:21:30.560> happening<02:21:30.880> here.<02:21:32.080> You<02:21:32.319> see<02:21:32.479> what<02:21:32.640> it<02:21:32.800> is 02:21:32.950 --> 02:21:32.960 align:start position:0% are happening here. You see what it is 02:21:32.960 --> 02:21:35.590 align:start position:0% are happening here. You see what it is doing.<02:21:33.280> First,<02:21:34.240> I<02:21:34.560> gave<02:21:34.800> this<02:21:35.040> information 02:21:35.590 --> 02:21:35.600 align:start position:0% doing. First, I gave this information 02:21:35.600 --> 02:21:38.710 align:start position:0% doing. First, I gave this information here.<02:21:36.800> Use<02:21:37.200> real<02:21:37.600> doctor<02:21:38.000> information<02:21:38.479> from 02:21:38.710 --> 02:21:38.720 align:start position:0% here. Use real doctor information from 02:21:38.720 --> 02:21:42.710 align:start position:0% here. Use real doctor information from Alaska.<02:21:40.080> I<02:21:40.399> want<02:21:40.560> to<02:21:40.720> launch<02:21:40.960> it.<02:21:41.200> There<02:21:42.240> it<02:21:42.560> is 02:21:42.710 --> 02:21:42.720 align:start position:0% Alaska. I want to launch it. There it is 02:21:42.720 --> 02:21:44.790 align:start position:0% Alaska. I want to launch it. There it is taking<02:21:43.040> Alaska<02:21:43.600> doctor<02:21:43.920> profiles<02:21:44.479> from<02:21:44.640> the 02:21:44.790 --> 02:21:44.800 align:start position:0% taking Alaska doctor profiles from the 02:21:44.800 --> 02:21:49.030 align:start position:0% taking Alaska doctor profiles from the list.<02:21:46.160> First<02:21:46.479> it<02:21:46.800> read<02:21:47.120> all<02:21:47.280> our<02:21:47.520> files.<02:21:48.800> Then 02:21:49.030 --> 02:21:49.040 align:start position:0% list. First it read all our files. Then 02:21:49.040 --> 02:21:52.630 align:start position:0% list. First it read all our files. Then it<02:21:49.359> understood<02:21:49.920> index.js<02:21:50.880> file.<02:21:52.080> Then<02:21:52.399> it 02:21:52.630 --> 02:21:52.640 align:start position:0% it understood index.js file. Then it 02:21:52.640 --> 02:21:55.910 align:start position:0% it understood index.js file. Then it understood<02:21:53.200> all<02:21:53.439> files<02:21:53.920> in<02:21:54.160> data.js. 02:21:55.910 --> 02:21:55.920 align:start position:0% understood all files in data.js. 02:21:55.920 --> 02:21:57.750 align:start position:0% understood all files in data.js. After<02:21:56.160> that<02:21:56.479> it<02:21:56.720> is<02:21:56.960> carrying<02:21:57.280> on<02:21:57.520> our 02:21:57.750 --> 02:21:57.760 align:start position:0% After that it is carrying on our 02:21:57.760 --> 02:21:59.670 align:start position:0% After that it is carrying on our research<02:21:58.160> purpose. 02:21:59.670 --> 02:21:59.680 align:start position:0% research purpose. 02:21:59.680 --> 02:22:02.150 align:start position:0% research purpose. When<02:22:00.000> these<02:22:00.240> things<02:22:00.479> are<02:22:00.640> included<02:22:01.520> our<02:22:01.840> final 02:22:02.150 --> 02:22:02.160 align:start position:0% When these things are included our final 02:22:02.160 --> 02:22:03.910 align:start position:0% When these things are included our final website<02:22:02.640> version<02:22:02.960> will<02:22:03.200> come<02:22:03.359> in<02:22:03.520> a<02:22:03.680> better 02:22:03.910 --> 02:22:03.920 align:start position:0% website version will come in a better 02:22:03.920 --> 02:22:07.830 align:start position:0% website version will come in a better form.<02:22:05.359> Let<02:22:05.600> me<02:22:05.760> tell<02:22:05.920> you<02:22:06.080> an<02:22:06.319> important<02:22:06.800> thing 02:22:07.830 --> 02:22:07.840 align:start position:0% form. Let me tell you an important thing 02:22:07.840 --> 02:22:10.309 align:start position:0% form. Let me tell you an important thing in<02:22:08.080> codeex.<02:22:09.120> Whatever<02:22:09.520> things<02:22:09.760> are<02:22:10.000> happening 02:22:10.309 --> 02:22:10.319 align:start position:0% in codeex. Whatever things are happening 02:22:10.319 --> 02:22:13.429 align:start position:0% in codeex. Whatever things are happening now,<02:22:10.800> you<02:22:11.040> can<02:22:11.200> see<02:22:11.359> them<02:22:11.600> all<02:22:11.840> here.<02:22:13.040> If<02:22:13.200> we 02:22:13.429 --> 02:22:13.439 align:start position:0% now, you can see them all here. If we 02:22:13.439 --> 02:22:16.389 align:start position:0% now, you can see them all here. If we have<02:22:13.600> any<02:22:13.840> output,<02:22:14.399> we<02:22:14.560> can<02:22:14.720> see<02:22:14.880> it<02:22:15.120> too.<02:22:16.160> If 02:22:16.389 --> 02:22:16.399 align:start position:0% have any output, we can see it too. If 02:22:16.399 --> 02:22:18.710 align:start position:0% have any output, we can see it too. If we<02:22:16.560> have<02:22:16.720> any<02:22:17.040> source,<02:22:17.840> we<02:22:18.080> can<02:22:18.240> see<02:22:18.399> which 02:22:18.710 --> 02:22:18.720 align:start position:0% we have any source, we can see which 02:22:18.720 --> 02:22:21.910 align:start position:0% we have any source, we can see which source<02:22:18.960> it<02:22:19.200> is<02:22:19.439> utilizing<02:22:19.920> here.<02:22:20.960> Like<02:22:21.280> here, 02:22:21.910 --> 02:22:21.920 align:start position:0% source it is utilizing here. Like here, 02:22:21.920 --> 02:22:24.070 align:start position:0% source it is utilizing here. Like here, from<02:22:22.160> a<02:22:22.399> regional<02:22:22.880> hospital<02:22:23.280> list,<02:22:23.680> it<02:22:23.920> is 02:22:24.070 --> 02:22:24.080 align:start position:0% from a regional hospital list, it is 02:22:24.080 --> 02:22:26.950 align:start position:0% from a regional hospital list, it is retrieving<02:22:24.640> doctors.<02:22:26.000> First,<02:22:26.399> it<02:22:26.640> makes 02:22:26.950 --> 02:22:26.960 align:start position:0% retrieving doctors. First, it makes 02:22:26.960 --> 02:22:29.349 align:start position:0% retrieving doctors. First, it makes concrete<02:22:27.439> changes,<02:22:28.319> replacing<02:22:28.880> generic 02:22:29.349 --> 02:22:29.359 align:start position:0% concrete changes, replacing generic 02:22:29.359 --> 02:22:31.910 align:start position:0% concrete changes, replacing generic healthcare<02:22:29.920> content<02:22:30.560> with<02:22:30.800> Alaska<02:22:31.439> specific 02:22:31.910 --> 02:22:31.920 align:start position:0% healthcare content with Alaska specific 02:22:31.920 --> 02:22:34.710 align:start position:0% healthcare content with Alaska specific facility<02:22:32.399> and<02:22:32.720> care<02:22:33.040> context. 02:22:34.710 --> 02:22:34.720 align:start position:0% facility and care context. 02:22:34.720 --> 02:22:36.710 align:start position:0% facility and care context. Second,<02:22:35.280> it<02:22:35.520> is<02:22:35.680> rebuilding<02:22:36.160> the<02:22:36.399> visual 02:22:36.710 --> 02:22:36.720 align:start position:0% Second, it is rebuilding the visual 02:22:36.720 --> 02:22:39.110 align:start position:0% Second, it is rebuilding the visual system<02:22:37.040> into<02:22:37.359> a<02:22:37.600> brighter,<02:22:38.399> premium<02:22:38.880> look 02:22:39.110 --> 02:22:39.120 align:start position:0% system into a brighter, premium look 02:22:39.120 --> 02:22:41.510 align:start position:0% system into a brighter, premium look that<02:22:39.439> feels<02:22:39.680> native<02:22:40.000> on<02:22:40.319> iPhone<02:22:40.640> and<02:22:40.880> Mac 02:22:41.510 --> 02:22:41.520 align:start position:0% that feels native on iPhone and Mac 02:22:41.520 --> 02:22:43.590 align:start position:0% that feels native on iPhone and Mac without<02:22:41.920> copying<02:22:42.399> Apple<02:22:42.720> trademarks<02:22:43.359> or 02:22:43.590 --> 02:22:43.600 align:start position:0% without copying Apple trademarks or 02:22:43.600 --> 02:22:46.870 align:start position:0% without copying Apple trademarks or proprietary<02:22:44.319> icon<02:22:44.640> sets.<02:22:46.000> All<02:22:46.160> these<02:22:46.479> changes 02:22:46.870 --> 02:22:46.880 align:start position:0% proprietary icon sets. All these changes 02:22:46.880 --> 02:22:49.910 align:start position:0% proprietary icon sets. All these changes are<02:22:47.040> being<02:22:47.280> created<02:22:47.840> right<02:22:48.080> now.<02:22:48.319> Here<02:22:49.520> in<02:22:49.760> the 02:22:49.910 --> 02:22:49.920 align:start position:0% are being created right now. Here in the 02:22:49.920 --> 02:22:52.230 align:start position:0% are being created right now. Here in the style<02:22:50.319> section,<02:22:51.120> you<02:22:51.359> can<02:22:51.520> see<02:22:51.600> that<02:22:51.840> we<02:22:52.080> have 02:22:52.230 --> 02:22:52.240 align:start position:0% style section, you can see that we have 02:22:52.240 --> 02:22:54.870 align:start position:0% style section, you can see that we have many<02:22:52.640> changes<02:22:53.040> appearing.<02:22:54.479> We<02:22:54.720> are 02:22:54.870 --> 02:22:54.880 align:start position:0% many changes appearing. We are 02:22:54.880 --> 02:22:57.429 align:start position:0% many changes appearing. We are experiencing<02:22:55.600> many<02:22:56.000> changes<02:22:56.800> because<02:22:57.040> it<02:22:57.280> is 02:22:57.429 --> 02:22:57.439 align:start position:0% experiencing many changes because it is 02:22:57.439 --> 02:22:59.429 align:start position:0% experiencing many changes because it is performing<02:22:57.920> complete<02:22:58.399> enhancements<02:22:59.040> in<02:22:59.280> our 02:22:59.429 --> 02:22:59.439 align:start position:0% performing complete enhancements in our 02:22:59.439 --> 02:23:01.270 align:start position:0% performing complete enhancements in our file.<02:22:59.760> Overall, 02:23:01.270 --> 02:23:01.280 align:start position:0% file. Overall, 02:23:01.280 --> 02:23:02.950 align:start position:0% file. Overall, all<02:23:01.520> the<02:23:01.680> styling<02:23:02.080> updates<02:23:02.479> are<02:23:02.720> being 02:23:02.950 --> 02:23:02.960 align:start position:0% all the styling updates are being 02:23:02.960 --> 02:23:04.870 align:start position:0% all the styling updates are being processed<02:23:03.439> to<02:23:03.600> match<02:23:03.840> the<02:23:04.080> ecosystem<02:23:04.640> we 02:23:04.870 --> 02:23:04.880 align:start position:0% processed to match the ecosystem we 02:23:04.880 --> 02:23:06.389 align:start position:0% processed to match the ecosystem we requested. 02:23:06.389 --> 02:23:06.399 align:start position:0% requested. 02:23:06.399 --> 02:23:08.469 align:start position:0% requested. Our<02:23:06.640> project<02:23:06.960> design<02:23:07.359> is<02:23:07.600> improving<02:23:08.000> to<02:23:08.240> look 02:23:08.469 --> 02:23:08.479 align:start position:0% Our project design is improving to look 02:23:08.479 --> 02:23:09.750 align:start position:0% Our project design is improving to look professional.<02:23:09.120> The<02:23:09.359> software 02:23:09.750 --> 02:23:09.760 align:start position:0% professional. The software 02:23:09.760 --> 02:23:11.750 align:start position:0% professional. The software implementation<02:23:10.560> has<02:23:10.800> reached<02:23:11.120> the<02:23:11.280> required 02:23:11.750 --> 02:23:11.760 align:start position:0% implementation has reached the required 02:23:11.760 --> 02:23:15.110 align:start position:0% implementation has reached the required final<02:23:12.080> stages.<02:23:13.200> All<02:23:13.439> web<02:23:13.760> files<02:23:14.000> were<02:23:14.240> edited. 02:23:15.110 --> 02:23:15.120 align:start position:0% final stages. All web files were edited. 02:23:15.120 --> 02:23:17.910 align:start position:0% final stages. All web files were edited. The<02:23:15.359> main<02:23:15.680> index<02:23:16.160> file<02:23:16.399> is<02:23:16.640> now<02:23:16.880> running.<02:23:17.680> The 02:23:17.910 --> 02:23:17.920 align:start position:0% The main index file is now running. The 02:23:17.920 --> 02:23:20.790 align:start position:0% The main index file is now running. The visual<02:23:18.319> brand<02:23:18.720> appears<02:23:19.040> much<02:23:19.359> better<02:23:19.600> now. 02:23:20.790 --> 02:23:20.800 align:start position:0% visual brand appears much better now. 02:23:20.800 --> 02:23:22.790 align:start position:0% visual brand appears much better now. Demo<02:23:21.200> login<02:23:21.520> credentials<02:23:22.160> exist<02:23:22.479> in<02:23:22.640> the 02:23:22.790 --> 02:23:22.800 align:start position:0% Demo login credentials exist in the 02:23:22.800 --> 02:23:25.590 align:start position:0% Demo login credentials exist in the database.<02:23:24.160> Entering<02:23:24.640> the<02:23:24.800> main<02:23:25.040> dashboard 02:23:25.590 --> 02:23:25.600 align:start position:0% database. Entering the main dashboard 02:23:25.600 --> 02:23:28.950 align:start position:0% database. Entering the main dashboard shows<02:23:25.920> Aurora<02:23:26.479> Care<02:23:26.720> Alaska.<02:23:28.080> Navigating<02:23:28.720> to 02:23:28.950 --> 02:23:28.960 align:start position:0% shows Aurora Care Alaska. Navigating to 02:23:28.960 --> 02:23:31.429 align:start position:0% shows Aurora Care Alaska. Navigating to care<02:23:29.200> teams<02:23:29.920> displays<02:23:30.399> available<02:23:30.960> health<02:23:31.200> and 02:23:31.429 --> 02:23:31.439 align:start position:0% care teams displays available health and 02:23:31.439 --> 02:23:34.150 align:start position:0% care teams displays available health and vascular<02:23:31.920> care,<02:23:32.640> internal<02:23:33.200> medicine,<02:23:33.920> and 02:23:34.150 --> 02:23:34.160 align:start position:0% vascular care, internal medicine, and 02:23:34.160 --> 02:23:36.389 align:start position:0% vascular care, internal medicine, and real-time<02:23:34.800> schedules. 02:23:36.389 --> 02:23:36.399 align:start position:0% real-time schedules. 02:23:36.399 --> 02:23:38.469 align:start position:0% real-time schedules. Alaska<02:23:36.960> Regional<02:23:37.439> Cardiology<02:23:38.160> and 02:23:38.469 --> 02:23:38.479 align:start position:0% Alaska Regional Cardiology and 02:23:38.479 --> 02:23:40.950 align:start position:0% Alaska Regional Cardiology and Providence<02:23:39.040> primary<02:23:39.439> care<02:23:39.760> access<02:23:40.160> details 02:23:40.950 --> 02:23:40.960 align:start position:0% Providence primary care access details 02:23:40.960 --> 02:23:43.030 align:start position:0% Providence primary care access details are<02:23:41.200> visible<02:23:41.520> with<02:23:41.840> exact<02:23:42.240> addresses<02:23:42.720> and 02:23:43.030 --> 02:23:43.040 align:start position:0% are visible with exact addresses and 02:23:43.040 --> 02:23:45.429 align:start position:0% are visible with exact addresses and contact<02:23:43.520> access<02:23:43.920> details. 02:23:45.429 --> 02:23:45.439 align:start position:0% contact access details. 02:23:45.439 --> 02:23:47.750 align:start position:0% contact access details. We<02:23:45.680> can<02:23:45.760> book<02:23:46.000> a<02:23:46.160> medical<02:23:46.479> appointment<02:23:46.880> here. 02:23:47.750 --> 02:23:47.760 align:start position:0% We can book a medical appointment here. 02:23:47.760 --> 02:23:49.750 align:start position:0% We can book a medical appointment here. For<02:23:47.840> example,<02:23:48.399> a<02:23:48.640> normal<02:23:48.960> checkup<02:23:49.359> for<02:23:49.520> a 02:23:49.750 --> 02:23:49.760 align:start position:0% For example, a normal checkup for a 02:23:49.760 --> 02:23:52.790 align:start position:0% For example, a normal checkup for a child<02:23:50.240> can<02:23:50.560> be<02:23:50.640> scheduled<02:23:51.040> at<02:23:51.200> 10:15. 02:23:52.790 --> 02:23:52.800 align:start position:0% child can be scheduled at 10:15. 02:23:52.800 --> 02:23:54.630 align:start position:0% child can be scheduled at 10:15. A<02:23:53.040> new<02:23:53.280> medical<02:23:53.680> appointment<02:23:54.080> request<02:23:54.479> is 02:23:54.630 --> 02:23:54.640 align:start position:0% A new medical appointment request is 02:23:54.640 --> 02:23:56.870 align:start position:0% A new medical appointment request is submitted<02:23:55.120> for<02:23:55.359> 1:30. 02:23:56.870 --> 02:23:56.880 align:start position:0% submitted for 1:30. 02:23:56.880 --> 02:23:59.670 align:start position:0% submitted for 1:30. The<02:23:57.200> system<02:23:57.439> updates<02:23:57.920> the<02:23:58.080> patient<02:23:58.479> schedule. 02:23:59.670 --> 02:23:59.680 align:start position:0% The system updates the patient schedule. 02:23:59.680 --> 02:24:02.710 align:start position:0% The system updates the patient schedule. The<02:24:00.000> active<02:24:00.399> list<02:24:00.720> shows<02:24:01.120> scheduled<02:24:01.600> visits. 02:24:02.710 --> 02:24:02.720 align:start position:0% The active list shows scheduled visits. 02:24:02.720 --> 02:24:04.790 align:start position:0% The active list shows scheduled visits. We<02:24:02.960> can<02:24:03.120> cancel<02:24:03.520> any<02:24:03.760> booked<02:24:04.160> visit<02:24:04.399> from<02:24:04.560> the 02:24:04.790 --> 02:24:04.800 align:start position:0% We can cancel any booked visit from the 02:24:04.800 --> 02:24:07.830 align:start position:0% We can cancel any booked visit from the records.<02:24:06.160> Previous<02:24:06.640> health<02:24:06.960> records<02:24:07.439> display 02:24:07.830 --> 02:24:07.840 align:start position:0% records. Previous health records display 02:24:07.840 --> 02:24:09.910 align:start position:0% records. Previous health records display current<02:24:08.240> patient<02:24:08.640> medications<02:24:09.280> and<02:24:09.600> known 02:24:09.910 --> 02:24:09.920 align:start position:0% current patient medications and known 02:24:09.920 --> 02:24:11.429 align:start position:0% current patient medications and known allergies. 02:24:11.429 --> 02:24:11.439 align:start position:0% allergies. 02:24:11.439 --> 02:24:13.510 align:start position:0% allergies. Recent<02:24:11.920> clinical<02:24:12.319> visits<02:24:12.720> and<02:24:12.880> lab<02:24:13.200> reviews 02:24:13.510 --> 02:24:13.520 align:start position:0% Recent clinical visits and lab reviews 02:24:13.520 --> 02:24:15.510 align:start position:0% Recent clinical visits and lab reviews are<02:24:13.760> also<02:24:14.000> listed. 02:24:15.510 --> 02:24:15.520 align:start position:0% are also listed. 02:24:15.520 --> 02:24:17.429 align:start position:0% are also listed. All<02:24:15.840> recommended<02:24:16.479> system<02:24:16.800> features<02:24:17.280> are 02:24:17.429 --> 02:24:17.439 align:start position:0% All recommended system features are 02:24:17.439 --> 02:24:20.630 align:start position:0% All recommended system features are implemented<02:24:17.920> in<02:24:18.160> this<02:24:18.319> application<02:24:18.880> version. 02:24:20.630 --> 02:24:20.640 align:start position:0% implemented in this application version. 02:24:20.640 --> 02:24:22.710 align:start position:0% implemented in this application version. All<02:24:20.880> these<02:24:21.200> recommended<02:24:21.840> software<02:24:22.240> features 02:24:22.710 --> 02:24:22.720 align:start position:0% All these recommended software features 02:24:22.720 --> 02:24:24.950 align:start position:0% All these recommended software features are<02:24:22.880> now<02:24:23.200> complete. 02:24:24.950 --> 02:24:24.960 align:start position:0% are now complete. 02:24:24.960 --> 02:24:26.790 align:start position:0% are now complete. Next,<02:24:25.439> a<02:24:25.680> brand<02:24:25.920> new<02:24:26.160> change<02:24:26.479> will<02:24:26.720> be 02:24:26.790 --> 02:24:26.800 align:start position:0% Next, a brand new change will be 02:24:26.800 --> 02:24:30.230 align:start position:0% Next, a brand new change will be adopted.<02:24:28.160> A<02:24:28.399> new<02:24:28.720> user<02:24:29.200> profile<02:24:29.680> feature<02:24:30.000> is 02:24:30.230 --> 02:24:30.240 align:start position:0% adopted. A new user profile feature is 02:24:30.240 --> 02:24:33.270 align:start position:0% adopted. A new user profile feature is needed.<02:24:31.439> The<02:24:31.680> end<02:24:31.920> user<02:24:32.319> should<02:24:32.560> create<02:24:32.800> a<02:24:33.040> new 02:24:33.270 --> 02:24:33.280 align:start position:0% needed. The end user should create a new 02:24:33.280 --> 02:24:35.830 align:start position:0% needed. The end user should create a new account,<02:24:34.000> add<02:24:34.319> personal<02:24:34.720> details,<02:24:35.520> and 02:24:35.830 --> 02:24:35.840 align:start position:0% account, add personal details, and 02:24:35.840 --> 02:24:38.550 align:start position:0% account, add personal details, and access<02:24:36.160> a<02:24:36.479> personalized<02:24:37.040> dashboard. 02:24:38.550 --> 02:24:38.560 align:start position:0% access a personalized dashboard. 02:24:38.560 --> 02:24:40.150 align:start position:0% access a personalized dashboard. Logging<02:24:38.960> out<02:24:39.120> of<02:24:39.280> the<02:24:39.439> current<02:24:39.760> active 02:24:40.150 --> 02:24:40.160 align:start position:0% Logging out of the current active 02:24:40.160 --> 02:24:42.790 align:start position:0% Logging out of the current active session<02:24:40.560> brings<02:24:40.880> us<02:24:41.040> to<02:24:41.120> the<02:24:41.280> main<02:24:41.520> screen. 02:24:42.790 --> 02:24:42.800 align:start position:0% session brings us to the main screen. 02:24:42.800 --> 02:24:45.510 align:start position:0% session brings us to the main screen. Clicking<02:24:43.120> on<02:24:43.520> create<02:24:43.840> a<02:24:44.080> demo<02:24:44.479> account<02:24:45.120> opens 02:24:45.510 --> 02:24:45.520 align:start position:0% Clicking on create a demo account opens 02:24:45.520 --> 02:24:48.790 align:start position:0% Clicking on create a demo account opens a<02:24:45.680> new<02:24:45.840> form.<02:24:46.960> A<02:24:47.200> new<02:24:47.439> name,<02:24:48.000> Alex,<02:24:48.560> is 02:24:48.790 --> 02:24:48.800 align:start position:0% a new form. A new name, Alex, is 02:24:48.800 --> 02:24:51.030 align:start position:0% a new form. A new name, Alex, is entered.<02:24:49.920> The<02:24:50.240> email<02:24:50.560> address 02:24:51.030 --> 02:24:51.040 align:start position:0% entered. The email address 02:24:51.040 --> 02:24:52.630 align:start position:0% entered. The email address alex@gmail.com 02:24:52.630 --> 02:24:52.640 align:start position:0% alex@gmail.com 02:24:52.640 --> 02:24:55.429 align:start position:0% alex@gmail.com is<02:24:52.880> provided.<02:24:54.080> A<02:24:54.399> secure<02:24:54.800> password<02:24:55.200> is 02:24:55.429 --> 02:24:55.439 align:start position:0% is provided. A secure password is 02:24:55.439 --> 02:24:58.389 align:start position:0% is provided. A secure password is created<02:24:55.840> for<02:24:56.080> this<02:24:56.240> new<02:24:56.479> account.<02:24:57.840> The<02:24:58.160> brand 02:24:58.389 --> 02:24:58.399 align:start position:0% created for this new account. The brand 02:24:58.399 --> 02:25:01.429 align:start position:0% created for this new account. The brand new<02:24:58.720> demo<02:24:59.120> account<02:24:59.359> is<02:24:59.680> accessed.<02:25:01.040> Looking<02:25:01.280> at 02:25:01.429 --> 02:25:01.439 align:start position:0% new demo account is accessed. Looking at 02:25:01.439 --> 02:25:03.750 align:start position:0% new demo account is accessed. Looking at the<02:25:01.600> health<02:25:01.840> records<02:25:02.240> for<02:25:02.399> this<02:25:02.640> new<02:25:02.880> user, 02:25:03.750 --> 02:25:03.760 align:start position:0% the health records for this new user, 02:25:03.760 --> 02:25:05.990 align:start position:0% the health records for this new user, previous<02:25:04.160> medications<02:25:04.960> and<02:25:05.200> known<02:25:05.520> allergies 02:25:05.990 --> 02:25:06.000 align:start position:0% previous medications and known allergies 02:25:06.000 --> 02:25:08.710 align:start position:0% previous medications and known allergies are<02:25:06.160> still<02:25:06.399> visible.<02:25:07.680> The<02:25:07.920> recent<02:25:08.319> clinical 02:25:08.710 --> 02:25:08.720 align:start position:0% are still visible. The recent clinical 02:25:08.720 --> 02:25:10.790 align:start position:0% are still visible. The recent clinical visit<02:25:09.120> data<02:25:09.439> is<02:25:09.680> also<02:25:10.080> showing<02:25:10.399> old 02:25:10.790 --> 02:25:10.800 align:start position:0% visit data is also showing old 02:25:10.800 --> 02:25:13.270 align:start position:0% visit data is also showing old information.<02:25:12.240> This<02:25:12.479> problem<02:25:12.880> happens 02:25:13.270 --> 02:25:13.280 align:start position:0% information. This problem happens 02:25:13.280 --> 02:25:16.230 align:start position:0% information. This problem happens because<02:25:13.600> synthetic<02:25:14.240> mock<02:25:14.560> data<02:25:14.880> is<02:25:15.120> used. 02:25:16.230 --> 02:25:16.240 align:start position:0% because synthetic mock data is used. 02:25:16.240 --> 02:25:19.030 align:start position:0% because synthetic mock data is used. When<02:25:16.479> a<02:25:16.640> new<02:25:16.880> user<02:25:17.280> account<02:25:17.520> is<02:25:17.840> created,<02:25:18.720> all 02:25:19.030 --> 02:25:19.040 align:start position:0% When a new user account is created, all 02:25:19.040 --> 02:25:21.910 align:start position:0% When a new user account is created, all personal<02:25:19.520> details<02:25:20.000> should<02:25:20.240> start<02:25:20.479> fresh.<02:25:21.680> We 02:25:21.910 --> 02:25:21.920 align:start position:0% personal details should start fresh. We 02:25:21.920 --> 02:25:24.070 align:start position:0% personal details should start fresh. We need<02:25:22.080> to<02:25:22.240> include<02:25:22.800> actual<02:25:23.200> user<02:25:23.600> inputs 02:25:24.070 --> 02:25:24.080 align:start position:0% need to include actual user inputs 02:25:24.080 --> 02:25:26.950 align:start position:0% need to include actual user inputs instead<02:25:24.399> of<02:25:24.560> synthetic<02:25:25.120> data.<02:25:26.399> Even<02:25:26.640> if 02:25:26.950 --> 02:25:26.960 align:start position:0% instead of synthetic data. Even if 02:25:26.960 --> 02:25:28.550 align:start position:0% instead of synthetic data. Even if previous<02:25:27.520> scheduled<02:25:27.920> appointments<02:25:28.319> are 02:25:28.550 --> 02:25:28.560 align:start position:0% previous scheduled appointments are 02:25:28.560 --> 02:25:30.710 align:start position:0% previous scheduled appointments are canled,<02:25:29.280> they<02:25:29.600> remain<02:25:29.840> in<02:25:30.000> the<02:25:30.240> application 02:25:30.710 --> 02:25:30.720 align:start position:0% canled, they remain in the application 02:25:30.720 --> 02:25:33.429 align:start position:0% canled, they remain in the application database<02:25:31.280> for<02:25:31.439> the<02:25:31.600> new<02:25:31.840> patient.<02:25:33.200> This 02:25:33.429 --> 02:25:33.439 align:start position:0% database for the new patient. This 02:25:33.439 --> 02:25:35.670 align:start position:0% database for the new patient. This behavior<02:25:34.000> applies<02:25:34.399> to<02:25:34.640> every<02:25:34.960> new<02:25:35.280> patient 02:25:35.670 --> 02:25:35.680 align:start position:0% behavior applies to every new patient 02:25:35.680 --> 02:25:37.670 align:start position:0% behavior applies to every new patient profile<02:25:36.160> created. 02:25:37.670 --> 02:25:37.680 align:start position:0% profile created. 02:25:37.680 --> 02:25:39.670 align:start position:0% profile created. New<02:25:37.920> data<02:25:38.319> is<02:25:38.479> not<02:25:38.720> available<02:25:39.120> yet<02:25:39.359> in<02:25:39.520> the 02:25:39.670 --> 02:25:39.680 align:start position:0% New data is not available yet in the 02:25:39.680 --> 02:25:41.270 align:start position:0% New data is not available yet in the interface. 02:25:41.270 --> 02:25:41.280 align:start position:0% interface. 02:25:41.280 --> 02:25:44.070 align:start position:0% interface. To<02:25:41.520> solve<02:25:41.760> this<02:25:42.000> issue,<02:25:42.720> new<02:25:43.040> code<02:25:43.359> logic<02:25:43.840> must 02:25:44.070 --> 02:25:44.080 align:start position:0% To solve this issue, new code logic must 02:25:44.080 --> 02:25:46.870 align:start position:0% To solve this issue, new code logic must be<02:25:44.240> introduced.<02:25:45.520> A<02:25:45.760> text<02:25:46.000> prompt<02:25:46.399> is<02:25:46.560> written 02:25:46.870 --> 02:25:46.880 align:start position:0% be introduced. A text prompt is written 02:25:46.880 --> 02:25:49.590 align:start position:0% be introduced. A text prompt is written to<02:25:47.040> update<02:25:47.439> the<02:25:47.680> application<02:25:48.160> logic.<02:25:49.359> The 02:25:49.590 --> 02:25:49.600 align:start position:0% to update the application logic. The 02:25:49.600 --> 02:25:51.830 align:start position:0% to update the application logic. The missing<02:25:50.000> profile<02:25:50.479> fields<02:25:50.960> need<02:25:51.120> to<02:25:51.280> be<02:25:51.359> added 02:25:51.830 --> 02:25:51.840 align:start position:0% missing profile fields need to be added 02:25:51.840 --> 02:25:54.790 align:start position:0% missing profile fields need to be added and<02:25:52.160> displayed<02:25:52.560> on<02:25:52.800> the<02:25:52.960> main<02:25:53.200> dashboard.<02:25:54.560> The 02:25:54.790 --> 02:25:54.800 align:start position:0% and displayed on the main dashboard. The 02:25:54.800 --> 02:25:56.790 align:start position:0% and displayed on the main dashboard. The user<02:25:55.200> account<02:25:55.600> creation<02:25:56.000> flow<02:25:56.399> must<02:25:56.640> be 02:25:56.790 --> 02:25:56.800 align:start position:0% user account creation flow must be 02:25:56.800 --> 02:25:59.990 align:start position:0% user account creation flow must be complete<02:25:57.200> from<02:25:57.439> end<02:25:57.600> to<02:25:57.840> end.<02:25:59.040> The<02:25:59.359> new<02:25:59.600> user 02:25:59.990 --> 02:26:00.000 align:start position:0% complete from end to end. The new user 02:26:00.000 --> 02:26:02.389 align:start position:0% complete from end to end. The new user must<02:26:00.319> feel<02:26:00.640> personalized<02:26:01.680> without<02:26:02.080> falling 02:26:02.389 --> 02:26:02.399 align:start position:0% must feel personalized without falling 02:26:02.399 --> 02:26:05.190 align:start position:0% must feel personalized without falling back<02:26:02.640> to<02:26:02.800> generic<02:26:03.280> demo<02:26:03.680> data. 02:26:05.190 --> 02:26:05.200 align:start position:0% back to generic demo data. 02:26:05.200 --> 02:26:08.309 align:start position:0% back to generic demo data. The<02:26:05.439> core<02:26:05.760> application<02:26:06.319> logic<02:26:06.720> is<02:26:06.880> updating. 02:26:08.309 --> 02:26:08.319 align:start position:0% The core application logic is updating. 02:26:08.319 --> 02:26:10.309 align:start position:0% The core application logic is updating. Five<02:26:08.640> project<02:26:09.040> files<02:26:09.359> are<02:26:09.600> being<02:26:09.760> edited<02:26:10.160> to 02:26:10.309 --> 02:26:10.319 align:start position:0% Five project files are being edited to 02:26:10.319 --> 02:26:12.309 align:start position:0% Five project files are being edited to implement<02:26:10.720> the<02:26:10.960> changes. 02:26:12.309 --> 02:26:12.319 align:start position:0% implement the changes. 02:26:12.319 --> 02:26:15.990 align:start position:0% implement the changes. These<02:26:12.640> code<02:26:12.960> items<02:26:13.439> include<02:26:13.920> data,<02:26:14.880> HTML, 02:26:15.990 --> 02:26:16.000 align:start position:0% These code items include data, HTML, 02:26:16.000 --> 02:26:19.429 align:start position:0% These code items include data, HTML, dashboard,<02:26:16.960> index,<02:26:17.520> and<02:26:17.760> records<02:26:18.160> files. 02:26:19.429 --> 02:26:19.439 align:start position:0% dashboard, index, and records files. 02:26:19.439 --> 02:26:21.429 align:start position:0% dashboard, index, and records files. More<02:26:19.760> software<02:26:20.240> changes<02:26:20.640> are<02:26:20.880> expected<02:26:21.200> to 02:26:21.429 --> 02:26:21.439 align:start position:0% More software changes are expected to 02:26:21.439 --> 02:26:24.309 align:start position:0% More software changes are expected to arrive<02:26:21.760> soon.<02:26:22.880> The<02:26:23.120> main<02:26:23.439> project<02:26:23.760> goal<02:26:24.080> is 02:26:24.309 --> 02:26:24.319 align:start position:0% arrive soon. The main project goal is 02:26:24.319 --> 02:26:27.750 align:start position:0% arrive soon. The main project goal is defined<02:26:24.800> now.<02:26:25.840> A<02:26:26.080> new<02:26:26.399> created<02:26:26.960> user<02:26:27.359> account 02:26:27.750 --> 02:26:27.760 align:start position:0% defined now. A new created user account 02:26:27.760 --> 02:26:30.550 align:start position:0% defined now. A new created user account must<02:26:28.080> feel<02:26:28.399> custom<02:26:28.800> and<02:26:29.040> personalized.<02:26:30.399> It 02:26:30.550 --> 02:26:30.560 align:start position:0% must feel custom and personalized. It 02:26:30.560 --> 02:26:32.389 align:start position:0% must feel custom and personalized. It should<02:26:30.720> not<02:26:30.960> fall<02:26:31.200> back<02:26:31.359> to<02:26:31.600> generic<02:26:32.080> demo 02:26:32.389 --> 02:26:32.399 align:start position:0% should not fall back to generic demo 02:26:32.399 --> 02:26:35.190 align:start position:0% should not fall back to generic demo data.<02:26:33.600> The<02:26:33.920> user<02:26:34.240> profile<02:26:34.640> flow<02:26:34.960> is 02:26:35.190 --> 02:26:35.200 align:start position:0% data. The user profile flow is 02:26:35.200 --> 02:26:37.990 align:start position:0% data. The user profile flow is implemented<02:26:35.600> in<02:26:35.840> the<02:26:36.000> source<02:26:36.319> code.<02:26:37.520> Syntax 02:26:37.990 --> 02:26:38.000 align:start position:0% implemented in the source code. Syntax 02:26:38.000 --> 02:26:39.510 align:start position:0% implemented in the source code. Syntax checks<02:26:38.399> are<02:26:38.560> running<02:26:38.800> to<02:26:38.960> verify<02:26:39.359> the 02:26:39.510 --> 02:26:39.520 align:start position:0% checks are running to verify the 02:26:39.520 --> 02:26:42.389 align:start position:0% checks are running to verify the software<02:26:39.920> changes.<02:26:41.040> The<02:26:41.359> main<02:26:41.600> index<02:26:42.080> file 02:26:42.389 --> 02:26:42.399 align:start position:0% software changes. The main index file 02:26:42.399 --> 02:26:45.190 align:start position:0% software changes. The main index file now<02:26:42.640> includes<02:26:42.960> a<02:26:43.200> complete<02:26:43.520> signup<02:26:44.000> form. 02:26:45.190 --> 02:26:45.200 align:start position:0% now includes a complete signup form. 02:26:45.200 --> 02:26:47.349 align:start position:0% now includes a complete signup form. Logging<02:26:45.600> out<02:26:45.840> again<02:26:46.160> allows<02:26:46.479> us<02:26:46.640> to<02:26:46.800> test<02:26:47.040> the 02:26:47.349 --> 02:26:47.359 align:start position:0% Logging out again allows us to test the 02:26:47.359 --> 02:26:50.150 align:start position:0% Logging out again allows us to test the updated<02:26:47.840> demo<02:26:48.319> account<02:26:48.640> creation. 02:26:50.150 --> 02:26:50.160 align:start position:0% updated demo account creation. 02:26:50.160 --> 02:26:52.150 align:start position:0% updated demo account creation. The<02:26:50.399> new<02:26:50.640> registration<02:26:51.200> form<02:26:51.600> requires 02:26:52.150 --> 02:26:52.160 align:start position:0% The new registration form requires 02:26:52.160 --> 02:26:55.349 align:start position:0% The new registration form requires comprehensive<02:26:52.800> user<02:26:53.200> details.<02:26:54.479> Full<02:26:54.800> name, 02:26:55.349 --> 02:26:55.359 align:start position:0% comprehensive user details. Full name, 02:26:55.359 --> 02:26:58.150 align:start position:0% comprehensive user details. Full name, email,<02:26:56.240> phone<02:26:56.479> number,<02:26:57.040> date<02:26:57.280> of<02:26:57.520> birth, 02:26:58.150 --> 02:26:58.160 align:start position:0% email, phone number, date of birth, 02:26:58.160 --> 02:27:00.630 align:start position:0% email, phone number, date of birth, blood<02:26:58.479> type,<02:26:59.200> address,<02:26:59.920> and<02:27:00.240> medical 02:27:00.630 --> 02:27:00.640 align:start position:0% blood type, address, and medical 02:27:00.640 --> 02:27:03.670 align:start position:0% blood type, address, and medical insurance<02:27:01.120> information<02:27:01.680> must<02:27:02.000> be<02:27:02.160> provided. 02:27:03.670 --> 02:27:03.680 align:start position:0% insurance information must be provided. 02:27:03.680 --> 02:27:05.750 align:start position:0% insurance information must be provided. Emergency<02:27:04.319> contact<02:27:04.720> details<02:27:05.200> are<02:27:05.439> also 02:27:05.750 --> 02:27:05.760 align:start position:0% Emergency contact details are also 02:27:05.760 --> 02:27:08.389 align:start position:0% Emergency contact details are also required<02:27:06.080> to<02:27:06.240> complete<02:27:06.560> the<02:27:06.800> setup.<02:27:08.000> These 02:27:08.389 --> 02:27:08.399 align:start position:0% required to complete the setup. These 02:27:08.399 --> 02:27:10.309 align:start position:0% required to complete the setup. These user<02:27:08.800> details<02:27:09.120> will<02:27:09.359> be<02:27:09.520> stored<02:27:09.760> across<02:27:10.080> the 02:27:10.309 --> 02:27:10.319 align:start position:0% user details will be stored across the 02:27:10.319 --> 02:27:12.550 align:start position:0% user details will be stored across the application<02:27:10.880> assets.<02:27:11.760> The<02:27:12.000> new<02:27:12.240> account 02:27:12.550 --> 02:27:12.560 align:start position:0% application assets. The new account 02:27:12.560 --> 02:27:14.309 align:start position:0% application assets. The new account registration<02:27:13.200> form<02:27:13.520> is<02:27:13.760> filled<02:27:14.080> with 02:27:14.309 --> 02:27:14.319 align:start position:0% registration form is filled with 02:27:14.319 --> 02:27:17.270 align:start position:0% registration form is filled with specific<02:27:14.880> user<02:27:15.280> data.<02:27:16.399> The<02:27:16.640> first<02:27:16.880> name, 02:27:17.270 --> 02:27:17.280 align:start position:0% specific user data. The first name, 02:27:17.280 --> 02:27:19.510 align:start position:0% specific user data. The first name, Alex,<02:27:18.000> is<02:27:18.319> entered<02:27:18.640> along<02:27:18.880> with<02:27:19.040> the<02:27:19.200> email 02:27:19.510 --> 02:27:19.520 align:start position:0% Alex, is entered along with the email 02:27:19.520 --> 02:27:21.910 align:start position:0% Alex, is entered along with the email address.<02:27:20.560> A<02:27:20.800> random<02:27:21.200> phone<02:27:21.439> number<02:27:21.680> is 02:27:21.910 --> 02:27:21.920 align:start position:0% address. A random phone number is 02:27:21.920 --> 02:27:24.389 align:start position:0% address. A random phone number is provided.<02:27:23.040> The<02:27:23.280> proper<02:27:23.600> date<02:27:23.760> of<02:27:24.000> birth<02:27:24.240> is 02:27:24.389 --> 02:27:24.399 align:start position:0% provided. The proper date of birth is 02:27:24.399 --> 02:27:27.349 align:start position:0% provided. The proper date of birth is set.<02:27:25.359> The<02:27:25.600> blood<02:27:25.840> type<02:27:26.160> is<02:27:26.319> selected<02:27:26.720> as<02:27:27.040> a 02:27:27.349 --> 02:27:27.359 align:start position:0% set. The blood type is selected as a 02:27:27.359 --> 02:27:30.389 align:start position:0% set. The blood type is selected as a positive.<02:27:28.640> The<02:27:28.880> user<02:27:29.280> city<02:27:29.520> is<02:27:29.760> entered<02:27:30.080> as 02:27:30.389 --> 02:27:30.399 align:start position:0% positive. The user city is entered as 02:27:30.399 --> 02:27:33.190 align:start position:0% positive. The user city is entered as Alaska.<02:27:31.680> The<02:27:31.920> geographic<02:27:32.560> region<02:27:32.960> is 02:27:33.190 --> 02:27:33.200 align:start position:0% Alaska. The geographic region is 02:27:33.200 --> 02:27:39.270 align:start position:0% Alaska. The geographic region is specified<02:27:33.840> as<02:27:34.399> USA.<02:27:35.840> region,<02:27:36.640> state,<02:27:37.520> Alaska. 02:27:39.270 --> 02:27:39.280 align:start position:0% specified as USA. region, state, Alaska. 02:27:39.280 --> 02:27:41.990 align:start position:0% specified as USA. region, state, Alaska. An<02:27:39.520> insurance<02:27:40.000> plan<02:27:40.319> named<02:27:41.040> master<02:27:41.439> insure 02:27:41.990 --> 02:27:42.000 align:start position:0% An insurance plan named master insure 02:27:42.000 --> 02:27:45.110 align:start position:0% An insurance plan named master insure pro<02:27:42.479> is<02:27:42.720> added.<02:27:43.920> An<02:27:44.160> emergency<02:27:44.720> contact 02:27:45.110 --> 02:27:45.120 align:start position:0% pro is added. An emergency contact 02:27:45.120 --> 02:27:48.630 align:start position:0% pro is added. An emergency contact number<02:27:45.439> is<02:27:45.680> also<02:27:46.000> provided.<02:27:47.359> In<02:27:47.600> the<02:27:47.840> end,<02:27:48.319> a 02:27:48.630 --> 02:27:48.640 align:start position:0% number is also provided. In the end, a 02:27:48.640 --> 02:27:50.710 align:start position:0% number is also provided. In the end, a secure<02:27:49.040> password<02:27:49.439> is<02:27:49.680> created<02:27:50.000> to<02:27:50.240> finalize 02:27:50.710 --> 02:27:50.720 align:start position:0% secure password is created to finalize 02:27:50.720 --> 02:27:52.469 align:start position:0% secure password is created to finalize the<02:27:50.960> account. 02:27:52.469 --> 02:27:52.479 align:start position:0% the account. 02:27:52.479 --> 02:27:55.190 align:start position:0% the account. The<02:27:52.720> new<02:27:52.880> user<02:27:53.280> account<02:27:53.600> is<02:27:53.840> created. 02:27:55.190 --> 02:27:55.200 align:start position:0% The new user account is created. 02:27:55.200 --> 02:27:57.670 align:start position:0% The new user account is created. Navigating<02:27:55.760> to<02:27:55.920> the<02:27:56.160> medical<02:27:56.479> record<02:27:56.880> section 02:27:57.670 --> 02:27:57.680 align:start position:0% Navigating to the medical record section 02:27:57.680 --> 02:28:01.030 align:start position:0% Navigating to the medical record section shows<02:27:58.000> the<02:27:58.160> updated<02:27:58.720> patient<02:27:59.280> identity.<02:28:00.720> All 02:28:01.030 --> 02:28:01.040 align:start position:0% shows the updated patient identity. All 02:28:01.040 --> 02:28:03.190 align:start position:0% shows the updated patient identity. All personal<02:28:01.439> details<02:28:01.920> provided<02:28:02.399> during<02:28:02.720> signup 02:28:03.190 --> 02:28:03.200 align:start position:0% personal details provided during signup 02:28:03.200 --> 02:28:05.750 align:start position:0% personal details provided during signup are<02:28:03.359> displayed<02:28:03.760> here.<02:28:05.040> The<02:28:05.280> scheduled 02:28:05.750 --> 02:28:05.760 align:start position:0% are displayed here. The scheduled 02:28:05.760 --> 02:28:07.670 align:start position:0% are displayed here. The scheduled appointment<02:28:06.240> section<02:28:06.560> is<02:28:06.800> now<02:28:07.040> empty<02:28:07.439> and 02:28:07.670 --> 02:28:07.680 align:start position:0% appointment section is now empty and 02:28:07.680 --> 02:28:09.830 align:start position:0% appointment section is now empty and ready<02:28:07.920> for<02:28:08.080> new<02:28:08.319> bookings. 02:28:09.830 --> 02:28:09.840 align:start position:0% ready for new bookings. 02:28:09.840 --> 02:28:11.670 align:start position:0% ready for new bookings. The<02:28:10.080> care<02:28:10.319> team<02:28:10.640> section<02:28:11.040> reflects<02:28:11.439> the 02:28:11.670 --> 02:28:11.680 align:start position:0% The care team section reflects the 02:28:11.680 --> 02:28:14.469 align:start position:0% The care team section reflects the correct<02:28:12.080> operational<02:28:12.720> details.<02:28:14.160> The 02:28:14.469 --> 02:28:14.479 align:start position:0% correct operational details. The 02:28:14.479 --> 02:28:16.230 align:start position:0% correct operational details. The personalized<02:28:15.200> user<02:28:15.520> dashboard<02:28:16.000> is 02:28:16.230 --> 02:28:16.240 align:start position:0% personalized user dashboard is 02:28:16.240 --> 02:28:18.950 align:start position:0% personalized user dashboard is functional.<02:28:17.680> Multiple<02:28:18.240> future<02:28:18.640> system 02:28:18.950 --> 02:28:18.960 align:start position:0% functional. Multiple future system 02:28:18.960 --> 02:28:20.950 align:start position:0% functional. Multiple future system changes<02:28:19.359> can<02:28:19.600> be<02:28:19.760> integrated<02:28:20.319> as<02:28:20.479> the<02:28:20.720> project 02:28:20.950 --> 02:28:20.960 align:start position:0% changes can be integrated as the project 02:28:20.960 --> 02:28:23.110 align:start position:0% changes can be integrated as the project evolves. 02:28:23.110 --> 02:28:23.120 align:start position:0% evolves. 02:28:23.120 --> 02:28:25.990 align:start position:0% evolves. All<02:28:23.439> main<02:28:23.760> project<02:28:24.080> details<02:28:24.560> are<02:28:24.720> configured. 02:28:25.990 --> 02:28:26.000 align:start position:0% All main project details are configured. 02:28:26.000 --> 02:28:28.230 align:start position:0% All main project details are configured. The<02:28:26.240> next<02:28:26.560> crucial<02:28:27.040> step<02:28:27.280> is<02:28:27.520> to<02:28:27.680> upload<02:28:28.000> the 02:28:28.230 --> 02:28:28.240 align:start position:0% The next crucial step is to upload the 02:28:28.240 --> 02:28:31.429 align:start position:0% The next crucial step is to upload the project<02:28:28.640> code.<02:28:29.920> A<02:28:30.240> command<02:28:30.560> request<02:28:30.960> is<02:28:31.200> made 02:28:31.429 --> 02:28:31.439 align:start position:0% project code. A command request is made 02:28:31.439 --> 02:28:33.990 align:start position:0% project code. A command request is made to<02:28:31.600> push<02:28:31.920> all<02:28:32.240> files<02:28:32.640> into<02:28:32.960> a<02:28:33.120> remote<02:28:33.520> GitHub 02:28:33.990 --> 02:28:34.000 align:start position:0% to push all files into a remote GitHub 02:28:34.000 --> 02:28:35.510 align:start position:0% to push all files into a remote GitHub repository. 02:28:35.510 --> 02:28:35.520 align:start position:0% repository. 02:28:35.520 --> 02:28:37.750 align:start position:0% repository. The<02:28:35.840> operating<02:28:36.399> system<02:28:36.800> checks<02:28:37.280> available 02:28:37.750 --> 02:28:37.760 align:start position:0% The operating system checks available 02:28:37.760 --> 02:28:39.910 align:start position:0% The operating system checks available GitHub<02:28:38.319> capabilities<02:28:39.040> within<02:28:39.359> the<02:28:39.520> active 02:28:39.910 --> 02:28:39.920 align:start position:0% GitHub capabilities within the active 02:28:39.920 --> 02:28:41.510 align:start position:0% GitHub capabilities within the active workspace. 02:28:41.510 --> 02:28:41.520 align:start position:0% workspace. 02:28:41.520 --> 02:28:43.910 align:start position:0% workspace. A<02:28:41.760> local<02:28:42.160> system<02:28:42.560> git<02:28:42.880> installation<02:28:43.439> is<02:28:43.680> not 02:28:43.910 --> 02:28:43.920 align:start position:0% A local system git installation is not 02:28:43.920 --> 02:28:46.870 align:start position:0% A local system git installation is not found.<02:28:45.280> The<02:28:45.520> active<02:28:45.920> folder<02:28:46.319> is<02:28:46.640> not 02:28:46.870 --> 02:28:46.880 align:start position:0% found. The active folder is not 02:28:46.880 --> 02:28:50.230 align:start position:0% found. The active folder is not recognized<02:28:47.439> as<02:28:47.680> a<02:28:47.840> valid<02:28:48.160> git<02:28:48.479> repository. 02:28:50.230 --> 02:28:50.240 align:start position:0% recognized as a valid git repository. 02:28:50.240 --> 02:28:52.870 align:start position:0% recognized as a valid git repository. Two<02:28:50.640> concrete<02:28:51.200> system<02:28:51.600> blockers<02:28:52.399> prevent<02:28:52.720> the 02:28:52.870 --> 02:28:52.880 align:start position:0% Two concrete system blockers prevent the 02:28:52.880 --> 02:28:56.309 align:start position:0% Two concrete system blockers prevent the code<02:28:53.200> push<02:28:53.520> process.<02:28:54.960> First,<02:28:55.760> the<02:28:55.920> Git 02:28:56.309 --> 02:28:56.319 align:start position:0% code push process. First, the Git 02:28:56.319 --> 02:28:57.990 align:start position:0% code push process. First, the Git software<02:28:56.720> is<02:28:56.960> not<02:28:57.200> installed<02:28:57.600> on<02:28:57.760> the 02:28:57.990 --> 02:28:58.000 align:start position:0% software is not installed on the 02:28:58.000 --> 02:28:59.349 align:start position:0% software is not installed on the machine. 02:28:59.349 --> 02:28:59.359 align:start position:0% machine. 02:28:59.359 --> 02:29:01.750 align:start position:0% machine. Second,<02:29:00.240> there<02:29:00.399> is<02:29:00.560> no<02:29:00.880> connected<02:29:01.359> remote 02:29:01.750 --> 02:29:01.760 align:start position:0% Second, there is no connected remote 02:29:01.760 --> 02:29:04.469 align:start position:0% Second, there is no connected remote GitHub<02:29:02.240> repository<02:29:02.720> available. 02:29:04.469 --> 02:29:04.479 align:start position:0% GitHub repository available. 02:29:04.479 --> 02:29:06.230 align:start position:0% GitHub repository available. Suggested<02:29:05.040> options<02:29:05.439> are<02:29:05.680> provided<02:29:06.080> to 02:29:06.230 --> 02:29:06.240 align:start position:0% Suggested options are provided to 02:29:06.240 --> 02:29:08.790 align:start position:0% Suggested options are provided to resolve<02:29:06.560> these<02:29:06.880> software<02:29:07.280> issues. 02:29:08.790 --> 02:29:08.800 align:start position:0% resolve these software issues. 02:29:08.800 --> 02:29:11.110 align:start position:0% resolve these software issues. A<02:29:09.040> new<02:29:09.280> public<02:29:09.680> code<02:29:10.080> repository<02:29:10.640> must<02:29:10.960> be 02:29:11.110 --> 02:29:11.120 align:start position:0% A new public code repository must be 02:29:11.120 --> 02:29:14.389 align:start position:0% A new public code repository must be created<02:29:11.600> first.<02:29:12.880> The<02:29:13.120> main<02:29:13.439> GitHub<02:29:13.920> website 02:29:14.389 --> 02:29:14.399 align:start position:0% created first. The main GitHub website 02:29:14.399 --> 02:29:16.469 align:start position:0% created first. The main GitHub website is<02:29:14.640> open<02:29:14.880> to<02:29:15.200> create<02:29:15.439> a<02:29:15.760> new<02:29:16.000> online 02:29:16.469 --> 02:29:16.479 align:start position:0% is open to create a new online 02:29:16.479 --> 02:29:17.990 align:start position:0% is open to create a new online repository. 02:29:17.990 --> 02:29:18.000 align:start position:0% repository. 02:29:18.000 --> 02:29:21.110 align:start position:0% repository. The<02:29:18.240> user<02:29:18.640> login<02:29:19.040> credentials<02:29:19.520> are<02:29:19.760> saved.<02:29:20.960> A 02:29:21.110 --> 02:29:21.120 align:start position:0% The user login credentials are saved. A 02:29:21.120 --> 02:29:23.830 align:start position:0% The user login credentials are saved. A new<02:29:21.359> repository<02:29:21.920> named<02:29:22.800> one<02:29:23.120> go<02:29:23.439> project 02:29:23.830 --> 02:29:23.840 align:start position:0% new repository named one go project 02:29:23.840 --> 02:29:26.309 align:start position:0% new repository named one go project healthcare<02:29:24.399> is<02:29:24.720> created. 02:29:26.309 --> 02:29:26.319 align:start position:0% healthcare is created. 02:29:26.319 --> 02:29:29.429 align:start position:0% healthcare is created. The<02:29:26.640> access<02:29:27.120> visibility<02:29:27.680> is<02:29:27.920> set<02:29:28.080> to<02:29:28.240> public. 02:29:29.429 --> 02:29:29.439 align:start position:0% The access visibility is set to public. 02:29:29.439 --> 02:29:31.190 align:start position:0% The access visibility is set to public. The<02:29:29.680> repository<02:29:30.240> creation<02:29:30.720> process 02:29:31.190 --> 02:29:31.200 align:start position:0% The repository creation process 02:29:31.200 --> 02:29:34.070 align:start position:0% The repository creation process completes.<02:29:32.560> The<02:29:32.880> internet<02:29:33.280> repository<02:29:33.840> link 02:29:34.070 --> 02:29:34.080 align:start position:0% completes. The internet repository link 02:29:34.080 --> 02:29:36.790 align:start position:0% completes. The internet repository link is<02:29:34.319> now<02:29:34.560> available<02:29:34.880> for<02:29:35.200> connection. 02:29:36.790 --> 02:29:36.800 align:start position:0% is now available for connection. 02:29:36.800 --> 02:29:38.870 align:start position:0% is now available for connection. The<02:29:37.120> required<02:29:37.520> remote<02:29:37.920> repository<02:29:38.399> link<02:29:38.720> is 02:29:38.870 --> 02:29:38.880 align:start position:0% The required remote repository link is 02:29:38.880 --> 02:29:41.910 align:start position:0% The required remote repository link is copied<02:29:39.280> from<02:29:39.439> GitHub.<02:29:40.880> This<02:29:41.120> specific<02:29:41.600> link 02:29:41.910 --> 02:29:41.920 align:start position:0% copied from GitHub. This specific link 02:29:41.920 --> 02:29:44.150 align:start position:0% copied from GitHub. This specific link is<02:29:42.160> pasted<02:29:42.560> into<02:29:42.800> the<02:29:43.040> system<02:29:43.359> prompt<02:29:43.920> to 02:29:44.150 --> 02:29:44.160 align:start position:0% is pasted into the system prompt to 02:29:44.160 --> 02:29:46.550 align:start position:0% is pasted into the system prompt to initiate<02:29:44.560> the<02:29:44.800> web<02:29:45.040> connection. 02:29:46.550 --> 02:29:46.560 align:start position:0% initiate the web connection. 02:29:46.560 --> 02:29:48.950 align:start position:0% initiate the web connection. The<02:29:46.800> active<02:29:47.280> system<02:29:47.760> processes<02:29:48.319> the<02:29:48.560> target 02:29:48.950 --> 02:29:48.960 align:start position:0% The active system processes the target 02:29:48.960 --> 02:29:52.309 align:start position:0% The active system processes the target online<02:29:49.439> repository<02:29:50.000> URL.<02:29:51.439> It<02:29:51.680> checks<02:29:52.000> whether 02:29:52.309 --> 02:29:52.319 align:start position:0% online repository URL. It checks whether 02:29:52.319 --> 02:29:54.469 align:start position:0% online repository URL. It checks whether the<02:29:52.560> main<02:29:52.800> GitHub<02:29:53.359> connector<02:29:54.000> has<02:29:54.240> the 02:29:54.469 --> 02:29:54.479 align:start position:0% the main GitHub connector has the 02:29:54.479 --> 02:29:57.670 align:start position:0% the main GitHub connector has the necessary<02:29:55.040> account<02:29:55.439> access.<02:29:56.800> The<02:29:57.040> code<02:29:57.359> push 02:29:57.670 --> 02:29:57.680 align:start position:0% necessary account access. The code push 02:29:57.680 --> 02:30:00.630 align:start position:0% necessary account access. The code push access<02:29:58.000> is<02:29:58.240> verified.<02:29:59.600> The<02:29:59.920> current<02:30:00.240> local 02:30:00.630 --> 02:30:00.640 align:start position:0% access is verified. The current local 02:30:00.640 --> 02:30:03.270 align:start position:0% access is verified. The current local project<02:30:01.040> files<02:30:01.359> are<02:30:01.520> being<02:30:01.760> read<02:30:02.000> in<02:30:02.160> order. 02:30:03.270 --> 02:30:03.280 align:start position:0% project files are being read in order. 02:30:03.280 --> 02:30:05.190 align:start position:0% project files are being read in order. The<02:30:03.600> development<02:30:04.000> plan<02:30:04.319> is<02:30:04.479> to<02:30:04.720> publish<02:30:05.040> them 02:30:05.190 --> 02:30:05.200 align:start position:0% The development plan is to publish them 02:30:05.200 --> 02:30:08.309 align:start position:0% The development plan is to publish them into<02:30:05.439> the<02:30:05.680> main<02:30:05.920> code<02:30:06.319> branch.<02:30:07.680> This<02:30:07.920> action 02:30:08.309 --> 02:30:08.319 align:start position:0% into the main code branch. This action 02:30:08.319 --> 02:30:10.150 align:start position:0% into the main code branch. This action is<02:30:08.560> done<02:30:08.720> through<02:30:08.960> the<02:30:09.120> built-in<02:30:09.600> GitHub 02:30:10.150 --> 02:30:10.160 align:start position:0% is done through the built-in GitHub 02:30:10.160 --> 02:30:11.670 align:start position:0% is done through the built-in GitHub connector. 02:30:11.670 --> 02:30:11.680 align:start position:0% connector. 02:30:11.680 --> 02:30:14.150 align:start position:0% connector. The<02:30:12.000> raw<02:30:12.319> text<02:30:12.720> content<02:30:13.200> of<02:30:13.439> all<02:30:13.760> project 02:30:14.150 --> 02:30:14.160 align:start position:0% The raw text content of all project 02:30:14.160 --> 02:30:16.230 align:start position:0% The raw text content of all project files<02:30:14.479> is<02:30:14.720> extracted. 02:30:16.230 --> 02:30:16.240 align:start position:0% files is extracted. 02:30:16.240 --> 02:30:18.070 align:start position:0% files is extracted. The<02:30:16.479> public<02:30:16.800> code<02:30:17.040> files<02:30:17.439> are<02:30:17.600> prepared<02:30:17.840> for 02:30:18.070 --> 02:30:18.080 align:start position:0% The public code files are prepared for 02:30:18.080 --> 02:30:21.270 align:start position:0% The public code files are prepared for web<02:30:18.319> publishing.<02:30:19.760> A<02:30:20.080> small<02:30:20.399> project<02:30:20.800> readme 02:30:21.270 --> 02:30:21.280 align:start position:0% web publishing. A small project readme 02:30:21.280 --> 02:30:22.870 align:start position:0% web publishing. A small project readme file<02:30:21.520> is<02:30:21.760> also<02:30:22.000> generated<02:30:22.479> for<02:30:22.720> the 02:30:22.870 --> 02:30:22.880 align:start position:0% file is also generated for the 02:30:22.880 --> 02:30:24.550 align:start position:0% file is also generated for the repository. 02:30:24.550 --> 02:30:24.560 align:start position:0% repository. 02:30:24.560 --> 02:30:27.110 align:start position:0% repository. At<02:30:24.800> this<02:30:25.040> moment,<02:30:25.600> the<02:30:25.920> online<02:30:26.319> repository<02:30:26.880> is 02:30:27.110 --> 02:30:27.120 align:start position:0% At this moment, the online repository is 02:30:27.120 --> 02:30:30.550 align:start position:0% At this moment, the online repository is empty.<02:30:28.399> Refreshing<02:30:28.880> the<02:30:29.120> web<02:30:29.359> GitHub<02:30:29.840> page 02:30:30.550 --> 02:30:30.560 align:start position:0% empty. Refreshing the web GitHub page 02:30:30.560 --> 02:30:33.910 align:start position:0% empty. Refreshing the web GitHub page confirms<02:30:31.120> no<02:30:31.439> files<02:30:31.760> are<02:30:31.920> uploaded<02:30:32.399> yet.<02:30:33.680> The 02:30:33.910 --> 02:30:33.920 align:start position:0% confirms no files are uploaded yet. The 02:30:33.920 --> 02:30:35.670 align:start position:0% confirms no files are uploaded yet. The background<02:30:34.399> publishing<02:30:34.880> application<02:30:35.439> is 02:30:35.670 --> 02:30:35.680 align:start position:0% background publishing application is 02:30:35.680 --> 02:30:38.150 align:start position:0% background publishing application is running<02:30:35.840> the<02:30:36.000> pull<02:30:36.319> request.<02:30:37.680> Once<02:30:38.000> the 02:30:38.150 --> 02:30:38.160 align:start position:0% running the pull request. Once the 02:30:38.160 --> 02:30:40.389 align:start position:0% running the pull request. Once the upload<02:30:38.560> process<02:30:38.960> is<02:30:39.120> approved,<02:30:39.840> the<02:30:40.160> new 02:30:40.389 --> 02:30:40.399 align:start position:0% upload process is approved, the new 02:30:40.399 --> 02:30:43.349 align:start position:0% upload process is approved, the new content<02:30:40.800> will<02:30:40.960> be<02:30:41.120> available<02:30:41.600> online. 02:30:43.349 --> 02:30:43.359 align:start position:0% content will be available online. 02:30:43.359 --> 02:30:45.110 align:start position:0% content will be available online. The<02:30:43.680> computer<02:30:44.080> system<02:30:44.479> waits<02:30:44.800> for<02:30:44.960> the 02:30:45.110 --> 02:30:45.120 align:start position:0% The computer system waits for the 02:30:45.120 --> 02:30:46.710 align:start position:0% The computer system waits for the background<02:30:45.600> publishing<02:30:46.080> process<02:30:46.479> to 02:30:46.710 --> 02:30:46.720 align:start position:0% background publishing process to 02:30:46.720 --> 02:30:48.230 align:start position:0% background publishing process to execute. 02:30:48.230 --> 02:30:48.240 align:start position:0% execute. 02:30:48.240 --> 02:30:50.150 align:start position:0% execute. A<02:30:48.560> new<02:30:48.720> approval<02:30:49.200> prompt<02:30:49.520> appears<02:30:49.840> on<02:30:50.000> the 02:30:50.150 --> 02:30:50.160 align:start position:0% A new approval prompt appears on the 02:30:50.160 --> 02:30:52.870 align:start position:0% A new approval prompt appears on the screen.<02:30:51.280> It<02:30:51.520> requests<02:30:51.920> security<02:30:52.399> permission 02:30:52.870 --> 02:30:52.880 align:start position:0% screen. It requests security permission 02:30:52.880 --> 02:30:55.110 align:start position:0% screen. It requests security permission to<02:30:53.040> allow<02:30:53.359> GitHub<02:30:53.840> to<02:30:54.000> run<02:30:54.160> the<02:30:54.399> file<02:30:54.640> creation 02:30:55.110 --> 02:30:55.120 align:start position:0% to allow GitHub to run the file creation 02:30:55.120 --> 02:30:57.990 align:start position:0% to allow GitHub to run the file creation tool.<02:30:56.240> The<02:30:56.479> required<02:30:56.960> permission<02:30:57.359> is<02:30:57.520> granted 02:30:57.990 --> 02:30:58.000 align:start position:0% tool. The required permission is granted 02:30:58.000 --> 02:31:01.110 align:start position:0% tool. The required permission is granted by<02:30:58.240> selecting<02:30:58.640> the<02:30:59.040> allow<02:30:59.520> option.<02:31:00.880> This 02:31:01.110 --> 02:31:01.120 align:start position:0% by selecting the allow option. This 02:31:01.120 --> 02:31:03.830 align:start position:0% by selecting the allow option. This choice<02:31:01.520> ensures<02:31:02.080> automatic<02:31:02.640> file<02:31:03.040> creation 02:31:03.830 --> 02:31:03.840 align:start position:0% choice ensures automatic file creation 02:31:03.840 --> 02:31:05.590 align:start position:0% choice ensures automatic file creation without<02:31:04.240> repetitive<02:31:04.800> manual<02:31:05.280> user 02:31:05.590 --> 02:31:05.600 align:start position:0% without repetitive manual user 02:31:05.600 --> 02:31:07.190 align:start position:0% without repetitive manual user approvals. 02:31:07.190 --> 02:31:07.200 align:start position:0% approvals. 02:31:07.200 --> 02:31:09.510 align:start position:0% approvals. A<02:31:07.439> subsequent<02:31:08.000> system<02:31:08.319> request<02:31:08.880> asks<02:31:09.280> to 02:31:09.510 --> 02:31:09.520 align:start position:0% A subsequent system request asks to 02:31:09.520 --> 02:31:12.389 align:start position:0% A subsequent system request asks to create<02:31:09.920> code<02:31:10.240> git<02:31:10.560> blobs.<02:31:11.680> This<02:31:11.920> security 02:31:12.389 --> 02:31:12.399 align:start position:0% create code git blobs. This security 02:31:12.399 --> 02:31:15.190 align:start position:0% create code git blobs. This security permission<02:31:12.880> is<02:31:13.120> also<02:31:13.359> allowed<02:31:13.680> to<02:31:13.920> proceed. 02:31:15.190 --> 02:31:15.200 align:start position:0% permission is also allowed to proceed. 02:31:15.200 --> 02:31:17.190 align:start position:0% permission is also allowed to proceed. These<02:31:15.600> technical<02:31:16.000> steps<02:31:16.319> are<02:31:16.479> necessary<02:31:16.960> to 02:31:17.190 --> 02:31:17.200 align:start position:0% These technical steps are necessary to 02:31:17.200 --> 02:31:19.510 align:start position:0% These technical steps are necessary to transfer<02:31:17.600> the<02:31:17.840> local<02:31:18.160> workspace<02:31:18.720> files<02:31:19.280> to 02:31:19.510 --> 02:31:19.520 align:start position:0% transfer the local workspace files to 02:31:19.520 --> 02:31:22.150 align:start position:0% transfer the local workspace files to the<02:31:19.680> remote<02:31:20.080> web<02:31:20.319> environment.<02:31:21.760> If<02:31:21.920> the 02:31:22.150 --> 02:31:22.160 align:start position:0% the remote web environment. If the 02:31:22.160 --> 02:31:23.670 align:start position:0% the remote web environment. If the source<02:31:22.479> code<02:31:22.720> is<02:31:22.880> left<02:31:23.040> in<02:31:23.200> the<02:31:23.359> local 02:31:23.670 --> 02:31:23.680 align:start position:0% source code is left in the local 02:31:23.680 --> 02:31:25.830 align:start position:0% source code is left in the local workspace,<02:31:24.640> it<02:31:24.880> cannot<02:31:25.120> be<02:31:25.280> shared<02:31:25.600> or 02:31:25.830 --> 02:31:25.840 align:start position:0% workspace, it cannot be shared or 02:31:25.840 --> 02:31:28.389 align:start position:0% workspace, it cannot be shared or deployed.<02:31:27.120> Moving<02:31:27.439> it<02:31:27.680> to<02:31:27.840> the<02:31:28.000> online 02:31:28.389 --> 02:31:28.399 align:start position:0% deployed. Moving it to the online 02:31:28.399 --> 02:31:30.550 align:start position:0% deployed. Moving it to the online repository<02:31:29.359> ensures<02:31:29.840> the<02:31:30.080> system<02:31:30.319> is 02:31:30.550 --> 02:31:30.560 align:start position:0% repository ensures the system is 02:31:30.560 --> 02:31:32.150 align:start position:0% repository ensures the system is integrated. 02:31:32.150 --> 02:31:32.160 align:start position:0% integrated. 02:31:32.160 --> 02:31:33.830 align:start position:0% integrated. Two<02:31:32.479> separate<02:31:32.880> system<02:31:33.200> blockers<02:31:33.600> are 02:31:33.830 --> 02:31:33.840 align:start position:0% Two separate system blockers are 02:31:33.840 --> 02:31:36.389 align:start position:0% Two separate system blockers are identified<02:31:34.319> again.<02:31:35.359> The<02:31:35.600> local<02:31:36.000> machine 02:31:36.389 --> 02:31:36.399 align:start position:0% identified again. The local machine 02:31:36.399 --> 02:31:38.389 align:start position:0% identified again. The local machine still<02:31:36.640> lacks<02:31:36.960> a<02:31:37.200> local<02:31:37.520> software<02:31:38.000> git 02:31:38.389 --> 02:31:38.399 align:start position:0% still lacks a local software git 02:31:38.399 --> 02:31:41.349 align:start position:0% still lacks a local software git installation.<02:31:39.840> The<02:31:40.080> web<02:31:40.319> GitHub<02:31:40.800> integration 02:31:41.349 --> 02:31:41.359 align:start position:0% installation. The web GitHub integration 02:31:41.359 --> 02:31:43.990 align:start position:0% installation. The web GitHub integration can<02:31:41.600> read<02:31:41.920> files<02:31:42.640> but<02:31:42.960> write<02:31:43.280> operations<02:31:43.760> are 02:31:43.990 --> 02:31:44.000 align:start position:0% can read files but write operations are 02:31:44.000 --> 02:31:46.630 align:start position:0% can read files but write operations are blocked.<02:31:45.359> This<02:31:45.600> problem<02:31:46.000> happens<02:31:46.319> because 02:31:46.630 --> 02:31:46.640 align:start position:0% blocked. This problem happens because 02:31:46.640 --> 02:31:48.630 align:start position:0% blocked. This problem happens because the<02:31:46.880> integration<02:31:47.520> cannot<02:31:48.000> access<02:31:48.319> the 02:31:48.630 --> 02:31:48.640 align:start position:0% the integration cannot access the 02:31:48.640 --> 02:31:51.429 align:start position:0% the integration cannot access the necessary<02:31:49.120> developer<02:31:49.600> tools.<02:31:50.800> To<02:31:51.040> resolve 02:31:51.429 --> 02:31:51.439 align:start position:0% necessary developer tools. To resolve 02:31:51.439 --> 02:31:53.670 align:start position:0% necessary developer tools. To resolve this<02:31:51.680> exact<02:31:52.080> issue,<02:31:52.800> a<02:31:53.040> local<02:31:53.359> system 02:31:53.670 --> 02:31:53.680 align:start position:0% this exact issue, a local system 02:31:53.680 --> 02:31:55.990 align:start position:0% this exact issue, a local system installation<02:31:54.240> is<02:31:54.479> required. 02:31:55.990 --> 02:31:56.000 align:start position:0% installation is required. 02:31:56.000 --> 02:31:58.950 align:start position:0% installation is required. A<02:31:56.240> new<02:31:56.479> internet<02:31:56.880> browser<02:31:57.200> tab<02:31:57.520> is<02:31:57.680> opened.<02:31:58.720> A 02:31:58.950 --> 02:31:58.960 align:start position:0% A new internet browser tab is opened. A 02:31:58.960 --> 02:32:01.270 align:start position:0% A new internet browser tab is opened. A search<02:31:59.280> query<02:31:59.680> for<02:32:00.160> install<02:32:00.640> Git<02:32:01.040> is 02:32:01.270 --> 02:32:01.280 align:start position:0% search query for install Git is 02:32:01.280 --> 02:32:02.790 align:start position:0% search query for install Git is executed. 02:32:02.790 --> 02:32:02.800 align:start position:0% executed. 02:32:02.800 --> 02:32:04.710 align:start position:0% executed. The<02:32:03.040> official<02:32:03.439> Git<02:32:03.760> software<02:32:04.160> installation 02:32:04.710 --> 02:32:04.720 align:start position:0% The official Git software installation 02:32:04.720 --> 02:32:07.830 align:start position:0% The official Git software installation page<02:32:05.040> is<02:32:05.280> accessed.<02:32:06.560> The<02:32:06.880> Windows<02:32:07.280> desktop 02:32:07.830 --> 02:32:07.840 align:start position:0% page is accessed. The Windows desktop 02:32:07.840 --> 02:32:10.790 align:start position:0% page is accessed. The Windows desktop operating<02:32:08.319> system<02:32:08.640> option<02:32:09.040> is<02:32:09.200> selected.<02:32:10.560> The 02:32:10.790 --> 02:32:10.800 align:start position:0% operating system option is selected. The 02:32:10.800 --> 02:32:12.389 align:start position:0% operating system option is selected. The standalone<02:32:11.359> software<02:32:11.760> installer<02:32:12.240> for 02:32:12.389 --> 02:32:12.399 align:start position:0% standalone software installer for 02:32:12.399 --> 02:32:15.190 align:start position:0% standalone software installer for Windows<02:32:12.800> is<02:32:13.040> downloaded.<02:32:14.479> The<02:32:14.720> software 02:32:15.190 --> 02:32:15.200 align:start position:0% Windows is downloaded. The software 02:32:15.200 --> 02:32:17.190 align:start position:0% Windows is downloaded. The software download<02:32:15.680> process<02:32:16.080> will<02:32:16.319> take<02:32:16.560> some<02:32:16.800> time<02:32:16.960> to 02:32:17.190 --> 02:32:17.200 align:start position:0% download process will take some time to 02:32:17.200 --> 02:32:19.990 align:start position:0% download process will take some time to finish.<02:32:18.399> The<02:32:18.720> installation<02:32:19.280> setup<02:32:19.600> will<02:32:19.840> be 02:32:19.990 --> 02:32:20.000 align:start position:0% finish. The installation setup will be 02:32:20.000 --> 02:32:23.429 align:start position:0% finish. The installation setup will be executed<02:32:20.560> soon.<02:32:22.000> The<02:32:22.240> main<02:32:22.560> Git<02:32:22.960> installer 02:32:23.429 --> 02:32:23.439 align:start position:0% executed soon. The main Git installer 02:32:23.439 --> 02:32:26.230 align:start position:0% executed soon. The main Git installer file<02:32:23.760> is<02:32:24.000> saved<02:32:24.240> to<02:32:24.479> the<02:32:24.640> computer<02:32:24.960> desktop. 02:32:26.230 --> 02:32:26.240 align:start position:0% file is saved to the computer desktop. 02:32:26.240 --> 02:32:28.070 align:start position:0% file is saved to the computer desktop. The<02:32:26.479> file<02:32:26.800> download<02:32:27.280> continues<02:32:27.760> in<02:32:27.920> the 02:32:28.070 --> 02:32:28.080 align:start position:0% The file download continues in the 02:32:28.080 --> 02:32:30.870 align:start position:0% The file download continues in the background.<02:32:29.439> In<02:32:29.600> the<02:32:29.760> meantime,<02:32:30.560> the 02:32:30.870 --> 02:32:30.880 align:start position:0% background. In the meantime, the 02:32:30.880 --> 02:32:32.950 align:start position:0% background. In the meantime, the computer<02:32:31.280> system<02:32:31.600> provides<02:32:32.000> a<02:32:32.160> text<02:32:32.479> list<02:32:32.720> of 02:32:32.950 --> 02:32:32.960 align:start position:0% computer system provides a text list of 02:32:32.960 --> 02:32:35.750 align:start position:0% computer system provides a text list of terminal<02:32:33.359> commands.<02:32:34.800> These<02:32:35.120> commands<02:32:35.520> are 02:32:35.750 --> 02:32:35.760 align:start position:0% terminal commands. These commands are 02:32:35.760 --> 02:32:39.030 align:start position:0% terminal commands. These commands are required<02:32:36.080> to<02:32:36.319> push<02:32:36.560> the<02:32:36.800> source<02:32:37.040> code<02:32:37.359> by<02:32:37.600> hand 02:32:39.030 --> 02:32:39.040 align:start position:0% required to push the source code by hand 02:32:39.040 --> 02:32:41.670 align:start position:0% required to push the source code by hand before<02:32:39.520> executing<02:32:40.080> them.<02:32:40.800> Remote<02:32:41.120> repository 02:32:41.670 --> 02:32:41.680 align:start position:0% before executing them. Remote repository 02:32:41.680 --> 02:32:44.550 align:start position:0% before executing them. Remote repository permissions<02:32:42.160> must<02:32:42.479> be<02:32:42.640> verified.<02:32:44.080> The<02:32:44.319> main 02:32:44.550 --> 02:32:44.560 align:start position:0% permissions must be verified. The main 02:32:44.560 --> 02:32:46.950 align:start position:0% permissions must be verified. The main GitHub<02:32:45.120> settings<02:32:45.520> page<02:32:45.760> is<02:32:46.000> opened<02:32:46.399> to<02:32:46.560> ensure 02:32:46.950 --> 02:32:46.960 align:start position:0% GitHub settings page is opened to ensure 02:32:46.960 --> 02:32:49.830 align:start position:0% GitHub settings page is opened to ensure proper<02:32:47.280> developer<02:32:47.840> access<02:32:48.160> rights.<02:32:49.600> The 02:32:49.830 --> 02:32:49.840 align:start position:0% proper developer access rights. The 02:32:49.840 --> 02:32:51.830 align:start position:0% proper developer access rights. The account<02:32:50.240> security<02:32:50.720> and<02:32:50.960> variables<02:32:51.520> section 02:32:51.830 --> 02:32:51.840 align:start position:0% account security and variables section 02:32:51.840 --> 02:32:54.550 align:start position:0% account security and variables section is<02:32:52.080> examined.<02:32:53.439> The<02:32:53.680> account<02:32:54.000> moderation 02:32:54.550 --> 02:32:54.560 align:start position:0% is examined. The account moderation 02:32:54.560 --> 02:32:57.510 align:start position:0% is examined. The account moderation options<02:32:54.960> are<02:32:55.120> also<02:32:55.439> visible.<02:32:56.800> Navigating<02:32:57.359> to 02:32:57.510 --> 02:32:57.520 align:start position:0% options are also visible. Navigating to 02:32:57.520 --> 02:32:59.590 align:start position:0% options are also visible. Navigating to the<02:32:57.760> repository<02:32:58.319> security<02:32:58.800> permissions<02:32:59.359> is 02:32:59.590 --> 02:32:59.600 align:start position:0% the repository security permissions is 02:32:59.600 --> 02:33:03.030 align:start position:0% the repository security permissions is necessary<02:33:00.080> to<02:33:00.319> allow<02:33:00.720> new<02:33:00.960> code<02:33:01.280> uploads. 02:33:03.030 --> 02:33:03.040 align:start position:0% necessary to allow new code uploads. 02:33:03.040 --> 02:33:04.950 align:start position:0% necessary to allow new code uploads. The<02:33:03.280> active<02:33:03.680> pull<02:33:04.000> request<02:33:04.399> settings<02:33:04.800> are 02:33:04.950 --> 02:33:04.960 align:start position:0% The active pull request settings are 02:33:04.960 --> 02:33:07.670 align:start position:0% The active pull request settings are reviewed.<02:33:06.160> The<02:33:06.479> code<02:33:06.720> merge<02:33:07.120> commits<02:33:07.439> and 02:33:07.670 --> 02:33:07.680 align:start position:0% reviewed. The code merge commits and 02:33:07.680 --> 02:33:09.750 align:start position:0% reviewed. The code merge commits and squash<02:33:08.080> merging<02:33:08.479> options<02:33:08.880> are<02:33:09.120> enabled<02:33:09.520> by 02:33:09.750 --> 02:33:09.760 align:start position:0% squash merging options are enabled by 02:33:09.760 --> 02:33:12.710 align:start position:0% squash merging options are enabled by default.<02:33:11.200> The<02:33:11.439> version<02:33:11.840> commit<02:33:12.160> settings<02:33:12.479> and 02:33:12.710 --> 02:33:12.720 align:start position:0% default. The version commit settings and 02:33:12.720 --> 02:33:15.110 align:start position:0% default. The version commit settings and archive<02:33:13.200> features<02:33:13.520> are<02:33:13.760> checked.<02:33:14.880> The 02:33:15.110 --> 02:33:15.120 align:start position:0% archive features are checked. The 02:33:15.120 --> 02:33:17.030 align:start position:0% archive features are checked. The critical<02:33:15.600> danger<02:33:16.000> zone<02:33:16.240> is<02:33:16.399> avoided<02:33:16.880> to 02:33:17.030 --> 02:33:17.040 align:start position:0% critical danger zone is avoided to 02:33:17.040 --> 02:33:19.910 align:start position:0% critical danger zone is avoided to prevent<02:33:17.439> accidental<02:33:18.080> project<02:33:18.399> deletion. 02:33:19.910 --> 02:33:19.920 align:start position:0% prevent accidental project deletion. 02:33:19.920 --> 02:33:21.750 align:start position:0% prevent accidental project deletion. Everything<02:33:20.319> appears<02:33:20.720> to<02:33:20.880> be<02:33:20.960> configured<02:33:21.359> in<02:33:21.600> a 02:33:21.750 --> 02:33:21.760 align:start position:0% Everything appears to be configured in a 02:33:21.760 --> 02:33:24.710 align:start position:0% Everything appears to be configured in a proper<02:33:22.000> state.<02:33:23.280> The<02:33:23.439> Git<02:33:23.840> software<02:33:24.240> installer 02:33:24.710 --> 02:33:24.720 align:start position:0% proper state. The Git software installer 02:33:24.720 --> 02:33:26.870 align:start position:0% proper state. The Git software installer download<02:33:25.120> is<02:33:25.359> now<02:33:25.600> complete.<02:33:26.640> The 02:33:26.870 --> 02:33:26.880 align:start position:0% download is now complete. The 02:33:26.880 --> 02:33:29.030 align:start position:0% download is now complete. The application<02:33:27.520> setup<02:33:27.920> file<02:33:28.160> will<02:33:28.319> be<02:33:28.479> executed 02:33:29.030 --> 02:33:29.040 align:start position:0% application setup file will be executed 02:33:29.040 --> 02:33:30.870 align:start position:0% application setup file will be executed next<02:33:29.359> to<02:33:29.600> install<02:33:29.920> the<02:33:30.080> software<02:33:30.479> on<02:33:30.640> the 02:33:30.870 --> 02:33:30.880 align:start position:0% next to install the software on the 02:33:30.880 --> 02:33:32.150 align:start position:0% next to install the software on the computer. 02:33:32.150 --> 02:33:32.160 align:start position:0% computer. 02:33:32.160 --> 02:33:34.309 align:start position:0% computer. The<02:33:32.399> downloaded<02:33:32.960> Git<02:33:33.280> software<02:33:33.680> installer<02:33:34.160> is 02:33:34.309 --> 02:33:34.319 align:start position:0% The downloaded Git software installer is 02:33:34.319 --> 02:33:37.270 align:start position:0% The downloaded Git software installer is executed<02:33:34.800> from<02:33:35.040> the<02:33:35.200> computer<02:33:35.600> desktop.<02:33:36.960> The 02:33:37.270 --> 02:33:37.280 align:start position:0% executed from the computer desktop. The 02:33:37.280 --> 02:33:39.190 align:start position:0% executed from the computer desktop. The application<02:33:37.840> setup<02:33:38.240> wizard<02:33:38.560> appears<02:33:38.880> on<02:33:39.040> the 02:33:39.190 --> 02:33:39.200 align:start position:0% application setup wizard appears on the 02:33:39.200 --> 02:33:41.670 align:start position:0% application setup wizard appears on the screen.<02:33:40.479> The<02:33:40.720> standard<02:33:41.200> default 02:33:41.670 --> 02:33:41.680 align:start position:0% screen. The standard default 02:33:41.680 --> 02:33:43.510 align:start position:0% screen. The standard default installation<02:33:42.240> options<02:33:42.640> are<02:33:42.880> selected<02:33:43.280> by 02:33:43.510 --> 02:33:43.520 align:start position:0% installation options are selected by 02:33:43.520 --> 02:33:46.550 align:start position:0% installation options are selected by clicking<02:33:43.840> the<02:33:44.080> next<02:33:44.319> button<02:33:44.720> multiple<02:33:45.200> times. 02:33:46.550 --> 02:33:46.560 align:start position:0% clicking the next button multiple times. 02:33:46.560 --> 02:33:48.469 align:start position:0% clicking the next button multiple times. The<02:33:46.800> default<02:33:47.280> components<02:33:47.760> are<02:33:48.000> chosen<02:33:48.240> for 02:33:48.469 --> 02:33:48.479 align:start position:0% The default components are chosen for 02:33:48.479 --> 02:33:50.389 align:start position:0% The default components are chosen for the<02:33:48.640> system<02:33:48.880> installation. 02:33:50.389 --> 02:33:50.399 align:start position:0% the system installation. 02:33:50.399 --> 02:33:53.429 align:start position:0% the system installation. The<02:33:50.640> default<02:33:51.040> code<02:33:51.359> editor<02:33:51.760> is<02:33:51.920> maintained. 02:33:53.429 --> 02:33:53.439 align:start position:0% The default code editor is maintained. 02:33:53.439 --> 02:33:55.030 align:start position:0% The default code editor is maintained. The<02:33:53.680> initial<02:33:54.080> project<02:33:54.399> branch<02:33:54.800> name 02:33:55.030 --> 02:33:55.040 align:start position:0% The initial project branch name 02:33:55.040 --> 02:33:56.870 align:start position:0% The initial project branch name configuration<02:33:55.680> is<02:33:55.920> left<02:33:56.160> as<02:33:56.319> a<02:33:56.560> default 02:33:56.870 --> 02:33:56.880 align:start position:0% configuration is left as a default 02:33:56.880 --> 02:33:59.910 align:start position:0% configuration is left as a default choice.<02:33:58.240> The<02:33:58.560> system<02:33:58.880> path<02:33:59.200> environment<02:33:59.680> is 02:33:59.910 --> 02:33:59.920 align:start position:0% choice. The system path environment is 02:33:59.920 --> 02:34:01.510 align:start position:0% choice. The system path environment is updated. 02:34:01.510 --> 02:34:01.520 align:start position:0% updated. 02:34:01.520 --> 02:34:03.670 align:start position:0% updated. The<02:34:01.760> software<02:34:02.160> installation<02:34:02.800> process<02:34:03.280> begins 02:34:03.670 --> 02:34:03.680 align:start position:0% The software installation process begins 02:34:03.680 --> 02:34:06.710 align:start position:0% The software installation process begins extracting<02:34:04.319> core<02:34:04.640> files.<02:34:06.080> The<02:34:06.319> visual 02:34:06.710 --> 02:34:06.720 align:start position:0% extracting core files. The visual 02:34:06.720 --> 02:34:08.550 align:start position:0% extracting core files. The visual progress<02:34:07.200> bar<02:34:07.520> indicates<02:34:08.000> the<02:34:08.240> current 02:34:08.550 --> 02:34:08.560 align:start position:0% progress bar indicates the current 02:34:08.560 --> 02:34:10.790 align:start position:0% progress bar indicates the current installation<02:34:09.200> status. 02:34:10.790 --> 02:34:10.800 align:start position:0% installation status. 02:34:10.800 --> 02:34:12.710 align:start position:0% installation status. The<02:34:11.040> program<02:34:11.439> installation<02:34:12.000> is<02:34:12.240> completed 02:34:12.710 --> 02:34:12.720 align:start position:0% The program installation is completed 02:34:12.720 --> 02:34:15.429 align:start position:0% The program installation is completed without<02:34:13.200> errors.<02:34:14.319> The<02:34:14.640> active<02:34:15.120> current 02:34:15.429 --> 02:34:15.439 align:start position:0% without errors. The active current 02:34:15.439 --> 02:34:18.230 align:start position:0% without errors. The active current terminal<02:34:16.000> window<02:34:16.319> is<02:34:16.560> closed. 02:34:18.230 --> 02:34:18.240 align:start position:0% terminal window is closed. 02:34:18.240 --> 02:34:20.469 align:start position:0% terminal window is closed. A<02:34:18.479> fresh<02:34:18.800> new<02:34:19.040> terminal<02:34:19.520> session<02:34:19.840> is<02:34:20.000> launched 02:34:20.469 --> 02:34:20.479 align:start position:0% A fresh new terminal session is launched 02:34:20.479 --> 02:34:23.910 align:start position:0% A fresh new terminal session is launched to<02:34:20.720> apply<02:34:21.040> the<02:34:21.280> updated<02:34:21.760> installation<02:34:22.319> paths. 02:34:23.910 --> 02:34:23.920 align:start position:0% to apply the updated installation paths. 02:34:23.920 --> 02:34:26.469 align:start position:0% to apply the updated installation paths. The<02:34:24.160> specific<02:34:24.800> git<02:34:25.200> initialize<02:34:25.840> command<02:34:26.240> is 02:34:26.469 --> 02:34:26.479 align:start position:0% The specific git initialize command is 02:34:26.479 --> 02:34:28.550 align:start position:0% The specific git initialize command is executed<02:34:27.040> again. 02:34:28.550 --> 02:34:28.560 align:start position:0% executed again. 02:34:28.560 --> 02:34:30.790 align:start position:0% executed again. The<02:34:28.800> operating<02:34:29.359> system<02:34:29.760> initializes<02:34:30.479> an 02:34:30.790 --> 02:34:30.800 align:start position:0% The operating system initializes an 02:34:30.800 --> 02:34:33.510 align:start position:0% The operating system initializes an empty<02:34:31.200> local<02:34:31.520> git<02:34:31.920> repository. 02:34:33.510 --> 02:34:33.520 align:start position:0% empty local git repository. 02:34:33.520 --> 02:34:35.750 align:start position:0% empty local git repository. The<02:34:33.760> local<02:34:34.080> development<02:34:34.640> project<02:34:35.040> folder<02:34:35.439> is 02:34:35.750 --> 02:34:35.760 align:start position:0% The local development project folder is 02:34:35.760 --> 02:34:38.790 align:start position:0% The local development project folder is now<02:34:36.000> tracked<02:34:36.319> by<02:34:36.479> the<02:34:36.640> git<02:34:37.040> tool.<02:34:38.319> The<02:34:38.560> next 02:34:38.790 --> 02:34:38.800 align:start position:0% now tracked by the git tool. The next 02:34:38.800 --> 02:34:41.030 align:start position:0% now tracked by the git tool. The next required<02:34:39.280> command<02:34:39.680> is<02:34:39.920> copied<02:34:40.319> from<02:34:40.479> the<02:34:40.720> text 02:34:41.030 --> 02:34:41.040 align:start position:0% required command is copied from the text 02:34:41.040 --> 02:34:42.870 align:start position:0% required command is copied from the text instructions. 02:34:42.870 --> 02:34:42.880 align:start position:0% instructions. 02:34:42.880 --> 02:34:45.429 align:start position:0% instructions. The<02:34:43.120> project<02:34:43.520> branch<02:34:43.840> is<02:34:44.080> renamed<02:34:44.560> to<02:34:44.800> main 02:34:45.429 --> 02:34:45.439 align:start position:0% The project branch is renamed to main 02:34:45.439 --> 02:34:47.990 align:start position:0% The project branch is renamed to main using<02:34:45.760> the<02:34:46.000> active<02:34:46.399> terminal. 02:34:47.990 --> 02:34:48.000 align:start position:0% using the active terminal. 02:34:48.000 --> 02:34:50.230 align:start position:0% using the active terminal. The<02:34:48.240> text<02:34:48.640> command<02:34:49.120> executes<02:34:49.680> without<02:34:50.000> any 02:34:50.230 --> 02:34:50.240 align:start position:0% The text command executes without any 02:34:50.240 --> 02:34:53.670 align:start position:0% The text command executes without any prompt<02:34:50.800> errors.<02:34:52.080> The<02:34:52.399> remote<02:34:52.720> origin<02:34:53.280> target 02:34:53.670 --> 02:34:53.680 align:start position:0% prompt errors. The remote origin target 02:34:53.680 --> 02:34:56.790 align:start position:0% prompt errors. The remote origin target command<02:34:54.080> is<02:34:54.319> copied.<02:34:54.720> Next,<02:34:56.000> this<02:34:56.319> specific 02:34:56.790 --> 02:34:56.800 align:start position:0% command is copied. Next, this specific 02:34:56.800 --> 02:34:59.190 align:start position:0% command is copied. Next, this specific command<02:34:57.280> links<02:34:57.600> the<02:34:57.760> local<02:34:58.080> code<02:34:58.399> repository 02:34:59.190 --> 02:34:59.200 align:start position:0% command links the local code repository 02:34:59.200 --> 02:35:01.590 align:start position:0% command links the local code repository to<02:34:59.439> the<02:34:59.680> new<02:35:00.000> created<02:35:00.560> online<02:35:01.120> GitHub 02:35:01.590 --> 02:35:01.600 align:start position:0% to the new created online GitHub 02:35:01.600 --> 02:35:03.270 align:start position:0% to the new created online GitHub repository. 02:35:03.270 --> 02:35:03.280 align:start position:0% repository. 02:35:03.280 --> 02:35:05.429 align:start position:0% repository. The<02:35:03.520> web<02:35:03.760> link<02:35:04.000> is<02:35:04.240> pasted<02:35:04.640> into<02:35:04.880> the<02:35:05.040> terminal 02:35:05.429 --> 02:35:05.439 align:start position:0% The web link is pasted into the terminal 02:35:05.439 --> 02:35:07.349 align:start position:0% The web link is pasted into the terminal and<02:35:05.760> executed. 02:35:07.349 --> 02:35:07.359 align:start position:0% and executed. 02:35:07.359 --> 02:35:09.429 align:start position:0% and executed. The<02:35:07.680> internet<02:35:08.080> connection<02:35:08.560> is<02:35:08.800> established 02:35:09.429 --> 02:35:09.439 align:start position:0% The internet connection is established 02:35:09.439 --> 02:35:11.429 align:start position:0% The internet connection is established without<02:35:09.760> issues. 02:35:11.429 --> 02:35:11.439 align:start position:0% without issues. 02:35:11.439 --> 02:35:13.349 align:start position:0% without issues. The<02:35:11.680> next<02:35:11.920> development<02:35:12.479> step<02:35:12.880> requires 02:35:13.349 --> 02:35:13.359 align:start position:0% The next development step requires 02:35:13.359 --> 02:35:15.429 align:start position:0% The next development step requires adding<02:35:13.760> all<02:35:14.000> project<02:35:14.399> files<02:35:14.800> to<02:35:14.960> the<02:35:15.120> code 02:35:15.429 --> 02:35:15.439 align:start position:0% adding all project files to the code 02:35:15.439 --> 02:35:18.630 align:start position:0% adding all project files to the code staging<02:35:15.920> area.<02:35:17.200> The<02:35:17.439> standard<02:35:18.000> git<02:35:18.319> add 02:35:18.630 --> 02:35:18.640 align:start position:0% staging area. The standard git add 02:35:18.640 --> 02:35:21.349 align:start position:0% staging area. The standard git add command<02:35:19.040> is<02:35:19.280> prepared.<02:35:20.399> An<02:35:20.800> error<02:35:20.960> prompt 02:35:21.349 --> 02:35:21.359 align:start position:0% command is prepared. An error prompt 02:35:21.359 --> 02:35:23.510 align:start position:0% command is prepared. An error prompt occurs<02:35:22.000> stating<02:35:22.479> access<02:35:22.960> permission<02:35:23.359> is 02:35:23.510 --> 02:35:23.520 align:start position:0% occurs stating access permission is 02:35:23.520 --> 02:35:26.950 align:start position:0% occurs stating access permission is denied.<02:35:24.960> The<02:35:25.200> operating<02:35:25.760> system<02:35:26.160> cannot<02:35:26.640> open 02:35:26.950 --> 02:35:26.960 align:start position:0% denied. The operating system cannot open 02:35:26.960 --> 02:35:30.309 align:start position:0% denied. The operating system cannot open a<02:35:27.200> distinct<02:35:27.680> application<02:35:28.319> data<02:35:28.720> directory. 02:35:30.309 --> 02:35:30.319 align:start position:0% a distinct application data directory. 02:35:30.319 --> 02:35:33.750 align:start position:0% a distinct application data directory. This<02:35:30.720> file<02:35:31.040> access<02:35:31.439> issue<02:35:31.840> must<02:35:32.160> be<02:35:32.399> resolved. 02:35:33.750 --> 02:35:33.760 align:start position:0% This file access issue must be resolved. 02:35:33.760 --> 02:35:36.070 align:start position:0% This file access issue must be resolved. The<02:35:34.080> access<02:35:34.479> permission<02:35:34.880> denied<02:35:35.439> error<02:35:35.680> halts 02:35:36.070 --> 02:35:36.080 align:start position:0% The access permission denied error halts 02:35:36.080 --> 02:35:38.150 align:start position:0% The access permission denied error halts the<02:35:36.319> running<02:35:36.640> process. 02:35:38.150 --> 02:35:38.160 align:start position:0% the running process. 02:35:38.160 --> 02:35:40.230 align:start position:0% the running process. The<02:35:38.399> operating<02:35:38.960> system<02:35:39.359> attempts<02:35:39.760> to<02:35:39.920> add 02:35:40.230 --> 02:35:40.240 align:start position:0% The operating system attempts to add 02:35:40.240 --> 02:35:42.070 align:start position:0% The operating system attempts to add developer<02:35:40.720> files<02:35:41.040> from<02:35:41.280> the<02:35:41.439> root<02:35:41.760> user 02:35:42.070 --> 02:35:42.080 align:start position:0% developer files from the root user 02:35:42.080 --> 02:35:45.349 align:start position:0% developer files from the root user directory<02:35:42.880> instead<02:35:43.280> of<02:35:43.359> the<02:35:43.600> project<02:35:43.920> folder. 02:35:45.349 --> 02:35:45.359 align:start position:0% directory instead of the project folder. 02:35:45.359 --> 02:35:48.389 align:start position:0% directory instead of the project folder. This<02:35:45.680> behavior<02:35:46.160> is<02:35:46.319> a<02:35:46.560> crucial<02:35:46.880> mistake. 02:35:48.389 --> 02:35:48.399 align:start position:0% This behavior is a crucial mistake. 02:35:48.399 --> 02:35:50.389 align:start position:0% This behavior is a crucial mistake. The<02:35:48.640> code<02:35:48.960> terminal<02:35:49.359> is<02:35:49.600> operating<02:35:50.000> in<02:35:50.240> the 02:35:50.389 --> 02:35:50.399 align:start position:0% The code terminal is operating in the 02:35:50.399 --> 02:35:53.110 align:start position:0% The code terminal is operating in the wrong<02:35:50.640> system<02:35:51.040> directory<02:35:51.600> path. 02:35:53.110 --> 02:35:53.120 align:start position:0% wrong system directory path. 02:35:53.120 --> 02:35:55.670 align:start position:0% wrong system directory path. A<02:35:53.359> new<02:35:53.600> terminal<02:35:54.160> application<02:35:54.720> tab<02:35:55.120> must<02:35:55.520> be 02:35:55.670 --> 02:35:55.680 align:start position:0% A new terminal application tab must be 02:35:55.680 --> 02:35:58.230 align:start position:0% A new terminal application tab must be opened<02:35:56.240> within<02:35:56.640> the<02:35:56.880> exact<02:35:57.280> correct<02:35:57.840> project 02:35:58.230 --> 02:35:58.240 align:start position:0% opened within the exact correct project 02:35:58.240 --> 02:36:01.670 align:start position:0% opened within the exact correct project folder.<02:35:59.680> The<02:35:59.920> root<02:36:00.240> user<02:36:00.640> terminal<02:36:01.040> is<02:36:01.280> closed 02:36:01.670 --> 02:36:01.680 align:start position:0% folder. The root user terminal is closed 02:36:01.680 --> 02:36:04.710 align:start position:0% folder. The root user terminal is closed without<02:36:02.000> delay.<02:36:03.280> The<02:36:03.520> new<02:36:03.840> command<02:36:04.240> terminal 02:36:04.710 --> 02:36:04.720 align:start position:0% without delay. The new command terminal 02:36:04.720 --> 02:36:07.030 align:start position:0% without delay. The new command terminal now<02:36:05.040> displays<02:36:05.520> the<02:36:05.760> correct<02:36:06.160> document<02:36:06.640> path 02:36:07.030 --> 02:36:07.040 align:start position:0% now displays the correct document path 02:36:07.040 --> 02:36:09.510 align:start position:0% now displays the correct document path for<02:36:07.280> the<02:36:07.439> software<02:36:07.920> project. 02:36:09.510 --> 02:36:09.520 align:start position:0% for the software project. 02:36:09.520 --> 02:36:11.830 align:start position:0% for the software project. The<02:36:09.840> standard<02:36:10.240> git<02:36:10.640> initialize<02:36:11.200> command<02:36:11.600> is 02:36:11.830 --> 02:36:11.840 align:start position:0% The standard git initialize command is 02:36:11.840 --> 02:36:15.030 align:start position:0% The standard git initialize command is executed<02:36:12.479> again<02:36:12.720> in<02:36:12.960> the<02:36:13.120> right<02:36:13.359> folder.<02:36:14.800> An 02:36:15.030 --> 02:36:15.040 align:start position:0% executed again in the right folder. An 02:36:15.040 --> 02:36:17.110 align:start position:0% executed again in the right folder. An empty<02:36:15.439> code<02:36:15.760> repository<02:36:16.319> is<02:36:16.479> initialized 02:36:17.110 --> 02:36:17.120 align:start position:0% empty code repository is initialized 02:36:17.120 --> 02:36:19.910 align:start position:0% empty code repository is initialized here<02:36:17.520> without<02:36:17.920> any<02:36:18.240> issues. 02:36:19.910 --> 02:36:19.920 align:start position:0% here without any issues. 02:36:19.920 --> 02:36:22.070 align:start position:0% here without any issues. The<02:36:20.240> branch<02:36:20.640> rename<02:36:21.120> text<02:36:21.439> command<02:36:21.840> is 02:36:22.070 --> 02:36:22.080 align:start position:0% The branch rename text command is 02:36:22.080 --> 02:36:25.510 align:start position:0% The branch rename text command is executed<02:36:22.960> to<02:36:23.200> set<02:36:23.439> the<02:36:23.680> main<02:36:24.000> branch. 02:36:25.510 --> 02:36:25.520 align:start position:0% executed to set the main branch. 02:36:25.520 --> 02:36:28.309 align:start position:0% executed to set the main branch. The<02:36:25.760> remote<02:36:26.160> origin<02:36:26.640> command<02:36:27.040> is<02:36:27.280> pasted<02:36:27.920> and 02:36:28.309 --> 02:36:28.319 align:start position:0% The remote origin command is pasted and 02:36:28.319 --> 02:36:30.630 align:start position:0% The remote origin command is pasted and executed<02:36:28.960> to<02:36:29.200> link<02:36:29.439> the<02:36:29.680> online<02:36:30.160> GitHub 02:36:30.630 --> 02:36:30.640 align:start position:0% executed to link the online GitHub 02:36:30.640 --> 02:36:32.309 align:start position:0% executed to link the online GitHub repository. 02:36:32.309 --> 02:36:32.319 align:start position:0% repository. 02:36:32.319 --> 02:36:34.309 align:start position:0% repository. The<02:36:32.640> correct<02:36:33.040> project<02:36:33.439> folder<02:36:33.840> is<02:36:34.080> now 02:36:34.309 --> 02:36:34.319 align:start position:0% The correct project folder is now 02:36:34.319 --> 02:36:36.070 align:start position:0% The correct project folder is now connected. 02:36:36.070 --> 02:36:36.080 align:start position:0% connected. 02:36:36.080 --> 02:36:38.550 align:start position:0% connected. The<02:36:36.319> next<02:36:36.640> workflow<02:36:37.200> step<02:36:37.600> is<02:36:37.840> to<02:36:38.000> add<02:36:38.319> all 02:36:38.550 --> 02:36:38.560 align:start position:0% The next workflow step is to add all 02:36:38.560 --> 02:36:41.030 align:start position:0% The next workflow step is to add all files<02:36:38.960> to<02:36:39.120> the<02:36:39.280> staging<02:36:39.680> area. 02:36:41.030 --> 02:36:41.040 align:start position:0% files to the staging area. 02:36:41.040 --> 02:36:43.750 align:start position:0% files to the staging area. The<02:36:41.280> simple<02:36:41.760> git<02:36:42.160> add<02:36:42.479> command<02:36:42.880> is<02:36:43.200> executed 02:36:43.750 --> 02:36:43.760 align:start position:0% The simple git add command is executed 02:36:43.760 --> 02:36:46.790 align:start position:0% The simple git add command is executed without<02:36:44.319> errors.<02:36:44.560> This<02:36:44.800> time<02:36:46.160> all<02:36:46.479> main 02:36:46.790 --> 02:36:46.800 align:start position:0% without errors. This time all main 02:36:46.800 --> 02:36:48.710 align:start position:0% without errors. This time all main project<02:36:47.200> files<02:36:47.520> are<02:36:47.760> added<02:36:48.080> to<02:36:48.240> the<02:36:48.399> code 02:36:48.710 --> 02:36:48.720 align:start position:0% project files are added to the code 02:36:48.720 --> 02:36:50.710 align:start position:0% project files are added to the code staging<02:36:49.120> area. 02:36:50.710 --> 02:36:50.720 align:start position:0% staging area. 02:36:50.720 --> 02:36:52.870 align:start position:0% staging area. The<02:36:50.960> standard<02:36:51.439> git<02:36:51.840> commit<02:36:52.240> command<02:36:52.640> is 02:36:52.870 --> 02:36:52.880 align:start position:0% The standard git commit command is 02:36:52.880 --> 02:36:56.150 align:start position:0% The standard git commit command is executed<02:36:53.520> with<02:36:53.760> a<02:36:53.920> descriptive<02:36:54.560> message. 02:36:56.150 --> 02:36:56.160 align:start position:0% executed with a descriptive message. 02:36:56.160 --> 02:36:58.790 align:start position:0% executed with a descriptive message. The<02:36:56.479> operating<02:36:56.960> system<02:36:57.439> returns<02:36:57.920> an<02:36:58.160> author 02:36:58.790 --> 02:36:58.800 align:start position:0% The operating system returns an author 02:36:58.800 --> 02:37:02.469 align:start position:0% The operating system returns an author identity<02:36:59.359> unknown<02:37:00.160> error.<02:37:01.439> The<02:37:01.680> code<02:37:02.000> commit 02:37:02.469 --> 02:37:02.479 align:start position:0% identity unknown error. The code commit 02:37:02.479 --> 02:37:04.550 align:start position:0% identity unknown error. The code commit cannot<02:37:02.880> proceed<02:37:03.280> without<02:37:03.680> proper<02:37:04.080> user 02:37:04.550 --> 02:37:04.560 align:start position:0% cannot proceed without proper user 02:37:04.560 --> 02:37:06.469 align:start position:0% cannot proceed without proper user identification. 02:37:06.469 --> 02:37:06.479 align:start position:0% identification. 02:37:06.479 --> 02:37:08.870 align:start position:0% identification. The<02:37:06.720> global<02:37:07.200> user<02:37:07.600> configuration<02:37:08.319> commands 02:37:08.870 --> 02:37:08.880 align:start position:0% The global user configuration commands 02:37:08.880 --> 02:37:11.510 align:start position:0% The global user configuration commands must<02:37:09.200> be<02:37:09.359> executed<02:37:10.000> first. 02:37:11.510 --> 02:37:11.520 align:start position:0% must be executed first. 02:37:11.520 --> 02:37:13.590 align:start position:0% must be executed first. The<02:37:11.760> terminal<02:37:12.240> command<02:37:12.560> to<02:37:12.800> set<02:37:13.040> the<02:37:13.280> user 02:37:13.590 --> 02:37:13.600 align:start position:0% The terminal command to set the user 02:37:13.600 --> 02:37:15.670 align:start position:0% The terminal command to set the user email<02:37:14.000> is<02:37:14.160> copied. 02:37:15.670 --> 02:37:15.680 align:start position:0% email is copied. 02:37:15.680 --> 02:37:18.230 align:start position:0% email is copied. The<02:37:15.920> account<02:37:16.319> email<02:37:16.720> address<02:37:17.040> is<02:37:17.280> updated<02:37:18.000> to 02:37:18.230 --> 02:37:18.240 align:start position:0% The account email address is updated to 02:37:18.240 --> 02:37:20.070 align:start position:0% The account email address is updated to match<02:37:18.479> the<02:37:18.720> online<02:37:19.200> GitHub<02:37:19.760> account 02:37:20.070 --> 02:37:20.080 align:start position:0% match the online GitHub account 02:37:20.080 --> 02:37:21.830 align:start position:0% match the online GitHub account credentials. 02:37:21.830 --> 02:37:21.840 align:start position:0% credentials. 02:37:21.840 --> 02:37:23.830 align:start position:0% credentials. The<02:37:22.080> command<02:37:22.399> is<02:37:22.640> executed<02:37:23.200> without<02:37:23.520> any 02:37:23.830 --> 02:37:23.840 align:start position:0% The command is executed without any 02:37:23.840 --> 02:37:27.030 align:start position:0% The command is executed without any system<02:37:24.319> errors.<02:37:25.760> The<02:37:26.000> terminal<02:37:26.479> command<02:37:26.800> to 02:37:27.030 --> 02:37:27.040 align:start position:0% system errors. The terminal command to 02:37:27.040 --> 02:37:30.309 align:start position:0% system errors. The terminal command to set<02:37:27.280> the<02:37:27.520> username<02:37:28.080> is<02:37:28.319> copied.<02:37:28.800> Next, 02:37:30.309 --> 02:37:30.319 align:start position:0% set the username is copied. Next, 02:37:30.319 --> 02:37:32.469 align:start position:0% set the username is copied. Next, the<02:37:30.560> developer<02:37:31.040> username<02:37:31.600> is<02:37:31.840> retrieved<02:37:32.319> from 02:37:32.469 --> 02:37:32.479 align:start position:0% the developer username is retrieved from 02:37:32.479 --> 02:37:35.429 align:start position:0% the developer username is retrieved from the<02:37:32.720> web<02:37:33.040> GitHub<02:37:33.520> profile<02:37:34.000> page. 02:37:35.429 --> 02:37:35.439 align:start position:0% the web GitHub profile page. 02:37:35.439 --> 02:37:37.910 align:start position:0% the web GitHub profile page. The<02:37:35.760> target<02:37:36.160> username<02:37:36.720> is<02:37:36.960> pasted<02:37:37.439> into<02:37:37.760> the 02:37:37.910 --> 02:37:37.920 align:start position:0% The target username is pasted into the 02:37:37.920 --> 02:37:40.309 align:start position:0% The target username is pasted into the terminal<02:37:38.399> command<02:37:38.800> line. 02:37:40.309 --> 02:37:40.319 align:start position:0% terminal command line. 02:37:40.319 --> 02:37:42.630 align:start position:0% terminal command line. The<02:37:40.560> system<02:37:41.040> configuration<02:37:41.840> is<02:37:42.080> updated 02:37:42.630 --> 02:37:42.640 align:start position:0% The system configuration is updated 02:37:42.640 --> 02:37:44.630 align:start position:0% The system configuration is updated without<02:37:43.040> issues. 02:37:44.630 --> 02:37:44.640 align:start position:0% without issues. 02:37:44.640 --> 02:37:46.870 align:start position:0% without issues. The<02:37:44.880> required<02:37:45.359> author<02:37:46.000> identity<02:37:46.399> is<02:37:46.640> now 02:37:46.870 --> 02:37:46.880 align:start position:0% The required author identity is now 02:37:46.880 --> 02:37:48.550 align:start position:0% The required author identity is now established. 02:37:48.550 --> 02:37:48.560 align:start position:0% established. 02:37:48.560 --> 02:37:50.870 align:start position:0% established. The<02:37:48.880> standard<02:37:49.359> git<02:37:49.680> commit<02:37:50.160> command<02:37:50.640> is 02:37:50.870 --> 02:37:50.880 align:start position:0% The standard git commit command is 02:37:50.880 --> 02:37:54.469 align:start position:0% The standard git commit command is executed<02:37:51.520> once<02:37:51.840> again.<02:37:53.200> This<02:37:53.520> specific<02:37:54.000> time, 02:37:54.469 --> 02:37:54.479 align:start position:0% executed once again. This specific time, 02:37:54.479 --> 02:37:57.429 align:start position:0% executed once again. This specific time, the<02:37:54.720> code<02:37:55.040> commit<02:37:55.439> is<02:37:55.600> a<02:37:55.840> success. 02:37:57.429 --> 02:37:57.439 align:start position:0% the code commit is a success. 02:37:57.439 --> 02:37:59.750 align:start position:0% the code commit is a success. All<02:37:57.760> modified<02:37:58.319> files<02:37:58.720> are<02:37:58.960> recorded<02:37:59.359> in<02:37:59.600> the 02:37:59.750 --> 02:37:59.760 align:start position:0% All modified files are recorded in the 02:37:59.760 --> 02:38:01.670 align:start position:0% All modified files are recorded in the local<02:38:00.080> repository. 02:38:01.670 --> 02:38:01.680 align:start position:0% local repository. 02:38:01.680 --> 02:38:03.830 align:start position:0% local repository. The<02:38:02.000> source<02:38:02.319> code<02:38:02.560> is<02:38:02.880> ready<02:38:03.120> for<02:38:03.280> the<02:38:03.520> final 02:38:03.830 --> 02:38:03.840 align:start position:0% The source code is ready for the final 02:38:03.840 --> 02:38:05.349 align:start position:0% The source code is ready for the final push. 02:38:05.349 --> 02:38:05.359 align:start position:0% push. 02:38:05.359 --> 02:38:07.590 align:start position:0% push. The<02:38:05.600> main<02:38:05.840> commit<02:38:06.240> process<02:38:06.800> includes<02:38:07.359> all 02:38:07.590 --> 02:38:07.600 align:start position:0% The main commit process includes all 02:38:07.600 --> 02:38:10.630 align:start position:0% The main commit process includes all necessary<02:38:08.240> application<02:38:08.960> files.<02:38:10.000> The<02:38:10.240> design 02:38:10.630 --> 02:38:10.640 align:start position:0% necessary application files. The design 02:38:10.640 --> 02:38:14.389 align:start position:0% necessary application files. The design assets,<02:38:11.760> HTML<02:38:12.399> web<02:38:12.640> pages,<02:38:13.520> and<02:38:13.840> application 02:38:14.389 --> 02:38:14.399 align:start position:0% assets, HTML web pages, and application 02:38:14.399 --> 02:38:17.510 align:start position:0% assets, HTML web pages, and application data<02:38:14.800> files<02:38:15.120> are<02:38:15.439> secured.<02:38:16.880> The<02:38:17.120> final 02:38:17.510 --> 02:38:17.520 align:start position:0% data files are secured. The final 02:38:17.520 --> 02:38:19.750 align:start position:0% data files are secured. The final terminal<02:38:18.080> command<02:38:18.479> to<02:38:18.720> push<02:38:18.960> the<02:38:19.200> source<02:38:19.520> code 02:38:19.750 --> 02:38:19.760 align:start position:0% terminal command to push the source code 02:38:19.760 --> 02:38:22.870 align:start position:0% terminal command to push the source code is<02:38:20.080> executed.<02:38:21.520> The<02:38:21.840> command<02:38:22.319> terminal 02:38:22.870 --> 02:38:22.880 align:start position:0% is executed. The command terminal 02:38:22.880 --> 02:38:25.590 align:start position:0% is executed. The command terminal requests<02:38:23.359> user<02:38:23.760> authentication<02:38:24.960> to<02:38:25.200> access 02:38:25.590 --> 02:38:25.600 align:start position:0% requests user authentication to access 02:38:25.600 --> 02:38:28.230 align:start position:0% requests user authentication to access the<02:38:25.840> remote<02:38:26.160> GitHub<02:38:26.640> repository. 02:38:28.230 --> 02:38:28.240 align:start position:0% the remote GitHub repository. 02:38:28.240 --> 02:38:30.550 align:start position:0% the remote GitHub repository. A<02:38:28.479> new<02:38:28.800> internet<02:38:29.200> browser<02:38:29.600> window<02:38:30.000> opens<02:38:30.399> for 02:38:30.550 --> 02:38:30.560 align:start position:0% A new internet browser window opens for 02:38:30.560 --> 02:38:33.190 align:start position:0% A new internet browser window opens for the<02:38:30.720> user<02:38:31.040> login<02:38:31.520> process. 02:38:33.190 --> 02:38:33.200 align:start position:0% the user login process. 02:38:33.200 --> 02:38:35.590 align:start position:0% the user login process. The<02:38:33.439> signin<02:38:34.000> with<02:38:34.319> internet<02:38:34.720> browser<02:38:35.200> option 02:38:35.590 --> 02:38:35.600 align:start position:0% The signin with internet browser option 02:38:35.600 --> 02:38:37.349 align:start position:0% The signin with internet browser option is<02:38:35.840> selected. 02:38:37.349 --> 02:38:37.359 align:start position:0% is selected. 02:38:37.359 --> 02:38:39.670 align:start position:0% is selected. The<02:38:37.600> existing<02:38:38.240> active<02:38:38.640> session<02:38:38.960> credentials 02:38:39.670 --> 02:38:39.680 align:start position:0% The existing active session credentials 02:38:39.680 --> 02:38:41.510 align:start position:0% The existing active session credentials are<02:38:39.920> used<02:38:40.160> to<02:38:40.399> authorize<02:38:40.880> the<02:38:41.120> upload 02:38:41.510 --> 02:38:41.520 align:start position:0% are used to authorize the upload 02:38:41.520 --> 02:38:43.110 align:start position:0% are used to authorize the upload transaction. 02:38:43.110 --> 02:38:43.120 align:start position:0% transaction. 02:38:43.120 --> 02:38:45.349 align:start position:0% transaction. The<02:38:43.439> access<02:38:43.840> authorization<02:38:44.800> succeeds 02:38:45.349 --> 02:38:45.359 align:start position:0% The access authorization succeeds 02:38:45.359 --> 02:38:48.070 align:start position:0% The access authorization succeeds without<02:38:45.680> delay.<02:38:46.880> Returning<02:38:47.359> to<02:38:47.520> the<02:38:47.680> command 02:38:48.070 --> 02:38:48.080 align:start position:0% without delay. Returning to the command 02:38:48.080 --> 02:38:50.790 align:start position:0% without delay. Returning to the command terminal<02:38:48.880> confirms<02:38:49.439> the<02:38:49.680> code<02:38:49.920> push<02:38:50.319> process 02:38:50.790 --> 02:38:50.800 align:start position:0% terminal confirms the code push process 02:38:50.800 --> 02:38:53.670 align:start position:0% terminal confirms the code push process is<02:38:51.040> active.<02:38:52.479> The<02:38:52.720> data<02:38:53.040> objects<02:38:53.520> are 02:38:53.670 --> 02:38:53.680 align:start position:0% is active. The data objects are 02:38:53.680 --> 02:38:55.670 align:start position:0% is active. The data objects are compressed<02:38:54.160> and<02:38:54.399> written<02:38:54.720> to<02:38:54.880> the<02:38:55.120> remote<02:38:55.439> web 02:38:55.670 --> 02:38:55.680 align:start position:0% compressed and written to the remote web 02:38:55.680 --> 02:38:58.950 align:start position:0% compressed and written to the remote web server.<02:38:56.960> The<02:38:57.200> main<02:38:57.520> code<02:38:57.840> branch<02:38:58.319> is<02:38:58.560> set<02:38:58.720> up 02:38:58.950 --> 02:38:58.960 align:start position:0% server. The main code branch is set up 02:38:58.960 --> 02:39:02.070 align:start position:0% server. The main code branch is set up to<02:38:59.200> track<02:38:59.439> the<02:38:59.680> remote<02:39:00.000> origin<02:39:00.479> point.<02:39:01.840> The 02:39:02.070 --> 02:39:02.080 align:start position:0% to track the remote origin point. The 02:39:02.080 --> 02:39:05.349 align:start position:0% to track the remote origin point. The entire<02:39:02.560> application<02:39:03.200> project<02:39:03.600> is<02:39:03.840> uploaded. 02:39:05.349 --> 02:39:05.359 align:start position:0% entire application project is uploaded. 02:39:05.359 --> 02:39:08.070 align:start position:0% entire application project is uploaded. The<02:39:05.600> online<02:39:06.080> GitHub<02:39:06.640> repository<02:39:07.200> page<02:39:07.760> is 02:39:08.070 --> 02:39:08.080 align:start position:0% The online GitHub repository page is 02:39:08.080 --> 02:39:11.110 align:start position:0% The online GitHub repository page is refreshed<02:39:08.560> in<02:39:08.800> the<02:39:08.960> internet<02:39:09.359> browser.<02:39:10.800> All 02:39:11.110 --> 02:39:11.120 align:start position:0% refreshed in the internet browser. All 02:39:11.120 --> 02:39:13.110 align:start position:0% refreshed in the internet browser. All local<02:39:11.439> project<02:39:11.840> files<02:39:12.240> are<02:39:12.479> now<02:39:12.720> visible 02:39:13.110 --> 02:39:13.120 align:start position:0% local project files are now visible 02:39:13.120 --> 02:39:14.710 align:start position:0% local project files are now visible online. 02:39:14.710 --> 02:39:14.720 align:start position:0% online. 02:39:14.720 --> 02:39:17.429 align:start position:0% online. The<02:39:14.960> assets<02:39:15.439> folder<02:39:16.160> and<02:39:16.399> HTML<02:39:17.120> text 02:39:17.429 --> 02:39:17.439 align:start position:0% The assets folder and HTML text 02:39:17.439 --> 02:39:20.710 align:start position:0% The assets folder and HTML text documents<02:39:17.920> are<02:39:18.160> listed.<02:39:19.600> The<02:39:19.840> code<02:39:20.240> upload 02:39:20.710 --> 02:39:20.720 align:start position:0% documents are listed. The code upload 02:39:20.720 --> 02:39:24.070 align:start position:0% documents are listed. The code upload process<02:39:21.120> is<02:39:21.439> verified<02:39:22.160> and<02:39:22.399> a<02:39:22.640> success.<02:39:23.840> The 02:39:24.070 --> 02:39:24.080 align:start position:0% process is verified and a success. The 02:39:24.080 --> 02:39:26.630 align:start position:0% process is verified and a success. The uploaded<02:39:24.720> index<02:39:25.120> document<02:39:25.600> file<02:39:26.000> is<02:39:26.240> opened 02:39:26.630 --> 02:39:26.640 align:start position:0% uploaded index document file is opened 02:39:26.640 --> 02:39:30.309 align:start position:0% uploaded index document file is opened on<02:39:26.800> GitHub<02:39:27.520> to<02:39:27.760> verify<02:39:28.160> its<02:39:28.479> code<02:39:28.800> contents. 02:39:30.309 --> 02:39:30.319 align:start position:0% on GitHub to verify its code contents. 02:39:30.319 --> 02:39:32.630 align:start position:0% on GitHub to verify its code contents. The<02:39:30.640> online<02:39:31.120> code<02:39:31.600> matches<02:39:32.000> the<02:39:32.240> local 02:39:32.630 --> 02:39:32.640 align:start position:0% The online code matches the local 02:39:32.640 --> 02:39:35.510 align:start position:0% The online code matches the local computer<02:39:33.040> version<02:39:33.520> without<02:39:34.000> flaws. 02:39:35.510 --> 02:39:35.520 align:start position:0% computer version without flaws. 02:39:35.520 --> 02:39:37.510 align:start position:0% computer version without flaws. The<02:39:35.760> source<02:39:36.160> blame<02:39:36.560> and<02:39:36.880> file<02:39:37.200> history 02:39:37.510 --> 02:39:37.520 align:start position:0% The source blame and file history 02:39:37.520 --> 02:39:40.389 align:start position:0% The source blame and file history options<02:39:38.000> are<02:39:38.240> functional.<02:39:39.439> The<02:39:39.680> raw<02:39:40.080> text 02:39:40.389 --> 02:39:40.399 align:start position:0% options are functional. The raw text 02:39:40.399 --> 02:39:43.510 align:start position:0% options are functional. The raw text code<02:39:40.800> can<02:39:40.960> be<02:39:41.120> accessed<02:39:41.680> any<02:39:42.000> time.<02:39:43.200> The 02:39:43.510 --> 02:39:43.520 align:start position:0% code can be accessed any time. The 02:39:43.520 --> 02:39:46.870 align:start position:0% code can be accessed any time. The entire<02:39:43.920> upload<02:39:44.399> process<02:39:44.880> is<02:39:45.120> now<02:39:45.359> concluded. 02:39:46.870 --> 02:39:46.880 align:start position:0% entire upload process is now concluded. 02:39:46.880 --> 02:39:49.110 align:start position:0% entire upload process is now concluded. The<02:39:47.120> initial<02:39:47.520> project<02:39:47.920> objective<02:39:48.640> was<02:39:48.960> to 02:39:49.110 --> 02:39:49.120 align:start position:0% The initial project objective was to 02:39:49.120 --> 02:39:51.270 align:start position:0% The initial project objective was to build<02:39:49.359> a<02:39:49.600> medical<02:39:50.080> healthcare<02:39:50.640> application 02:39:51.270 --> 02:39:51.280 align:start position:0% build a medical healthcare application 02:39:51.280 --> 02:39:54.309 align:start position:0% build a medical healthcare application project.<02:39:52.560> A<02:39:52.800> detailed<02:39:53.280> development<02:39:53.760> plan<02:39:54.000> was 02:39:54.309 --> 02:39:54.319 align:start position:0% project. A detailed development plan was 02:39:54.319 --> 02:39:57.429 align:start position:0% project. A detailed development plan was formulated<02:39:54.960> first.<02:39:56.160> The<02:39:56.479> project<02:39:56.800> scope<02:39:57.200> was 02:39:57.429 --> 02:39:57.439 align:start position:0% formulated first. The project scope was 02:39:57.439 --> 02:40:00.230 align:start position:0% formulated first. The project scope was defined<02:39:58.080> for<02:39:58.319> a<02:39:58.560> basic<02:39:59.120> minimum<02:39:59.680> viable 02:40:00.230 --> 02:40:00.240 align:start position:0% defined for a basic minimum viable 02:40:00.240 --> 02:40:02.870 align:start position:0% defined for a basic minimum viable product.<02:40:01.600> The<02:40:01.840> database<02:40:02.399> backend 02:40:02.870 --> 02:40:02.880 align:start position:0% product. The database backend 02:40:02.880 --> 02:40:05.349 align:start position:0% product. The database backend requirements<02:40:03.520> were<02:40:03.760> later<02:40:04.160> removed<02:40:04.720> to<02:40:05.040> focus 02:40:05.349 --> 02:40:05.359 align:start position:0% requirements were later removed to focus 02:40:05.359 --> 02:40:08.389 align:start position:0% requirements were later removed to focus on<02:40:05.520> the<02:40:05.760> user<02:40:06.080> front-end<02:40:06.720> interface. 02:40:08.389 --> 02:40:08.399 align:start position:0% on the user front-end interface. 02:40:08.399 --> 02:40:11.750 align:start position:0% on the user front-end interface. The<02:40:08.640> HTML<02:40:09.359> and<02:40:09.680> CSS<02:40:10.319> design<02:40:10.720> structures<02:40:11.520> were 02:40:11.750 --> 02:40:11.760 align:start position:0% The HTML and CSS design structures were 02:40:11.760 --> 02:40:15.190 align:start position:0% The HTML and CSS design structures were developed<02:40:12.240> with<02:40:12.479> minimal<02:40:12.880> JavaScript<02:40:13.520> logic. 02:40:15.190 --> 02:40:15.200 align:start position:0% developed with minimal JavaScript logic. 02:40:15.200 --> 02:40:17.670 align:start position:0% developed with minimal JavaScript logic. Various<02:40:15.760> design<02:40:16.080> iterations<02:40:16.960> improved<02:40:17.439> the 02:40:17.670 --> 02:40:17.680 align:start position:0% Various design iterations improved the 02:40:17.680 --> 02:40:19.910 align:start position:0% Various design iterations improved the visual<02:40:18.080> page<02:40:18.319> aesthetics<02:40:19.200> and<02:40:19.520> user 02:40:19.910 --> 02:40:19.920 align:start position:0% visual page aesthetics and user 02:40:19.920 --> 02:40:21.670 align:start position:0% visual page aesthetics and user experience. 02:40:21.670 --> 02:40:21.680 align:start position:0% experience. 02:40:21.680 --> 02:40:24.230 align:start position:0% experience. The<02:40:22.000> personalized<02:40:22.800> user<02:40:23.200> profile<02:40:23.680> creation 02:40:24.230 --> 02:40:24.240 align:start position:0% The personalized user profile creation 02:40:24.240 --> 02:40:26.710 align:start position:0% The personalized user profile creation feature<02:40:24.640> was<02:40:24.960> integrated. 02:40:26.710 --> 02:40:26.720 align:start position:0% feature was integrated. 02:40:26.720 --> 02:40:29.270 align:start position:0% feature was integrated. In<02:40:26.960> the<02:40:27.200> end,<02:40:27.760> the<02:40:28.000> local<02:40:28.399> source<02:40:28.720> code<02:40:29.040> was 02:40:29.270 --> 02:40:29.280 align:start position:0% In the end, the local source code was 02:40:29.280 --> 02:40:32.230 align:start position:0% In the end, the local source code was pushed<02:40:29.600> to<02:40:29.760> a<02:40:30.000> public<02:40:30.399> code<02:40:30.720> repository. 02:40:32.230 --> 02:40:32.240 align:start position:0% pushed to a public code repository. 02:40:32.240 --> 02:40:34.710 align:start position:0% pushed to a public code repository. The<02:40:32.560> application<02:40:33.200> project<02:40:33.600> is<02:40:33.920> stored<02:40:34.319> and 02:40:34.710 --> 02:40:34.720 align:start position:0% The application project is stored and 02:40:34.720 --> 02:40:36.230 align:start position:0% The application project is stored and accessible. 02:40:36.230 --> 02:40:36.240 align:start position:0% accessible. 02:40:36.240 --> 02:40:38.230 align:start position:0% accessible. Future<02:40:36.720> code<02:40:37.040> modifications<02:40:37.840> can<02:40:38.080> be 02:40:38.230 --> 02:40:38.240 align:start position:0% Future code modifications can be 02:40:38.240 --> 02:40:40.309 align:start position:0% Future code modifications can be implemented<02:40:39.120> and<02:40:39.439> tracked<02:40:39.840> through<02:40:40.080> this 02:40:40.309 --> 02:40:40.319 align:start position:0% implemented and tracked through this 02:40:40.319 --> 02:40:42.309 align:start position:0% implemented and tracked through this version<02:40:40.720> repository<02:40:41.359> system<02:40:41.840> without 02:40:42.309 --> 02:40:42.319 align:start position:0% version repository system without 02:40:42.319 --> 02:40:45.030 align:start position:0% version repository system without effort.<02:40:43.760> The<02:40:44.080> detailed<02:40:44.560> software 02:40:45.030 --> 02:40:45.040 align:start position:0% effort. The detailed software 02:40:45.040 --> 02:40:47.590 align:start position:0% effort. The detailed software implementation<02:40:45.760> plan<02:40:46.399> proved<02:40:46.880> effective<02:40:47.280> in 02:40:47.590 --> 02:40:47.600 align:start position:0% implementation plan proved effective in 02:40:47.600 --> 02:40:50.870 align:start position:0% implementation plan proved effective in practice.<02:40:48.880> We<02:40:49.200> established<02:40:49.760> a<02:40:50.080> strong<02:40:50.479> code 02:40:50.870 --> 02:40:50.880 align:start position:0% practice. We established a strong code 02:40:50.880 --> 02:40:53.750 align:start position:0% practice. We established a strong code foundation<02:40:51.920> using<02:40:52.399> standard<02:40:52.960> modern<02:40:53.439> web 02:40:53.750 --> 02:40:53.760 align:start position:0% foundation using standard modern web 02:40:53.760 --> 02:40:55.510 align:start position:0% foundation using standard modern web technologies. 02:40:55.510 --> 02:40:55.520 align:start position:0% technologies. 02:40:55.520 --> 02:40:58.389 align:start position:0% technologies. The<02:40:55.760> front-end<02:40:56.399> user<02:40:56.720> interface<02:40:57.680> provides<02:40:58.160> a 02:40:58.389 --> 02:40:58.399 align:start position:0% The front-end user interface provides a 02:40:58.399 --> 02:41:00.950 align:start position:0% The front-end user interface provides a seamless<02:40:59.120> smooth<02:40:59.600> experience<02:41:00.160> for<02:41:00.479> clinical 02:41:00.950 --> 02:41:00.960 align:start position:0% seamless smooth experience for clinical 02:41:00.960 --> 02:41:02.950 align:start position:0% seamless smooth experience for clinical patients<02:41:01.760> managing<02:41:02.240> their<02:41:02.479> healthcare 02:41:02.950 --> 02:41:02.960 align:start position:0% patients managing their healthcare 02:41:02.960 --> 02:41:04.469 align:start position:0% patients managing their healthcare needs. 02:41:04.469 --> 02:41:04.479 align:start position:0% needs. 02:41:04.479 --> 02:41:07.349 align:start position:0% needs. The<02:41:04.720> synthetic<02:41:05.359> mock<02:41:05.760> data<02:41:06.080> limitations<02:41:07.040> were 02:41:07.349 --> 02:41:07.359 align:start position:0% The synthetic mock data limitations were 02:41:07.359 --> 02:41:09.830 align:start position:0% The synthetic mock data limitations were overcome<02:41:07.840> by<02:41:08.160> implementing<02:41:08.800> dynamic<02:41:09.439> user 02:41:09.830 --> 02:41:09.840 align:start position:0% overcome by implementing dynamic user 02:41:09.840 --> 02:41:11.750 align:start position:0% overcome by implementing dynamic user input<02:41:10.240> handling. 02:41:11.750 --> 02:41:11.760 align:start position:0% input handling. 02:41:11.760 --> 02:41:14.309 align:start position:0% input handling. The<02:41:12.000> medical<02:41:12.399> appointmentuling<02:41:13.600> and<02:41:13.920> user 02:41:14.309 --> 02:41:14.319 align:start position:0% The medical appointmentuling and user 02:41:14.319 --> 02:41:17.030 align:start position:0% The medical appointmentuling and user cancellation<02:41:15.040> workflows<02:41:16.080> operate<02:41:16.640> without 02:41:17.030 --> 02:41:17.040 align:start position:0% cancellation workflows operate without 02:41:17.040 --> 02:41:20.469 align:start position:0% cancellation workflows operate without any<02:41:17.439> system<02:41:18.000> errors.<02:41:19.359> Essential<02:41:20.000> patient 02:41:20.469 --> 02:41:20.479 align:start position:0% any system errors. Essential patient 02:41:20.479 --> 02:41:23.110 align:start position:0% any system errors. Essential patient medical<02:41:20.880> records<02:41:21.439> remain<02:41:21.840> accessible<02:41:22.640> on<02:41:22.880> the 02:41:23.110 --> 02:41:23.120 align:start position:0% medical records remain accessible on the 02:41:23.120 --> 02:41:25.750 align:start position:0% medical records remain accessible on the personalized<02:41:23.840> user<02:41:24.240> dashboard 02:41:25.750 --> 02:41:25.760 align:start position:0% personalized user dashboard 02:41:25.760 --> 02:41:28.150 align:start position:0% personalized user dashboard by<02:41:26.160> utilizing<02:41:26.720> the<02:41:26.960> git<02:41:27.359> version<02:41:27.760> control 02:41:28.150 --> 02:41:28.160 align:start position:0% by utilizing the git version control 02:41:28.160 --> 02:41:30.790 align:start position:0% by utilizing the git version control system.<02:41:29.040> The<02:41:29.280> main<02:41:29.600> source<02:41:30.000> code<02:41:30.399> remains 02:41:30.790 --> 02:41:30.800 align:start position:0% system. The main source code remains 02:41:30.800 --> 02:41:34.230 align:start position:0% system. The main source code remains protected<02:41:31.359> against<02:41:31.840> accidental<02:41:32.479> data<02:41:32.800> loss. 02:41:34.230 --> 02:41:34.240 align:start position:0% protected against accidental data loss. 02:41:34.240 --> 02:41:37.190 align:start position:0% protected against accidental data loss. The<02:41:34.560> open<02:41:34.960> public<02:41:35.359> repository<02:41:36.399> allows<02:41:36.880> other 02:41:37.190 --> 02:41:37.200 align:start position:0% The open public repository allows other 02:41:37.200 --> 02:41:38.870 align:start position:0% The open public repository allows other software<02:41:37.600> developers<02:41:38.160> to<02:41:38.319> review<02:41:38.640> the 02:41:38.870 --> 02:41:38.880 align:start position:0% software developers to review the 02:41:38.880 --> 02:41:41.510 align:start position:0% software developers to review the application<02:41:39.439> project<02:41:39.920> structure. 02:41:41.510 --> 02:41:41.520 align:start position:0% application project structure. 02:41:41.520 --> 02:41:44.150 align:start position:0% application project structure. This<02:41:41.840> developer<02:41:42.399> workflow<02:41:43.280> demonstrates<02:41:43.920> a 02:41:44.150 --> 02:41:44.160 align:start position:0% This developer workflow demonstrates a 02:41:44.160 --> 02:41:46.070 align:start position:0% This developer workflow demonstrates a practical<02:41:44.720> approach<02:41:45.040> to<02:41:45.359> rapid<02:41:45.760> web 02:41:46.070 --> 02:41:46.080 align:start position:0% practical approach to rapid web 02:41:46.080 --> 02:41:47.990 align:start position:0% practical approach to rapid web application<02:41:46.720> development<02:41:47.359> and<02:41:47.680> code 02:41:47.990 --> 02:41:48.000 align:start position:0% application development and code 02:41:48.000 --> 02:41:49.590 align:start position:0% application development and code deployment. 02:41:49.590 --> 02:41:49.600 align:start position:0% deployment. 02:41:49.600 --> 02:41:51.590 align:start position:0% deployment. The<02:41:49.760> initial<02:41:50.240> system<02:41:50.640> setup<02:41:51.040> challenges 02:41:51.590 --> 02:41:51.600 align:start position:0% The initial system setup challenges 02:41:51.600 --> 02:41:53.349 align:start position:0% The initial system setup challenges regarding<02:41:52.160> local<02:41:52.479> machine<02:41:52.880> software 02:41:53.349 --> 02:41:53.359 align:start position:0% regarding local machine software 02:41:53.359 --> 02:41:55.750 align:start position:0% regarding local machine software requirements<02:41:54.319> were<02:41:54.640> resolved<02:41:55.120> with<02:41:55.359> great 02:41:55.750 --> 02:41:55.760 align:start position:0% requirements were resolved with great 02:41:55.760 --> 02:41:58.870 align:start position:0% requirements were resolved with great speed.<02:41:57.200> The<02:41:57.439> comprehensive<02:41:58.319> command 02:41:58.870 --> 02:41:58.880 align:start position:0% speed. The comprehensive command 02:41:58.880 --> 02:42:01.590 align:start position:0% speed. The comprehensive command terminal<02:41:59.359> instructions<02:42:00.399> ensured<02:42:00.960> execution 02:42:01.590 --> 02:42:01.600 align:start position:0% terminal instructions ensured execution 02:42:01.600 --> 02:42:04.710 align:start position:0% terminal instructions ensured execution of<02:42:01.920> necessary<02:42:02.560> developer<02:42:03.120> commands. 02:42:04.710 --> 02:42:04.720 align:start position:0% of necessary developer commands. 02:42:04.720 --> 02:42:07.110 align:start position:0% of necessary developer commands. The<02:42:04.960> final<02:42:05.359> software<02:42:05.840> outcome<02:42:06.640> is<02:42:06.880> a 02:42:07.110 --> 02:42:07.120 align:start position:0% The final software outcome is a 02:42:07.120 --> 02:42:10.230 align:start position:0% The final software outcome is a functional,<02:42:08.000> well<02:42:08.319> doumented<02:42:09.280> and<02:42:09.600> versioned 02:42:10.230 --> 02:42:10.240 align:start position:0% functional, well doumented and versioned 02:42:10.240 --> 02:42:12.469 align:start position:0% functional, well doumented and versioned front-end<02:42:10.880> application. 02:42:12.469 --> 02:42:12.479 align:start position:0% front-end application. 02:42:12.479 --> 02:42:14.150 align:start position:0% front-end application. The<02:42:12.720> established<02:42:13.280> project<02:42:13.600> goals<02:42:14.000> are 02:42:14.150 --> 02:42:14.160 align:start position:0% The established project goals are 02:42:14.160 --> 02:42:16.309 align:start position:0% The established project goals are fulfilled.<02:42:15.120> The<02:42:15.359> discussion<02:42:15.840> relates<02:42:16.160> to 02:42:16.309 --> 02:42:16.319 align:start position:0% fulfilled. The discussion relates to 02:42:16.319 --> 02:42:19.670 align:start position:0% fulfilled. The discussion relates to possible<02:42:16.720> iterations<02:42:17.359> we<02:42:17.600> can<02:42:17.760> include<02:42:18.080> here. 02:42:19.670 --> 02:42:19.680 align:start position:0% possible iterations we can include here. 02:42:19.680 --> 02:42:22.469 align:start position:0% possible iterations we can include here. In<02:42:19.920> our<02:42:20.160> use<02:42:20.399> cases,<02:42:21.359> we<02:42:21.600> create<02:42:21.920> projects 02:42:22.469 --> 02:42:22.479 align:start position:0% In our use cases, we create projects 02:42:22.479 --> 02:42:25.590 align:start position:0% In our use cases, we create projects multiple<02:42:22.960> times<02:42:23.520> requiring<02:42:24.080> iterations. 02:42:25.590 --> 02:42:25.600 align:start position:0% multiple times requiring iterations. 02:42:25.600 --> 02:42:27.429 align:start position:0% multiple times requiring iterations. We<02:42:25.840> can<02:42:26.000> include<02:42:26.240> these<02:42:26.479> iterations<02:42:27.040> to<02:42:27.280> see 02:42:27.429 --> 02:42:27.439 align:start position:0% We can include these iterations to see 02:42:27.439 --> 02:42:29.590 align:start position:0% We can include these iterations to see what<02:42:27.600> is<02:42:27.840> possible. 02:42:29.590 --> 02:42:29.600 align:start position:0% what is possible. 02:42:29.600 --> 02:42:31.990 align:start position:0% what is possible. Iterations<02:42:30.160> start<02:42:30.399> from<02:42:30.640> the<02:42:30.800> beginning.<02:42:31.760> We 02:42:31.990 --> 02:42:32.000 align:start position:0% Iterations start from the beginning. We 02:42:32.000 --> 02:42:34.870 align:start position:0% Iterations start from the beginning. We include<02:42:32.319> project<02:42:32.720> details<02:42:33.200> and<02:42:33.439> formats. 02:42:34.870 --> 02:42:34.880 align:start position:0% include project details and formats. 02:42:34.880 --> 02:42:36.790 align:start position:0% include project details and formats. Another<02:42:35.280> option<02:42:35.680> is<02:42:35.920> available<02:42:36.399> after 02:42:36.790 --> 02:42:36.800 align:start position:0% Another option is available after 02:42:36.800 --> 02:42:40.150 align:start position:0% Another option is available after project<02:42:37.200> creation.<02:42:38.560> Moving<02:42:38.880> to<02:42:39.040> the<02:42:39.280> end,<02:42:39.840> our 02:42:40.150 --> 02:42:40.160 align:start position:0% project creation. Moving to the end, our 02:42:40.160 --> 02:42:42.950 align:start position:0% project creation. Moving to the end, our index<02:42:40.560> was<02:42:40.800> complete<02:42:41.040> at<02:42:41.280> this<02:42:41.439> step. 02:42:42.950 --> 02:42:42.960 align:start position:0% index was complete at this step. 02:42:42.960 --> 02:42:45.190 align:start position:0% index was complete at this step. Here<02:42:43.359> in<02:42:43.600> front<02:42:43.920> end,<02:42:44.399> back<02:42:44.640> end, 02:42:45.190 --> 02:42:45.200 align:start position:0% Here in front end, back end, 02:42:45.200 --> 02:42:47.750 align:start position:0% Here in front end, back end, appointments<02:42:45.840> and<02:42:46.160> records,<02:42:46.960> our<02:42:47.200> option<02:42:47.520> has 02:42:47.750 --> 02:42:47.760 align:start position:0% appointments and records, our option has 02:42:47.760 --> 02:42:51.670 align:start position:0% appointments and records, our option has arrived.<02:42:49.200> Changes<02:42:49.680> are<02:42:49.920> never<02:42:50.240> small.<02:42:51.359> For 02:42:51.670 --> 02:42:51.680 align:start position:0% arrived. Changes are never small. For 02:42:51.680 --> 02:42:53.830 align:start position:0% arrived. Changes are never small. For changes,<02:42:52.560> we<02:42:52.800> will<02:42:52.960> include<02:42:53.280> details 02:42:53.830 --> 02:42:53.840 align:start position:0% changes, we will include details 02:42:53.840 --> 02:42:56.790 align:start position:0% changes, we will include details multiple<02:42:54.399> times.<02:42:55.680> Another<02:42:56.160> important<02:42:56.640> thing 02:42:56.790 --> 02:42:56.800 align:start position:0% multiple times. Another important thing 02:42:56.800 --> 02:42:58.870 align:start position:0% multiple times. Another important thing is<02:42:57.200> working<02:42:57.439> in<02:42:57.680> an<02:42:57.840> environment<02:42:58.319> requiring 02:42:58.870 --> 02:42:58.880 align:start position:0% is working in an environment requiring 02:42:58.880 --> 02:43:00.790 align:start position:0% is working in an environment requiring code<02:42:59.200> changes. 02:43:00.790 --> 02:43:00.800 align:start position:0% code changes. 02:43:00.800 --> 02:43:03.830 align:start position:0% code changes. Iterations<02:43:01.439> become<02:43:01.840> version<02:43:02.319> based.<02:43:03.520> The 02:43:03.830 --> 02:43:03.840 align:start position:0% Iterations become version based. The 02:43:03.840 --> 02:43:05.670 align:start position:0% Iterations become version based. The first<02:43:04.080> website<02:43:04.560> version<02:43:05.040> was<02:43:05.359> quite 02:43:05.670 --> 02:43:05.680 align:start position:0% first website version was quite 02:43:05.680 --> 02:43:08.070 align:start position:0% first website version was quite different<02:43:05.920> from<02:43:06.160> the<02:43:06.399> current<02:43:06.640> version.<02:43:07.840> We 02:43:08.070 --> 02:43:08.080 align:start position:0% different from the current version. We 02:43:08.080 --> 02:43:10.070 align:start position:0% different from the current version. We must<02:43:08.399> understand<02:43:08.880> version<02:43:09.280> histories<02:43:09.680> to<02:43:09.920> see 02:43:10.070 --> 02:43:10.080 align:start position:0% must understand version histories to see 02:43:10.080 --> 02:43:12.550 align:start position:0% must understand version histories to see which<02:43:10.319> was<02:43:10.479> more<02:43:10.720> compatible. 02:43:12.550 --> 02:43:12.560 align:start position:0% which was more compatible. 02:43:12.560 --> 02:43:14.550 align:start position:0% which was more compatible. Sometimes<02:43:13.040> we<02:43:13.280> include<02:43:13.760> specific<02:43:14.240> things 02:43:14.550 --> 02:43:14.560 align:start position:0% Sometimes we include specific things 02:43:14.560 --> 02:43:17.429 align:start position:0% Sometimes we include specific things from<02:43:14.720> a<02:43:14.960> specific<02:43:15.439> version.<02:43:16.640> Going<02:43:16.960> into<02:43:17.200> our 02:43:17.429 --> 02:43:17.439 align:start position:0% from a specific version. Going into our 02:43:17.439 --> 02:43:20.790 align:start position:0% from a specific version. Going into our project,<02:43:18.240> this<02:43:18.479> was<02:43:18.640> the<02:43:18.880> final<02:43:19.120> version. 02:43:20.790 --> 02:43:20.800 align:start position:0% project, this was the final version. 02:43:20.800 --> 02:43:23.190 align:start position:0% project, this was the final version. Looking<02:43:21.040> at<02:43:21.280> this<02:43:21.439> project,<02:43:22.399> considering<02:43:22.880> the 02:43:23.190 --> 02:43:23.200 align:start position:0% Looking at this project, considering the 02:43:23.200 --> 02:43:26.550 align:start position:0% Looking at this project, considering the whole<02:43:23.439> use<02:43:23.680> case,<02:43:24.479> the<02:43:24.720> logo<02:43:25.040> is<02:43:25.200> incorrect. 02:43:26.550 --> 02:43:26.560 align:start position:0% whole use case, the logo is incorrect. 02:43:26.560 --> 02:43:29.190 align:start position:0% whole use case, the logo is incorrect. We<02:43:26.800> can<02:43:26.960> change<02:43:27.200> the<02:43:27.439> logo.<02:43:28.479> The<02:43:28.720> dashboard 02:43:29.190 --> 02:43:29.200 align:start position:0% We can change the logo. The dashboard 02:43:29.200 --> 02:43:31.270 align:start position:0% We can change the logo. The dashboard should<02:43:29.439> be<02:43:29.520> a<02:43:29.760> sliding<02:43:30.240> dashboard,<02:43:30.880> not<02:43:31.120> a 02:43:31.270 --> 02:43:31.280 align:start position:0% should be a sliding dashboard, not a 02:43:31.280 --> 02:43:34.389 align:start position:0% should be a sliding dashboard, not a consistent<02:43:31.760> one.<02:43:32.880> Instead<02:43:33.280> of<02:43:33.439> this,<02:43:34.160> some 02:43:34.389 --> 02:43:34.399 align:start position:0% consistent one. Instead of this, some 02:43:34.399 --> 02:43:37.190 align:start position:0% consistent one. Instead of this, some analytics<02:43:35.040> should<02:43:35.280> be<02:43:35.359> involved<02:43:35.760> here. 02:43:37.190 --> 02:43:37.200 align:start position:0% analytics should be involved here. 02:43:37.200 --> 02:43:39.750 align:start position:0% analytics should be involved here. Looking<02:43:37.600> here,<02:43:38.240> the<02:43:38.560> card<02:43:38.880> distance<02:43:39.359> and<02:43:39.520> the 02:43:39.750 --> 02:43:39.760 align:start position:0% Looking here, the card distance and the 02:43:39.760 --> 02:43:41.429 align:start position:0% Looking here, the card distance and the empty<02:43:40.080> space<02:43:40.319> in<02:43:40.479> the<02:43:40.720> website<02:43:41.120> should<02:43:41.280> be 02:43:41.429 --> 02:43:41.439 align:start position:0% empty space in the website should be 02:43:41.439 --> 02:43:44.070 align:start position:0% empty space in the website should be minimal.<02:43:42.720> We<02:43:42.960> should<02:43:43.120> fill<02:43:43.359> such<02:43:43.680> spaces 02:43:44.070 --> 02:43:44.080 align:start position:0% minimal. We should fill such spaces 02:43:44.080 --> 02:43:45.910 align:start position:0% minimal. We should fill such spaces beforehand. 02:43:45.910 --> 02:43:45.920 align:start position:0% beforehand. 02:43:45.920 --> 02:43:48.389 align:start position:0% beforehand. In<02:43:46.160> our<02:43:46.399> website<02:43:46.800> text,<02:43:47.680> search<02:43:48.080> engine 02:43:48.389 --> 02:43:48.399 align:start position:0% In our website text, search engine 02:43:48.399 --> 02:43:51.590 align:start position:0% In our website text, search engine optimization<02:43:49.120> is<02:43:49.439> not<02:43:49.760> involved.<02:43:51.040> The<02:43:51.279> colors 02:43:51.590 --> 02:43:51.600 align:start position:0% optimization is not involved. The colors 02:43:51.600 --> 02:43:54.309 align:start position:0% optimization is not involved. The colors involved<02:43:52.000> here<02:43:52.240> are<02:43:52.479> quite<02:43:52.800> dull.<02:43:53.920> We<02:43:54.160> can 02:43:54.309 --> 02:43:54.319 align:start position:0% involved here are quite dull. We can 02:43:54.319 --> 02:43:56.389 align:start position:0% involved here are quite dull. We can improve<02:43:54.800> all<02:43:54.960> these<02:43:55.279> things<02:43:55.760> just<02:43:56.000> by<02:43:56.160> giving 02:43:56.389 --> 02:43:56.399 align:start position:0% improve all these things just by giving 02:43:56.399 --> 02:43:59.269 align:start position:0% improve all these things just by giving it<02:43:56.640> some<02:43:56.800> prompts.<02:43:58.240> Our<02:43:58.560> iteration<02:43:59.040> will 02:43:59.269 --> 02:43:59.279 align:start position:0% it some prompts. Our iteration will 02:43:59.279 --> 02:44:01.750 align:start position:0% it some prompts. Our iteration will start<02:43:59.520> happening.<02:44:00.000> Now<02:44:01.200> alongside 02:44:01.750 --> 02:44:01.760 align:start position:0% start happening. Now alongside 02:44:01.760 --> 02:44:04.389 align:start position:0% start happening. Now alongside iteration,<02:44:02.960> another<02:44:03.439> important<02:44:03.840> thing<02:44:04.080> is 02:44:04.389 --> 02:44:04.399 align:start position:0% iteration, another important thing is 02:44:04.399 --> 02:44:06.550 align:start position:0% iteration, another important thing is making<02:44:04.800> large<02:44:05.200> scale<02:44:05.520> improvements<02:44:06.160> via 02:44:06.550 --> 02:44:06.560 align:start position:0% making large scale improvements via 02:44:06.560 --> 02:44:09.510 align:start position:0% making large scale improvements via prompts.<02:44:08.000> Since<02:44:08.319> this<02:44:08.479> tool<02:44:08.800> is<02:44:08.960> based<02:44:09.200> on<02:44:09.279> our 02:44:09.510 --> 02:44:09.520 align:start position:0% prompts. Since this tool is based on our 02:44:09.520 --> 02:44:11.830 align:start position:0% prompts. Since this tool is based on our prompts,<02:44:10.479> any<02:44:10.800> new<02:44:11.040> improvement<02:44:11.520> will<02:44:11.760> be 02:44:11.830 --> 02:44:11.840 align:start position:0% prompts, any new improvement will be 02:44:11.840 --> 02:44:14.630 align:start position:0% prompts, any new improvement will be based<02:44:12.080> on<02:44:12.240> prompts.<02:44:13.439> There<02:44:13.680> is<02:44:13.920> no<02:44:14.160> other<02:44:14.479> way 02:44:14.630 --> 02:44:14.640 align:start position:0% based on prompts. There is no other way 02:44:14.640 --> 02:44:17.590 align:start position:0% based on prompts. There is no other way to<02:44:14.880> improve<02:44:15.200> our<02:44:15.439> stuff.<02:44:16.880> These<02:44:17.200> things<02:44:17.439> will 02:44:17.590 --> 02:44:17.600 align:start position:0% to improve our stuff. These things will 02:44:17.600 --> 02:44:20.389 align:start position:0% to improve our stuff. These things will be<02:44:17.760> induced<02:44:18.160> here<02:44:18.319> with<02:44:18.479> our<02:44:18.720> ongoing<02:44:19.200> time. 02:44:20.389 --> 02:44:20.399 align:start position:0% be induced here with our ongoing time. 02:44:20.399 --> 02:44:23.110 align:start position:0% be induced here with our ongoing time. As<02:44:20.640> our<02:44:20.880> time<02:44:21.120> increases,<02:44:22.160> we<02:44:22.399> must<02:44:22.720> iterate 02:44:23.110 --> 02:44:23.120 align:start position:0% As our time increases, we must iterate 02:44:23.120 --> 02:44:25.030 align:start position:0% As our time increases, we must iterate these<02:44:23.439> things<02:44:23.760> and<02:44:24.080> see<02:44:24.319> how<02:44:24.479> we<02:44:24.640> are<02:44:24.800> taking 02:44:25.030 --> 02:44:25.040 align:start position:0% these things and see how we are taking 02:44:25.040 --> 02:44:26.870 align:start position:0% these things and see how we are taking them<02:44:25.200> forward. 02:44:26.870 --> 02:44:26.880 align:start position:0% them forward. 02:44:26.880 --> 02:44:29.510 align:start position:0% them forward. Along<02:44:27.200> with<02:44:27.439> this,<02:44:28.319> another<02:44:28.720> important<02:44:29.200> thing 02:44:29.510 --> 02:44:29.520 align:start position:0% Along with this, another important thing 02:44:29.520 --> 02:44:31.429 align:start position:0% Along with this, another important thing is<02:44:29.680> that<02:44:29.920> when<02:44:30.160> making<02:44:30.479> improvements<02:44:31.120> based 02:44:31.429 --> 02:44:31.439 align:start position:0% is that when making improvements based 02:44:31.439 --> 02:44:34.950 align:start position:0% is that when making improvements based on<02:44:31.680> prompts,<02:44:32.720> error<02:44:32.960> chances<02:44:33.600> increase. 02:44:34.950 --> 02:44:34.960 align:start position:0% on prompts, error chances increase. 02:44:34.960 --> 02:44:37.030 align:start position:0% on prompts, error chances increase. Therefore,<02:44:35.760> we<02:44:36.000> should<02:44:36.160> review<02:44:36.479> our<02:44:36.800> code 02:44:37.030 --> 02:44:37.040 align:start position:0% Therefore, we should review our code 02:44:37.040 --> 02:44:40.309 align:start position:0% Therefore, we should review our code first.<02:44:38.479> After<02:44:38.880> reviewing<02:44:39.279> the<02:44:39.520> code,<02:44:40.080> we 02:44:40.309 --> 02:44:40.319 align:start position:0% first. After reviewing the code, we 02:44:40.319 --> 02:44:41.910 align:start position:0% first. After reviewing the code, we should<02:44:40.479> take<02:44:40.720> things<02:44:41.040> towards<02:44:41.439> our<02:44:41.680> other 02:44:41.910 --> 02:44:41.920 align:start position:0% should take things towards our other 02:44:41.920 --> 02:44:44.630 align:start position:0% should take things towards our other generations<02:44:42.560> and<02:44:42.800> discussions. 02:44:44.630 --> 02:44:44.640 align:start position:0% generations and discussions. 02:44:44.640 --> 02:44:47.590 align:start position:0% generations and discussions. Sometimes<02:44:45.600> within<02:44:45.920> our<02:44:46.160> code<02:44:46.399> itself,<02:44:47.359> there 02:44:47.590 --> 02:44:47.600 align:start position:0% Sometimes within our code itself, there 02:44:47.600 --> 02:44:49.349 align:start position:0% Sometimes within our code itself, there are<02:44:47.760> multiple<02:44:48.319> errors<02:44:48.560> we<02:44:48.800> spend<02:44:49.040> time 02:44:49.349 --> 02:44:49.359 align:start position:0% are multiple errors we spend time 02:44:49.359 --> 02:44:50.870 align:start position:0% are multiple errors we spend time correcting. 02:44:50.870 --> 02:44:50.880 align:start position:0% correcting. 02:44:50.880 --> 02:44:52.710 align:start position:0% correcting. We<02:44:51.120> are<02:44:51.279> focusing<02:44:51.600> on<02:44:51.840> making<02:44:52.080> the<02:44:52.240> dashboard 02:44:52.710 --> 02:44:52.720 align:start position:0% We are focusing on making the dashboard 02:44:52.720 --> 02:44:55.590 align:start position:0% We are focusing on making the dashboard intuitive.<02:44:54.160> The<02:44:54.479> layout<02:44:54.720> needs<02:44:55.040> adjustments, 02:44:55.590 --> 02:44:55.600 align:start position:0% intuitive. The layout needs adjustments, 02:44:55.600 --> 02:44:57.910 align:start position:0% intuitive. The layout needs adjustments, so<02:44:55.920> upcoming<02:44:56.399> visits<02:44:56.800> and<02:44:57.040> active<02:44:57.439> reminders 02:44:57.910 --> 02:44:57.920 align:start position:0% so upcoming visits and active reminders 02:44:57.920 --> 02:45:00.309 align:start position:0% so upcoming visits and active reminders are<02:44:58.160> visible<02:44:58.399> to<02:44:58.560> the<02:44:58.800> user. 02:45:00.309 --> 02:45:00.319 align:start position:0% are visible to the user. 02:45:00.319 --> 02:45:02.550 align:start position:0% are visible to the user. Care<02:45:00.640> teams<02:45:00.960> and<02:45:01.200> appointment<02:45:01.680> sections<02:45:02.240> must 02:45:02.550 --> 02:45:02.560 align:start position:0% Care teams and appointment sections must 02:45:02.560 --> 02:45:05.750 align:start position:0% Care teams and appointment sections must be<02:45:02.720> integrated<02:45:03.359> together.<02:45:04.640> This<02:45:04.960> ensures<02:45:05.439> the 02:45:05.750 --> 02:45:05.760 align:start position:0% be integrated together. This ensures the 02:45:05.760 --> 02:45:07.910 align:start position:0% be integrated together. This ensures the entire<02:45:06.240> application<02:45:06.880> functions<02:45:07.439> without 02:45:07.910 --> 02:45:07.920 align:start position:0% entire application functions without 02:45:07.920 --> 02:45:11.269 align:start position:0% entire application functions without visual<02:45:08.319> or<02:45:08.560> technical<02:45:09.040> interruptions. 02:45:11.269 --> 02:45:11.279 align:start position:0% visual or technical interruptions. 02:45:11.279 --> 02:45:13.269 align:start position:0% visual or technical interruptions. This<02:45:11.600> completes<02:45:12.000> our<02:45:12.319> entire<02:45:12.720> discussion 02:45:13.269 --> 02:45:13.279 align:start position:0% This completes our entire discussion 02:45:13.279 --> 02:45:15.750 align:start position:0% This completes our entire discussion related<02:45:13.680> to<02:45:13.840> our<02:45:14.080> iteration. 02:45:15.750 --> 02:45:15.760 align:start position:0% related to our iteration. 02:45:15.760 --> 02:45:18.150 align:start position:0% related to our iteration. Along<02:45:16.000> with<02:45:16.160> the<02:45:16.319> iteration,<02:45:17.439> we<02:45:17.760> covered 02:45:18.150 --> 02:45:18.160 align:start position:0% Along with the iteration, we covered 02:45:18.160 --> 02:45:19.990 align:start position:0% Along with the iteration, we covered possible<02:45:18.640> improvements<02:45:19.120> that<02:45:19.359> needed<02:45:19.680> to<02:45:19.840> be 02:45:19.990 --> 02:45:20.000 align:start position:0% possible improvements that needed to be 02:45:20.000 --> 02:45:21.590 align:start position:0% possible improvements that needed to be discussed. 02:45:21.590 --> 02:45:21.600 align:start position:0% discussed. 02:45:21.600 --> 02:45:23.750 align:start position:0% discussed. Looking<02:45:21.920> at<02:45:22.080> the<02:45:22.240> bottom<02:45:22.560> section,<02:45:23.439> the 02:45:23.750 --> 02:45:23.760 align:start position:0% Looking at the bottom section, the 02:45:23.760 --> 02:45:26.230 align:start position:0% Looking at the bottom section, the reminders<02:45:24.240> and<02:45:24.560> profile<02:45:25.120> loaded<02:45:25.600> cards<02:45:26.000> have 02:45:26.230 --> 02:45:26.240 align:start position:0% reminders and profile loaded cards have 02:45:26.240 --> 02:45:28.550 align:start position:0% reminders and profile loaded cards have gaps<02:45:26.640> needing<02:45:27.040> fixes. 02:45:28.550 --> 02:45:28.560 align:start position:0% gaps needing fixes. 02:45:28.560 --> 02:45:30.550 align:start position:0% gaps needing fixes. The<02:45:28.800> design<02:45:29.120> should<02:45:29.359> feel<02:45:29.680> premium<02:45:30.240> and 02:45:30.550 --> 02:45:30.560 align:start position:0% The design should feel premium and 02:45:30.560 --> 02:45:32.309 align:start position:0% The design should feel premium and responsive. 02:45:32.309 --> 02:45:32.319 align:start position:0% responsive. 02:45:32.319 --> 02:45:34.469 align:start position:0% responsive. The<02:45:32.640> patient<02:45:33.040> readiness<02:45:33.520> items<02:45:34.000> must<02:45:34.319> be 02:45:34.469 --> 02:45:34.479 align:start position:0% The patient readiness items must be 02:45:34.479 --> 02:45:37.590 align:start position:0% The patient readiness items must be tracked<02:45:34.800> on<02:45:35.040> one<02:45:35.359> premium<02:45:35.920> dashboard. 02:45:37.590 --> 02:45:37.600 align:start position:0% tracked on one premium dashboard. 02:45:37.600 --> 02:45:39.269 align:start position:0% tracked on one premium dashboard. When<02:45:37.920> looking<02:45:38.080> at<02:45:38.319> source<02:45:38.720> options<02:45:39.040> for 02:45:39.269 --> 02:45:39.279 align:start position:0% When looking at source options for 02:45:39.279 --> 02:45:41.590 align:start position:0% When looking at source options for medical<02:45:39.600> centers<02:45:40.319> like<02:45:40.560> Providence<02:45:41.120> Alaska 02:45:41.590 --> 02:45:41.600 align:start position:0% medical centers like Providence Alaska 02:45:41.600 --> 02:45:43.910 align:start position:0% medical centers like Providence Alaska Medical<02:45:42.000> Center<02:45:42.399> or<02:45:42.720> Alaska<02:45:43.200> Native<02:45:43.600> Medical 02:45:43.910 --> 02:45:43.920 align:start position:0% Medical Center or Alaska Native Medical 02:45:43.920 --> 02:45:47.750 align:start position:0% Medical Center or Alaska Native Medical Center,<02:45:45.040> information<02:45:45.680> must<02:45:46.000> be<02:45:46.160> displayed. 02:45:47.750 --> 02:45:47.760 align:start position:0% Center, information must be displayed. 02:45:47.760 --> 02:45:49.590 align:start position:0% Center, information must be displayed. The<02:45:48.160> layout<02:45:48.399> structure<02:45:48.880> lacks<02:45:49.279> proper 02:45:49.590 --> 02:45:49.600 align:start position:0% The layout structure lacks proper 02:45:49.600 --> 02:45:51.830 align:start position:0% The layout structure lacks proper alignment<02:45:50.560> and<02:45:50.800> text<02:45:51.200> blocks<02:45:51.600> feel 02:45:51.830 --> 02:45:51.840 align:start position:0% alignment and text blocks feel 02:45:51.840 --> 02:45:53.510 align:start position:0% alignment and text blocks feel disconnected. 02:45:53.510 --> 02:45:53.520 align:start position:0% disconnected. 02:45:53.520 --> 02:45:55.910 align:start position:0% disconnected. We<02:45:53.760> will<02:45:54.000> use<02:45:54.319> specific<02:45:54.880> commands<02:45:55.359> to<02:45:55.600> refine 02:45:55.910 --> 02:45:55.920 align:start position:0% We will use specific commands to refine 02:45:55.920 --> 02:45:58.469 align:start position:0% We will use specific commands to refine these<02:45:56.160> interface<02:45:56.720> elements. 02:45:58.469 --> 02:45:58.479 align:start position:0% these interface elements. 02:45:58.479 --> 02:46:01.030 align:start position:0% these interface elements. Once<02:45:58.800> we<02:45:58.960> apply<02:45:59.279> new<02:45:59.520> styles,<02:46:00.399> the<02:46:00.640> final 02:46:01.030 --> 02:46:01.040 align:start position:0% Once we apply new styles, the final 02:46:01.040 --> 02:46:03.830 align:start position:0% Once we apply new styles, the final product<02:46:01.359> will<02:46:01.600> look<02:46:01.840> more<02:46:02.080> professional. 02:46:03.830 --> 02:46:03.840 align:start position:0% product will look more professional. 02:46:03.840 --> 02:46:05.269 align:start position:0% product will look more professional. Everything<02:46:04.240> will<02:46:04.479> be<02:46:04.640> committed<02:46:04.960> to<02:46:05.120> the 02:46:05.269 --> 02:46:05.279 align:start position:0% Everything will be committed to the 02:46:05.279 --> 02:46:07.990 align:start position:0% Everything will be committed to the repository,<02:46:06.399> ensuring<02:46:06.960> all<02:46:07.279> changes<02:46:07.760> are 02:46:07.990 --> 02:46:08.000 align:start position:0% repository, ensuring all changes are 02:46:08.000 --> 02:46:10.230 align:start position:0% repository, ensuring all changes are saved<02:46:08.319> and<02:46:08.560> tracked<02:46:08.880> for<02:46:09.120> future<02:46:09.520> updates<02:46:10.000> and 02:46:10.230 --> 02:46:10.240 align:start position:0% saved and tracked for future updates and 02:46:10.240 --> 02:46:12.389 align:start position:0% saved and tracked for future updates and continuous<02:46:10.800> development.<02:46:11.680> Now<02:46:11.920> comes<02:46:12.160> the 02:46:12.389 --> 02:46:12.399 align:start position:0% continuous development. Now comes the 02:46:12.399 --> 02:46:15.190 align:start position:0% continuous development. Now comes the last<02:46:12.640> part.<02:46:13.840> At<02:46:14.080> the<02:46:14.240> end<02:46:14.319> of<02:46:14.479> this<02:46:14.720> course, 02:46:15.190 --> 02:46:15.200 align:start position:0% last part. At the end of this course, 02:46:15.200 --> 02:46:17.910 align:start position:0% last part. At the end of this course, you<02:46:15.439> saw<02:46:15.760> one<02:46:16.080> main<02:46:16.399> thing.<02:46:17.359> It<02:46:17.600> was<02:46:17.680> our 02:46:17.910 --> 02:46:17.920 align:start position:0% you saw one main thing. It was our 02:46:17.920 --> 02:46:20.950 align:start position:0% you saw one main thing. It was our GitHub<02:46:18.399> and<02:46:18.640> codeex<02:46:19.120> tools.<02:46:20.240> We<02:46:20.479> tried<02:46:20.720> to 02:46:20.950 --> 02:46:20.960 align:start position:0% GitHub and codeex tools. We tried to 02:46:20.960 --> 02:46:23.670 align:start position:0% GitHub and codeex tools. We tried to connect<02:46:21.279> GitHub.<02:46:22.399> Then<02:46:22.640> we<02:46:22.800> got<02:46:23.040> many<02:46:23.359> tech 02:46:23.670 --> 02:46:23.680 align:start position:0% connect GitHub. Then we got many tech 02:46:23.680 --> 02:46:26.630 align:start position:0% connect GitHub. Then we got many tech issues.<02:46:24.880> I<02:46:25.120> will<02:46:25.279> say<02:46:25.520> here<02:46:25.920> I<02:46:26.160> will<02:46:26.319> use<02:46:26.479> our 02:46:26.630 --> 02:46:26.640 align:start position:0% issues. I will say here I will use our 02:46:26.640 --> 02:46:29.590 align:start position:0% issues. I will say here I will use our plugin<02:46:27.040> of<02:46:27.200> GitHub.<02:46:27.680> Now<02:46:28.720> I<02:46:28.960> will<02:46:29.200> start<02:46:29.359> a 02:46:29.590 --> 02:46:29.600 align:start position:0% plugin of GitHub. Now I will start a 02:46:29.600 --> 02:46:32.230 align:start position:0% plugin of GitHub. Now I will start a discussion<02:46:29.920> with<02:46:30.080> the<02:46:30.319> GitHub<02:46:30.720> plug-in<02:46:31.120> tool. 02:46:32.230 --> 02:46:32.240 align:start position:0% discussion with the GitHub plug-in tool. 02:46:32.240 --> 02:46:34.790 align:start position:0% discussion with the GitHub plug-in tool. I<02:46:32.479> will<02:46:32.640> ask<02:46:33.520> can<02:46:33.760> you<02:46:33.920> check<02:46:34.080> if<02:46:34.319> GitHub 02:46:34.790 --> 02:46:34.800 align:start position:0% I will ask can you check if GitHub 02:46:34.800 --> 02:46:37.590 align:start position:0% I will ask can you check if GitHub plugin<02:46:35.200> is<02:46:35.359> working.<02:46:36.800> This<02:46:37.040> will<02:46:37.200> test<02:46:37.439> our 02:46:37.590 --> 02:46:37.600 align:start position:0% plugin is working. This will test our 02:46:37.600 --> 02:46:40.230 align:start position:0% plugin is working. This will test our plug-in<02:46:38.000> once.<02:46:38.960> We<02:46:39.200> will<02:46:39.279> see<02:46:39.439> if<02:46:39.600> our<02:46:39.840> plug-in 02:46:40.230 --> 02:46:40.240 align:start position:0% plug-in once. We will see if our plug-in 02:46:40.240 --> 02:46:43.190 align:start position:0% plug-in once. We will see if our plug-in works<02:46:40.399> in<02:46:40.640> any<02:46:40.880> user<02:46:41.200> case.<02:46:42.399> If<02:46:42.640> our<02:46:42.880> plug-in 02:46:43.190 --> 02:46:43.200 align:start position:0% works in any user case. If our plug-in 02:46:43.200 --> 02:46:46.309 align:start position:0% works in any user case. If our plug-in is<02:46:43.439> not<02:46:43.600> available,<02:46:44.319> we<02:46:44.560> can<02:46:44.720> check<02:46:44.960> it.<02:46:46.160> You 02:46:46.309 --> 02:46:46.319 align:start position:0% is not available, we can check it. You 02:46:46.319 --> 02:46:49.110 align:start position:0% is not available, we can check it. You can<02:46:46.479> see<02:46:46.640> we<02:46:46.880> have<02:46:47.040> verification<02:46:47.840> now.<02:46:48.960> You 02:46:49.110 --> 02:46:49.120 align:start position:0% can see we have verification now. You 02:46:49.120 --> 02:46:51.670 align:start position:0% can see we have verification now. You can<02:46:49.279> see<02:46:49.439> that<02:46:49.600> I<02:46:49.840> have<02:46:49.920> verified<02:46:50.399> it.<02:46:51.359> This 02:46:51.670 --> 02:46:51.680 align:start position:0% can see that I have verified it. This 02:46:51.680 --> 02:46:54.230 align:start position:0% can see that I have verified it. This login<02:46:52.080> account<02:46:52.319> Robert<02:46:52.720> is<02:46:52.960> here.<02:46:53.840> You<02:46:54.080> will 02:46:54.230 --> 02:46:54.240 align:start position:0% login account Robert is here. You will 02:46:54.240 --> 02:46:56.630 align:start position:0% login account Robert is here. You will remember<02:46:54.560> our<02:46:54.880> main<02:46:55.120> account<02:46:55.439> here<02:46:56.160> that<02:46:56.399> is 02:46:56.630 --> 02:46:56.640 align:start position:0% remember our main account here that is 02:46:56.640 --> 02:46:59.750 align:start position:0% remember our main account here that is connected<02:46:57.040> here.<02:46:58.160> Its<02:46:58.479> user<02:46:58.880> ID<02:46:59.200> has<02:46:59.439> also 02:46:59.750 --> 02:46:59.760 align:start position:0% connected here. Its user ID has also 02:46:59.760 --> 02:47:02.309 align:start position:0% connected here. Its user ID has also come<02:47:00.560> that<02:47:00.880> confirmed<02:47:01.359> that<02:47:01.520> the<02:47:01.680> plug-in<02:47:02.080> is 02:47:02.309 --> 02:47:02.319 align:start position:0% come that confirmed that the plug-in is 02:47:02.319 --> 02:47:05.990 align:start position:0% come that confirmed that the plug-in is installed,<02:47:03.120> reachable<02:47:03.760> and<02:47:04.080> authenticated. 02:47:05.990 --> 02:47:06.000 align:start position:0% installed, reachable and authenticated. 02:47:06.000 --> 02:47:09.190 align:start position:0% installed, reachable and authenticated. Now<02:47:06.240> I<02:47:06.479> can<02:47:06.640> say<02:47:07.040> what<02:47:07.279> can<02:47:07.439> I<02:47:07.600> do<02:47:07.760> with<02:47:07.920> this. 02:47:09.190 --> 02:47:09.200 align:start position:0% Now I can say what can I do with this. 02:47:09.200 --> 02:47:11.830 align:start position:0% Now I can say what can I do with this. This<02:47:09.439> will<02:47:09.600> start<02:47:09.840> giving<02:47:10.080> us<02:47:10.319> a<02:47:10.479> response.<02:47:11.680> It 02:47:11.830 --> 02:47:11.840 align:start position:0% This will start giving us a response. It 02:47:11.840 --> 02:47:13.429 align:start position:0% This will start giving us a response. It will<02:47:12.000> tell<02:47:12.160> us<02:47:12.399> where<02:47:12.640> we<02:47:12.880> can<02:47:13.040> use<02:47:13.200> this 02:47:13.429 --> 02:47:13.439 align:start position:0% will tell us where we can use this 02:47:13.439 --> 02:47:16.630 align:start position:0% will tell us where we can use this plug-in.<02:47:14.800> This<02:47:15.040> tool<02:47:15.439> is<02:47:15.680> not<02:47:15.920> available<02:47:16.240> on<02:47:16.479> a 02:47:16.630 --> 02:47:16.640 align:start position:0% plug-in. This tool is not available on a 02:47:16.640 --> 02:47:19.349 align:start position:0% plug-in. This tool is not available on a weak<02:47:16.960> level.<02:47:18.000> But<02:47:18.160> still<02:47:18.479> we<02:47:18.800> have<02:47:18.880> to<02:47:19.040> see<02:47:19.200> how 02:47:19.349 --> 02:47:19.359 align:start position:0% weak level. But still we have to see how 02:47:19.359 --> 02:47:22.070 align:start position:0% weak level. But still we have to see how our<02:47:19.600> tool<02:47:19.840> can<02:47:20.080> work.<02:47:20.319> Here<02:47:21.520> you<02:47:21.760> will<02:47:21.920> see 02:47:22.070 --> 02:47:22.080 align:start position:0% our tool can work. Here you will see 02:47:22.080 --> 02:47:24.469 align:start position:0% our tool can work. Here you will see here<02:47:22.399> it<02:47:22.640> says<02:47:23.200> you<02:47:23.439> can<02:47:23.520> ask<02:47:23.760> it<02:47:24.000> to<02:47:24.160> read 02:47:24.469 --> 02:47:24.479 align:start position:0% here it says you can ask it to read 02:47:24.479 --> 02:47:27.750 align:start position:0% here it says you can ask it to read multiple<02:47:25.040> actions.<02:47:26.399> In<02:47:26.720> this<02:47:27.040> we<02:47:27.279> also<02:47:27.600> get 02:47:27.750 --> 02:47:27.760 align:start position:0% multiple actions. In this we also get 02:47:27.760 --> 02:47:29.750 align:start position:0% multiple actions. In this we also get more<02:47:28.080> recommendations. 02:47:29.750 --> 02:47:29.760 align:start position:0% more recommendations. 02:47:29.760 --> 02:47:31.750 align:start position:0% more recommendations. I<02:47:30.080> will<02:47:30.160> suggest<02:47:30.560> to<02:47:30.720> you<02:47:30.880> that<02:47:31.120> we<02:47:31.279> should<02:47:31.520> use 02:47:31.750 --> 02:47:31.760 align:start position:0% I will suggest to you that we should use 02:47:31.760 --> 02:47:34.550 align:start position:0% I will suggest to you that we should use multiple<02:47:32.240> plugins<02:47:33.279> like<02:47:33.600> right<02:47:33.920> now<02:47:34.240> you<02:47:34.399> are 02:47:34.550 --> 02:47:34.560 align:start position:0% multiple plugins like right now you are 02:47:34.560 --> 02:47:37.269 align:start position:0% multiple plugins like right now you are seeing<02:47:34.800> that<02:47:34.960> we<02:47:35.200> can<02:47:35.359> use<02:47:35.520> our<02:47:35.760> windows.<02:47:37.040> We 02:47:37.269 --> 02:47:37.279 align:start position:0% seeing that we can use our windows. We 02:47:37.279 --> 02:47:39.510 align:start position:0% seeing that we can use our windows. We have<02:47:37.359> our<02:47:37.680> chrome<02:47:38.000> and<02:47:38.319> data<02:47:38.640> analytics<02:47:39.200> and 02:47:39.510 --> 02:47:39.520 align:start position:0% have our chrome and data analytics and 02:47:39.520 --> 02:47:42.870 align:start position:0% have our chrome and data analytics and product<02:47:39.840> design.<02:47:41.200> We<02:47:41.439> also<02:47:41.760> have<02:47:42.080> Apollo<02:47:42.640> and 02:47:42.870 --> 02:47:42.880 align:start position:0% product design. We also have Apollo and 02:47:42.880 --> 02:47:46.389 align:start position:0% product design. We also have Apollo and Atio<02:47:43.680> and<02:47:44.000> Carter<02:47:44.479> CRM<02:47:45.359> and<02:47:45.680> Clay<02:47:46.080> and 02:47:46.389 --> 02:47:46.399 align:start position:0% Atio and Carter CRM and Clay and 02:47:46.399 --> 02:47:49.429 align:start position:0% Atio and Carter CRM and Clay and Circleback.<02:47:47.840> We<02:47:48.080> have<02:47:48.319> granola<02:47:48.800> and<02:47:49.120> otter 02:47:49.429 --> 02:47:49.439 align:start position:0% Circleback. We have granola and otter 02:47:49.439 --> 02:47:53.670 align:start position:0% Circleback. We have granola and otter and<02:47:49.680> canva.<02:47:51.120> We<02:47:51.359> can<02:47:51.520> use<02:47:51.840> all<02:47:52.080> these<02:47:52.319> plugins. 02:47:53.670 --> 02:47:53.680 align:start position:0% and canva. We can use all these plugins. 02:47:53.680 --> 02:47:56.790 align:start position:0% and canva. We can use all these plugins. We<02:47:53.920> have<02:47:54.160> many<02:47:54.479> options.<02:47:55.600> If<02:47:55.920> we<02:47:56.080> bring<02:47:56.399> any<02:47:56.640> of 02:47:56.790 --> 02:47:56.800 align:start position:0% We have many options. If we bring any of 02:47:56.800 --> 02:47:59.590 align:start position:0% We have many options. If we bring any of these<02:47:57.040> in<02:47:57.279> here,<02:47:57.680> we<02:47:57.920> can<02:47:58.000> use<02:47:58.240> it<02:47:58.479> out.<02:47:59.359> For 02:47:59.590 --> 02:47:59.600 align:start position:0% these in here, we can use it out. For 02:47:59.600 --> 02:48:01.510 align:start position:0% these in here, we can use it out. For every<02:47:59.840> niche,<02:48:00.319> we<02:48:00.479> have<02:48:00.720> separate<02:48:01.120> options 02:48:01.510 --> 02:48:01.520 align:start position:0% every niche, we have separate options 02:48:01.520 --> 02:48:04.230 align:start position:0% every niche, we have separate options available<02:48:02.000> for<02:48:02.240> us.<02:48:03.040> Like<02:48:03.279> for<02:48:03.520> our<02:48:03.760> education 02:48:04.230 --> 02:48:04.240 align:start position:0% available for us. Like for our education 02:48:04.240 --> 02:48:06.630 align:start position:0% available for us. Like for our education and<02:48:04.479> research,<02:48:05.520> we<02:48:05.760> also<02:48:06.080> have<02:48:06.240> options 02:48:06.630 --> 02:48:06.640 align:start position:0% and research, we also have options 02:48:06.640 --> 02:48:09.429 align:start position:0% and research, we also have options available<02:48:07.120> right<02:48:07.439> here.<02:48:08.560> We<02:48:08.800> have<02:48:08.880> our<02:48:09.120> Dow 02:48:09.429 --> 02:48:09.439 align:start position:0% available right here. We have our Dow 02:48:09.439 --> 02:48:12.230 align:start position:0% available right here. We have our Dow Jones<02:48:09.760> Factiva.<02:48:10.399> Here<02:48:11.279> we<02:48:11.520> have<02:48:11.600> our<02:48:11.840> gov 02:48:12.230 --> 02:48:12.240 align:start position:0% Jones Factiva. Here we have our gov 02:48:12.240 --> 02:48:15.590 align:start position:0% Jones Factiva. Here we have our gov tribe<02:48:12.880> and<02:48:13.120> we<02:48:13.279> have<02:48:13.520> life<02:48:13.840> science<02:48:14.240> research. 02:48:15.590 --> 02:48:15.600 align:start position:0% tribe and we have life science research. 02:48:15.600 --> 02:48:17.750 align:start position:0% tribe and we have life science research. For<02:48:15.840> finance,<02:48:16.399> we<02:48:16.640> have<02:48:16.800> multiple<02:48:17.279> softwares 02:48:17.750 --> 02:48:17.760 align:start position:0% For finance, we have multiple softwares 02:48:17.760 --> 02:48:20.870 align:start position:0% For finance, we have multiple softwares available<02:48:18.240> right<02:48:18.560> here.<02:48:19.760> So<02:48:20.000> what<02:48:20.240> codeex 02:48:20.870 --> 02:48:20.880 align:start position:0% available right here. So what codeex 02:48:20.880 --> 02:48:22.950 align:start position:0% available right here. So what codeex does<02:48:21.120> is<02:48:21.359> on<02:48:21.520> a<02:48:21.680> large<02:48:22.000> scale,<02:48:22.319> it<02:48:22.560> gives<02:48:22.720> us 02:48:22.950 --> 02:48:22.960 align:start position:0% does is on a large scale, it gives us 02:48:22.960 --> 02:48:26.550 align:start position:0% does is on a large scale, it gives us multiple<02:48:23.439> plugins<02:48:23.920> to<02:48:24.160> use<02:48:25.359> from<02:48:25.600> these.<02:48:26.319> The 02:48:26.550 --> 02:48:26.560 align:start position:0% multiple plugins to use from these. The 02:48:26.560 --> 02:48:28.710 align:start position:0% multiple plugins to use from these. The used<02:48:26.960> plug-in<02:48:27.359> on<02:48:27.520> our<02:48:27.680> developer<02:48:28.160> side<02:48:28.479> is 02:48:28.710 --> 02:48:28.720 align:start position:0% used plug-in on our developer side is 02:48:28.720 --> 02:48:31.590 align:start position:0% used plug-in on our developer side is our<02:48:28.880> GitHub<02:48:29.439> plug-in.<02:48:30.720> But<02:48:30.880> if<02:48:31.120> we<02:48:31.279> want<02:48:31.439> to 02:48:31.590 --> 02:48:31.600 align:start position:0% our GitHub plug-in. But if we want to 02:48:31.600 --> 02:48:33.670 align:start position:0% our GitHub plug-in. But if we want to use<02:48:31.920> multiple<02:48:32.399> plugins<02:48:32.880> on<02:48:33.120> our<02:48:33.359> whole 02:48:33.670 --> 02:48:33.680 align:start position:0% use multiple plugins on our whole 02:48:33.680 --> 02:48:36.630 align:start position:0% use multiple plugins on our whole enterprise<02:48:34.160> level,<02:48:34.880> we<02:48:35.120> can<02:48:35.279> do<02:48:35.359> that<02:48:35.680> too. 02:48:36.630 --> 02:48:36.640 align:start position:0% enterprise level, we can do that too. 02:48:36.640 --> 02:48:39.349 align:start position:0% enterprise level, we can do that too. With<02:48:36.880> that,<02:48:37.120> our<02:48:37.439> price<02:48:37.680> will<02:48:38.000> increase.<02:48:39.120> Our 02:48:39.349 --> 02:48:39.359 align:start position:0% With that, our price will increase. Our 02:48:39.359 --> 02:48:41.510 align:start position:0% With that, our price will increase. Our usage<02:48:39.760> cost<02:48:40.080> will<02:48:40.319> also<02:48:40.640> become<02:48:40.880> a<02:48:41.040> cost<02:48:41.279> that 02:48:41.510 --> 02:48:41.520 align:start position:0% usage cost will also become a cost that 02:48:41.520 --> 02:48:46.150 align:start position:0% usage cost will also become a cost that is<02:48:41.680> quite<02:48:42.000> high. 02:48:46.150 --> 02:48:46.160 align:start position:0% 02:48:46.160 --> 02:48:48.950 align:start position:0% The<02:48:46.399> open<02:48:46.800> AI<02:48:47.200> ecosystem<02:48:48.000> is<02:48:48.240> a<02:48:48.479> collection<02:48:48.800> of 02:48:48.950 --> 02:48:48.960 align:start position:0% The open AI ecosystem is a collection of 02:48:48.960 --> 02:48:51.910 align:start position:0% The open AI ecosystem is a collection of tools,<02:48:49.680> models,<02:48:50.160> and<02:48:50.399> platforms<02:48:51.359> that<02:48:51.600> help 02:48:51.910 --> 02:48:51.920 align:start position:0% tools, models, and platforms that help 02:48:51.920 --> 02:48:54.070 align:start position:0% tools, models, and platforms that help individuals<02:48:52.560> and<02:48:52.880> organizations<02:48:53.760> use 02:48:54.070 --> 02:48:54.080 align:start position:0% individuals and organizations use 02:48:54.080 --> 02:48:56.150 align:start position:0% individuals and organizations use artificial<02:48:54.720> intelligence<02:48:55.279> in<02:48:55.600> practical 02:48:56.150 --> 02:48:56.160 align:start position:0% artificial intelligence in practical 02:48:56.160 --> 02:48:58.309 align:start position:0% artificial intelligence in practical workflows. 02:48:58.309 --> 02:48:58.319 align:start position:0% workflows. 02:48:58.319 --> 02:49:01.590 align:start position:0% workflows. In<02:48:58.560> this<02:48:58.800> diagram,<02:48:59.760> open<02:49:00.160> AI<02:49:00.640> ecosystem<02:49:01.359> is 02:49:01.590 --> 02:49:01.600 align:start position:0% In this diagram, open AI ecosystem is 02:49:01.600 --> 02:49:04.309 align:start position:0% In this diagram, open AI ecosystem is the<02:49:01.840> central<02:49:02.160> idea<02:49:03.120> and<02:49:03.359> the<02:49:03.600> main<02:49:03.840> branches 02:49:04.309 --> 02:49:04.319 align:start position:0% the central idea and the main branches 02:49:04.319 --> 02:49:06.230 align:start position:0% the central idea and the main branches show<02:49:04.560> the<02:49:04.800> important<02:49:05.279> parts<02:49:05.600> connected<02:49:06.000> to 02:49:06.230 --> 02:49:06.240 align:start position:0% show the important parts connected to 02:49:06.240 --> 02:49:07.750 align:start position:0% show the important parts connected to it. 02:49:07.750 --> 02:49:07.760 align:start position:0% it. 02:49:07.760 --> 02:49:10.070 align:start position:0% it. Chat<02:49:08.160> GPT<02:49:08.720> is<02:49:08.960> one<02:49:09.120> of<02:49:09.200> the<02:49:09.439> most<02:49:09.600> familiar 02:49:10.070 --> 02:49:10.080 align:start position:0% Chat GPT is one of the most familiar 02:49:10.080 --> 02:49:12.230 align:start position:0% Chat GPT is one of the most familiar parts<02:49:10.319> of<02:49:10.479> the<02:49:10.640> ecosystem. 02:49:12.230 --> 02:49:12.240 align:start position:0% parts of the ecosystem. 02:49:12.240 --> 02:49:14.870 align:start position:0% parts of the ecosystem. It<02:49:12.479> helps<02:49:12.800> users<02:49:13.200> write<02:49:13.520> content,<02:49:14.399> explain 02:49:14.870 --> 02:49:14.880 align:start position:0% It helps users write content, explain 02:49:14.880 --> 02:49:17.830 align:start position:0% It helps users write content, explain concepts,<02:49:15.840> solve<02:49:16.240> problems,<02:49:17.200> summarize 02:49:17.830 --> 02:49:17.840 align:start position:0% concepts, solve problems, summarize 02:49:17.840 --> 02:49:21.269 align:start position:0% concepts, solve problems, summarize information,<02:49:18.560> and<02:49:18.880> support<02:49:19.279> daily<02:49:19.680> work. 02:49:21.269 --> 02:49:21.279 align:start position:0% information, and support daily work. 02:49:21.279 --> 02:49:24.070 align:start position:0% information, and support daily work. In<02:49:21.600> software<02:49:22.000> development,<02:49:22.960> Chat<02:49:23.279> GPT<02:49:23.840> can 02:49:24.070 --> 02:49:24.080 align:start position:0% In software development, Chat GPT can 02:49:24.080 --> 02:49:26.550 align:start position:0% In software development, Chat GPT can help<02:49:24.319> developers<02:49:24.880> understand<02:49:25.600> errors,<02:49:26.240> write 02:49:26.550 --> 02:49:26.560 align:start position:0% help developers understand errors, write 02:49:26.560 --> 02:49:29.349 align:start position:0% help developers understand errors, write documentation,<02:49:27.920> plan<02:49:28.240> features,<02:49:29.040> and 02:49:29.349 --> 02:49:29.359 align:start position:0% documentation, plan features, and 02:49:29.359 --> 02:49:31.190 align:start position:0% documentation, plan features, and improve<02:49:29.760> prompts<02:49:30.240> before<02:49:30.560> using<02:49:30.800> them<02:49:31.040> with 02:49:31.190 --> 02:49:31.200 align:start position:0% improve prompts before using them with 02:49:31.200 --> 02:49:33.269 align:start position:0% improve prompts before using them with coding<02:49:31.600> tools. 02:49:33.269 --> 02:49:33.279 align:start position:0% coding tools. 02:49:33.279 --> 02:49:37.030 align:start position:0% coding tools. The<02:49:33.600> Open<02:49:34.000> AI<02:49:34.640> API<02:49:35.840> allows<02:49:36.319> developers<02:49:36.800> to 02:49:37.030 --> 02:49:37.040 align:start position:0% The Open AI API allows developers to 02:49:37.040 --> 02:49:39.510 align:start position:0% The Open AI API allows developers to connect<02:49:37.439> OpenAI<02:49:38.160> models<02:49:38.640> directly<02:49:39.200> into 02:49:39.510 --> 02:49:39.520 align:start position:0% connect OpenAI models directly into 02:49:39.520 --> 02:49:41.750 align:start position:0% connect OpenAI models directly into their<02:49:39.760> own<02:49:40.000> applications. 02:49:41.750 --> 02:49:41.760 align:start position:0% their own applications. 02:49:41.760 --> 02:49:44.309 align:start position:0% their own applications. For<02:49:41.920> example,<02:49:43.200> a<02:49:43.439> company<02:49:43.760> can<02:49:44.000> build<02:49:44.160> a 02:49:44.309 --> 02:49:44.319 align:start position:0% For example, a company can build a 02:49:44.319 --> 02:49:47.190 align:start position:0% For example, a company can build a chatbot,<02:49:45.279> document<02:49:45.840> assistant,<02:49:46.720> coding 02:49:47.190 --> 02:49:47.200 align:start position:0% chatbot, document assistant, coding 02:49:47.200 --> 02:49:50.309 align:start position:0% chatbot, document assistant, coding assistant,<02:49:48.240> customer<02:49:48.720> support<02:49:49.120> tool,<02:49:49.920> or 02:49:50.309 --> 02:49:50.319 align:start position:0% assistant, customer support tool, or 02:49:50.319 --> 02:49:53.990 align:start position:0% assistant, customer support tool, or automation<02:49:50.960> system<02:49:51.520> using<02:49:51.840> the<02:49:52.080> API. 02:49:53.990 --> 02:49:54.000 align:start position:0% automation system using the API. 02:49:54.000 --> 02:49:56.389 align:start position:0% automation system using the API. This<02:49:54.240> makes<02:49:54.560> AI<02:49:55.120> usable<02:49:55.600> inside<02:49:56.080> real 02:49:56.389 --> 02:49:56.399 align:start position:0% This makes AI usable inside real 02:49:56.399 --> 02:49:57.910 align:start position:0% This makes AI usable inside real business<02:49:56.800> products<02:49:57.120> and<02:49:57.439> enterprise 02:49:57.910 --> 02:49:57.920 align:start position:0% business products and enterprise 02:49:57.920 --> 02:49:59.830 align:start position:0% business products and enterprise systems. 02:49:59.830 --> 02:49:59.840 align:start position:0% systems. 02:49:59.840 --> 02:50:01.670 align:start position:0% systems. Codeex<02:50:00.479> is<02:50:00.640> focused<02:50:00.960> on<02:50:01.200> software 02:50:01.670 --> 02:50:01.680 align:start position:0% Codeex is focused on software 02:50:01.680 --> 02:50:04.070 align:start position:0% Codeex is focused on software development.<02:50:03.040> It<02:50:03.279> helps<02:50:03.520> developers 02:50:04.070 --> 02:50:04.080 align:start position:0% development. It helps developers 02:50:04.080 --> 02:50:07.429 align:start position:0% development. It helps developers generate<02:50:04.560> code,<02:50:05.359> refactor<02:50:06.000> files,<02:50:06.960> explain 02:50:07.429 --> 02:50:07.439 align:start position:0% generate code, refactor files, explain 02:50:07.439 --> 02:50:10.469 align:start position:0% generate code, refactor files, explain existing<02:50:07.920> code,<02:50:08.800> create<02:50:09.200> tests,<02:50:10.000> debug 02:50:10.469 --> 02:50:10.479 align:start position:0% existing code, create tests, debug 02:50:10.479 --> 02:50:13.830 align:start position:0% existing code, create tests, debug issues,<02:50:11.359> and<02:50:11.600> work<02:50:11.840> with<02:50:12.080> repositories. 02:50:13.830 --> 02:50:13.840 align:start position:0% issues, and work with repositories. 02:50:13.840 --> 02:50:16.389 align:start position:0% issues, and work with repositories. In<02:50:14.080> an<02:50:14.319> enterprise<02:50:14.800> course,<02:50:15.600> codeex<02:50:16.160> is 02:50:16.389 --> 02:50:16.399 align:start position:0% In an enterprise course, codeex is 02:50:16.399 --> 02:50:18.469 align:start position:0% In an enterprise course, codeex is important<02:50:16.720> because<02:50:16.960> it<02:50:17.200> shows<02:50:17.439> how<02:50:17.760> AI<02:50:18.240> can 02:50:18.469 --> 02:50:18.479 align:start position:0% important because it shows how AI can 02:50:18.479 --> 02:50:20.710 align:start position:0% important because it shows how AI can support<02:50:18.880> real<02:50:19.200> development<02:50:19.760> workflows 02:50:20.710 --> 02:50:20.720 align:start position:0% support real development workflows 02:50:20.720 --> 02:50:23.990 align:start position:0% support real development workflows instead<02:50:21.120> of<02:50:21.279> only<02:50:21.680> answering<02:50:22.160> questions. 02:50:23.990 --> 02:50:24.000 align:start position:0% instead of only answering questions. 02:50:24.000 --> 02:50:26.230 align:start position:0% instead of only answering questions. The<02:50:24.240> models<02:50:24.640> branch<02:50:25.120> represents<02:50:25.600> the<02:50:25.840> AI 02:50:26.230 --> 02:50:26.240 align:start position:0% The models branch represents the AI 02:50:26.240 --> 02:50:28.790 align:start position:0% The models branch represents the AI models<02:50:26.640> behind<02:50:26.880> the<02:50:27.120> ecosystem. 02:50:28.790 --> 02:50:28.800 align:start position:0% models behind the ecosystem. 02:50:28.800 --> 02:50:31.670 align:start position:0% models behind the ecosystem. These<02:50:29.120> models<02:50:29.520> can<02:50:29.680> work<02:50:29.840> with<02:50:30.080> text,<02:50:30.880> code, 02:50:31.670 --> 02:50:31.680 align:start position:0% These models can work with text, code, 02:50:31.680 --> 02:50:33.910 align:start position:0% These models can work with text, code, images,<02:50:32.560> and<02:50:32.800> other<02:50:33.040> types<02:50:33.279> of<02:50:33.439> input 02:50:33.910 --> 02:50:33.920 align:start position:0% images, and other types of input 02:50:33.920 --> 02:50:35.190 align:start position:0% images, and other types of input depending<02:50:34.240> on<02:50:34.399> the<02:50:34.640> product<02:50:34.880> or 02:50:35.190 --> 02:50:35.200 align:start position:0% depending on the product or 02:50:35.200 --> 02:50:37.190 align:start position:0% depending on the product or configuration. 02:50:37.190 --> 02:50:37.200 align:start position:0% configuration. 02:50:37.200 --> 02:50:39.030 align:start position:0% configuration. Better<02:50:37.600> models<02:50:38.080> usually<02:50:38.399> mean<02:50:38.720> better 02:50:39.030 --> 02:50:39.040 align:start position:0% Better models usually mean better 02:50:39.040 --> 02:50:41.510 align:start position:0% Better models usually mean better reasoning,<02:50:39.840> better<02:50:40.160> code<02:50:40.479> understanding, 02:50:41.510 --> 02:50:41.520 align:start position:0% reasoning, better code understanding, 02:50:41.520 --> 02:50:44.469 align:start position:0% reasoning, better code understanding, and<02:50:41.760> more<02:50:42.080> accurate<02:50:42.479> responses. 02:50:44.469 --> 02:50:44.479 align:start position:0% and more accurate responses. 02:50:44.479 --> 02:50:46.870 align:start position:0% and more accurate responses. Finally,<02:50:45.520> enterprise<02:50:46.000> tools<02:50:46.399> are<02:50:46.560> important 02:50:46.870 --> 02:50:46.880 align:start position:0% Finally, enterprise tools are important 02:50:46.880 --> 02:50:49.110 align:start position:0% Finally, enterprise tools are important for<02:50:47.120> organizations. 02:50:49.110 --> 02:50:49.120 align:start position:0% for organizations. 02:50:49.120 --> 02:50:51.990 align:start position:0% for organizations. Enterprises<02:50:49.760> need<02:50:50.080> security,<02:50:51.040> governance, 02:50:51.990 --> 02:50:52.000 align:start position:0% Enterprises need security, governance, 02:50:52.000 --> 02:50:54.950 align:start position:0% Enterprises need security, governance, permissions,<02:50:53.040> auditing,<02:50:54.000> and<02:50:54.319> control<02:50:54.640> over 02:50:54.950 --> 02:50:54.960 align:start position:0% permissions, auditing, and control over 02:50:54.960 --> 02:50:57.269 align:start position:0% permissions, auditing, and control over how<02:50:55.200> AI<02:50:55.600> is<02:50:55.840> used. 02:50:57.269 --> 02:50:57.279 align:start position:0% how AI is used. 02:50:57.279 --> 02:50:59.510 align:start position:0% how AI is used. These<02:50:57.600> tools<02:50:58.000> help<02:50:58.240> companies<02:50:58.720> adopt<02:50:59.120> AI 02:50:59.510 --> 02:50:59.520 align:start position:0% These tools help companies adopt AI 02:50:59.520 --> 02:51:02.550 align:start position:0% These tools help companies adopt AI safely<02:51:00.319> while<02:51:00.720> protecting<02:51:01.200> data,<02:51:02.000> managing 02:51:02.550 --> 02:51:02.560 align:start position:0% safely while protecting data, managing 02:51:02.560 --> 02:51:06.550 align:start position:0% safely while protecting data, managing access,<02:51:03.359> and<02:51:03.680> following<02:51:04.080> internal<02:51:04.640> policies. 02:51:06.550 --> 02:51:06.560 align:start position:0% access, and following internal policies. 02:51:06.560 --> 02:51:09.269 align:start position:0% access, and following internal policies. Overall,<02:51:07.439> the<02:51:07.760> diagram<02:51:08.240> shows<02:51:08.479> that<02:51:08.720> the<02:51:08.880> open 02:51:09.269 --> 02:51:09.279 align:start position:0% Overall, the diagram shows that the open 02:51:09.279 --> 02:51:13.269 align:start position:0% Overall, the diagram shows that the open AI<02:51:09.680> ecosystem<02:51:10.720> is<02:51:10.960> not<02:51:11.200> just<02:51:11.439> one<02:51:11.760> product.<02:51:13.040> It 02:51:13.269 --> 02:51:13.279 align:start position:0% AI ecosystem is not just one product. It 02:51:13.279 --> 02:51:15.990 align:start position:0% AI ecosystem is not just one product. It includes<02:51:13.840> user-facing<02:51:14.560> tools,<02:51:15.439> developer 02:51:15.990 --> 02:51:16.000 align:start position:0% includes user-facing tools, developer 02:51:16.000 --> 02:51:19.190 align:start position:0% includes user-facing tools, developer APIs,<02:51:17.120> coding<02:51:17.520> assistance,<02:51:18.640> advanced 02:51:19.190 --> 02:51:19.200 align:start position:0% APIs, coding assistance, advanced 02:51:19.200 --> 02:51:22.550 align:start position:0% APIs, coding assistance, advanced models,<02:51:19.920> and<02:51:20.240> enterprise<02:51:20.880> controls. 02:51:22.550 --> 02:51:22.560 align:start position:0% models, and enterprise controls. 02:51:22.560 --> 02:51:25.670 align:start position:0% models, and enterprise controls. Together,<02:51:23.439> these<02:51:23.760> parts<02:51:24.160> help<02:51:24.479> teams<02:51:24.880> build, 02:51:25.670 --> 02:51:25.680 align:start position:0% Together, these parts help teams build, 02:51:25.680 --> 02:51:28.309 align:start position:0% Together, these parts help teams build, automate,<02:51:26.560> learn,<02:51:27.200> and<02:51:27.520> develop<02:51:27.840> software 02:51:28.309 --> 02:51:28.319 align:start position:0% automate, learn, and develop software 02:51:28.319 --> 02:51:33.429 align:start position:0% automate, learn, and develop software more<02:51:28.560> efficiently. 02:51:33.429 --> 02:51:33.439 align:start position:0% 02:51:33.439 --> 02:51:35.830 align:start position:0% This<02:51:33.680> conclusion<02:51:34.240> mind<02:51:34.560> map<02:51:34.960> summarizes<02:51:35.680> the 02:51:35.830 --> 02:51:35.840 align:start position:0% This conclusion mind map summarizes the 02:51:35.840 --> 02:51:37.670 align:start position:0% This conclusion mind map summarizes the key<02:51:36.080> lessons<02:51:36.479> learned<02:51:37.120> throughout<02:51:37.439> the 02:51:37.670 --> 02:51:37.680 align:start position:0% key lessons learned throughout the 02:51:37.680 --> 02:51:39.990 align:start position:0% key lessons learned throughout the OpenAI<02:51:38.319> codeex<02:51:38.960> enterprise<02:51:39.520> development 02:51:39.990 --> 02:51:40.000 align:start position:0% OpenAI codeex enterprise development 02:51:40.000 --> 02:51:41.750 align:start position:0% OpenAI codeex enterprise development course. 02:51:41.750 --> 02:51:41.760 align:start position:0% course. 02:51:41.760 --> 02:51:44.309 align:start position:0% course. The<02:51:42.080> central<02:51:42.399> idea<02:51:42.960> is<02:51:43.200> that<02:51:43.439> AI<02:51:43.840> assisted 02:51:44.309 --> 02:51:44.319 align:start position:0% The central idea is that AI assisted 02:51:44.319 --> 02:51:46.309 align:start position:0% The central idea is that AI assisted development<02:51:44.880> is<02:51:45.200> becoming<02:51:45.520> an<02:51:45.840> important 02:51:46.309 --> 02:51:46.319 align:start position:0% development is becoming an important 02:51:46.319 --> 02:51:49.190 align:start position:0% development is becoming an important part<02:51:46.640> of<02:51:46.880> modern<02:51:47.279> software<02:51:47.680> engineering<02:51:48.880> and 02:51:49.190 --> 02:51:49.200 align:start position:0% part of modern software engineering and 02:51:49.200 --> 02:51:51.030 align:start position:0% part of modern software engineering and organizations<02:51:49.920> that<02:51:50.160> learn<02:51:50.399> to<02:51:50.640> use<02:51:50.800> these 02:51:51.030 --> 02:51:51.040 align:start position:0% organizations that learn to use these 02:51:51.040 --> 02:51:53.590 align:start position:0% organizations that learn to use these tools<02:51:51.439> effectively<02:51:52.640> can<02:51:52.880> significantly 02:51:53.590 --> 02:51:53.600 align:start position:0% tools effectively can significantly 02:51:53.600 --> 02:51:56.630 align:start position:0% tools effectively can significantly improve<02:51:54.080> productivity,<02:51:55.359> software<02:51:55.840> quality 02:51:56.630 --> 02:51:56.640 align:start position:0% improve productivity, software quality 02:51:56.640 --> 02:51:59.349 align:start position:0% improve productivity, software quality and<02:51:56.880> development<02:51:57.439> speed. 02:51:59.349 --> 02:51:59.359 align:start position:0% and development speed. 02:51:59.359 --> 02:52:01.590 align:start position:0% and development speed. The<02:51:59.600> first<02:51:59.920> branch<02:52:00.319> focuses<02:52:00.720> on<02:52:00.960> OpenAI 02:52:01.590 --> 02:52:01.600 align:start position:0% The first branch focuses on OpenAI 02:52:01.600 --> 02:52:04.630 align:start position:0% The first branch focuses on OpenAI codeex<02:52:02.160> itself.<02:52:03.520> Throughout<02:52:03.920> the<02:52:04.160> course, 02:52:04.630 --> 02:52:04.640 align:start position:0% codeex itself. Throughout the course, 02:52:04.640 --> 02:52:06.790 align:start position:0% codeex itself. Throughout the course, learners<02:52:05.200> discovered<02:52:05.600> how<02:52:05.840> Codeex<02:52:06.479> helps 02:52:06.790 --> 02:52:06.800 align:start position:0% learners discovered how Codeex helps 02:52:06.800 --> 02:52:09.269 align:start position:0% learners discovered how Codeex helps developers<02:52:07.359> generate<02:52:07.840> code,<02:52:08.720> analyze 02:52:09.269 --> 02:52:09.279 align:start position:0% developers generate code, analyze 02:52:09.279 --> 02:52:12.550 align:start position:0% developers generate code, analyze repositories,<02:52:10.560> refactor<02:52:11.120> applications, 02:52:12.550 --> 02:52:12.560 align:start position:0% repositories, refactor applications, 02:52:12.560 --> 02:52:15.190 align:start position:0% repositories, refactor applications, create<02:52:12.960> tests,<02:52:13.840> and<02:52:14.080> automate<02:52:14.560> repetitive 02:52:15.190 --> 02:52:15.200 align:start position:0% create tests, and automate repetitive 02:52:15.200 --> 02:52:17.269 align:start position:0% create tests, and automate repetitive development<02:52:15.680> tasks. 02:52:17.269 --> 02:52:17.279 align:start position:0% development tasks. 02:52:17.279 --> 02:52:20.230 align:start position:0% development tasks. Rather<02:52:17.680> than<02:52:17.920> replacing<02:52:18.479> developers,<02:52:19.600> Codeex 02:52:20.230 --> 02:52:20.240 align:start position:0% Rather than replacing developers, Codeex 02:52:20.240 --> 02:52:21.910 align:start position:0% Rather than replacing developers, Codeex acts<02:52:20.479> as<02:52:20.640> an<02:52:20.800> intelligent<02:52:21.359> development 02:52:21.910 --> 02:52:21.920 align:start position:0% acts as an intelligent development 02:52:21.920 --> 02:52:24.230 align:start position:0% acts as an intelligent development assistant<02:52:22.720> that<02:52:23.040> helps<02:52:23.359> teams<02:52:23.760> work<02:52:24.000> more 02:52:24.230 --> 02:52:24.240 align:start position:0% assistant that helps teams work more 02:52:24.240 --> 02:52:26.070 align:start position:0% assistant that helps teams work more efficiently. 02:52:26.070 --> 02:52:26.080 align:start position:0% efficiently. 02:52:26.080 --> 02:52:27.830 align:start position:0% efficiently. The<02:52:26.399> next<02:52:26.640> branch<02:52:27.200> highlights<02:52:27.600> the 02:52:27.830 --> 02:52:27.840 align:start position:0% The next branch highlights the 02:52:27.840 --> 02:52:30.070 align:start position:0% The next branch highlights the development<02:52:28.399> workflow. 02:52:30.070 --> 02:52:30.080 align:start position:0% development workflow. 02:52:30.080 --> 02:52:31.910 align:start position:0% development workflow. One<02:52:30.319> of<02:52:30.399> the<02:52:30.560> most<02:52:30.880> important<02:52:31.359> lessons<02:52:31.760> from 02:52:31.910 --> 02:52:31.920 align:start position:0% One of the most important lessons from 02:52:31.920 --> 02:52:34.790 align:start position:0% One of the most important lessons from the<02:52:32.160> course<02:52:32.720> is<02:52:33.040> that<02:52:33.200> AI<02:52:33.600> can<02:52:33.840> support<02:52:34.399> every 02:52:34.790 --> 02:52:34.800 align:start position:0% the course is that AI can support every 02:52:34.800 --> 02:52:37.349 align:start position:0% the course is that AI can support every stage<02:52:35.120> of<02:52:35.279> software<02:52:35.760> development. 02:52:37.349 --> 02:52:37.359 align:start position:0% stage of software development. 02:52:37.359 --> 02:52:39.269 align:start position:0% stage of software development. Developers<02:52:37.920> can<02:52:38.160> use<02:52:38.399> codeex<02:52:38.960> during 02:52:39.269 --> 02:52:39.279 align:start position:0% Developers can use codeex during 02:52:39.279 --> 02:52:42.550 align:start position:0% Developers can use codeex during planning,<02:52:40.080> implementation,<02:52:41.520> testing, 02:52:42.550 --> 02:52:42.560 align:start position:0% planning, implementation, testing, 02:52:42.560 --> 02:52:46.230 align:start position:0% planning, implementation, testing, debugging,<02:52:43.600> and<02:52:44.000> deployment<02:52:44.479> preparation. 02:52:46.230 --> 02:52:46.240 align:start position:0% debugging, and deployment preparation. 02:52:46.240 --> 02:52:48.550 align:start position:0% debugging, and deployment preparation. Instead<02:52:46.640> of<02:52:46.800> viewing<02:52:47.120> AI<02:52:47.600> as<02:52:47.760> a<02:52:47.920> tool<02:52:48.240> used 02:52:48.550 --> 02:52:48.560 align:start position:0% Instead of viewing AI as a tool used 02:52:48.560 --> 02:52:51.190 align:start position:0% Instead of viewing AI as a tool used only<02:52:48.800> for<02:52:49.040> coding,<02:52:50.080> organizations<02:52:50.960> can 02:52:51.190 --> 02:52:51.200 align:start position:0% only for coding, organizations can 02:52:51.200 --> 02:52:53.269 align:start position:0% only for coding, organizations can integrate<02:52:51.680> it<02:52:51.840> into<02:52:52.160> the<02:52:52.399> complete<02:52:52.800> software 02:52:53.269 --> 02:52:53.279 align:start position:0% integrate it into the complete software 02:52:53.279 --> 02:52:55.830 align:start position:0% integrate it into the complete software development<02:52:53.840> life<02:52:54.080> cycle. 02:52:55.830 --> 02:52:55.840 align:start position:0% development life cycle. 02:52:55.840 --> 02:52:58.150 align:start position:0% development life cycle. The<02:52:56.160> enterprise<02:52:56.720> adoption<02:52:57.200> section 02:52:58.150 --> 02:52:58.160 align:start position:0% The enterprise adoption section 02:52:58.160 --> 02:53:00.230 align:start position:0% The enterprise adoption section emphasizes<02:52:58.880> that<02:52:59.200> successful<02:52:59.760> AI 02:53:00.230 --> 02:53:00.240 align:start position:0% emphasizes that successful AI 02:53:00.240 --> 02:53:02.469 align:start position:0% emphasizes that successful AI implementation<02:53:01.520> requires<02:53:02.080> more<02:53:02.319> than 02:53:02.469 --> 02:53:02.479 align:start position:0% implementation requires more than 02:53:02.479 --> 02:53:04.870 align:start position:0% implementation requires more than technical<02:53:02.960> capability. 02:53:04.870 --> 02:53:04.880 align:start position:0% technical capability. 02:53:04.880 --> 02:53:07.110 align:start position:0% technical capability. Organizations<02:53:05.760> must<02:53:06.080> establish<02:53:06.640> governance 02:53:07.110 --> 02:53:07.120 align:start position:0% Organizations must establish governance 02:53:07.120 --> 02:53:09.750 align:start position:0% Organizations must establish governance frameworks,<02:53:08.160> security<02:53:08.720> controls, 02:53:09.750 --> 02:53:09.760 align:start position:0% frameworks, security controls, 02:53:09.760 --> 02:53:12.309 align:start position:0% frameworks, security controls, compliance<02:53:10.319> processes,<02:53:11.279> and<02:53:11.600> collaboration 02:53:12.309 --> 02:53:12.319 align:start position:0% compliance processes, and collaboration 02:53:12.319 --> 02:53:13.830 align:start position:0% compliance processes, and collaboration standards. 02:53:13.830 --> 02:53:13.840 align:start position:0% standards. 02:53:13.840 --> 02:53:16.070 align:start position:0% standards. Enterprise<02:53:14.399> teams<02:53:14.800> need<02:53:15.040> visibility<02:53:15.760> into 02:53:16.070 --> 02:53:16.080 align:start position:0% Enterprise teams need visibility into 02:53:16.080 --> 02:53:18.870 align:start position:0% Enterprise teams need visibility into how<02:53:16.399> AI<02:53:16.800> is<02:53:17.040> used<02:53:17.760> and<02:53:18.000> must<02:53:18.240> ensure<02:53:18.560> that 02:53:18.870 --> 02:53:18.880 align:start position:0% how AI is used and must ensure that 02:53:18.880 --> 02:53:21.349 align:start position:0% how AI is used and must ensure that generated<02:53:19.439> code<02:53:20.080> meets<02:53:20.479> organizational 02:53:21.349 --> 02:53:21.359 align:start position:0% generated code meets organizational 02:53:21.359 --> 02:53:24.630 align:start position:0% generated code meets organizational policies<02:53:22.160> and<02:53:22.479> quality<02:53:22.960> requirements. 02:53:24.630 --> 02:53:24.640 align:start position:0% policies and quality requirements. 02:53:24.640 --> 02:53:27.190 align:start position:0% policies and quality requirements. The<02:53:24.880> best<02:53:25.120> practices<02:53:25.760> branch<02:53:26.479> represents<02:53:27.040> the 02:53:27.190 --> 02:53:27.200 align:start position:0% The best practices branch represents the 02:53:27.200 --> 02:53:28.950 align:start position:0% The best practices branch represents the habits<02:53:27.600> that<02:53:27.840> produce<02:53:28.160> the<02:53:28.399> best<02:53:28.640> results 02:53:28.950 --> 02:53:28.960 align:start position:0% habits that produce the best results 02:53:28.960 --> 02:53:31.269 align:start position:0% habits that produce the best results when<02:53:29.279> working<02:53:29.439> with<02:53:29.680> codecs. 02:53:31.269 --> 02:53:31.279 align:start position:0% when working with codecs. 02:53:31.279 --> 02:53:33.190 align:start position:0% when working with codecs. Effective<02:53:31.760> prompt<02:53:32.160> engineering<02:53:32.800> helps 02:53:33.190 --> 02:53:33.200 align:start position:0% Effective prompt engineering helps 02:53:33.200 --> 02:53:34.950 align:start position:0% Effective prompt engineering helps developers<02:53:33.760> communicate<02:53:34.319> requirements 02:53:34.950 --> 02:53:34.960 align:start position:0% developers communicate requirements 02:53:34.960 --> 02:53:38.150 align:start position:0% developers communicate requirements clearly.<02:53:36.319> Code<02:53:36.640> reviews<02:53:37.120> ensure<02:53:37.600> generated 02:53:38.150 --> 02:53:38.160 align:start position:0% clearly. Code reviews ensure generated 02:53:38.160 --> 02:53:40.950 align:start position:0% clearly. Code reviews ensure generated code<02:53:38.399> is<02:53:38.640> maintainable<02:53:39.279> and<02:53:39.600> secure. 02:53:40.950 --> 02:53:40.960 align:start position:0% code is maintainable and secure. 02:53:40.960 --> 02:53:43.510 align:start position:0% code is maintainable and secure. Validation<02:53:41.600> and<02:53:41.920> testing<02:53:42.399> confirm<02:53:42.800> that<02:53:43.040> AI 02:53:43.510 --> 02:53:43.520 align:start position:0% Validation and testing confirm that AI 02:53:43.520 --> 02:53:45.830 align:start position:0% Validation and testing confirm that AI generated<02:53:44.000> features<02:53:44.800> satisfy<02:53:45.439> business 02:53:45.830 --> 02:53:45.840 align:start position:0% generated features satisfy business 02:53:45.840 --> 02:53:47.670 align:start position:0% generated features satisfy business requirements. 02:53:47.670 --> 02:53:47.680 align:start position:0% requirements. 02:53:47.680 --> 02:53:49.910 align:start position:0% requirements. These<02:53:48.080> practices<02:53:48.640> help<02:53:48.960> maximize<02:53:49.439> the<02:53:49.680> value 02:53:49.910 --> 02:53:49.920 align:start position:0% These practices help maximize the value 02:53:49.920 --> 02:53:52.710 align:start position:0% These practices help maximize the value of<02:53:50.160> AI<02:53:50.640> assisted<02:53:51.120> development. 02:53:52.710 --> 02:53:52.720 align:start position:0% of AI assisted development. 02:53:52.720 --> 02:53:54.950 align:start position:0% of AI assisted development. Another<02:53:53.200> important<02:53:53.600> area<02:53:54.000> is<02:53:54.240> operational 02:53:54.950 --> 02:53:54.960 align:start position:0% Another important area is operational 02:53:54.960 --> 02:53:58.230 align:start position:0% Another important area is operational excellence.<02:53:56.240> As<02:53:56.560> AI<02:53:56.960> adoption<02:53:57.439> grows, 02:53:58.230 --> 02:53:58.240 align:start position:0% excellence. As AI adoption grows, 02:53:58.240 --> 02:54:01.110 align:start position:0% excellence. As AI adoption grows, organizations<02:53:59.040> must<02:53:59.439> monitor<02:53:59.840> usage,<02:54:00.720> manage 02:54:01.110 --> 02:54:01.120 align:start position:0% organizations must monitor usage, manage 02:54:01.120 --> 02:54:03.990 align:start position:0% organizations must monitor usage, manage costs,<02:54:01.920> optimize<02:54:02.560> resources,<02:54:03.359> and<02:54:03.600> measure 02:54:03.990 --> 02:54:04.000 align:start position:0% costs, optimize resources, and measure 02:54:04.000 --> 02:54:05.590 align:start position:0% costs, optimize resources, and measure performance. 02:54:05.590 --> 02:54:05.600 align:start position:0% performance. 02:54:05.600 --> 02:54:07.750 align:start position:0% performance. Understanding<02:54:06.240> token<02:54:06.720> consumption, 02:54:07.750 --> 02:54:07.760 align:start position:0% Understanding token consumption, 02:54:07.760 --> 02:54:10.150 align:start position:0% Understanding token consumption, tracking<02:54:08.240> productivity<02:54:08.880> improvements,<02:54:09.920> and 02:54:10.150 --> 02:54:10.160 align:start position:0% tracking productivity improvements, and 02:54:10.160 --> 02:54:12.790 align:start position:0% tracking productivity improvements, and evaluating<02:54:10.880> return<02:54:11.200> on<02:54:11.520> investment<02:54:12.479> help 02:54:12.790 --> 02:54:12.800 align:start position:0% evaluating return on investment help 02:54:12.800 --> 02:54:15.830 align:start position:0% evaluating return on investment help organizations<02:54:13.680> scale<02:54:14.080> AI<02:54:14.640> responsibly<02:54:15.520> and 02:54:15.830 --> 02:54:15.840 align:start position:0% organizations scale AI responsibly and 02:54:15.840 --> 02:54:17.750 align:start position:0% organizations scale AI responsibly and efficiently. 02:54:17.750 --> 02:54:17.760 align:start position:0% efficiently. 02:54:17.760 --> 02:54:19.910 align:start position:0% efficiently. The<02:54:18.000> continuous<02:54:18.560> learning<02:54:19.040> branch<02:54:19.520> reminds 02:54:19.910 --> 02:54:19.920 align:start position:0% The continuous learning branch reminds 02:54:19.920 --> 02:54:22.550 align:start position:0% The continuous learning branch reminds learners<02:54:20.640> that<02:54:21.040> AI<02:54:21.439> technologies<02:54:22.080> evolve 02:54:22.550 --> 02:54:22.560 align:start position:0% learners that AI technologies evolve 02:54:22.560 --> 02:54:24.070 align:start position:0% learners that AI technologies evolve rapidly. 02:54:24.070 --> 02:54:24.080 align:start position:0% rapidly. 02:54:24.080 --> 02:54:25.910 align:start position:0% rapidly. Developers<02:54:24.720> should<02:54:24.960> stay<02:54:25.120> informed<02:54:25.600> about 02:54:25.910 --> 02:54:25.920 align:start position:0% Developers should stay informed about 02:54:25.920 --> 02:54:28.790 align:start position:0% Developers should stay informed about new<02:54:26.160> codeex<02:54:26.720> capabilities,<02:54:28.080> open<02:54:28.399> AI 02:54:28.790 --> 02:54:28.800 align:start position:0% new codeex capabilities, open AI 02:54:28.800 --> 02:54:31.190 align:start position:0% new codeex capabilities, open AI platform<02:54:29.200> updates,<02:54:30.399> community<02:54:30.880> best 02:54:31.190 --> 02:54:31.200 align:start position:0% platform updates, community best 02:54:31.200 --> 02:54:34.630 align:start position:0% platform updates, community best practices,<02:54:32.240> and<02:54:32.479> industry<02:54:32.960> trends. 02:54:34.630 --> 02:54:34.640 align:start position:0% practices, and industry trends. 02:54:34.640 --> 02:54:37.190 align:start position:0% practices, and industry trends. Teams<02:54:35.040> that<02:54:35.279> continuously<02:54:36.000> learn<02:54:36.240> and<02:54:36.479> adapt 02:54:37.190 --> 02:54:37.200 align:start position:0% Teams that continuously learn and adapt 02:54:37.200 --> 02:54:38.950 align:start position:0% Teams that continuously learn and adapt will<02:54:37.439> gain<02:54:37.680> the<02:54:37.920> greatest<02:54:38.399> long-term 02:54:38.950 --> 02:54:38.960 align:start position:0% will gain the greatest long-term 02:54:38.960 --> 02:54:42.710 align:start position:0% will gain the greatest long-term benefits<02:54:39.439> from<02:54:39.680> AI<02:54:40.240> assisted<02:54:40.720> development. 02:54:42.710 --> 02:54:42.720 align:start position:0% benefits from AI assisted development. 02:54:42.720 --> 02:54:45.110 align:start position:0% benefits from AI assisted development. The<02:54:42.960> future<02:54:43.279> of<02:54:43.520> development<02:54:44.000> section<02:54:44.800> looks 02:54:45.110 --> 02:54:45.120 align:start position:0% The future of development section looks 02:54:45.120 --> 02:54:47.590 align:start position:0% The future of development section looks ahead<02:54:45.359> to<02:54:45.600> emerging<02:54:46.080> trends. 02:54:47.590 --> 02:54:47.600 align:start position:0% ahead to emerging trends. 02:54:47.600 --> 02:54:50.550 align:start position:0% ahead to emerging trends. AI<02:54:48.160> assistance<02:54:48.720> will<02:54:48.960> become<02:54:49.279> more<02:54:49.520> capable. 02:54:50.550 --> 02:54:50.560 align:start position:0% AI assistance will become more capable. 02:54:50.560 --> 02:54:52.630 align:start position:0% AI assistance will become more capable. Agent-based<02:54:51.359> workflows<02:54:51.920> will<02:54:52.160> become<02:54:52.399> more 02:54:52.630 --> 02:54:52.640 align:start position:0% Agent-based workflows will become more 02:54:52.640 --> 02:54:55.910 align:start position:0% Agent-based workflows will become more common<02:54:53.439> and<02:54:53.760> human<02:54:54.240> AI<02:54:54.640> collaboration<02:54:55.600> will 02:54:55.910 --> 02:54:55.920 align:start position:0% common and human AI collaboration will 02:54:55.920 --> 02:54:58.150 align:start position:0% common and human AI collaboration will continue<02:54:56.319> to<02:54:56.560> evolve. 02:54:58.150 --> 02:54:58.160 align:start position:0% continue to evolve. 02:54:58.160 --> 02:55:00.309 align:start position:0% continue to evolve. Developers<02:54:58.720> will<02:54:58.960> increasingly<02:54:59.600> focus<02:55:00.000> on 02:55:00.309 --> 02:55:00.319 align:start position:0% Developers will increasingly focus on 02:55:00.319 --> 02:55:02.870 align:start position:0% Developers will increasingly focus on architecture,<02:55:01.439> business<02:55:01.840> logic,<02:55:02.640> and 02:55:02.870 --> 02:55:02.880 align:start position:0% architecture, business logic, and 02:55:02.880 --> 02:55:05.990 align:start position:0% architecture, business logic, and strategic<02:55:03.520> decision-m<02:55:04.800> while<02:55:05.120> AI<02:55:05.600> handles 02:55:05.990 --> 02:55:06.000 align:start position:0% strategic decision-m while AI handles 02:55:06.000 --> 02:55:08.710 align:start position:0% strategic decision-m while AI handles more<02:55:06.240> implementation<02:55:06.960> tasks. 02:55:08.710 --> 02:55:08.720 align:start position:0% more implementation tasks. 02:55:08.720 --> 02:55:11.349 align:start position:0% more implementation tasks. Finally,<02:55:09.600> the<02:55:09.840> most<02:55:10.160> important<02:55:10.560> takeaway<02:55:11.120> is 02:55:11.349 --> 02:55:11.359 align:start position:0% Finally, the most important takeaway is 02:55:11.359 --> 02:55:14.389 align:start position:0% Finally, the most important takeaway is that<02:55:11.600> AI<02:55:12.080> augments<02:55:12.720> developers<02:55:13.760> rather<02:55:14.080> than 02:55:14.389 --> 02:55:14.399 align:start position:0% that AI augments developers rather than 02:55:14.399 --> 02:55:17.670 align:start position:0% that AI augments developers rather than replacing<02:55:14.880> them.<02:55:16.160> Human<02:55:16.560> expertise<02:55:17.200> remains 02:55:17.670 --> 02:55:17.680 align:start position:0% replacing them. Human expertise remains 02:55:17.680 --> 02:55:19.429 align:start position:0% replacing them. Human expertise remains essential<02:55:18.080> for<02:55:18.399> understanding<02:55:19.040> business 02:55:19.429 --> 02:55:19.439 align:start position:0% essential for understanding business 02:55:19.439 --> 02:55:21.750 align:start position:0% essential for understanding business requirements,<02:55:20.640> making<02:55:20.960> architectural 02:55:21.750 --> 02:55:21.760 align:start position:0% requirements, making architectural 02:55:21.760 --> 02:55:24.630 align:start position:0% requirements, making architectural decisions,<02:55:22.800> reviewing<02:55:23.279> code<02:55:23.600> quality, 02:55:24.630 --> 02:55:24.640 align:start position:0% decisions, reviewing code quality, 02:55:24.640 --> 02:55:27.190 align:start position:0% decisions, reviewing code quality, managing<02:55:25.120> risk,<02:55:25.920> and<02:55:26.160> ensuring<02:55:26.640> software 02:55:27.190 --> 02:55:27.200 align:start position:0% managing risk, and ensuring software 02:55:27.200 --> 02:55:29.910 align:start position:0% managing risk, and ensuring software meets<02:55:27.520> organizational<02:55:28.319> goals. 02:55:29.910 --> 02:55:29.920 align:start position:0% meets organizational goals. 02:55:29.920 --> 02:55:32.710 align:start position:0% meets organizational goals. When<02:55:30.160> used<02:55:30.479> effectively,<02:55:31.680> codeex<02:55:32.319> enables 02:55:32.710 --> 02:55:32.720 align:start position:0% When used effectively, codeex enables 02:55:32.720 --> 02:55:34.710 align:start position:0% When used effectively, codeex enables developers<02:55:33.279> to<02:55:33.439> deliver<02:55:33.840> better<02:55:34.160> software 02:55:34.710 --> 02:55:34.720 align:start position:0% developers to deliver better software 02:55:34.720 --> 02:55:37.349 align:start position:0% developers to deliver better software faster<02:55:35.600> while<02:55:35.920> maintaining<02:55:36.479> quality, 02:55:37.349 --> 02:55:37.359 align:start position:0% faster while maintaining quality, 02:55:37.359 --> 02:55:40.630 align:start position:0% faster while maintaining quality, security,<02:55:38.240> and<02:55:38.560> reliability. 02:55:40.630 --> 02:55:40.640 align:start position:0% security, and reliability. 02:55:40.640 --> 02:55:43.190 align:start position:0% security, and reliability. In<02:55:40.880> summary,<02:55:41.680> the<02:55:41.920> course<02:55:42.319> demonstrates<02:55:42.880> that 02:55:43.190 --> 02:55:43.200 align:start position:0% In summary, the course demonstrates that 02:55:43.200 --> 02:55:45.670 align:start position:0% In summary, the course demonstrates that successful<02:55:43.840> enterprise<02:55:44.399> AI<02:55:44.800> adoption 02:55:45.670 --> 02:55:45.680 align:start position:0% successful enterprise AI adoption 02:55:45.680 --> 02:55:47.429 align:start position:0% successful enterprise AI adoption requires<02:55:46.160> a<02:55:46.319> combination<02:55:46.720> of<02:55:46.960> technical 02:55:47.429 --> 02:55:47.439 align:start position:0% requires a combination of technical 02:55:47.439 --> 02:55:50.389 align:start position:0% requires a combination of technical skills,<02:55:48.319> governance<02:55:48.800> practices,<02:55:49.840> continuous 02:55:50.389 --> 02:55:50.399 align:start position:0% skills, governance practices, continuous 02:55:50.399 --> 02:55:52.710 align:start position:0% skills, governance practices, continuous learning,<02:55:51.279> and<02:55:51.520> thoughtful<02:55:52.080> collaboration 02:55:52.710 --> 02:55:52.720 align:start position:0% learning, and thoughtful collaboration 02:55:52.720 --> 02:55:57.200 align:start position:0% learning, and thoughtful collaboration between<02:55:53.120> humans<02:55:53.600> and<02:55:53.840> AI<02:55:54.240> systems.