WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:11.860 align:start position:0% [Applause] 00:00:11.860 --> 00:00:11.870 align:start position:0% 00:00:11.870 --> 00:00:14.870 align:start position:0% sir<00:00:12.870> further<00:00:13.230> today<00:00:13.410> the<00:00:13.920> first<00:00:14.130> period<00:00:14.460> some 00:00:14.870 --> 00:00:14.880 align:start position:0% sir further today the first period some 00:00:14.880 --> 00:00:17.540 align:start position:0% sir further today the first period some think<00:00:15.240> about<00:00:15.299> the<00:00:15.570> ecologist<00:00:16.020> and<00:00:16.550> I'm 00:00:17.540 --> 00:00:17.550 align:start position:0% think about the ecologist and I'm 00:00:17.550 --> 00:00:20.089 align:start position:0% think about the ecologist and I'm grateful<00:00:18.360> that<00:00:18.390> so<00:00:18.810> many<00:00:18.869> people<00:00:19.439> came<00:00:19.650> and 00:00:20.089 --> 00:00:20.099 align:start position:0% grateful that so many people came and 00:00:20.099 --> 00:00:23.749 align:start position:0% grateful that so many people came and talked<00:00:20.610> the<00:00:20.880> pest<00:00:21.180> or<00:00:21.630> two<00:00:21.869> type<00:00:22.369> of<00:00:23.369> Korean 00:00:23.749 --> 00:00:23.759 align:start position:0% talked the pest or two type of Korean 00:00:23.759 --> 00:00:26.179 align:start position:0% talked the pest or two type of Korean three<00:00:24.090> times<00:00:24.390> in<00:00:24.660> the<00:00:24.779> title<00:00:25.230> so<00:00:25.439> thanks<00:00:26.070> for 00:00:26.179 --> 00:00:26.189 align:start position:0% three times in the title so thanks for 00:00:26.189 --> 00:00:27.050 align:start position:0% three times in the title so thanks for being<00:00:26.400> here 00:00:27.050 --> 00:00:27.060 align:start position:0% being here 00:00:27.060 --> 00:00:29.720 align:start position:0% being here my<00:00:27.930> name<00:00:28.079> is<00:00:28.200> first<00:00:28.439> I<00:00:28.619> work<00:00:28.829> at<00:00:29.009> maker 00:00:29.720 --> 00:00:29.730 align:start position:0% my name is first I work at maker 00:00:29.730 --> 00:00:31.970 align:start position:0% my name is first I work at maker Foundation<00:00:30.360> and<00:00:30.660> today<00:00:31.320> I'm<00:00:31.560> going<00:00:31.770> to<00:00:31.829> be 00:00:31.970 --> 00:00:31.980 align:start position:0% Foundation and today I'm going to be 00:00:31.980 --> 00:00:34.760 align:start position:0% Foundation and today I'm going to be talking<00:00:32.550> about<00:00:33.030> creating<00:00:33.450> site<00:00:33.989> type<00:00:34.470> site 00:00:34.760 --> 00:00:34.770 align:start position:0% talking about creating site type site 00:00:34.770 --> 00:00:41.360 align:start position:0% talking about creating site type site tops<00:00:37.760> so<00:00:38.760> let<00:00:39.600> me<00:00:39.720> ask<00:00:39.780> you<00:00:39.960> a<00:00:40.260> question<00:00:40.649> how 00:00:41.360 --> 00:00:41.370 align:start position:0% tops so let me ask you a question how 00:00:41.370 --> 00:00:48.020 align:start position:0% tops so let me ask you a question how many<00:00:41.399> it<00:00:41.730> with<00:00:41.880> your<00:00:42.090> use<00:00:43.699> faces<00:00:46.969> more<00:00:47.969> than 00:00:48.020 --> 00:00:48.030 align:start position:0% many it with your use faces more than 00:00:48.030 --> 00:00:50.150 align:start position:0% many it with your use faces more than more<00:00:48.690> than<00:00:48.719> half<00:00:49.079> our<00:00:49.230> room<00:00:49.559> already 00:00:50.150 --> 00:00:50.160 align:start position:0% more than half our room already 00:00:50.160 --> 00:00:53.180 align:start position:0% more than half our room already so<00:00:50.579> in<00:00:51.030> the<00:00:51.120> in<00:00:51.480> the<00:00:51.629> last<00:00:51.750> two<00:00:52.260> months<00:00:52.469> yes 00:00:53.180 --> 00:00:53.190 align:start position:0% so in the in the last two months yes 00:00:53.190 --> 00:00:55.549 align:start position:0% so in the in the last two months yes even<00:00:53.730> we<00:00:54.210> have<00:00:54.329> seen<00:00:54.539> like<00:00:54.780> this<00:00:54.960> tremendous 00:00:55.549 --> 00:00:55.559 align:start position:0% even we have seen like this tremendous 00:00:55.559 --> 00:00:59.599 align:start position:0% even we have seen like this tremendous growth<00:00:55.829> of<00:00:56.070> time<00:00:56.609> popularity<00:00:57.570> and<00:00:58.609> presently 00:00:59.599 --> 00:00:59.609 align:start position:0% growth of time popularity and presently 00:00:59.609 --> 00:01:01.790 align:start position:0% growth of time popularity and presently it<00:00:59.969> even<00:01:00.329> got<00:01:00.480> more<00:01:00.690> popular<00:01:01.170> than<00:01:01.409> you<00:01:01.649> know 00:01:01.790 --> 00:01:01.800 align:start position:0% it even got more popular than you know 00:01:01.800 --> 00:01:04.670 align:start position:0% it even got more popular than you know well-established<00:01:02.570> languages<00:01:03.570> like<00:01:03.989> Ruby<00:01:04.350> for 00:01:04.670 --> 00:01:04.680 align:start position:0% well-established languages like Ruby for 00:01:04.680 --> 00:01:06.910 align:start position:0% well-established languages like Ruby for example<00:01:05.129> as<00:01:05.489> you<00:01:05.550> see<00:01:05.820> like<00:01:06.000> steady<00:01:06.330> growth<00:01:06.570> of 00:01:06.910 --> 00:01:06.920 align:start position:0% example as you see like steady growth of 00:01:06.920 --> 00:01:09.680 align:start position:0% example as you see like steady growth of NPM<00:01:07.920> and<00:01:07.950> so<00:01:08.310> on<00:01:08.370> and<00:01:08.580> so<00:01:08.700> on<00:01:08.730> so<00:01:08.940> basically 00:01:09.680 --> 00:01:09.690 align:start position:0% NPM and so on and so on so basically 00:01:09.690 --> 00:01:12.470 align:start position:0% NPM and so on and so on so basically typescript<00:01:10.440> has<00:01:10.650> this<00:01:10.830> huge<00:01:11.130> company<00:01:11.610> kind 00:01:12.470 --> 00:01:12.480 align:start position:0% typescript has this huge company kind 00:01:12.480 --> 00:01:15.560 align:start position:0% typescript has this huge company kind itself<00:01:12.990> called<00:01:13.700> Microsoft<00:01:14.700> and<00:01:14.909> you<00:01:15.479> know 00:01:15.560 --> 00:01:15.570 align:start position:0% itself called Microsoft and you know 00:01:15.570 --> 00:01:19.520 align:start position:0% itself called Microsoft and you know there's<00:01:15.869> a<00:01:15.990> lots<00:01:16.200> of<00:01:17.869> workforce<00:01:18.869> workforce 00:01:19.520 --> 00:01:19.530 align:start position:0% there's a lots of workforce workforce 00:01:19.530 --> 00:01:23.149 align:start position:0% there's a lots of workforce workforce work<00:01:20.340> young<00:01:20.600> language<00:01:21.600> itself<00:01:21.960> and<00:01:22.290> on<00:01:22.740> the 00:01:23.149 --> 00:01:23.159 align:start position:0% work young language itself and on the 00:01:23.159 --> 00:01:26.469 align:start position:0% work young language itself and on the whole<00:01:23.610> tree<00:01:24.210> tooling<00:01:25.110> around<00:01:25.290> so<00:01:25.680> for<00:01:25.890> example 00:01:26.469 --> 00:01:26.479 align:start position:0% whole tree tooling around so for example 00:01:26.479 --> 00:01:30.170 align:start position:0% whole tree tooling around so for example like<00:01:27.479> Visual<00:01:27.930> Studio<00:01:28.049> code<00:01:28.560> was<00:01:29.250> for<00:01:29.759> many 00:01:30.170 --> 00:01:30.180 align:start position:0% like Visual Studio code was for many 00:01:30.180 --> 00:01:33.230 align:start position:0% like Visual Studio code was for many people<00:01:30.659> and<00:01:30.930> entropy<00:01:31.920> like<00:01:32.369> you<00:01:32.640> know<00:01:32.790> entry 00:01:33.230 --> 00:01:33.240 align:start position:0% people and entropy like you know entry 00:01:33.240 --> 00:01:36.740 align:start position:0% people and entropy like you know entry drugs<00:01:33.600> or<00:01:33.899> types<00:01:34.740> because<00:01:35.340> they<00:01:35.579> work<00:01:36.180> so<00:01:36.210> well 00:01:36.740 --> 00:01:36.750 align:start position:0% drugs or types because they work so well 00:01:36.750 --> 00:01:42.050 align:start position:0% drugs or types because they work so well so<00:01:39.439> for<00:01:40.439> those<00:01:40.649> who<00:01:40.710> don't<00:01:40.979> respect<00:01:41.610> people<00:01:41.789> I 00:01:42.050 --> 00:01:42.060 align:start position:0% so for those who don't respect people I 00:01:42.060 --> 00:01:43.819 align:start position:0% so for those who don't respect people I think<00:01:42.299> if<00:01:42.509> you<00:01:42.600> like<00:01:42.780> you<00:01:43.229> know<00:01:43.380> more<00:01:43.680> or<00:01:43.799> less 00:01:43.819 --> 00:01:43.829 align:start position:0% think if you like you know more or less 00:01:43.829 --> 00:01:46.039 align:start position:0% think if you like you know more or less what<00:01:44.460> to<00:01:44.640> expect<00:01:45.060> from<00:01:45.210> the<00:01:45.390> language<00:01:45.719> itself 00:01:46.039 --> 00:01:46.049 align:start position:0% what to expect from the language itself 00:01:46.049 --> 00:01:49.670 align:start position:0% what to expect from the language itself some<00:01:46.799> some<00:01:47.070> ideas<00:01:47.579> behind<00:01:47.759> it<00:01:48.030> so<00:01:48.530> first<00:01:49.530> of 00:01:49.670 --> 00:01:49.680 align:start position:0% some some ideas behind it so first of 00:01:49.680 --> 00:01:51.499 align:start position:0% some some ideas behind it so first of all<00:01:49.740> like<00:01:50.009> you<00:01:50.219> can<00:01:50.369> think<00:01:50.579> about<00:01:50.700> typescript 00:01:51.499 --> 00:01:51.509 align:start position:0% all like you can think about typescript 00:01:51.509 --> 00:01:54.859 align:start position:0% all like you can think about typescript as<00:01:51.780> a<00:01:51.810> JavaScript<00:01:52.439> with<00:01:52.859> types<00:01:53.280> and<00:01:53.640> the<00:01:54.509> only 00:01:54.859 --> 00:01:54.869 align:start position:0% as a JavaScript with types and the only 00:01:54.869 --> 00:01:57.499 align:start position:0% as a JavaScript with types and the only twisting<00:01:55.799> this<00:01:56.009> explanation<00:01:56.670> is<00:01:57.119> that<00:01:57.149> the 00:01:57.499 --> 00:01:57.509 align:start position:0% twisting this explanation is that the 00:01:57.509 --> 00:01:59.480 align:start position:0% twisting this explanation is that the tank<00:01:57.539> system<00:01:58.170> is<00:01:58.289> very<00:01:58.649> different<00:01:59.039> from<00:01:59.280> the 00:01:59.480 --> 00:01:59.490 align:start position:0% tank system is very different from the 00:01:59.490 --> 00:02:02.060 align:start position:0% tank system is very different from the one<00:01:59.640> that<00:01:59.820> you<00:01:59.939> will<00:02:00.030> find<00:02:00.329> in<00:02:00.509> classical<00:02:01.109> of 00:02:02.060 --> 00:02:02.070 align:start position:0% one that you will find in classical of 00:02:02.070 --> 00:02:03.679 align:start position:0% one that you will find in classical of different<00:02:02.609> programming<00:02:03.090> languages<00:02:03.539> like 00:02:03.679 --> 00:02:03.689 align:start position:0% different programming languages like 00:02:03.689 --> 00:02:07.550 align:start position:0% different programming languages like Java<00:02:04.289> or<00:02:04.560> C<00:02:05.250> sharp<00:02:05.460> so<00:02:06.179> first<00:02:07.049> of<00:02:07.170> all<00:02:07.229> you 00:02:07.550 --> 00:02:07.560 align:start position:0% Java or C sharp so first of all you 00:02:07.560 --> 00:02:10.760 align:start position:0% Java or C sharp so first of all you tractors<00:02:08.280> I<00:02:08.520> think<00:02:08.789> so<00:02:09.539> imagine<00:02:10.229> you<00:02:10.319> have<00:02:10.470> two 00:02:10.760 --> 00:02:10.770 align:start position:0% tractors I think so imagine you have two 00:02:10.770 --> 00:02:14.809 align:start position:0% tractors I think so imagine you have two types<00:02:11.430> with<00:02:12.090> like<00:02:12.930> interface<00:02:13.830> and<00:02:14.160> interface 00:02:14.809 --> 00:02:14.819 align:start position:0% types with like interface and interface 00:02:14.819 --> 00:02:18.830 align:start position:0% types with like interface and interface person<00:02:15.390> name<00:02:16.790> property<00:02:17.790> of<00:02:17.880> the<00:02:18.030> string<00:02:18.599> type 00:02:18.830 --> 00:02:18.840 align:start position:0% person name property of the string type 00:02:18.840 --> 00:02:22.970 align:start position:0% person name property of the string type and<00:02:19.280> in<00:02:20.280> typescript<00:02:20.700> these<00:02:21.330> types<00:02:21.720> are<00:02:22.080> in 00:02:22.970 --> 00:02:22.980 align:start position:0% and in typescript these types are in 00:02:22.980 --> 00:02:25.250 align:start position:0% and in typescript these types are in turkette<00:02:23.630> interchangeable<00:02:24.630> so<00:02:24.870> you<00:02:24.930> can 00:02:25.250 --> 00:02:25.260 align:start position:0% turkette interchangeable so you can 00:02:25.260 --> 00:02:26.660 align:start position:0% turkette interchangeable so you can assign<00:02:25.590> one<00:02:25.650> to<00:02:26.069> another 00:02:26.660 --> 00:02:26.670 align:start position:0% assign one to another 00:02:26.670 --> 00:02:29.690 align:start position:0% assign one to another this<00:02:27.180> is<00:02:27.470> totally<00:02:28.470> unexpected<00:02:28.860> for<00:02:29.340> a<00:02:29.370> Java 00:02:29.690 --> 00:02:29.700 align:start position:0% this is totally unexpected for a Java 00:02:29.700 --> 00:02:33.800 align:start position:0% this is totally unexpected for a Java programmer<00:02:30.330> which<00:02:30.810> has<00:02:31.170> nominal<00:02:32.069> type<00:02:32.940> II<00:02:32.970> so 00:02:33.800 --> 00:02:33.810 align:start position:0% programmer which has nominal type II so 00:02:33.810 --> 00:02:37.699 align:start position:0% programmer which has nominal type II so this<00:02:34.560> is<00:02:34.819> totally<00:02:35.819> doable<00:02:36.599> in<00:02:36.870> types<00:02:37.110> but<00:02:37.500> it's 00:02:37.699 --> 00:02:37.709 align:start position:0% this is totally doable in types but it's 00:02:37.709 --> 00:02:40.330 align:start position:0% this is totally doable in types but it's not<00:02:37.860> possible<00:02:38.040> has<00:02:38.550> festered<00:02:38.940> all<00:02:39.360> the 00:02:40.330 --> 00:02:40.340 align:start position:0% not possible has festered all the 00:02:40.340 --> 00:02:42.800 align:start position:0% not possible has festered all the languages<00:02:41.340> and<00:02:41.519> you<00:02:42.299> might<00:02:42.480> be<00:02:42.660> wondering 00:02:42.800 --> 00:02:42.810 align:start position:0% languages and you might be wondering 00:02:42.810 --> 00:02:46.850 align:start position:0% languages and you might be wondering about<00:02:43.400> that<00:02:44.400> picture<00:02:45.090> on<00:02:45.540> the<00:02:45.660> right<00:02:45.860> right 00:02:46.850 --> 00:02:46.860 align:start position:0% about that picture on the right right 00:02:46.860 --> 00:02:50.030 align:start position:0% about that picture on the right right side<00:02:47.160> that<00:02:47.819> image<00:02:48.239> so<00:02:48.269> if<00:02:49.140> your<00:02:49.380> JavaScript 00:02:50.030 --> 00:02:50.040 align:start position:0% side that image so if your JavaScript 00:02:50.040 --> 00:02:52.030 align:start position:0% side that image so if your JavaScript programmer<00:02:50.400> it<00:02:50.640> might<00:02:50.819> be<00:02:51.030> familiar<00:02:51.480> with 00:02:52.030 --> 00:02:52.040 align:start position:0% programmer it might be familiar with 00:02:52.040 --> 00:02:56.539 align:start position:0% programmer it might be familiar with that<00:02:53.040> type<00:02:53.370> in<00:02:53.640> concept<00:02:54.209> so<00:02:54.569> this<00:02:54.989> is<00:02:55.110> that<00:02:55.549> the 00:02:56.539 --> 00:02:56.549 align:start position:0% that type in concept so this is that the 00:02:56.549 --> 00:02:58.580 align:start position:0% that type in concept so this is that the idea<00:02:56.819> is<00:02:57.000> just<00:02:57.030> as<00:02:57.330> follows<00:02:57.690> walks<00:02:58.290> like<00:02:58.530> a 00:02:58.580 --> 00:02:58.590 align:start position:0% idea is just as follows walks like a 00:02:58.590 --> 00:03:01.490 align:start position:0% idea is just as follows walks like a duck<00:02:58.920> quacks<00:02:59.849> like<00:03:00.060> an<00:03:00.390> occupant<00:03:00.959> company<00:03:01.440> is 00:03:01.490 --> 00:03:01.500 align:start position:0% duck quacks like an occupant company is 00:03:01.500 --> 00:03:04.309 align:start position:0% duck quacks like an occupant company is a<00:03:01.620> duck<00:03:01.890> so<00:03:02.430> you<00:03:02.519> don't<00:03:02.760> need<00:03:02.880> to<00:03:03.090> know<00:03:03.319> the 00:03:04.309 --> 00:03:04.319 align:start position:0% a duck so you don't need to know the 00:03:04.319 --> 00:03:06.800 align:start position:0% a duck so you don't need to know the exact<00:03:04.769> shape<00:03:05.160> of<00:03:05.540> entity<00:03:06.540> that<00:03:06.660> you're 00:03:06.800 --> 00:03:06.810 align:start position:0% exact shape of entity that you're 00:03:06.810 --> 00:03:09.170 align:start position:0% exact shape of entity that you're interacting<00:03:07.260> with<00:03:07.440> in<00:03:07.860> just<00:03:08.130> now<00:03:08.459> if<00:03:08.700> it<00:03:08.849> you 00:03:09.170 --> 00:03:09.180 align:start position:0% interacting with in just now if it you 00:03:09.180 --> 00:03:13.250 align:start position:0% interacting with in just now if it you know<00:03:09.620> answer<00:03:10.620> some<00:03:10.980> some<00:03:11.310> common<00:03:12.299> sense<00:03:12.510> a<00:03:12.750> and 00:03:13.250 --> 00:03:13.260 align:start position:0% know answer some some common sense a and 00:03:13.260 --> 00:03:17.750 align:start position:0% know answer some some common sense a and that's<00:03:13.560> why<00:03:13.769> we<00:03:13.890> have<00:03:14.070> that<00:03:14.989> thank<00:03:15.989> you<00:03:16.190> so<00:03:17.190> so 00:03:17.750 --> 00:03:17.760 align:start position:0% that's why we have that thank you so so 00:03:17.760 --> 00:03:19.699 align:start position:0% that's why we have that thank you so so so<00:03:17.790> structure<00:03:18.540> attacking<00:03:19.019> is<00:03:19.140> like<00:03:19.320> a<00:03:19.350> duck 00:03:19.699 --> 00:03:19.709 align:start position:0% so structure attacking is like a duck 00:03:19.709 --> 00:03:25.190 align:start position:0% so structure attacking is like a duck typing<00:03:20.160> but<00:03:20.690> queuing<00:03:21.690> compile-time<00:03:23.989> so<00:03:24.989> then 00:03:25.190 --> 00:03:25.200 align:start position:0% typing but queuing compile-time so then 00:03:25.200 --> 00:03:28.640 align:start position:0% typing but queuing compile-time so then we<00:03:25.350> have<00:03:25.530> touched<00:03:26.280> it<00:03:26.519> press<00:03:27.299> advanced<00:03:27.720> level 00:03:28.640 --> 00:03:28.650 align:start position:0% we have touched it press advanced level 00:03:28.650 --> 00:03:32.780 align:start position:0% we have touched it press advanced level programming<00:03:29.540> internet<00:03:30.540> so<00:03:31.459> pretty 00:03:32.780 --> 00:03:32.790 align:start position:0% programming internet so pretty 00:03:32.790 --> 00:03:36.349 align:start position:0% programming internet so pretty basically<00:03:33.180> it<00:03:33.359> allows<00:03:33.510> us<00:03:33.900> to<00:03:34.760> transport<00:03:35.760> high 00:03:36.349 --> 00:03:36.359 align:start position:0% basically it allows us to transport high 00:03:36.359 --> 00:03:38.680 align:start position:0% basically it allows us to transport high doing<00:03:37.079> compile<00:03:37.590> time 00:03:38.680 --> 00:03:38.690 align:start position:0% doing compile time 00:03:38.690 --> 00:03:42.850 align:start position:0% doing compile time like<00:03:39.280> unimaginable<00:03:40.280> a<00:03:40.520> so<00:03:41.290> here<00:03:42.290> we<00:03:42.410> have<00:03:42.590> a 00:03:42.850 --> 00:03:42.860 align:start position:0% like unimaginable a so here we have a 00:03:42.860 --> 00:03:45.760 align:start position:0% like unimaginable a so here we have a complex<00:03:43.430> object<00:03:44.300> type<00:03:44.570> which<00:03:44.870> has<00:03:44.900> like<00:03:45.380> some 00:03:45.760 --> 00:03:45.770 align:start position:0% complex object type which has like some 00:03:45.770 --> 00:03:49.540 align:start position:0% complex object type which has like some nested<00:03:47.110> mr.<00:03:48.110> properties<00:03:48.680> we<00:03:48.920> have<00:03:48.950> some<00:03:49.160> area 00:03:49.540 --> 00:03:49.550 align:start position:0% nested mr. properties we have some area 00:03:49.550 --> 00:03:52.480 align:start position:0% nested mr. properties we have some area is<00:03:49.610> nested<00:03:50.120> and<00:03:50.240> so<00:03:50.420> on<00:03:50.600> so<00:03:50.810> on<00:03:50.840> and<00:03:51.230> now<00:03:51.740> we<00:03:52.220> can 00:03:52.480 --> 00:03:52.490 align:start position:0% is nested and so on so on and now we can 00:03:52.490 --> 00:03:56.130 align:start position:0% is nested and so on so on and now we can use<00:03:53.890> some<00:03:54.890> generic<00:03:55.370> type<00:03:55.640> like<00:03:55.850> for<00:03:56.030> example 00:03:56.130 --> 00:03:56.140 align:start position:0% use some generic type like for example 00:03:56.140 --> 00:04:00.480 align:start position:0% use some generic type like for example departure<00:03:57.140> coming<00:03:57.560> from<00:03:57.770> the<00:03:58.900> health<00:03:59.900> ER 00:04:00.480 --> 00:04:00.490 align:start position:0% departure coming from the health ER 00:04:00.490 --> 00:04:03.270 align:start position:0% departure coming from the health ER library<00:04:01.490> called<00:04:01.790> des<00:04:02.390> essentials<00:04:02.690> and 00:04:03.270 --> 00:04:03.280 align:start position:0% library called des essentials and 00:04:03.280 --> 00:04:06.400 align:start position:0% library called des essentials and associate<00:04:04.280> and<00:04:04.760> and<00:04:05.120> we<00:04:05.270> gonna<00:04:05.420> get<00:04:05.750> like<00:04:06.170> an 00:04:06.400 --> 00:04:06.410 align:start position:0% associate and and we gonna get like an 00:04:06.410 --> 00:04:08.650 align:start position:0% associate and and we gonna get like an object<00:04:06.740> with<00:04:07.220> all<00:04:07.430> properties<00:04:08.060> marked<00:04:08.450> as 00:04:08.650 --> 00:04:08.660 align:start position:0% object with all properties marked as 00:04:08.660 --> 00:04:11.770 align:start position:0% object with all properties marked as optional<00:04:09.580> recursively<00:04:10.580> and<00:04:11.150> this<00:04:11.480> is<00:04:11.540> pretty 00:04:11.770 --> 00:04:11.780 align:start position:0% optional recursively and this is pretty 00:04:11.780 --> 00:04:13.050 align:start position:0% optional recursively and this is pretty awesome<00:04:11.900> like<00:04:12.260> you<00:04:12.410> know<00:04:12.530> you<00:04:12.650> can<00:04:12.830> have<00:04:13.010> a 00:04:13.050 --> 00:04:13.060 align:start position:0% awesome like you know you can have a 00:04:13.060 --> 00:04:16.509 align:start position:0% awesome like you know you can have a config<00:04:14.060> which<00:04:14.420> is<00:04:14.630> like<00:04:14.950> strict<00:04:15.950> and<00:04:16.220> then<00:04:16.370> we 00:04:16.509 --> 00:04:16.519 align:start position:0% config which is like strict and then we 00:04:16.519 --> 00:04:18.460 align:start position:0% config which is like strict and then we can<00:04:16.670> have<00:04:16.910> like<00:04:17.150> you<00:04:17.359> know<00:04:17.480> some<00:04:17.780> defaults<00:04:18.290> and 00:04:18.460 --> 00:04:18.470 align:start position:0% can have like you know some defaults and 00:04:18.470 --> 00:04:20.949 align:start position:0% can have like you know some defaults and then<00:04:18.680> make<00:04:18.920> automatically<00:04:19.670> user<00:04:20.120> input<00:04:20.660> which 00:04:20.949 --> 00:04:20.959 align:start position:0% then make automatically user input which 00:04:20.959 --> 00:04:25.060 align:start position:0% then make automatically user input which is<00:04:21.109> like<00:04:21.260> optional<00:04:21.859> of<00:04:22.100> this<00:04:22.580> of<00:04:22.820> this<00:04:24.070> config 00:04:25.060 --> 00:04:25.070 align:start position:0% is like optional of this of this config 00:04:25.070 --> 00:04:29.050 align:start position:0% is like optional of this of this config object<00:04:26.860> and<00:04:27.860> finally<00:04:28.160> we<00:04:28.460> have<00:04:28.610> gradual 00:04:29.050 --> 00:04:29.060 align:start position:0% object and finally we have gradual 00:04:29.060 --> 00:04:30.730 align:start position:0% object and finally we have gradual typing<00:04:29.330> this<00:04:29.660> means<00:04:29.870> basically<00:04:30.260> that<00:04:30.530> we 00:04:30.730 --> 00:04:30.740 align:start position:0% typing this means basically that we 00:04:30.740 --> 00:04:34.120 align:start position:0% typing this means basically that we don't<00:04:31.040> have<00:04:31.310> to<00:04:31.490> type<00:04:31.820> our<00:04:32.290> application<00:04:33.290> 100% 00:04:34.120 --> 00:04:34.130 align:start position:0% don't have to type our application 100% 00:04:34.130 --> 00:04:36.040 align:start position:0% don't have to type our application 100% correctly<00:04:34.550> of<00:04:35.060> course<00:04:35.390> you<00:04:35.570> should<00:04:35.720> try<00:04:35.990> to 00:04:36.040 --> 00:04:36.050 align:start position:0% correctly of course you should try to 00:04:36.050 --> 00:04:38.110 align:start position:0% correctly of course you should try to have<00:04:36.350> this<00:04:36.590> we<00:04:37.370> can<00:04:37.520> come<00:04:37.730> up<00:04:37.760> with 00:04:38.110 --> 00:04:38.120 align:start position:0% have this we can come up with 00:04:38.120 --> 00:04:40.510 align:start position:0% have this we can come up with type<00:04:38.480> type<00:04:39.260> coverage<00:04:39.770> metric<00:04:40.340> which 00:04:40.510 --> 00:04:40.520 align:start position:0% type type coverage metric which 00:04:40.520 --> 00:04:43.330 align:start position:0% type type coverage metric which basically<00:04:41.060> means<00:04:41.360> like<00:04:41.480> we<00:04:42.440> can<00:04:42.620> count<00:04:43.010> the 00:04:43.330 --> 00:04:43.340 align:start position:0% basically means like we can count the 00:04:43.340 --> 00:04:46.500 align:start position:0% basically means like we can count the number<00:04:43.640> of<00:04:44.180> symbols<00:04:44.660> now<00:04:45.050> programs<00:04:45.590> that<00:04:45.830> are 00:04:46.500 --> 00:04:46.510 align:start position:0% number of symbols now programs that are 00:04:46.510 --> 00:04:49.840 align:start position:0% number of symbols now programs that are typed<00:04:47.510> as<00:04:47.750> any<00:04:47.990> any<00:04:48.500> means<00:04:48.980> that<00:04:49.130> it's<00:04:49.460> pre 00:04:49.840 --> 00:04:49.850 align:start position:0% typed as any any means that it's pre 00:04:49.850 --> 00:04:53.140 align:start position:0% typed as any any means that it's pre untied<00:04:50.500> and<00:04:51.500> divided<00:04:52.040> by<00:04:52.070> all<00:04:52.490> the<00:04:52.669> symbols<00:04:53.060> in 00:04:53.140 --> 00:04:53.150 align:start position:0% untied and divided by all the symbols in 00:04:53.150 --> 00:04:54.460 align:start position:0% untied and divided by all the symbols in our<00:04:53.270> program<00:04:53.690> and<00:04:53.840> we<00:04:53.900> be<00:04:53.990> able<00:04:54.140> to<00:04:54.230> come<00:04:54.440> up 00:04:54.460 --> 00:04:54.470 align:start position:0% our program and we be able to come up 00:04:54.470 --> 00:04:57.340 align:start position:0% our program and we be able to come up with<00:04:54.590> this<00:04:54.860> presentation<00:04:55.730> how<00:04:56.030> my<00:04:56.630> how<00:04:57.110> your 00:04:57.340 --> 00:04:57.350 align:start position:0% with this presentation how my how your 00:04:57.350 --> 00:05:01.150 align:start position:0% with this presentation how my how your program<00:04:57.710> is<00:04:57.890> you<00:04:58.220> know<00:04:58.450> tight<00:04:59.480> and<00:05:00.260> this<00:05:00.860> is 00:05:01.150 --> 00:05:01.160 align:start position:0% program is you know tight and this is 00:05:01.160 --> 00:05:03.250 align:start position:0% program is you know tight and this is still<00:05:01.400> tight<00:05:01.760> coverage<00:05:02.240> test<00:05:02.570> first<00:05:02.930> and 00:05:03.250 --> 00:05:03.260 align:start position:0% still tight coverage test first and 00:05:03.260 --> 00:05:07.630 align:start position:0% still tight coverage test first and basically<00:05:04.840> this<00:05:05.840> allows<00:05:06.020> us<00:05:06.410> to<00:05:06.680> just<00:05:07.190> fall 00:05:07.630 --> 00:05:07.640 align:start position:0% basically this allows us to just fall 00:05:07.640 --> 00:05:10.120 align:start position:0% basically this allows us to just fall back<00:05:07.669> to<00:05:08.210> JavaScript<00:05:09.200> if<00:05:09.440> we<00:05:09.650> don't<00:05:09.890> have 00:05:10.120 --> 00:05:10.130 align:start position:0% back to JavaScript if we don't have 00:05:10.130 --> 00:05:12.880 align:start position:0% back to JavaScript if we don't have tight<00:05:10.550> coverage<00:05:11.060> or<00:05:11.330> we<00:05:12.260> don't<00:05:12.470> have<00:05:12.650> typed 00:05:12.880 --> 00:05:12.890 align:start position:0% tight coverage or we don't have typed 00:05:12.890 --> 00:05:15.040 align:start position:0% tight coverage or we don't have typed information<00:05:13.610> or<00:05:13.850> we<00:05:14.000> just<00:05:14.210> don't<00:05:14.480> care<00:05:14.810> about 00:05:15.040 --> 00:05:15.050 align:start position:0% information or we just don't care about 00:05:15.050 --> 00:05:17.950 align:start position:0% information or we just don't care about types<00:05:15.590> in<00:05:15.800> this<00:05:16.100> specific<00:05:16.669> place<00:05:16.880> but<00:05:17.180> a 00:05:17.950 --> 00:05:17.960 align:start position:0% types in this specific place but a 00:05:17.960 --> 00:05:21.210 align:start position:0% types in this specific place but a person<00:05:18.530> should<00:05:18.710> be<00:05:18.740> used<00:05:19.490> as<00:05:19.790> a<00:05:20.120> thesis 00:05:21.210 --> 00:05:21.220 align:start position:0% person should be used as a thesis 00:05:21.220 --> 00:05:24.440 align:start position:0% person should be used as a thesis as<00:05:21.280> possible<00:05:21.840> so<00:05:22.840> now<00:05:23.050> let's<00:05:23.320> talk<00:05:23.500> about<00:05:23.560> how 00:05:24.440 --> 00:05:24.450 align:start position:0% as possible so now let's talk about how 00:05:24.450 --> 00:05:26.400 align:start position:0% as possible so now let's talk about how well<00:05:25.450> I<00:05:25.480> did<00:05:25.630> the<00:05:25.840> challenge<00:05:26.230> is<00:05:26.380> about 00:05:26.400 --> 00:05:26.410 align:start position:0% well I did the challenge is about 00:05:26.410 --> 00:05:31.100 align:start position:0% well I did the challenge is about typescript<00:05:27.130> and<00:05:27.430> web<00:05:28.300> free<00:05:28.630> and<00:05:29.280> iam 00:05:31.100 --> 00:05:31.110 align:start position:0% typescript and web free and iam 00:05:31.110 --> 00:05:48.780 align:start position:0% typescript and web free and iam ecosystem<00:05:32.110> challenges<00:05:44.490> so<00:05:46.260> Amy<00:05:47.260> so<00:05:47.890> now<00:05:48.760> I 00:05:48.780 --> 00:05:48.790 align:start position:0% ecosystem challenges so Amy so now I 00:05:48.790 --> 00:05:52.350 align:start position:0% ecosystem challenges so Amy so now I created<00:05:49.690> like<00:05:49.870> a<00:05:50.020> simple<00:05:50.500> web<00:05:51.130> free<00:05:51.490> diet 00:05:52.350 --> 00:05:52.360 align:start position:0% created like a simple web free diet 00:05:52.360 --> 00:05:56.520 align:start position:0% created like a simple web free diet called<00:05:53.110> snippet<00:05:53.560> so<00:05:54.280> here<00:05:54.640> we<00:05:55.000> so<00:05:55.390> what<00:05:55.960> web 00:05:56.520 --> 00:05:56.530 align:start position:0% called snippet so here we so what web 00:05:56.530 --> 00:05:58.200 align:start position:0% called snippet so here we so what web page<00:05:56.770> is<00:05:56.980> is<00:05:57.250> a<00:05:57.280> library<00:05:57.730> written<00:05:57.880> in 00:05:58.200 --> 00:05:58.210 align:start position:0% page is is a library written in 00:05:58.210 --> 00:06:02.400 align:start position:0% page is is a library written in JavaScript<00:05:59.020> it's<00:05:59.470> not<00:05:59.680> types<00:06:00.250> hi<00:06:01.380> neighbors 00:06:02.400 --> 00:06:02.410 align:start position:0% JavaScript it's not types hi neighbors 00:06:02.410 --> 00:06:06.170 align:start position:0% JavaScript it's not types hi neighbors so<00:06:02.650> here<00:06:03.490> even<00:06:03.850> though<00:06:04.120> it's<00:06:04.360> a<00:06:04.540> type<00:06:04.900> of<00:06:04.930> pipe 00:06:06.170 --> 00:06:06.180 align:start position:0% so here even though it's a type of pipe 00:06:06.180 --> 00:06:10.620 align:start position:0% so here even though it's a type of pipe we<00:06:07.180> use<00:06:07.390> it<00:06:07.630> as<00:06:08.160> it's<00:06:09.160> marked<00:06:09.490> as<00:06:09.610> any<00:06:09.910> we<00:06:10.510> don't 00:06:10.620 --> 00:06:10.630 align:start position:0% we use it as it's marked as any we don't 00:06:10.630 --> 00:06:12.390 align:start position:0% we use it as it's marked as any we don't have<00:06:10.840> any<00:06:11.050> type<00:06:11.320> information<00:06:11.890> about<00:06:12.130> it<00:06:12.250> but 00:06:12.390 --> 00:06:12.400 align:start position:0% have any type information about it but 00:06:12.400 --> 00:06:14.280 align:start position:0% have any type information about it but we<00:06:12.490> can<00:06:12.669> still<00:06:12.880> use<00:06:12.940> it<00:06:13.270> and<00:06:13.450> just<00:06:13.750> operate 00:06:14.280 --> 00:06:14.290 align:start position:0% we can still use it and just operate 00:06:14.290 --> 00:06:16.860 align:start position:0% we can still use it and just operate like<00:06:14.530> if<00:06:14.860> we<00:06:15.070> just<00:06:15.340> write<00:06:16.120> out<00:06:16.419> that<00:06:16.450> moved 00:06:16.860 --> 00:06:16.870 align:start position:0% like if we just write out that moved 00:06:16.870 --> 00:06:19.470 align:start position:0% like if we just write out that moved right<00:06:17.200> normally<00:06:17.680> in<00:06:17.800> JavaScript<00:06:18.340> so<00:06:18.550> if 00:06:19.470 --> 00:06:19.480 align:start position:0% right normally in JavaScript so if 00:06:19.480 --> 00:06:21.150 align:start position:0% right normally in JavaScript so if you're<00:06:19.690> like<00:06:19.840> really<00:06:20.200> desperate<00:06:20.740> you<00:06:20.830> can 00:06:21.150 --> 00:06:21.160 align:start position:0% you're like really desperate you can 00:06:21.160 --> 00:06:22.920 align:start position:0% you're like really desperate you can still<00:06:21.430> use<00:06:21.820> it<00:06:22.000> like<00:06:22.150> this<00:06:22.300> so<00:06:22.480> for<00:06:22.630> example 00:06:22.920 --> 00:06:22.930 align:start position:0% still use it like this so for example 00:06:22.930 --> 00:06:25.560 align:start position:0% still use it like this so for example here<00:06:23.140> used<00:06:23.410> when<00:06:23.710> we're<00:06:23.919> getting<00:06:24.250> like<00:06:24.700> when 00:06:25.560 --> 00:06:25.570 align:start position:0% here used when we're getting like when 00:06:25.570 --> 00:06:27.510 align:start position:0% here used when we're getting like when we're<00:06:25.690> creating<00:06:25.870> web<00:06:26.410> freeze<00:06:26.680> and<00:06:27.040> in<00:06:27.250> what 00:06:27.510 --> 00:06:27.520 align:start position:0% we're creating web freeze and in what 00:06:27.520 --> 00:06:29.250 align:start position:0% we're creating web freeze and in what we're<00:06:27.640> getting<00:06:27.970> the<00:06:28.120> block<00:06:28.330> number<00:06:28.540> it's<00:06:28.930> any 00:06:29.250 --> 00:06:29.260 align:start position:0% we're getting the block number it's any 00:06:29.260 --> 00:06:34.560 align:start position:0% we're getting the block number it's any when<00:06:30.190> we're<00:06:30.669> loading<00:06:32.430> ABI<00:06:33.430> to<00:06:33.850> interact<00:06:34.450> with 00:06:34.560 --> 00:06:34.570 align:start position:0% when we're loading ABI to interact with 00:06:34.570 --> 00:06:38.070 align:start position:0% when we're loading ABI to interact with smart<00:06:35.380> contracts<00:06:35.950> that<00:06:36.130> died<00:06:36.930> contract<00:06:37.930> on 00:06:38.070 --> 00:06:38.080 align:start position:0% smart contracts that died contract on 00:06:38.080 --> 00:06:42.420 align:start position:0% smart contracts that died contract on the<00:06:38.169> magnet<00:06:38.590> it's<00:06:39.010> again<00:06:39.540> any<00:06:40.540> and<00:06:41.310> you<00:06:42.310> know 00:06:42.420 --> 00:06:42.430 align:start position:0% the magnet it's again any and you know 00:06:42.430 --> 00:06:45.180 align:start position:0% the magnet it's again any and you know everything<00:06:43.120> is<00:06:43.240> any<00:06:43.690> like<00:06:44.080> you<00:06:44.560> do<00:06:45.010> in 00:06:45.180 --> 00:06:45.190 align:start position:0% everything is any like you do in 00:06:45.190 --> 00:06:49.080 align:start position:0% everything is any like you do in JavaScript<00:06:45.790> so<00:06:47.010> some<00:06:48.010> people<00:06:48.280> are<00:06:48.400> happy<00:06:48.910> with 00:06:49.080 --> 00:06:49.090 align:start position:0% JavaScript so some people are happy with 00:06:49.090 --> 00:06:49.640 align:start position:0% JavaScript so some people are happy with this 00:06:49.640 --> 00:06:49.650 align:start position:0% this 00:06:49.650 --> 00:06:53.210 align:start position:0% this but<00:06:50.220> basically<00:06:50.610> this<00:06:51.320> like<00:06:52.320> active<00:06:52.889> in<00:06:53.040> this 00:06:53.210 --> 00:06:53.220 align:start position:0% but basically this like active in this 00:06:53.220 --> 00:06:55.430 align:start position:0% but basically this like active in this case<00:06:53.430> doesn't<00:06:53.850> have<00:06:54.000> a<00:06:54.030> stuff<00:06:54.510> much<00:06:54.780> like<00:06:55.020> you 00:06:55.430 --> 00:06:55.440 align:start position:0% case doesn't have a stuff much like you 00:06:55.440 --> 00:06:58.040 align:start position:0% case doesn't have a stuff much like you know<00:06:55.560> it's<00:06:55.979> there<00:06:56.220> but<00:06:56.550> when<00:06:57.479> interacting 00:06:58.040 --> 00:06:58.050 align:start position:0% know it's there but when interacting 00:06:58.050 --> 00:07:01.550 align:start position:0% know it's there but when interacting with<00:06:58.530> doctrine<00:06:58.949> it's<00:06:59.130> a<00:06:59.310> dime<00:06:59.669> so<00:07:00.419> the<00:07:01.290> easiest 00:07:01.550 --> 00:07:01.560 align:start position:0% with doctrine it's a dime so the easiest 00:07:01.560 --> 00:07:04.760 align:start position:0% with doctrine it's a dime so the easiest approach<00:07:01.770> here<00:07:02.280> is<00:07:02.430> to<00:07:02.520> load<00:07:03.440> typing<00:07:04.440> so 00:07:04.760 --> 00:07:04.770 align:start position:0% approach here is to load typing so 00:07:04.770 --> 00:07:07.370 align:start position:0% approach here is to load typing so Taipings<00:07:05.250> is<00:07:05.699> just<00:07:06.150> like<00:07:06.300> external<00:07:06.810> type 00:07:07.370 --> 00:07:07.380 align:start position:0% Taipings is just like external type 00:07:07.380 --> 00:07:08.930 align:start position:0% Taipings is just like external type information<00:07:07.770> that<00:07:08.250> was<00:07:08.370> provided<00:07:08.639> by 00:07:08.930 --> 00:07:08.940 align:start position:0% information that was provided by 00:07:08.940 --> 00:07:11.360 align:start position:0% information that was provided by community<00:07:09.540> usually<00:07:09.660> and<00:07:10.169> it<00:07:10.710> just<00:07:10.949> provides 00:07:11.360 --> 00:07:11.370 align:start position:0% community usually and it just provides 00:07:11.370 --> 00:07:16.610 align:start position:0% community usually and it just provides this<00:07:12.169> information<00:07:13.169> for<00:07:14.160> library<00:07:15.350> written<00:07:16.350> in 00:07:16.610 --> 00:07:16.620 align:start position:0% this information for library written in 00:07:16.620 --> 00:07:19.159 align:start position:0% this information for library written in JavaScript<00:07:17.190> and<00:07:17.580> there<00:07:17.850> are<00:07:17.940> typing<00:07:18.419> for<00:07:18.750> web 00:07:19.159 --> 00:07:19.169 align:start position:0% JavaScript and there are typing for web 00:07:19.169 --> 00:07:27.010 align:start position:0% JavaScript and there are typing for web free<00:07:20.240> usually<00:07:21.240> you<00:07:21.510> would<00:07:22.880> inside<00:07:23.880> by<00:07:24.380> our 00:07:27.010 --> 00:07:27.020 align:start position:0% free usually you would inside by our 00:07:27.020 --> 00:07:32.540 align:start position:0% free usually you would inside by our types<00:07:28.340> window<00:07:29.449> we're<00:07:30.449> free<00:07:30.860> but<00:07:31.860> we<00:07:32.340> don't 00:07:32.540 --> 00:07:32.550 align:start position:0% types window we're free but we don't 00:07:32.550 --> 00:07:35.170 align:start position:0% types window we're free but we don't have<00:07:32.639> internet<00:07:32.910> connections<00:07:33.600> I<00:07:33.750> can<00:07:34.260> adjust 00:07:35.170 --> 00:07:35.180 align:start position:0% have internet connections I can adjust 00:07:35.180 --> 00:07:38.480 align:start position:0% have internet connections I can adjust again<00:07:36.180> actually<00:07:36.810> that<00:07:36.960> they<00:07:37.080> did<00:07:37.350> before<00:07:38.190> the 00:07:38.480 --> 00:07:38.490 align:start position:0% again actually that they did before the 00:07:38.490 --> 00:07:43.879 align:start position:0% again actually that they did before the stop<00:07:40.460> and<00:07:41.460> now<00:07:42.419> each<00:07:42.660> change<00:07:43.080> in<00:07:43.169> the<00:07:43.380> code<00:07:43.590> is 00:07:43.879 --> 00:07:43.889 align:start position:0% stop and now each change in the code is 00:07:43.889 --> 00:07:46.430 align:start position:0% stop and now each change in the code is that<00:07:43.919> the<00:07:44.729> way<00:07:44.940> that<00:07:45.240> we<00:07:45.419> import<00:07:45.900> library 00:07:46.430 --> 00:07:46.440 align:start position:0% that the way that we import library 00:07:46.440 --> 00:07:50.120 align:start position:0% that the way that we import library instead<00:07:46.949> of<00:07:47.100> using<00:07:47.250> require<00:07:47.760> use<00:07:48.150> es6<00:07:49.130> style 00:07:50.120 --> 00:07:50.130 align:start position:0% instead of using require use es6 style 00:07:50.130 --> 00:07:53.469 align:start position:0% instead of using require use es6 style imports<00:07:50.639> and<00:07:50.850> then<00:07:51.360> suddenly<00:07:51.990> our<00:07:52.350> code<00:07:52.710> is 00:07:53.469 --> 00:07:53.479 align:start position:0% imports and then suddenly our code is 00:07:53.479 --> 00:07:55.310 align:start position:0% imports and then suddenly our code is properly<00:07:54.479> tight 00:07:55.310 --> 00:07:55.320 align:start position:0% properly tight 00:07:55.320 --> 00:07:59.770 align:start position:0% properly tight oh<00:07:55.580> so<00:07:56.580> the<00:07:57.360> web<00:07:57.539> free<00:07:57.810> is<00:07:58.139> properly<00:07:58.770> typed<00:07:59.130> we 00:07:59.770 --> 00:07:59.780 align:start position:0% oh so the web free is properly typed we 00:07:59.780 --> 00:08:03.260 align:start position:0% oh so the web free is properly typed we see<00:08:00.780> that<00:08:01.020> the<00:08:01.139> block<00:08:01.349> number<00:08:01.560> is<00:08:01.860> not<00:08:02.729> number 00:08:03.260 --> 00:08:03.270 align:start position:0% see that the block number is not number 00:08:03.270 --> 00:08:07.839 align:start position:0% see that the block number is not number as<00:08:04.080> we<00:08:04.229> expected<00:08:04.800> we<00:08:05.070> get<00:08:05.400> like<00:08:06.590> normal 00:08:07.839 --> 00:08:07.849 align:start position:0% as we expected we get like normal 00:08:07.849 --> 00:08:10.520 align:start position:0% as we expected we get like normal competition<00:08:08.849> and<00:08:09.539> so<00:08:09.720> on<00:08:09.870> and<00:08:09.990> so<00:08:10.139> on 00:08:10.520 --> 00:08:10.530 align:start position:0% competition and so on and so on 00:08:10.530 --> 00:08:14.779 align:start position:0% competition and so on and so on but<00:08:11.190> when<00:08:11.880> we<00:08:12.090> interact<00:08:12.570> with<00:08:12.660> a<00:08:13.789> contract 00:08:14.779 --> 00:08:14.789 align:start position:0% but when we interact with a contract 00:08:14.789 --> 00:08:17.350 align:start position:0% but when we interact with a contract because<00:08:14.970> of<00:08:15.180> the<00:08:15.479> main<00:08:16.080> that<00:08:16.320> with<00:08:16.950> all<00:08:17.099> this 00:08:17.350 --> 00:08:17.360 align:start position:0% because of the main that with all this 00:08:17.360 --> 00:08:20.960 align:start position:0% because of the main that with all this we<00:08:18.360> love<00:08:18.510> this<00:08:19.070> API<00:08:20.070> on<00:08:20.250> the<00:08:20.400> fight<00:08:20.610> the 00:08:20.960 --> 00:08:20.970 align:start position:0% we love this API on the fight the 00:08:20.970 --> 00:08:24.050 align:start position:0% we love this API on the fight the support<00:08:21.330> of<00:08:21.479> it<00:08:21.660> it<00:08:22.229> was<00:08:22.410> really<00:08:23.060> this 00:08:24.050 --> 00:08:24.060 align:start position:0% support of it it was really this 00:08:24.060 --> 00:08:27.020 align:start position:0% support of it it was really this contract<00:08:24.840> is<00:08:25.199> is<00:08:25.710> the<00:08:25.919> dynamic<00:08:26.490> structure 00:08:27.020 --> 00:08:27.030 align:start position:0% contract is is the dynamic structure 00:08:27.030 --> 00:08:29.689 align:start position:0% contract is is the dynamic structure changes<00:08:27.870> you<00:08:28.349> know<00:08:28.500> depending<00:08:29.160> of<00:08:29.280> the<00:08:29.370> API 00:08:29.689 --> 00:08:29.699 align:start position:0% changes you know depending of the API 00:08:29.699 --> 00:08:32.860 align:start position:0% changes you know depending of the API that<00:08:29.789> you<00:08:30.120> love<00:08:30.270> so<00:08:30.930> in<00:08:31.080> this<00:08:31.229> case<00:08:31.640> so 00:08:32.860 --> 00:08:32.870 align:start position:0% that you love so in this case so 00:08:32.870 --> 00:08:36.350 align:start position:0% that you love so in this case so basically<00:08:33.870> this<00:08:34.110> metals<00:08:34.620> are<00:08:34.830> like<00:08:35.099> I've<00:08:35.490> only 00:08:36.350 --> 00:08:36.360 align:start position:0% basically this metals are like I've only 00:08:36.360 --> 00:08:38.839 align:start position:0% basically this metals are like I've only a<00:08:36.599> little<00:08:36.810> bit<00:08:37.080> right<00:08:37.260> like<00:08:37.560> see<00:08:37.860> you<00:08:38.400> see<00:08:38.610> here 00:08:38.839 --> 00:08:38.849 align:start position:0% a little bit right like see you see here 00:08:38.849 --> 00:08:41.180 align:start position:0% a little bit right like see you see here the<00:08:39.029> balance<00:08:39.270> of<00:08:39.630> his<00:08:39.750> type<00:08:40.020> has<00:08:40.320> just<00:08:40.800> take 00:08:41.180 --> 00:08:41.190 align:start position:0% the balance of his type has just take 00:08:41.190 --> 00:08:43.370 align:start position:0% the balance of his type has just take some<00:08:41.459> arguments<00:08:42.089> the<00:08:42.209> area<00:08:42.570> of<00:08:42.719> argument<00:08:43.229> so 00:08:43.370 --> 00:08:43.380 align:start position:0% some arguments the area of argument so 00:08:43.380 --> 00:08:45.980 align:start position:0% some arguments the area of argument so it's<00:08:43.529> not<00:08:43.650> read<00:08:43.919> properly<00:08:44.339> type<00:08:44.790> and<00:08:45.060> return 00:08:45.980 --> 00:08:45.990 align:start position:0% it's not read properly type and return 00:08:45.990 --> 00:08:47.140 align:start position:0% it's not read properly type and return type<00:08:46.470> is<00:08:46.680> a 00:08:47.140 --> 00:08:47.150 align:start position:0% type is a 00:08:47.150 --> 00:08:50.320 align:start position:0% type is a any<00:08:47.480> which<00:08:48.050> in<00:08:48.290> fact<00:08:48.470> is<00:08:48.710> pick<00:08:49.010> number<00:08:49.430> so<00:08:49.850> you 00:08:50.320 --> 00:08:50.330 align:start position:0% any which in fact is pick number so you 00:08:50.330 --> 00:08:52.030 align:start position:0% any which in fact is pick number so you know<00:08:50.420> it's<00:08:50.660> also<00:08:50.839> it<00:08:51.230> would<00:08:51.380> be<00:08:51.529> cool<00:08:51.710> if<00:08:51.890> it 00:08:52.030 --> 00:08:52.040 align:start position:0% know it's also it would be cool if it 00:08:52.040 --> 00:08:54.190 align:start position:0% know it's also it would be cool if it will<00:08:52.460> say<00:08:52.730> to<00:08:53.120> us<00:08:53.240> that<00:08:53.270> it's<00:08:53.690> big<00:08:53.870> number 00:08:54.190 --> 00:08:54.200 align:start position:0% will say to us that it's big number 00:08:54.200 --> 00:08:56.470 align:start position:0% will say to us that it's big number because<00:08:54.529> people<00:08:54.860> are<00:08:54.950> often<00:08:55.580> thinking<00:08:56.150> that 00:08:56.470 --> 00:08:56.480 align:start position:0% because people are often thinking that 00:08:56.480 --> 00:08:58.780 align:start position:0% because people are often thinking that it's<00:08:56.660> just<00:08:56.750> number<00:08:57.290> and<00:08:57.529> try<00:08:57.710> to<00:08:57.770> I<00:08:58.279> don't<00:08:58.460> know 00:08:58.780 --> 00:08:58.790 align:start position:0% it's just number and try to I don't know 00:08:58.790 --> 00:09:01.480 align:start position:0% it's just number and try to I don't know use<00:08:59.029> fast<00:08:59.360> on<00:08:59.570> it<00:08:59.690> and<00:08:59.960> they<00:09:00.110> just<00:09:00.310> get<00:09:01.310> an 00:09:01.480 --> 00:09:01.490 align:start position:0% use fast on it and they just get an 00:09:01.490 --> 00:09:05.200 align:start position:0% use fast on it and they just get an urgent<00:09:02.089> runtime<00:09:02.660> which<00:09:03.290> sucks<00:09:03.890> so<00:09:04.610> how<00:09:04.970> do<00:09:05.029> we 00:09:05.200 --> 00:09:05.210 align:start position:0% urgent runtime which sucks so how do we 00:09:05.210 --> 00:09:10.780 align:start position:0% urgent runtime which sucks so how do we fix<00:09:05.750> this<00:09:08.620> so<00:09:09.620> so<00:09:09.920> thank<00:09:10.250> you<00:09:10.370> says<00:09:10.610> this 00:09:10.780 --> 00:09:10.790 align:start position:0% fix this so so thank you says this 00:09:10.790 --> 00:09:13.630 align:start position:0% fix this so so thank you says this limitation<00:09:11.270> like<00:09:11.600> it<00:09:12.020> lacks<00:09:12.440> API<00:09:13.040> changes<00:09:13.490> as 00:09:13.630 --> 00:09:13.640 align:start position:0% limitation like it lacks API changes as 00:09:13.640 --> 00:09:15.970 align:start position:0% limitation like it lacks API changes as well<00:09:13.820> so<00:09:14.089> if<00:09:14.360> if<00:09:14.660> there's<00:09:14.960> a<00:09:15.020> change<00:09:15.350> to<00:09:15.560> web<00:09:15.710> P 00:09:15.970 --> 00:09:15.980 align:start position:0% well so if if there's a change to web P 00:09:15.980 --> 00:09:19.300 align:start position:0% well so if if there's a change to web P yes<00:09:16.700> like<00:09:17.690> freedom<00:09:18.140> tie<00:09:18.529> things<00:09:18.800> needs<00:09:19.070> to<00:09:19.190> be 00:09:19.300 --> 00:09:19.310 align:start position:0% yes like freedom tie things needs to be 00:09:19.310 --> 00:09:21.790 align:start position:0% yes like freedom tie things needs to be changed<00:09:19.850> by<00:09:20.660> someone<00:09:21.110> like<00:09:21.140> that 00:09:21.790 --> 00:09:21.800 align:start position:0% changed by someone like that 00:09:21.800 --> 00:09:24.040 align:start position:0% changed by someone like that and<00:09:22.070> as<00:09:22.640> mentioned<00:09:23.000> before<00:09:23.270> it<00:09:23.540> doesn't<00:09:23.930> work 00:09:24.040 --> 00:09:24.050 align:start position:0% and as mentioned before it doesn't work 00:09:24.050 --> 00:09:26.530 align:start position:0% and as mentioned before it doesn't work with<00:09:24.230> the<00:09:24.320> dynamic<00:09:24.500> interfaces<00:09:25.460> I<00:09:25.610> love<00:09:26.089> API 00:09:26.530 --> 00:09:26.540 align:start position:0% with the dynamic interfaces I love API 00:09:26.540 --> 00:09:29.320 align:start position:0% with the dynamic interfaces I love API and<00:09:26.960> them<00:09:27.200> that<00:09:27.440> and<00:09:27.680> we<00:09:28.070> generator<00:09:28.520> a<00:09:28.670> wrapper 00:09:29.320 --> 00:09:29.330 align:start position:0% and them that and we generator a wrapper 00:09:29.330 --> 00:09:31.269 align:start position:0% and them that and we generator a wrapper on<00:09:29.540> the<00:09:29.690> fly<00:09:29.870> during<00:09:30.140> the<00:09:30.380> round<00:09:30.560> there<00:09:30.770> so<00:09:30.980> so 00:09:31.269 --> 00:09:31.279 align:start position:0% on the fly during the round there so so 00:09:31.279 --> 00:09:33.730 align:start position:0% on the fly during the round there so so it's<00:09:31.490> impossible<00:09:31.790> to<00:09:32.120> type<00:09:32.560> solution<00:09:33.560> for 00:09:33.730 --> 00:09:33.740 align:start position:0% it's impossible to type solution for 00:09:33.740 --> 00:09:35.769 align:start position:0% it's impossible to type solution for this<00:09:33.890> problem<00:09:34.040> is<00:09:34.520> to<00:09:34.550> generate<00:09:35.210> type<00:09:35.510> things 00:09:35.769 --> 00:09:35.779 align:start position:0% this problem is to generate type things 00:09:35.779 --> 00:09:38.110 align:start position:0% this problem is to generate type things from<00:09:35.930> the<00:09:36.050> sky<00:09:36.230> so<00:09:36.580> basically<00:09:37.580> we<00:09:37.730> can<00:09:37.880> gather 00:09:38.110 --> 00:09:38.120 align:start position:0% from the sky so basically we can gather 00:09:38.120 --> 00:09:42.519 align:start position:0% from the sky so basically we can gather API<00:09:39.110> files<00:09:39.470> from<00:09:40.010> our<00:09:40.190> project<00:09:41.140> project<00:09:42.140> up 00:09:42.519 --> 00:09:42.529 align:start position:0% API files from our project project up 00:09:42.529 --> 00:09:45.370 align:start position:0% API files from our project project up front<00:09:42.800> before<00:09:43.700> combining<00:09:44.570> it<00:09:44.720> with<00:09:44.750> active 00:09:45.370 --> 00:09:45.380 align:start position:0% front before combining it with active 00:09:45.380 --> 00:09:45.880 align:start position:0% front before combining it with active Kamiya 00:09:45.880 --> 00:09:45.890 align:start position:0% Kamiya 00:09:45.890 --> 00:09:47.980 align:start position:0% Kamiya and<00:09:46.100> in<00:09:46.610> the<00:09:46.730> separate<00:09:47.060> bits<00:09:47.420> that<00:09:47.660> just 00:09:47.980 --> 00:09:47.990 align:start position:0% and in the separate bits that just 00:09:47.990 --> 00:09:52.170 align:start position:0% and in the separate bits that just generate<00:09:48.560> this<00:09:48.920> these<00:09:49.820> typing<00:09:50.690> type<00:09:50.930> typing 00:09:52.170 --> 00:09:52.180 align:start position:0% generate this these typing type typing 00:09:52.180 --> 00:09:55.600 align:start position:0% generate this these typing type typing so<00:09:53.180> basic<00:09:53.540> it<00:09:53.720> ETS<00:09:54.350> files<00:09:54.740> and<00:09:55.100> this<00:09:55.459> is 00:09:55.600 --> 00:09:55.610 align:start position:0% so basic it ETS files and this is 00:09:55.610 --> 00:09:59.440 align:start position:0% so basic it ETS files and this is exactly<00:09:55.790> what<00:09:56.180> type<00:09:57.080> China<00:09:57.560> does<00:09:58.070> so<00:09:58.640> another 00:09:59.440 --> 00:09:59.450 align:start position:0% exactly what type China does so another 00:09:59.450 --> 00:10:02.079 align:start position:0% exactly what type China does so another twist<00:09:59.839> here<00:10:00.080> is<00:10:00.290> that<00:10:00.650> we<00:10:01.550> need<00:10:01.700> to<00:10:01.880> generate 00:10:02.079 --> 00:10:02.089 align:start position:0% twist here is that we need to generate 00:10:02.089 --> 00:10:06.670 align:start position:0% twist here is that we need to generate typing<00:10:03.050> specific<00:10:03.740> to<00:10:03.980> the<00:10:04.130> web<00:10:04.700> 3<00:10:05.680> like 00:10:06.670 --> 00:10:06.680 align:start position:0% typing specific to the web 3 like 00:10:06.680 --> 00:10:08.860 align:start position:0% typing specific to the web 3 like blockchain<00:10:07.370> access<00:10:07.820> libraries<00:10:08.330> of<00:10:08.510> people 00:10:08.860 --> 00:10:08.870 align:start position:0% blockchain access libraries of people 00:10:08.870 --> 00:10:14.440 align:start position:0% blockchain access libraries of people using<00:10:09.050> web<00:10:09.410> 3<00:10:09.790> is<00:10:12.130> the<00:10:13.130> API<00:10:13.790> of<00:10:14.029> a<00:10:14.150> smart 00:10:14.440 --> 00:10:14.450 align:start position:0% using web 3 is the API of a smart 00:10:14.450 --> 00:10:17.140 align:start position:0% using web 3 is the API of a smart contract<00:10:14.870> a<00:10:15.470> wrapper<00:10:15.620> is<00:10:15.830> society<00:10:16.730> different 00:10:17.140 --> 00:10:17.150 align:start position:0% contract a wrapper is society different 00:10:17.150 --> 00:10:19.570 align:start position:0% contract a wrapper is society different than<00:10:17.330> from<00:10:17.630> others<00:10:18.140> or<00:10:18.410> from<00:10:18.740> truffle<00:10:19.400> and 00:10:19.570 --> 00:10:19.580 align:start position:0% than from others or from truffle and 00:10:19.580 --> 00:10:22.210 align:start position:0% than from others or from truffle and Samsung<00:10:20.180> so<00:10:20.660> basically<00:10:20.990> type<00:10:21.560> chain<00:10:21.830> gathers 00:10:22.210 --> 00:10:22.220 align:start position:0% Samsung so basically type chain gathers 00:10:22.220 --> 00:10:24.930 align:start position:0% Samsung so basically type chain gathers are<00:10:22.459> like<00:10:22.700> the<00:10:22.910> eyes<00:10:22.940> gathers<00:10:23.870> like<00:10:24.020> the 00:10:24.930 --> 00:10:24.940 align:start position:0% are like the eyes gathers like the 00:10:24.940 --> 00:10:27.130 align:start position:0% are like the eyes gathers like the target<00:10:25.940> that<00:10:26.180> you<00:10:26.360> want<00:10:26.510> to<00:10:26.630> use<00:10:26.779> so<00:10:26.990> for 00:10:27.130 --> 00:10:27.140 align:start position:0% target that you want to use so for 00:10:27.140 --> 00:10:30.160 align:start position:0% target that you want to use so for example<00:10:27.529> a<00:10:27.740> spider<00:10:28.010> to<00:10:28.279> use<00:10:28.850> enters<00:10:29.360> and<00:10:29.990> it 00:10:30.160 --> 00:10:30.170 align:start position:0% example a spider to use enters and it 00:10:30.170 --> 00:10:35.190 align:start position:0% example a spider to use enters and it generates<00:10:30.650> the<00:10:31.040> these<00:10:31.880> GPS<00:10:32.630> files<00:10:33.080> for<00:10:33.470> you<00:10:33.670> so 00:10:35.190 --> 00:10:35.200 align:start position:0% generates the these GPS files for you so 00:10:35.200 --> 00:10:39.510 align:start position:0% generates the these GPS files for you so let<00:10:36.200> me<00:10:36.230> let<00:10:37.190> me<00:10:37.220> show<00:10:37.400> you<00:10:37.640> how<00:10:38.180> this<00:10:38.360> works<00:10:38.570> so 00:10:39.510 --> 00:10:39.520 align:start position:0% let me let me show you how this works so 00:10:39.520 --> 00:10:44.230 align:start position:0% let me let me show you how this works so again<00:10:40.520> we<00:10:40.730> will<00:10:40.910> just<00:10:41.270> do<00:10:41.600> young<00:10:42.880> type<00:10:43.880> train 00:10:44.230 --> 00:10:44.240 align:start position:0% again we will just do young type train 00:10:44.240 --> 00:10:47.610 align:start position:0% again we will just do young type train and<00:10:44.779> a<00:10:45.529> specific<00:10:46.279> target<00:10:46.730> so<00:10:46.940> in<00:10:47.120> this<00:10:47.270> case 00:10:47.610 --> 00:10:47.620 align:start position:0% and a specific target so in this case 00:10:47.620 --> 00:10:51.950 align:start position:0% and a specific target so in this case we<00:10:47.740> want<00:10:48.279> to<00:10:48.460> lock<00:10:49.180> target<00:10:49.600> of<00:10:50.140> wet<00:10:50.650> dream 00:10:51.950 --> 00:10:51.960 align:start position:0% we want to lock target of wet dream 00:10:51.960 --> 00:10:57.829 align:start position:0% we want to lock target of wet dream because<00:10:52.960> reusing<00:10:53.500> web<00:10:53.740> 3<00:10:53.980> now<00:10:54.130> matters<00:10:54.550> and 00:10:57.829 --> 00:10:57.839 align:start position:0% 00:10:57.839 --> 00:11:00.840 align:start position:0% and<00:10:58.839> then<00:10:59.230> this<00:10:59.650> is<00:10:59.740> a<00:10:59.770> see<00:11:00.010> a<00:11:00.040> title<00:11:00.520> that<00:11:00.700> you 00:11:00.840 --> 00:11:00.850 align:start position:0% and then this is a see a title that you 00:11:00.850 --> 00:11:03.210 align:start position:0% and then this is a see a title that you could<00:11:01.000> you<00:11:01.270> know<00:11:01.390> made<00:11:01.660> like<00:11:01.900> a<00:11:01.930> post<00:11:02.320> post 00:11:03.210 --> 00:11:03.220 align:start position:0% could you know made like a post post 00:11:03.220 --> 00:11:05.790 align:start position:0% could you know made like a post post insta<00:11:03.760> hook<00:11:04.029> or<00:11:04.360> anything<00:11:04.839> but<00:11:05.170> here<00:11:05.620> we<00:11:05.770> just 00:11:05.790 --> 00:11:05.800 align:start position:0% insta hook or anything but here we just 00:11:05.800 --> 00:11:08.910 align:start position:0% insta hook or anything but here we just go<00:11:06.100> around<00:11:06.250> it<00:11:06.690> directly<00:11:07.690> so<00:11:08.020> as<00:11:08.529> you<00:11:08.710> can<00:11:08.860> see 00:11:08.910 --> 00:11:08.920 align:start position:0% go around it directly so as you can see 00:11:08.920 --> 00:11:09.960 align:start position:0% go around it directly so as you can see it<00:11:09.160> let<00:11:09.370> me<00:11:09.460> go 00:11:09.960 --> 00:11:09.970 align:start position:0% it let me go 00:11:09.970 --> 00:11:13.920 align:start position:0% it let me go so<00:11:10.839> basically<00:11:11.260> you<00:11:12.160> specify<00:11:12.940> the<00:11:13.000> target<00:11:13.300> as<00:11:13.810> I 00:11:13.920 --> 00:11:13.930 align:start position:0% so basically you specify the target as I 00:11:13.930 --> 00:11:17.250 align:start position:0% so basically you specify the target as I mentioned<00:11:14.290> can<00:11:14.650> you<00:11:14.740> see<00:11:15.540> okay 00:11:17.250 --> 00:11:17.260 align:start position:0% mentioned can you see okay 00:11:17.260 --> 00:11:20.510 align:start position:0% mentioned can you see okay you<00:11:17.620> specify<00:11:17.860> target<00:11:18.670> and<00:11:18.910> we<00:11:19.029> specify<00:11:19.540> the 00:11:20.510 --> 00:11:20.520 align:start position:0% you specify target and we specify the 00:11:20.520 --> 00:11:23.579 align:start position:0% you specify target and we specify the API<00:11:21.520> files<00:11:21.820> in<00:11:22.510> this<00:11:22.690> case<00:11:22.750> it's<00:11:23.140> just<00:11:23.230> one 00:11:23.579 --> 00:11:23.589 align:start position:0% API files in this case it's just one 00:11:23.589 --> 00:11:25.920 align:start position:0% API files in this case it's just one file<00:11:23.860> but<00:11:23.980> examples<00:11:24.610> about<00:11:24.910> well<00:11:25.390> patterns 00:11:25.920 --> 00:11:25.930 align:start position:0% file but examples about well patterns 00:11:25.930 --> 00:11:28.290 align:start position:0% file but examples about well patterns and<00:11:26.110> so<00:11:26.230> on<00:11:26.260> and<00:11:26.470> so<00:11:26.589> on<00:11:26.710> and<00:11:27.040> basically<00:11:27.790> we<00:11:28.150> can 00:11:28.290 --> 00:11:28.300 align:start position:0% and so on and so on and basically we can 00:11:28.300 --> 00:11:30.600 align:start position:0% and so on and so on and basically we can see<00:11:28.510> that<00:11:28.660> we<00:11:28.810> generated<00:11:29.290> generated<00:11:30.010> some 00:11:30.600 --> 00:11:30.610 align:start position:0% see that we generated generated some 00:11:30.610 --> 00:11:34.230 align:start position:0% see that we generated generated some some<00:11:30.970> general<00:11:31.390> types<00:11:31.750> or<00:11:32.080> web<00:11:32.500> 3<00:11:32.770> and<00:11:33.010> ears<00:11:33.610> 20 00:11:34.230 --> 00:11:34.240 align:start position:0% some general types or web 3 and ears 20 00:11:34.240 --> 00:11:40.740 align:start position:0% some general types or web 3 and ears 20 DTS<00:11:35.170> 5<00:11:35.440> and<00:11:37.200> now<00:11:38.200> in<00:11:38.589> called<00:11:39.540> application<00:11:40.540> we 00:11:40.740 --> 00:11:40.750 align:start position:0% DTS 5 and now in called application we 00:11:40.750 --> 00:11:43.560 align:start position:0% DTS 5 and now in called application we need<00:11:40.779> an<00:11:41.080> explicit<00:11:41.860> cast<00:11:42.100> for<00:11:42.760> this<00:11:43.029> interface 00:11:43.560 --> 00:11:43.570 align:start position:0% need an explicit cast for this interface 00:11:43.570 --> 00:11:46.320 align:start position:0% need an explicit cast for this interface that<00:11:44.470> was<00:11:44.920> generated<00:11:45.279> because<00:11:45.550> it's<00:11:45.880> just<00:11:46.120> two 00:11:46.320 --> 00:11:46.330 align:start position:0% that was generated because it's just two 00:11:46.330 --> 00:11:50.790 align:start position:0% that was generated because it's just two possible<00:11:46.750> to<00:11:46.930> to<00:11:47.910> guess<00:11:48.910> that<00:11:49.390> like<00:11:50.110> to<00:11:50.350> make<00:11:50.770> a 00:11:50.790 --> 00:11:50.800 align:start position:0% possible to to guess that like to make a 00:11:50.800 --> 00:11:53.370 align:start position:0% possible to to guess that like to make a connection<00:11:51.730> between<00:11:51.940> the<00:11:52.240> address<00:11:52.930> that<00:11:53.200> can 00:11:53.370 --> 00:11:53.380 align:start position:0% connection between the address that can 00:11:53.380 --> 00:11:55.410 align:start position:0% connection between the address that can be<00:11:53.529> random<00:11:54.100> between<00:11:54.880> the<00:11:55.029> compile<00:11:55.390> time 00:11:55.410 --> 00:11:55.420 align:start position:0% be random between the compile time 00:11:55.420 --> 00:11:58.320 align:start position:0% be random between the compile time working<00:11:56.050> with<00:11:56.560> the<00:11:57.010> typing<00:11:57.400> so<00:11:57.610> here<00:11:57.940> we<00:11:58.120> just 00:11:58.320 --> 00:11:58.330 align:start position:0% working with the typing so here we just 00:11:58.330 --> 00:12:01.680 align:start position:0% working with the typing so here we just need<00:11:58.450> something<00:11:58.930> like<00:11:59.640> this<00:12:00.640> explicit<00:12:01.420> cast 00:12:01.680 --> 00:12:01.690 align:start position:0% need something like this explicit cast 00:12:01.690 --> 00:12:09.090 align:start position:0% need something like this explicit cast and<00:12:03.930> well<00:12:04.930> now<00:12:05.830> that<00:12:06.610> is<00:12:07.000> your<00:12:07.540> ECT<00:12:07.990> 2010<00:12:08.830> and 00:12:09.090 --> 00:12:09.100 align:start position:0% and well now that is your ECT 2010 and 00:12:09.100 --> 00:12:12.090 align:start position:0% and well now that is your ECT 2010 and balance<00:12:10.000> is<00:12:10.410> number<00:12:11.410> as<00:12:11.620> you<00:12:11.830> would<00:12:11.950> expect 00:12:12.090 --> 00:12:12.100 align:start position:0% balance is number as you would expect 00:12:12.100 --> 00:12:20.280 align:start position:0% balance is number as you would expect and<00:12:13.020> we're<00:12:14.020> getting<00:12:14.940> proper<00:12:18.600> proper<00:12:19.600> code 00:12:20.280 --> 00:12:20.290 align:start position:0% and we're getting proper proper code 00:12:20.290 --> 00:12:23.130 align:start position:0% and we're getting proper proper code competition<00:12:20.920> here<00:12:21.190> so<00:12:21.400> these<00:12:21.550> are<00:12:21.610> all<00:12:22.140> here 00:12:23.130 --> 00:12:23.140 align:start position:0% competition here so these are all here 00:12:23.140 --> 00:12:25.800 align:start position:0% competition here so these are all here see<00:12:23.380> plenty<00:12:23.589> plus<00:12:24.070> some<00:12:24.370> others<00:12:24.810> metals 00:12:25.800 --> 00:12:25.810 align:start position:0% see plenty plus some others metals 00:12:25.810 --> 00:12:30.180 align:start position:0% see plenty plus some others metals ductile<00:12:26.580> contracts<00:12:27.580> have<00:12:27.839> passed<00:12:28.839> and<00:12:29.190> as 00:12:30.180 --> 00:12:30.190 align:start position:0% ductile contracts have passed and as 00:12:30.190 --> 00:12:33.079 align:start position:0% ductile contracts have passed and as well<00:12:30.430> as<00:12:31.380> events<00:12:32.380> for<00:12:32.650> me 00:12:33.079 --> 00:12:33.089 align:start position:0% well as events for me 00:12:33.089 --> 00:12:37.459 align:start position:0% well as events for me here<00:12:34.339> yeah<00:12:35.339> so<00:12:35.459> you<00:12:36.059> know<00:12:36.149> he<00:12:36.479> supports<00:12:36.659> events 00:12:37.459 --> 00:12:37.469 align:start position:0% here yeah so you know he supports events 00:12:37.469 --> 00:12:45.499 align:start position:0% here yeah so you know he supports events as<00:12:37.619> well<00:12:41.809> we<00:12:42.809> can<00:12:42.959> also<00:12:43.049> browse<00:12:43.649> this<00:12:44.479> citing 00:12:45.499 --> 00:12:45.509 align:start position:0% as well we can also browse this citing 00:12:45.509 --> 00:12:49.309 align:start position:0% as well we can also browse this citing investor<00:12:46.049> generated<00:12:46.829> so<00:12:47.929> basically<00:12:48.929> you<00:12:49.079> can 00:12:49.309 --> 00:12:49.319 align:start position:0% investor generated so basically you can 00:12:49.319 --> 00:12:51.979 align:start position:0% investor generated so basically you can also<00:12:49.739> see<00:12:50.039> that<00:12:50.069> sometimes<00:12:50.669> it<00:12:51.359> allows<00:12:51.749> us<00:12:51.779> to 00:12:51.979 --> 00:12:51.989 align:start position:0% also see that sometimes it allows us to 00:12:51.989 --> 00:12:54.589 align:start position:0% also see that sometimes it allows us to specify<00:12:52.379> either<00:12:52.799> number<00:12:53.219> or<00:12:53.609> string<00:12:53.879> because 00:12:54.589 --> 00:12:54.599 align:start position:0% specify either number or string because 00:12:54.599 --> 00:12:57.199 align:start position:0% specify either number or string because this<00:12:54.809> is<00:12:54.959> what<00:12:55.139> what<00:12:55.889> free<00:12:56.189> allows<00:12:56.519> us<00:12:56.759> were 00:12:57.199 --> 00:12:57.209 align:start position:0% this is what what free allows us were 00:12:57.209 --> 00:12:58.879 align:start position:0% this is what what free allows us were three<00:12:57.449> players<00:12:57.809> allows<00:12:58.139> us<00:12:58.349> to<00:12:58.499> those<00:12:58.679> also 00:12:58.879 --> 00:12:58.889 align:start position:0% three players allows us to those also 00:12:58.889 --> 00:13:00.439 align:start position:0% three players allows us to those also you<00:12:59.249> know<00:12:59.369> these<00:12:59.579> titles<00:12:59.939> are<00:13:00.119> really 00:13:00.439 --> 00:13:00.449 align:start position:0% you know these titles are really 00:13:00.449 --> 00:13:03.949 align:start position:0% you know these titles are really convenient<00:13:01.289> and<00:13:01.649> they<00:13:02.219> they're<00:13:02.729> like<00:13:03.659> they're 00:13:03.949 --> 00:13:03.959 align:start position:0% convenient and they they're like they're 00:13:03.959 --> 00:13:07.219 align:start position:0% convenient and they they're like they're as<00:13:04.729> open<00:13:05.729> as<00:13:05.879> possible<00:13:05.909> right<00:13:06.509> like<00:13:06.779> if<00:13:07.079> there 00:13:07.219 --> 00:13:07.229 align:start position:0% as open as possible right like if there 00:13:07.229 --> 00:13:08.629 align:start position:0% as open as possible right like if there are<00:13:07.349> some<00:13:07.529> progression<00:13:08.069> happening<00:13:08.459> your 00:13:08.629 --> 00:13:08.639 align:start position:0% are some progression happening your 00:13:08.639 --> 00:13:11.329 align:start position:0% are some progression happening your filter<00:13:08.969> sit<00:13:09.449> here<00:13:09.749> as<00:13:09.869> well<00:13:10.049> so<00:13:10.259> now<00:13:11.069> we<00:13:11.189> don't 00:13:11.329 --> 00:13:11.339 align:start position:0% filter sit here as well so now we don't 00:13:11.339 --> 00:13:13.719 align:start position:0% filter sit here as well so now we don't have<00:13:11.489> to<00:13:11.729> be<00:13:11.819> super<00:13:11.999> strict<00:13:12.419> about<00:13:12.989> something 00:13:13.719 --> 00:13:13.729 align:start position:0% have to be super strict about something 00:13:13.729 --> 00:13:21.409 align:start position:0% have to be super strict about something okay<00:13:15.739> so<00:13:16.739> in<00:13:17.699> general<00:13:17.969> I<00:13:18.509> train<00:13:20.419> works 00:13:21.409 --> 00:13:21.419 align:start position:0% okay so in general I train works 00:13:21.419 --> 00:13:24.049 align:start position:0% okay so in general I train works perfectly<00:13:22.169> with<00:13:22.349> any<00:13:22.559> idea<00:13:23.009> if<00:13:23.489> your<00:13:23.729> IDE 00:13:24.049 --> 00:13:24.059 align:start position:0% perfectly with any idea if your IDE 00:13:24.059 --> 00:13:26.839 align:start position:0% perfectly with any idea if your IDE supports<00:13:24.749> typescript<00:13:25.409> it<00:13:25.619> supports<00:13:26.129> type 00:13:26.839 --> 00:13:26.849 align:start position:0% supports typescript it supports type 00:13:26.849 --> 00:13:31.809 align:start position:0% supports typescript it supports type change<00:13:27.149> generated<00:13:27.629> wrappers<00:13:29.359> it<00:13:30.469> supports 00:13:31.809 --> 00:13:31.819 align:start position:0% change generated wrappers it supports 00:13:31.819 --> 00:13:35.119 align:start position:0% change generated wrappers it supports officially<00:13:32.819> free<00:13:33.689> different<00:13:34.499> targets<00:13:34.919> so 00:13:35.119 --> 00:13:35.129 align:start position:0% officially free different targets so 00:13:35.129 --> 00:13:38.809 align:start position:0% officially free different targets so it's<00:13:35.309> web<00:13:36.059> free<00:13:36.389> the<00:13:36.749> one<00:13:36.899> point<00:13:37.199> that<00:13:37.819> at 00:13:38.809 --> 00:13:38.819 align:start position:0% it's web free the one point that at 00:13:38.819 --> 00:13:39.469 align:start position:0% it's web free the one point that at Thursday's 00:13:39.469 --> 00:13:39.479 align:start position:0% Thursday's 00:13:39.479 --> 00:13:44.169 align:start position:0% Thursday's and<00:13:39.719> travel<00:13:41.639> it<00:13:41.909> supports<00:13:42.359> custom<00:13:42.629> targets<00:13:43.319> so 00:13:44.169 --> 00:13:44.179 align:start position:0% and travel it supports custom targets so 00:13:44.179 --> 00:13:46.909 align:start position:0% and travel it supports custom targets so what<00:13:45.179> you<00:13:45.359> like<00:13:45.989> for<00:13:46.139> example<00:13:46.259> imagine<00:13:46.709> that 00:13:46.909 --> 00:13:46.919 align:start position:0% what you like for example imagine that 00:13:46.919 --> 00:13:48.709 align:start position:0% what you like for example imagine that you're<00:13:47.159> not<00:13:47.309> developing<00:13:47.549> it<00:13:47.939> down<00:13:48.209> you're 00:13:48.709 --> 00:13:48.719 align:start position:0% you're not developing it down you're 00:13:48.719 --> 00:13:51.529 align:start position:0% you're not developing it down you're developing<00:13:49.019> like<00:13:49.549> protocol<00:13:50.549> and<00:13:50.789> you<00:13:51.209> want<00:13:51.389> to 00:13:51.529 --> 00:13:51.539 align:start position:0% developing like protocol and you want to 00:13:51.539 --> 00:13:56.629 align:start position:0% developing like protocol and you want to have<00:13:52.639> generated<00:13:53.639> acts<00:13:54.559> generated<00:13:55.559> library<00:13:56.459> to 00:13:56.629 --> 00:13:56.639 align:start position:0% have generated acts generated library to 00:13:56.639 --> 00:13:58.639 align:start position:0% have generated acts generated library to use<00:13:56.789> by<00:13:57.059> different<00:13:57.509> developers<00:13:57.689> and<00:13:58.379> you<00:13:58.469> want 00:13:58.639 --> 00:13:58.649 align:start position:0% use by different developers and you want 00:13:58.649 --> 00:14:00.439 align:start position:0% use by different developers and you want to<00:13:58.769> you<00:13:58.859> know<00:13:59.009> have<00:13:59.489> come<00:13:59.939> up<00:14:00.089> with<00:14:00.119> your<00:14:00.419> own 00:14:00.439 --> 00:14:00.449 align:start position:0% to you know have come up with your own 00:14:00.449 --> 00:14:02.899 align:start position:0% to you know have come up with your own interface<00:14:01.049> you<00:14:01.439> know<00:14:01.589> like<00:14:02.249> some<00:14:02.549> metals 00:14:02.899 --> 00:14:02.909 align:start position:0% interface you know like some metals 00:14:02.909 --> 00:14:05.149 align:start position:0% interface you know like some metals whatever<00:14:03.299> you<00:14:03.869> can<00:14:04.019> generated<00:14:04.589> automatically 00:14:05.149 --> 00:14:05.159 align:start position:0% whatever you can generated automatically 00:14:05.159 --> 00:14:07.399 align:start position:0% whatever you can generated automatically by<00:14:05.279> providing<00:14:06.119> here<00:14:06.479> your<00:14:06.719> custom<00:14:07.199> target 00:14:07.399 --> 00:14:07.409 align:start position:0% by providing here your custom target 00:14:07.409 --> 00:14:10.159 align:start position:0% by providing here your custom target which<00:14:07.739> just<00:14:08.009> takes<00:14:08.249> first<00:14:08.789> API<00:14:09.509> and<00:14:09.719> generate 00:14:10.159 --> 00:14:10.169 align:start position:0% which just takes first API and generate 00:14:10.169 --> 00:14:13.069 align:start position:0% which just takes first API and generate some<00:14:10.469> code<00:14:10.799> and<00:14:11.039> by<00:14:11.459> the<00:14:11.519> way<00:14:11.729> can<00:14:12.539> generate 00:14:13.069 --> 00:14:13.079 align:start position:0% some code and by the way can generate 00:14:13.079 --> 00:14:15.229 align:start position:0% some code and by the way can generate even<00:14:13.439> called<00:14:13.739> in<00:14:14.219> different<00:14:14.609> language<00:14:14.969> than 00:14:15.229 --> 00:14:15.239 align:start position:0% even called in different language than 00:14:15.239 --> 00:14:17.689 align:start position:0% even called in different language than type<00:14:15.659> space<00:14:15.989> it's<00:14:16.589> very<00:14:16.799> general<00:14:17.249> interface 00:14:17.689 --> 00:14:17.699 align:start position:0% type space it's very general interface 00:14:17.699 --> 00:14:20.569 align:start position:0% type space it's very general interface and<00:14:18.469> basically<00:14:19.469> then<00:14:19.799> you<00:14:19.829> can<00:14:20.099> just<00:14:20.309> hide 00:14:20.569 --> 00:14:20.579 align:start position:0% and basically then you can just hide 00:14:20.579 --> 00:14:22.909 align:start position:0% and basically then you can just hide implementation<00:14:21.419> details<00:14:21.869> from<00:14:22.349> from<00:14:22.739> the 00:14:22.909 --> 00:14:22.919 align:start position:0% implementation details from from the 00:14:22.919 --> 00:14:25.719 align:start position:0% implementation details from from the users<00:14:23.549> of<00:14:23.729> your<00:14:23.879> library<00:14:24.359> you<00:14:24.779> could<00:14:24.929> swap 00:14:25.719 --> 00:14:25.729 align:start position:0% users of your library you could swap 00:14:25.729 --> 00:14:29.359 align:start position:0% users of your library you could swap internal<00:14:26.729> web<00:14:27.209> 3<00:14:27.569> like<00:14:28.229> about<00:14:28.739> China<00:14:29.009> access 00:14:29.359 --> 00:14:29.369 align:start position:0% internal web 3 like about China access 00:14:29.369 --> 00:14:30.829 align:start position:0% internal web 3 like about China access the<00:14:29.459> library<00:14:29.819> without<00:14:30.149> affecting<00:14:30.719> your 00:14:30.829 --> 00:14:30.839 align:start position:0% the library without affecting your 00:14:30.839 --> 00:14:31.900 align:start position:0% the library without affecting your clients<00:14:31.319> and<00:14:31.439> so<00:14:31.619> on 00:14:31.900 --> 00:14:31.910 align:start position:0% clients and so on 00:14:31.910 --> 00:14:35.440 align:start position:0% clients and so on some<00:14:32.590> patron<00:14:33.590> has<00:14:33.800> full<00:14:34.070> API<00:14:34.520> version<00:14:35.240> to 00:14:35.440 --> 00:14:35.450 align:start position:0% some patron has full API version to 00:14:35.450 --> 00:14:37.660 align:start position:0% some patron has full API version to support<00:14:35.690> so<00:14:36.200> you<00:14:36.290> know<00:14:36.440> things<00:14:36.740> extracts 00:14:37.660 --> 00:14:37.670 align:start position:0% support so you know things extracts 00:14:37.670 --> 00:14:40.210 align:start position:0% support so you know things extracts things<00:14:38.150> like<00:14:38.440> callback<00:14:39.440> functions<00:14:40.040> are 00:14:40.210 --> 00:14:40.220 align:start position:0% things like callback functions are 00:14:40.220 --> 00:14:43.320 align:start position:0% things like callback functions are overrated<00:14:40.780> overridden<00:14:41.780> functions<00:14:42.440> now<00:14:42.800> works 00:14:43.320 --> 00:14:43.330 align:start position:0% overrated overridden functions now works 00:14:43.330 --> 00:14:46.930 align:start position:0% overrated overridden functions now works and<00:14:44.330> I<00:14:44.420> work<00:14:44.630> and<00:14:44.870> it<00:14:45.860> supports<00:14:46.250> events<00:14:46.670> as<00:14:46.790> I 00:14:46.930 --> 00:14:46.940 align:start position:0% and I work and it supports events as I 00:14:46.940 --> 00:14:51.070 align:start position:0% and I work and it supports events as I shown<00:14:47.480> before<00:14:47.720> and<00:14:49.420> what's<00:14:50.420> pretty<00:14:50.570> cool<00:14:50.690> that 00:14:51.070 --> 00:14:51.080 align:start position:0% shown before and what's pretty cool that 00:14:51.080 --> 00:14:55.360 align:start position:0% shown before and what's pretty cool that it<00:14:51.200> works<00:14:51.530> with<00:14:51.740> travel<00:14:52.190> so<00:14:52.520> we<00:14:52.850> can<00:14:53.030> do<00:14:54.370> smart 00:14:55.360 --> 00:14:55.370 align:start position:0% it works with travel so we can do smart 00:14:55.370 --> 00:14:57.670 align:start position:0% it works with travel so we can do smart contract<00:14:55.850> development<00:14:56.360> not<00:14:56.510> top<00:14:56.870> development 00:14:57.670 --> 00:14:57.680 align:start position:0% contract development not top development 00:14:57.680 --> 00:15:03.480 align:start position:0% contract development not top development on<00:14:57.830> me<00:14:57.980> so<00:14:58.870> here<00:14:59.870> I<00:14:59.900> have<00:15:00.440> this<00:15:00.860> example<00:15:01.850> of 00:15:03.480 --> 00:15:03.490 align:start position:0% on me so here I have this example of 00:15:03.490 --> 00:15:09.060 align:start position:0% on me so here I have this example of single<00:15:04.490> cell<00:15:05.420> DD<00:15:05.630> contract<00:15:06.190> it<00:15:07.250> it's<00:15:07.850> like 00:15:09.060 --> 00:15:09.070 align:start position:0% single cell DD contract it it's like 00:15:09.070 --> 00:15:12.040 align:start position:0% single cell DD contract it it's like traffic<00:15:10.070> onto<00:15:10.430> the<00:15:10.640> traffic<00:15:11.150> project<00:15:11.570> or<00:15:11.750> some 00:15:12.040 --> 00:15:12.050 align:start position:0% traffic onto the traffic project or some 00:15:12.050 --> 00:15:15.250 align:start position:0% traffic onto the traffic project or some simple<00:15:12.320> scientific<00:15:13.130> contract<00:15:14.120> of<00:15:14.360> return<00:15:14.960> and 00:15:15.250 --> 00:15:15.260 align:start position:0% simple scientific contract of return and 00:15:15.260 --> 00:15:20.950 align:start position:0% simple scientific contract of return and it<00:15:15.860> has<00:15:16.040> some<00:15:16.840> functions<00:15:17.840> we<00:15:18.350> have<00:15:18.590> some<00:15:19.960> tests 00:15:20.950 --> 00:15:20.960 align:start position:0% it has some functions we have some tests 00:15:20.960 --> 00:15:24.910 align:start position:0% it has some functions we have some tests here<00:15:21.260> and<00:15:22.450> you<00:15:23.450> know<00:15:23.570> it's<00:15:23.900> super<00:15:24.290> nice<00:15:24.530> now<00:15:24.860> to 00:15:24.910 --> 00:15:24.920 align:start position:0% here and you know it's super nice now to 00:15:24.920 --> 00:15:27.370 align:start position:0% here and you know it's super nice now to write<00:15:25.340> this<00:15:25.580> because<00:15:25.970> we<00:15:26.180> have<00:15:26.360> not<00:15:26.540> called 00:15:27.370 --> 00:15:27.380 align:start position:0% write this because we have not called 00:15:27.380 --> 00:15:29.500 align:start position:0% write this because we have not called competitions<00:15:28.070> having<00:15:28.340> them<00:15:28.550> to<00:15:28.760> guess<00:15:29.210> them 00:15:29.500 --> 00:15:29.510 align:start position:0% competitions having them to guess them 00:15:29.510 --> 00:15:32.410 align:start position:0% competitions having them to guess them there<00:15:29.900> that<00:15:30.380> the<00:15:30.530> method<00:15:30.920> name<00:15:31.100> change<00:15:32.090> PI's 00:15:32.410 --> 00:15:32.420 align:start position:0% there that the method name change PI's 00:15:32.420 --> 00:15:36.310 align:start position:0% there that the method name change PI's to<00:15:32.450> do<00:15:33.380> you<00:15:33.440> know<00:15:33.670> be<00:15:34.670> sure<00:15:34.910> what<00:15:35.180> was<00:15:35.990> the<00:15:36.140> name 00:15:36.310 --> 00:15:36.320 align:start position:0% to do you know be sure what was the name 00:15:36.320 --> 00:15:39.940 align:start position:0% to do you know be sure what was the name of<00:15:36.350> the<00:15:36.560> method<00:15:36.710> and<00:15:37.780> what's<00:15:38.780> cool<00:15:39.080> is<00:15:39.350> that<00:15:39.710> if 00:15:39.940 --> 00:15:39.950 align:start position:0% of the method and what's cool is that if 00:15:39.950 --> 00:15:42.310 align:start position:0% of the method and what's cool is that if we<00:15:40.220> introduce<00:15:40.880> a<00:15:41.060> change<00:15:41.090> to<00:15:41.840> the<00:15:42.140> so 00:15:42.310 --> 00:15:42.320 align:start position:0% we introduce a change to the so 00:15:42.320 --> 00:15:43.180 align:start position:0% we introduce a change to the so difficult 00:15:43.180 --> 00:15:43.190 align:start position:0% difficult 00:15:43.190 --> 00:15:46.320 align:start position:0% difficult like<00:15:43.760> let's<00:15:44.030> say<00:15:44.210> we<00:15:44.480> rename<00:15:44.930> say<00:15:45.290> hello<00:15:45.620> to 00:15:46.320 --> 00:15:46.330 align:start position:0% like let's say we rename say hello to 00:15:46.330 --> 00:15:53.800 align:start position:0% like let's say we rename say hello to screen<00:15:47.380> hello<00:15:48.410> and<00:15:49.210> we<00:15:50.260> regenerate<00:15:52.540> or<00:15:53.540> we 00:15:53.800 --> 00:15:53.810 align:start position:0% screen hello and we regenerate or we 00:15:53.810 --> 00:15:57.550 align:start position:0% screen hello and we regenerate or we don't 00:15:57.550 --> 00:15:57.560 align:start position:0% 00:15:57.560 --> 00:16:02.510 align:start position:0% and<00:15:58.560> we<00:15:59.010> originally<00:15:59.550> the<00:16:00.800> rappers<00:16:01.800> we're 00:16:02.510 --> 00:16:02.520 align:start position:0% and we originally the rappers we're 00:16:02.520 --> 00:16:04.970 align:start position:0% and we originally the rappers we're gonna<00:16:02.730> find<00:16:03.800> automatically<00:16:04.800> without 00:16:04.970 --> 00:16:04.980 align:start position:0% gonna find automatically without 00:16:04.980 --> 00:16:07.430 align:start position:0% gonna find automatically without rounding<00:16:05.490> our<00:16:05.820> as<00:16:06.630> we're<00:16:06.930> gonna<00:16:07.170> find 00:16:07.430 --> 00:16:07.440 align:start position:0% rounding our as we're gonna find 00:16:07.440 --> 00:16:10.720 align:start position:0% rounding our as we're gonna find breaking<00:16:07.920> changes<00:16:08.370> so<00:16:08.580> if<00:16:09.210> you<00:16:09.390> do<00:16:09.570> a<00:16:09.870> lot<00:16:10.440> of 00:16:10.720 --> 00:16:10.730 align:start position:0% breaking changes so if you do a lot of 00:16:10.730 --> 00:16:13.400 align:start position:0% breaking changes so if you do a lot of my<00:16:11.730> strength<00:16:12.120> development<00:16:12.420> is<00:16:12.810> just<00:16:13.020> faster 00:16:13.400 --> 00:16:13.410 align:start position:0% my strength development is just faster 00:16:13.410 --> 00:16:16.280 align:start position:0% my strength development is just faster to<00:16:13.620> find<00:16:13.890> breaking<00:16:14.490> terms<00:16:14.760> like<00:16:14.970> this<00:16:15.290> you 00:16:16.280 --> 00:16:16.290 align:start position:0% to find breaking terms like this you 00:16:16.290 --> 00:16:23.450 align:start position:0% to find breaking terms like this you know<00:16:16.380> it<00:16:16.650> just<00:16:16.680> saves<00:16:17.130> a<00:16:17.340> lot<00:16:17.520> of<00:16:17.580> time<00:16:22.130> and<00:16:23.130> by 00:16:23.450 --> 00:16:23.460 align:start position:0% know it just saves a lot of time and by 00:16:23.460 --> 00:16:24.910 align:start position:0% know it just saves a lot of time and by the<00:16:23.490> way<00:16:23.670> is<00:16:23.730> to<00:16:23.940> use<00:16:23.970> something<00:16:24.390> like<00:16:24.540> what 00:16:24.910 --> 00:16:24.920 align:start position:0% the way is to use something like what 00:16:24.920 --> 00:16:30.560 align:start position:0% the way is to use something like what are<00:16:26.840> similar<00:16:27.840> to<00:16:28.350> track<00:16:29.010> but<00:16:29.310> using<00:16:29.670> enters<00:16:30.030> it 00:16:30.560 --> 00:16:30.570 align:start position:0% are similar to track but using enters it 00:16:30.570 --> 00:16:34.190 align:start position:0% are similar to track but using enters it works<00:16:30.780> as<00:16:31.020> well<00:16:32.180> generate<00:16:33.180> better<00:16:33.720> style 00:16:34.190 --> 00:16:34.200 align:start position:0% works as well generate better style 00:16:34.200 --> 00:16:37.670 align:start position:0% works as well generate better style packing<00:16:35.190> so<00:16:35.840> recently<00:16:36.840> it's<00:16:36.990> it's<00:16:37.320> telling 00:16:37.670 --> 00:16:37.680 align:start position:0% packing so recently it's it's telling 00:16:37.680 --> 00:16:40.280 align:start position:0% packing so recently it's it's telling that<00:16:37.710> beat<00:16:38.160> array<00:16:38.520> I<00:16:38.730> started<00:16:39.510> to<00:16:39.810> release<00:16:40.080> it 00:16:40.280 --> 00:16:40.290 align:start position:0% that beat array I started to release it 00:16:40.290 --> 00:16:42.980 align:start position:0% that beat array I started to release it today<00:16:40.620> because<00:16:40.800> it<00:16:41.610> works<00:16:41.850> very<00:16:42.000> well<00:16:42.120> it<00:16:42.840> will 00:16:42.980 --> 00:16:42.990 align:start position:0% today because it works very well it will 00:16:42.990 --> 00:16:44.330 align:start position:0% today because it works very well it will test<00:16:43.140> the<00:16:43.290> deterrent<00:16:43.710> effect<00:16:43.860> of<00:16:44.190> this 00:16:44.330 --> 00:16:44.340 align:start position:0% test the deterrent effect of this 00:16:44.340 --> 00:16:46.280 align:start position:0% test the deterrent effect of this protective<00:16:44.760> access<00:16:45.090> cure<00:16:45.330> unique<00:16:45.780> so 00:16:46.280 --> 00:16:46.290 align:start position:0% protective access cure unique so 00:16:46.290 --> 00:16:49.220 align:start position:0% protective access cure unique so basically<00:16:46.740> actually<00:16:47.250> version<00:16:47.640> 1.0<00:16:48.240> you<00:16:49.020> can 00:16:49.220 --> 00:16:49.230 align:start position:0% basically actually version 1.0 you can 00:16:49.230 --> 00:16:52.160 align:start position:0% basically actually version 1.0 you can see<00:16:49.380> a<00:16:49.410> few<00:16:49.890> new<00:16:50.340> additions<00:16:50.700> so<00:16:51.300> if<00:16:51.870> you<00:16:52.020> use<00:16:52.140> it 00:16:52.160 --> 00:16:52.170 align:start position:0% see a few new additions so if you use it 00:16:52.170 --> 00:16:55.430 align:start position:0% see a few new additions so if you use it before<00:16:52.740> now<00:16:53.010> the<00:16:53.070> targets<00:16:53.970> as<00:16:54.270> are<00:16:54.630> extracted 00:16:55.430 --> 00:16:55.440 align:start position:0% before now the targets as are extracted 00:16:55.440 --> 00:16:57.800 align:start position:0% before now the targets as are extracted as<00:16:55.590> a<00:16:55.620> separate<00:16:56.010> packages<00:16:56.520> which<00:16:56.820> which<00:16:57.150> is 00:16:57.800 --> 00:16:57.810 align:start position:0% as a separate packages which which is 00:16:57.810 --> 00:16:59.660 align:start position:0% as a separate packages which which is much<00:16:58.200> nicer<00:16:58.410> because<00:16:58.770> you<00:16:59.010> can<00:16:59.160> even<00:16:59.400> get<00:16:59.610> your 00:16:59.660 --> 00:16:59.670 align:start position:0% much nicer because you can even get your 00:16:59.670 --> 00:17:02.420 align:start position:0% much nicer because you can even get your own<00:16:59.970> package<00:17:00.300> your<00:17:01.050> own<00:17:01.230> target<00:17:01.710> like<00:17:02.040> without 00:17:02.420 --> 00:17:02.430 align:start position:0% own package your own target like without 00:17:02.430 --> 00:17:05.270 align:start position:0% own package your own target like without you<00:17:02.610> know<00:17:03.110> polluting<00:17:04.110> the<00:17:04.320> types<00:17:04.589> type 00:17:05.270 --> 00:17:05.280 align:start position:0% you know polluting the types type 00:17:05.280 --> 00:17:08.420 align:start position:0% you know polluting the types type trainers<00:17:05.760> are<00:17:05.910> a<00:17:06.000> repository<00:17:06.530> the<00:17:07.530> avi<00:17:07.890> parser 00:17:08.420 --> 00:17:08.430 align:start position:0% trainers are a repository the avi parser 00:17:08.430 --> 00:17:10.220 align:start position:0% trainers are a repository the avi parser is<00:17:08.670> much<00:17:08.880> nicer<00:17:09.150> so<00:17:09.600> you<00:17:09.839> might<00:17:10.020> be<00:17:10.050> wondering 00:17:10.220 --> 00:17:10.230 align:start position:0% is much nicer so you might be wondering 00:17:10.230 --> 00:17:13.340 align:start position:0% is much nicer so you might be wondering why<00:17:11.040> do<00:17:11.100> we<00:17:11.280> have<00:17:11.459> a<00:17:11.640> DI<00:17:11.910> parser<00:17:12.360> at<00:17:12.689> all<00:17:12.870> so 00:17:13.340 --> 00:17:13.350 align:start position:0% why do we have a DI parser at all so 00:17:13.350 --> 00:17:16.699 align:start position:0% why do we have a DI parser at all so basically<00:17:13.709> we<00:17:13.980> can<00:17:14.010> parse<00:17:14.930> you<00:17:15.930> know<00:17:16.050> try<00:17:16.380> some 00:17:16.699 --> 00:17:16.709 align:start position:0% basically we can parse you know try some 00:17:16.709 --> 00:17:21.530 align:start position:0% basically we can parse you know try some styles<00:17:17.520> avi<00:17:17.880> to<00:17:18.709> something<00:17:19.709> type<00:17:20.250> site<00:17:20.550> like 00:17:21.530 --> 00:17:21.540 align:start position:0% styles avi to something type site like 00:17:21.540 --> 00:17:23.689 align:start position:0% styles avi to something type site like discriminated<00:17:22.350> unions<00:17:22.770> in<00:17:23.070> in<00:17:23.339> typescript 00:17:23.689 --> 00:17:23.699 align:start position:0% discriminated unions in in typescript 00:17:23.699 --> 00:17:27.290 align:start position:0% discriminated unions in in typescript winds<00:17:24.329> up<00:17:24.600> writing<00:17:25.500> the<00:17:26.100> the<00:17:26.640> code<00:17:26.880> generation 00:17:27.290 --> 00:17:27.300 align:start position:0% winds up writing the the code generation 00:17:27.300 --> 00:17:29.900 align:start position:0% winds up writing the the code generation part<00:17:27.750> a<00:17:28.050> lot<00:17:28.590> and<00:17:28.920> it<00:17:29.100> just<00:17:29.400> like<00:17:29.610> you<00:17:29.790> know 00:17:29.900 --> 00:17:29.910 align:start position:0% part a lot and it just like you know 00:17:29.910 --> 00:17:32.450 align:start position:0% part a lot and it just like you know less<00:17:30.540> error-prone<00:17:30.930> and<00:17:31.440> basically<00:17:32.250> their 00:17:32.450 --> 00:17:32.460 align:start position:0% less error-prone and basically their 00:17:32.460 --> 00:17:34.160 align:start position:0% less error-prone and basically their architecture<00:17:32.940> of<00:17:33.030> type<00:17:33.240> train<00:17:33.510> now 00:17:34.160 --> 00:17:34.170 align:start position:0% architecture of type train now 00:17:34.170 --> 00:17:36.320 align:start position:0% architecture of type train now reassembles<00:17:35.070> and<00:17:35.340> with<00:17:35.550> the<00:17:35.760> compiler 00:17:36.320 --> 00:17:36.330 align:start position:0% reassembles and with the compiler 00:17:36.330 --> 00:17:39.350 align:start position:0% reassembles and with the compiler general<00:17:36.930> compiler<00:17:37.910> architectures<00:17:38.910> where<00:17:39.210> you 00:17:39.350 --> 00:17:39.360 align:start position:0% general compiler architectures where you 00:17:39.360 --> 00:17:40.940 align:start position:0% general compiler architectures where you have<00:17:39.600> you<00:17:39.810> know<00:17:39.930> this<00:17:40.110> processing<00:17:40.800> in 00:17:40.940 --> 00:17:40.950 align:start position:0% have you know this processing in 00:17:40.950 --> 00:17:43.730 align:start position:0% have you know this processing in pipeline<00:17:41.430> so<00:17:41.700> first<00:17:41.970> we<00:17:42.150> parsing<00:17:42.990> VI<00:17:43.260> and<00:17:43.560> the 00:17:43.730 --> 00:17:43.740 align:start position:0% pipeline so first we parsing VI and the 00:17:43.740 --> 00:17:46.670 align:start position:0% pipeline so first we parsing VI and the code<00:17:44.310> generation<00:17:44.730> and<00:17:45.150> this<00:17:45.990> basically<00:17:46.410> means 00:17:46.670 --> 00:17:46.680 align:start position:0% code generation and this basically means 00:17:46.680 --> 00:17:48.820 align:start position:0% code generation and this basically means the<00:17:47.040> code<00:17:47.400> generation<00:17:47.850> is<00:17:48.120> just 00:17:48.820 --> 00:17:48.830 align:start position:0% the code generation is just 00:17:48.830 --> 00:17:50.740 align:start position:0% the code generation is just function<00:17:49.190> that<00:17:49.370> takes<00:17:49.610> in<00:17:49.850> gyeom<00:17:50.330> to<00:17:50.480> return 00:17:50.740 --> 00:17:50.750 align:start position:0% function that takes in gyeom to return 00:17:50.750 --> 00:17:53.340 align:start position:0% function that takes in gyeom to return some<00:17:51.050> strings<00:17:51.590> without<00:17:51.770> any<00:17:52.220> i/o<00:17:52.370> and<00:17:52.730> so<00:17:53.000> on 00:17:53.340 --> 00:17:53.350 align:start position:0% some strings without any i/o and so on 00:17:53.350 --> 00:17:58.120 align:start position:0% some strings without any i/o and so on so<00:17:54.350> it's<00:17:54.710> as<00:17:55.040> simple<00:17:55.250> as<00:17:55.430> possible<00:17:55.670> and<00:17:56.920> I<00:17:57.920> want 00:17:58.120 --> 00:17:58.130 align:start position:0% so it's as simple as possible and I want 00:17:58.130 --> 00:17:59.620 align:start position:0% so it's as simple as possible and I want to<00:17:58.220> talk<00:17:58.370> a<00:17:58.430> little<00:17:58.700> bit<00:17:58.850> now<00:17:58.880> about<00:17:59.030> the<00:17:59.450> two 00:17:59.620 --> 00:17:59.630 align:start position:0% to talk a little bit now about the two 00:17:59.630 --> 00:18:43.930 align:start position:0% to talk a little bit now about the two Gs<00:18:00.050> organization<00:18:42.490> special<00:18:43.490> and<00:18:43.670> I'm<00:18:43.760> dumb 00:18:43.930 --> 00:18:43.940 align:start position:0% Gs organization special and I'm dumb 00:18:43.940 --> 00:18:45.940 align:start position:0% Gs organization special and I'm dumb because<00:18:44.180> I'm<00:18:44.600> running<00:18:44.870> out<00:18:45.110> of<00:18:45.170> time<00:18:45.380> and<00:18:45.620> we 00:18:45.940 --> 00:18:45.950 align:start position:0% because I'm running out of time and we 00:18:45.950 --> 00:18:49.870 align:start position:0% because I'm running out of time and we gonna<00:18:46.130> we<00:18:46.850> have<00:18:47.000> here<00:18:47.990> so<00:18:48.620> that<00:18:49.550> chain<00:18:49.760> is 00:18:49.870 --> 00:18:49.880 align:start position:0% gonna we have here so that chain is 00:18:49.880 --> 00:18:52.450 align:start position:0% gonna we have here so that chain is already<00:18:50.150> used<00:18:50.480> by<00:18:50.630> well-known<00:18:51.590> companies 00:18:52.450 --> 00:18:52.460 align:start position:0% already used by well-known companies 00:18:52.460 --> 00:18:55.540 align:start position:0% already used by well-known companies like<00:18:52.640> maker<00:18:53.170> now<00:18:54.170> if<00:18:54.290> I'm<00:18:54.470> changing<00:18:54.890> and<00:18:55.340> so 00:18:55.540 --> 00:18:55.550 align:start position:0% like maker now if I'm changing and so 00:18:55.550 --> 00:18:58.030 align:start position:0% like maker now if I'm changing and so and<00:18:55.700> song<00:18:55.940> so<00:18:56.720> it's<00:18:57.140> not<00:18:57.290> like<00:18:57.530> you<00:18:57.650> know<00:18:57.800> some 00:18:58.030 --> 00:18:58.040 align:start position:0% and song so it's not like you know some 00:18:58.040 --> 00:19:02.490 align:start position:0% and song so it's not like you know some project<00:18:58.900> uses<00:18:59.900> its<00:19:00.410> various<00:19:01.130> in<00:19:01.850> a<00:19:01.970> while<00:19:02.150> and 00:19:02.490 --> 00:19:02.500 align:start position:0% project uses its various in a while and 00:19:02.500 --> 00:19:06.030 align:start position:0% project uses its various in a while and keep<00:19:03.500> going<00:19:03.740> also<00:19:04.010> sponsored<00:19:04.610> like<00:19:04.880> many 00:19:06.030 --> 00:19:06.040 align:start position:0% keep going also sponsored like many 00:19:06.040 --> 00:19:08.970 align:start position:0% keep going also sponsored like many counties<00:19:07.040> and<00:19:07.310> to<00:19:07.670> you<00:19:08.090> know 00:19:08.970 --> 00:19:08.980 align:start position:0% counties and to you know 00:19:08.980 --> 00:19:13.140 align:start position:0% counties and to you know inject<00:19:09.760> some<00:19:10.030> cash<00:19:10.380> or<00:19:11.550> for<00:19:12.550> external 00:19:13.140 --> 00:19:13.150 align:start position:0% inject some cash or for external 00:19:13.150 --> 00:19:17.930 align:start position:0% inject some cash or for external developers<00:19:13.780> to<00:19:14.050> help<00:19:14.350> us<00:19:14.530> with<00:19:15.720> exact<00:19:16.720> issues 00:19:17.930 --> 00:19:17.940 align:start position:0% developers to help us with exact issues 00:19:17.940 --> 00:19:20.340 align:start position:0% developers to help us with exact issues and<00:19:18.940> basically<00:19:19.630> that's<00:19:19.780> it<00:19:19.870> man<00:19:20.050> see<00:19:20.200> that's 00:19:20.340 --> 00:19:20.350 align:start position:0% and basically that's it man see that's 00:19:20.350 --> 00:19:21.930 align:start position:0% and basically that's it man see that's my<00:19:20.470> twitter<00:19:20.740> handle<00:19:20.830> but<00:19:21.340> you<00:19:21.370> can<00:19:21.550> consider 00:19:21.930 --> 00:19:21.940 align:start position:0% my twitter handle but you can consider 00:19:21.940 --> 00:19:28.140 align:start position:0% my twitter handle but you can consider following 00:19:28.140 --> 00:19:28.150 align:start position:0% 00:19:28.150 --> 00:19:34.290 align:start position:0% [Applause]