WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:10.360 align:start position:0% [Applause] 00:00:10.360 --> 00:00:10.370 align:start position:0% 00:00:10.370 --> 00:00:29.560 align:start position:0% a<00:00:23.830> school<00:00:24.830> or<00:00:24.950> scripts<00:00:27.040> in<00:00:28.040> a<00:00:28.540> lot<00:00:29.540> of 00:00:29.560 --> 00:00:29.570 align:start position:0% a school or scripts in a lot of 00:00:29.570 --> 00:00:40.389 align:start position:0% a school or scripts in a lot of libraries<00:00:36.910> specifically<00:00:38.829> now<00:00:39.829> I<00:00:39.860> worked<00:00:40.190> on<00:00:40.340> a 00:00:40.389 --> 00:00:40.399 align:start position:0% libraries specifically now I worked on a 00:00:40.399 --> 00:00:42.280 align:start position:0% libraries specifically now I worked on a different<00:00:40.790> project<00:00:41.120> cost<00:00:41.480> of<00:00:41.690> really<00:00:42.110> have 00:00:42.280 --> 00:00:42.290 align:start position:0% different project cost of really have 00:00:42.290 --> 00:00:47.500 align:start position:0% different project cost of really have some<00:00:42.440> onions<00:00:42.859> like<00:00:44.530> yeah<00:00:46.239> give<00:00:47.239> me<00:00:47.300> in<00:00:47.420> the 00:00:47.500 --> 00:00:47.510 align:start position:0% some onions like yeah give me in the 00:00:47.510 --> 00:00:57.819 align:start position:0% some onions like yeah give me in the back<00:00:48.190> I<00:00:49.190> literally<00:00:50.030> shouting<00:00:56.379> now<00:00:57.379> we're<00:00:57.649> in<00:00:57.769> a 00:00:57.819 --> 00:00:57.829 align:start position:0% back I literally shouting now we're in a 00:00:57.829 --> 00:00:59.770 align:start position:0% back I literally shouting now we're in a different<00:00:58.129> project<00:00:58.249> basically<00:00:58.969> like<00:00:59.300> Haskell 00:00:59.770 --> 00:00:59.780 align:start position:0% different project basically like Haskell 00:00:59.780 --> 00:01:01.549 align:start position:0% different project basically like Haskell bindings<00:01:00.379> to<00:01:00.589> like<00:01:00.859> a 00:01:01.549 --> 00:01:01.559 align:start position:0% bindings to like a 00:01:01.559 --> 00:01:05.930 align:start position:0% bindings to like a you<00:01:02.399> know<00:01:02.550> Enderman<00:01:03.120> API<00:01:03.840> soccer<00:01:04.830> ball<00:01:05.339> and<00:01:05.580> at 00:01:05.930 --> 00:01:05.940 align:start position:0% you know Enderman API soccer ball and at 00:01:05.940 --> 00:01:09.560 align:start position:0% you know Enderman API soccer ball and at Haskell<00:01:06.119> SDK<00:01:07.159> for<00:01:08.159> the<00:01:08.369> like<00:01:08.820> cosmos<00:01:09.240> Network 00:01:09.560 --> 00:01:09.570 align:start position:0% Haskell SDK for the like cosmos Network 00:01:09.570 --> 00:01:14.539 align:start position:0% Haskell SDK for the like cosmos Network that's<00:01:09.869> also<00:01:10.200> forever<00:01:10.409> or<00:01:10.740> my<00:01:11.369> work<00:01:13.159> so<00:01:14.159> that's 00:01:14.539 --> 00:01:14.549 align:start position:0% that's also forever or my work so that's 00:01:14.549 --> 00:01:29.520 align:start position:0% that's also forever or my work so that's what<00:01:14.759> we<00:01:14.850> do<00:01:15.060> or<00:01:15.299> less 00:01:29.520 --> 00:01:29.530 align:start position:0% 00:01:29.530 --> 00:02:10.150 align:start position:0% all<00:01:30.530> right<00:02:05.650> so<00:02:07.060> we<00:02:08.060> basically<00:02:08.300> focus<00:02:09.160> purely 00:02:10.150 --> 00:02:10.160 align:start position:0% all right so we basically focus purely 00:02:10.160 --> 00:02:12.070 align:start position:0% all right so we basically focus purely functional<00:02:10.369> languages<00:02:10.970> with<00:02:11.450> strong<00:02:11.750> static 00:02:12.070 --> 00:02:12.080 align:start position:0% functional languages with strong static 00:02:12.080 --> 00:02:19.350 align:start position:0% functional languages with strong static typing<00:02:13.540> what<00:02:14.540> does<00:02:14.660> that<00:02:14.690> mean<00:02:15.700> purity<00:02:16.700> is 00:02:19.350 --> 00:02:19.360 align:start position:0% 00:02:19.360 --> 00:02:21.880 align:start position:0% much<00:02:20.360> like<00:02:20.570> referential<00:02:21.200> transparency<00:02:21.410> it 00:02:21.880 --> 00:02:21.890 align:start position:0% much like referential transparency it 00:02:21.890 --> 00:02:23.320 align:start position:0% much like referential transparency it means<00:02:22.100> that<00:02:22.250> your<00:02:22.520> conversations<00:02:23.150> actually 00:02:23.320 --> 00:02:23.330 align:start position:0% means that your conversations actually 00:02:23.330 --> 00:02:24.940 align:start position:0% means that your conversations actually don't<00:02:23.660> know<00:02:23.780> these<00:02:23.930> side<00:02:24.140> effects<00:02:24.410> so<00:02:24.680> think 00:02:24.940 --> 00:02:24.950 align:start position:0% don't know these side effects so think 00:02:24.950 --> 00:02:27.640 align:start position:0% don't know these side effects so think about<00:02:25.040> your<00:02:25.400> reputation<00:02:25.700> as<00:02:26.270> equation<00:02:26.720> like<00:02:27.260> X 00:02:27.640 --> 00:02:27.650 align:start position:0% about your reputation as equation like X 00:02:27.650 --> 00:02:31.030 align:start position:0% about your reputation as equation like X equals<00:02:28.459> 5<00:02:29.170> whatever<00:02:30.170> you're<00:02:30.650> not<00:02:30.680> actually 00:02:31.030 --> 00:02:31.040 align:start position:0% equals 5 whatever you're not actually 00:02:31.040 --> 00:02:37.690 align:start position:0% equals 5 whatever you're not actually performing<00:02:31.310> any<00:02:35.650> two<00:02:36.650> different<00:02:37.190> kinds<00:02:37.610> of 00:02:37.690 --> 00:02:37.700 align:start position:0% performing any two different kinds of 00:02:37.700 --> 00:02:41.009 align:start position:0% performing any two different kinds of concepts<00:02:38.060> in<00:02:38.769> hospital<00:02:39.769> and<00:02:40.070> clear<00:02:40.250> script 00:02:41.009 --> 00:02:41.019 align:start position:0% concepts in hospital and clear script 00:02:41.019 --> 00:02:44.500 align:start position:0% concepts in hospital and clear script Monat<00:02:42.040> it's<00:02:43.040> sort<00:02:43.340> of<00:02:43.370> a<00:02:43.459> pure<00:02:43.850> way<00:02:44.090> to<00:02:44.150> talk 00:02:44.500 --> 00:02:44.510 align:start position:0% Monat it's sort of a pure way to talk 00:02:44.510 --> 00:02:47.740 align:start position:0% Monat it's sort of a pure way to talk about<00:02:44.630> impure<00:02:45.230> programs<00:02:45.709> that<00:02:46.010> the<00:02:46.820> type 00:02:47.740 --> 00:02:47.750 align:start position:0% about impure programs that the type 00:02:47.750 --> 00:02:51.610 align:start position:0% about impure programs that the type system<00:02:48.130> which<00:02:49.130> may<00:02:49.910> be<00:02:50.060> your<00:02:50.239> typical<00:02:50.620> program 00:02:51.610 --> 00:02:51.620 align:start position:0% system which may be your typical program 00:02:51.620 --> 00:02:52.520 align:start position:0% system which may be your typical program electricity 00:02:52.520 --> 00:02:52.530 align:start position:0% electricity 00:02:52.530 --> 00:02:54.140 align:start position:0% electricity with<00:02:52.620> different<00:02:52.800> types<00:02:53.160> of<00:02:53.340> data<00:02:53.580> strings 00:02:54.140 --> 00:02:54.150 align:start position:0% with different types of data strings 00:02:54.150 --> 00:02:57.980 align:start position:0% with different types of data strings integers<00:02:54.720> and<00:02:55.560> so<00:02:55.710> on<00:02:55.860> the<00:02:56.760> type<00:02:57.000> system<00:02:57.210> in 00:02:57.980 --> 00:02:57.990 align:start position:0% integers and so on the type system in 00:02:57.990 --> 00:02:59.660 align:start position:0% integers and so on the type system in the<00:02:58.620> programming<00:02:58.950> language<00:02:59.040> that<00:02:59.340> we've 00:02:59.660 --> 00:02:59.670 align:start position:0% the programming language that we've 00:02:59.670 --> 00:03:01.580 align:start position:0% the programming language that we've talked<00:03:00.210> about<00:03:00.420> actually<00:03:00.630> are<00:03:00.840> able<00:03:00.990> to<00:03:01.110> reason 00:03:01.580 --> 00:03:01.590 align:start position:0% talked about actually are able to reason 00:03:01.590 --> 00:03:04.100 align:start position:0% talked about actually are able to reason about<00:03:01.680> these<00:03:02.040> defenses<00:03:02.640> as<00:03:02.970> well<00:03:03.210> so<00:03:03.900> it 00:03:04.100 --> 00:03:04.110 align:start position:0% about these defenses as well so it 00:03:04.110 --> 00:03:06.560 align:start position:0% about these defenses as well so it prevents<00:03:04.530> you<00:03:04.620> from<00:03:04.650> doing<00:03:05.070> things<00:03:05.490> that<00:03:05.820> in 00:03:06.560 --> 00:03:06.570 align:start position:0% prevents you from doing things that in 00:03:06.570 --> 00:03:08.060 align:start position:0% prevents you from doing things that in the<00:03:06.660> real<00:03:06.840> world<00:03:07.080> when<00:03:07.710> you're<00:03:07.830> writing 00:03:08.060 --> 00:03:08.070 align:start position:0% the real world when you're writing 00:03:08.070 --> 00:03:11.650 align:start position:0% the real world when you're writing something<00:03:08.370> that<00:03:08.520> is<00:03:09.150> almost<00:03:09.390> computer<00:03:10.200> valid 00:03:11.650 --> 00:03:11.660 align:start position:0% something that is almost computer valid 00:03:11.660 --> 00:03:22.040 align:start position:0% something that is almost computer valid then<00:03:12.660> you<00:03:13.650> see<00:03:13.860> what<00:03:14.640> happens<00:03:14.970> so<00:03:20.660> we<00:03:21.660> try<00:03:22.020> to 00:03:22.040 --> 00:03:22.050 align:start position:0% then you see what happens so we try to 00:03:22.050 --> 00:03:28.940 align:start position:0% then you see what happens so we try to use<00:03:22.470> that<00:03:22.740> for<00:03:23.100> our<00:03:23.220> benefit<00:03:23.700> so<00:03:24.120> the<00:03:27.950> language 00:03:28.940 --> 00:03:28.950 align:start position:0% use that for our benefit so the language 00:03:28.950 --> 00:03:31.400 align:start position:0% use that for our benefit so the language that<00:03:29.310> we<00:03:29.459> represent<00:03:29.940> and<00:03:30.540> one<00:03:31.110> of<00:03:31.230> the 00:03:31.400 --> 00:03:31.410 align:start position:0% that we represent and one of the 00:03:31.410 --> 00:03:32.660 align:start position:0% that we represent and one of the libraries<00:03:31.800> that<00:03:31.980> you've<00:03:32.130> been<00:03:32.250> developing 00:03:32.660 --> 00:03:32.670 align:start position:0% libraries that you've been developing 00:03:32.670 --> 00:03:36.980 align:start position:0% libraries that you've been developing utilize<00:03:33.450> that 00:03:36.980 --> 00:03:36.990 align:start position:0% 00:03:36.990 --> 00:03:43.380 align:start position:0% yeah<00:03:39.270> yeah<00:03:41.370> basically<00:03:42.370> like<00:03:42.820> the<00:03:42.940> kind<00:03:43.150> things 00:03:43.380 --> 00:03:43.390 align:start position:0% yeah yeah basically like the kind things 00:03:43.390 --> 00:03:46.620 align:start position:0% yeah yeah basically like the kind things that<00:03:43.540> work<00:03:43.740> contrasting<00:03:44.740> is<00:03:44.890> here<00:03:45.160> are<00:03:46.120> widely 00:03:46.620 --> 00:03:46.630 align:start position:0% that work contrasting is here are widely 00:03:46.630 --> 00:03:48.990 align:start position:0% that work contrasting is here are widely popular<00:03:47.170> target<00:03:47.620> languages<00:03:48.070> like<00:03:48.340> JavaScript 00:03:48.990 --> 00:03:49.000 align:start position:0% popular target languages like JavaScript 00:03:49.000 --> 00:03:51.510 align:start position:0% popular target languages like JavaScript or<00:03:49.150> go<00:03:49.710> they're<00:03:50.710> kind<00:03:50.920> of<00:03:50.950> like<00:03:51.070> languages 00:03:51.510 --> 00:03:51.520 align:start position:0% or go they're kind of like languages 00:03:51.520 --> 00:03:55.470 align:start position:0% or go they're kind of like languages everybody<00:03:52.000> uses<00:03:52.360> this<00:03:52.960> space<00:03:54.210> people<00:03:55.210> seem<00:03:55.450> to 00:03:55.470 --> 00:03:55.480 align:start position:0% everybody uses this space people seem to 00:03:55.480 --> 00:03:57.120 align:start position:0% everybody uses this space people seem to be<00:03:55.630> very<00:03:55.660> productive<00:03:56.110> and<00:03:56.410> those<00:03:56.620> things<00:03:56.860> so 00:03:57.120 --> 00:03:57.130 align:start position:0% be very productive and those things so 00:03:57.130 --> 00:04:01.080 align:start position:0% be very productive and those things so that's<00:03:57.490> your<00:03:57.640> DM<00:03:57.910> and<00:03:58.210> like<00:03:59.640> but<00:04:00.640> you<00:04:01.060> know 00:04:01.080 --> 00:04:01.090 align:start position:0% that's your DM and like but you know 00:04:01.090 --> 00:04:03.420 align:start position:0% that's your DM and like but you know basically<00:04:01.780> like<00:04:02.020> you<00:04:02.740> can't<00:04:02.980> really<00:04:03.100> make<00:04:03.250> the 00:04:03.420 --> 00:04:03.430 align:start position:0% basically like you can't really make the 00:04:03.430 --> 00:04:04.950 align:start position:0% basically like you can't really make the argument<00:04:03.820> that<00:04:03.850> really<00:04:04.030> lie<00:04:04.300> there<00:04:04.540> is<00:04:04.660> like<00:04:04.930> a 00:04:04.950 --> 00:04:04.960 align:start position:0% argument that really lie there is like a 00:04:04.960 --> 00:04:06.660 align:start position:0% argument that really lie there is like a particularly<00:04:05.590> future<00:04:06.130> thinking<00:04:06.520> or 00:04:06.660 --> 00:04:06.670 align:start position:0% particularly future thinking or 00:04:06.670 --> 00:04:07.950 align:start position:0% particularly future thinking or innovative<00:04:07.030> programming<00:04:07.570> languages 00:04:07.950 --> 00:04:07.960 align:start position:0% innovative programming languages 00:04:07.960 --> 00:04:10.230 align:start position:0% innovative programming languages especially<00:04:08.590> like<00:04:09.220> you<00:04:09.520> know<00:04:09.610> people<00:04:09.880> like<00:04:10.030> go 00:04:10.230 --> 00:04:10.240 align:start position:0% especially like you know people like go 00:04:10.240 --> 00:04:12.090 align:start position:0% especially like you know people like go and<00:04:10.450> it's<00:04:10.570> it<00:04:10.900> seems<00:04:11.170> like<00:04:11.410> lots<00:04:11.680> of<00:04:11.770> programs 00:04:12.090 --> 00:04:12.100 align:start position:0% and it's it seems like lots of programs 00:04:12.100 --> 00:04:13.980 align:start position:0% and it's it seems like lots of programs are<00:04:12.280> successful<00:04:12.430> break<00:04:12.880> and<00:04:13.060> go<00:04:13.180> but<00:04:13.510> for 00:04:13.980 --> 00:04:13.990 align:start position:0% are successful break and go but for 00:04:13.990 --> 00:04:17.670 align:start position:0% are successful break and go but for language<00:04:14.320> that<00:04:14.470> was<00:04:15.660> 2005<00:04:16.660> or<00:04:17.350> whatever<00:04:17.560> it 00:04:17.670 --> 00:04:17.680 align:start position:0% language that was 2005 or whatever it 00:04:17.680 --> 00:04:18.990 align:start position:0% language that was 2005 or whatever it was<00:04:17.799> that<00:04:17.860> knowing<00:04:18.220> everything<00:04:18.430> we<00:04:18.670> know<00:04:18.790> now 00:04:18.990 --> 00:04:19.000 align:start position:0% was that knowing everything we know now 00:04:19.000 --> 00:04:21.810 align:start position:0% was that knowing everything we know now like<00:04:19.720> they<00:04:19.870> basically<00:04:20.260> just<00:04:20.530> create<00:04:21.489> a<00:04:21.520> Java 00:04:21.810 --> 00:04:21.820 align:start position:0% like they basically just create a Java 00:04:21.820 --> 00:04:26.100 align:start position:0% like they basically just create a Java server<00:04:22.210> like<00:04:22.480> 1982<00:04:23.350> so<00:04:23.890> it's<00:04:24.760> like<00:04:24.940> you<00:04:25.810> can<00:04:25.960> do 00:04:26.100 --> 00:04:26.110 align:start position:0% server like 1982 so it's like you can do 00:04:26.110 --> 00:04:27.780 align:start position:0% server like 1982 so it's like you can do things<00:04:26.290> in<00:04:26.470> those<00:04:26.620> you<00:04:26.920> know<00:04:27.010> that's<00:04:27.280> cool<00:04:27.490> but 00:04:27.780 --> 00:04:27.790 align:start position:0% things in those you know that's cool but 00:04:27.790 --> 00:04:29.970 align:start position:0% things in those you know that's cool but there's<00:04:28.360> like<00:04:28.570> a<00:04:28.600> lot<00:04:28.870> of<00:04:29.020> research<00:04:29.800> and 00:04:29.970 --> 00:04:29.980 align:start position:0% there's like a lot of research and 00:04:29.980 --> 00:04:31.230 align:start position:0% there's like a lot of research and perfect 00:04:31.230 --> 00:04:31.240 align:start position:0% perfect 00:04:31.240 --> 00:04:34.150 align:start position:0% perfect kinds<00:04:32.240> of<00:04:32.300> reason<00:04:33.110> to<00:04:33.140> the<00:04:33.320> program<00:04:33.710> pretty<00:04:33.890> my 00:04:34.150 --> 00:04:34.160 align:start position:0% kinds of reason to the program pretty my 00:04:34.160 --> 00:04:35.660 align:start position:0% kinds of reason to the program pretty my brother<00:04:34.460> and<00:04:34.610> we<00:04:34.790> do 00:04:35.660 --> 00:04:35.670 align:start position:0% brother and we do 00:04:35.670 --> 00:04:37.670 align:start position:0% brother and we do 19<00:04:36.330> that<00:04:36.540> was<00:04:36.690> not<00:04:36.900> possible<00:04:37.110> in<00:04:37.410> the<00:04:37.530> night 00:04:37.670 --> 00:04:37.680 align:start position:0% 19 that was not possible in the night 00:04:37.680 --> 00:04:40.780 align:start position:0% 19 that was not possible in the night that's 00:04:40.780 --> 00:04:40.790 align:start position:0% 00:04:40.790 --> 00:04:42.460 align:start position:0% so<00:04:41.390> because<00:04:41.720> like<00:04:41.900> either<00:04:42.080> one<00:04:42.260> of<00:04:42.320> these 00:04:42.460 --> 00:04:42.470 align:start position:0% so because like either one of these 00:04:42.470 --> 00:04:44.530 align:start position:0% so because like either one of these others<00:04:42.800> much<00:04:42.980> in<00:04:43.160> terms<00:04:43.370> of<00:04:43.520> like<00:04:43.700> safeties<00:04:44.270> of 00:04:44.530 --> 00:04:44.540 align:start position:0% others much in terms of like safeties of 00:04:44.540 --> 00:04:46.870 align:start position:0% others much in terms of like safeties of the<00:04:44.660> ability<00:04:45.050> to<00:04:45.080> statically<00:04:45.680> analyze<00:04:46.010> her 00:04:46.870 --> 00:04:46.880 align:start position:0% the ability to statically analyze her 00:04:46.880 --> 00:04:50.260 align:start position:0% the ability to statically analyze her behavior<00:04:47.600> performance<00:04:47.930> or<00:04:48.500> possible<00:04:49.270> or 00:04:50.260 --> 00:04:50.270 align:start position:0% behavior performance or possible or 00:04:50.270 --> 00:04:51.490 align:start position:0% behavior performance or possible or whatever<00:04:50.600> you<00:04:50.840> know<00:04:50.930> people<00:04:51.200> focus 00:04:51.490 --> 00:04:51.500 align:start position:0% whatever you know people focus 00:04:51.500 --> 00:04:52.600 align:start position:0% whatever you know people focus especially<00:04:51.710> on<00:04:52.010> things<00:04:52.220> like<00:04:52.430> security 00:04:52.600 --> 00:04:52.610 align:start position:0% especially on things like security 00:04:52.610 --> 00:04:54.280 align:start position:0% especially on things like security threats<00:04:53.150> in<00:04:53.300> the<00:04:53.390> space<00:04:53.630> and<00:04:53.900> all<00:04:54.110> those 00:04:54.280 --> 00:04:54.290 align:start position:0% threats in the space and all those 00:04:54.290 --> 00:05:04.500 align:start position:0% threats in the space and all those things<00:04:54.470> are<00:04:54.620> really<00:04:54.650> difficult<00:04:55.250> oh<00:05:00.850> and<00:05:01.850> so 00:05:04.500 --> 00:05:04.510 align:start position:0% 00:05:04.510 --> 00:05:06.700 align:start position:0% basically<00:05:05.510> the<00:05:05.930> light<00:05:06.110> rates<00:05:06.350> that<00:05:06.530> we're 00:05:06.700 --> 00:05:06.710 align:start position:0% basically the light rates that we're 00:05:06.710 --> 00:05:08.680 align:start position:0% basically the light rates that we're talking<00:05:07.100> about<00:05:07.460> right<00:05:07.730> today<00:05:08.150> or<00:05:08.360> like<00:05:08.600> you 00:05:08.680 --> 00:05:08.690 align:start position:0% talking about right today or like you 00:05:08.690 --> 00:05:10.510 align:start position:0% talking about right today or like you tomorrow<00:05:09.170> with<00:05:09.500> this<00:05:09.620> other<00:05:09.830> workshop<00:05:10.250> course 00:05:10.510 --> 00:05:10.520 align:start position:0% tomorrow with this other workshop course 00:05:10.520 --> 00:05:13.960 align:start position:0% tomorrow with this other workshop course on<00:05:10.670> the<00:05:12.460> Democrats<00:05:13.460> which<00:05:13.640> we'll<00:05:13.760> talk<00:05:13.910> about 00:05:13.960 --> 00:05:13.970 align:start position:0% on the Democrats which we'll talk about 00:05:13.970 --> 00:05:17.440 align:start position:0% on the Democrats which we'll talk about later<00:05:15.550> basically<00:05:16.550> like<00:05:16.730> the<00:05:16.850> one<00:05:16.970> so<00:05:17.210> you<00:05:17.420> know 00:05:17.440 --> 00:05:17.450 align:start position:0% later basically like the one so you know 00:05:17.450 --> 00:05:18.870 align:start position:0% later basically like the one so you know whatever<00:05:17.720> there's<00:05:18.020> a<00:05:18.080> web<00:05:18.200> create<00:05:18.560> guide 00:05:18.870 --> 00:05:18.880 align:start position:0% whatever there's a web create guide 00:05:18.880 --> 00:05:21.850 align:start position:0% whatever there's a web create guide similar<00:05:19.880> to<00:05:20.090> Twitter<00:05:20.150> and<00:05:20.720> jonah<00:05:21.050> jameson<00:05:21.650> for 00:05:21.850 --> 00:05:21.860 align:start position:0% similar to Twitter and jonah jameson for 00:05:21.860 --> 00:05:24.190 align:start position:0% similar to Twitter and jonah jameson for your<00:05:21.980> job<00:05:22.220> or<00:05:22.700> whatever<00:05:22.970> it<00:05:23.690> has<00:05:23.840> lots<00:05:24.110> of 00:05:24.190 --> 00:05:24.200 align:start position:0% your job or whatever it has lots of 00:05:24.200 --> 00:05:25.480 align:start position:0% your job or whatever it has lots of features<00:05:24.320> that<00:05:24.530> those<00:05:24.800> things<00:05:24.950> don't<00:05:25.190> but 00:05:25.480 --> 00:05:25.490 align:start position:0% features that those things don't but 00:05:25.490 --> 00:05:26.980 align:start position:0% features that those things don't but that's<00:05:25.670> some<00:05:25.880> kind<00:05:26.090> of<00:05:26.120> like<00:05:26.270> functionality 00:05:26.980 --> 00:05:26.990 align:start position:0% that's some kind of like functionality 00:05:26.990 --> 00:05:28.530 align:start position:0% that's some kind of like functionality that<00:05:27.110> it<00:05:27.230> covers 00:05:28.530 --> 00:05:28.540 align:start position:0% that it covers 00:05:28.540 --> 00:05:30.600 align:start position:0% that it covers and<00:05:28.900> then<00:05:29.050> chanterelle<00:05:29.530> is<00:05:29.770> like<00:05:30.010> a<00:05:30.040> tool<00:05:30.310> that 00:05:30.600 --> 00:05:30.610 align:start position:0% and then chanterelle is like a tool that 00:05:30.610 --> 00:05:34.640 align:start position:0% and then chanterelle is like a tool that we<00:05:30.760> have<00:05:31.060> made<00:05:31.740> like<00:05:32.740> maturity<00:05:33.280> at<00:05:33.940> this<00:05:34.180> point 00:05:34.640 --> 00:05:34.650 align:start position:0% we have made like maturity at this point 00:05:34.650 --> 00:05:38.460 align:start position:0% we have made like maturity at this point and<00:05:35.650> is<00:05:36.100> the<00:05:36.540> contract<00:05:37.540> employed<00:05:37.840> management 00:05:38.460 --> 00:05:38.470 align:start position:0% and is the contract employed management 00:05:38.470 --> 00:05:40.590 align:start position:0% and is the contract employed management and<00:05:38.680> testing<00:05:38.890> tool<00:05:39.310> similar<00:05:39.760> to<00:05:39.910> truffle<00:05:40.450> but 00:05:40.590 --> 00:05:40.600 align:start position:0% and testing tool similar to truffle but 00:05:40.600 --> 00:05:42.510 align:start position:0% and testing tool similar to truffle but without<00:05:40.810> other<00:05:41.080> you<00:05:41.470> know<00:05:41.620> nonsense 00:05:42.510 --> 00:05:42.520 align:start position:0% without other you know nonsense 00:05:42.520 --> 00:05:45.570 align:start position:0% without other you know nonsense so<00:05:43.320> and<00:05:44.320> I<00:05:44.620> should<00:05:44.770> also<00:05:44.830> mention<00:05:45.010> that<00:05:45.370> like 00:05:45.570 --> 00:05:45.580 align:start position:0% so and I should also mention that like 00:05:45.580 --> 00:05:46.920 align:start position:0% so and I should also mention that like okay<00:05:45.970> then<00:05:46.120> there's<00:05:46.270> others<00:05:46.540> at<00:05:46.750> Haskell 00:05:46.920 --> 00:05:46.930 align:start position:0% okay then there's others at Haskell 00:05:46.930 --> 00:05:48.600 align:start position:0% okay then there's others at Haskell libraries<00:05:47.620> which<00:05:47.800> are<00:05:47.890> maintaining<00:05:48.280> for<00:05:48.490> this 00:05:48.600 --> 00:05:48.610 align:start position:0% libraries which are maintaining for this 00:05:48.610 --> 00:05:51.180 align:start position:0% libraries which are maintaining for this we<00:05:49.510> don't<00:05:49.690> maintain<00:05:49.840> this<00:05:50.230> but<00:05:50.500> we're<00:05:50.890> I'm 00:05:51.180 --> 00:05:51.190 align:start position:0% we don't maintain this but we're I'm 00:05:51.190 --> 00:05:52.410 align:start position:0% we don't maintain this but we're I'm like<00:05:51.340> the<00:05:51.460> largest<00:05:51.820> contributor<00:05:52.270> to<00:05:52.390> that 00:05:52.410 --> 00:05:52.420 align:start position:0% like the largest contributor to that 00:05:52.420 --> 00:05:57.920 align:start position:0% like the largest contributor to that we're<00:05:52.750> probably<00:05:52.900> this<00:05:53.170> point<00:05:53.880> right<00:05:54.880> a<00:05:54.940> fourth 00:05:57.920 --> 00:05:57.930 align:start position:0% 00:05:57.930 --> 00:06:00.600 align:start position:0% it's<00:05:58.930> also<00:05:59.050> worth<00:05:59.260> mentioning<00:05:59.290> that<00:05:59.650> I<00:05:59.920> bless 00:06:00.600 --> 00:06:00.610 align:start position:0% it's also worth mentioning that I bless 00:06:00.610 --> 00:06:01.950 align:start position:0% it's also worth mentioning that I bless this<00:06:00.760> talk<00:06:01.000> before<00:06:01.150> last<00:06:01.510> year's<00:06:01.780> thing 00:06:01.950 --> 00:06:01.960 align:start position:0% this talk before last year's thing 00:06:01.960 --> 00:06:03.090 align:start position:0% this talk before last year's thing everywhere<00:06:02.350> tonight<00:06:02.470> because<00:06:02.920> it's 00:06:03.090 --> 00:06:03.100 align:start position:0% everywhere tonight because it's 00:06:03.100 --> 00:06:05.790 align:start position:0% everywhere tonight because it's considered<00:06:03.520> like<00:06:03.610> fringe<00:06:04.180> or<00:06:04.570> like<00:06:05.170> me<00:06:05.380> to<00:06:05.620> be 00:06:05.790 --> 00:06:05.800 align:start position:0% considered like fringe or like me to be 00:06:05.800 --> 00:06:11.130 align:start position:0% considered like fringe or like me to be sure<00:06:06.010> whatever<00:06:06.250> so<00:06:06.460> if<00:06:06.760> this<00:06:09.960> none<00:06:10.960> of<00:06:10.990> these 00:06:11.130 --> 00:06:11.140 align:start position:0% sure whatever so if this none of these 00:06:11.140 --> 00:06:13.410 align:start position:0% sure whatever so if this none of these things<00:06:11.350> are<00:06:11.470> doing<00:06:11.650> around<00:06:12.070> over<00:06:12.700> here<00:06:12.730> and 00:06:13.410 --> 00:06:13.420 align:start position:0% things are doing around over here and 00:06:13.420 --> 00:06:18.600 align:start position:0% things are doing around over here and it's<00:06:13.600> now<00:06:13.780> we<00:06:13.840> got<00:06:14.110> the<00:06:14.830> extra<00:06:15.100> behind<00:06:17.610> and 00:06:18.600 --> 00:06:18.610 align:start position:0% it's now we got the extra behind and 00:06:18.610 --> 00:06:20.970 align:start position:0% it's now we got the extra behind and yeah<00:06:18.940> so<00:06:19.210> that<00:06:19.240> one<00:06:19.540> sitter<00:06:19.780> it<00:06:19.960> gold<00:06:20.830> or 00:06:20.970 --> 00:06:20.980 align:start position:0% yeah so that one sitter it gold or 00:06:20.980 --> 00:06:22.140 align:start position:0% yeah so that one sitter it gold or whatever<00:06:21.070> those<00:06:21.460> are<00:06:21.520> things<00:06:21.820> that<00:06:21.910> he 00:06:22.140 --> 00:06:22.150 align:start position:0% whatever those are things that he 00:06:22.150 --> 00:06:27.000 align:start position:0% whatever those are things that he actually 00:06:27.000 --> 00:06:27.010 align:start position:0% 00:06:27.010 --> 00:06:29.140 align:start position:0% it's<00:06:28.010> not<00:06:28.190> super<00:06:28.460> interesting<00:06:28.820> with<00:06:28.940> just<00:06:29.060> a 00:06:29.140 --> 00:06:29.150 align:start position:0% it's not super interesting with just a 00:06:29.150 --> 00:06:30.400 align:start position:0% it's not super interesting with just a highlight<00:06:29.270> the<00:06:29.480> point<00:06:29.600> that<00:06:29.750> we<00:06:29.870> actually<00:06:30.050> did 00:06:30.400 --> 00:06:30.410 align:start position:0% highlight the point that we actually did 00:06:30.410 --> 00:06:32.530 align:start position:0% highlight the point that we actually did all<00:06:30.590> this<00:06:30.770> stuff<00:06:30.950> last<00:06:31.250> year<00:06:31.550> so<00:06:32.120> this<00:06:32.330> isn't 00:06:32.530 --> 00:06:32.540 align:start position:0% all this stuff last year so this isn't 00:06:32.540 --> 00:06:35.020 align:start position:0% all this stuff last year so this isn't like<00:06:32.810> your<00:06:33.020> new<00:06:33.350> like<00:06:33.680> j/s<00:06:34.130> framework<00:06:34.730> you 00:06:35.020 --> 00:06:35.030 align:start position:0% like your new like j/s framework you 00:06:35.030 --> 00:06:37.989 align:start position:0% like your new like j/s framework you know<00:06:35.120> one<00:06:35.270> week<00:06:35.420> or<00:06:35.600> whatever<00:06:35.720> this 00:06:37.989 --> 00:06:37.999 align:start position:0% know one week or whatever this 00:06:37.999 --> 00:06:39.669 align:start position:0% know one week or whatever this place<00:06:38.209> at<00:06:38.419> all<00:06:38.599> I'll<00:06:39.139> say<00:06:39.289> is<00:06:39.319> that<00:06:39.439> these 00:06:39.669 --> 00:06:39.679 align:start position:0% place at all I'll say is that these 00:06:39.679 --> 00:06:41.979 align:start position:0% place at all I'll say is that these libraries<00:06:40.189> are<00:06:40.309> mature<00:06:41.149> and<00:06:41.509> you<00:06:41.659> can<00:06:41.839> use 00:06:41.979 --> 00:06:41.989 align:start position:0% libraries are mature and you can use 00:06:41.989 --> 00:06:43.839 align:start position:0% libraries are mature and you can use them<00:06:42.169> illustrate<00:06:43.129> that<00:06:43.279> in<00:06:43.399> this<00:06:43.489> workshop 00:06:43.839 --> 00:06:43.849 align:start position:0% them illustrate that in this workshop 00:06:43.849 --> 00:06:46.539 align:start position:0% them illustrate that in this workshop tomorrow<00:06:44.209> but<00:06:45.199> this<00:06:45.349> is<00:06:45.529> not<00:06:45.709> like<00:06:45.739> some<00:06:46.249> new 00:06:46.539 --> 00:06:46.549 align:start position:0% tomorrow but this is not like some new 00:06:46.549 --> 00:06:49.779 align:start position:0% tomorrow but this is not like some new thing<00:06:46.969> that<00:06:47.149> doesn't<00:06:47.539> work<00:06:48.069> all<00:06:49.069> I<00:06:49.129> want<00:06:49.399> to 00:06:49.779 --> 00:06:49.789 align:start position:0% thing that doesn't work all I want to 00:06:49.789 --> 00:06:51.189 align:start position:0% thing that doesn't work all I want to skip<00:06:49.999> this<00:06:50.179> in<00:06:50.360> the<00:06:50.419> end<00:06:50.509> or<00:06:50.629> some<00:06:50.779> time<00:06:50.959> but 00:06:51.189 --> 00:06:51.199 align:start position:0% skip this in the end or some time but 00:06:51.199 --> 00:06:52.659 align:start position:0% skip this in the end or some time but basically<00:06:51.319> all<00:06:51.799> of<00:06:51.829> this<00:06:52.009> work<00:06:52.339> really 00:06:52.659 --> 00:06:52.669 align:start position:0% basically all of this work really 00:06:52.669 --> 00:06:55.139 align:start position:0% basically all of this work really starting<00:06:52.999> 2017<00:06:53.809> and<00:06:53.989> more<00:06:54.199> or<00:06:54.259> less<00:06:54.289> like 00:06:55.139 --> 00:06:55.149 align:start position:0% starting 2017 and more or less like 00:06:55.149 --> 00:06:57.429 align:start position:0% starting 2017 and more or less like accepting<00:06:56.149> you<00:06:56.389> know<00:06:56.479> case<00:06:56.719> of<00:06:56.899> truffle<00:06:57.289> which 00:06:57.429 --> 00:06:57.439 align:start position:0% accepting you know case of truffle which 00:06:57.439 --> 00:06:59.079 align:start position:0% accepting you know case of truffle which happens<00:06:57.799> cemetery<00:06:58.249> whatever<00:06:58.549> it<00:06:58.639> is<00:06:58.729> like<00:06:58.879> the 00:06:59.079 --> 00:06:59.089 align:start position:0% happens cemetery whatever it is like the 00:06:59.089 --> 00:07:01.659 align:start position:0% happens cemetery whatever it is like the truffle<00:06:59.599> decision<00:07:00.139> replace<00:07:00.559> it<00:07:00.799> it's<00:07:01.489> kind<00:07:01.639> of 00:07:01.659 --> 00:07:01.669 align:start position:0% truffle decision replace it it's kind of 00:07:01.669 --> 00:07:03.129 align:start position:0% truffle decision replace it it's kind of all<00:07:01.819> happening<00:07:02.179> contemporaneously<00:07:02.929> like 00:07:03.129 --> 00:07:03.139 align:start position:0% all happening contemporaneously like 00:07:03.139 --> 00:07:05.139 align:start position:0% all happening contemporaneously like with<00:07:03.319> our<00:07:03.469> growth<00:07:04.309> as<00:07:04.429> a<00:07:04.459> company<00:07:04.909> like 00:07:05.139 --> 00:07:05.149 align:start position:0% with our growth as a company like 00:07:05.149 --> 00:07:06.729 align:start position:0% with our growth as a company like probably<00:07:05.539> not<00:07:05.839> maybe<00:07:06.079> you<00:07:06.199> have<00:07:06.349> your<00:07:06.469> haven't 00:07:06.729 --> 00:07:06.739 align:start position:0% probably not maybe you have your haven't 00:07:06.739 --> 00:07:09.989 align:start position:0% probably not maybe you have your haven't heard<00:07:06.860> of<00:07:06.949> home<00:07:07.219> it's<00:07:08.179> a<00:07:08.269> cereal<00:07:09.199> company<00:07:09.589> but 00:07:09.989 --> 00:07:09.999 align:start position:0% heard of home it's a cereal company but 00:07:09.999 --> 00:07:12.129 align:start position:0% heard of home it's a cereal company but you<00:07:10.999> know<00:07:11.089> started<00:07:11.479> writing<00:07:11.659> software<00:07:11.869> in 00:07:12.129 --> 00:07:12.139 align:start position:0% you know started writing software in 00:07:12.139 --> 00:07:14.499 align:start position:0% you know started writing software in 2017<00:07:12.949> and<00:07:13.219> like<00:07:13.399> basically<00:07:13.669> the<00:07:13.939> reason<00:07:14.360> why 00:07:14.499 --> 00:07:14.509 align:start position:0% 2017 and like basically the reason why 00:07:14.509 --> 00:07:16.059 align:start position:0% 2017 and like basically the reason why all<00:07:14.659> this<00:07:14.809> software<00:07:14.989> exists<00:07:15.559> that<00:07:15.709> we<00:07:15.829> trying 00:07:16.059 --> 00:07:16.069 align:start position:0% all this software exists that we trying 00:07:16.069 --> 00:07:20.859 align:start position:0% all this software exists that we trying to<00:07:16.099> use<00:07:16.309> off-the-shelf<00:07:17.089> stuff<00:07:17.749> and<00:07:18.169> I<00:07:19.869> like 00:07:20.859 --> 00:07:20.869 align:start position:0% to use off-the-shelf stuff and I like 00:07:20.869 --> 00:07:23.109 align:start position:0% to use off-the-shelf stuff and I like basically<00:07:21.229> smart<00:07:21.559> people<00:07:21.860> so<00:07:22.039> all<00:07:22.849> of<00:07:23.029> this 00:07:23.109 --> 00:07:23.119 align:start position:0% basically smart people so all of this 00:07:23.119 --> 00:07:24.759 align:start position:0% basically smart people so all of this started<00:07:23.419> to<00:07:23.539> be<00:07:23.629> developed<00:07:23.659> in<00:07:24.349> order<00:07:24.499> to 00:07:24.759 --> 00:07:24.769 align:start position:0% started to be developed in order to 00:07:24.769 --> 00:07:26.589 align:start position:0% started to be developed in order to produce<00:07:25.129> our<00:07:25.369> own<00:07:25.399> products<00:07:25.969> and<00:07:26.059> better<00:07:26.389> own 00:07:26.589 --> 00:07:26.599 align:start position:0% produce our own products and better own 00:07:26.599 --> 00:07:30.890 align:start position:0% produce our own products and better own applications<00:07:27.139> which<00:07:27.349> today<00:07:27.619> my<00:07:27.919> main<00:07:28.309> area 00:07:30.890 --> 00:07:30.900 align:start position:0% 00:07:30.900 --> 00:07:38.499 align:start position:0% I<00:07:30.930> think<00:07:35.060> and<00:07:36.060> the<00:07:36.389> fact<00:07:36.570> we<00:07:36.780> don't<00:07:36.900> have<00:07:37.139> like 00:07:38.499 --> 00:07:38.509 align:start position:0% I think and the fact we don't have like 00:07:38.509 --> 00:07:40.700 align:start position:0% I think and the fact we don't have like we<00:07:39.509> have<00:07:39.600> a<00:07:39.630> lot<00:07:39.750> of<00:07:39.780> users<00:07:40.139> and<00:07:40.350> not<00:07:40.470> a<00:07:40.500> lot<00:07:40.650> of 00:07:40.700 --> 00:07:40.710 align:start position:0% we have a lot of users and not a lot of 00:07:40.710 --> 00:07:47.460 align:start position:0% we have a lot of users and not a lot of complainers<00:07:41.070> so 00:07:47.460 --> 00:07:47.470 align:start position:0% 00:07:47.470 --> 00:07:53.439 align:start position:0% [Music] 00:07:53.439 --> 00:07:53.449 align:start position:0% 00:07:53.449 --> 00:07:58.659 align:start position:0% so<00:07:54.449> just<00:07:54.689> before<00:07:55.500> we<00:07:55.680> dive<00:07:55.979> into<00:07:56.189> sort<00:07:56.550> of<00:07:56.610> like 00:07:58.659 --> 00:07:58.669 align:start position:0% so just before we dive into sort of like 00:07:58.669 --> 00:08:01.159 align:start position:0% so just before we dive into sort of like you<00:07:59.669> know<00:07:59.759> how<00:07:59.879> these<00:08:00.000> libraries<00:08:00.419> work<00:08:00.689> I<00:08:00.960> just 00:08:01.159 --> 00:08:01.169 align:start position:0% you know how these libraries work I just 00:08:01.169 --> 00:08:02.360 align:start position:0% you know how these libraries work I just wanted<00:08:01.500> to<00:08:01.590> get<00:08:01.680> a<00:08:01.740> little<00:08:02.039> bit<00:08:02.189> of<00:08:02.250> motivation 00:08:02.360 --> 00:08:02.370 align:start position:0% wanted to get a little bit of motivation 00:08:02.370 --> 00:08:06.379 align:start position:0% wanted to get a little bit of motivation for<00:08:04.219> why<00:08:05.219> we<00:08:05.400> think<00:08:05.610> it's<00:08:05.729> important<00:08:06.120> so 00:08:06.379 --> 00:08:06.389 align:start position:0% for why we think it's important so 00:08:06.389 --> 00:08:09.110 align:start position:0% for why we think it's important so Martin<00:08:07.349> show<00:08:07.560> that<00:08:07.800> we<00:08:07.949> read<00:08:08.520> Mary<00:08:08.729> started 00:08:09.110 --> 00:08:09.120 align:start position:0% Martin show that we read Mary started 00:08:09.120 --> 00:08:12.189 align:start position:0% Martin show that we read Mary started working<00:08:09.330> on<00:08:09.360> these<00:08:09.509> libraries<00:08:10.349> to<00:08:10.379> 2017<00:08:11.370> when 00:08:12.189 --> 00:08:12.199 align:start position:0% working on these libraries to 2017 when 00:08:12.199 --> 00:08:15.110 align:start position:0% working on these libraries to 2017 when home<00:08:13.199> was<00:08:13.889> new<00:08:14.370> when<00:08:14.550> we<00:08:14.699> started<00:08:15.000> developing 00:08:15.110 --> 00:08:15.120 align:start position:0% home was new when we started developing 00:08:15.120 --> 00:08:19.100 align:start position:0% home was new when we started developing what's<00:08:15.900> now<00:08:16.050> called<00:08:16.610> our<00:08:17.610> map<00:08:18.030> back<00:08:18.930> then 00:08:19.100 --> 00:08:19.110 align:start position:0% what's now called our map back then 00:08:19.110 --> 00:08:20.809 align:start position:0% what's now called our map back then called<00:08:19.349> spatial<00:08:19.620> index<00:08:20.099> that<00:08:20.250> we<00:08:20.400> were<00:08:20.520> faced 00:08:20.809 --> 00:08:20.819 align:start position:0% called spatial index that we were faced 00:08:20.819 --> 00:08:23.119 align:start position:0% called spatial index that we were faced with<00:08:21.120> we<00:08:21.689> have<00:08:21.840> a<00:08:21.870> little<00:08:22.139> bit<00:08:22.229> of<00:08:22.319> Hospital 00:08:23.119 --> 00:08:23.129 align:start position:0% with we have a little bit of Hospital 00:08:23.129 --> 00:08:24.619 align:start position:0% with we have a little bit of Hospital blockchain<00:08:23.520> experience<00:08:24.060> and<00:08:24.210> we<00:08:24.270> were<00:08:24.419> faced 00:08:24.619 --> 00:08:24.629 align:start position:0% blockchain experience and we were faced 00:08:24.629 --> 00:08:26.869 align:start position:0% blockchain experience and we were faced with<00:08:24.889> having<00:08:25.889> to<00:08:26.039> write<00:08:26.279> a<00:08:26.310> full<00:08:26.580> stack 00:08:26.869 --> 00:08:26.879 align:start position:0% with having to write a full stack 00:08:26.879 --> 00:08:29.119 align:start position:0% with having to write a full stack application<00:08:27.659> that's<00:08:28.319> no<00:08:28.529> credit 00:08:29.119 --> 00:08:29.129 align:start position:0% application that's no credit 00:08:29.129 --> 00:08:34.219 align:start position:0% application that's no credit sophisticated<00:08:29.960> mental<00:08:30.960> maps<00:08:33.169> running<00:08:34.169> the 00:08:34.219 --> 00:08:34.229 align:start position:0% sophisticated mental maps running the 00:08:34.229 --> 00:08:36.589 align:start position:0% sophisticated mental maps running the material<00:08:34.680> and<00:08:34.950> so<00:08:35.519> we've<00:08:35.969> had<00:08:36.089> a<00:08:36.149> couple<00:08:36.209> years 00:08:36.589 --> 00:08:36.599 align:start position:0% material and so we've had a couple years 00:08:36.599 --> 00:08:39.290 align:start position:0% material and so we've had a couple years and<00:08:36.899> we<00:08:37.099> back<00:08:38.099> then<00:08:38.310> decided<00:08:38.789> that<00:08:38.820> like<00:08:39.089> it's 00:08:39.290 --> 00:08:39.300 align:start position:0% and we back then decided that like it's 00:08:39.300 --> 00:08:41.360 align:start position:0% and we back then decided that like it's worth<00:08:39.659> doing<00:08:40.110> the<00:08:40.140> upfront<00:08:40.440> investment<00:08:41.039> to 00:08:41.360 --> 00:08:41.370 align:start position:0% worth doing the upfront investment to 00:08:41.370 --> 00:08:43.279 align:start position:0% worth doing the upfront investment to develop<00:08:41.700> these<00:08:42.089> libraries<00:08:42.570> for<00:08:43.140> the 00:08:43.279 --> 00:08:43.289 align:start position:0% develop these libraries for the 00:08:43.289 --> 00:08:44.660 align:start position:0% develop these libraries for the front-end<00:08:43.680> side<00:08:43.919> as<00:08:44.130> well<00:08:44.310> as<00:08:44.370> the<00:08:44.459> backend 00:08:44.660 --> 00:08:44.670 align:start position:0% front-end side as well as the backend 00:08:44.670 --> 00:08:46.759 align:start position:0% front-end side as well as the backend instead<00:08:45.540> of<00:08:45.690> using<00:08:45.959> established 00:08:46.759 --> 00:08:46.769 align:start position:0% instead of using established 00:08:46.769 --> 00:08:50.500 align:start position:0% instead of using established technologies<00:08:47.250> and<00:08:47.370> I<00:08:47.430> guess<00:08:47.579> the<00:08:48.180> the<00:08:48.380> recent 00:08:50.500 --> 00:08:50.510 align:start position:0% technologies and I guess the the recent 00:08:50.510 --> 00:08:52.639 align:start position:0% technologies and I guess the the recent before<00:08:51.510> why<00:08:51.660> we're<00:08:51.839> still<00:08:52.019> happy<00:08:52.260> with<00:08:52.529> that 00:08:52.639 --> 00:08:52.649 align:start position:0% before why we're still happy with that 00:08:52.649 --> 00:08:54.230 align:start position:0% before why we're still happy with that and<00:08:52.890> like<00:08:53.279> to<00:08:53.519> invite<00:08:53.700> you<00:08:53.850> to<00:08:53.880> use<00:08:54.089> these 00:08:54.230 --> 00:08:54.240 align:start position:0% and like to invite you to use these 00:08:54.240 --> 00:08:57.800 align:start position:0% and like to invite you to use these tools<00:08:54.540> as<00:08:54.690> well<00:08:54.870> is<00:08:55.110> that<00:08:56.300> we<00:08:57.300> are<00:08:57.630> basically 00:08:57.800 --> 00:08:57.810 align:start position:0% tools as well is that we are basically 00:08:57.810 --> 00:09:00.230 align:start position:0% tools as well is that we are basically now<00:08:58.199> a<00:08:58.230> small<00:08:58.560> operation<00:08:58.949> vertical<00:08:59.610> for<00:09:00.029> five 00:09:00.230 --> 00:09:00.240 align:start position:0% now a small operation vertical for five 00:09:00.240 --> 00:09:02.090 align:start position:0% now a small operation vertical for five developers<00:09:00.779> working<00:09:01.320> mostly<00:09:01.529> other<00:09:01.680> things 00:09:02.090 --> 00:09:02.100 align:start position:0% developers working mostly other things 00:09:02.100 --> 00:09:05.900 align:start position:0% developers working mostly other things at<00:09:02.250> this<00:09:02.339> point<00:09:02.570> and<00:09:03.570> we<00:09:03.990> have<00:09:04.260> the<00:09:04.910> basically 00:09:05.900 --> 00:09:05.910 align:start position:0% at this point and we have the basically 00:09:05.910 --> 00:09:07.350 align:start position:0% at this point and we have the basically typesafe<00:09:06.390> develop<00:09:06.839> different 00:09:07.350 --> 00:09:07.360 align:start position:0% typesafe develop different 00:09:07.360 --> 00:09:11.039 align:start position:0% typesafe develop different another<00:09:07.749> we're<00:09:08.559> generating<00:09:08.949> code<00:09:09.309> from<00:09:10.049> you 00:09:11.039 --> 00:09:11.049 align:start position:0% another we're generating code from you 00:09:11.049 --> 00:09:13.769 align:start position:0% another we're generating code from you know<00:09:11.170> our<00:09:11.199> stuff<00:09:11.790> the<00:09:12.790> solidity<00:09:13.179> can<00:09:13.360> generate 00:09:13.769 --> 00:09:13.779 align:start position:0% know our stuff the solidity can generate 00:09:13.779 --> 00:09:16.350 align:start position:0% know our stuff the solidity can generate kinds<00:09:14.259> of<00:09:14.379> binding<00:09:15.129> the<00:09:15.399> back<00:09:15.759> end<00:09:16.029> and<00:09:16.299> the 00:09:16.350 --> 00:09:16.360 align:start position:0% kinds of binding the back end and the 00:09:16.360 --> 00:09:19.859 align:start position:0% kinds of binding the back end and the front<00:09:16.509> end<00:09:17.399> because<00:09:18.399> we're<00:09:18.970> using<00:09:19.600> these 00:09:19.859 --> 00:09:19.869 align:start position:0% front end because we're using these 00:09:19.869 --> 00:09:21.720 align:start position:0% front end because we're using these strongly<00:09:20.199> typed<00:09:20.410> languages<00:09:20.889> these<00:09:21.220> bindings 00:09:21.720 --> 00:09:21.730 align:start position:0% strongly typed languages these bindings 00:09:21.730 --> 00:09:24.419 align:start position:0% strongly typed languages these bindings are<00:09:21.999> also<00:09:22.720> have<00:09:22.989> a<00:09:23.019> tiny<00:09:23.259> straight<00:09:23.709> so<00:09:24.309> that 00:09:24.419 --> 00:09:24.429 align:start position:0% are also have a tiny straight so that 00:09:24.429 --> 00:09:26.609 align:start position:0% are also have a tiny straight so that means<00:09:24.610> that<00:09:24.819> the<00:09:25.029> compiler<00:09:25.600> will<00:09:25.749> tell<00:09:26.110> us<00:09:26.319> if 00:09:26.609 --> 00:09:26.619 align:start position:0% means that the compiler will tell us if 00:09:26.619 --> 00:09:28.289 align:start position:0% means that the compiler will tell us if we've<00:09:26.889> changed<00:09:27.189> something<00:09:27.759> on<00:09:27.879> one<00:09:28.029> end<00:09:28.239> of 00:09:28.289 --> 00:09:28.299 align:start position:0% we've changed something on one end of 00:09:28.299 --> 00:09:30.239 align:start position:0% we've changed something on one end of the<00:09:28.420> step<00:09:28.629> and<00:09:28.839> the<00:09:29.529> rest<00:09:29.739> of<00:09:29.860> the<00:09:29.949> stack<00:09:30.129> to 00:09:30.239 --> 00:09:30.249 align:start position:0% the step and the rest of the stack to 00:09:30.249 --> 00:09:33.329 align:start position:0% the step and the rest of the stack to the<00:09:30.339> Pennsylvania<00:09:30.699> hasn't<00:09:31.689> made<00:09:32.339> Rebecca 00:09:33.329 --> 00:09:33.339 align:start position:0% the Pennsylvania hasn't made Rebecca 00:09:33.339 --> 00:09:35.699 align:start position:0% the Pennsylvania hasn't made Rebecca changes<00:09:33.910> and<00:09:34.329> because<00:09:34.899> it's<00:09:35.079> not<00:09:35.259> just<00:09:35.529> like 00:09:35.699 --> 00:09:35.709 align:start position:0% changes and because it's not just like 00:09:35.709 --> 00:09:37.710 align:start position:0% changes and because it's not just like matching<00:09:36.189> word<00:09:36.429> by<00:09:36.639> word<00:09:36.879> or<00:09:37.149> County<00:09:37.569> however 00:09:37.710 --> 00:09:37.720 align:start position:0% matching word by word or County however 00:09:37.720 --> 00:09:39.389 align:start position:0% matching word by word or County however Oregon's<00:09:38.170> that's<00:09:38.410> been<00:09:38.589> very<00:09:38.769> able<00:09:38.889> to<00:09:39.069> encode 00:09:39.389 --> 00:09:39.399 align:start position:0% Oregon's that's been very able to encode 00:09:39.399 --> 00:09:42.179 align:start position:0% Oregon's that's been very able to encode a<00:09:39.459> lot<00:09:39.670> of<00:09:39.759> the<00:09:39.879> actual<00:09:40.679> behavior<00:09:41.679> of<00:09:42.100> those 00:09:42.179 --> 00:09:42.189 align:start position:0% a lot of the actual behavior of those 00:09:42.189 --> 00:09:44.970 align:start position:0% a lot of the actual behavior of those functions<00:09:42.549> we<00:09:43.209> get<00:09:43.509> a<00:09:43.779> lot<00:09:44.259> of<00:09:44.290> safety<00:09:44.589> when 00:09:44.970 --> 00:09:44.980 align:start position:0% functions we get a lot of safety when 00:09:44.980 --> 00:09:47.879 align:start position:0% functions we get a lot of safety when deployed<00:09:45.339> and<00:09:45.610> so<00:09:45.879> this<00:09:46.559> you<00:09:47.559> know<00:09:47.679> we're<00:09:47.829> not 00:09:47.879 --> 00:09:47.889 align:start position:0% deployed and so this you know we're not 00:09:47.889 --> 00:09:49.259 align:start position:0% deployed and so this you know we're not in<00:09:48.009> the<00:09:48.069> camera<00:09:48.399> we're<00:09:48.549> saying<00:09:48.730> don't<00:09:49.089> write 00:09:49.259 --> 00:09:49.269 align:start position:0% in the camera we're saying don't write 00:09:49.269 --> 00:09:51.900 align:start position:0% in the camera we're saying don't write tests<00:09:49.629> anymore<00:09:49.989> but<00:09:50.199> the<00:09:50.860> types<00:09:51.309> of<00:09:51.670> the 00:09:51.900 --> 00:09:51.910 align:start position:0% tests anymore but the types of the 00:09:51.910 --> 00:09:53.900 align:start position:0% tests anymore but the types of the compiler<00:09:52.420> and<00:09:52.629> type<00:09:52.899> checking<00:09:53.199> our 00:09:53.900 --> 00:09:53.910 align:start position:0% compiler and type checking our 00:09:53.910 --> 00:09:56.699 align:start position:0% compiler and type checking our integration<00:09:54.910> effectively<00:09:55.899> in<00:09:55.959> my<00:09:56.110> eliminates 00:09:56.699 --> 00:09:56.709 align:start position:0% integration effectively in my eliminates 00:09:56.709 --> 00:10:01.949 align:start position:0% integration effectively in my eliminates a<00:09:56.799> whole<00:09:57.089> and<00:09:58.649> this<00:09:59.649> has<00:10:00.220> pretty<00:10:00.999> well<00:10:01.119> very 00:10:01.949 --> 00:10:01.959 align:start position:0% a whole and this has pretty well very 00:10:01.959 --> 00:10:06.359 align:start position:0% a whole and this has pretty well very creative<00:10:02.819> application<00:10:04.860> another<00:10:05.860> point<00:10:06.309> that 00:10:06.359 --> 00:10:06.369 align:start position:0% creative application another point that 00:10:06.369 --> 00:10:09.030 align:start position:0% creative application another point that I<00:10:06.819> don't<00:10:07.149> think<00:10:07.629> we'll<00:10:07.779> get<00:10:07.959> to<00:10:08.019> it<00:10:08.290> to<00:10:08.649> show<00:10:08.889> it 00:10:09.030 --> 00:10:09.040 align:start position:0% I don't think we'll get to it to show it 00:10:09.040 --> 00:10:10.679 align:start position:0% I don't think we'll get to it to show it here<00:10:09.069> but<00:10:09.249> one<00:10:09.549> of<00:10:09.579> the<00:10:09.759> really<00:10:10.149> beautiful 00:10:10.679 --> 00:10:10.689 align:start position:0% here but one of the really beautiful 00:10:10.689 --> 00:10:13.409 align:start position:0% here but one of the really beautiful aspects<00:10:11.589> of<00:10:11.799> the<00:10:12.009> hospital<00:10:12.910> part<00:10:13.119> of<00:10:13.179> this<00:10:13.269> is 00:10:13.409 --> 00:10:13.419 align:start position:0% aspects of the hospital part of this is 00:10:13.419 --> 00:10:17.039 align:start position:0% aspects of the hospital part of this is that<00:10:13.629> our<00:10:14.169> mobile<00:10:14.410> API<00:10:14.769> is<00:10:15.399> a<00:10:15.639> title<00:10:16.360> so<00:10:16.660> that 00:10:17.039 --> 00:10:17.049 align:start position:0% that our mobile API is a title so that 00:10:17.049 --> 00:10:20.280 align:start position:0% that our mobile API is a title so that means<00:10:18.009> that<00:10:18.309> the<00:10:18.699> compiler<00:10:19.290> compiler 00:10:20.280 --> 00:10:20.290 align:start position:0% means that the compiler compiler 00:10:20.290 --> 00:10:21.659 align:start position:0% means that the compiler compiler understands<00:10:20.709> the<00:10:20.799> type<00:10:21.069> you<00:10:21.220> can<00:10:21.369> reason 00:10:21.659 --> 00:10:21.669 align:start position:0% understands the type you can reason 00:10:21.669 --> 00:10:23.069 align:start position:0% understands the type you can reason about<00:10:21.699> it<00:10:21.999> but<00:10:22.149> so<00:10:22.299> it<00:10:22.449> it<00:10:22.569> effectively 00:10:23.069 --> 00:10:23.079 align:start position:0% about it but so it it effectively 00:10:23.079 --> 00:10:26.369 align:start position:0% about it but so it it effectively generates<00:10:23.739> all<00:10:24.399> applause<00:10:25.179> or<00:10:25.389> take<00:10:25.569> most<00:10:26.199> of 00:10:26.369 --> 00:10:26.379 align:start position:0% generates all applause or take most of 00:10:26.379 --> 00:10:28.799 align:start position:0% generates all applause or take most of our<00:10:26.499> bindings<00:10:27.100> compiler<00:10:28.089> does<00:10:28.269> that<00:10:28.449> for<00:10:28.689> us 00:10:28.799 --> 00:10:28.809 align:start position:0% our bindings compiler does that for us 00:10:28.809 --> 00:10:31.379 align:start position:0% our bindings compiler does that for us and<00:10:29.739> that<00:10:29.829> means<00:10:30.009> that<00:10:30.129> we<00:10:30.369> do<00:10:30.669> get<00:10:30.879> so<00:10:31.179> we 00:10:31.379 --> 00:10:31.389 align:start position:0% and that means that we do get so we 00:10:31.389 --> 00:10:34.439 align:start position:0% and that means that we do get so we expose<00:10:31.809> our<00:10:32.249> production<00:10:33.249> API<00:10:33.910> in<00:10:34.119> terms<00:10:34.299> of 00:10:34.439 --> 00:10:34.449 align:start position:0% expose our production API in terms of 00:10:34.449 --> 00:10:36.340 align:start position:0% expose our production API in terms of swagger<00:10:35.350> definition<00:10:35.889> which<00:10:36.069> is 00:10:36.340 --> 00:10:36.350 align:start position:0% swagger definition which is 00:10:36.350 --> 00:10:38.200 align:start position:0% swagger definition which is a<00:10:36.380> standard<00:10:36.770> for<00:10:36.920> exposing<00:10:37.280> it<00:10:37.370> yet<00:10:37.580> we<00:10:38.000> didn't 00:10:38.200 --> 00:10:38.210 align:start position:0% a standard for exposing it yet we didn't 00:10:38.210 --> 00:10:39.520 align:start position:0% a standard for exposing it yet we didn't write<00:10:38.360> that<00:10:38.540> that's<00:10:38.690> generated<00:10:39.380> by<00:10:39.410> the 00:10:39.520 --> 00:10:39.530 align:start position:0% write that that's generated by the 00:10:39.530 --> 00:10:41.860 align:start position:0% write that that's generated by the compiler<00:10:39.920> every<00:10:40.310> time<00:10:40.520> we<00:10:40.700> deploy<00:10:40.970> we<00:10:41.600> use 00:10:41.860 --> 00:10:41.870 align:start position:0% compiler every time we deploy we use 00:10:41.870 --> 00:10:44.590 align:start position:0% compiler every time we deploy we use that<00:10:42.110> internally<00:10:42.770> but<00:10:42.920> other<00:10:43.640> companies<00:10:44.180> use 00:10:44.590 --> 00:10:44.600 align:start position:0% that internally but other companies use 00:10:44.600 --> 00:10:46.600 align:start position:0% that internally but other companies use the<00:10:44.780> same<00:10:45.080> swagger<00:10:45.500> definition<00:10:46.040> to<00:10:46.220> integrate 00:10:46.600 --> 00:10:46.610 align:start position:0% the same swagger definition to integrate 00:10:46.610 --> 00:10:48.910 align:start position:0% the same swagger definition to integrate products<00:10:46.910> so<00:10:47.450> they<00:10:47.690> have<00:10:47.960> the<00:10:48.110> same<00:10:48.320> level<00:10:48.800> of 00:10:48.910 --> 00:10:48.920 align:start position:0% products so they have the same level of 00:10:48.920 --> 00:10:51.520 align:start position:0% products so they have the same level of this<00:10:49.040> you<00:10:49.280> know<00:10:50.140> guarantees<00:10:51.140> that<00:10:51.170> our 00:10:51.520 --> 00:10:51.530 align:start position:0% this you know guarantees that our 00:10:51.530 --> 00:10:56.260 align:start position:0% this you know guarantees that our salesmen<00:10:52.010> so<00:10:52.660> recently<00:10:54.730> we've<00:10:55.730> had<00:10:55.790> a<00:10:55.970> couple 00:10:56.260 --> 00:10:56.270 align:start position:0% salesmen so recently we've had a couple 00:10:56.270 --> 00:10:59.470 align:start position:0% salesmen so recently we've had a couple of<00:10:56.650> sort<00:10:57.650> of<00:10:57.710> great<00:10:58.520> integration<00:10:58.940> have<00:10:59.300> been 00:10:59.470 --> 00:10:59.480 align:start position:0% of sort of great integration have been 00:10:59.480 --> 00:11:00.820 align:start position:0% of sort of great integration have been completed<00:10:59.930> without<00:10:59.990> our<00:11:00.350> council<00:11:00.650> so<00:11:00.770> you 00:11:00.820 --> 00:11:00.830 align:start position:0% completed without our council so you 00:11:00.830 --> 00:11:03.490 align:start position:0% completed without our council so you know<00:11:01.190> like<00:11:01.460> telegram<00:11:02.180> you<00:11:03.170> know<00:11:03.260> health 00:11:03.490 --> 00:11:03.500 align:start position:0% know like telegram you know health 00:11:03.500 --> 00:11:06.310 align:start position:0% know like telegram you know health channels<00:11:03.920> or<00:11:04.220> create<00:11:04.690> we're<00:11:05.690> just<00:11:05.840> exposing 00:11:06.310 --> 00:11:06.320 align:start position:0% channels or create we're just exposing 00:11:06.320 --> 00:11:08.410 align:start position:0% channels or create we're just exposing this<00:11:06.410> API<00:11:06.740> in<00:11:07.460> the<00:11:07.580> generative<00:11:08.000> Dobson's 00:11:08.410 --> 00:11:08.420 align:start position:0% this API in the generative Dobson's 00:11:08.420 --> 00:11:11.230 align:start position:0% this API in the generative Dobson's we've<00:11:08.660> had<00:11:09.040> recently<00:11:10.040> an<00:11:10.790> Android 00:11:11.230 --> 00:11:11.240 align:start position:0% we've had recently an Android 00:11:11.240 --> 00:11:14.080 align:start position:0% we've had recently an Android application<00:11:11.840> that<00:11:12.340> knows<00:11:13.340> the<00:11:13.490> safe<00:11:13.730> and<00:11:13.970> use 00:11:14.080 --> 00:11:14.090 align:start position:0% application that knows the safe and use 00:11:14.090 --> 00:11:18.610 align:start position:0% application that knows the safe and use this<00:11:14.240> phone<00:11:14.920> for<00:11:15.920> locating<00:11:16.580> points<00:11:17.590> so<00:11:18.590> you 00:11:18.610 --> 00:11:18.620 align:start position:0% this phone for locating points so you 00:11:18.620 --> 00:11:20.530 align:start position:0% this phone for locating points so you need<00:11:18.890> time<00:11:19.460> different<00:11:19.730> when<00:11:19.910> sophisticated 00:11:20.530 --> 00:11:20.540 align:start position:0% need time different when sophisticated 00:11:20.540 --> 00:11:23.290 align:start position:0% need time different when sophisticated like<00:11:20.690> recover<00:11:21.050> your<00:11:21.260> wallet<00:11:21.910> they<00:11:22.910> want<00:11:23.120> some 00:11:23.290 --> 00:11:23.300 align:start position:0% like recover your wallet they want some 00:11:23.300 --> 00:11:26.140 align:start position:0% like recover your wallet they want some hackathon<00:11:23.930> there's<00:11:24.530> an<00:11:24.710> upcoming<00:11:25.150> chaining 00:11:26.140 --> 00:11:26.150 align:start position:0% hackathon there's an upcoming chaining 00:11:26.150 --> 00:11:29.020 align:start position:0% hackathon there's an upcoming chaining integration<00:11:27.020> that<00:11:27.290> uses<00:11:27.950> cross<00:11:28.160> chains<00:11:28.460> both 00:11:29.020 --> 00:11:29.030 align:start position:0% integration that uses cross chains both 00:11:29.030 --> 00:11:36.100 align:start position:0% integration that uses cross chains both maintenance<00:11:29.690> and<00:11:29.960> hold<00:11:30.410> on<00:11:34.270> from<00:11:35.270> our<00:11:35.450> API<00:11:35.720> and 00:11:36.100 --> 00:11:36.110 align:start position:0% maintenance and hold on from our API and 00:11:36.110 --> 00:11:38.980 align:start position:0% maintenance and hold on from our API and actually<00:11:37.100> part<00:11:37.400> of<00:11:37.490> our<00:11:37.610> host<00:11:37.790> we<00:11:38.660> don't<00:11:38.840> have 00:11:38.980 --> 00:11:38.990 align:start position:0% actually part of our host we don't have 00:11:38.990 --> 00:11:40.690 align:start position:0% actually part of our host we don't have the<00:11:39.170> ability<00:11:39.530> to<00:11:39.560> write<00:11:39.920> applications<00:11:40.190> for 00:11:40.690 --> 00:11:40.700 align:start position:0% the ability to write applications for 00:11:40.700 --> 00:11:42.250 align:start position:0% the ability to write applications for every<00:11:40.790> use<00:11:41.060> case<00:11:41.180> so<00:11:41.750> we<00:11:41.870> actually<00:11:42.110> have<00:11:42.230> a 00:11:42.250 --> 00:11:42.260 align:start position:0% every use case so we actually have a 00:11:42.260 --> 00:11:44.410 align:start position:0% every use case so we actually have a user<00:11:42.500> community<00:11:43.160> that<00:11:43.340> builds<00:11:43.580> applications 00:11:44.410 --> 00:11:44.420 align:start position:0% user community that builds applications 00:11:44.420 --> 00:11:47.530 align:start position:0% user community that builds applications for<00:11:44.690> us<00:11:44.870> to<00:11:45.110> serve<00:11:45.380> our<00:11:45.410> users<00:11:45.980> and<00:11:46.370> again<00:11:46.940> very 00:11:47.530 --> 00:11:47.540 align:start position:0% for us to serve our users and again very 00:11:47.540 --> 00:11:49.390 align:start position:0% for us to serve our users and again very little<00:11:47.660> support<00:11:47.900> so<00:11:48.350> that's<00:11:48.860> kind<00:11:49.190> of<00:11:49.250> why 00:11:49.390 --> 00:11:49.400 align:start position:0% little support so that's kind of why 00:11:49.400 --> 00:11:51.760 align:start position:0% little support so that's kind of why this<00:11:49.460> tools<00:11:50.120> will<00:11:50.420> only<00:11:50.570> help<00:11:50.720> our<00:11:50.960> large 00:11:51.760 --> 00:11:51.770 align:start position:0% this tools will only help our large 00:11:51.770 --> 00:11:54.010 align:start position:0% this tools will only help our large learning<00:11:52.180> professionals<00:11:53.180> they<00:11:53.570> really<00:11:53.810> pay 00:11:54.010 --> 00:11:54.020 align:start position:0% learning professionals they really pay 00:11:54.020 --> 00:11:59.770 align:start position:0% learning professionals they really pay off<00:11:54.050> once<00:11:54.410> you<00:11:54.530> have<00:11:54.650> a<00:11:54.680> big<00:11:58.180> yeah<00:11:59.180> we<00:11:59.630> can 00:11:59.770 --> 00:11:59.780 align:start position:0% off once you have a big yeah we can 00:11:59.780 --> 00:12:01.040 align:start position:0% off once you have a big yeah we can probably<00:11:59.870> skip<00:12:00.320> this 00:12:01.040 --> 00:12:01.050 align:start position:0% probably skip this 00:12:01.050 --> 00:12:02.720 align:start position:0% probably skip this or<00:12:01.140> whatever<00:12:01.350> but<00:12:01.560> I<00:12:01.620> will<00:12:01.860> say<00:12:02.070> that<00:12:02.279> like<00:12:02.459> I 00:12:02.720 --> 00:12:02.730 align:start position:0% or whatever but I will say that like I 00:12:02.730 --> 00:12:06.680 align:start position:0% or whatever but I will say that like I had<00:12:03.560> to<00:12:04.560> work<00:12:04.709> so<00:12:04.950> yeah<00:12:05.850> people<00:12:06.089> you<00:12:06.600> know 00:12:06.680 --> 00:12:06.690 align:start position:0% had to work so yeah people you know 00:12:06.690 --> 00:12:10.670 align:start position:0% had to work so yeah people you know there's<00:12:07.170> like<00:12:07.380> a<00:12:08.000> smoothie<00:12:09.050> medium<00:12:10.050> hangover 00:12:10.670 --> 00:12:10.680 align:start position:0% there's like a smoothie medium hangover 00:12:10.680 --> 00:12:13.070 align:start position:0% there's like a smoothie medium hangover and<00:12:11.040> Hitler<00:12:11.399> kind<00:12:11.610> of<00:12:11.670> like<00:12:11.820> look<00:12:12.080> these 00:12:13.070 --> 00:12:13.080 align:start position:0% and Hitler kind of like look these 00:12:13.080 --> 00:12:14.329 align:start position:0% and Hitler kind of like look these things<00:12:13.140> are<00:12:13.470> talking<00:12:13.740> about<00:12:13.920> like<00:12:14.100> five 00:12:14.329 --> 00:12:14.339 align:start position:0% things are talking about like five 00:12:14.339 --> 00:12:16.340 align:start position:0% things are talking about like five Assembly<00:12:14.850> there<00:12:15.480> are<00:12:15.570> various<00:12:15.899> states<00:12:16.230> of 00:12:16.340 --> 00:12:16.350 align:start position:0% Assembly there are various states of 00:12:16.350 --> 00:12:18.230 align:start position:0% Assembly there are various states of development<00:12:16.830> on<00:12:16.890> those<00:12:17.070> things<00:12:17.339> you<00:12:18.120> know 00:12:18.230 --> 00:12:18.240 align:start position:0% development on those things you know 00:12:18.240 --> 00:12:21.590 align:start position:0% development on those things you know okay<00:12:18.570> flakes 00:12:21.590 --> 00:12:21.600 align:start position:0% 00:12:21.600 --> 00:12:23.360 align:start position:0% or<00:12:22.080> even<00:12:22.290> like<00:12:22.410> in<00:12:22.560> the<00:12:22.650> area<00:12:23.100> of<00:12:23.220> like 00:12:23.360 --> 00:12:23.370 align:start position:0% or even like in the area of like 00:12:23.370 --> 00:12:24.980 align:start position:0% or even like in the area of like application-specific<00:12:24.030> watching<00:12:24.690> people 00:12:24.980 --> 00:12:24.990 align:start position:0% application-specific watching people 00:12:24.990 --> 00:12:26.510 align:start position:0% application-specific watching people were<00:12:25.050> looking<00:12:25.320> at<00:12:25.470> not<00:12:25.920> even<00:12:26.100> having<00:12:26.310> to<00:12:26.370> worry 00:12:26.510 --> 00:12:26.520 align:start position:0% were looking at not even having to worry 00:12:26.520 --> 00:12:29.150 align:start position:0% were looking at not even having to worry about<00:12:26.580> this<00:12:27.060> entirely<00:12:27.570> things<00:12:28.320> like<00:12:28.500> Cosmo 00:12:29.150 --> 00:12:29.160 align:start position:0% about this entirely things like Cosmo 00:12:29.160 --> 00:12:33.470 align:start position:0% about this entirely things like Cosmo specifically<00:12:30.150> right<00:12:30.300> now<00:12:32.360> that<00:12:33.360> you're 00:12:33.470 --> 00:12:33.480 align:start position:0% specifically right now that you're 00:12:33.480 --> 00:12:35.120 align:start position:0% specifically right now that you're giving<00:12:33.810> like<00:12:33.960> a<00:12:33.990> good<00:12:34.470> variety<00:12:34.740> of<00:12:34.860> choices 00:12:35.120 --> 00:12:35.130 align:start position:0% giving like a good variety of choices 00:12:35.130 --> 00:12:37.400 align:start position:0% giving like a good variety of choices it's<00:12:35.520> kind<00:12:35.760> of<00:12:35.820> like<00:12:36.000> well<00:12:36.420> don't<00:12:37.200> make<00:12:37.320> the 00:12:37.400 --> 00:12:37.410 align:start position:0% it's kind of like well don't make the 00:12:37.410 --> 00:12:42.940 align:start position:0% it's kind of like well don't make the same<00:12:37.620> mistake<00:12:37.890> twice<00:12:38.060> peso 00:12:42.940 --> 00:12:42.950 align:start position:0% 00:12:42.950 --> 00:12:44.440 align:start position:0% also<00:12:43.550> there's<00:12:43.730> like<00:12:43.910> probably<00:12:44.149> some 00:12:44.440 --> 00:12:44.450 align:start position:0% also there's like probably some 00:12:44.450 --> 00:12:45.850 align:start position:0% also there's like probably some confusion<00:12:44.899> because<00:12:44.990> appear<00:12:45.410> script<00:12:45.620> it's<00:12:45.769> not 00:12:45.850 --> 00:12:45.860 align:start position:0% confusion because appear script it's not 00:12:45.860 --> 00:12:48.100 align:start position:0% confusion because appear script it's not really<00:12:46.070> a<00:12:46.100> planet<00:12:46.310> language<00:12:46.820> the<00:12:47.510> imperative 00:12:48.100 --> 00:12:48.110 align:start position:0% really a planet language the imperative 00:12:48.110 --> 00:12:51.250 align:start position:0% really a planet language the imperative Pascal<00:12:49.060> which<00:12:50.060> molecular<00:12:50.690> pertaineth 00:12:51.250 --> 00:12:51.260 align:start position:0% Pascal which molecular pertaineth 00:12:51.260 --> 00:12:53.199 align:start position:0% Pascal which molecular pertaineth hospital<00:12:52.220> is<00:12:52.310> kind<00:12:52.519> of<00:12:52.550> like<00:12:52.700> more<00:12:52.940> of<00:12:53.000> this 00:12:53.199 --> 00:12:53.209 align:start position:0% hospital is kind of like more of this 00:12:53.209 --> 00:12:54.850 align:start position:0% hospital is kind of like more of this big<00:12:53.420> point<00:12:53.750> means<00:12:53.959> like<00:12:54.170> the<00:12:54.320> family<00:12:54.769> of 00:12:54.850 --> 00:12:54.860 align:start position:0% big point means like the family of 00:12:54.860 --> 00:12:56.680 align:start position:0% big point means like the family of languages<00:12:55.190> and<00:12:55.550> it<00:12:55.639> does<00:12:55.790> even<00:12:55.970> one<00:12:56.089> specific 00:12:56.680 --> 00:12:56.690 align:start position:0% languages and it does even one specific 00:12:56.690 --> 00:12:58.389 align:start position:0% languages and it does even one specific thing<00:12:56.720> so<00:12:57.050> they're<00:12:57.290> talking<00:12:58.160> about<00:12:58.310> a 00:12:58.389 --> 00:12:58.399 align:start position:0% thing so they're talking about a 00:12:58.399 --> 00:13:00.519 align:start position:0% thing so they're talking about a hospital<00:12:59.060> it<00:12:59.510> just<00:12:59.540> means<00:12:59.839> like<00:12:59.930> the<00:13:00.199> language 00:13:00.519 --> 00:13:00.529 align:start position:0% hospital it just means like the language 00:13:00.529 --> 00:13:02.410 align:start position:0% hospital it just means like the language which<00:13:00.680> has<00:13:00.800> a<00:13:00.860> similar<00:13:01.160> type<00:13:01.579> system<00:13:01.940> up<00:13:02.240> to<00:13:02.389> a 00:13:02.410 --> 00:13:02.420 align:start position:0% which has a similar type system up to a 00:13:02.420 --> 00:13:04.060 align:start position:0% which has a similar type system up to a certain<00:13:02.660> point<00:13:02.810> and<00:13:03.529> there<00:13:03.709> are<00:13:03.769> some<00:13:03.949> more 00:13:04.060 --> 00:13:04.070 align:start position:0% certain point and there are some more 00:13:04.070 --> 00:13:08.560 align:start position:0% certain point and there are some more syntax<00:13:05.050> so<00:13:06.730> basically<00:13:07.730> like<00:13:07.970> pure<00:13:08.209> script<00:13:08.449> is 00:13:08.560 --> 00:13:08.570 align:start position:0% syntax so basically like pure script is 00:13:08.570 --> 00:13:10.620 align:start position:0% syntax so basically like pure script is an<00:13:08.720> opinionated<00:13:09.139> dialect<00:13:09.740> and<00:13:09.860> Pascal<00:13:10.250> it<00:13:10.399> was 00:13:10.620 --> 00:13:10.630 align:start position:0% an opinionated dialect and Pascal it was 00:13:10.630 --> 00:13:13.000 align:start position:0% an opinionated dialect and Pascal it was created<00:13:11.630> the<00:13:11.870> compiler<00:13:12.290> first<00:13:12.470> compiler<00:13:12.889> was 00:13:13.000 --> 00:13:13.010 align:start position:0% created the compiler first compiler was 00:13:13.010 --> 00:13:16.090 align:start position:0% created the compiler first compiler was written<00:13:13.370> in<00:13:13.490> 2013<00:13:14.209> so<00:13:15.110> like<00:13:15.440> to<00:13:15.620> compare<00:13:15.920> with 00:13:16.090 --> 00:13:16.100 align:start position:0% written in 2013 so like to compare with 00:13:16.100 --> 00:13:17.319 align:start position:0% written in 2013 so like to compare with other<00:13:16.250> things<00:13:16.459> that<00:13:16.579> people<00:13:16.610> know<00:13:16.910> about<00:13:16.940> like 00:13:17.319 --> 00:13:17.329 align:start position:0% other things that people know about like 00:13:17.329 --> 00:13:18.970 align:start position:0% other things that people know about like type<00:13:17.540> script<00:13:17.779> are<00:13:17.990> no<00:13:18.139> words<00:13:18.560> are<00:13:18.800> the<00:13:18.920> same 00:13:18.970 --> 00:13:18.980 align:start position:0% type script are no words are the same 00:13:18.980 --> 00:13:21.790 align:start position:0% type script are no words are the same like<00:13:19.339> family<00:13:19.760> of<00:13:20.199> functioning<00:13:21.199> languages<00:13:21.620> but 00:13:21.790 --> 00:13:21.800 align:start position:0% like family of functioning languages but 00:13:21.800 --> 00:13:25.210 align:start position:0% like family of functioning languages but alright<00:13:22.639> sorry<00:13:22.850> not<00:13:23.000> text<00:13:23.269> for<00:13:23.420> fidelity<00:13:24.220> but 00:13:25.210 --> 00:13:25.220 align:start position:0% alright sorry not text for fidelity but 00:13:25.220 --> 00:13:27.699 align:start position:0% alright sorry not text for fidelity but are<00:13:25.370> comparatively<00:13:25.850> much<00:13:26.120> weaker<00:13:26.709> they're 00:13:27.699 --> 00:13:27.709 align:start position:0% are comparatively much weaker they're 00:13:27.709 --> 00:13:29.530 align:start position:0% are comparatively much weaker they're roughly<00:13:28.160> the<00:13:28.279> same<00:13:28.490> age<00:13:28.670> this<00:13:29.000> is<00:13:29.149> enough<00:13:29.389> this 00:13:29.530 --> 00:13:29.540 align:start position:0% roughly the same age this is enough this 00:13:29.540 --> 00:13:31.110 align:start position:0% roughly the same age this is enough this is<00:13:29.660> also<00:13:29.810> not<00:13:30.019> something<00:13:30.230> like<00:13:30.410> a<00:13:30.470> new 00:13:31.110 --> 00:13:31.120 align:start position:0% is also not something like a new 00:13:31.120 --> 00:13:35.110 align:start position:0% is also not something like a new framework<00:13:32.120> for<00:13:32.240> this<00:13:32.570> week<00:13:32.810> and<00:13:34.120> basically 00:13:35.110 --> 00:13:35.120 align:start position:0% framework for this week and basically 00:13:35.120 --> 00:13:37.509 align:start position:0% framework for this week and basically likes<00:13:35.660> it<00:13:35.959> said<00:13:36.170> language<00:13:36.560> itself<00:13:36.980> simplifies 00:13:37.509 --> 00:13:37.519 align:start position:0% likes it said language itself simplifies 00:13:37.519 --> 00:13:39.759 align:start position:0% likes it said language itself simplifies distills<00:13:38.269> a<00:13:38.420> lot<00:13:38.540> of<00:13:38.630> concepts<00:13:39.079> from<00:13:39.290> Pascal 00:13:39.759 --> 00:13:39.769 align:start position:0% distills a lot of concepts from Pascal 00:13:39.769 --> 00:13:41.230 align:start position:0% distills a lot of concepts from Pascal that<00:13:39.889> were<00:13:40.130> learned<00:13:40.430> over<00:13:40.790> a<00:13:40.820> really<00:13:41.000> long 00:13:41.230 --> 00:13:41.240 align:start position:0% that were learned over a really long 00:13:41.240 --> 00:13:42.879 align:start position:0% that were learned over a really long period<00:13:41.510> of<00:13:41.540> time<00:13:41.720> and<00:13:41.990> don't<00:13:42.170> suffer<00:13:42.560> from<00:13:42.709> the 00:13:42.879 --> 00:13:42.889 align:start position:0% period of time and don't suffer from the 00:13:42.889 --> 00:13:44.280 align:start position:0% period of time and don't suffer from the constantly<00:13:43.399> the<00:13:43.730> backwards<00:13:44.120> compatibility 00:13:44.280 --> 00:13:44.290 align:start position:0% constantly the backwards compatibility 00:13:44.290 --> 00:13:46.689 align:start position:0% constantly the backwards compatibility problems<00:13:45.290> that<00:13:45.440> askable<00:13:45.889> has<00:13:46.100> because<00:13:46.459> it's<00:13:46.640> a 00:13:46.689 --> 00:13:46.699 align:start position:0% problems that askable has because it's a 00:13:46.699 --> 00:13:48.850 align:start position:0% problems that askable has because it's a very<00:13:46.910> old<00:13:47.120> language<00:13:47.570> so<00:13:48.290> a<00:13:48.320> lots<00:13:48.589> of<00:13:48.680> things 00:13:48.850 --> 00:13:48.860 align:start position:0% very old language so a lots of things 00:13:48.860 --> 00:13:50.860 align:start position:0% very old language so a lots of things are<00:13:48.980> like<00:13:49.100> might<00:13:49.579> it<00:13:49.970> might<00:13:50.149> be<00:13:50.360> done<00:13:50.540> it<00:13:50.720> done 00:13:50.860 --> 00:13:50.870 align:start position:0% are like might it might be done it done 00:13:50.870 --> 00:13:51.880 align:start position:0% are like might it might be done it done right<00:13:51.050> the<00:13:51.199> first<00:13:51.230> time 00:13:51.880 --> 00:13:51.890 align:start position:0% right the first time 00:13:51.890 --> 00:13:53.800 align:start position:0% right the first time and<00:13:52.790> it's<00:13:52.970> actually<00:13:53.240> I'm<00:13:53.300> not<00:13:53.390> even<00:13:53.449> really<00:13:53.720> a 00:13:53.800 --> 00:13:53.810 align:start position:0% and it's actually I'm not even really a 00:13:53.810 --> 00:13:55.120 align:start position:0% and it's actually I'm not even really a language<00:13:54.230> itself<00:13:54.529> it's<00:13:54.769> more<00:13:54.920> like<00:13:55.040> the 00:13:55.120 --> 00:13:55.130 align:start position:0% language itself it's more like the 00:13:55.130 --> 00:13:56.860 align:start position:0% language itself it's more like the language<00:13:55.430> technology<00:13:56.029> that<00:13:56.300> supports<00:13:56.449> like 00:13:56.860 --> 00:13:56.870 align:start position:0% language technology that supports like 00:13:56.870 --> 00:13:59.290 align:start position:0% language technology that supports like multiple<00:13:57.290> patents<00:13:57.769> or<00:13:57.980> run<00:13:58.190> types<00:13:58.430> so<00:13:59.120> like 00:13:59.290 --> 00:13:59.300 align:start position:0% multiple patents or run types so like 00:13:59.300 --> 00:14:00.699 align:start position:0% multiple patents or run types so like the<00:13:59.449> peer<00:13:59.660> script<00:13:59.870> language<00:14:00.199> and<00:14:00.350> selfishness 00:14:00.699 --> 00:14:00.709 align:start position:0% the peer script language and selfishness 00:14:00.709 --> 00:14:02.410 align:start position:0% the peer script language and selfishness of<00:14:00.920> language<00:14:01.250> specification<00:14:01.940> it<00:14:02.089> doesn't 00:14:02.410 --> 00:14:02.420 align:start position:0% of language specification it doesn't 00:14:02.420 --> 00:14:04.420 align:start position:0% of language specification it doesn't specify<00:14:02.570> the<00:14:02.870> runtime<00:14:03.260> behavior<00:14:03.410> which<00:14:04.190> means 00:14:04.420 --> 00:14:04.430 align:start position:0% specify the runtime behavior which means 00:14:04.430 --> 00:14:06.130 align:start position:0% specify the runtime behavior which means that<00:14:04.640> you<00:14:04.760> can<00:14:04.910> technically<00:14:05.390> write<00:14:05.630> bindings 00:14:06.130 --> 00:14:06.140 align:start position:0% that you can technically write bindings 00:14:06.140 --> 00:14:08.829 align:start position:0% that you can technically write bindings to<00:14:06.860> like<00:14:07.130> the<00:14:07.220> peer<00:14:07.430> script<00:14:07.670> word<00:14:08.149> um<00:14:08.570> or 00:14:08.829 --> 00:14:08.839 align:start position:0% to like the peer script word um or 00:14:08.839 --> 00:14:10.540 align:start position:0% to like the peer script word um or whatever<00:14:09.140> in<00:14:09.440> any<00:14:09.680> language<00:14:10.160> that<00:14:10.190> you<00:14:10.370> want 00:14:10.540 --> 00:14:10.550 align:start position:0% whatever in any language that you want 00:14:10.550 --> 00:14:12.400 align:start position:0% whatever in any language that you want and<00:14:10.820> the<00:14:10.940> most<00:14:11.390> popular<00:14:11.810> one<00:14:11.839> is<00:14:12.110> JavaScript 00:14:12.400 --> 00:14:12.410 align:start position:0% and the most popular one is JavaScript 00:14:12.410 --> 00:14:13.960 align:start position:0% and the most popular one is JavaScript because<00:14:12.800> it<00:14:13.070> needs<00:14:13.220> to<00:14:13.310> write<00:14:13.459> in<00:14:13.519> the<00:14:13.579> browser 00:14:13.960 --> 00:14:13.970 align:start position:0% because it needs to write in the browser 00:14:13.970 --> 00:14:15.939 align:start position:0% because it needs to write in the browser and<00:14:14.420> the<00:14:14.510> reason<00:14:14.810> why<00:14:14.959> is<00:14:15.019> that<00:14:15.199> most<00:14:15.709> of<00:14:15.860> the 00:14:15.939 --> 00:14:15.949 align:start position:0% and the reason why is that most of the 00:14:15.949 --> 00:14:18.040 align:start position:0% and the reason why is that most of the peer<00:14:16.130> script<00:14:16.370> work<00:14:16.970> at<00:14:17.149> the<00:14:17.240> core<00:14:17.570> developers 00:14:18.040 --> 00:14:18.050 align:start position:0% peer script work at the core developers 00:14:18.050 --> 00:14:20.380 align:start position:0% peer script work at the core developers were<00:14:18.350> coming<00:14:18.740> from<00:14:18.890> but<00:14:19.100> from<00:14:19.970> like<00:14:20.180> user 00:14:20.380 --> 00:14:20.390 align:start position:0% were coming from but from like user 00:14:20.390 --> 00:14:21.670 align:start position:0% were coming from but from like user interface<00:14:20.720> design<00:14:21.050> and<00:14:21.260> they<00:14:21.350> wanted<00:14:21.620> to 00:14:21.670 --> 00:14:21.680 align:start position:0% interface design and they wanted to 00:14:21.680 --> 00:14:23.319 align:start position:0% interface design and they wanted to provide<00:14:22.010> friendly<00:14:22.339> lunch<00:14:22.730> right<00:14:22.910> frameworks 00:14:23.319 --> 00:14:23.329 align:start position:0% provide friendly lunch right frameworks 00:14:23.329 --> 00:14:25.900 align:start position:0% provide friendly lunch right frameworks to<00:14:23.449> write<00:14:23.690> web<00:14:24.620> applications<00:14:25.459> in<00:14:25.670> this 00:14:25.900 --> 00:14:25.910 align:start position:0% to write web applications in this 00:14:25.910 --> 00:14:28.180 align:start position:0% to write web applications in this language<00:14:26.230> so<00:14:27.230> that's<00:14:27.560> why<00:14:27.740> it's<00:14:27.890> the<00:14:28.010> most 00:14:28.180 --> 00:14:28.190 align:start position:0% language so that's why it's the most 00:14:28.190 --> 00:14:29.530 align:start position:0% language so that's why it's the most sophisticated<00:14:28.279> but<00:14:28.880> there<00:14:29.089> are<00:14:29.209> others 00:14:29.530 --> 00:14:29.540 align:start position:0% sophisticated but there are others 00:14:29.540 --> 00:14:31.630 align:start position:0% sophisticated but there are others there's<00:14:30.230> an<00:14:30.319> Erlang<00:14:30.649> ones<00:14:30.949> which<00:14:31.130> I<00:14:31.399> didn't 00:14:31.630 --> 00:14:31.640 align:start position:0% there's an Erlang ones which I didn't 00:14:31.640 --> 00:14:33.040 align:start position:0% there's an Erlang ones which I didn't somehow<00:14:31.850> is<00:14:32.029> the<00:14:32.120> most<00:14:32.300> advanced<00:14:32.600> of<00:14:32.720> them<00:14:32.899> but 00:14:33.040 --> 00:14:33.050 align:start position:0% somehow is the most advanced of them but 00:14:33.050 --> 00:14:34.540 align:start position:0% somehow is the most advanced of them but there's<00:14:33.199> also<00:14:33.380> the<00:14:33.620> C++<00:14:34.160> and<00:14:34.399> there's 00:14:34.540 --> 00:14:34.550 align:start position:0% there's also the C++ and there's 00:14:34.550 --> 00:14:36.809 align:start position:0% there's also the C++ and there's something<00:14:35.180> like<00:14:35.240> experimental<00:14:35.959> work<00:14:36.110> on<00:14:36.290> some 00:14:36.809 --> 00:14:36.819 align:start position:0% something like experimental work on some 00:14:36.819 --> 00:14:38.729 align:start position:0% something like experimental work on some go<00:14:37.119> as<00:14:37.359> well<00:14:37.539> so<00:14:38.139> basically<00:14:38.439> what<00:14:38.589> this<00:14:38.679> means 00:14:38.729 --> 00:14:38.739 align:start position:0% go as well so basically what this means 00:14:38.739 --> 00:14:40.529 align:start position:0% go as well so basically what this means is<00:14:39.039> that<00:14:39.069> like<00:14:39.309> if<00:14:39.429> you<00:14:39.549> have<00:14:39.699> like<00:14:39.729> a<00:14:39.910> large<00:14:40.179> go 00:14:40.529 --> 00:14:40.539 align:start position:0% is that like if you have like a large go 00:14:40.539 --> 00:14:42.299 align:start position:0% is that like if you have like a large go application<00:14:41.229> in<00:14:41.470> the<00:14:41.589> cold<00:14:41.769> not<00:14:41.919> now<00:14:42.100> but<00:14:42.279> in 00:14:42.299 --> 00:14:42.309 align:start position:0% application in the cold not now but in 00:14:42.309 --> 00:14:44.340 align:start position:0% application in the cold not now but in the<00:14:42.429> future<00:14:42.459> but<00:14:43.149> today<00:14:43.629> if<00:14:43.899> you<00:14:43.989> had<00:14:44.139> like<00:14:44.289> a 00:14:44.340 --> 00:14:44.350 align:start position:0% the future but today if you had like a 00:14:44.350 --> 00:14:46.139 align:start position:0% the future but today if you had like a C++<00:14:44.919> application<00:14:45.459> and<00:14:45.579> you<00:14:45.639> wanted<00:14:45.850> to<00:14:45.879> start 00:14:46.139 --> 00:14:46.149 align:start position:0% C++ application and you wanted to start 00:14:46.149 --> 00:14:48.779 align:start position:0% C++ application and you wanted to start offloading<00:14:46.359> some<00:14:47.289> of<00:14:47.439> the<00:14:47.589> core<00:14:48.309> parts<00:14:48.639> of<00:14:48.699> the 00:14:48.779 --> 00:14:48.789 align:start position:0% offloading some of the core parts of the 00:14:48.789 --> 00:14:51.059 align:start position:0% offloading some of the core parts of the application<00:14:48.910> to<00:14:49.479> a<00:14:49.509> word<00:14:49.809> they<00:14:50.649> typed<00:14:50.859> any 00:14:51.059 --> 00:14:51.069 align:start position:0% application to a word they typed any 00:14:51.069 --> 00:14:52.679 align:start position:0% application to a word they typed any language<00:14:51.519> you<00:14:51.549> can<00:14:51.819> write<00:14:52.029> certain<00:14:52.299> parts<00:14:52.629> of 00:14:52.679 --> 00:14:52.689 align:start position:0% language you can write certain parts of 00:14:52.689 --> 00:14:54.179 align:start position:0% language you can write certain parts of this<00:14:52.809> thing<00:14:53.019> in<00:14:53.229> your<00:14:53.529> script<00:14:53.829> and<00:14:53.979> have<00:14:54.160> a 00:14:54.179 --> 00:14:54.189 align:start position:0% this thing in your script and have a 00:14:54.189 --> 00:14:55.799 align:start position:0% this thing in your script and have a full<00:14:54.489> mile<00:14:54.729> that's<00:14:54.939> linked<00:14:55.149> to<00:14:55.329> it<00:14:55.449> seem<00:14:55.660> plus 00:14:55.799 --> 00:14:55.809 align:start position:0% full mile that's linked to it seem plus 00:14:55.809 --> 00:15:04.350 align:start position:0% full mile that's linked to it seem plus plus<00:14:56.079> like<00:14:56.410> dinner<00:14:56.649> later 00:15:04.350 --> 00:15:04.360 align:start position:0% 00:15:04.360 --> 00:15:08.609 align:start position:0% yeah<00:15:05.100> sure<00:15:06.129> over<00:15:07.089> in<00:15:07.449> this<00:15:07.689> oh<00:15:07.899> I<00:15:07.989> see<00:15:08.259> this 00:15:08.609 --> 00:15:08.619 align:start position:0% yeah sure over in this oh I see this 00:15:08.619 --> 00:15:13.130 align:start position:0% yeah sure over in this oh I see this great<00:15:08.949> democracy 00:15:13.130 --> 00:15:13.140 align:start position:0% 00:15:13.140 --> 00:15:15.780 align:start position:0% [Music] 00:15:15.780 --> 00:15:15.790 align:start position:0% [Music] 00:15:15.790 --> 00:15:17.650 align:start position:0% [Music] I<00:15:16.790> see<00:15:17.180> how<00:15:17.360> it 00:15:17.650 --> 00:15:17.660 align:start position:0% I see how it 00:15:17.660 --> 00:15:18.520 align:start position:0% I see how it we're<00:15:17.810> like<00:15:17.990> somewhere<00:15:18.290> like<00:15:18.500> a 00:15:18.520 --> 00:15:18.530 align:start position:0% we're like somewhere like a 00:15:18.530 --> 00:15:22.980 align:start position:0% we're like somewhere like a three-dimensional<00:15:19.120> slice 00:15:22.980 --> 00:15:22.990 align:start position:0% 00:15:22.990 --> 00:15:26.230 align:start position:0% yes<00:15:23.990> so<00:15:24.200> basically<00:15:24.560> like<00:15:25.340> the<00:15:25.790> present-day 00:15:26.230 --> 00:15:26.240 align:start position:0% yes so basically like the present-day 00:15:26.240 --> 00:15:27.790 align:start position:0% yes so basically like the present-day situation<00:15:26.540> is<00:15:26.960> that<00:15:26.990> it<00:15:27.230> like<00:15:27.380> I<00:15:27.410> said<00:15:27.560> all 00:15:27.790 --> 00:15:27.800 align:start position:0% situation is that it like I said all 00:15:27.800 --> 00:15:29.620 align:start position:0% situation is that it like I said all these<00:15:27.950> things<00:15:28.100> are<00:15:28.460> insurers<00:15:29.150> or<00:15:29.330> working 00:15:29.620 --> 00:15:29.630 align:start position:0% these things are insurers or working 00:15:29.630 --> 00:15:31.720 align:start position:0% these things are insurers or working with<00:15:29.750> the<00:15:29.810> standard<00:15:30.170> stack<00:15:31.040> of<00:15:31.250> material 00:15:31.720 --> 00:15:31.730 align:start position:0% with the standard stack of material 00:15:31.730 --> 00:15:36.880 align:start position:0% with the standard stack of material watch<00:15:31.940> chain<00:15:34.690> with<00:15:35.690> an<00:15:35.810> ethereal<00:15:36.170> watching 00:15:36.880 --> 00:15:36.890 align:start position:0% watch chain with an ethereal watching 00:15:36.890 --> 00:15:41.350 align:start position:0% watch chain with an ethereal watching and<00:15:37.040> no<00:15:39.220> solidity<00:15:40.220> or<00:15:41.000> something<00:15:41.240> that 00:15:41.350 --> 00:15:41.360 align:start position:0% and no solidity or something that 00:15:41.360 --> 00:15:43.030 align:start position:0% and no solidity or something that produces<00:15:41.510> an<00:15:41.810> amyís<00:15:42.050> of<00:15:42.410> the<00:15:42.560> standard<00:15:42.890> type 00:15:43.030 --> 00:15:43.040 align:start position:0% produces an amyís of the standard type 00:15:43.040 --> 00:15:45.790 align:start position:0% produces an amyís of the standard type of<00:15:43.190> what<00:15:43.490> we're<00:15:43.640> used<00:15:43.700> to<00:15:44.410> chantrelle<00:15:45.410> itself 00:15:45.790 --> 00:15:45.800 align:start position:0% of what we're used to chantrelle itself 00:15:45.800 --> 00:15:47.950 align:start position:0% of what we're used to chantrelle itself is<00:15:45.980> it's<00:15:46.490> kind<00:15:46.820> of<00:15:46.880> like<00:15:47.090> married<00:15:47.450> to<00:15:47.570> solidity 00:15:47.950 --> 00:15:47.960 align:start position:0% is it's kind of like married to solidity 00:15:47.960 --> 00:15:53.740 align:start position:0% is it's kind of like married to solidity in<00:15:48.110> this<00:15:48.290> one<00:15:50.920> I<00:15:51.920> want<00:15:52.730> to<00:15:52.910> build<00:15:53.300> high<00:15:53.510> plank 00:15:53.740 --> 00:15:53.750 align:start position:0% in this one I want to build high plank 00:15:53.750 --> 00:15:55.030 align:start position:0% in this one I want to build high plank but<00:15:53.990> you<00:15:54.350> know<00:15:54.410> there's<00:15:54.620> other<00:15:54.770> things<00:15:54.830> you 00:15:55.030 --> 00:15:55.040 align:start position:0% but you know there's other things you 00:15:55.040 --> 00:15:56.440 align:start position:0% but you know there's other things you could<00:15:55.190> go<00:15:55.340> in<00:15:55.520> directions<00:15:55.820> there<00:15:56.150> that<00:15:56.360> are 00:15:56.440 --> 00:15:56.450 align:start position:0% could go in directions there that are 00:15:56.450 --> 00:15:58.540 align:start position:0% could go in directions there that are kind<00:15:56.660> of<00:15:56.750> more<00:15:56.810> they're<00:15:57.590> newer<00:15:57.830> they're<00:15:58.310> kind 00:15:58.540 --> 00:15:58.550 align:start position:0% kind of more they're newer they're kind 00:15:58.550 --> 00:16:00.370 align:start position:0% kind of more they're newer they're kind of<00:15:58.640> stable<00:15:58.970> like<00:15:59.270> stabilizing<00:15:59.990> but<00:16:00.200> they're 00:16:00.370 --> 00:16:00.380 align:start position:0% of stable like stabilizing but they're 00:16:00.380 --> 00:16:01.810 align:start position:0% of stable like stabilizing but they're not<00:16:00.530> really<00:16:00.800> stable<00:16:01.100> enough<00:16:01.370> for<00:16:01.430> us<00:16:01.670> to 00:16:01.810 --> 00:16:01.820 align:start position:0% not really stable enough for us to 00:16:01.820 --> 00:16:02.980 align:start position:0% not really stable enough for us to really<00:16:01.940> integrate<00:16:02.150> with<00:16:02.450> like<00:16:02.660> this<00:16:02.810> need 00:16:02.980 --> 00:16:02.990 align:start position:0% really integrate with like this need 00:16:02.990 --> 00:16:05.830 align:start position:0% really integrate with like this need p.m.<00:16:03.290> support<00:16:03.880> which<00:16:04.880> is<00:16:05.030> like<00:16:05.180> you're<00:16:05.720> in 00:16:05.830 --> 00:16:05.840 align:start position:0% p.m. support which is like you're in 00:16:05.840 --> 00:16:08.800 align:start position:0% p.m. support which is like you're in package<00:16:06.140> manager<00:16:06.590> like<00:16:07.480> that's<00:16:08.480> not<00:16:08.720> about 00:16:08.800 --> 00:16:08.810 align:start position:0% package manager like that's not about 00:16:08.810 --> 00:16:10.080 align:start position:0% package manager like that's not about the<00:16:08.990> shore<00:16:09.170> less<00:16:09.350> it<00:16:09.470> takes<00:16:09.650> to<00:16:09.770> do 00:16:10.080 --> 00:16:10.090 align:start position:0% the shore less it takes to do 00:16:10.090 --> 00:16:11.490 align:start position:0% the shore less it takes to do but<00:16:10.510> then<00:16:10.630> there's<00:16:10.780> other<00:16:10.930> things<00:16:11.020> like 00:16:11.490 --> 00:16:11.500 align:start position:0% but then there's other things like 00:16:11.500 --> 00:16:13.290 align:start position:0% but then there's other things like language<00:16:11.950> other<00:16:12.310> language<00:16:12.400> support<00:16:13.000> like<00:16:13.120> by 00:16:13.290 --> 00:16:13.300 align:start position:0% language other language support like by 00:16:13.300 --> 00:16:19.080 align:start position:0% language other language support like by profit<00:16:13.810> or<00:16:17.310> formality<00:16:18.310> or<00:16:18.340> whatever<00:16:18.790> the<00:16:18.940> case 00:16:19.080 --> 00:16:19.090 align:start position:0% profit or formality or whatever the case 00:16:19.090 --> 00:16:20.580 align:start position:0% profit or formality or whatever the case is<00:16:19.240> I<00:16:19.330> mean<00:16:19.480> making<00:16:19.810> the<00:16:19.900> generates<00:16:20.230> an<00:16:20.320> API 00:16:20.580 --> 00:16:20.590 align:start position:0% is I mean making the generates an API 00:16:20.590 --> 00:16:25.770 align:start position:0% is I mean making the generates an API though<00:16:20.920> is<00:16:21.070> a<00:16:21.100> very<00:16:21.460> embarrassing<00:16:23.550> and<00:16:24.780> then 00:16:25.770 --> 00:16:25.780 align:start position:0% though is a very embarrassing and then 00:16:25.780 --> 00:16:27.840 align:start position:0% though is a very embarrassing and then here's<00:16:26.080> like<00:16:26.200> a<00:16:26.260> comparative<00:16:27.160> stack<00:16:27.400> diagram 00:16:27.840 --> 00:16:27.850 align:start position:0% here's like a comparative stack diagram 00:16:27.850 --> 00:16:29.520 align:start position:0% here's like a comparative stack diagram in<00:16:28.060> case<00:16:28.210> none<00:16:28.540> of<00:16:28.570> that<00:16:28.660> makes<00:16:28.930> any<00:16:29.080> sense<00:16:29.380> to 00:16:29.520 --> 00:16:29.530 align:start position:0% in case none of that makes any sense to 00:16:29.530 --> 00:16:32.130 align:start position:0% in case none of that makes any sense to you<00:16:29.680> so<00:16:29.740> basically<00:16:30.310> like<00:16:30.520> left<00:16:31.480> hand<00:16:31.750> side<00:16:31.960> you 00:16:32.130 --> 00:16:32.140 align:start position:0% you so basically like left hand side you 00:16:32.140 --> 00:16:33.780 align:start position:0% you so basically like left hand side you have<00:16:32.170> like<00:16:32.500> your<00:16:32.710> kind<00:16:32.890> of<00:16:32.980> traditional<00:16:33.490> stack 00:16:33.780 --> 00:16:33.790 align:start position:0% have like your kind of traditional stack 00:16:33.790 --> 00:16:36.810 align:start position:0% have like your kind of traditional stack that<00:16:34.000> you<00:16:34.330> know<00:16:34.420> consensus<00:16:35.550> you<00:16:36.550> know<00:16:36.640> that 00:16:36.810 --> 00:16:36.820 align:start position:0% that you know consensus you know that 00:16:36.820 --> 00:16:38.070 align:start position:0% that you know consensus you know that you<00:16:36.970> kind<00:16:37.120> of<00:16:37.240> like<00:16:37.390> because<00:16:37.510> for<00:16:37.870> a<00:16:37.900> lot<00:16:38.020> of 00:16:38.070 --> 00:16:38.080 align:start position:0% you kind of like because for a lot of 00:16:38.080 --> 00:16:40.110 align:start position:0% you kind of like because for a lot of Victorian<00:16:38.650> consensus<00:16:39.130> to<00:16:39.280> getting<00:16:39.850> it<00:16:39.940> now 00:16:40.110 --> 00:16:40.120 align:start position:0% Victorian consensus to getting it now 00:16:40.120 --> 00:16:43.050 align:start position:0% Victorian consensus to getting it now it's<00:16:40.330> kind<00:16:40.390> of<00:16:40.540> like<00:16:40.690> offshoots<00:16:42.060> companies 00:16:43.050 --> 00:16:43.060 align:start position:0% it's kind of like offshoots companies 00:16:43.060 --> 00:16:45.420 align:start position:0% it's kind of like offshoots companies but<00:16:43.420> you<00:16:43.870> have<00:16:43.990> things<00:16:44.230> like<00:16:44.440> test<00:16:44.710> RPC<00:16:45.220> are 00:16:45.420 --> 00:16:45.430 align:start position:0% but you have things like test RPC are 00:16:45.430 --> 00:16:50.340 align:start position:0% but you have things like test RPC are like<00:16:45.640> Ganesh<00:16:46.330> or<00:16:48.600> the<00:16:49.600> same<00:16:49.780> product<00:16:50.140> as<00:16:50.320> a 00:16:50.340 --> 00:16:50.350 align:start position:0% like Ganesh or the same product as a 00:16:50.350 --> 00:16:52.650 align:start position:0% like Ganesh or the same product as a point<00:16:50.590> or<00:16:50.710> truffle<00:16:51.070> they<00:16:51.130> may<00:16:51.250> love<00:16:51.460> it<00:16:51.660> like 00:16:52.650 --> 00:16:52.660 align:start position:0% point or truffle they may love it like 00:16:52.660 --> 00:16:56.040 align:start position:0% point or truffle they may love it like one<00:16:52.840> project<00:16:53.080> sitting<00:16:53.850> sorry<00:16:54.850> you<00:16:55.720> know<00:16:55.810> those 00:16:56.040 --> 00:16:56.050 align:start position:0% one project sitting sorry you know those 00:16:56.050 --> 00:16:57.810 align:start position:0% one project sitting sorry you know those kinds<00:16:56.320> of<00:16:56.380> like<00:16:56.560> big<00:16:56.860> theorem<00:16:57.280> layers<00:16:57.610> or 00:16:57.810 --> 00:16:57.820 align:start position:0% kinds of like big theorem layers or 00:16:57.820 --> 00:16:59.100 align:start position:0% kinds of like big theorem layers or maybe<00:16:57.970> a<00:16:58.060> real<00:16:58.240> afeared<00:16:58.540> layer<00:16:58.750> you<00:16:58.960> have<00:16:59.080> a 00:16:59.100 --> 00:16:59.110 align:start position:0% maybe a real afeared layer you have a 00:16:59.110 --> 00:17:01.440 align:start position:0% maybe a real afeared layer you have a slimming<00:16:59.440> Tyler<00:16:59.980> went<00:17:00.190> 3GS<00:17:00.700> truffle<00:17:01.180> and<00:17:01.240> and 00:17:01.440 --> 00:17:01.450 align:start position:0% slimming Tyler went 3GS truffle and and 00:17:01.450 --> 00:17:03.330 align:start position:0% slimming Tyler went 3GS truffle and and you<00:17:01.510> build<00:17:01.690> on<00:17:01.840> your<00:17:02.080> applications<00:17:02.890> on<00:17:03.010> top<00:17:03.190> of 00:17:03.330 --> 00:17:03.340 align:start position:0% you build on your applications on top of 00:17:03.340 --> 00:17:05.400 align:start position:0% you build on your applications on top of that<00:17:03.460> what<00:17:04.120> we're<00:17:04.300> advocating<00:17:04.570> for<00:17:04.900> us<00:17:05.050> on<00:17:05.290> the 00:17:05.400 --> 00:17:05.410 align:start position:0% that what we're advocating for us on the 00:17:05.410 --> 00:17:07.250 align:start position:0% that what we're advocating for us on the right-hand<00:17:05.800> side<00:17:05.890> so<00:17:06.370> there's<00:17:06.910> laying 00:17:07.250 --> 00:17:07.260 align:start position:0% right-hand side so there's laying 00:17:07.260 --> 00:17:09.510 align:start position:0% right-hand side so there's laying etherium<00:17:08.260> and<00:17:08.410> clipping<00:17:08.830> it<00:17:09.010> just<00:17:09.190> like<00:17:09.310> our 00:17:09.510 --> 00:17:09.520 align:start position:0% etherium and clipping it just like our 00:17:09.520 --> 00:17:12.220 align:start position:0% etherium and clipping it just like our version<00:17:09.910> of 00:17:12.220 --> 00:17:12.230 align:start position:0% 00:17:12.230 --> 00:17:14.079 align:start position:0% that<00:17:12.559> would<00:17:12.679> like<00:17:12.860> dr.<00:17:13.130> container<00:17:13.730> that<00:17:13.850> was<00:17:14.029> a 00:17:14.079 --> 00:17:14.089 align:start position:0% that would like dr. container that was a 00:17:14.089 --> 00:17:16.269 align:start position:0% that would like dr. container that was a real<00:17:14.419> ethereal<00:17:15.110> no<00:17:15.260> but<00:17:15.529> at<00:17:15.620> the<00:17:15.829> time<00:17:16.039> why<00:17:16.250> I 00:17:16.269 --> 00:17:16.279 align:start position:0% real ethereal no but at the time why I 00:17:16.279 --> 00:17:18.490 align:start position:0% real ethereal no but at the time why I didn't<00:17:16.639> expect<00:17:17.539> to<00:17:17.600> run<00:17:17.659> unit<00:17:18.049> tests<00:17:18.409> as 00:17:18.490 --> 00:17:18.500 align:start position:0% didn't expect to run unit tests as 00:17:18.500 --> 00:17:20.070 align:start position:0% didn't expect to run unit tests as delegates 00:17:20.070 --> 00:17:20.080 align:start position:0% delegates 00:17:20.080 --> 00:17:22.730 align:start position:0% delegates triskin<00:17:20.709> web<00:17:20.980> 3<00:17:21.250> solidity<00:17:21.970> compiler 00:17:22.730 --> 00:17:22.740 align:start position:0% triskin web 3 solidity compiler 00:17:22.740 --> 00:17:25.590 align:start position:0% triskin web 3 solidity compiler chantrelle<00:17:23.800> I<00:17:23.980> saw<00:17:24.339> your<00:17:24.580> app<00:17:24.880> development<00:17:25.300> so 00:17:25.590 --> 00:17:25.600 align:start position:0% chantrelle I saw your app development so 00:17:25.600 --> 00:17:30.590 align:start position:0% chantrelle I saw your app development so these<00:17:26.440> slides<00:17:26.589> will<00:17:26.860> be<00:17:26.920> published<00:17:29.160> so<00:17:30.160> like 00:17:30.590 --> 00:17:30.600 align:start position:0% these slides will be published so like 00:17:30.600 --> 00:17:32.820 align:start position:0% these slides will be published so like that's<00:17:31.600> part<00:17:31.930> of<00:17:31.990> talk<00:17:32.170> basically<00:17:32.440> giving 00:17:32.820 --> 00:17:32.830 align:start position:0% that's part of talk basically giving 00:17:32.830 --> 00:17:35.820 align:start position:0% that's part of talk basically giving some<00:17:33.010> examples<00:17:33.100> of<00:17:34.320> what<00:17:35.320> the<00:17:35.440> stuff<00:17:35.650> looks 00:17:35.820 --> 00:17:35.830 align:start position:0% some examples of what the stuff looks 00:17:35.830 --> 00:17:39.750 align:start position:0% some examples of what the stuff looks like<00:17:36.070> and<00:17:36.970> you<00:17:37.600> know<00:17:37.660> here's<00:17:38.590> like<00:17:38.800> progresses 00:17:39.750 --> 00:17:39.760 align:start position:0% like and you know here's like progresses 00:17:39.760 --> 00:17:41.700 align:start position:0% like and you know here's like progresses like<00:17:39.790> gasifier<00:17:40.540> life<00:17:40.780> or<00:17:40.990> some<00:17:41.170> definition<00:17:41.650> of 00:17:41.700 --> 00:17:41.710 align:start position:0% like gasifier life or some definition of 00:17:41.710 --> 00:17:43.470 align:start position:0% like gasifier life or some definition of the<00:17:41.770> word<00:17:41.920> simplified<00:17:42.400> because<00:17:42.730> there's<00:17:43.360> like 00:17:43.470 --> 00:17:43.480 align:start position:0% the word simplified because there's like 00:17:43.480 --> 00:17:45.240 align:start position:0% the word simplified because there's like a<00:17:43.540> pretty<00:17:43.810> steep<00:17:44.020> learning<00:17:44.200> curve<00:17:44.560> starting 00:17:45.240 --> 00:17:45.250 align:start position:0% a pretty steep learning curve starting 00:17:45.250 --> 00:17:46.830 align:start position:0% a pretty steep learning curve starting you<00:17:45.580> know<00:17:45.610> any<00:17:45.910> of<00:17:46.000> these<00:17:46.090> things<00:17:46.270> but<00:17:46.540> you 00:17:46.830 --> 00:17:46.840 align:start position:0% you know any of these things but you 00:17:46.840 --> 00:17:48.420 align:start position:0% you know any of these things but you know<00:17:46.960> at<00:17:47.410> some<00:17:47.470> point<00:17:47.860> your<00:17:47.980> life<00:17:48.160> gets 00:17:48.420 --> 00:17:48.430 align:start position:0% know at some point your life gets 00:17:48.430 --> 00:17:50.640 align:start position:0% know at some point your life gets exponentially<00:17:49.000> simpler<00:17:49.540> it's<00:17:50.080> just<00:17:50.290> I<00:17:50.470> don't 00:17:50.640 --> 00:17:50.650 align:start position:0% exponentially simpler it's just I don't 00:17:50.650 --> 00:17:59.100 align:start position:0% exponentially simpler it's just I don't know<00:17:50.710> how<00:17:51.840> but<00:17:52.950> you<00:17:53.950> kind<00:17:54.160> of<00:17:54.220> like<00:17:55.350> yeah<00:17:58.110> well 00:17:59.100 --> 00:17:59.110 align:start position:0% know how but you kind of like yeah well 00:17:59.110 --> 00:18:00.660 align:start position:0% know how but you kind of like yeah well basically<00:17:59.500> like<00:17:59.890> it's<00:18:00.130> my<00:18:00.250> time<00:18:00.430> to<00:18:00.460> decide 00:18:00.660 --> 00:18:00.670 align:start position:0% basically like it's my time to decide 00:18:00.670 --> 00:18:02.370 align:start position:0% basically like it's my time to decide yeah<00:18:01.000> this<00:18:01.180> is<00:18:01.300> kind<00:18:01.510> of<00:18:01.540> like<00:18:01.660> more<00:18:01.810> of<00:18:01.870> like 00:18:02.370 --> 00:18:02.380 align:start position:0% yeah this is kind of like more of like 00:18:02.380 --> 00:18:05.880 align:start position:0% yeah this is kind of like more of like where<00:18:04.050> this<00:18:05.050> is<00:18:05.170> more<00:18:05.290> like<00:18:05.470> an<00:18:05.590> in-depth 00:18:05.880 --> 00:18:05.890 align:start position:0% where this is more like an in-depth 00:18:05.890 --> 00:18:07.110 align:start position:0% where this is more like an in-depth section<00:18:06.190> of<00:18:06.250> over<00:18:06.430> to<00:18:06.550> my<00:18:06.670> earlier<00:18:06.940> if<00:18:07.000> I'd 00:18:07.110 --> 00:18:07.120 align:start position:0% section of over to my earlier if I'd 00:18:07.120 --> 00:18:09.090 align:start position:0% section of over to my earlier if I'd like<00:18:07.300> some<00:18:07.540> of<00:18:07.600> these<00:18:07.660> more<00:18:08.440> concepts<00:18:08.890> of<00:18:09.010> my 00:18:09.090 --> 00:18:09.100 align:start position:0% like some of these more concepts of my 00:18:09.100 --> 00:18:10.860 align:start position:0% like some of these more concepts of my functional<00:18:09.490> programmer<00:18:09.880> analyst<00:18:10.660> rated 00:18:10.860 --> 00:18:10.870 align:start position:0% functional programmer analyst rated 00:18:10.870 --> 00:18:12.960 align:start position:0% functional programmer analyst rated through<00:18:11.020> these<00:18:11.140> libraries<00:18:11.590> so<00:18:11.890> again<00:18:12.820> like 00:18:12.960 --> 00:18:12.970 align:start position:0% through these libraries so again like 00:18:12.970 --> 00:18:14.430 align:start position:0% through these libraries so again like pure<00:18:13.270> like<00:18:13.600> there's<00:18:13.780> this<00:18:13.870> notion<00:18:14.020> of<00:18:14.260> purity 00:18:14.430 --> 00:18:14.440 align:start position:0% pure like there's this notion of purity 00:18:14.440 --> 00:18:15.930 align:start position:0% pure like there's this notion of purity and<00:18:14.650> insects<00:18:15.160> are<00:18:15.220> two<00:18:15.310> separate<00:18:15.730> they're 00:18:15.930 --> 00:18:15.940 align:start position:0% and insects are two separate they're 00:18:15.940 --> 00:18:17.220 align:start position:0% and insects are two separate they're somehow<00:18:16.090> like<00:18:16.270> a<00:18:16.360> separation<00:18:16.870> in<00:18:16.900> the<00:18:17.020> type 00:18:17.220 --> 00:18:17.230 align:start position:0% somehow like a separation in the type 00:18:17.230 --> 00:18:19.320 align:start position:0% somehow like a separation in the type system<00:18:17.440> between<00:18:17.770> was<00:18:18.610> how<00:18:18.760> like<00:18:18.940> effectual 00:18:19.320 --> 00:18:19.330 align:start position:0% system between was how like effectual 00:18:19.330 --> 00:18:21.180 align:start position:0% system between was how like effectual computation<00:18:20.080> their<00:18:20.230> stuff<00:18:20.440> it<00:18:20.620> has<00:18:20.740> like<00:18:20.980> side 00:18:21.180 --> 00:18:21.190 align:start position:0% computation their stuff it has like side 00:18:21.190 --> 00:18:23.640 align:start position:0% computation their stuff it has like side effects<00:18:21.490> or<00:18:21.670> micro<00:18:22.120> exceptions<00:18:22.600> or<00:18:23.380> whatever 00:18:23.640 --> 00:18:23.650 align:start position:0% effects or micro exceptions or whatever 00:18:23.650 --> 00:18:26.700 align:start position:0% effects or micro exceptions or whatever it's<00:18:23.920> kind<00:18:24.910> of<00:18:24.940> like<00:18:25.120> like<00:18:26.020> the<00:18:26.080> cortex<00:18:26.500> like 00:18:26.700 --> 00:18:26.710 align:start position:0% it's kind of like like the cortex like 00:18:26.710 --> 00:18:28.620 align:start position:0% it's kind of like like the cortex like coming<00:18:27.010> to<00:18:27.160> in<00:18:27.310> front<00:18:27.580> bytes<00:18:27.820> you<00:18:28.150> know<00:18:28.420> or 00:18:28.620 --> 00:18:28.630 align:start position:0% coming to in front bytes you know or 00:18:28.630 --> 00:18:30.150 align:start position:0% coming to in front bytes you know or byte<00:18:28.810> strings<00:18:29.080> whatever<00:18:29.380> has<00:18:29.560> possibilities 00:18:30.150 --> 00:18:30.160 align:start position:0% byte strings whatever has possibilities 00:18:30.160 --> 00:18:31.800 align:start position:0% byte strings whatever has possibilities like<00:18:30.400> you<00:18:30.700> know<00:18:30.790> decoding<00:18:31.330> errors<00:18:31.540> and<00:18:31.720> what 00:18:31.800 --> 00:18:31.810 align:start position:0% like you know decoding errors and what 00:18:31.810 --> 00:18:33.090 align:start position:0% like you know decoding errors and what happens<00:18:32.140> when<00:18:32.260> you<00:18:32.380> have<00:18:32.650> those<00:18:32.800> two<00:18:32.860> the 00:18:33.090 --> 00:18:33.100 align:start position:0% happens when you have those two the 00:18:33.100 --> 00:18:34.500 align:start position:0% happens when you have those two the health<00:18:33.310> part<00:18:33.490> they<00:18:33.670> bubble<00:18:33.820> up<00:18:34.030> and<00:18:34.270> how<00:18:34.330> much 00:18:34.500 --> 00:18:34.510 align:start position:0% health part they bubble up and how much 00:18:34.510 --> 00:18:35.910 align:start position:0% health part they bubble up and how much do<00:18:34.630> you<00:18:34.720> have<00:18:34.840> a<00:18:34.870> liver<00:18:35.140> that's<00:18:35.530> the<00:18:35.650> kind<00:18:35.860> of 00:18:35.910 --> 00:18:35.920 align:start position:0% do you have a liver that's the kind of 00:18:35.920 --> 00:18:37.800 align:start position:0% do you have a liver that's the kind of side<00:18:36.130> effect<00:18:36.430> that's<00:18:36.610> like<00:18:36.790> or<00:18:37.210> pure<00:18:37.570> in<00:18:37.720> the 00:18:37.800 --> 00:18:37.810 align:start position:0% side effect that's like or pure in the 00:18:37.810 --> 00:18:39.090 align:start position:0% side effect that's like or pure in the sense<00:18:38.020> that<00:18:38.110> it<00:18:38.290> didn't<00:18:38.560> happen<00:18:38.680> because<00:18:38.890> of 00:18:39.090 --> 00:18:39.100 align:start position:0% sense that it didn't happen because of 00:18:39.100 --> 00:18:40.470 align:start position:0% sense that it didn't happen because of like<00:18:39.220> a<00:18:39.250> network<00:18:39.520> failure<00:18:39.790> and<00:18:40.150> something 00:18:40.470 --> 00:18:40.480 align:start position:0% like a network failure and something 00:18:40.480 --> 00:18:41.880 align:start position:0% like a network failure and something that<00:18:40.540> just<00:18:40.750> your<00:18:41.230> program<00:18:41.620> through<00:18:41.770> an 00:18:41.880 --> 00:18:41.890 align:start position:0% that just your program through an 00:18:41.890 --> 00:18:44.760 align:start position:0% that just your program through an exception<00:18:42.280> in<00:18:42.370> some<00:18:42.550> way 00:18:44.760 --> 00:18:44.770 align:start position:0% 00:18:44.770 --> 00:18:46.680 align:start position:0% throwing<00:18:45.730> other<00:18:45.820> kinds<00:18:46.150> of<00:18:46.240> runtime 00:18:46.680 --> 00:18:46.690 align:start position:0% throwing other kinds of runtime 00:18:46.690 --> 00:18:48.720 align:start position:0% throwing other kinds of runtime exceptions<00:18:47.380> or<00:18:47.560> indicated<00:18:48.070> errors<00:18:48.400> that<00:18:48.550> have 00:18:48.720 --> 00:18:48.730 align:start position:0% exceptions or indicated errors that have 00:18:48.730 --> 00:18:50.790 align:start position:0% exceptions or indicated errors that have an<00:18:48.880> unrecoverable<00:18:49.510> errors<00:18:50.260> such<00:18:50.500> as<00:18:50.530> like 00:18:50.790 --> 00:18:50.800 align:start position:0% an unrecoverable errors such as like 00:18:50.800 --> 00:18:53.190 align:start position:0% an unrecoverable errors such as like database<00:18:51.190> failures<00:18:51.700> or<00:18:52.000> API<00:18:52.450> call<00:18:52.750> failures 00:18:53.190 --> 00:18:53.200 align:start position:0% database failures or API call failures 00:18:53.200 --> 00:18:56.000 align:start position:0% database failures or API call failures but<00:18:53.830> also<00:18:54.010> you<00:18:54.820> know<00:18:54.940> basically<00:18:55.660> like 00:18:56.000 --> 00:18:56.010 align:start position:0% but also you know basically like 00:18:56.010 --> 00:18:58.860 align:start position:0% but also you know basically like improperly<00:18:57.010> formatted<00:18:57.460> data<00:18:57.790> exceptions<00:18:58.390> etc 00:18:58.860 --> 00:18:58.870 align:start position:0% improperly formatted data exceptions etc 00:18:58.870 --> 00:19:01.140 align:start position:0% improperly formatted data exceptions etc also<00:18:59.470> like<00:18:59.740> invoking<00:19:00.100> a<00:19:00.310> web<00:19:00.460> 3<00:19:00.760> or<00:19:00.910> another 00:19:01.140 --> 00:19:01.150 align:start position:0% also like invoking a web 3 or another 00:19:01.150 --> 00:19:02.430 align:start position:0% also like invoking a web 3 or another network<00:19:01.390> call<00:19:01.750> these<00:19:01.930> are<00:19:02.050> all<00:19:02.170> things<00:19:02.320> that 00:19:02.430 --> 00:19:02.440 align:start position:0% network call these are all things that 00:19:02.440 --> 00:19:03.960 align:start position:0% network call these are all things that we<00:19:02.560> needed<00:19:02.740> by<00:19:02.890> like<00:19:03.070> side<00:19:03.280> effects<00:19:03.610> because 00:19:03.960 --> 00:19:03.970 align:start position:0% we needed by like side effects because 00:19:03.970 --> 00:19:05.520 align:start position:0% we needed by like side effects because you<00:19:04.180> communicate<00:19:04.900> in<00:19:05.020> that<00:19:05.080> sense<00:19:05.410> you 00:19:05.520 --> 00:19:05.530 align:start position:0% you communicate in that sense you 00:19:05.530 --> 00:19:07.680 align:start position:0% you communicate in that sense you communicate<00:19:06.070> somehow<00:19:06.370> the<00:19:06.520> real<00:19:06.880> world<00:19:07.150> which 00:19:07.680 --> 00:19:07.690 align:start position:0% communicate somehow the real world which 00:19:07.690 --> 00:19:09.180 align:start position:0% communicate somehow the real world which means<00:19:07.900> you've<00:19:08.050> actually<00:19:08.410> created<00:19:08.770> some 00:19:09.180 --> 00:19:09.190 align:start position:0% means you've actually created some 00:19:09.190 --> 00:19:10.470 align:start position:0% means you've actually created some side-effects<00:19:09.700> such<00:19:09.790> that<00:19:10.060> if<00:19:10.150> you've<00:19:10.300> been 00:19:10.470 --> 00:19:10.480 align:start position:0% side-effects such that if you've been 00:19:10.480 --> 00:19:11.880 align:start position:0% side-effects such that if you've been you<00:19:10.600> made<00:19:10.750> the<00:19:10.840> same<00:19:11.020> call<00:19:11.290> again 00:19:11.880 --> 00:19:11.890 align:start position:0% you made the same call again 00:19:11.890 --> 00:19:16.800 align:start position:0% you made the same call again you<00:19:12.130> would<00:19:12.250> get<00:19:12.370> different<00:19:12.400> results<00:19:15.810> examples 00:19:16.800 --> 00:19:16.810 align:start position:0% you would get different results examples 00:19:16.810 --> 00:19:19.410 align:start position:0% you would get different results examples of<00:19:16.900> pure<00:19:17.050> functions<00:19:17.590> are<00:19:18.100> like<00:19:18.280> or<00:19:18.790> kind<00:19:19.360> of 00:19:19.410 --> 00:19:19.420 align:start position:0% of pure functions are like or kind of 00:19:19.420 --> 00:19:22.110 align:start position:0% of pure functions are like or kind of like<00:19:19.680> you<00:19:20.680> know<00:19:20.800> they're<00:19:21.550> everywhere<00:19:21.850> but 00:19:22.110 --> 00:19:22.120 align:start position:0% like you know they're everywhere but 00:19:22.120 --> 00:19:27.270 align:start position:0% like you know they're everywhere but they're<00:19:22.300> like<00:19:22.480> somehow<00:19:26.280> situation-specific 00:19:27.270 --> 00:19:27.280 align:start position:0% they're like somehow situation-specific 00:19:27.280 --> 00:19:29.760 align:start position:0% they're like somehow situation-specific but<00:19:28.240> like<00:19:28.390> data<00:19:28.630> transformations<00:19:29.350> that<00:19:29.530> can't 00:19:29.760 --> 00:19:29.770 align:start position:0% but like data transformations that can't 00:19:29.770 --> 00:19:32.040 align:start position:0% but like data transformations that can't fail<00:19:30.010> like<00:19:30.610> storing<00:19:31.000> a<00:19:31.090> list<00:19:31.300> for<00:19:31.540> example<00:19:31.600> as 00:19:32.040 --> 00:19:32.050 align:start position:0% fail like storing a list for example as 00:19:32.050 --> 00:19:34.080 align:start position:0% fail like storing a list for example as a<00:19:32.080> pure<00:19:32.380> computation<00:19:33.040> of<00:19:33.070> users<00:19:33.430> there's 00:19:34.080 --> 00:19:34.090 align:start position:0% a pure computation of users there's 00:19:34.090 --> 00:19:35.910 align:start position:0% a pure computation of users there's really<00:19:34.240> nothing<00:19:34.690> what<00:19:35.020> are<00:19:35.080> you<00:19:35.170> going<00:19:35.290> to<00:19:35.350> 22 00:19:35.910 --> 00:19:35.920 align:start position:0% really nothing what are you going to 22 00:19:35.920 --> 00:19:38.640 align:start position:0% really nothing what are you going to 22 ask<00:19:36.120> the<00:19:37.120> internet<00:19:37.420> how<00:19:37.780> to<00:19:37.810> sort<00:19:38.110> you<00:19:38.470> just 00:19:38.640 --> 00:19:38.650 align:start position:0% ask the internet how to sort you just 00:19:38.650 --> 00:19:40.380 align:start position:0% ask the internet how to sort you just like<00:19:38.800> way<00:19:38.950> to<00:19:39.010> sort<00:19:39.280> out<00:19:39.430> for<00:19:39.580> them<00:19:39.700> and<00:19:39.910> it 00:19:40.380 --> 00:19:40.390 align:start position:0% like way to sort out for them and it 00:19:40.390 --> 00:19:42.570 align:start position:0% like way to sort out for them and it works<00:19:40.540> there's<00:19:40.900> no<00:19:41.080> unless<00:19:41.770> you<00:19:41.830> ask<00:19:42.400> the 00:19:42.570 --> 00:19:42.580 align:start position:0% works there's no unless you ask the 00:19:42.580 --> 00:19:43.230 align:start position:0% works there's no unless you ask the staff<00:19:42.850> over 00:19:43.230 --> 00:19:43.240 align:start position:0% staff over 00:19:43.240 --> 00:19:46.560 align:start position:0% staff over yeah<00:19:44.010> yes<00:19:45.010> you<00:19:45.280> basically<00:19:46.000> there's<00:19:46.240> no<00:19:46.360> way 00:19:46.560 --> 00:19:46.570 align:start position:0% yeah yes you basically there's no way 00:19:46.570 --> 00:19:48.390 align:start position:0% yeah yes you basically there's no way that<00:19:46.720> there's<00:19:47.590> no<00:19:47.680> way<00:19:47.800> that<00:19:47.890> I<00:19:47.980> can<00:19:48.040> throw<00:19:48.280> an 00:19:48.390 --> 00:19:48.400 align:start position:0% that there's no way that I can throw an 00:19:48.400 --> 00:19:50.010 align:start position:0% that there's no way that I can throw an exception<00:19:48.490> there's<00:19:49.360> no<00:19:49.510> way<00:19:49.600> that<00:19:49.750> thinking 00:19:50.010 --> 00:19:50.020 align:start position:0% exception there's no way that thinking 00:19:50.020 --> 00:19:51.690 align:start position:0% exception there's no way that thinking with<00:19:50.110> a<00:19:50.170> call<00:19:50.380> because<00:19:50.740> the<00:19:51.040> network<00:19:51.340> failure 00:19:51.690 --> 00:19:51.700 align:start position:0% with a call because the network failure 00:19:51.700 --> 00:19:52.950 align:start position:0% with a call because the network failure there's<00:19:51.910> knowing<00:19:52.120> that<00:19:52.330> he's<00:19:52.480> our<00:19:52.660> leader 00:19:52.950 --> 00:19:52.960 align:start position:0% there's knowing that he's our leader 00:19:52.960 --> 00:19:54.450 align:start position:0% there's knowing that he's our leader right<00:19:53.170> from<00:19:53.380> the<00:19:53.470> disk<00:19:53.680> the<00:19:54.160> sorting 00:19:54.450 --> 00:19:54.460 align:start position:0% right from the disk the sorting 00:19:54.460 --> 00:19:56.280 align:start position:0% right from the disk the sorting algorithm<00:19:54.850> itself<00:19:55.150> is<00:19:55.330> pure<00:19:56.050> data 00:19:56.280 --> 00:19:56.290 align:start position:0% algorithm itself is pure data 00:19:56.290 --> 00:19:58.080 align:start position:0% algorithm itself is pure data transformation<00:19:56.980> from<00:19:57.130> list 00:19:58.080 --> 00:19:58.090 align:start position:0% transformation from list 00:19:58.090 --> 00:20:00.200 align:start position:0% transformation from list that's<00:19:58.719> an<00:19:58.779> example<00:19:59.019> of<00:19:59.259> like<00:19:59.440> a<00:19:59.469> perfection 00:20:00.200 --> 00:20:00.210 align:start position:0% that's an example of like a perfection 00:20:00.210 --> 00:20:02.729 align:start position:0% that's an example of like a perfection for<00:20:01.210> other<00:20:01.389> like<00:20:01.599> mathematical<00:20:02.200> functions<00:20:02.649> or 00:20:02.729 --> 00:20:02.739 align:start position:0% for other like mathematical functions or 00:20:02.739 --> 00:20:04.289 align:start position:0% for other like mathematical functions or operations<00:20:03.249> that<00:20:03.580> just<00:20:03.820> basically<00:20:03.969> stuff 00:20:04.289 --> 00:20:04.299 align:start position:0% operations that just basically stuff 00:20:04.299 --> 00:20:05.969 align:start position:0% operations that just basically stuff that<00:20:04.450> can't<00:20:04.690> possibly<00:20:04.869> fail<00:20:05.440> unless<00:20:05.679> it's 00:20:05.969 --> 00:20:05.979 align:start position:0% that can't possibly fail unless it's 00:20:05.979 --> 00:20:07.589 align:start position:0% that can't possibly fail unless it's implemented<00:20:06.340> wrong<00:20:06.729> but<00:20:07.059> like<00:20:07.239> there's<00:20:07.419> no 00:20:07.589 --> 00:20:07.599 align:start position:0% implemented wrong but like there's no 00:20:07.599 --> 00:20:12.419 align:start position:0% implemented wrong but like there's no like<00:20:07.629> random<00:20:08.349> reason<00:20:08.769> why<00:20:08.889> it<00:20:09.009> might<00:20:09.129> fit<00:20:11.429> so 00:20:12.419 --> 00:20:12.429 align:start position:0% like random reason why it might fit so 00:20:12.429 --> 00:20:14.129 align:start position:0% like random reason why it might fit so like<00:20:12.580> here's<00:20:12.820> you<00:20:13.059> know<00:20:13.090> like<00:20:13.840> starting<00:20:14.109> to 00:20:14.129 --> 00:20:14.139 align:start position:0% like here's you know like starting to 00:20:14.139 --> 00:20:15.239 align:start position:0% like here's you know like starting to get<00:20:14.259> into<00:20:14.440> something<00:20:14.619> with<00:20:14.769> something<00:20:14.919> simple 00:20:15.239 --> 00:20:15.249 align:start position:0% get into something with something simple 00:20:15.249 --> 00:20:17.549 align:start position:0% get into something with something simple looks<00:20:15.369> like<00:20:15.519> just<00:20:15.999> as<00:20:16.119> like<00:20:16.269> a<00:20:16.299> you<00:20:16.779> know<00:20:16.869> round 00:20:17.549 --> 00:20:17.559 align:start position:0% looks like just as like a you know round 00:20:17.559 --> 00:20:20.099 align:start position:0% looks like just as like a you know round like<00:20:18.009> a<00:20:18.059> common<00:20:19.059> framework<00:20:19.419> here<00:20:19.629> like<00:20:19.809> we<00:20:19.989> can 00:20:20.099 --> 00:20:20.109 align:start position:0% like a common framework here like we can 00:20:20.109 --> 00:20:22.409 align:start position:0% like a common framework here like we can talk<00:20:20.259> about<00:20:20.379> you<00:20:21.340> know<00:20:21.429> private<00:20:21.940> public<00:20:22.299> and 00:20:22.409 --> 00:20:22.419 align:start position:0% talk about you know private public and 00:20:22.419 --> 00:20:23.879 align:start position:0% talk about you know private public and private<00:20:22.659> keys<00:20:22.809> in<00:20:22.960> Imperial<00:20:23.349> they<00:20:23.710> use<00:20:23.859> a 00:20:23.879 --> 00:20:23.889 align:start position:0% private keys in Imperial they use a 00:20:23.889 --> 00:20:27.450 align:start position:0% private keys in Imperial they use a certain<00:20:24.450> signature<00:20:25.450> scheme<00:20:25.690> like<00:20:25.809> oh<00:20:26.309> yes<00:20:27.309> a 00:20:27.450 --> 00:20:27.460 align:start position:0% certain signature scheme like oh yes a 00:20:27.460 --> 00:20:31.109 align:start position:0% certain signature scheme like oh yes a on<00:20:27.669> this<00:20:28.029> particular<00:20:28.599> curve<00:20:28.919> people<00:20:30.119> levels 00:20:31.109 --> 00:20:31.119 align:start position:0% on this particular curve people levels 00:20:31.119 --> 00:20:34.099 align:start position:0% on this particular curve people levels probably<00:20:31.570> come<00:20:31.659> across<00:20:31.690> this<00:20:32.219> a<00:20:33.219> private<00:20:33.669> key 00:20:34.099 --> 00:20:34.109 align:start position:0% probably come across this a private key 00:20:34.109 --> 00:20:36.839 align:start position:0% probably come across this a private key uniquely<00:20:35.109> determines<00:20:35.529> a<00:20:35.619> party<00:20:36.070> this<00:20:36.639> might 00:20:36.839 --> 00:20:36.849 align:start position:0% uniquely determines a party this might 00:20:36.849 --> 00:20:38.820 align:start position:0% uniquely determines a party this might work<00:20:37.029> and<00:20:37.269> an<00:20:37.359> address<00:20:37.509> like<00:20:38.259> the<00:20:38.409> typical<00:20:38.589> if 00:20:38.820 --> 00:20:38.830 align:start position:0% work and an address like the typical if 00:20:38.830 --> 00:20:40.379 align:start position:0% work and an address like the typical if you're<00:20:38.979> in<00:20:39.070> the<00:20:39.159> dress<00:20:39.369> that<00:20:39.399> we<00:20:39.700> all<00:20:39.789> talk 00:20:40.379 --> 00:20:40.389 align:start position:0% you're in the dress that we all talk 00:20:40.389 --> 00:20:41.459 align:start position:0% you're in the dress that we all talk about<00:20:40.419> all<00:20:40.659> the<00:20:40.719> time<00:20:40.749> it's<00:20:41.080> basically<00:20:41.349> just 00:20:41.459 --> 00:20:41.469 align:start position:0% about all the time it's basically just 00:20:41.469 --> 00:20:45.299 align:start position:0% about all the time it's basically just like<00:20:41.589> blastoma<00:20:42.219> bytes<00:20:43.289> so<00:20:44.289> like<00:20:44.469> this<00:20:45.039> is<00:20:45.219> just 00:20:45.299 --> 00:20:45.309 align:start position:0% like blastoma bytes so like this is just 00:20:45.309 --> 00:20:46.440 align:start position:0% like blastoma bytes so like this is just a<00:20:45.399> common<00:20:45.639> framework<00:20:45.849> to<00:20:46.029> say<00:20:46.179> they're<00:20:46.359> like 00:20:46.440 --> 00:20:46.450 align:start position:0% a common framework to say they're like 00:20:46.450 --> 00:20:47.669 align:start position:0% a common framework to say they're like these<00:20:46.899> are<00:20:47.019> the<00:20:47.109> things<00:20:47.289> that<00:20:47.349> you<00:20:47.529> can 00:20:47.669 --> 00:20:47.679 align:start position:0% these are the things that you can 00:20:47.679 --> 00:20:49.019 align:start position:0% these are the things that you can actually<00:20:47.859> talk<00:20:48.129> about<00:20:48.369> in<00:20:48.460> these<00:20:48.549> like<00:20:48.759> these 00:20:49.019 --> 00:20:49.029 align:start position:0% actually talk about in these like these 00:20:49.029 --> 00:20:50.519 align:start position:0% actually talk about in these like these are<00:20:49.210> it's<00:20:49.749> probably<00:20:49.809> a<00:20:50.019> bit<00:20:50.109> difficult<00:20:50.229> to<00:20:50.440> see 00:20:50.519 --> 00:20:50.529 align:start position:0% are it's probably a bit difficult to see 00:20:50.529 --> 00:20:54.239 align:start position:0% are it's probably a bit difficult to see from<00:20:50.710> the<00:20:50.830> back<00:20:51.059> try<00:20:52.059> to<00:20:52.469> hear<00:20:53.469> but<00:20:54.099> like 00:20:54.239 --> 00:20:54.249 align:start position:0% from the back try to hear but like 00:20:54.249 --> 00:20:56.279 align:start position:0% from the back try to hear but like anybody<00:20:54.669> you<00:20:55.089> know<00:20:55.210> this<00:20:55.539> is<00:20:55.659> basically<00:20:56.019> like 00:20:56.279 --> 00:20:56.289 align:start position:0% anybody you know this is basically like 00:20:56.289 --> 00:20:58.499 align:start position:0% anybody you know this is basically like kind<00:20:56.919> of<00:20:56.950> like<00:20:57.159> parts<00:20:57.849> where<00:20:58.059> you<00:20:58.089> know<00:20:58.239> by<00:20:58.450> the 00:20:58.499 --> 00:20:58.509 align:start position:0% kind of like parts where you know by the 00:20:58.509 --> 00:21:00.149 align:start position:0% kind of like parts where you know by the types<00:20:58.809> of<00:20:58.960> society<00:20:59.409> using<00:20:59.739> the<00:20:59.799> type<00:20:59.979> system 00:21:00.149 --> 00:21:00.159 align:start position:0% types of society using the type system 00:21:00.159 --> 00:21:01.469 align:start position:0% types of society using the type system this<00:21:00.399> way<00:21:00.580> your<00:21:00.729> place<00:21:00.879> in<00:21:00.999> the<00:21:01.089> building<00:21:01.389> at 00:21:01.469 --> 00:21:01.479 align:start position:0% this way your place in the building at 00:21:01.479 --> 00:21:03.570 align:start position:0% this way your place in the building at university<00:21:02.200> to<00:21:02.320> top<00:21:02.769> so<00:21:03.009> like<00:21:03.159> there's 00:21:03.570 --> 00:21:03.580 align:start position:0% university to top so like there's 00:21:03.580 --> 00:21:05.770 align:start position:0% university to top so like there's private<00:21:03.940> either<00:21:04.149> public<00:21:04.659> keys<00:21:04.869> in<00:21:05.019> it 00:21:05.770 --> 00:21:05.780 align:start position:0% private either public keys in it 00:21:05.780 --> 00:21:08.020 align:start position:0% private either public keys in it one<00:21:06.710> of<00:21:06.770> these<00:21:06.860> things<00:21:07.040> in<00:21:07.250> a<00:21:07.280> level<00:21:07.820> they're 00:21:08.020 --> 00:21:08.030 align:start position:0% one of these things in a level they're 00:21:08.030 --> 00:21:09.820 align:start position:0% one of these things in a level they're like<00:21:08.210> ice<00:21:08.480> drinks<00:21:08.810> of<00:21:09.050> course<00:21:09.080> everything<00:21:09.740> at 00:21:09.820 --> 00:21:09.830 align:start position:0% like ice drinks of course everything at 00:21:09.830 --> 00:21:11.590 align:start position:0% like ice drinks of course everything at some<00:21:10.040> point<00:21:10.280> quite<00:21:10.610> straight<00:21:10.940> away<00:21:11.180> but<00:21:11.480> the 00:21:11.590 --> 00:21:11.600 align:start position:0% some point quite straight away but the 00:21:11.600 --> 00:21:12.940 align:start position:0% some point quite straight away but the point<00:21:11.810> is<00:21:11.900> so<00:21:12.020> like<00:21:12.170> basically<00:21:12.320> build<00:21:12.830> up 00:21:12.940 --> 00:21:12.950 align:start position:0% point is so like basically build up 00:21:12.950 --> 00:21:14.260 align:start position:0% point is so like basically build up abstractions<00:21:13.520> like<00:21:13.550> to<00:21:13.760> do<00:21:13.880> and<00:21:14.030> every<00:21:14.180> other 00:21:14.260 --> 00:21:14.270 align:start position:0% abstractions like to do and every other 00:21:14.270 --> 00:21:16.000 align:start position:0% abstractions like to do and every other language<00:21:14.690> so<00:21:14.900> that<00:21:14.930> you<00:21:15.320> know<00:21:15.410> you<00:21:15.800> can't 00:21:16.000 --> 00:21:16.010 align:start position:0% language so that you know you can't 00:21:16.010 --> 00:21:17.830 align:start position:0% language so that you know you can't confuse<00:21:16.460> things<00:21:16.880> like<00:21:17.120> God<00:21:17.330> your<00:21:17.540> private 00:21:17.830 --> 00:21:17.840 align:start position:0% confuse things like God your private 00:21:17.840 --> 00:21:19.480 align:start position:0% confuse things like God your private keys<00:21:18.020> even<00:21:18.260> though<00:21:18.320> they<00:21:18.440> both<00:21:18.650> refer<00:21:19.100> by 00:21:19.480 --> 00:21:19.490 align:start position:0% keys even though they both refer by 00:21:19.490 --> 00:21:21.160 align:start position:0% keys even though they both refer by strings<00:21:19.850> you<00:21:20.390> basically<00:21:20.660> trying<00:21:20.930> to<00:21:20.990> like 00:21:21.160 --> 00:21:21.170 align:start position:0% strings you basically trying to like 00:21:21.170 --> 00:21:22.630 align:start position:0% strings you basically trying to like abstraction<00:21:21.710> way<00:21:21.800> like<00:21:21.980> the<00:21:22.100> low-level 00:21:22.630 --> 00:21:22.640 align:start position:0% abstraction way like the low-level 00:21:22.640 --> 00:21:29.800 align:start position:0% abstraction way like the low-level things<00:21:27.700> and<00:21:28.700> then<00:21:28.910> addressing<00:21:29.420> the<00:21:29.630> whatever 00:21:29.800 --> 00:21:29.810 align:start position:0% things and then addressing the whatever 00:21:29.810 --> 00:21:31.270 align:start position:0% things and then addressing the whatever it's<00:21:30.050> the<00:21:30.140> hash<00:21:30.290> result<00:21:30.710> so<00:21:30.830> it<00:21:30.890> could<00:21:31.040> be<00:21:31.160> like 00:21:31.270 --> 00:21:31.280 align:start position:0% it's the hash result so it could be like 00:21:31.280 --> 00:21:32.860 align:start position:0% it's the hash result so it could be like an<00:21:31.400> X<00:21:31.550> it's<00:21:31.880> usually<00:21:32.000> written<00:21:32.270> as<00:21:32.570> a<00:21:32.630> hex 00:21:32.860 --> 00:21:32.870 align:start position:0% an X it's usually written as a hex 00:21:32.870 --> 00:21:34.380 align:start position:0% an X it's usually written as a hex string<00:21:32.960> or<00:21:33.260> whatever<00:21:33.320> it's<00:21:33.740> very<00:21:34.130> high 00:21:34.380 --> 00:21:34.390 align:start position:0% string or whatever it's very high 00:21:34.390 --> 00:21:36.670 align:start position:0% string or whatever it's very high strength<00:21:35.390> but<00:21:35.630> it<00:21:35.840> possibly<00:21:36.290> whatever 00:21:36.670 --> 00:21:36.680 align:start position:0% strength but it possibly whatever 00:21:36.680 --> 00:21:39.310 align:start position:0% strength but it possibly whatever so<00:21:37.610> like<00:21:37.760> example<00:21:38.270> of<00:21:38.360> purity<00:21:38.780> for<00:21:38.960> example 00:21:39.310 --> 00:21:39.320 align:start position:0% so like example of purity for example 00:21:39.320 --> 00:21:40.690 align:start position:0% so like example of purity for example here<00:21:39.500> like<00:21:39.680> these<00:21:39.920> are<00:21:40.100> kind<00:21:40.220> of<00:21:40.370> boring 00:21:40.690 --> 00:21:40.700 align:start position:0% here like these are kind of boring 00:21:40.700 --> 00:21:46.330 align:start position:0% here like these are kind of boring functions<00:21:41.330> or<00:21:41.420> whatever<00:21:41.630> but<00:21:44.830> like<00:21:45.830> basically 00:21:46.330 --> 00:21:46.340 align:start position:0% functions or whatever but like basically 00:21:46.340 --> 00:21:49.120 align:start position:0% functions or whatever but like basically a<00:21:46.430> way<00:21:46.610> to<00:21:46.670> like<00:21:47.030> unwrap<00:21:47.900> things<00:21:48.260> or<00:21:48.560> to<00:21:48.830> you 00:21:49.120 --> 00:21:49.130 align:start position:0% a way to like unwrap things or to you 00:21:49.130 --> 00:21:50.380 align:start position:0% a way to like unwrap things or to you know<00:21:49.160> basically<00:21:49.340> to<00:21:49.730> take<00:21:49.850> a<00:21:49.910> public<00:21:50.150> he 00:21:50.380 --> 00:21:50.390 align:start position:0% know basically to take a public he 00:21:50.390 --> 00:21:51.550 align:start position:0% know basically to take a public he introduced<00:21:50.720> the<00:21:50.810> hex<00:21:50.990> string<00:21:51.080> there's<00:21:51.410> pretty 00:21:51.550 --> 00:21:51.560 align:start position:0% introduced the hex string there's pretty 00:21:51.560 --> 00:21:53.170 align:start position:0% introduced the hex string there's pretty much<00:21:51.620> no<00:21:51.890> way<00:21:51.920> that<00:21:52.310> can<00:21:52.430> fail<00:21:52.610> because<00:21:52.880> you're 00:21:53.170 --> 00:21:53.180 align:start position:0% much no way that can fail because you're 00:21:53.180 --> 00:21:55.090 align:start position:0% much no way that can fail because you're taking<00:21:53.420> action<00:21:53.540> so<00:21:53.990> it's<00:21:54.320> not<00:21:54.410> a<00:21:54.470> computation 00:21:55.090 --> 00:21:55.100 align:start position:0% taking action so it's not a computation 00:21:55.100 --> 00:21:57.970 align:start position:0% taking action so it's not a computation Pedernales<00:21:55.550> in<00:21:55.730> you<00:21:56.480> can<00:21:56.660> basically<00:21:57.620> you<00:21:57.860> can 00:21:57.970 --> 00:21:57.980 align:start position:0% Pedernales in you can basically you can 00:21:57.980 --> 00:21:59.560 align:start position:0% Pedernales in you can basically you can ask<00:21:58.130> for<00:21:58.340> like<00:21:58.550> how<00:21:58.940> to<00:21:59.000> get<00:21:59.180> them<00:21:59.330> you<00:21:59.480> know 00:21:59.560 --> 00:21:59.570 align:start position:0% ask for like how to get them you know 00:21:59.570 --> 00:22:02.500 align:start position:0% ask for like how to get them you know how<00:21:59.690> do<00:21:59.750> you<00:21:59.780> make<00:21:59.900> a<00:21:59.960> private<00:22:00.350> eye<00:22:00.500> sorry<00:22:01.510> how 00:22:02.500 --> 00:22:02.510 align:start position:0% how do you make a private eye sorry how 00:22:02.510 --> 00:22:05.260 align:start position:0% how do you make a private eye sorry how do<00:22:02.570> how<00:22:03.350> to<00:22:03.380> make<00:22:03.590> a<00:22:03.730> public<00:22:04.730> key<00:22:04.880> from<00:22:05.150> a 00:22:05.260 --> 00:22:05.270 align:start position:0% do how to make a public key from a 00:22:05.270 --> 00:22:07.900 align:start position:0% do how to make a public key from a private<00:22:05.630> key<00:22:05.810> something<00:22:06.590> that<00:22:06.740> again<00:22:07.190> lace<00:22:07.760> in 00:22:07.900 --> 00:22:07.910 align:start position:0% private key something that again lace in 00:22:07.910 --> 00:22:08.950 align:start position:0% private key something that again lace in the<00:22:07.940> description<00:22:08.360> of<00:22:08.480> a<00:22:08.540> statement<00:22:08.780> last 00:22:08.950 --> 00:22:08.960 align:start position:0% the description of a statement last 00:22:08.960 --> 00:22:10.690 align:start position:0% the description of a statement last night<00:22:09.130> accommodation<00:22:10.130> like<00:22:10.310> actually 00:22:10.690 --> 00:22:10.700 align:start position:0% night accommodation like actually 00:22:10.700 --> 00:22:12.410 align:start position:0% night accommodation like actually obtaining<00:22:11.060> slices<00:22:11.660> or<00:22:11.840> whatever 00:22:12.410 --> 00:22:12.420 align:start position:0% obtaining slices or whatever 00:22:12.420 --> 00:22:13.730 align:start position:0% obtaining slices or whatever because<00:22:12.690> you<00:22:12.810> know<00:22:12.930> that<00:22:13.050> hashes<00:22:13.380> the<00:22:13.470> second 00:22:13.730 --> 00:22:13.740 align:start position:0% because you know that hashes the second 00:22:13.740 --> 00:22:15.290 align:start position:0% because you know that hashes the second size<00:22:13.950> you<00:22:14.220> know<00:22:14.340> that<00:22:14.460> the<00:22:14.550> slice<00:22:14.820> won't<00:22:15.060> fail 00:22:15.290 --> 00:22:15.300 align:start position:0% size you know that the slice won't fail 00:22:15.300 --> 00:22:17.960 align:start position:0% size you know that the slice won't fail is<00:22:15.600> it<00:22:15.750> pure<00:22:15.990> computations<00:22:16.700> these<00:22:17.700> are<00:22:17.820> kind 00:22:17.960 --> 00:22:17.970 align:start position:0% is it pure computations these are kind 00:22:17.970 --> 00:22:19.880 align:start position:0% is it pure computations these are kind of<00:22:18.000> boring<00:22:18.210> right<00:22:18.440> these<00:22:19.440> are<00:22:19.500> the<00:22:19.650> ones<00:22:19.800> that 00:22:19.880 --> 00:22:19.890 align:start position:0% of boring right these are the ones that 00:22:19.890 --> 00:22:21.440 align:start position:0% of boring right these are the ones that are<00:22:20.130> in<00:22:20.280> some<00:22:20.490> sense<00:22:20.670> effectual<00:22:21.150> right 00:22:21.440 --> 00:22:21.450 align:start position:0% are in some sense effectual right 00:22:21.450 --> 00:22:24.440 align:start position:0% are in some sense effectual right because<00:22:21.780> like<00:22:21.960> is<00:22:22.740> every<00:22:23.130> next<00:22:23.520> ring<00:22:23.730> or<00:22:24.270> this 00:22:24.440 --> 00:22:24.450 align:start position:0% because like is every next ring or this 00:22:24.450 --> 00:22:26.000 align:start position:0% because like is every next ring or this every<00:22:24.780> byte<00:22:24.960> string<00:22:25.290> or<00:22:25.410> Hexter<00:22:25.740> never 00:22:26.000 --> 00:22:26.010 align:start position:0% every byte string or Hexter never 00:22:26.010 --> 00:22:28.640 align:start position:0% every byte string or Hexter never correspond<00:22:26.520> to<00:22:26.580> a<00:22:26.670> public<00:22:27.000> key<00:22:27.290> probably<00:22:28.290> not 00:22:28.640 --> 00:22:28.650 align:start position:0% correspond to a public key probably not 00:22:28.650 --> 00:22:30.560 align:start position:0% correspond to a public key probably not it's<00:22:29.040> not<00:22:29.160> 20<00:22:29.460> bytes<00:22:29.610> long<00:22:29.850> it<00:22:30.030> doesn't<00:22:30.420> so 00:22:30.560 --> 00:22:30.570 align:start position:0% it's not 20 bytes long it doesn't so 00:22:30.570 --> 00:22:32.240 align:start position:0% it's not 20 bytes long it doesn't so there's<00:22:30.750> like<00:22:30.930> a<00:22:30.960> potential<00:22:31.470> avail<00:22:31.920> here 00:22:32.240 --> 00:22:32.250 align:start position:0% there's like a potential avail here 00:22:32.250 --> 00:22:41.690 align:start position:0% there's like a potential avail here which<00:22:32.400> I<00:22:39.200> can<00:22:40.200> you<00:22:40.320> can<00:22:40.650> anything<00:22:41.220> it<00:22:41.490> ain't 00:22:41.690 --> 00:22:41.700 align:start position:0% which I can you can anything it ain't 00:22:41.700 --> 00:22:46.760 align:start position:0% which I can you can anything it ain't extreme<00:22:42.300> become<00:22:42.630> the<00:22:42.720> private<00:22:42.960> key<00:22:45.620> there<00:22:46.620> are 00:22:46.760 --> 00:22:46.770 align:start position:0% extreme become the private key there are 00:22:46.770 --> 00:22:50.270 align:start position:0% extreme become the private key there are cases<00:22:47.780> in<00:22:48.780> any<00:22:48.960> add<00:22:49.170> in<00:22:49.530> any<00:22:49.740> extreme 00:22:50.270 --> 00:22:50.280 align:start position:0% cases in any add in any extreme 00:22:50.280 --> 00:22:52.340 align:start position:0% cases in any add in any extreme correspond<00:22:50.820> address<00:22:51.330> though<00:22:51.630> it<00:22:51.960> has<00:22:52.080> to<00:22:52.200> be<00:22:52.320> a 00:22:52.340 --> 00:22:52.350 align:start position:0% correspond address though it has to be a 00:22:52.350 --> 00:22:56.390 align:start position:0% correspond address though it has to be a certain<00:22:52.680> number<00:22:52.710> of<00:22:52.920> bytes<00:22:53.190> long<00:22:55.310> here's<00:22:56.310> an 00:22:56.390 --> 00:22:56.400 align:start position:0% certain number of bytes long here's an 00:22:56.400 --> 00:22:57.830 align:start position:0% certain number of bytes long here's an example<00:22:56.640> of<00:22:56.880> like<00:22:57.060> you<00:22:57.510> know<00:22:57.630> whatever 00:22:57.830 --> 00:22:57.840 align:start position:0% example of like you know whatever 00:22:57.840 --> 00:22:59.810 align:start position:0% example of like you know whatever encoding<00:22:58.470> you<00:22:58.710> know<00:22:58.770> what<00:22:59.400> I<00:22:59.490> say<00:22:59.670> like 00:22:59.810 --> 00:22:59.820 align:start position:0% encoding you know what I say like 00:22:59.820 --> 00:23:01.910 align:start position:0% encoding you know what I say like encoding<00:23:00.300> certain<00:23:00.960> these<00:23:01.140> are<00:23:01.290> like<00:23:01.440> infected 00:23:01.910 --> 00:23:01.920 align:start position:0% encoding certain these are like infected 00:23:01.920 --> 00:23:04.220 align:start position:0% encoding certain these are like infected or<00:23:02.040> not<00:23:02.070> pure<00:23:02.370> it's<00:23:02.670> because<00:23:03.000> basically<00:23:03.720> like 00:23:04.220 --> 00:23:04.230 align:start position:0% or not pure it's because basically like 00:23:04.230 --> 00:23:06.620 align:start position:0% or not pure it's because basically like you<00:23:04.470> look<00:23:04.620> at<00:23:04.710> this<00:23:04.890> like<00:23:05.190> yeah<00:23:05.910> okay<00:23:06.360> maybe 00:23:06.620 --> 00:23:06.630 align:start position:0% you look at this like yeah okay maybe 00:23:06.630 --> 00:23:08.420 align:start position:0% you look at this like yeah okay maybe I'm<00:23:06.810> going<00:23:07.110> through<00:23:07.560> the<00:23:07.710> specification 00:23:08.420 --> 00:23:08.430 align:start position:0% I'm going through the specification 00:23:08.430 --> 00:23:09.860 align:start position:0% I'm going through the specification somewhere<00:23:08.820> if<00:23:08.910> you<00:23:08.940> read<00:23:09.150> the<00:23:09.240> docs<00:23:09.450> how<00:23:09.810> do 00:23:09.860 --> 00:23:09.870 align:start position:0% somewhere if you read the docs how do 00:23:09.870 --> 00:23:11.660 align:start position:0% somewhere if you read the docs how do you<00:23:10.050> talk<00:23:10.260> how<00:23:10.530> do<00:23:10.590> you<00:23:10.650> encode<00:23:11.010> data<00:23:11.250> that<00:23:11.520> can 00:23:11.660 --> 00:23:11.670 align:start position:0% you talk how do you encode data that can 00:23:11.670 --> 00:23:14.060 align:start position:0% you talk how do you encode data that can be<00:23:11.700> read<00:23:12.030> by<00:23:12.260> Imperial<00:23:13.260> smart<00:23:13.500> contracted 00:23:14.060 --> 00:23:14.070 align:start position:0% be read by Imperial smart contracted 00:23:14.070 --> 00:23:16.540 align:start position:0% be read by Imperial smart contracted through<00:23:14.250> its<00:23:14.790> through<00:23:14.940> codec<00:23:15.390> schema<00:23:15.810> called 00:23:16.540 --> 00:23:16.550 align:start position:0% through its through codec schema called 00:23:16.550 --> 00:23:18.800 align:start position:0% through its through codec schema called NDIS<00:23:17.550> or<00:23:17.670> something<00:23:18.030> if<00:23:18.120> it<00:23:18.210> hasn't<00:23:18.390> even<00:23:18.540> in<00:23:18.720> a 00:23:18.800 --> 00:23:18.810 align:start position:0% NDIS or something if it hasn't even in a 00:23:18.810 --> 00:23:21.050 align:start position:0% NDIS or something if it hasn't even in a middle<00:23:19.140> but<00:23:19.860> you<00:23:20.040> know<00:23:20.160> basically<00:23:20.760> for<00:23:21.000> any 00:23:21.050 --> 00:23:21.060 align:start position:0% middle but you know basically for any 00:23:21.060 --> 00:23:22.340 align:start position:0% middle but you know basically for any data<00:23:21.360> type<00:23:21.600> that<00:23:21.810> you<00:23:21.870> should<00:23:22.020> be<00:23:22.110> able<00:23:22.170> to 00:23:22.340 --> 00:23:22.350 align:start position:0% data type that you should be able to 00:23:22.350 --> 00:23:24.380 align:start position:0% data type that you should be able to communicate<00:23:22.680> across<00:23:23.070> a<00:23:23.190> contractor<00:23:23.940> boundary 00:23:24.380 --> 00:23:24.390 align:start position:0% communicate across a contractor boundary 00:23:24.390 --> 00:23:26.570 align:start position:0% communicate across a contractor boundary line<00:23:25.170> there<00:23:25.530> should<00:23:25.680> be<00:23:25.800> a<00:23:25.830> way<00:23:25.980> to<00:23:26.010> turn<00:23:26.310> it<00:23:26.370> in 00:23:26.570 --> 00:23:26.580 align:start position:0% line there should be a way to turn it in 00:23:26.580 --> 00:23:28.890 align:start position:0% line there should be a way to turn it in the<00:23:26.670> Sun<00:23:26.880> like<00:23:27.120> bytes<00:23:27.420> from<00:23:27.720> your<00:23:27.930> SM 00:23:28.890 --> 00:23:28.900 align:start position:0% the Sun like bytes from your SM 00:23:28.900 --> 00:23:31.290 align:start position:0% the Sun like bytes from your SM and<00:23:29.170> similarly<00:23:29.920> like<00:23:30.070> if<00:23:30.460> you<00:23:30.610> wanted<00:23:30.880> to<00:23:31.059> code 00:23:31.290 --> 00:23:31.300 align:start position:0% and similarly like if you wanted to code 00:23:31.300 --> 00:23:33.600 align:start position:0% and similarly like if you wanted to code like<00:23:31.510> a<00:23:31.540> to<00:23:31.809> pool<00:23:32.050> of<00:23:32.230> and<00:23:32.530> you<00:23:32.620> know<00:23:32.740> Olivia 00:23:33.600 --> 00:23:33.610 align:start position:0% like a to pool of and you know Olivia 00:23:33.610 --> 00:23:35.160 align:start position:0% like a to pool of and you know Olivia page<00:23:33.910> we're<00:23:34.059> going<00:23:34.180> to<00:23:34.420> code<00:23:34.570> like<00:23:34.720> a<00:23:34.750> tuple<00:23:35.110> of 00:23:35.160 --> 00:23:35.170 align:start position:0% page we're going to code like a tuple of 00:23:35.170 --> 00:23:37.560 align:start position:0% page we're going to code like a tuple of EBM<00:23:35.559> types<00:23:35.890> eat<00:23:36.520> some<00:23:36.730> way<00:23:36.850> to<00:23:36.910> parse<00:23:37.270> hex 00:23:37.560 --> 00:23:37.570 align:start position:0% EBM types eat some way to parse hex 00:23:37.570 --> 00:23:39.690 align:start position:0% EBM types eat some way to parse hex things<00:23:37.840> into<00:23:38.140> those<00:23:38.260> things<00:23:38.590> so<00:23:39.309> this<00:23:39.430> is<00:23:39.550> like 00:23:39.690 --> 00:23:39.700 align:start position:0% things into those things so this is like 00:23:39.700 --> 00:23:41.070 align:start position:0% things into those things so this is like basically<00:23:40.120> like<00:23:40.420> this<00:23:40.600> is<00:23:40.750> a<00:23:40.780> language 00:23:41.070 --> 00:23:41.080 align:start position:0% basically like this is a language 00:23:41.080 --> 00:23:43.020 align:start position:0% basically like this is a language specific<00:23:41.590> idea<00:23:41.890> that<00:23:42.160> like<00:23:42.340> you<00:23:42.700> know<00:23:42.790> there's 00:23:43.020 --> 00:23:43.030 align:start position:0% specific idea that like you know there's 00:23:43.030 --> 00:23:44.820 align:start position:0% specific idea that like you know there's some<00:23:43.240> for<00:23:43.600> some<00:23:43.780> types<00:23:44.050> out<00:23:44.260> there<00:23:44.320> we<00:23:44.650> can 00:23:44.820 --> 00:23:44.830 align:start position:0% some for some types out there we can 00:23:44.830 --> 00:23:46.850 align:start position:0% some for some types out there we can encode<00:23:45.370> them<00:23:45.610> and<00:23:45.790> for<00:23:45.940> some<00:23:46.090> times 00:23:46.850 --> 00:23:46.860 align:start position:0% encode them and for some times 00:23:46.860 --> 00:23:48.870 align:start position:0% encode them and for some times ideally<00:23:47.860> there's<00:23:48.130> the<00:23:48.309> same<00:23:48.490> right<00:23:48.700> to 00:23:48.870 --> 00:23:48.880 align:start position:0% ideally there's the same right to 00:23:48.880 --> 00:23:51.360 align:start position:0% ideally there's the same right to anybody<00:23:49.420> should<00:23:49.540> be<00:23:49.720> able<00:23:49.809> to<00:23:49.960> do<00:23:50.220> but<00:23:51.220> then 00:23:51.360 --> 00:23:51.370 align:start position:0% anybody should be able to do but then 00:23:51.370 --> 00:23:53.370 align:start position:0% anybody should be able to do but then like<00:23:51.580> here's<00:23:51.970> this<00:23:52.090> idea<00:23:52.420> you<00:23:52.870> know<00:23:52.990> like<00:23:53.170> okay 00:23:53.370 --> 00:23:53.380 align:start position:0% like here's this idea you know like okay 00:23:53.380 --> 00:23:55.170 align:start position:0% like here's this idea you know like okay we<00:23:53.770> have<00:23:53.980> like<00:23:54.220> a<00:23:54.340> texturing<00:23:54.790> we<00:23:54.940> want<00:23:55.120> to 00:23:55.170 --> 00:23:55.180 align:start position:0% we have like a texturing we want to 00:23:55.180 --> 00:23:56.820 align:start position:0% we have like a texturing we want to parse<00:23:55.390> it<00:23:55.570> into<00:23:55.660> something<00:23:55.990> it<00:23:56.650> has<00:23:56.800> a 00:23:56.820 --> 00:23:56.830 align:start position:0% parse it into something it has a 00:23:56.830 --> 00:23:58.830 align:start position:0% parse it into something it has a particular<00:23:57.070> type<00:23:57.700> and<00:23:58.059> we're<00:23:58.510> making<00:23:58.750> a 00:23:58.830 --> 00:23:58.840 align:start position:0% particular type and we're making a 00:23:58.840 --> 00:24:00.450 align:start position:0% particular type and we're making a constraint<00:23:59.410> on<00:23:59.559> this<00:23:59.770> particular<00:24:00.280> type 00:24:00.450 --> 00:24:00.460 align:start position:0% constraint on this particular type 00:24:00.460 --> 00:24:02.280 align:start position:0% constraint on this particular type that's<00:24:00.760> somewhere<00:24:01.210> you've<00:24:01.450> defined<00:24:01.840> products 00:24:02.280 --> 00:24:02.290 align:start position:0% that's somewhere you've defined products 00:24:02.290 --> 00:24:04.380 align:start position:0% that's somewhere you've defined products for<00:24:02.500> this<00:24:02.559> thing<00:24:02.800> this<00:24:03.580> still<00:24:03.850> might<00:24:04.059> fail 00:24:04.380 --> 00:24:04.390 align:start position:0% for this thing this still might fail 00:24:04.390 --> 00:24:06.360 align:start position:0% for this thing this still might fail because<00:24:04.929> like<00:24:05.170> it<00:24:05.650> doesn't<00:24:05.950> matter<00:24:06.100> that<00:24:06.190> the 00:24:06.360 --> 00:24:06.370 align:start position:0% because like it doesn't matter that the 00:24:06.370 --> 00:24:08.610 align:start position:0% because like it doesn't matter that the thing<00:24:06.610> has<00:24:06.850> the<00:24:06.880> decode<00:24:07.720> instance<00:24:08.170> the 00:24:08.610 --> 00:24:08.620 align:start position:0% thing has the decode instance the 00:24:08.620 --> 00:24:09.990 align:start position:0% thing has the decode instance the problem<00:24:09.040> is<00:24:09.160> is<00:24:09.340> that<00:24:09.460> the<00:24:09.580> thing<00:24:09.760> that<00:24:09.790> you're 00:24:09.990 --> 00:24:10.000 align:start position:0% problem is is that the thing that you're 00:24:10.000 --> 00:24:12.000 align:start position:0% problem is is that the thing that you're during<00:24:10.510> inhabit<00:24:10.990> and<00:24:11.230> this<00:24:11.559> table<00:24:11.830> by 00:24:12.000 --> 00:24:12.010 align:start position:0% during inhabit and this table by 00:24:12.010 --> 00:24:14.490 align:start position:0% during inhabit and this table by straining<00:24:12.370> might<00:24:13.030> be<00:24:13.300> coming<00:24:14.080> from<00:24:14.110> somewhere 00:24:14.490 --> 00:24:14.500 align:start position:0% straining might be coming from somewhere 00:24:14.500 --> 00:24:16.200 align:start position:0% straining might be coming from somewhere else<00:24:14.679> where<00:24:14.950> you<00:24:14.980> get<00:24:15.370> done<00:24:15.550> it's<00:24:15.700> not<00:24:15.880> long 00:24:16.200 --> 00:24:16.210 align:start position:0% else where you get done it's not long 00:24:16.210 --> 00:24:17.820 align:start position:0% else where you get done it's not long enough<00:24:16.450> for<00:24:16.510> it<00:24:16.780> doesn't<00:24:17.080> correspond<00:24:17.530> in<00:24:17.679> some 00:24:17.820 --> 00:24:17.830 align:start position:0% enough for it doesn't correspond in some 00:24:17.830 --> 00:24:19.140 align:start position:0% enough for it doesn't correspond in some ways<00:24:17.980> nothing<00:24:18.190> in<00:24:18.460> your<00:24:18.610> trying<00:24:18.820> to<00:24:18.850> decode 00:24:19.140 --> 00:24:19.150 align:start position:0% ways nothing in your trying to decode 00:24:19.150 --> 00:24:21.150 align:start position:0% ways nothing in your trying to decode because<00:24:19.990> you<00:24:20.110> made<00:24:20.260> a<00:24:20.290> mistake<00:24:20.590> somewhere<00:24:20.770> so 00:24:21.150 --> 00:24:21.160 align:start position:0% because you made a mistake somewhere so 00:24:21.160 --> 00:24:23.370 align:start position:0% because you made a mistake somewhere so in<00:24:21.309> this<00:24:21.429> second<00:24:21.850> sense<00:24:22.720> like<00:24:22.960> this<00:24:23.110> is<00:24:23.260> an 00:24:23.370 --> 00:24:23.380 align:start position:0% in this second sense like this is an 00:24:23.380 --> 00:24:24.990 align:start position:0% in this second sense like this is an impure<00:24:23.740> computation<00:24:24.370> because<00:24:24.640> it<00:24:24.820> might 00:24:24.990 --> 00:24:25.000 align:start position:0% impure computation because it might 00:24:25.000 --> 00:24:26.640 align:start position:0% impure computation because it might produce<00:24:25.210> the<00:24:25.900> value<00:24:26.080> that<00:24:26.260> you're<00:24:26.410> looking 00:24:26.640 --> 00:24:26.650 align:start position:0% produce the value that you're looking 00:24:26.650 --> 00:24:27.150 align:start position:0% produce the value that you're looking for 00:24:27.150 --> 00:24:27.160 align:start position:0% for 00:24:27.160 --> 00:24:28.650 align:start position:0% for it<00:24:27.370> might<00:24:27.520> also<00:24:27.670> produce<00:24:28.000> a<00:24:28.270> parse<00:24:28.480> error 00:24:28.650 --> 00:24:28.660 align:start position:0% it might also produce a parse error 00:24:28.660 --> 00:24:29.970 align:start position:0% it might also produce a parse error instead<00:24:29.140> this<00:24:29.470> you're<00:24:29.650> telling<00:24:29.920> you 00:24:29.970 --> 00:24:29.980 align:start position:0% instead this you're telling you 00:24:29.980 --> 00:24:35.400 align:start position:0% instead this you're telling you basically<00:24:33.030> this<00:24:34.030> is<00:24:34.240> just<00:24:34.420> basically<00:24:35.110> saying 00:24:35.400 --> 00:24:35.410 align:start position:0% basically this is just basically saying 00:24:35.410 --> 00:24:38.279 align:start position:0% basically this is just basically saying what<00:24:35.590> I<00:24:35.620> could<00:24:35.830> say 00:24:38.279 --> 00:24:38.289 align:start position:0% 00:24:38.289 --> 00:24:40.889 align:start position:0% and<00:24:39.250> then<00:24:39.639> like<00:24:39.820> usually<00:24:40.299> what<00:24:40.480> we<00:24:40.570> say<00:24:40.750> it's 00:24:40.889 --> 00:24:40.899 align:start position:0% and then like usually what we say it's 00:24:40.899 --> 00:24:43.440 align:start position:0% and then like usually what we say it's like<00:24:41.049> this<00:24:41.980> last<00:24:42.220> computation<00:24:43.000> or<00:24:43.090> ever<00:24:43.240> that 00:24:43.440 --> 00:24:43.450 align:start position:0% like this last computation or ever that 00:24:43.450 --> 00:24:46.560 align:start position:0% like this last computation or ever that takes<00:24:43.720> it<00:24:44.200> takes<00:24:44.500> a<00:24:44.679> hex<00:24:44.860> string<00:24:44.950> and<00:24:45.279> and<00:24:45.570> runs 00:24:46.560 --> 00:24:46.570 align:start position:0% takes it takes a hex string and and runs 00:24:46.570 --> 00:24:48.360 align:start position:0% takes it takes a hex string and and runs it<00:24:46.809> into<00:24:47.110> either<00:24:47.289> something<00:24:47.919> of<00:24:48.039> the<00:24:48.129> type<00:24:48.309> of 00:24:48.360 --> 00:24:48.370 align:start position:0% it into either something of the type of 00:24:48.370 --> 00:24:50.460 align:start position:0% it into either something of the type of parse<00:24:48.669> error<00:24:48.940> or<00:24:49.269> now<00:24:49.720> you're<00:24:49.960> looking<00:24:50.259> for 00:24:50.460 --> 00:24:50.470 align:start position:0% parse error or now you're looking for 00:24:50.470 --> 00:24:52.619 align:start position:0% parse error or now you're looking for it's<00:24:51.070> like<00:24:51.250> basically<00:24:51.730> you<00:24:51.909> can<00:24:52.090> think<00:24:52.480> about 00:24:52.619 --> 00:24:52.629 align:start position:0% it's like basically you can think about 00:24:52.629 --> 00:24:54.450 align:start position:0% it's like basically you can think about this<00:24:52.809> so<00:24:52.960> like<00:24:53.080> resolve<00:24:53.500> the<00:24:53.710> effects<00:24:54.009> at<00:24:54.279> some 00:24:54.450 --> 00:24:54.460 align:start position:0% this so like resolve the effects at some 00:24:54.460 --> 00:24:55.889 align:start position:0% this so like resolve the effects at some point<00:24:54.700> like<00:24:54.850> all<00:24:55.090> the<00:24:55.179> effects<00:24:55.450> have<00:24:55.629> to<00:24:55.659> come 00:24:55.889 --> 00:24:55.899 align:start position:0% point like all the effects have to come 00:24:55.899 --> 00:24:57.180 align:start position:0% point like all the effects have to come out<00:24:56.080> at<00:24:56.259> the<00:24:56.350> end<00:24:56.440> of<00:24:56.529> the<00:24:56.620> day<00:24:56.769> the<00:24:56.980> program 00:24:57.180 --> 00:24:57.190 align:start position:0% out at the end of the day the program 00:24:57.190 --> 00:25:00.149 align:start position:0% out at the end of the day the program has<00:24:57.519> a<00:24:57.549> title<00:24:58.029> which<00:24:58.570> is<00:24:58.600> IO<00:24:58.960> of<00:24:59.259> unit<00:24:59.590> every 00:25:00.149 --> 00:25:00.159 align:start position:0% has a title which is IO of unit every 00:25:00.159 --> 00:25:01.680 align:start position:0% has a title which is IO of unit every program<00:25:00.519> has<00:25:00.549> this<00:25:00.820> type<00:25:01.029> in<00:25:01.210> history<00:25:01.570> of 00:25:01.680 --> 00:25:01.690 align:start position:0% program has this type in history of 00:25:01.690 --> 00:25:04.590 align:start position:0% program has this type in history of mankind<00:25:02.139> and<00:25:02.919> at<00:25:03.700> the<00:25:03.879> end<00:25:04.000> of<00:25:04.059> the<00:25:04.149> day<00:25:04.299> all 00:25:04.590 --> 00:25:04.600 align:start position:0% mankind and at the end of the day all 00:25:04.600 --> 00:25:06.299 align:start position:0% mankind and at the end of the day all your<00:25:04.870> texts<00:25:05.200> have<00:25:05.320> to<00:25:05.470> resolve<00:25:05.710> to<00:25:05.980> something 00:25:06.299 --> 00:25:06.309 align:start position:0% your texts have to resolve to something 00:25:06.309 --> 00:25:08.070 align:start position:0% your texts have to resolve to something some<00:25:06.519> basic<00:25:06.970> thing<00:25:07.149> that<00:25:07.299> the<00:25:07.389> program<00:25:07.870> can 00:25:08.070 --> 00:25:08.080 align:start position:0% some basic thing that the program can 00:25:08.080 --> 00:25:10.680 align:start position:0% some basic thing that the program can project<00:25:08.500> and<00:25:08.799> as<00:25:09.370> you<00:25:09.669> talk<00:25:10.120> about<00:25:10.179> involves 00:25:10.680 --> 00:25:10.690 align:start position:0% project and as you talk about involves 00:25:10.690 --> 00:25:12.659 align:start position:0% project and as you talk about involves special<00:25:10.899> programs<00:25:11.379> like<00:25:11.620> coming<00:25:12.399> down<00:25:12.549> the 00:25:12.659 --> 00:25:12.669 align:start position:0% special programs like coming down the 00:25:12.669 --> 00:25:13.889 align:start position:0% special programs like coming down the way<00:25:12.759> you're<00:25:13.000> basically<00:25:13.389> constantly 00:25:13.889 --> 00:25:13.899 align:start position:0% way you're basically constantly 00:25:13.899 --> 00:25:20.149 align:start position:0% way you're basically constantly resolving<00:25:14.289> effects<00:25:15.269> at<00:25:16.269> the<00:25:16.299> end<00:25:16.509> of<00:25:16.600> the<00:25:16.690> day 00:25:20.149 --> 00:25:20.159 align:start position:0% 00:25:20.159 --> 00:25:22.289 align:start position:0% all<00:25:21.159> of<00:25:21.190> these<00:25:21.399> effects<00:25:21.700> systems<00:25:22.059> like 00:25:22.289 --> 00:25:22.299 align:start position:0% all of these effects systems like 00:25:22.299 --> 00:25:24.210 align:start position:0% all of these effects systems like weather<00:25:22.509> may<00:25:22.750> like<00:25:22.929> the<00:25:23.110> error<00:25:23.889> in<00:25:24.190> that 00:25:24.210 --> 00:25:24.220 align:start position:0% weather may like the error in that 00:25:24.220 --> 00:25:25.710 align:start position:0% weather may like the error in that system 00:25:25.710 --> 00:25:25.720 align:start position:0% system 00:25:25.720 --> 00:25:27.390 align:start position:0% system they<00:25:26.140> all<00:25:26.320> have<00:25:26.530> to<00:25:26.560> present<00:25:26.920> all<00:25:26.980> agenda 00:25:27.390 --> 00:25:27.400 align:start position:0% they all have to present all agenda 00:25:27.400 --> 00:25:39.030 align:start position:0% they all have to present all agenda today<00:25:27.750> and<00:25:28.750> this<00:25:28.810> is<00:25:28.990> part<00:25:29.260> of<00:25:29.290> life<00:25:32.640> so<00:25:37.560> how<00:25:38.560> so 00:25:39.030 --> 00:25:39.040 align:start position:0% today and this is part of life so how so 00:25:39.040 --> 00:25:41.010 align:start position:0% today and this is part of life so how so basically<00:25:39.400> like<00:25:39.640> you<00:25:40.300> know<00:25:40.390> as<00:25:40.510> a<00:25:40.540> specific 00:25:41.010 --> 00:25:41.020 align:start position:0% basically like you know as a specific 00:25:41.020 --> 00:25:46.680 align:start position:0% basically like you know as a specific it's<00:25:41.410> a<00:25:41.500> specific<00:25:41.710> example<00:25:45.270> specific<00:25:46.270> example 00:25:46.680 --> 00:25:46.690 align:start position:0% it's a specific example specific example 00:25:46.690 --> 00:25:50.790 align:start position:0% it's a specific example specific example look<00:25:46.810> like<00:25:48.960> that<00:25:49.960> place<00:25:50.200> where<00:25:50.440> this<00:25:50.500> vivid 00:25:50.790 --> 00:25:50.800 align:start position:0% look like that place where this vivid 00:25:50.800 --> 00:25:52.230 align:start position:0% look like that place where this vivid interesting<00:25:51.220> it's<00:25:51.370> like<00:25:51.430> okay<00:25:51.850> on<00:25:52.030> like 00:25:52.230 --> 00:25:52.240 align:start position:0% interesting it's like okay on like 00:25:52.240 --> 00:25:54.540 align:start position:0% interesting it's like okay on like addresses<00:25:52.900> is<00:25:53.110> it<00:25:53.260> practice<00:25:53.710> and<00:25:53.950> EVM<00:25:54.280> type 00:25:54.540 --> 00:25:54.550 align:start position:0% addresses is it practice and EVM type 00:25:54.550 --> 00:25:56.520 align:start position:0% addresses is it practice and EVM type you<00:25:55.060> can<00:25:55.210> decode<00:25:55.570> this<00:25:55.840> if<00:25:56.020> you<00:25:56.140> have<00:25:56.320> it<00:25:56.410> from 00:25:56.520 --> 00:25:56.530 align:start position:0% you can decode this if you have it from 00:25:56.530 --> 00:25:59.550 align:start position:0% you can decode this if you have it from us<00:25:56.620> you<00:25:57.040> have<00:25:57.720> by<00:25:58.720> answering<00:25:58.990> of<00:25:59.170> a<00:25:59.260> certain 00:25:59.550 --> 00:25:59.560 align:start position:0% us you have by answering of a certain 00:25:59.560 --> 00:26:00.030 align:start position:0% us you have by answering of a certain length 00:26:00.030 --> 00:26:00.040 align:start position:0% length 00:26:00.040 --> 00:26:01.770 align:start position:0% length you<00:26:00.190> can't<00:26:00.430> decode<00:26:00.760> it<00:26:00.940> so<00:26:01.090> basically<00:26:01.240> like<00:26:01.690> to 00:26:01.770 --> 00:26:01.780 align:start position:0% you can't decode it so basically like to 00:26:01.780 --> 00:26:03.930 align:start position:0% you can't decode it so basically like to throw<00:26:01.990> away<00:26:02.110> the<00:26:02.380> first<00:26:02.590> 12<00:26:03.490> bytes<00:26:03.700> or 00:26:03.930 --> 00:26:03.940 align:start position:0% throw away the first 12 bytes or 00:26:03.940 --> 00:26:05.820 align:start position:0% throw away the first 12 bytes or whatever<00:26:04.180> it<00:26:04.330> take<00:26:04.480> or<00:26:04.840> take<00:26:05.170> the<00:26:05.290> last<00:26:05.500> 20 00:26:05.820 --> 00:26:05.830 align:start position:0% whatever it take or take the last 20 00:26:05.830 --> 00:26:09.330 align:start position:0% whatever it take or take the last 20 bytes<00:26:06.010> and<00:26:06.730> try<00:26:07.540> to<00:26:07.620> basically<00:26:08.620> just<00:26:08.860> figure 00:26:09.330 --> 00:26:09.340 align:start position:0% bytes and try to basically just figure 00:26:09.340 --> 00:26:11.150 align:start position:0% bytes and try to basically just figure out<00:26:09.370> if<00:26:09.610> you<00:26:09.970> haven't<00:26:10.270> already 00:26:11.150 --> 00:26:11.160 align:start position:0% out if you haven't already 00:26:11.160 --> 00:26:13.230 align:start position:0% out if you haven't already sorry<00:26:12.160> if<00:26:12.280> you<00:26:12.310> can<00:26:12.550> make<00:26:12.700> an<00:26:12.820> address<00:26:13.120> from 00:26:13.230 --> 00:26:13.240 align:start position:0% sorry if you can make an address from 00:26:13.240 --> 00:26:14.460 align:start position:0% sorry if you can make an address from you<00:26:13.390> that's<00:26:13.630> okay<00:26:13.900> bunny 00:26:14.460 --> 00:26:14.470 align:start position:0% you that's okay bunny 00:26:14.470 --> 00:26:16.440 align:start position:0% you that's okay bunny and<00:26:14.830> then<00:26:15.070> it<00:26:15.190> should<00:26:15.310> be<00:26:15.430> good<00:26:15.580> otherwise<00:26:16.030> it 00:26:16.440 --> 00:26:16.450 align:start position:0% and then it should be good otherwise it 00:26:16.450 --> 00:26:18.870 align:start position:0% and then it should be good otherwise it should<00:26:16.600> fail<00:26:16.840> I<00:26:17.280> think<00:26:18.280> this<00:26:18.370> last<00:26:18.520> one<00:26:18.790> is 00:26:18.870 --> 00:26:18.880 align:start position:0% should fail I think this last one is 00:26:18.880 --> 00:26:21.090 align:start position:0% should fail I think this last one is David<00:26:19.270> and<00:26:19.750> I<00:26:19.960> did<00:26:20.110> these<00:26:20.200> finance<00:26:20.590> this<00:26:20.860> might 00:26:21.090 --> 00:26:21.100 align:start position:0% David and I did these finance this might 00:26:21.100 --> 00:26:22.230 align:start position:0% David and I did these finance this might not<00:26:21.220> even<00:26:21.310> there's<00:26:21.670> no<00:26:21.760> way<00:26:21.880> that<00:26:22.000> this<00:26:22.090> can 00:26:22.230 --> 00:26:22.240 align:start position:0% not even there's no way that this can 00:26:22.240 --> 00:26:23.700 align:start position:0% not even there's no way that this can feel<00:26:22.360> isolated<00:26:22.510> this<00:26:23.080> is<00:26:23.200> basically<00:26:23.470> saying 00:26:23.700 --> 00:26:23.710 align:start position:0% feel isolated this is basically saying 00:26:23.710 --> 00:26:25.710 align:start position:0% feel isolated this is basically saying you<00:26:23.860> like<00:26:24.010> take<00:26:24.460> the<00:26:24.550> first<00:26:24.760> to<00:26:24.940> take<00:26:25.630> the 00:26:25.710 --> 00:26:25.720 align:start position:0% you like take the first to take the 00:26:25.720 --> 00:26:29.130 align:start position:0% you like take the first to take the first<00:26:25.930> 12<00:26:26.970> remaining<00:26:27.970> 20<00:26:28.300> bytes<00:26:28.480> irrelevant 00:26:29.130 --> 00:26:29.140 align:start position:0% first 12 remaining 20 bytes irrelevant 00:26:29.140 --> 00:26:30.540 align:start position:0% first 12 remaining 20 bytes irrelevant address<00:26:29.410> the<00:26:29.680> only<00:26:29.800> way<00:26:29.890> this<00:26:30.010> can<00:26:30.160> fail<00:26:30.370> is 00:26:30.540 --> 00:26:30.550 align:start position:0% address the only way this can fail is 00:26:30.550 --> 00:26:32.690 align:start position:0% address the only way this can fail is that<00:26:30.670> this<00:26:30.760> tank<00:26:31.060> fails<00:26:31.360> or<00:26:31.660> this<00:26:31.750> ting<00:26:31.990> fails 00:26:32.690 --> 00:26:32.700 align:start position:0% that this tank fails or this ting fails 00:26:32.700 --> 00:26:34.680 align:start position:0% that this tank fails or this ting fails and<00:26:33.700> what<00:26:33.820> that<00:26:33.940> means<00:26:34.060> is<00:26:34.150> the<00:26:34.240> thing<00:26:34.390> you<00:26:34.480> had 00:26:34.680 --> 00:26:34.690 align:start position:0% and what that means is the thing you had 00:26:34.690 --> 00:26:36.300 align:start position:0% and what that means is the thing you had to<00:26:34.990> show<00:26:35.140> it<00:26:35.260> wasn't<00:26:35.530> long<00:26:35.650> enough<00:26:35.830> that's<00:26:36.190> all 00:26:36.300 --> 00:26:36.310 align:start position:0% to show it wasn't long enough that's all 00:26:36.310 --> 00:26:38.220 align:start position:0% to show it wasn't long enough that's all this<00:26:36.400> is<00:26:36.460> say<00:26:36.730> okay<00:26:37.180> cool<00:26:37.390> so<00:26:37.420> you<00:26:37.630> can<00:26:37.840> decode 00:26:38.220 --> 00:26:38.230 align:start position:0% this is say okay cool so you can decode 00:26:38.230 --> 00:26:39.870 align:start position:0% this is say okay cool so you can decode after<00:26:38.590> since<00:26:38.830> four<00:26:39.010> types<00:26:39.280> whatever<00:26:39.610> that's 00:26:39.870 --> 00:26:39.880 align:start position:0% after since four types whatever that's 00:26:39.880 --> 00:26:42.660 align:start position:0% after since four types whatever that's pretty<00:26:40.090> cool<00:26:40.240> but<00:26:40.960> like<00:26:41.170> what<00:26:41.950> if<00:26:41.980> you<00:26:42.100> you 00:26:42.660 --> 00:26:42.670 align:start position:0% pretty cool but like what if you you 00:26:42.670 --> 00:26:43.190 align:start position:0% pretty cool but like what if you you know 00:26:43.190 --> 00:26:43.200 align:start position:0% know 00:26:43.200 --> 00:26:46.229 align:start position:0% know more<00:26:44.200> complicated<00:26:44.769> for<00:26:44.919> example<00:26:45.279> like<00:26:45.460> in<00:26:46.059> the 00:26:46.229 --> 00:26:46.239 align:start position:0% more complicated for example like in the 00:26:46.239 --> 00:26:48.329 align:start position:0% more complicated for example like in the EVM<00:26:46.539> you<00:26:46.899> also<00:26:47.080> have<00:26:47.440> this<00:26:47.739> notion<00:26:47.950> of<00:26:48.159> like 00:26:48.329 --> 00:26:48.339 align:start position:0% EVM you also have this notion of like 00:26:48.339 --> 00:26:50.579 align:start position:0% EVM you also have this notion of like size<00:26:48.609> to<00:26:48.999> raise<00:26:49.179> so<00:26:49.570> later<00:26:49.809> you<00:26:50.229> have<00:26:50.529> a 00:26:50.579 --> 00:26:50.589 align:start position:0% size to raise so later you have a 00:26:50.589 --> 00:26:52.079 align:start position:0% size to raise so later you have a precise<00:26:51.009> array<00:26:51.369> let's<00:26:51.609> say<00:26:51.759> it's<00:26:51.909> like<00:26:52.059> a 00:26:52.079 --> 00:26:52.089 align:start position:0% precise array let's say it's like a 00:26:52.089 --> 00:26:55.639 align:start position:0% precise array let's say it's like a tuple<00:26:52.599> of<00:26:52.629> addresses<00:26:53.259> right<00:26:53.679> and<00:26:54.609> then<00:26:54.729> type 00:26:55.639 --> 00:26:55.649 align:start position:0% tuple of addresses right and then type 00:26:55.649 --> 00:26:58.139 align:start position:0% tuple of addresses right and then type something<00:26:56.649> like<00:26:56.799> for<00:26:57.339> example<00:26:57.399> everybody's 00:26:58.139 --> 00:26:58.149 align:start position:0% something like for example everybody's 00:26:58.149 --> 00:27:00.570 align:start position:0% something like for example everybody's favorite<00:26:58.509> event<00:26:58.779> is<00:26:59.049> probably<00:26:59.889> the<00:27:00.070> transfer 00:27:00.570 --> 00:27:00.580 align:start position:0% favorite event is probably the transfer 00:27:00.580 --> 00:27:03.329 align:start position:0% favorite event is probably the transfer and<00:27:00.869> results<00:27:01.869> in<00:27:01.989> your<00:27:02.139> address<00:27:02.619> getting<00:27:03.099> more 00:27:03.329 --> 00:27:03.339 align:start position:0% and results in your address getting more 00:27:03.339 --> 00:27:06.719 align:start position:0% and results in your address getting more money<00:27:03.700> whatever<00:27:04.599> and<00:27:05.219> that's<00:27:06.219> effectively 00:27:06.719 --> 00:27:06.729 align:start position:0% money whatever and that's effectively 00:27:06.729 --> 00:27:08.279 align:start position:0% money whatever and that's effectively like<00:27:06.969> that<00:27:07.119> free<00:27:07.330> to<00:27:07.450> a<00:27:07.479> little<00:27:07.749> rate<00:27:07.899> of<00:27:08.080> like 00:27:08.279 --> 00:27:08.289 align:start position:0% like that free to a little rate of like 00:27:08.289 --> 00:27:10.109 align:start position:0% like that free to a little rate of like well<00:27:08.619> there's<00:27:08.919> two<00:27:09.099> mattresses<00:27:09.309> in<00:27:09.759> there<00:27:09.940> and 00:27:10.109 --> 00:27:10.119 align:start position:0% well there's two mattresses in there and 00:27:10.119 --> 00:27:14.339 align:start position:0% well there's two mattresses in there and then<00:27:10.210> there's<00:27:10.389> like<00:27:12.479> you<00:27:13.479> went<00:27:13.690> in<00:27:14.169> there 00:27:14.339 --> 00:27:14.349 align:start position:0% then there's like you went in there 00:27:14.349 --> 00:27:16.499 align:start position:0% then there's like you went in there sorry<00:27:14.619> but<00:27:15.489> in<00:27:15.700> this<00:27:15.789> sense<00:27:15.999> like<00:27:16.239> there's 00:27:16.499 --> 00:27:16.509 align:start position:0% sorry but in this sense like there's 00:27:16.509 --> 00:27:18.419 align:start position:0% sorry but in this sense like there's like<00:27:16.690> the<00:27:16.839> notion<00:27:17.349> of<00:27:17.409> like<00:27:17.619> it<00:27:18.009> doesn't<00:27:18.249> make 00:27:18.419 --> 00:27:18.429 align:start position:0% like the notion of like it doesn't make 00:27:18.429 --> 00:27:20.249 align:start position:0% like the notion of like it doesn't make sense<00:27:18.489> to<00:27:18.669> speak<00:27:18.909> about<00:27:18.999> like<00:27:19.239> perfecter<00:27:19.719> or 00:27:20.249 --> 00:27:20.259 align:start position:0% sense to speak about like perfecter or 00:27:20.259 --> 00:27:22.469 align:start position:0% sense to speak about like perfecter or like<00:27:20.409> effector<00:27:20.859> of<00:27:20.969> addresses<00:27:21.969> which<00:27:22.149> is<00:27:22.299> like 00:27:22.469 --> 00:27:22.479 align:start position:0% like effector of addresses which is like 00:27:22.479 --> 00:27:24.599 align:start position:0% like effector of addresses which is like a<00:27:22.509> list<00:27:23.109> of<00:27:23.229> addresses<00:27:23.440> under<00:27:23.889> predefined<00:27:24.429> Li 00:27:24.599 --> 00:27:24.609 align:start position:0% a list of addresses under predefined Li 00:27:24.609 --> 00:27:27.930 align:start position:0% a list of addresses under predefined Li and<00:27:25.419> like<00:27:25.859> okay<00:27:26.859> so<00:27:26.919> if<00:27:27.489> you<00:27:27.580> can<00:27:27.729> somehow 00:27:27.930 --> 00:27:27.940 align:start position:0% and like okay so if you can somehow 00:27:27.940 --> 00:27:30.749 align:start position:0% and like okay so if you can somehow communicate<00:27:28.539> the<00:27:28.659> predefined<00:27:29.200> linked<00:27:29.559> to<00:27:29.830> the 00:27:30.749 --> 00:27:30.759 align:start position:0% communicate the predefined linked to the 00:27:30.759 --> 00:27:34.739 align:start position:0% communicate the predefined linked to the program<00:27:31.119> that<00:27:31.239> you're<00:27:31.330> writing<00:27:31.539> it<00:27:33.570> you<00:27:34.570> can 00:27:34.739 --> 00:27:34.749 align:start position:0% program that you're writing it you can 00:27:34.749 --> 00:27:36.329 align:start position:0% program that you're writing it you can basically<00:27:35.080> reason<00:27:35.649> about<00:27:35.799> it<00:27:35.859> and<00:27:36.070> say<00:27:36.159> like 00:27:36.329 --> 00:27:36.339 align:start position:0% basically reason about it and say like 00:27:36.339 --> 00:27:38.129 align:start position:0% basically reason about it and say like okay<00:27:36.609> like<00:27:36.759> the<00:27:37.330> only<00:27:37.479> way<00:27:37.659> that<00:27:37.779> this<00:27:37.899> thing 00:27:38.129 --> 00:27:38.139 align:start position:0% okay like the only way that this thing 00:27:38.139 --> 00:27:40.549 align:start position:0% okay like the only way that this thing can<00:27:38.320> fail<00:27:38.589> in<00:27:39.009> parsing<00:27:39.460> or<00:27:39.549> whatever<00:27:39.759> is<00:27:39.969> it 00:27:40.549 --> 00:27:40.559 align:start position:0% can fail in parsing or whatever is it 00:27:40.559 --> 00:27:42.329 align:start position:0% can fail in parsing or whatever is it sorry<00:27:41.559> I<00:27:41.619> understand<00:27:41.919> yeah 00:27:42.329 --> 00:27:42.339 align:start position:0% sorry I understand yeah 00:27:42.339 --> 00:27:44.820 align:start position:0% sorry I understand yeah so<00:27:42.489> if<00:27:43.269> you're<00:27:43.479> looking<00:27:43.599> at<00:27:43.779> like<00:27:43.899> a<00:27:43.929> vector<00:27:44.259> of 00:27:44.820 --> 00:27:44.830 align:start position:0% so if you're looking at like a vector of 00:27:44.830 --> 00:27:47.070 align:start position:0% so if you're looking at like a vector of a<00:27:45.190> predefined<00:27:45.849> length<00:27:46.089> bunch<00:27:46.570> of<00:27:46.659> this<00:27:46.839> in 00:27:47.070 --> 00:27:47.080 align:start position:0% a predefined length bunch of this in 00:27:47.080 --> 00:27:49.889 align:start position:0% a predefined length bunch of this in here<00:27:47.409> of<00:27:47.619> certain<00:27:48.070> type<00:27:48.249> a<00:27:48.460> you<00:27:49.330> can't<00:27:49.539> decode 00:27:49.889 --> 00:27:49.899 align:start position:0% here of certain type a you can't decode 00:27:49.899 --> 00:27:51.779 align:start position:0% here of certain type a you can't decode into<00:27:50.169> this<00:27:50.289> thing<00:27:50.529> basically<00:27:51.369> what<00:27:51.639> you're 00:27:51.779 --> 00:27:51.789 align:start position:0% into this thing basically what you're 00:27:51.789 --> 00:27:54.019 align:start position:0% into this thing basically what you're telling<00:27:51.909> which<00:27:52.389> are<00:27:52.539> less<00:27:52.809> you<00:27:52.989> can<00:27:53.169> success 00:27:54.019 --> 00:27:54.029 align:start position:0% telling which are less you can success 00:27:54.029 --> 00:27:55.969 align:start position:0% telling which are less you can success you're<00:27:54.749> telling<00:27:54.989> the<00:27:55.080> program<00:27:55.349> it's<00:27:55.679> like<00:27:55.830> no 00:27:55.969 --> 00:27:55.979 align:start position:0% you're telling the program it's like no 00:27:55.979 --> 00:27:57.499 align:start position:0% you're telling the program it's like no matter<00:27:56.129> what<00:27:56.489> at<00:27:56.729> this<00:27:56.849> point<00:27:57.119> I<00:27:57.299> know<00:27:57.359> that 00:27:57.499 --> 00:27:57.509 align:start position:0% matter what at this point I know that 00:27:57.509 --> 00:28:01.070 align:start position:0% matter what at this point I know that this<00:27:57.989> thing<00:27:58.859> here<00:27:59.340> is<00:27:59.549> a<00:27:59.609> it's<00:28:00.509> a<00:28:00.629> vector<00:28:00.809> of<00:28:01.019> a 00:28:01.070 --> 00:28:01.080 align:start position:0% this thing here is a it's a vector of a 00:28:01.080 --> 00:28:02.570 align:start position:0% this thing here is a it's a vector of a certain<00:28:01.379> way<00:28:01.529> you<00:28:02.099> don't<00:28:02.249> ever<00:28:02.369> have<00:28:02.429> to<00:28:02.489> worry 00:28:02.570 --> 00:28:02.580 align:start position:0% certain way you don't ever have to worry 00:28:02.580 --> 00:28:04.039 align:start position:0% certain way you don't ever have to worry again<00:28:02.879> about<00:28:03.059> like<00:28:03.419> checking<00:28:03.719> the<00:28:03.899> good 00:28:04.039 --> 00:28:04.049 align:start position:0% again about like checking the good 00:28:04.049 --> 00:28:06.200 align:start position:0% again about like checking the good science<00:28:04.499> this<00:28:04.679> thing<00:28:04.950> like<00:28:05.279> you<00:28:05.759> pass<00:28:05.940> it<00:28:06.119> off 00:28:06.200 --> 00:28:06.210 align:start position:0% science this thing like you pass it off 00:28:06.210 --> 00:28:07.820 align:start position:0% science this thing like you pass it off to<00:28:06.239> a<00:28:06.389> different<00:28:06.690> function<00:28:06.899> that<00:28:07.649> function 00:28:07.820 --> 00:28:07.830 align:start position:0% to a different function that function 00:28:07.830 --> 00:28:10.039 align:start position:0% to a different function that function also<00:28:08.219> will<00:28:08.549> know<00:28:08.729> the<00:28:08.969> length<00:28:09.210> of<00:28:09.419> this<00:28:09.570> vector 00:28:10.039 --> 00:28:10.049 align:start position:0% also will know the length of this vector 00:28:10.049 --> 00:28:13.190 align:start position:0% also will know the length of this vector because<00:28:10.769> it's<00:28:11.279> encoded<00:28:11.759> in<00:28:11.879> the<00:28:11.969> types<00:28:12.179> of<00:28:12.330> so 00:28:13.190 --> 00:28:13.200 align:start position:0% because it's encoded in the types of so 00:28:13.200 --> 00:28:15.529 align:start position:0% because it's encoded in the types of so you<00:28:14.009> can<00:28:14.159> build<00:28:14.369> that<00:28:14.489> into<00:28:14.549> like<00:28:14.969> the<00:28:15.119> Codex 00:28:15.529 --> 00:28:15.539 align:start position:0% you can build that into like the Codex 00:28:15.539 --> 00:28:17.149 align:start position:0% you can build that into like the Codex or<00:28:15.719> whatever<00:28:16.019> basically<00:28:16.440> what<00:28:16.679> it<00:28:16.769> means<00:28:16.950> then 00:28:17.149 --> 00:28:17.159 align:start position:0% or whatever basically what it means then 00:28:17.159 --> 00:28:21.139 align:start position:0% or whatever basically what it means then after<00:28:17.549> you're<00:28:17.700> able<00:28:17.909> to<00:28:18.019> decode<00:28:19.019> a<00:28:19.279> PM<00:28:20.279> you 00:28:21.139 --> 00:28:21.149 align:start position:0% after you're able to decode a PM you 00:28:21.149 --> 00:28:22.759 align:start position:0% after you're able to decode a PM you have<00:28:21.330> enough<00:28:21.749> information<00:28:21.899> about<00:28:22.590> this 00:28:22.759 --> 00:28:22.769 align:start position:0% have enough information about this 00:28:22.769 --> 00:28:24.560 align:start position:0% have enough information about this effect<00:28:23.369> in<00:28:23.549> this<00:28:23.639> particular<00:28:23.940> case<00:28:24.299> inspector 00:28:24.560 --> 00:28:24.570 align:start position:0% effect in this particular case inspector 00:28:24.570 --> 00:28:28.159 align:start position:0% effect in this particular case inspector so<00:28:24.989> that<00:28:25.109> you'll<00:28:25.229> never<00:28:25.440> get<00:28:25.649> an<00:28:25.769> array<00:28:27.169> access 00:28:28.159 --> 00:28:28.169 align:start position:0% so that you'll never get an array access 00:28:28.169 --> 00:28:30.259 align:start position:0% so that you'll never get an array access like<00:28:28.349> it's<00:28:28.529> a<00:28:28.589> third<00:28:29.009> argument<00:28:29.309> because<00:28:30.119> you 00:28:30.259 --> 00:28:30.269 align:start position:0% like it's a third argument because you 00:28:30.269 --> 00:28:31.759 align:start position:0% like it's a third argument because you know<00:28:30.419> that<00:28:30.719> in<00:28:31.080> order<00:28:31.259> to<00:28:31.320> you<00:28:31.409> and<00:28:31.559> try<00:28:31.710> to 00:28:31.759 --> 00:28:31.769 align:start position:0% know that in order to you and try to 00:28:31.769 --> 00:28:34.519 align:start position:0% know that in order to you and try to access<00:28:31.919> the<00:28:32.219> third<00:28:32.399> argument<00:28:33.259> this<00:28:34.259> vector 00:28:34.519 --> 00:28:34.529 align:start position:0% access the third argument this vector 00:28:34.529 --> 00:28:36.379 align:start position:0% access the third argument this vector has<00:28:34.649> a<00:28:34.679> size<00:28:34.950> emphasized<00:28:35.519> occasionally<00:28:36.089> like 00:28:36.379 --> 00:28:36.389 align:start position:0% has a size emphasized occasionally like 00:28:36.389 --> 00:28:37.820 align:start position:0% has a size emphasized occasionally like you<00:28:36.570> will<00:28:36.719> get<00:28:36.839> and<00:28:37.109> I<00:28:37.320> will<00:28:37.440> show<00:28:37.589> you<00:28:37.619> an 00:28:37.820 --> 00:28:37.830 align:start position:0% you will get and I will show you an 00:28:37.830 --> 00:28:39.200 align:start position:0% you will get and I will show you an example<00:28:37.859> of<00:28:38.249> this<00:28:38.339> you<00:28:38.519> will<00:28:38.609> get<00:28:38.729> a<00:28:38.789> compile 00:28:39.200 --> 00:28:39.210 align:start position:0% example of this you will get a compile 00:28:39.210 --> 00:28:40.629 align:start position:0% example of this you will get a compile time<00:28:39.239> error<00:28:39.719> if<00:28:39.989> you<00:28:40.019> try<00:28:40.109> to<00:28:40.349> access 00:28:40.629 --> 00:28:40.639 align:start position:0% time error if you try to access 00:28:40.639 --> 00:28:43.190 align:start position:0% time error if you try to access something<00:28:41.639> which<00:28:41.759> is<00:28:41.879> not<00:28:42.029> there<00:28:42.269> so<00:28:42.570> rather 00:28:43.190 --> 00:28:43.200 align:start position:0% something which is not there so rather 00:28:43.200 --> 00:28:44.479 align:start position:0% something which is not there so rather than<00:28:43.409> like<00:28:43.649> trying<00:28:43.979> to<00:28:44.009> check<00:28:44.219> for<00:28:44.429> this 00:28:44.479 --> 00:28:44.489 align:start position:0% than like trying to check for this 00:28:44.489 --> 00:28:46.459 align:start position:0% than like trying to check for this everywhere<00:28:44.879> try<00:28:45.659> and<00:28:45.779> throw<00:28:45.929> some<00:28:46.080> exception 00:28:46.459 --> 00:28:46.469 align:start position:0% everywhere try and throw some exception 00:28:46.469 --> 00:28:49.219 align:start position:0% everywhere try and throw some exception in<00:28:46.589> case<00:28:46.710> it<00:28:46.889> didn't<00:28:47.129> happen<00:28:47.429> what<00:28:48.419> you<00:28:49.019> what's 00:28:49.219 --> 00:28:49.229 align:start position:0% in case it didn't happen what you what's 00:28:49.229 --> 00:28:50.959 align:start position:0% in case it didn't happen what you what's ended<00:28:49.469> up<00:28:49.589> happening<00:28:49.769> is<00:28:50.070> that<00:28:50.249> like<00:28:50.399> every 00:28:50.959 --> 00:28:50.969 align:start position:0% ended up happening is that like every 00:28:50.969 --> 00:28:52.519 align:start position:0% ended up happening is that like every part<00:28:51.179> of<00:28:51.210> your<00:28:51.299> program<00:28:51.659> will<00:28:51.779> now<00:28:51.929> be<00:28:52.109> a<00:28:52.139> not 00:28:52.519 --> 00:28:52.529 align:start position:0% part of your program will now be a not 00:28:52.529 --> 00:28:54.079 align:start position:0% part of your program will now be a not in<00:28:52.769> sync<00:28:53.070> and<00:28:53.249> we'll<00:28:53.399> know<00:28:53.549> that<00:28:53.580> this<00:28:53.879> vector 00:28:54.079 --> 00:28:54.089 align:start position:0% in sync and we'll know that this vector 00:28:54.089 --> 00:28:57.440 align:start position:0% in sync and we'll know that this vector has<00:28:55.339> it<00:28:56.339> seems<00:28:56.549> like<00:28:56.700> a<00:28:56.759> stupid<00:28:56.969> thing<00:28:57.239> but 00:28:57.440 --> 00:28:57.450 align:start position:0% has it seems like a stupid thing but 00:28:57.450 --> 00:28:59.209 align:start position:0% has it seems like a stupid thing but then<00:28:57.599> you<00:28:57.899> know<00:28:58.139> it<00:28:58.440> is<00:28:58.529> a<00:28:58.559> stupid<00:28:58.769> thing<00:28:58.919> but 00:28:59.209 --> 00:28:59.219 align:start position:0% then you know it is a stupid thing but 00:28:59.219 --> 00:29:00.320 align:start position:0% then you know it is a stupid thing but they<00:28:59.339> want<00:28:59.549> us<00:28:59.580> to<00:28:59.639> realize<00:28:59.909> how<00:28:59.999> to<00:29:00.029> do<00:29:00.210> this 00:29:00.320 --> 00:29:00.330 align:start position:0% they want us to realize how to do this 00:29:00.330 --> 00:29:02.610 align:start position:0% they want us to realize how to do this human 00:29:02.610 --> 00:29:02.620 align:start position:0% human 00:29:02.620 --> 00:29:04.930 align:start position:0% human this<00:29:03.620> is<00:29:03.740> a<00:29:03.770> particular<00:29:04.250> example<00:29:04.370> of<00:29:04.700> what<00:29:04.850> I'm 00:29:04.930 --> 00:29:04.940 align:start position:0% this is a particular example of what I'm 00:29:04.940 --> 00:29:09.130 align:start position:0% this is a particular example of what I'm talking<00:29:04.970> about 00:29:09.130 --> 00:29:09.140 align:start position:0% 00:29:09.140 --> 00:29:11.500 align:start position:0% you<00:29:09.679> know<00:29:09.799> ecstatically<00:29:10.460> size<00:29:10.700> factors<00:29:11.090> if 00:29:11.500 --> 00:29:11.510 align:start position:0% you know ecstatically size factors if 00:29:11.510 --> 00:29:13.360 align:start position:0% you know ecstatically size factors if you<00:29:11.630> did<00:29:11.990> you<00:29:12.110> do<00:29:12.289> enough<00:29:12.530> like<00:29:12.770> the<00:29:12.980> level 00:29:13.360 --> 00:29:13.370 align:start position:0% you did you do enough like the level 00:29:13.370 --> 00:29:15.730 align:start position:0% you did you do enough like the level stuff<00:29:13.970> with<00:29:14.179> solidity<00:29:14.600> you<00:29:14.900> know<00:29:15.110> how<00:29:15.440> these 00:29:15.730 --> 00:29:15.740 align:start position:0% stuff with solidity you know how these 00:29:15.740 --> 00:29:17.230 align:start position:0% stuff with solidity you know how these things<00:29:15.799> are<00:29:16.130> encoded<00:29:16.580> or<00:29:16.669> ever<00:29:16.789> the<00:29:17.000> first 00:29:17.230 --> 00:29:17.240 align:start position:0% things are encoded or ever the first 00:29:17.240 --> 00:29:18.940 align:start position:0% things are encoded or ever the first word<00:29:17.600> it's<00:29:17.870> like<00:29:17.929> the<00:29:18.169> length<00:29:18.380> of<00:29:18.650> the<00:29:18.770> thing 00:29:18.940 --> 00:29:18.950 align:start position:0% word it's like the length of the thing 00:29:18.950 --> 00:29:20.860 align:start position:0% word it's like the length of the thing that<00:29:19.190> you're<00:29:19.309> looking<00:29:19.340> at<00:29:19.760> and<00:29:20.150> this<00:29:20.330> and<00:29:20.660> then 00:29:20.860 --> 00:29:20.870 align:start position:0% that you're looking at and this and then 00:29:20.870 --> 00:29:22.750 align:start position:0% that you're looking at and this and then it's<00:29:20.990> followed<00:29:21.110> by<00:29:21.320> just<00:29:21.890> a<00:29:21.980> concatenation<00:29:22.490> of 00:29:22.750 --> 00:29:22.760 align:start position:0% it's followed by just a concatenation of 00:29:22.760 --> 00:29:25.120 align:start position:0% it's followed by just a concatenation of all<00:29:22.940> the<00:29:23.030> arguments<00:29:23.299> so<00:29:24.020> I<00:29:24.380> can<00:29:24.799> have<00:29:24.980> this 00:29:25.120 --> 00:29:25.130 align:start position:0% all the arguments so I can have this 00:29:25.130 --> 00:29:27.520 align:start position:0% all the arguments so I can have this link<00:29:25.760> this<00:29:25.940> is<00:29:26.120> a<00:29:26.150> you<00:29:26.600> know<00:29:26.720> you<00:29:27.200> can't<00:29:27.410> read 00:29:27.520 --> 00:29:27.530 align:start position:0% link this is a you know you can't read 00:29:27.530 --> 00:29:28.570 align:start position:0% link this is a you know you can't read this<00:29:27.620> in<00:29:27.740> the<00:29:27.799> back<00:29:27.919> probably<00:29:28.160> but<00:29:28.340> this<00:29:28.460> is 00:29:28.570 --> 00:29:28.580 align:start position:0% this in the back probably but this is 00:29:28.580 --> 00:29:30.850 align:start position:0% this in the back probably but this is just<00:29:28.700> the<00:29:28.940> number<00:29:29.299> two<00:29:29.539> followed<00:29:30.350> by<00:29:30.470> two 00:29:30.850 --> 00:29:30.860 align:start position:0% just the number two followed by two 00:29:30.860 --> 00:29:33.250 align:start position:0% just the number two followed by two addresses<00:29:31.220> and<00:29:32.090> you'd<00:29:32.299> like<00:29:32.450> to<00:29:32.570> parse<00:29:33.080> this 00:29:33.250 --> 00:29:33.260 align:start position:0% addresses and you'd like to parse this 00:29:33.260 --> 00:29:35.350 align:start position:0% addresses and you'd like to parse this into<00:29:33.530> a<00:29:33.559> vector<00:29:33.860> of<00:29:34.130> length<00:29:34.159> two<00:29:34.669> this<00:29:35.059> is<00:29:35.210> like 00:29:35.350 --> 00:29:35.360 align:start position:0% into a vector of length two this is like 00:29:35.360 --> 00:29:37.270 align:start position:0% into a vector of length two this is like some<00:29:35.600> type<00:29:35.960> level<00:29:36.169> language<00:29:36.679> that's<00:29:36.890> very 00:29:37.270 --> 00:29:37.280 align:start position:0% some type level language that's very 00:29:37.280 --> 00:29:38.860 align:start position:0% some type level language that's very specific<00:29:37.520> to<00:29:37.850> like<00:29:38.090> the<00:29:38.240> libraries<00:29:38.630> that<00:29:38.750> we 00:29:38.860 --> 00:29:38.870 align:start position:0% specific to like the libraries that we 00:29:38.870 --> 00:29:40.539 align:start position:0% specific to like the libraries that we use<00:29:39.080> but<00:29:39.650> basically<00:29:39.919> what<00:29:40.130> this<00:29:40.250> is<00:29:40.370> going<00:29:40.490> to 00:29:40.539 --> 00:29:40.549 align:start position:0% use but basically what this is going to 00:29:40.549 --> 00:29:43.000 align:start position:0% use but basically what this is going to do<00:29:40.730> is<00:29:40.880> try<00:29:41.090> to<00:29:41.150> determine<00:29:41.539> this<00:29:41.809> X<00:29:42.080> ring<00:29:42.380> into 00:29:43.000 --> 00:29:43.010 align:start position:0% do is try to determine this X ring into 00:29:43.010 --> 00:29:45.190 align:start position:0% do is try to determine this X ring into either<00:29:43.280> a<00:29:43.460> parse<00:29:43.760> error<00:29:44.059> or<00:29:44.539> a<00:29:44.600> vector<00:29:44.960> of 00:29:45.190 --> 00:29:45.200 align:start position:0% either a parse error or a vector of 00:29:45.200 --> 00:29:47.590 align:start position:0% either a parse error or a vector of length<00:29:45.230> two<00:29:45.650> of<00:29:45.890> type<00:29:46.100> of<00:29:46.220> migrants<00:29:46.640> and<00:29:46.760> after 00:29:47.590 --> 00:29:47.600 align:start position:0% length two of type of migrants and after 00:29:47.600 --> 00:29:50.500 align:start position:0% length two of type of migrants and after that<00:29:48.159> and<00:29:49.159> after<00:29:49.309> that<00:29:49.460> forever<00:29:49.880> like<00:29:50.210> you 00:29:50.500 --> 00:29:50.510 align:start position:0% that and after that forever like you 00:29:50.510 --> 00:29:53.590 align:start position:0% that and after that forever like you can't<00:29:51.110> for<00:29:51.530> example<00:29:51.860> if<00:29:51.950> this<00:29:52.039> you<00:29:53.030> can't<00:29:53.299> fail 00:29:53.590 --> 00:29:53.600 align:start position:0% can't for example if this you can't fail 00:29:53.600 --> 00:29:55.240 align:start position:0% can't for example if this you can't fail in<00:29:53.809> this<00:29:53.929> last<00:29:54.230> case<00:29:54.470> when<00:29:54.740> you<00:29:54.830> try<00:29:55.010> to<00:29:55.070> take 00:29:55.240 --> 00:29:55.250 align:start position:0% in this last case when you try to take 00:29:55.250 --> 00:29:57.510 align:start position:0% in this last case when you try to take that<00:29:55.309> and<00:29:56.179> you<00:29:56.240> try<00:29:56.390> to<00:29:56.450> take<00:29:56.630> the<00:29:56.780> first 00:29:57.510 --> 00:29:57.520 align:start position:0% that and you try to take the first 00:29:57.520 --> 00:29:59.500 align:start position:0% that and you try to take the first coordinate<00:29:58.520> of<00:29:58.580> this<00:29:58.730> array<00:29:59.030> and<00:29:59.330> you<00:29:59.360> never 00:29:59.500 --> 00:29:59.510 align:start position:0% coordinate of this array and you never 00:29:59.510 --> 00:30:00.530 align:start position:0% coordinate of this array and you never fear 00:30:00.530 --> 00:30:00.540 align:start position:0% fear 00:30:00.540 --> 00:30:03.170 align:start position:0% fear yeah<00:30:01.170> so<00:30:01.620> maybe<00:30:01.800> the<00:30:02.070> intuition<00:30:02.880> here<00:30:02.910> is<00:30:03.090> a 00:30:03.170 --> 00:30:03.180 align:start position:0% yeah so maybe the intuition here is a 00:30:03.180 --> 00:30:05.000 align:start position:0% yeah so maybe the intuition here is a little<00:30:03.360> bit<00:30:03.570> like<00:30:03.780> so<00:30:03.990> when<00:30:04.170> you're<00:30:04.350> typically 00:30:05.000 --> 00:30:05.010 align:start position:0% little bit like so when you're typically 00:30:05.010 --> 00:30:06.530 align:start position:0% little bit like so when you're typically and<00:30:05.190> like<00:30:05.340> an<00:30:05.520> inherited<00:30:05.970> languages<00:30:06.450> or 00:30:06.530 --> 00:30:06.540 align:start position:0% and like an inherited languages or 00:30:06.540 --> 00:30:09.230 align:start position:0% and like an inherited languages or languages<00:30:06.930> less<00:30:07.760> sophisticated<00:30:08.760> type 00:30:09.230 --> 00:30:09.240 align:start position:0% languages less sophisticated type 00:30:09.240 --> 00:30:11.690 align:start position:0% languages less sophisticated type language<00:30:09.660> every<00:30:10.440> kind<00:30:10.680> of<00:30:10.830> operation<00:30:11.370> you<00:30:11.400> end 00:30:11.690 --> 00:30:11.700 align:start position:0% language every kind of operation you end 00:30:11.700 --> 00:30:13.340 align:start position:0% language every kind of operation you end up<00:30:11.820> doing<00:30:12.150> something<00:30:12.450> important<00:30:12.990> you'll<00:30:13.110> have 00:30:13.340 --> 00:30:13.350 align:start position:0% up doing something important you'll have 00:30:13.350 --> 00:30:15.440 align:start position:0% up doing something important you'll have like<00:30:13.500> a<00:30:13.560> lot<00:30:13.890> of<00:30:13.950> instinct<00:30:14.490> and<00:30:14.760> they<00:30:15.210> kind<00:30:15.420> of 00:30:15.440 --> 00:30:15.450 align:start position:0% like a lot of instinct and they kind of 00:30:15.450 --> 00:30:16.730 align:start position:0% like a lot of instinct and they kind of like<00:30:15.540> all<00:30:15.780> end<00:30:15.990> up<00:30:16.080> at<00:30:16.230> the<00:30:16.320> same<00:30:16.500> place 00:30:16.730 --> 00:30:16.740 align:start position:0% like all end up at the same place 00:30:16.740 --> 00:30:18.680 align:start position:0% like all end up at the same place because<00:30:17.610> you're<00:30:17.760> doing<00:30:17.940> something<00:30:18.270> you<00:30:18.540> can 00:30:18.680 --> 00:30:18.690 align:start position:0% because you're doing something you can 00:30:18.690 --> 00:30:22.220 align:start position:0% because you're doing something you can have<00:30:18.780> whatever<00:30:19.530> was<00:30:19.920> coming<00:30:20.220> before<00:30:20.420> Kari<00:30:21.420> the 00:30:22.220 --> 00:30:22.230 align:start position:0% have whatever was coming before Kari the 00:30:22.230 --> 00:30:24.290 align:start position:0% have whatever was coming before Kari the certainty<00:30:22.890> of<00:30:22.920> that<00:30:23.160> information<00:30:23.610> at<00:30:24.150> that 00:30:24.290 --> 00:30:24.300 align:start position:0% certainty of that information at that 00:30:24.300 --> 00:30:26.330 align:start position:0% certainty of that information at that point<00:30:24.600> in<00:30:24.870> your<00:30:25.020> code<00:30:25.230> whereas<00:30:26.100> like 00:30:26.330 --> 00:30:26.340 align:start position:0% point in your code whereas like 00:30:26.340 --> 00:30:28.100 align:start position:0% point in your code whereas like typically<00:30:26.940> by<00:30:27.090> composing<00:30:27.540> a<00:30:27.810> lot<00:30:27.960> of 00:30:28.100 --> 00:30:28.110 align:start position:0% typically by composing a lot of 00:30:28.110 --> 00:30:31.550 align:start position:0% typically by composing a lot of interactions<00:30:29.040> in<00:30:29.280> which<00:30:29.490> the<00:30:30.200> guarantees<00:30:31.200> of 00:30:31.550 --> 00:30:31.560 align:start position:0% interactions in which the guarantees of 00:30:31.560 --> 00:30:33.830 align:start position:0% interactions in which the guarantees of the<00:30:31.740> data<00:30:31.920> is<00:30:32.100> encoded<00:30:32.400> in<00:30:32.670> a<00:30:32.730> passive<00:30:33.150> way<00:30:33.330> you 00:30:33.830 --> 00:30:33.840 align:start position:0% the data is encoded in a passive way you 00:30:33.840 --> 00:30:35.630 align:start position:0% the data is encoded in a passive way you basically<00:30:34.410> don't<00:30:34.620> see<00:30:34.950> any<00:30:35.220> of<00:30:35.310> these<00:30:35.400> if 00:30:35.630 --> 00:30:35.640 align:start position:0% basically don't see any of these if 00:30:35.640 --> 00:30:37.850 align:start position:0% basically don't see any of these if statements<00:30:35.670> or<00:30:36.330> assertions<00:30:36.960> in<00:30:37.170> your<00:30:37.500> code 00:30:37.850 --> 00:30:37.860 align:start position:0% statements or assertions in your code 00:30:37.860 --> 00:30:40.580 align:start position:0% statements or assertions in your code itself<00:30:38.280> they're<00:30:38.700> all<00:30:38.910> packed<00:30:39.660> into<00:30:39.960> the<00:30:40.350> type 00:30:40.580 --> 00:30:40.590 align:start position:0% itself they're all packed into the type 00:30:40.590 --> 00:30:41.570 align:start position:0% itself they're all packed into the type and<00:30:40.860> then<00:30:40.950> they're<00:30:41.190> sort<00:30:41.340> of<00:30:41.430> the 00:30:41.570 --> 00:30:41.580 align:start position:0% and then they're sort of the 00:30:41.580 --> 00:30:43.340 align:start position:0% and then they're sort of the corresponding<00:30:42.150> parser<00:30:42.630> or<00:30:42.840> whatever<00:30:43.140> it<00:30:43.320> is 00:30:43.340 --> 00:30:43.350 align:start position:0% corresponding parser or whatever it is 00:30:43.350 --> 00:30:45.830 align:start position:0% corresponding parser or whatever it is inferred<00:30:43.830> yeah<00:30:44.550> so<00:30:44.940> when<00:30:45.390> you're<00:30:45.510> looking<00:30:45.720> at 00:30:45.830 --> 00:30:45.840 align:start position:0% inferred yeah so when you're looking at 00:30:45.840 --> 00:30:48.770 align:start position:0% inferred yeah so when you're looking at an<00:30:45.960> actual<00:30:46.770> application<00:30:47.220> code<00:30:47.970> you<00:30:48.180> don't<00:30:48.420> see 00:30:48.770 --> 00:30:48.780 align:start position:0% an actual application code you don't see 00:30:48.780 --> 00:30:51.050 align:start position:0% an actual application code you don't see any<00:30:49.170> of<00:30:49.260> these<00:30:49.470> type<00:30:49.800> oh<00:30:50.070> let<00:30:50.670> me<00:30:50.730> just<00:30:50.760> make 00:30:51.050 --> 00:30:51.060 align:start position:0% any of these type oh let me just make 00:30:51.060 --> 00:30:53.000 align:start position:0% any of these type oh let me just make sure<00:30:51.090> right<00:30:51.570> here<00:30:51.810> that<00:30:51.990> I<00:30:52.020> did<00:30:52.260> it<00:30:52.350> like<00:30:52.530> mess 00:30:53.000 --> 00:30:53.010 align:start position:0% sure right here that I did it like mess 00:30:53.010 --> 00:30:57.280 align:start position:0% sure right here that I did it like mess up<00:30:53.040> hold<00:30:53.940> on<00:30:54.180> and<00:30:54.420> it's<00:30:55.050> in<00:30:55.170> this<00:30:55.380> sort<00:30:56.280> of<00:30:56.310> like 00:30:57.280 --> 00:30:57.290 align:start position:0% up hold on and it's in this sort of like 00:30:57.290 --> 00:31:00.580 align:start position:0% up hold on and it's in this sort of like so<00:30:57.920> that<00:30:58.070> company<00:30:58.430> with<00:30:58.550> a<00:30:58.640> mission<00:30:59.590> yeah 00:31:00.580 --> 00:31:00.590 align:start position:0% so that company with a mission yeah 00:31:00.590 --> 00:31:05.590 align:start position:0% so that company with a mission yeah totally<00:31:01.780> and<00:31:02.800> then<00:31:03.800> you<00:31:04.040> know<00:31:04.160> for<00:31:04.550> okay<00:31:05.150> back 00:31:05.590 --> 00:31:05.600 align:start position:0% totally and then you know for okay back 00:31:05.600 --> 00:31:06.970 align:start position:0% totally and then you know for okay back to<00:31:05.630> the<00:31:05.810> inflexible<00:31:06.080> system<00:31:06.560> for<00:31:06.830> like 00:31:06.970 --> 00:31:06.980 align:start position:0% to the inflexible system for like 00:31:06.980 --> 00:31:08.590 align:start position:0% to the inflexible system for like Network<00:31:07.370> computations<00:31:08.030> so<00:31:08.210> we<00:31:08.300> previously 00:31:08.590 --> 00:31:08.600 align:start position:0% Network computations so we previously 00:31:08.600 --> 00:31:10.150 align:start position:0% Network computations so we previously coverages<00:31:09.170> things<00:31:09.350> that<00:31:09.530> are<00:31:09.650> like<00:31:09.830> basically 00:31:10.150 --> 00:31:10.160 align:start position:0% coverages things that are like basically 00:31:10.160 --> 00:31:11.680 align:start position:0% coverages things that are like basically hand<00:31:10.460> on<00:31:10.550> the<00:31:10.640> arrows<00:31:10.970> or<00:31:11.090> exceptions<00:31:11.570> or 00:31:11.680 --> 00:31:11.690 align:start position:0% hand on the arrows or exceptions or 00:31:11.690 --> 00:31:13.960 align:start position:0% hand on the arrows or exceptions or whatever<00:31:11.900> what<00:31:12.830> you<00:31:13.190> know<00:31:13.280> if<00:31:13.550> you're<00:31:13.670> able<00:31:13.760> to 00:31:13.960 --> 00:31:13.970 align:start position:0% whatever what you know if you're able to 00:31:13.970 --> 00:31:16.030 align:start position:0% whatever what you know if you're able to encapsulate<00:31:14.240> like<00:31:14.900> network<00:31:15.830> laws 00:31:16.030 --> 00:31:16.040 align:start position:0% encapsulate like network laws 00:31:16.040 --> 00:31:18.280 align:start position:0% encapsulate like network laws particularly<00:31:16.460> in<00:31:16.820> the<00:31:16.900> context<00:31:17.900> of<00:31:17.990> a<00:31:18.080> theory 00:31:18.280 --> 00:31:18.290 align:start position:0% particularly in the context of a theory 00:31:18.290 --> 00:31:20.050 align:start position:0% particularly in the context of a theory whatever<00:31:18.470> inside<00:31:19.220> of<00:31:19.280> a<00:31:19.340> synthetic<00:31:19.520> system 00:31:20.050 --> 00:31:20.060 align:start position:0% whatever inside of a synthetic system 00:31:20.060 --> 00:31:21.940 align:start position:0% whatever inside of a synthetic system when<00:31:20.690> it<00:31:20.810> kind<00:31:21.020> of<00:31:21.110> guarantee<00:31:21.560> visas<00:31:21.890> that 00:31:21.940 --> 00:31:21.950 align:start position:0% when it kind of guarantee visas that 00:31:21.950 --> 00:31:23.770 align:start position:0% when it kind of guarantee visas that like<00:31:22.250> you<00:31:22.400> can't<00:31:22.640> take<00:31:22.820> for<00:31:22.970> granted<00:31:23.240> that<00:31:23.600> if 00:31:23.770 --> 00:31:23.780 align:start position:0% like you can't take for granted that if 00:31:23.780 --> 00:31:26.140 align:start position:0% like you can't take for granted that if you<00:31:23.900> run<00:31:24.110> you<00:31:24.470> know<00:31:24.560> computation<00:31:25.280> in<00:31:25.820> one 00:31:26.140 --> 00:31:26.150 align:start position:0% you run you know computation in one 00:31:26.150 --> 00:31:27.610 align:start position:0% you run you know computation in one place<00:31:26.390> that<00:31:26.660> you<00:31:26.750> would<00:31:26.870> get<00:31:27.080> the<00:31:27.410> same 00:31:27.610 --> 00:31:27.620 align:start position:0% place that you would get the same 00:31:27.620 --> 00:31:30.000 align:start position:0% place that you would get the same results<00:31:28.040> as<00:31:28.130> if<00:31:28.250> you<00:31:28.310> try<00:31:28.490> to<00:31:28.550> write<00:31:28.700> ahead<00:31:28.820> so 00:31:30.000 --> 00:31:30.010 align:start position:0% results as if you try to write ahead so 00:31:30.010 --> 00:31:32.710 align:start position:0% results as if you try to write ahead so what<00:31:31.010> it's<00:31:31.130> saying<00:31:31.190> is<00:31:31.400> that<00:31:31.460> like<00:31:31.670> where<00:31:32.570> you 00:31:32.710 --> 00:31:32.720 align:start position:0% what it's saying is that like where you 00:31:32.720 --> 00:31:34.780 align:start position:0% what it's saying is that like where you where<00:31:33.110> you<00:31:33.260> call<00:31:33.530> where<00:31:33.800> you<00:31:33.830> live<00:31:34.070> where<00:31:34.760> you 00:31:34.780 --> 00:31:34.790 align:start position:0% where you call where you live where you 00:31:34.790 --> 00:31:36.460 align:start position:0% where you call where you live where you make<00:31:35.000> a<00:31:35.030> quick<00:31:35.240> phone<00:31:35.390> calls<00:31:35.630> and<00:31:35.960> change<00:31:36.230> the 00:31:36.460 --> 00:31:36.470 align:start position:0% make a quick phone calls and change the 00:31:36.470 --> 00:31:37.870 align:start position:0% make a quick phone calls and change the code<00:31:36.620> that<00:31:36.800> comes<00:31:36.920> after<00:31:37.310> it<00:31:37.430> and<00:31:37.610> so<00:31:37.760> you 00:31:37.870 --> 00:31:37.880 align:start position:0% code that comes after it and so you 00:31:37.880 --> 00:31:39.280 align:start position:0% code that comes after it and so you can't<00:31:38.120> just<00:31:38.300> like<00:31:38.480> make<00:31:38.780> them<00:31:38.960> wherever<00:31:39.170> you 00:31:39.280 --> 00:31:39.290 align:start position:0% can't just like make them wherever you 00:31:39.290 --> 00:31:41.050 align:start position:0% can't just like make them wherever you want<00:31:39.440> you<00:31:39.830> need<00:31:39.980> to<00:31:40.100> have<00:31:40.250> them<00:31:40.430> sequence<00:31:40.850> in<00:31:41.000> a 00:31:41.050 --> 00:31:41.060 align:start position:0% want you need to have them sequence in a 00:31:41.060 --> 00:31:42.550 align:start position:0% want you need to have them sequence in a certain<00:31:41.300> way<00:31:41.420> if<00:31:41.570> you<00:31:41.720> don't<00:31:41.900> do<00:31:42.110> a<00:31:42.140> good<00:31:42.230> tight 00:31:42.550 --> 00:31:42.560 align:start position:0% certain way if you don't do a good tight 00:31:42.560 --> 00:31:42.940 align:start position:0% certain way if you don't do a good tight barrier 00:31:42.940 --> 00:31:42.950 align:start position:0% barrier 00:31:42.950 --> 00:31:44.980 align:start position:0% barrier the<00:31:43.490> program<00:31:43.790> will<00:31:43.910> never<00:31:44.090> run<00:31:44.540> because<00:31:44.870> it 00:31:44.980 --> 00:31:44.990 align:start position:0% the program will never run because it 00:31:44.990 --> 00:31:47.110 align:start position:0% the program will never run because it can't<00:31:45.140> quite<00:31:45.500> say<00:31:46.430> for<00:31:46.580> example<00:31:46.940> like 00:31:47.110 --> 00:31:47.120 align:start position:0% can't quite say for example like 00:31:47.120 --> 00:31:49.660 align:start position:0% can't quite say for example like whatever<00:31:47.960> there's<00:31:48.860> like<00:31:49.010> any<00:31:49.040> but<00:31:49.400> three 00:31:49.660 --> 00:31:49.670 align:start position:0% whatever there's like any but three 00:31:49.670 --> 00:31:51.460 align:start position:0% whatever there's like any but three effect<00:31:50.030> which<00:31:50.210> is<00:31:50.360> in<00:31:50.510> this<00:31:50.660> library<00:31:50.930> which 00:31:51.460 --> 00:31:51.470 align:start position:0% effect which is in this library which 00:31:51.470 --> 00:31:52.780 align:start position:0% effect which is in this library which manages<00:31:52.070> all<00:31:52.280> of<00:31:52.370> the<00:31:52.460> effectual 00:31:52.780 --> 00:31:52.790 align:start position:0% manages all of the effectual 00:31:52.790 --> 00:31:56.430 align:start position:0% manages all of the effectual computations<00:31:53.420> that<00:31:53.510> run<00:31:54.050> against 00:31:56.430 --> 00:31:56.440 align:start position:0% 00:31:56.440 --> 00:31:58.600 align:start position:0% there<00:31:57.440> is<00:31:57.530> a<00:31:57.560> really<00:31:57.890> really<00:31:58.010> big<00:31:58.250> difference 00:31:58.600 --> 00:31:58.610 align:start position:0% there is a really really big difference 00:31:58.610 --> 00:32:00.850 align:start position:0% there is a really really big difference between<00:31:58.700> the<00:31:58.970> value<00:31:59.270> of<00:31:59.390> type<00:31:59.570> A<00:31:59.840> and<00:32:00.140> a<00:32:00.590> value 00:32:00.850 --> 00:32:00.860 align:start position:0% between the value of type A and a value 00:32:00.860 --> 00:32:03.340 align:start position:0% between the value of type A and a value of<00:32:00.980> type<00:32:01.160> 2b<00:32:01.610> domain<00:32:01.970> and<00:32:02.270> basically<00:32:03.170> like 00:32:03.340 --> 00:32:03.350 align:start position:0% of type 2b domain and basically like 00:32:03.350 --> 00:32:04.720 align:start position:0% of type 2b domain and basically like understanding<00:32:04.010> this<00:32:04.130> difference<00:32:04.520> or<00:32:04.670> at 00:32:04.720 --> 00:32:04.730 align:start position:0% understanding this difference or at 00:32:04.730 --> 00:32:06.100 align:start position:0% understanding this difference or at least<00:32:04.910> getting<00:32:05.090> used<00:32:05.300> to<00:32:05.390> it<00:32:05.570> is<00:32:05.660> kind<00:32:05.930> of<00:32:05.960> the 00:32:06.100 --> 00:32:06.110 align:start position:0% least getting used to it is kind of the 00:32:06.110 --> 00:32:07.990 align:start position:0% least getting used to it is kind of the basis<00:32:06.500> for<00:32:06.680> everything<00:32:07.010> that<00:32:07.310> happens<00:32:07.820> here 00:32:07.990 --> 00:32:08.000 align:start position:0% basis for everything that happens here 00:32:08.000 --> 00:32:10.060 align:start position:0% basis for everything that happens here so<00:32:08.330> I<00:32:08.600> can't<00:32:08.930> tell<00:32:09.140> you<00:32:09.290> how<00:32:09.470> to<00:32:09.530> understand<00:32:10.010> it 00:32:10.060 --> 00:32:10.070 align:start position:0% so I can't tell you how to understand it 00:32:10.070 --> 00:32:10.990 align:start position:0% so I can't tell you how to understand it but<00:32:10.250> I<00:32:10.310> can<00:32:10.490> tell<00:32:10.520> you<00:32:10.700> that<00:32:10.820> if<00:32:10.910> you 00:32:10.990 --> 00:32:11.000 align:start position:0% but I can tell you that if you 00:32:11.000 --> 00:32:12.670 align:start position:0% but I can tell you that if you understand<00:32:11.390> the<00:32:11.450> difference<00:32:11.750> between<00:32:12.050> having 00:32:12.670 --> 00:32:12.680 align:start position:0% understand the difference between having 00:32:12.680 --> 00:32:15.220 align:start position:0% understand the difference between having a<00:32:13.130> value<00:32:13.610> of<00:32:13.880> type<00:32:14.090> address<00:32:14.690> and<00:32:14.960> having 00:32:15.220 --> 00:32:15.230 align:start position:0% a value of type address and having 00:32:15.230 --> 00:32:17.110 align:start position:0% a value of type address and having entire<00:32:15.500> the<00:32:15.950> value<00:32:16.190> of<00:32:16.250> type<00:32:16.430> web<00:32:16.640> 3<00:32:16.970> of 00:32:17.110 --> 00:32:17.120 align:start position:0% entire the value of type web 3 of 00:32:17.120 --> 00:32:18.820 align:start position:0% entire the value of type web 3 of interest<00:32:17.480> these<00:32:17.900> are<00:32:18.050> very<00:32:18.290> very<00:32:18.470> different 00:32:18.820 --> 00:32:18.830 align:start position:0% interest these are very very different 00:32:18.830 --> 00:32:20.740 align:start position:0% interest these are very very different things<00:32:18.980> I<00:32:19.370> can't<00:32:20.030> explain<00:32:20.240> it<00:32:20.330> to<00:32:20.480> you<00:32:20.540> all<00:32:20.660> I 00:32:20.740 --> 00:32:20.750 align:start position:0% things I can't explain it to you all I 00:32:20.750 --> 00:32:24.790 align:start position:0% things I can't explain it to you all I can<00:32:20.780> do<00:32:20.990> examines<00:32:23.110> this<00:32:24.110> is<00:32:24.260> an<00:32:24.380> example<00:32:24.620> which 00:32:24.790 --> 00:32:24.800 align:start position:0% can do examines this is an example which 00:32:24.800 --> 00:32:26.020 align:start position:0% can do examines this is an example which unfortunately<00:32:25.100> it's<00:32:25.460> gonna<00:32:25.550> be<00:32:25.670> really<00:32:25.820> hard 00:32:26.020 --> 00:32:26.030 align:start position:0% unfortunately it's gonna be really hard 00:32:26.030 --> 00:32:28.780 align:start position:0% unfortunately it's gonna be really hard to<00:32:26.060> reproduce<00:32:26.450> my<00:32:26.630> back<00:32:26.810> but<00:32:27.700> here's<00:32:28.700> an 00:32:28.780 --> 00:32:28.790 align:start position:0% to reproduce my back but here's an 00:32:28.790 --> 00:32:30.760 align:start position:0% to reproduce my back but here's an example<00:32:29.000> for<00:32:29.210> test<00:32:29.510> suite<00:32:29.720> or<00:32:29.870> whatever<00:32:30.080> so 00:32:30.760 --> 00:32:30.770 align:start position:0% example for test suite or whatever so 00:32:30.770 --> 00:32:33.760 align:start position:0% example for test suite or whatever so here<00:32:31.430> I<00:32:31.460> have<00:32:31.580> in<00:32:32.150> highlighted<00:32:32.750> so<00:32:33.140> here<00:32:33.740> I 00:32:33.760 --> 00:32:33.770 align:start position:0% here I have in highlighted so here I 00:32:33.770 --> 00:32:34.930 align:start position:0% here I have in highlighted so here I have<00:32:33.830> highlighted<00:32:34.310> all<00:32:34.520> of<00:32:34.550> the<00:32:34.730> pure 00:32:34.930 --> 00:32:34.940 align:start position:0% have highlighted all of the pure 00:32:34.940 --> 00:32:37.090 align:start position:0% have highlighted all of the pure computations<00:32:35.570> here<00:32:35.750> interactively<00:32:36.740> a<00:32:36.770> series 00:32:37.090 --> 00:32:37.100 align:start position:0% computations here interactively a series 00:32:37.100 --> 00:32:39.130 align:start position:0% computations here interactively a series of<00:32:37.130> led<00:32:37.400> by<00:32:37.580> this<00:32:37.640> so<00:32:38.510> basically<00:32:38.870> like 00:32:39.130 --> 00:32:39.140 align:start position:0% of led by this so basically like 00:32:39.140 --> 00:32:42.490 align:start position:0% of led by this so basically like variable<00:32:39.890> bindings<00:32:40.310> and<00:32:40.580> making<00:32:41.500> sized 00:32:42.490 --> 00:32:42.500 align:start position:0% variable bindings and making sized 00:32:42.500 --> 00:32:46.180 align:start position:0% variable bindings and making sized integers<00:32:43.070> and<00:32:43.310> things<00:32:43.570> and<00:32:44.950> these<00:32:45.950> are<00:32:46.100> the 00:32:46.180 --> 00:32:46.190 align:start position:0% integers and things and these are the 00:32:46.190 --> 00:32:49.240 align:start position:0% integers and things and these are the things<00:32:46.370> which<00:32:46.460> they<00:32:46.790> are<00:32:46.910> not<00:32:47.060> effective<00:32:48.250> and 00:32:49.240 --> 00:32:49.250 align:start position:0% things which they are not effective and 00:32:49.250 --> 00:32:51.430 align:start position:0% things which they are not effective and then<00:32:49.760> actually<00:32:50.240> for<00:32:50.510> example<00:32:50.870> this<00:32:51.170> is<00:32:51.320> it 00:32:51.430 --> 00:32:51.440 align:start position:0% then actually for example this is it 00:32:51.440 --> 00:32:53.650 align:start position:0% then actually for example this is it says<00:32:51.740> for<00:32:52.520> context<00:32:52.910> this<00:32:53.000> is<00:32:53.150> a<00:32:53.180> set<00:32:53.420> up<00:32:53.510> to 00:32:53.650 --> 00:32:53.660 align:start position:0% says for context this is a set up to 00:32:53.660 --> 00:32:56.710 align:start position:0% says for context this is a set up to basically<00:32:53.930> in<00:32:54.080> the<00:32:54.140> u.s.<00:32:54.290> in<00:32:54.470> 2002<00:32:54.800> over<00:32:55.720> here 00:32:56.710 --> 00:32:56.720 align:start position:0% basically in the u.s. in 2002 over here 00:32:56.720 --> 00:32:58.210 align:start position:0% basically in the u.s. in 2002 over here is<00:32:56.840> like<00:32:57.020> the<00:32:57.200> attentional<00:32:57.560> computations<00:32:58.100> are 00:32:58.210 --> 00:32:58.220 align:start position:0% is like the attentional computations are 00:32:58.220 --> 00:32:59.860 align:start position:0% is like the attentional computations are highlighted<00:32:58.610> here<00:32:58.640> basically<00:32:59.000> as<00:32:59.300> a<00:32:59.330> trend<00:32:59.690> is 00:32:59.860 --> 00:32:59.870 align:start position:0% highlighted here basically as a trend is 00:32:59.870 --> 00:33:02.410 align:start position:0% highlighted here basically as a trend is a<00:32:59.900> transfer<00:33:00.380> so<00:33:00.980> when<00:33:01.700> you<00:33:01.820> want<00:33:01.970> to<00:33:02.000> transfer 00:33:02.410 --> 00:33:02.420 align:start position:0% a transfer so when you want to transfer 00:33:02.420 --> 00:33:04.720 align:start position:0% a transfer so when you want to transfer tokens<00:33:02.810> that<00:33:03.080> is<00:33:03.680> an<00:33:03.800> effect<00:33:04.130> when<00:33:04.460> you<00:33:04.580> do 00:33:04.720 --> 00:33:04.730 align:start position:0% tokens that is an effect when you do 00:33:04.730 --> 00:33:07.090 align:start position:0% tokens that is an effect when you do that<00:33:04.880> it<00:33:05.270> whether<00:33:05.900> it<00:33:06.080> succeeds<00:33:06.260> or<00:33:06.620> fails<00:33:06.650> the 00:33:07.090 --> 00:33:07.100 align:start position:0% that it whether it succeeds or fails the 00:33:07.100 --> 00:33:10.840 align:start position:0% that it whether it succeeds or fails the world<00:33:07.580> is<00:33:07.730> forever<00:33:07.940> changed<00:33:08.450> because<00:33:09.700> all<00:33:10.700> you 00:33:10.840 --> 00:33:10.850 align:start position:0% world is forever changed because all you 00:33:10.850 --> 00:33:12.210 align:start position:0% world is forever changed because all you cause<00:33:11.090> some<00:33:11.330> other<00:33:11.450> thing<00:33:11.840> else 00:33:12.210 --> 00:33:12.220 align:start position:0% cause some other thing else 00:33:12.220 --> 00:33:16.289 align:start position:0% cause some other thing else to<00:33:12.880> react<00:33:13.500> and<00:33:14.500> then<00:33:15.370> basically<00:33:16.030> what<00:33:16.179> I'm 00:33:16.289 --> 00:33:16.299 align:start position:0% to react and then basically what I'm 00:33:16.299 --> 00:33:19.020 align:start position:0% to react and then basically what I'm saying<00:33:16.330> here<00:33:16.750> is<00:33:16.780> that<00:33:16.870> like<00:33:17.230> in<00:33:17.799> order<00:33:18.730> to<00:33:18.850> run 00:33:19.020 --> 00:33:19.030 align:start position:0% saying here is that like in order to run 00:33:19.030 --> 00:33:21.360 align:start position:0% saying here is that like in order to run the<00:33:19.179> in<00:33:19.539> order<00:33:19.690> to<00:33:19.750> run<00:33:20.020> the<00:33:20.200> effects<00:33:20.530> remember 00:33:21.360 --> 00:33:21.370 align:start position:0% the in order to run the effects remember 00:33:21.370 --> 00:33:22.409 align:start position:0% the in order to run the effects remember to<00:33:21.460> give<00:33:21.640> the<00:33:21.789> thing<00:33:21.909> that<00:33:22.030> you're<00:33:22.120> looking 00:33:22.409 --> 00:33:22.419 align:start position:0% to give the thing that you're looking 00:33:22.419 --> 00:33:24.930 align:start position:0% to give the thing that you're looking for<00:33:22.570> which<00:33:23.020> is<00:33:23.049> effectively<00:33:23.679> like<00:33:23.799> at<00:33:24.669> the<00:33:24.820> end 00:33:24.930 --> 00:33:24.940 align:start position:0% for which is effectively like at the end 00:33:24.940 --> 00:33:28.640 align:start position:0% for which is effectively like at the end of<00:33:25.059> this<00:33:25.120> commutation<00:33:25.630> is<00:33:25.870> like<00:33:26.049> a 00:33:28.640 --> 00:33:28.650 align:start position:0% 00:33:28.650 --> 00:33:31.070 align:start position:0% and<00:33:29.520> results<00:33:30.000> and<00:33:30.120> causing<00:33:30.510> this<00:33:30.630> transfer 00:33:31.070 --> 00:33:31.080 align:start position:0% and results and causing this transfer 00:33:31.080 --> 00:33:34.580 align:start position:0% and results and causing this transfer event<00:33:31.380> to<00:33:31.470> happen<00:33:32.660> it's<00:33:33.660> usually<00:33:34.080> previous<00:33:34.500> in 00:33:34.580 --> 00:33:34.590 align:start position:0% event to happen it's usually previous in 00:33:34.590 --> 00:33:36.110 align:start position:0% event to happen it's usually previous in terms<00:33:34.800> of<00:33:34.950> like<00:33:35.070> events<00:33:35.460> or<00:33:35.550> whatever<00:33:35.790> this 00:33:36.110 --> 00:33:36.120 align:start position:0% terms of like events or whatever this 00:33:36.120 --> 00:33:38.060 align:start position:0% terms of like events or whatever this year<00:33:36.330> is<00:33:36.720> when<00:33:36.930> is<00:33:37.050> another<00:33:37.290> effect<00:33:37.710> like 00:33:38.060 --> 00:33:38.070 align:start position:0% year is when is another effect like 00:33:38.070 --> 00:33:40.010 align:start position:0% year is when is another effect like these<00:33:38.370> things<00:33:38.670> it<00:33:39.030> has<00:33:39.270> to<00:33:39.420> happen<00:33:39.570> before 00:33:40.010 --> 00:33:40.020 align:start position:0% these things it has to happen before 00:33:40.020 --> 00:33:42.620 align:start position:0% these things it has to happen before this<00:33:40.140> can<00:33:40.320> happen<00:33:40.500> yeah<00:33:41.460> so<00:33:41.640> maybe<00:33:41.790> just<00:33:41.910> from 00:33:42.620 --> 00:33:42.630 align:start position:0% this can happen yeah so maybe just from 00:33:42.630 --> 00:33:45.560 align:start position:0% this can happen yeah so maybe just from here<00:33:43.010> we're<00:33:44.010> we're<00:33:44.490> telling<00:33:45.150> the<00:33:45.270> compiler 00:33:45.560 --> 00:33:45.570 align:start position:0% here we're we're telling the compiler 00:33:45.570 --> 00:33:48.020 align:start position:0% here we're we're telling the compiler that<00:33:45.750> this<00:33:46.520> transformational<00:33:47.520> medicine<00:33:47.910> web 00:33:48.020 --> 00:33:48.030 align:start position:0% that this transformational medicine web 00:33:48.030 --> 00:33:49.970 align:start position:0% that this transformational medicine web 3<00:33:48.330> we<00:33:49.020> don't<00:33:49.200> know<00:33:49.350> what<00:33:49.500> that's<00:33:49.620> what<00:33:49.800> other 00:33:49.970 --> 00:33:49.980 align:start position:0% 3 we don't know what that's what other 00:33:49.980 --> 00:33:51.860 align:start position:0% 3 we don't know what that's what other tech<00:33:50.160> centers<00:33:50.520> in<00:33:50.670> the<00:33:50.790> other<00:33:51.240> world<00:33:51.450> the<00:33:51.660> only 00:33:51.860 --> 00:33:51.870 align:start position:0% tech centers in the other world the only 00:33:51.870 --> 00:33:53.960 align:start position:0% tech centers in the other world the only way<00:33:51.990> we<00:33:52.050> can<00:33:52.290> sort<00:33:52.500> of<00:33:52.590> look<00:33:52.800> into<00:33:53.070> it<00:33:53.310> is<00:33:53.490> to 00:33:53.960 --> 00:33:53.970 align:start position:0% way we can sort of look into it is to 00:33:53.970 --> 00:33:56.090 align:start position:0% way we can sort of look into it is to run<00:33:54.660> the<00:33:54.840> circuitry<00:33:55.350> this<00:33:55.650> is<00:33:55.770> sort<00:33:55.920> of<00:33:55.950> like<00:33:56.040> a 00:33:56.090 --> 00:33:56.100 align:start position:0% run the circuitry this is sort of like a 00:33:56.100 --> 00:33:59.120 align:start position:0% run the circuitry this is sort of like a run<00:33:56.430> demo<00:33:57.290> now<00:33:58.290> you<00:33:58.350> like<00:33:58.560> resolve<00:33:58.980> the 00:33:59.120 --> 00:33:59.130 align:start position:0% run demo now you like resolve the 00:33:59.130 --> 00:34:04.610 align:start position:0% run demo now you like resolve the effects<00:34:01.280> so<00:34:02.280> like<00:34:03.020> I'm<00:34:04.020> happy<00:34:04.200> to<00:34:04.350> talk<00:34:04.500> to 00:34:04.610 --> 00:34:04.620 align:start position:0% effects so like I'm happy to talk to 00:34:04.620 --> 00:34:06.320 align:start position:0% effects so like I'm happy to talk to anybody<00:34:04.740> or<00:34:05.370> has<00:34:05.610> some<00:34:05.760> questions<00:34:06.030> about<00:34:06.090> this 00:34:06.320 --> 00:34:06.330 align:start position:0% anybody or has some questions about this 00:34:06.330 --> 00:34:08.530 align:start position:0% anybody or has some questions about this but<00:34:06.600> it's<00:34:06.990> kind<00:34:07.200> of<00:34:07.260> like<00:34:07.320> saying<00:34:07.710> that<00:34:07.890> like 00:34:08.530 --> 00:34:08.540 align:start position:0% but it's kind of like saying that like 00:34:08.540 --> 00:34:10.940 align:start position:0% but it's kind of like saying that like you<00:34:09.540> have<00:34:09.570> to<00:34:09.930> there<00:34:10.470> are<00:34:10.590> certain<00:34:10.830> places 00:34:10.940 --> 00:34:10.950 align:start position:0% you have to there are certain places 00:34:10.950 --> 00:34:13.790 align:start position:0% you have to there are certain places where<00:34:11.340> you're<00:34:11.490> allowed<00:34:11.700> to<00:34:12.000> you<00:34:12.390> know<00:34:12.620> find<00:34:13.620> a 00:34:13.790 --> 00:34:13.800 align:start position:0% where you're allowed to you know find a 00:34:13.800 --> 00:34:16.160 align:start position:0% where you're allowed to you know find a variable<00:34:14.280> to<00:34:14.550> the<00:34:14.760> results<00:34:15.180> of<00:34:15.240> an<00:34:15.360> effect<00:34:15.690> and 00:34:16.160 --> 00:34:16.170 align:start position:0% variable to the results of an effect and 00:34:16.170 --> 00:34:17.750 align:start position:0% variable to the results of an effect and it<00:34:16.290> can't<00:34:16.530> be<00:34:16.620> just<00:34:16.980> like<00:34:17.220> in<00:34:17.370> a<00:34:17.430> simple 00:34:17.750 --> 00:34:17.760 align:start position:0% it can't be just like in a simple 00:34:17.760 --> 00:34:20.030 align:start position:0% it can't be just like in a simple assertion<00:34:18.000> statement<00:34:18.570> here<00:34:19.080> where<00:34:19.290> I'd<00:34:19.410> like 00:34:20.030 --> 00:34:20.040 align:start position:0% assertion statement here where I'd like 00:34:20.040 --> 00:34:22.040 align:start position:0% assertion statement here where I'd like the<00:34:20.460> recipient<00:34:20.970> of<00:34:21.060> this<00:34:21.210> token<00:34:21.690> is<00:34:21.780> going<00:34:21.990> to 00:34:22.040 --> 00:34:22.050 align:start position:0% the recipient of this token is going to 00:34:22.050 --> 00:34:23.900 align:start position:0% the recipient of this token is going to be<00:34:22.140> the<00:34:22.260> null<00:34:22.410> address<00:34:22.740> that's<00:34:23.340> cool<00:34:23.520> I<00:34:23.550> can<00:34:23.820> do 00:34:23.900 --> 00:34:23.910 align:start position:0% be the null address that's cool I can do 00:34:23.910 --> 00:34:25.160 align:start position:0% be the null address that's cool I can do that<00:34:24.030> because<00:34:24.180> there's<00:34:24.480> no<00:34:24.570> effect<00:34:24.840> there's 00:34:25.160 --> 00:34:25.170 align:start position:0% that because there's no effect there's 00:34:25.170 --> 00:34:27.140 align:start position:0% that because there's no effect there's no<00:34:25.260> effect<00:34:25.530> here<00:34:25.590> but<00:34:26.430> at<00:34:26.550> some<00:34:26.730> point<00:34:26.760> if<00:34:27.030> I 00:34:27.140 --> 00:34:27.150 align:start position:0% no effect here but at some point if I 00:34:27.150 --> 00:34:28.820 align:start position:0% no effect here but at some point if I wanted<00:34:27.450> to<00:34:27.570> like<00:34:27.720> take<00:34:27.990> the<00:34:28.200> result<00:34:28.560> of<00:34:28.740> this 00:34:28.820 --> 00:34:28.830 align:start position:0% wanted to like take the result of this 00:34:28.830 --> 00:34:35.990 align:start position:0% wanted to like take the result of this transfer<00:34:33.410> computation<00:34:34.410> I<00:34:34.980> have<00:34:35.550> to<00:34:35.700> do<00:34:35.850> that 00:34:35.990 --> 00:34:36.000 align:start position:0% transfer computation I have to do that 00:34:36.000 --> 00:34:38.750 align:start position:0% transfer computation I have to do that inside<00:34:36.420> there<00:34:36.540> some<00:34:36.810> effects<00:34:37.610> but<00:34:38.610> when 00:34:38.750 --> 00:34:38.760 align:start position:0% inside there some effects but when 00:34:38.760 --> 00:34:40.640 align:start position:0% inside there some effects but when you're<00:34:38.850> saying<00:34:39.120> it<00:34:39.270> yes<00:34:39.510> sir<00:34:39.870> really<00:34:40.500> like 00:34:40.640 --> 00:34:40.650 align:start position:0% you're saying it yes sir really like 00:34:40.650 --> 00:34:42.200 align:start position:0% you're saying it yes sir really like actually<00:34:41.070> caused<00:34:41.280> it<00:34:41.460> to<00:34:41.580> happen<00:34:41.610> is<00:34:42.030> that 00:34:42.200 --> 00:34:42.210 align:start position:0% actually caused it to happen is that 00:34:42.210 --> 00:34:45.890 align:start position:0% actually caused it to happen is that strict<00:34:42.840> over<00:34:43.140> there<00:34:43.350> or<00:34:43.590> is<00:34:43.710> it<00:34:43.740> still<00:34:44.660> is<00:34:45.660> it 00:34:45.890 --> 00:34:45.900 align:start position:0% strict over there or is it still is it 00:34:45.900 --> 00:34:47.810 align:start position:0% strict over there or is it still is it will<00:34:46.260> it<00:34:46.380> still<00:34:46.560> be<00:34:46.740> like<00:34:46.920> lazy<00:34:47.190> there<00:34:47.490> and<00:34:47.730> it 00:34:47.810 --> 00:34:47.820 align:start position:0% will it still be like lazy there and it 00:34:47.820 --> 00:34:49.610 align:start position:0% will it still be like lazy there and it will<00:34:47.910> be<00:34:48.020> there's<00:34:49.020> something<00:34:49.290> down<00:34:49.410> the<00:34:49.590> line 00:34:49.610 --> 00:34:49.620 align:start position:0% will be there's something down the line 00:34:49.620 --> 00:34:53.360 align:start position:0% will be there's something down the line will<00:34:50.070> force<00:34:50.340> the<00:34:50.520> computation<00:34:51.980> yeah<00:34:53.010> so<00:34:53.250> in 00:34:53.360 --> 00:34:53.370 align:start position:0% will force the computation yeah so in 00:34:53.370 --> 00:34:55.400 align:start position:0% will force the computation yeah so in this<00:34:53.490> language<00:34:53.700> the<00:34:54.450> peer<00:34:54.690> script<00:34:54.930> is<00:34:55.020> strict 00:34:55.400 --> 00:34:55.410 align:start position:0% this language the peer script is strict 00:34:55.410 --> 00:34:56.900 align:start position:0% this language the peer script is strict which<00:34:55.590> means<00:34:55.830> that<00:34:56.010> like<00:34:56.250> all<00:34:56.580> these<00:34:56.730> things 00:34:56.900 --> 00:34:56.910 align:start position:0% which means that like all these things 00:34:56.910 --> 00:34:59.480 align:start position:0% which means that like all these things will<00:34:57.090> happen<00:34:57.320> but<00:34:58.320> in<00:34:58.440> Haskell<00:34:58.860> this<00:34:59.040> but<00:34:59.340> this 00:34:59.480 --> 00:34:59.490 align:start position:0% will happen but in Haskell this but this 00:34:59.490 --> 00:35:03.050 align:start position:0% will happen but in Haskell this but this would<00:34:59.790> look<00:34:59.940> identical 00:35:03.050 --> 00:35:03.060 align:start position:0% 00:35:03.060 --> 00:35:06.060 align:start position:0% but<00:35:04.060> yeah<00:35:04.240> that<00:35:04.570> case<00:35:04.840> actually<00:35:05.380> you<00:35:05.920> have 00:35:06.060 --> 00:35:06.070 align:start position:0% but yeah that case actually you have 00:35:06.070 --> 00:35:09.420 align:start position:0% but yeah that case actually you have some<00:35:06.310> notions<00:35:07.290> from<00:35:08.290> instead<00:35:09.040> the<00:35:09.220> type<00:35:09.400> of 00:35:09.420 --> 00:35:09.430 align:start position:0% some notions from instead the type of 00:35:09.430 --> 00:35:11.100 align:start position:0% some notions from instead the type of professional<00:35:09.640> program<00:35:10.240> in<00:35:10.360> the<00:35:10.540> world<00:35:10.810> there 00:35:11.100 --> 00:35:11.110 align:start position:0% professional program in the world there 00:35:11.110 --> 00:35:12.990 align:start position:0% professional program in the world there are<00:35:11.230> some<00:35:11.380> notions<00:35:11.740> about<00:35:11.890> win<00:35:12.310> competitions 00:35:12.990 --> 00:35:13.000 align:start position:0% are some notions about win competitions 00:35:13.000 --> 00:35:15.420 align:start position:0% are some notions about win competitions right<00:35:13.270> as<00:35:14.080> part<00:35:14.380> of<00:35:14.410> the<00:35:14.500> run<00:35:14.710> time<00:35:14.740> is<00:35:15.160> built 00:35:15.420 --> 00:35:15.430 align:start position:0% right as part of the run time is built 00:35:15.430 --> 00:35:17.160 align:start position:0% right as part of the run time is built for<00:35:15.640> the<00:35:15.730> language<00:35:15.940> itself<00:35:16.390> and<00:35:16.750> that<00:35:17.110> can 00:35:17.160 --> 00:35:17.170 align:start position:0% for the language itself and that can 00:35:17.170 --> 00:35:18.930 align:start position:0% for the language itself and that can your<00:35:18.160> still<00:35:18.340> guarantee<00:35:18.640> that<00:35:18.730> they're<00:35:18.880> gonna 00:35:18.930 --> 00:35:18.940 align:start position:0% your still guarantee that they're gonna 00:35:18.940 --> 00:35:21.120 align:start position:0% your still guarantee that they're gonna have<00:35:19.150> an<00:35:19.240> importer<00:35:19.690> but<00:35:19.960> yeah<00:35:20.200> like<00:35:20.440> it<00:35:20.740> what 00:35:21.120 --> 00:35:21.130 align:start position:0% have an importer but yeah like it what 00:35:21.130 --> 00:35:23.430 align:start position:0% have an importer but yeah like it what it<00:35:21.430> what<00:35:21.700> time<00:35:22.000> like<00:35:22.360> take<00:35:22.600> it<00:35:22.900> depends<00:35:23.260> on 00:35:23.430 --> 00:35:23.440 align:start position:0% it what time like take it depends on 00:35:23.440 --> 00:35:30.870 align:start position:0% it what time like take it depends on their<00:35:28.200> so<00:35:29.200> basically<00:35:29.710> like<00:35:29.950> yeah<00:35:30.400> this<00:35:30.580> you 00:35:30.870 --> 00:35:30.880 align:start position:0% their so basically like yeah this you 00:35:30.880 --> 00:35:33.510 align:start position:0% their so basically like yeah this you can<00:35:31.000> go<00:35:31.120> through<00:35:31.270> these<00:35:31.390> slides<00:35:31.630> you<00:35:32.620> know<00:35:32.740> and 00:35:33.510 --> 00:35:33.520 align:start position:0% can go through these slides you know and 00:35:33.520 --> 00:35:35.220 align:start position:0% can go through these slides you know and ask<00:35:33.910> yourself<00:35:34.240> these<00:35:34.300> questions<00:35:34.390> like<00:35:34.930> which 00:35:35.220 --> 00:35:35.230 align:start position:0% ask yourself these questions like which 00:35:35.230 --> 00:35:37.500 align:start position:0% ask yourself these questions like which joke<00:35:35.590> to<00:35:36.070> uses<00:35:36.400> previous<00:35:36.730> lightly<00:35:37.030> which<00:35:37.270> part 00:35:37.500 --> 00:35:37.510 align:start position:0% joke to uses previous lightly which part 00:35:37.510 --> 00:35:38.970 align:start position:0% joke to uses previous lightly which part of<00:35:37.570> this<00:35:37.690> computation<00:35:37.990> is<00:35:38.320> pure<00:35:38.560> which<00:35:38.860> are 00:35:38.970 --> 00:35:38.980 align:start position:0% of this computation is pure which are 00:35:38.980 --> 00:35:41.490 align:start position:0% of this computation is pure which are effective<00:35:39.520> of<00:35:40.510> which<00:35:40.690> parts<00:35:40.990> can<00:35:41.110> be<00:35:41.140> throwing 00:35:41.490 --> 00:35:41.500 align:start position:0% effective of which parts can be throwing 00:35:41.500 --> 00:35:43.110 align:start position:0% effective of which parts can be throwing an<00:35:41.590> exception<00:35:41.680> which<00:35:42.340> parts<00:35:42.640> moving<00:35:42.850> to<00:35:43.000> our 00:35:43.110 --> 00:35:43.120 align:start position:0% an exception which parts moving to our 00:35:43.120 --> 00:35:44.880 align:start position:0% an exception which parts moving to our null<00:35:43.330> pointer<00:35:43.600> exceptions<00:35:44.080> there<00:35:44.530> are<00:35:44.680> none 00:35:44.880 --> 00:35:44.890 align:start position:0% null pointer exceptions there are none 00:35:44.890 --> 00:35:46.500 align:start position:0% null pointer exceptions there are none because<00:35:45.340> they<00:35:45.460> don't<00:35:45.640> exist<00:35:45.850> as<00:35:46.090> languages 00:35:46.500 --> 00:35:46.510 align:start position:0% because they don't exist as languages 00:35:46.510 --> 00:35:48.960 align:start position:0% because they don't exist as languages okay<00:35:47.290> which<00:35:47.710> person<00:35:48.100> can<00:35:48.220> fail<00:35:48.460> which<00:35:48.700> parts 00:35:48.960 --> 00:35:48.970 align:start position:0% okay which person can fail which parts 00:35:48.970 --> 00:35:51.510 align:start position:0% okay which person can fail which parts can't<00:35:49.240> fail<00:35:49.450> is<00:35:50.200> these<00:35:50.560> become<00:35:50.980> basically 00:35:51.510 --> 00:35:51.520 align:start position:0% can't fail is these become basically 00:35:51.520 --> 00:35:53.580 align:start position:0% can't fail is these become basically like<00:35:51.820> self-evident<00:35:52.780> from<00:35:52.900> the<00:35:53.050> code<00:35:53.260> itself 00:35:53.580 --> 00:35:53.590 align:start position:0% like self-evident from the code itself 00:35:53.590 --> 00:35:55.740 align:start position:0% like self-evident from the code itself and<00:35:54.010> so<00:35:54.400> rather<00:35:54.790> than<00:35:54.940> like<00:35:55.270> skimming<00:35:55.720> through 00:35:55.740 --> 00:35:55.750 align:start position:0% and so rather than like skimming through 00:35:55.750 --> 00:35:57.450 align:start position:0% and so rather than like skimming through line<00:35:56.140> by<00:35:56.320> line<00:35:56.350> is<00:35:56.710> inserted<00:35:57.010> much 00:35:57.450 --> 00:35:57.460 align:start position:0% line by line is inserted much 00:35:57.460 --> 00:35:58.980 align:start position:0% line by line is inserted much Princeton's<00:35:58.060> for<00:35:58.360> things<00:35:58.570> to<00:35:58.660> figure<00:35:58.900> out 00:35:58.980 --> 00:35:58.990 align:start position:0% Princeton's for things to figure out 00:35:58.990 --> 00:36:00.570 align:start position:0% Princeton's for things to figure out like<00:35:59.230> when<00:35:59.470> something<00:35:59.800> is<00:35:59.890> going<00:36:00.040> to<00:36:00.100> fail<00:36:00.280> I 00:36:00.570 --> 00:36:00.580 align:start position:0% like when something is going to fail I 00:36:00.580 --> 00:36:06.270 align:start position:0% like when something is going to fail I can<00:36:01.030> look<00:36:01.150> at<00:36:01.270> this<00:36:01.360> program<00:36:04.260> I<00:36:05.260> can<00:36:06.040> look<00:36:06.130> at 00:36:06.270 --> 00:36:06.280 align:start position:0% can look at this program I can look at 00:36:06.280 --> 00:36:08.450 align:start position:0% can look at this program I can look at this<00:36:06.370> program<00:36:06.760> in<00:36:06.880> advance<00:36:07.000> and<00:36:07.510> tell<00:36:07.720> that 00:36:08.450 --> 00:36:08.460 align:start position:0% this program in advance and tell that 00:36:08.460 --> 00:36:10.860 align:start position:0% this program in advance and tell that this<00:36:09.460> line<00:36:09.760> could<00:36:09.940> fail<00:36:10.150> because<00:36:10.300> it<00:36:10.510> has<00:36:10.720> it 00:36:10.860 --> 00:36:10.870 align:start position:0% this line could fail because it has it 00:36:10.870 --> 00:36:11.480 align:start position:0% this line could fail because it has it has 00:36:11.480 --> 00:36:11.490 align:start position:0% has 00:36:11.490 --> 00:36:13.790 align:start position:0% has commutation<00:36:12.240> it's<00:36:12.450> might<00:36:12.660> be<00:36:12.690> tripped<00:36:13.560> up<00:36:13.650> by 00:36:13.790 --> 00:36:13.800 align:start position:0% commutation it's might be tripped up by 00:36:13.800 --> 00:36:15.920 align:start position:0% commutation it's might be tripped up by network<00:36:14.190> error<00:36:14.460> this<00:36:15.060> is<00:36:15.210> a<00:36:15.240> variable<00:36:15.750> binding 00:36:15.920 --> 00:36:15.930 align:start position:0% network error this is a variable binding 00:36:15.930 --> 00:36:17.810 align:start position:0% network error this is a variable binding that<00:36:16.350> could<00:36:16.650> cause<00:36:16.860> that<00:36:16.890> basically<00:36:17.700> his 00:36:17.810 --> 00:36:17.820 align:start position:0% that could cause that basically his 00:36:17.820 --> 00:36:20.570 align:start position:0% that could cause that basically his result<00:36:18.240> is<00:36:18.480> an<00:36:18.920> ineffectual<00:36:19.920> computation 00:36:20.570 --> 00:36:20.580 align:start position:0% result is an ineffectual computation 00:36:20.580 --> 00:36:22.130 align:start position:0% result is an ineffectual computation with<00:36:20.670> in<00:36:20.850> front<00:36:20.970> later<00:36:21.270> there's<00:36:21.840> nothing 00:36:22.130 --> 00:36:22.140 align:start position:0% with in front later there's nothing 00:36:22.140 --> 00:36:23.960 align:start position:0% with in front later there's nothing being<00:36:22.320> run<00:36:22.590> here<00:36:22.950> it's<00:36:23.160> just<00:36:23.460> setting<00:36:23.670> it<00:36:23.850> up 00:36:23.960 --> 00:36:23.970 align:start position:0% being run here it's just setting it up 00:36:23.970 --> 00:36:25.670 align:start position:0% being run here it's just setting it up so<00:36:24.240> there's<00:36:24.720> nothing<00:36:24.810> that<00:36:24.960> can<00:36:25.140> fail<00:36:25.290> here 00:36:25.670 --> 00:36:25.680 align:start position:0% so there's nothing that can fail here 00:36:25.680 --> 00:36:26.870 align:start position:0% so there's nothing that can fail here there's<00:36:26.010> nothing<00:36:26.280> that<00:36:26.400> can<00:36:26.490> fail<00:36:26.670> it<00:36:26.790> in 00:36:26.870 --> 00:36:26.880 align:start position:0% there's nothing that can fail it in 00:36:26.880 --> 00:36:29.690 align:start position:0% there's nothing that can fail it in these<00:36:27.030> lead<00:36:27.330> pipes<00:36:27.570> so<00:36:27.869> this<00:36:28.080> this<00:36:28.680> test<00:36:29.040> fails 00:36:29.690 --> 00:36:29.700 align:start position:0% these lead pipes so this this test fails 00:36:29.700 --> 00:36:31.700 align:start position:0% these lead pipes so this this test fails because<00:36:30.030> of<00:36:30.210> an<00:36:30.450> effectual<00:36:30.780> reason<00:36:31.170> I<00:36:31.410> know<00:36:31.530> it 00:36:31.700 --> 00:36:31.710 align:start position:0% because of an effectual reason I know it 00:36:31.710 --> 00:36:33.350 align:start position:0% because of an effectual reason I know it has<00:36:31.830> to<00:36:31.980> take<00:36:32.160> place<00:36:32.310> in<00:36:32.520> this<00:36:32.700> line<00:36:32.940> there's 00:36:33.350 --> 00:36:33.360 align:start position:0% has to take place in this line there's 00:36:33.360 --> 00:36:34.670 align:start position:0% has to take place in this line there's no<00:36:33.480> possible<00:36:33.869> way<00:36:33.930> that<00:36:34.020> it<00:36:34.230> can<00:36:34.350> do<00:36:34.440> anything 00:36:34.670 --> 00:36:34.680 align:start position:0% no possible way that it can do anything 00:36:34.680 --> 00:36:38.060 align:start position:0% no possible way that it can do anything else<00:36:34.860> so<00:36:35.990> it<00:36:36.990> is<00:36:37.140> I<00:36:37.380> don't<00:36:37.560> know<00:36:37.619> in<00:36:37.740> that<00:36:37.830> sense 00:36:38.060 --> 00:36:38.070 align:start position:0% else so it is I don't know in that sense 00:36:38.070 --> 00:36:40.790 align:start position:0% else so it is I don't know in that sense like<00:36:38.220> how<00:36:39.119> you<00:36:39.180> certainly<00:36:39.990> look<00:36:40.200> at<00:36:40.320> projects 00:36:40.790 --> 00:36:40.800 align:start position:0% like how you certainly look at projects 00:36:40.800 --> 00:36:43.640 align:start position:0% like how you certainly look at projects large<00:36:41.280> large<00:36:41.820> piles<00:36:42.480> of<00:36:42.720> code<00:36:42.930> where<00:36:43.350> many 00:36:43.640 --> 00:36:43.650 align:start position:0% large large piles of code where many 00:36:43.650 --> 00:36:45.560 align:start position:0% large large piles of code where many things<00:36:43.740> are<00:36:44.040> happening<00:36:44.460> it's<00:36:45.000> very<00:36:45.240> important 00:36:45.560 --> 00:36:45.570 align:start position:0% things are happening it's very important 00:36:45.570 --> 00:36:47.600 align:start position:0% things are happening it's very important to<00:36:45.660> basically<00:36:45.900> be<00:36:46.080> able<00:36:46.170> to<00:36:46.380> look<00:36:46.560> at<00:36:46.740> looking 00:36:47.600 --> 00:36:47.610 align:start position:0% to basically be able to look at looking 00:36:47.610 --> 00:36:50.450 align:start position:0% to basically be able to look at looking at<00:36:47.820> only<00:36:48.030> this<00:36:48.390> this<00:36:48.869> particular<00:36:49.500> block<00:36:49.980> I<00:36:50.250> can 00:36:50.450 --> 00:36:50.460 align:start position:0% at only this this particular block I can 00:36:50.460 --> 00:36:52.550 align:start position:0% at only this this particular block I can tell<00:36:50.670> that<00:36:50.700> the<00:36:51.210> only<00:36:51.360> way<00:36:51.570> this<00:36:51.630> can<00:36:51.990> fail<00:36:52.320> is 00:36:52.550 --> 00:36:52.560 align:start position:0% tell that the only way this can fail is 00:36:52.560 --> 00:36:59.390 align:start position:0% tell that the only way this can fail is this<00:36:52.830> one<00:36:53.160> this<00:36:54.090> one<00:36:54.480> right<00:36:55.080> here<00:36:56.750> so<00:36:58.340> what<00:36:59.340> do 00:36:59.390 --> 00:36:59.400 align:start position:0% this one this one right here so what do 00:36:59.400 --> 00:37:01.130 align:start position:0% this one this one right here so what do you<00:36:59.490> gain<00:36:59.700> the<00:37:00.060> analogy<00:37:00.480> here<00:37:00.510> is<00:37:00.690> that<00:37:00.930> like 00:37:01.130 --> 00:37:01.140 align:start position:0% you gain the analogy here is that like 00:37:01.140 --> 00:37:04.670 align:start position:0% you gain the analogy here is that like whatever<00:37:01.950> length<00:37:02.310> you<00:37:02.790> know<00:37:03.500> you<00:37:04.500> know<00:37:04.590> the 00:37:04.670 --> 00:37:04.680 align:start position:0% whatever length you know you know the 00:37:04.680 --> 00:37:06.140 align:start position:0% whatever length you know you know the Commodus<00:37:05.100> of<00:37:05.250> the<00:37:05.310> program<00:37:05.730> is<00:37:05.910> like<00:37:06.060> the 00:37:06.140 --> 00:37:06.150 align:start position:0% Commodus of the program is like the 00:37:06.150 --> 00:37:07.670 align:start position:0% Commodus of the program is like the types<00:37:06.390> are<00:37:06.600> another<00:37:06.960> program<00:37:07.320> which<00:37:07.440> is<00:37:07.560> to 00:37:07.670 --> 00:37:07.680 align:start position:0% types are another program which is to 00:37:07.680 --> 00:37:09.890 align:start position:0% types are another program which is to say<00:37:07.830> that<00:37:07.980> like<00:37:08.130> the<00:37:08.730> compiler<00:37:09.300> is<00:37:09.420> taking<00:37:09.750> and 00:37:09.890 --> 00:37:09.900 align:start position:0% say that like the compiler is taking and 00:37:09.900 --> 00:37:12.590 align:start position:0% say that like the compiler is taking and the<00:37:10.020> types<00:37:10.260> that<00:37:10.440> you're<00:37:10.710> giving<00:37:11.280> to<00:37:11.600> the 00:37:12.590 --> 00:37:12.600 align:start position:0% the types that you're giving to the 00:37:12.600 --> 00:37:13.910 align:start position:0% the types that you're giving to the program<00:37:12.930> that<00:37:13.050> you<00:37:13.140> are<00:37:13.200> writing<00:37:13.500> whether<00:37:13.740> you 00:37:13.910 --> 00:37:13.920 align:start position:0% program that you are writing whether you 00:37:13.920 --> 00:37:16.700 align:start position:0% program that you are writing whether you like<00:37:14.070> or<00:37:14.190> not<00:37:14.250> is<00:37:14.550> is<00:37:14.820> creating<00:37:15.330> it's<00:37:16.140> time<00:37:16.470> to 00:37:16.700 --> 00:37:16.710 align:start position:0% like or not is is creating it's time to 00:37:16.710 --> 00:37:18.020 align:start position:0% like or not is is creating it's time to like<00:37:16.920> the<00:37:17.040> language<00:37:17.250> you<00:37:17.609> don't<00:37:17.760> have<00:37:17.910> to 00:37:18.020 --> 00:37:18.030 align:start position:0% like the language you don't have to 00:37:18.030 --> 00:37:19.790 align:start position:0% like the language you don't have to probably<00:37:18.300> write<00:37:18.660> it<00:37:18.780> yourself<00:37:19.109> but<00:37:19.350> you<00:37:19.710> know 00:37:19.790 --> 00:37:19.800 align:start position:0% probably write it yourself but you know 00:37:19.800 --> 00:37:21.280 align:start position:0% probably write it yourself but you know I<00:37:19.830> always<00:37:20.010> have<00:37:20.190> to<00:37:20.280> annotate 00:37:21.280 --> 00:37:21.290 align:start position:0% I always have to annotate 00:37:21.290 --> 00:37:24.370 align:start position:0% I always have to annotate has<00:37:21.710> type<00:37:21.980> never<00:37:22.940> the<00:37:23.420> program<00:37:23.780> the<00:37:23.930> compiler 00:37:24.370 --> 00:37:24.380 align:start position:0% has type never the program the compiler 00:37:24.380 --> 00:37:25.840 align:start position:0% has type never the program the compiler is<00:37:24.500> able<00:37:24.710> to<00:37:24.800> figure<00:37:24.980> out<00:37:25.130> a<00:37:25.190> lot<00:37:25.370> of<00:37:25.430> that<00:37:25.580> for 00:37:25.840 --> 00:37:25.850 align:start position:0% is able to figure out a lot of that for 00:37:25.850 --> 00:37:28.830 align:start position:0% is able to figure out a lot of that for you<00:37:25.970> but<00:37:26.510> by<00:37:27.230> typing<00:37:28.040> the<00:37:28.160> language<00:37:28.490> itself 00:37:28.830 --> 00:37:28.840 align:start position:0% you but by typing the language itself 00:37:28.840 --> 00:37:32.730 align:start position:0% you but by typing the language itself the<00:37:29.840> compiler<00:37:30.260> is<00:37:30.380> able<00:37:30.560> to<00:37:30.650> operate<00:37:30.830> on<00:37:31.310> your 00:37:32.730 --> 00:37:32.740 align:start position:0% the compiler is able to operate on your 00:37:32.740 --> 00:37:35.710 align:start position:0% the compiler is able to operate on your on<00:37:33.740> a<00:37:33.800> newer<00:37:34.100> types<00:37:34.430> and<00:37:34.790> to<00:37:35.000> produce<00:37:35.180> like 00:37:35.710 --> 00:37:35.720 align:start position:0% on a newer types and to produce like 00:37:35.720 --> 00:37:37.720 align:start position:0% on a newer types and to produce like certain<00:37:36.200> guarantees<00:37:36.650> or<00:37:37.130> certain<00:37:37.370> things<00:37:37.550> in 00:37:37.720 --> 00:37:37.730 align:start position:0% certain guarantees or certain things in 00:37:37.730 --> 00:37:38.980 align:start position:0% certain guarantees or certain things in the<00:37:37.820> same<00:37:37.970> way<00:37:38.150> that<00:37:38.270> your<00:37:38.420> program<00:37:38.810> can 00:37:38.980 --> 00:37:38.990 align:start position:0% the same way that your program can 00:37:38.990 --> 00:37:41.080 align:start position:0% the same way that your program can operate<00:37:39.320> on<00:37:39.440> the<00:37:39.530> values<00:37:39.860> so<00:37:40.160> in<00:37:40.760> the<00:37:40.820> same<00:37:40.970> way 00:37:41.080 --> 00:37:41.090 align:start position:0% operate on the values so in the same way 00:37:41.090 --> 00:37:42.610 align:start position:0% operate on the values so in the same way that<00:37:41.180> your<00:37:41.300> program<00:37:41.630> manipulates<00:37:42.110> values<00:37:42.440> the 00:37:42.610 --> 00:37:42.620 align:start position:0% that your program manipulates values the 00:37:42.620 --> 00:37:44.770 align:start position:0% that your program manipulates values the compiler<00:37:43.460> here<00:37:43.670> is<00:37:43.760> like<00:37:43.970> basically<00:37:44.480> reading 00:37:44.770 --> 00:37:44.780 align:start position:0% compiler here is like basically reading 00:37:44.780 --> 00:37:46.630 align:start position:0% compiler here is like basically reading in<00:37:44.900> time<00:37:45.110> sitting<00:37:45.500> and<00:37:45.650> reasoning<00:37:46.550> about 00:37:46.630 --> 00:37:46.640 align:start position:0% in time sitting and reasoning about 00:37:46.640 --> 00:37:47.980 align:start position:0% in time sitting and reasoning about those<00:37:46.880> things<00:37:47.060> the<00:37:47.240> same<00:37:47.540> way<00:37:47.600> that<00:37:47.840> you 00:37:47.980 --> 00:37:47.990 align:start position:0% those things the same way that you 00:37:47.990 --> 00:37:50.320 align:start position:0% those things the same way that you reason<00:37:48.440> about<00:37:48.530> boolean<00:37:49.490> logic<00:37:49.640> or<00:37:50.060> whenever 00:37:50.320 --> 00:37:50.330 align:start position:0% reason about boolean logic or whenever 00:37:50.330 --> 00:37:51.640 align:start position:0% reason about boolean logic or whenever it's<00:37:50.570> there 00:37:51.640 --> 00:37:51.650 align:start position:0% it's there 00:37:51.650 --> 00:37:53.320 align:start position:0% it's there and<00:37:51.980> the<00:37:52.040> more<00:37:52.220> accurate<00:37:52.670> and<00:37:52.790> expressive 00:37:53.320 --> 00:37:53.330 align:start position:0% and the more accurate and expressive 00:37:53.330 --> 00:37:55.300 align:start position:0% and the more accurate and expressive that<00:37:53.480> your<00:37:53.630> types<00:37:53.870> are<00:37:54.110> the<00:37:54.530> more<00:37:54.710> working 00:37:55.300 --> 00:37:55.310 align:start position:0% that your types are the more working 00:37:55.310 --> 00:37:57.000 align:start position:0% that your types are the more working powder<00:37:55.520> can<00:37:55.790> do<00:37:55.940> three 00:37:57.000 --> 00:37:57.010 align:start position:0% powder can do three 00:37:57.010 --> 00:37:59.550 align:start position:0% powder can do three so<00:37:57.310> for<00:37:57.520> example<00:37:57.580> like<00:37:58.060> the<00:37:59.020> more<00:37:59.200> accurate 00:37:59.550 --> 00:37:59.560 align:start position:0% so for example like the more accurate 00:37:59.560 --> 00:38:00.900 align:start position:0% so for example like the more accurate that<00:37:59.590> your<00:37:59.859> types<00:38:00.070> are<00:38:00.310> presenting<00:38:00.760> like 00:38:00.900 --> 00:38:00.910 align:start position:0% that your types are presenting like 00:38:00.910 --> 00:38:02.460 align:start position:0% that your types are presenting like commit<00:38:01.210> things<00:38:01.420> can<00:38:01.660> throw<00:38:01.840> exceptions<00:38:01.990> in 00:38:02.460 --> 00:38:02.470 align:start position:0% commit things can throw exceptions in 00:38:02.470 --> 00:38:04.859 align:start position:0% commit things can throw exceptions in the<00:38:02.530> pecans<00:38:02.859> but<00:38:03.160> it<00:38:03.250> might<00:38:03.400> fail<00:38:03.869> the 00:38:04.859 --> 00:38:04.869 align:start position:0% the pecans but it might fail the 00:38:04.869 --> 00:38:07.380 align:start position:0% the pecans but it might fail the compiler<00:38:05.350> is<00:38:05.680> able<00:38:06.250> to<00:38:06.400> basically<00:38:06.670> like<00:38:07.060> tell 00:38:07.380 --> 00:38:07.390 align:start position:0% compiler is able to basically like tell 00:38:07.390 --> 00:38:08.940 align:start position:0% compiler is able to basically like tell you<00:38:07.570> more<00:38:07.810> more<00:38:08.050> about<00:38:08.350> the<00:38:08.470> possible<00:38:08.830> places 00:38:08.940 --> 00:38:08.950 align:start position:0% you more more about the possible places 00:38:08.950 --> 00:38:10.590 align:start position:0% you more more about the possible places where<00:38:09.340> your<00:38:09.430> programs<00:38:09.820> may<00:38:10.090> be<00:38:10.119> incorrectly 00:38:10.590 --> 00:38:10.600 align:start position:0% where your programs may be incorrectly 00:38:10.600 --> 00:38:13.260 align:start position:0% where your programs may be incorrectly written<00:38:10.780> or<00:38:11.080> where<00:38:11.260> it<00:38:11.350> might<00:38:11.440> fail<00:38:12.270> the 00:38:13.260 --> 00:38:13.270 align:start position:0% written or where it might fail the 00:38:13.270 --> 00:38:14.520 align:start position:0% written or where it might fail the downside<00:38:13.720> of<00:38:13.750> this<00:38:13.900> is<00:38:13.960> that<00:38:14.170> this<00:38:14.260> kind<00:38:14.470> of 00:38:14.520 --> 00:38:14.530 align:start position:0% downside of this is that this kind of 00:38:14.530 --> 00:38:16.140 align:start position:0% downside of this is that this kind of program<00:38:14.650> is<00:38:14.950> really<00:38:15.070> hard<00:38:15.340> but<00:38:16.000> it's 00:38:16.140 --> 00:38:16.150 align:start position:0% program is really hard but it's 00:38:16.150 --> 00:38:17.790 align:start position:0% program is really hard but it's different<00:38:16.390> than<00:38:16.630> it's<00:38:17.020> different<00:38:17.500> than<00:38:17.680> being 00:38:17.790 --> 00:38:17.800 align:start position:0% different than it's different than being 00:38:17.800 --> 00:38:19.230 align:start position:0% different than it's different than being really<00:38:18.100> hard<00:38:18.280> to<00:38:18.369> get<00:38:18.490> right<00:38:18.760> it's<00:38:19.060> really 00:38:19.230 --> 00:38:19.240 align:start position:0% really hard to get right it's really 00:38:19.240 --> 00:38:21.210 align:start position:0% really hard to get right it's really hard<00:38:19.450> to<00:38:19.540> learn<00:38:19.720> but<00:38:20.410> once<00:38:20.740> you<00:38:20.920> learn<00:38:21.160> that 00:38:21.210 --> 00:38:21.220 align:start position:0% hard to learn but once you learn that 00:38:21.220 --> 00:38:24.300 align:start position:0% hard to learn but once you learn that into<00:38:21.609> it<00:38:21.760> there<00:38:22.030> is<00:38:22.210> not<00:38:22.510> really<00:38:22.740> if<00:38:23.740> the<00:38:24.190> kind 00:38:24.300 --> 00:38:24.310 align:start position:0% into it there is not really if the kind 00:38:24.310 --> 00:38:25.980 align:start position:0% into it there is not really if the kind of<00:38:24.400> thing<00:38:24.609> that<00:38:24.640> you<00:38:24.820> can't<00:38:25.090> it's<00:38:25.600> very 00:38:25.980 --> 00:38:25.990 align:start position:0% of thing that you can't it's very 00:38:25.990 --> 00:38:27.510 align:start position:0% of thing that you can't it's very difficult<00:38:26.350> to<00:38:26.530> implement<00:38:26.680> a<00:38:27.220> program 00:38:27.510 --> 00:38:27.520 align:start position:0% difficult to implement a program 00:38:27.520 --> 00:38:29.490 align:start position:0% difficult to implement a program improperly<00:38:28.480> in<00:38:28.660> this<00:38:28.810> language<00:38:28.990> it's<00:38:29.260> like 00:38:29.490 --> 00:38:29.500 align:start position:0% improperly in this language it's like 00:38:29.500 --> 00:38:32.130 align:start position:0% improperly in this language it's like you<00:38:29.619> have<00:38:29.940> to<00:38:30.940> talk<00:38:31.150> about<00:38:31.180> a<00:38:31.690> school 00:38:32.130 --> 00:38:32.140 align:start position:0% you have to talk about a school 00:38:32.140 --> 00:38:34.170 align:start position:0% you have to talk about a school especially<00:38:32.500> like<00:38:33.040> other<00:38:33.310> person<00:38:33.609> or<00:38:33.760> a<00:38:33.820> school 00:38:34.170 --> 00:38:34.180 align:start position:0% especially like other person or a school 00:38:34.180 --> 00:38:36.180 align:start position:0% especially like other person or a school program<00:38:35.080> by<00:38:35.380> the<00:38:35.470> time<00:38:35.650> I<00:38:35.680> figured<00:38:35.890> out<00:38:36.010> how<00:38:36.160> to 00:38:36.180 --> 00:38:36.190 align:start position:0% program by the time I figured out how to 00:38:36.190 --> 00:38:37.890 align:start position:0% program by the time I figured out how to get<00:38:36.310> us<00:38:36.430> here<00:38:36.550> a<00:38:36.609> while<00:38:36.790> like<00:38:37.060> a<00:38:37.090> few<00:38:37.180> months 00:38:37.890 --> 00:38:37.900 align:start position:0% get us here a while like a few months 00:38:37.900 --> 00:38:40.080 align:start position:0% get us here a while like a few months later<00:38:38.200> you<00:38:38.920> just<00:38:39.100> work<00:38:39.340> the<00:38:39.490> first<00:38:39.700> time<00:38:39.790> there 00:38:40.080 --> 00:38:40.090 align:start position:0% later you just work the first time there 00:38:40.090 --> 00:38:42.000 align:start position:0% later you just work the first time there was<00:38:40.119> no<00:38:40.359> like<00:38:40.660> there<00:38:41.109> was<00:38:41.200> no<00:38:41.290> again<00:38:41.530> at<00:38:41.619> s2 00:38:42.000 --> 00:38:42.010 align:start position:0% was no like there was no again at s2 00:38:42.010 --> 00:38:42.359 align:start position:0% was no like there was no again at s2 support 00:38:42.359 --> 00:38:42.369 align:start position:0% support 00:38:42.369 --> 00:38:44.460 align:start position:0% support it's<00:38:43.030> because<00:38:43.300> like<00:38:43.510> it's<00:38:43.630> actually<00:38:43.780> somewhat 00:38:44.460 --> 00:38:44.470 align:start position:0% it's because like it's actually somewhat 00:38:44.470 --> 00:38:45.990 align:start position:0% it's because like it's actually somewhat well<00:38:44.770> somewhat<00:38:45.100> difficult<00:38:45.280> to<00:38:45.640> express 00:38:45.990 --> 00:38:46.000 align:start position:0% well somewhat difficult to express 00:38:46.000 --> 00:38:48.030 align:start position:0% well somewhat difficult to express programmers<00:38:46.570> in<00:38:46.690> these<00:38:46.840> languages<00:38:47.290> there<00:38:48.010> is 00:38:48.030 --> 00:38:48.040 align:start position:0% programmers in these languages there is 00:38:48.040 --> 00:38:50.580 align:start position:0% programmers in these languages there is it's<00:38:48.820> difficult<00:38:49.390> to<00:38:49.540> get<00:38:50.020> a<00:38:50.080> program<00:38:50.350> to 00:38:50.580 --> 00:38:50.590 align:start position:0% it's difficult to get a program to 00:38:50.590 --> 00:38:52.290 align:start position:0% it's difficult to get a program to compile<00:38:50.980> that<00:38:51.130> doesn't<00:38:51.580> do<00:38:51.730> the<00:38:51.850> same<00:38:52.000> thing 00:38:52.290 --> 00:38:52.300 align:start position:0% compile that doesn't do the same thing 00:38:52.300 --> 00:38:54.060 align:start position:0% compile that doesn't do the same thing as<00:38:52.420> and<00:38:52.900> when<00:38:53.290> it<00:38:53.320> does<00:38:53.590> is<00:38:53.859> something 00:38:54.060 --> 00:38:54.070 align:start position:0% as and when it does is something 00:38:54.070 --> 00:38:56.400 align:start position:0% as and when it does is something actually<00:38:54.369> it's<00:38:54.700> it's<00:38:55.600> interesting<00:38:56.050> because 00:38:56.400 --> 00:38:56.410 align:start position:0% actually it's it's interesting because 00:38:56.410 --> 00:38:58.620 align:start position:0% actually it's it's interesting because it's<00:38:56.830> somehow<00:38:57.100> like<00:38:57.250> done<00:38:57.700> in<00:38:58.180> some<00:38:58.390> sense 00:38:58.620 --> 00:38:58.630 align:start position:0% it's somehow like done in some sense 00:38:58.630 --> 00:39:00.980 align:start position:0% it's somehow like done in some sense like<00:38:58.869> they're<00:38:59.080> supposed<00:38:59.350> to<00:38:59.380> be<00:38:59.500> impossible 00:39:00.980 --> 00:39:00.990 align:start position:0% like they're supposed to be impossible 00:39:00.990 --> 00:39:03.300 align:start position:0% like they're supposed to be impossible so<00:39:01.990> they<00:39:02.109> do<00:39:02.170> you<00:39:02.320> think<00:39:02.500> you<00:39:02.830> know<00:39:02.920> parts<00:39:03.220> of 00:39:03.300 --> 00:39:03.310 align:start position:0% so they do you think you know parts of 00:39:03.310 --> 00:39:04.950 align:start position:0% so they do you think you know parts of this<00:39:03.369> library<00:39:03.850> which<00:39:04.060> I<00:39:04.210> like<00:39:04.390> the<00:39:04.420> couch<00:39:04.720> or 00:39:04.950 --> 00:39:04.960 align:start position:0% this library which I like the couch or 00:39:04.960 --> 00:39:07.170 align:start position:0% this library which I like the couch or whatever<00:39:05.200> is<00:39:05.470> like<00:39:05.710> whatever<00:39:06.310> like<00:39:06.760> the<00:39:07.060> way 00:39:07.170 --> 00:39:07.180 align:start position:0% whatever is like whatever like the way 00:39:07.180 --> 00:39:09.300 align:start position:0% whatever is like whatever like the way that<00:39:07.330> it<00:39:07.420> does<00:39:07.570> you<00:39:07.990> know<00:39:08.109> the<00:39:08.950> way<00:39:09.070> that<00:39:09.190> it 00:39:09.300 --> 00:39:09.310 align:start position:0% that it does you know the way that it 00:39:09.310 --> 00:39:11.070 align:start position:0% that it does you know the way that it does<00:39:09.430> the<00:39:09.580> parsing<00:39:10.000> and<00:39:10.150> what<00:39:10.480> in<00:39:10.660> gave<00:39:10.960> me<00:39:10.990> I 00:39:11.070 --> 00:39:11.080 align:start position:0% does the parsing and what in gave me I 00:39:11.080 --> 00:39:12.510 align:start position:0% does the parsing and what in gave me I you<00:39:11.500> know 00:39:12.510 --> 00:39:12.520 align:start position:0% you know 00:39:12.520 --> 00:39:14.620 align:start position:0% you know decoding<00:39:13.520> stuff<00:39:13.790> looks<00:39:13.940> like<00:39:14.000> pretty<00:39:14.300> bullet 00:39:14.620 --> 00:39:14.630 align:start position:0% decoding stuff looks like pretty bullet 00:39:14.630 --> 00:39:16.570 align:start position:0% decoding stuff looks like pretty bullet through<00:39:14.840> this<00:39:14.900> ice<00:39:15.350> it's<00:39:15.650> like<00:39:15.860> easy<00:39:16.130> to<00:39:16.280> do<00:39:16.460> it 00:39:16.570 --> 00:39:16.580 align:start position:0% through this ice it's like easy to do it 00:39:16.580 --> 00:39:18.490 align:start position:0% through this ice it's like easy to do it all<00:39:16.700> this<00:39:16.790> is<00:39:16.970> correct<00:39:17.360> so<00:39:17.660> I<00:39:17.930> didn't<00:39:18.290> spend 00:39:18.490 --> 00:39:18.500 align:start position:0% all this is correct so I didn't spend 00:39:18.500 --> 00:39:20.890 align:start position:0% all this is correct so I didn't spend six<00:39:18.800> months<00:39:18.890> reading<00:39:19.400> test<00:39:19.730> me<00:39:19.880> stuff<00:39:20.150> I<00:39:20.420> spent 00:39:20.890 --> 00:39:20.900 align:start position:0% six months reading test me stuff I spent 00:39:20.900 --> 00:39:23.080 align:start position:0% six months reading test me stuff I spent like<00:39:21.080> a<00:39:21.110> month<00:39:21.200> writing<00:39:21.830> it<00:39:21.980> and<00:39:22.400> then<00:39:22.730> it<00:39:22.940> just 00:39:23.080 --> 00:39:23.090 align:start position:0% like a month writing it and then it just 00:39:23.090 --> 00:39:27.300 align:start position:0% like a month writing it and then it just like<00:39:23.890> really 00:39:27.300 --> 00:39:27.310 align:start position:0% 00:39:27.310 --> 00:39:29.730 align:start position:0% the<00:39:27.790> thing<00:39:28.600> which<00:39:28.780> I<00:39:28.900> would<00:39:29.050> say<00:39:29.200> is<00:39:29.530> like<00:39:29.560> the 00:39:29.730 --> 00:39:29.740 align:start position:0% the thing which I would say is like the 00:39:29.740 --> 00:39:32.430 align:start position:0% the thing which I would say is like the most<00:39:30.100> interesting<00:39:30.550> thing<00:39:30.760> is<00:39:31.210> probably<00:39:32.080> the 00:39:32.430 --> 00:39:32.440 align:start position:0% most interesting thing is probably the 00:39:32.440 --> 00:39:34.020 align:start position:0% most interesting thing is probably the way<00:39:32.530> that<00:39:32.560> it<00:39:32.800> doesn't<00:39:33.070> slang<00:39:33.250> tranio<00:39:33.790> so 00:39:34.020 --> 00:39:34.030 align:start position:0% way that it doesn't slang tranio so 00:39:34.030 --> 00:39:36.750 align:start position:0% way that it doesn't slang tranio so there's<00:39:34.210> like<00:39:34.360> immune<00:39:34.690> here<00:39:35.130> forever<00:39:36.130> I<00:39:36.370> think 00:39:36.750 --> 00:39:36.760 align:start position:0% there's like immune here forever I think 00:39:36.760 --> 00:39:37.980 align:start position:0% there's like immune here forever I think I<00:39:36.820> would<00:39:36.940> say<00:39:37.060> Q<00:39:37.240> is<00:39:37.300> probably<00:39:37.690> the<00:39:37.810> most 00:39:37.980 --> 00:39:37.990 align:start position:0% I would say Q is probably the most 00:39:37.990 --> 00:39:43.500 align:start position:0% I would say Q is probably the most interesting<00:39:38.200> feature<00:39:38.680> that<00:39:38.830> this<00:39:39.070> has<00:39:42.510> is 00:39:43.500 --> 00:39:43.510 align:start position:0% interesting feature that this has is 00:39:43.510 --> 00:39:44.870 align:start position:0% interesting feature that this has is something<00:39:43.720> that's<00:39:44.050> his<00:39:44.200> problem 00:39:44.870 --> 00:39:44.880 align:start position:0% something that's his problem 00:39:44.880 --> 00:39:47.880 align:start position:0% something that's his problem like<00:39:45.880> the<00:39:46.290> filtering<00:39:47.290> or<00:39:47.440> something<00:39:47.770> which 00:39:47.880 --> 00:39:47.890 align:start position:0% like the filtering or something which 00:39:47.890 --> 00:39:51.090 align:start position:0% like the filtering or something which it's<00:39:48.070> like<00:39:48.220> basically<00:39:48.700> a<00:39:48.820> weighted<00:39:49.270> as<00:39:50.100> the 00:39:51.090 --> 00:39:51.100 align:start position:0% it's like basically a weighted as the 00:39:51.100 --> 00:39:53.760 align:start position:0% it's like basically a weighted as the theory<00:39:51.340> of<00:39:51.430> logs<00:39:51.760> in<00:39:52.300> a<00:39:52.930> particular<00:39:53.410> order 00:39:53.760 --> 00:39:53.770 align:start position:0% theory of logs in a particular order 00:39:53.770 --> 00:39:56.340 align:start position:0% theory of logs in a particular order that<00:39:53.800> she<00:39:54.100> went<00:39:54.250> to<00:39:54.340> specify<00:39:54.850> I<00:39:55.120> just<00:39:56.080> still 00:39:56.340 --> 00:39:56.350 align:start position:0% that she went to specify I just still 00:39:56.350 --> 00:39:58.080 align:start position:0% that she went to specify I just still left<00:39:56.470> with<00:39:56.560> the<00:39:56.740> remaining<00:39:56.980> time<00:39:57.250> before<00:39:57.850> we 00:39:58.080 --> 00:39:58.090 align:start position:0% left with the remaining time before we 00:39:58.090 --> 00:40:00.090 align:start position:0% left with the remaining time before we have<00:39:58.180> two<00:39:58.450> questions<00:39:59.410> whenever<00:39:59.680> I<00:39:59.770> would<00:39:59.890> just 00:40:00.090 --> 00:40:00.100 align:start position:0% have two questions whenever I would just 00:40:00.100 --> 00:40:02.220 align:start position:0% have two questions whenever I would just specify<00:40:00.520> like<00:40:00.700> what<00:40:00.880> that<00:40:01.030> means<00:40:01.240> so<00:40:01.480> the 00:40:02.220 --> 00:40:02.230 align:start position:0% specify like what that means so the 00:40:02.230 --> 00:40:03.540 align:start position:0% specify like what that means so the theory<00:40:02.440> of<00:40:02.500> logs<00:40:02.740> if<00:40:02.980> you<00:40:03.040> don't<00:40:03.220> know<00:40:03.370> or 00:40:03.540 --> 00:40:03.550 align:start position:0% theory of logs if you don't know or 00:40:03.550 --> 00:40:05.430 align:start position:0% theory of logs if you don't know or basically<00:40:03.850> the<00:40:03.940> way<00:40:04.210> that<00:40:04.240> it's<00:40:04.810> a<00:40:04.900> mechanism 00:40:05.430 --> 00:40:05.440 align:start position:0% basically the way that it's a mechanism 00:40:05.440 --> 00:40:07.950 align:start position:0% basically the way that it's a mechanism for<00:40:05.710> applications<00:40:06.430> of<00:40:06.580> updates<00:40:07.210> to<00:40:07.330> track 00:40:07.950 --> 00:40:07.960 align:start position:0% for applications of updates to track 00:40:07.960 --> 00:40:10.800 align:start position:0% for applications of updates to track state<00:40:08.200> so<00:40:08.410> the<00:40:08.590> contracts<00:40:09.400> change<00:40:09.730> you<00:40:10.720> don't 00:40:10.800 --> 00:40:10.810 align:start position:0% state so the contracts change you don't 00:40:10.810 --> 00:40:12.630 align:start position:0% state so the contracts change you don't always<00:40:10.990> know<00:40:11.320> unless<00:40:11.770> there's<00:40:12.010> an<00:40:12.220> ending 00:40:12.630 --> 00:40:12.640 align:start position:0% always know unless there's an ending 00:40:12.640 --> 00:40:14.820 align:start position:0% always know unless there's an ending inspired<00:40:13.060> to<00:40:13.270> it<00:40:13.420> telling<00:40:14.050> you<00:40:14.170> to<00:40:14.320> go<00:40:14.470> back<00:40:14.650> in 00:40:14.820 --> 00:40:14.830 align:start position:0% inspired to it telling you to go back in 00:40:14.830 --> 00:40:18.090 align:start position:0% inspired to it telling you to go back in to<00:40:15.540> possibly<00:40:16.540> just<00:40:16.690> assume<00:40:17.080> the<00:40:17.320> log<00:40:17.920> itself 00:40:18.090 --> 00:40:18.100 align:start position:0% to possibly just assume the log itself 00:40:18.100 --> 00:40:19.980 align:start position:0% to possibly just assume the log itself to<00:40:18.610> get<00:40:18.790> all<00:40:19.060> the<00:40:19.180> information<00:40:19.360> you<00:40:19.660> want<00:40:19.780> you 00:40:19.980 --> 00:40:19.990 align:start position:0% to get all the information you want you 00:40:19.990 --> 00:40:21.810 align:start position:0% to get all the information you want you know<00:40:20.110> and<00:40:20.710> these<00:40:20.860> are<00:40:20.980> consumed<00:40:21.280> by<00:40:21.310> some<00:40:21.580> kind 00:40:21.810 --> 00:40:21.820 align:start position:0% know and these are consumed by some kind 00:40:21.820 --> 00:40:23.550 align:start position:0% know and these are consumed by some kind of<00:40:21.910> fights<00:40:22.120> I<00:40:22.330> mean<00:40:22.450> color<00:40:22.600> filter<00:40:23.050> like<00:40:23.320> a<00:40:23.410> web 00:40:23.550 --> 00:40:23.560 align:start position:0% of fights I mean color filter like a web 00:40:23.560 --> 00:40:25.590 align:start position:0% of fights I mean color filter like a web three<00:40:23.830> filter<00:40:24.190> it's<00:40:24.730> a<00:40:24.790> diagram<00:40:25.210> about<00:40:25.480> how 00:40:25.590 --> 00:40:25.600 align:start position:0% three filter it's a diagram about how 00:40:25.600 --> 00:40:27.080 align:start position:0% three filter it's a diagram about how this<00:40:25.780> works 00:40:27.080 --> 00:40:27.090 align:start position:0% this works 00:40:27.090 --> 00:40:31.430 align:start position:0% this works took<00:40:27.930> me<00:40:28.050> forever<00:40:28.200> to<00:40:28.440> make<00:40:28.670> and<00:40:30.140> so<00:40:31.140> like<00:40:31.320> the 00:40:31.430 --> 00:40:31.440 align:start position:0% took me forever to make and so like the 00:40:31.440 --> 00:40:32.870 align:start position:0% took me forever to make and so like the problem<00:40:31.830> statement<00:40:32.070> for<00:40:32.340> like<00:40:32.460> this<00:40:32.580> multi 00:40:32.870 --> 00:40:32.880 align:start position:0% problem statement for like this multi 00:40:32.880 --> 00:40:34.250 align:start position:0% problem statement for like this multi filter<00:40:33.150> thing<00:40:33.360> for<00:40:33.510> example<00:40:33.810> is<00:40:33.900> like<00:40:34.050> you 00:40:34.250 --> 00:40:34.260 align:start position:0% filter thing for example is like you 00:40:34.260 --> 00:40:35.570 align:start position:0% filter thing for example is like you want<00:40:34.440> to<00:40:34.500> listen<00:40:34.650> to<00:40:34.800> like<00:40:35.070> you<00:40:35.370> want<00:40:35.460> to 00:40:35.570 --> 00:40:35.580 align:start position:0% want to listen to like you want to 00:40:35.580 --> 00:40:37.580 align:start position:0% want to listen to like you want to listen<00:40:35.700> to<00:40:35.850> multiple<00:40:36.330> events<00:40:36.690> each<00:40:37.230> one<00:40:37.500> of 00:40:37.580 --> 00:40:37.590 align:start position:0% listen to multiple events each one of 00:40:37.590 --> 00:40:38.590 align:start position:0% listen to multiple events each one of them<00:40:37.710> coming 00:40:38.590 --> 00:40:38.600 align:start position:0% them coming 00:40:38.600 --> 00:40:42.020 align:start position:0% them coming Traxxas<00:40:39.600> is<00:40:39.750> very<00:40:40.400> common<00:40:41.400> because<00:40:41.550> you<00:40:41.880> have 00:40:42.020 --> 00:40:42.030 align:start position:0% Traxxas is very common because you have 00:40:42.030 --> 00:40:44.270 align:start position:0% Traxxas is very common because you have multiple<00:40:42.390> though<00:40:42.900> two<00:40:42.960> separate<00:40:43.680> concerns 00:40:44.270 --> 00:40:44.280 align:start position:0% multiple though two separate concerns 00:40:44.280 --> 00:40:45.230 align:start position:0% multiple though two separate concerns you<00:40:44.460> write<00:40:44.610> in<00:40:44.760> multiple<00:40:45.119> different 00:40:45.230 --> 00:40:45.240 align:start position:0% you write in multiple different 00:40:45.240 --> 00:40:46.760 align:start position:0% you write in multiple different contracts<00:40:45.810> you<00:40:45.900> don't<00:40:46.080> have<00:40:46.170> just<00:40:46.260> one<00:40:46.350> giant 00:40:46.760 --> 00:40:46.770 align:start position:0% contracts you don't have just one giant 00:40:46.770 --> 00:40:48.260 align:start position:0% contracts you don't have just one giant contract<00:40:47.250> each<00:40:47.670> one<00:40:47.850> of<00:40:47.940> these<00:40:48.030> things 00:40:48.260 --> 00:40:48.270 align:start position:0% contract each one of these things 00:40:48.270 --> 00:40:49.910 align:start position:0% contract each one of these things submitting<00:40:48.810> different<00:40:49.530> kinds<00:40:49.680> of<00:40:49.770> events 00:40:49.910 --> 00:40:49.920 align:start position:0% submitting different kinds of events 00:40:49.920 --> 00:40:51.890 align:start position:0% submitting different kinds of events from<00:40:50.160> different<00:40:50.460> addresses<00:40:50.850> and<00:40:51.210> you<00:40:51.240> want<00:40:51.810> to 00:40:51.890 --> 00:40:51.900 align:start position:0% from different addresses and you want to 00:40:51.900 --> 00:40:53.570 align:start position:0% from different addresses and you want to define<00:40:52.200> specific<00:40:52.740> handlers<00:40:53.160> that<00:40:53.190> run 00:40:53.570 --> 00:40:53.580 align:start position:0% define specific handlers that run 00:40:53.580 --> 00:40:56.450 align:start position:0% define specific handlers that run against<00:40:53.850> you<00:40:54.060> submit<00:40:54.420> type<00:40:54.660> this<00:40:55.020> is<00:40:55.340> you<00:40:56.340> know 00:40:56.450 --> 00:40:56.460 align:start position:0% against you submit type this is you know 00:40:56.460 --> 00:40:58.220 align:start position:0% against you submit type this is you know most<00:40:56.820> common<00:40:57.270> in<00:40:57.390> some<00:40:57.630> cases<00:40:57.840> when<00:40:58.140> you're 00:40:58.220 --> 00:40:58.230 align:start position:0% most common in some cases when you're 00:40:58.230 --> 00:41:00.740 align:start position:0% most common in some cases when you're just<00:40:58.380> trying<00:40:58.619> to<00:40:58.710> store<00:40:59.040> them<00:40:59.220> cash<00:41:00.090> later<00:41:00.540> but 00:41:00.740 --> 00:41:00.750 align:start position:0% just trying to store them cash later but 00:41:00.750 --> 00:41:02.870 align:start position:0% just trying to store them cash later but it<00:41:00.840> also<00:41:00.990> might<00:41:01.320> you<00:41:01.980> know<00:41:02.070> whatever<00:41:02.310> it<00:41:02.550> might 00:41:02.870 --> 00:41:02.880 align:start position:0% it also might you know whatever it might 00:41:02.880 --> 00:41:05.750 align:start position:0% it also might you know whatever it might update<00:41:03.090> UI<00:41:03.420> examples<00:41:04.250> and<00:41:05.250> every<00:41:05.520> time<00:41:05.730> that 00:41:05.750 --> 00:41:05.760 align:start position:0% update UI examples and every time that 00:41:05.760 --> 00:41:07.880 align:start position:0% update UI examples and every time that you<00:41:06.119> you<00:41:06.360> want<00:41:06.750> to<00:41:06.810> run<00:41:06.930> each<00:41:07.050> handler<00:41:07.380> or<00:41:07.470> its 00:41:07.880 --> 00:41:07.890 align:start position:0% you you want to run each handler or its 00:41:07.890 --> 00:41:17.359 align:start position:0% you you want to run each handler or its event<00:41:08.220> in<00:41:08.700> the<00:41:08.970> event<00:41:15.110> so<00:41:16.110> like<00:41:16.260> contracts<00:41:16.740> you 00:41:17.359 --> 00:41:17.369 align:start position:0% event in the event so like contracts you 00:41:17.369 --> 00:41:19.190 align:start position:0% event in the event so like contracts you know<00:41:17.400> calling<00:41:17.940> if<00:41:18.150> I<00:41:18.270> have<00:41:18.450> one<00:41:18.630> contracted 00:41:19.190 --> 00:41:19.200 align:start position:0% know calling if I have one contracted 00:41:19.200 --> 00:41:20.900 align:start position:0% know calling if I have one contracted innocent<00:41:19.590> men<00:41:19.800> to<00:41:19.950> this<00:41:20.040> very<00:41:20.340> before<00:41:20.760> its 00:41:20.900 --> 00:41:20.910 align:start position:0% innocent men to this very before its 00:41:20.910 --> 00:41:22.040 align:start position:0% innocent men to this very before its return<00:41:21.210> statement 00:41:22.040 --> 00:41:22.050 align:start position:0% return statement 00:41:22.050 --> 00:41:25.160 align:start position:0% return statement makes<00:41:22.260> a<00:41:22.380> call<00:41:22.619> somewhere<00:41:23.100> in<00:41:23.220> his<00:41:23.310> body<00:41:24.170> which 00:41:25.160 --> 00:41:25.170 align:start position:0% makes a call somewhere in his body which 00:41:25.170 --> 00:41:26.900 align:start position:0% makes a call somewhere in his body which causes<00:41:25.560> another<00:41:25.800> event<00:41:26.070> to<00:41:26.130> fire<00:41:26.369> then<00:41:26.670> like<00:41:26.820> I 00:41:26.900 --> 00:41:26.910 align:start position:0% causes another event to fire then like I 00:41:26.910 --> 00:41:28.520 align:start position:0% causes another event to fire then like I want<00:41:27.150> to<00:41:27.210> resolve<00:41:27.480> these<00:41:27.660> things<00:41:27.720> in<00:41:28.260> the 00:41:28.520 --> 00:41:28.530 align:start position:0% want to resolve these things in the 00:41:28.530 --> 00:41:30.109 align:start position:0% want to resolve these things in the order<00:41:28.830> that<00:41:28.860> they<00:41:29.160> came<00:41:29.400> out<00:41:29.460> and<00:41:29.880> basically 00:41:30.109 --> 00:41:30.119 align:start position:0% order that they came out and basically 00:41:30.119 --> 00:41:32.600 align:start position:0% order that they came out and basically like<00:41:30.360> a<00:41:30.420> block<00:41:31.010> and<00:41:32.010> so<00:41:32.160> the<00:41:32.250> use<00:41:32.400> case<00:41:32.430> for 00:41:32.600 --> 00:41:32.610 align:start position:0% like a block and so the use case for 00:41:32.610 --> 00:41:33.890 align:start position:0% like a block and so the use case for this<00:41:32.850> which<00:41:33.030> we<00:41:33.180> have<00:41:33.330> there's<00:41:33.570> probably<00:41:33.780> lots 00:41:33.890 --> 00:41:33.900 align:start position:0% this which we have there's probably lots 00:41:33.900 --> 00:41:36.350 align:start position:0% this which we have there's probably lots of<00:41:34.020> other<00:41:34.110> people<00:41:34.440> have<00:41:34.590> is<00:41:34.950> that<00:41:35.640> you're 00:41:36.350 --> 00:41:36.360 align:start position:0% of other people have is that you're 00:41:36.360 --> 00:41:37.850 align:start position:0% of other people have is that you're building<00:41:36.480> in<00:41:36.720> cash<00:41:36.900> for<00:41:37.230> contract<00:41:37.650> state 00:41:37.850 --> 00:41:37.860 align:start position:0% building in cash for contract state 00:41:37.860 --> 00:41:40.040 align:start position:0% building in cash for contract state which<00:41:38.130> is<00:41:38.280> updated<00:41:38.550> or<00:41:38.970> revalidated<00:41:39.690> whenever 00:41:40.040 --> 00:41:40.050 align:start position:0% which is updated or revalidated whenever 00:41:40.050 --> 00:41:42.800 align:start position:0% which is updated or revalidated whenever certain<00:41:40.350> times<00:41:40.530> fire<00:41:40.740> so<00:41:41.630> because<00:41:42.630> you<00:41:42.780> want 00:41:42.800 --> 00:41:42.810 align:start position:0% certain times fire so because you want 00:41:42.810 --> 00:41:44.660 align:start position:0% certain times fire so because you want to<00:41:43.050> want<00:41:43.530> to<00:41:43.560> use<00:41:43.710> this<00:41:43.859> your<00:41:44.010> packet<00:41:44.369> you<00:41:44.400> want 00:41:44.660 --> 00:41:44.670 align:start position:0% to want to use this your packet you want 00:41:44.670 --> 00:41:46.910 align:start position:0% to want to use this your packet you want to<00:41:44.730> use<00:41:44.850> like<00:41:45.000> a<00:41:45.060> relational<00:41:45.540> database<00:41:45.920> but 00:41:46.910 --> 00:41:46.920 align:start position:0% to use like a relational database but 00:41:46.920 --> 00:41:49.190 align:start position:0% to use like a relational database but you<00:41:47.730> know<00:41:47.820> you<00:41:47.880> don't<00:41:48.180> use<00:41:48.390> like<00:41:48.600> the<00:41:48.750> EPM<00:41:49.050> as 00:41:49.190 --> 00:41:49.200 align:start position:0% you know you don't use like the EPM as 00:41:49.200 --> 00:41:53.120 align:start position:0% you know you don't use like the EPM as your<00:41:49.320> back<00:41:49.470> in<00:41:49.680> here<00:41:49.859> whenever<00:41:52.100> there<00:41:53.100> are 00:41:53.120 --> 00:41:53.130 align:start position:0% your back in here whenever there are 00:41:53.130 --> 00:41:54.650 align:start position:0% your back in here whenever there are dependencies<00:41:53.460> in<00:41:53.970> your<00:41:54.090> events<00:41:54.420> for<00:41:54.630> example 00:41:54.650 --> 00:41:54.660 align:start position:0% dependencies in your events for example 00:41:54.660 --> 00:41:57.260 align:start position:0% dependencies in your events for example like<00:41:55.140> to<00:41:55.260> the<00:41:55.410> empty<00:41:55.740> market<00:41:56.160> contract<00:41:56.700> either 00:41:57.260 --> 00:41:57.270 align:start position:0% like to the empty market contract either 00:41:57.270 --> 00:41:59.150 align:start position:0% like to the empty market contract either get<00:41:57.600> token<00:41:57.780> listed<00:41:58.260> for<00:41:58.440> sale<00:41:58.619> event<00:41:58.980> that 00:41:59.150 --> 00:41:59.160 align:start position:0% get token listed for sale event that 00:41:59.160 --> 00:42:00.890 align:start position:0% get token listed for sale event that indicates<00:41:59.580> like<00:41:59.850> others<00:42:00.119> a<00:42:00.150> new<00:42:00.330> token<00:42:00.540> I<00:42:00.720> can 00:42:00.890 --> 00:42:00.900 align:start position:0% indicates like others a new token I can 00:42:00.900 --> 00:42:03.290 align:start position:0% indicates like others a new token I can buy<00:42:01.050> but<00:42:01.710> that<00:42:02.010> token<00:42:02.400> itself<00:42:02.700> refers<00:42:03.000> to<00:42:03.030> a 00:42:03.290 --> 00:42:03.300 align:start position:0% buy but that token itself refers to a 00:42:03.300 --> 00:42:06.440 align:start position:0% buy but that token itself refers to a token<00:42:03.660> ID<00:42:03.810> and<00:42:04.560> that<00:42:04.710> token<00:42:05.010> ID<00:42:05.160> is<00:42:05.609> you<00:42:06.330> would 00:42:06.440 --> 00:42:06.450 align:start position:0% token ID and that token ID is you would 00:42:06.450 --> 00:42:08.010 align:start position:0% token ID and that token ID is you would only<00:42:06.600> know<00:42:06.869> that<00:42:07.050> that<00:42:07.200> token<00:42:07.560> exists 00:42:08.010 --> 00:42:08.020 align:start position:0% only know that that token exists 00:42:08.020 --> 00:42:12.510 align:start position:0% only know that that token exists if<00:42:09.060> the<00:42:10.060> evented<00:42:10.540> like<00:42:10.750> mint<00:42:11.140> new<00:42:11.770> token<00:42:12.160> event 00:42:12.510 --> 00:42:12.520 align:start position:0% if the evented like mint new token event 00:42:12.520 --> 00:42:14.610 align:start position:0% if the evented like mint new token event from<00:42:12.790> the<00:42:12.940> NFT<00:42:13.210> contract<00:42:13.870> itself<00:42:14.140> and<00:42:14.410> fired 00:42:14.610 --> 00:42:14.620 align:start position:0% from the NFT contract itself and fired 00:42:14.620 --> 00:42:16.320 align:start position:0% from the NFT contract itself and fired at<00:42:14.830> some<00:42:15.010> cakes<00:42:15.250> like<00:42:15.610> there's<00:42:16.030> kind<00:42:16.150> of<00:42:16.240> like 00:42:16.320 --> 00:42:16.330 align:start position:0% at some cakes like there's kind of like 00:42:16.330 --> 00:42:18.810 align:start position:0% at some cakes like there's kind of like there's<00:42:17.080> all<00:42:17.200> the<00:42:17.350> good<00:42:17.500> actions<00:42:17.710> that<00:42:18.100> spawn 00:42:18.810 --> 00:42:18.820 align:start position:0% there's all the good actions that spawn 00:42:18.820 --> 00:42:20.460 align:start position:0% there's all the good actions that spawn things<00:42:19.180> to<00:42:19.330> happen<00:42:19.480> but<00:42:19.840> in<00:42:19.960> order<00:42:20.170> to<00:42:20.290> make 00:42:20.460 --> 00:42:20.470 align:start position:0% things to happen but in order to make 00:42:20.470 --> 00:42:21.840 align:start position:0% things to happen but in order to make sense<00:42:20.680> of<00:42:20.890> what<00:42:21.040> actually<00:42:21.190> I<00:42:21.430> might<00:42:21.610> have<00:42:21.730> to 00:42:21.840 --> 00:42:21.850 align:start position:0% sense of what actually I might have to 00:42:21.850 --> 00:42:23.640 align:start position:0% sense of what actually I might have to know<00:42:22.030> that<00:42:22.330> this<00:42:22.660> token<00:42:22.960> was<00:42:23.080> meant<00:42:23.350> in<00:42:23.440> a 00:42:23.640 --> 00:42:23.650 align:start position:0% know that this token was meant in a 00:42:23.650 --> 00:42:25.320 align:start position:0% know that this token was meant in a different<00:42:23.950> location<00:42:24.040> and<00:42:24.670> the<00:42:24.880> reason<00:42:25.150> why<00:42:25.270> is 00:42:25.320 --> 00:42:25.330 align:start position:0% different location and the reason why is 00:42:25.330 --> 00:42:26.910 align:start position:0% different location and the reason why is that<00:42:25.450> you<00:42:25.810> know<00:42:25.960> in<00:42:26.110> a<00:42:26.200> relational<00:42:26.770> database 00:42:26.910 --> 00:42:26.920 align:start position:0% that you know in a relational database 00:42:26.920 --> 00:42:28.560 align:start position:0% that you know in a relational database for<00:42:27.310> example<00:42:27.640> you<00:42:27.730> know<00:42:27.820> things<00:42:28.060> like<00:42:28.120> orange 00:42:28.560 --> 00:42:28.570 align:start position:0% for example you know things like orange 00:42:28.570 --> 00:42:30.690 align:start position:0% for example you know things like orange constraints<00:42:29.230> that<00:42:29.470> say<00:42:29.800> that<00:42:30.250> like<00:42:30.400> this 00:42:30.690 --> 00:42:30.700 align:start position:0% constraints that say that like this 00:42:30.700 --> 00:42:33.030 align:start position:0% constraints that say that like this token<00:42:31.120> for<00:42:31.300> sale<00:42:31.510> this<00:42:32.380> something<00:42:32.770> for<00:42:32.920> sale 00:42:33.030 --> 00:42:33.040 align:start position:0% token for sale this something for sale 00:42:33.040 --> 00:42:35.340 align:start position:0% token for sale this something for sale is<00:42:33.370> a<00:42:33.400> row<00:42:33.700> in<00:42:33.910> some<00:42:34.120> database<00:42:34.480> in<00:42:34.780> that<00:42:35.080> row 00:42:35.340 --> 00:42:35.350 align:start position:0% is a row in some database in that row 00:42:35.350 --> 00:42:37.650 align:start position:0% is a row in some database in that row has<00:42:35.590> a<00:42:35.620> column<00:42:36.160> called<00:42:36.490> token<00:42:36.880> ID<00:42:37.030> and<00:42:37.540> that 00:42:37.650 --> 00:42:37.660 align:start position:0% has a column called token ID and that 00:42:37.660 --> 00:42:40.460 align:start position:0% has a column called token ID and that token<00:42:37.960> ID<00:42:38.110> is<00:42:38.290> pointing<00:42:38.740> to<00:42:38.950> a<00:42:39.310> token<00:42:39.790> table 00:42:40.460 --> 00:42:40.470 align:start position:0% token ID is pointing to a token table 00:42:40.470 --> 00:42:42.750 align:start position:0% token ID is pointing to a token table somewhere<00:42:41.470> else<00:42:41.620> and<00:42:41.830> if<00:42:41.950> that<00:42:42.100> token<00:42:42.460> is<00:42:42.550> not 00:42:42.750 --> 00:42:42.760 align:start position:0% somewhere else and if that token is not 00:42:42.760 --> 00:42:44.760 align:start position:0% somewhere else and if that token is not in<00:42:42.880> that<00:42:43.000> token<00:42:43.330> table<00:42:43.690> then<00:42:43.930> this<00:42:44.170> schema<00:42:44.650> has 00:42:44.760 --> 00:42:44.770 align:start position:0% in that token table then this schema has 00:42:44.770 --> 00:42:46.380 align:start position:0% in that token table then this schema has now<00:42:44.950> been<00:42:45.100> invalidated<00:42:45.610> because<00:42:46.030> I<00:42:46.180> can't 00:42:46.380 --> 00:42:46.390 align:start position:0% now been invalidated because I can't 00:42:46.390 --> 00:42:48.180 align:start position:0% now been invalidated because I can't talk<00:42:46.540> about<00:42:46.720> a<00:42:46.840> token<00:42:47.170> for<00:42:47.320> sale<00:42:47.470> unless<00:42:48.010> I 00:42:48.180 --> 00:42:48.190 align:start position:0% talk about a token for sale unless I 00:42:48.190 --> 00:42:50.130 align:start position:0% talk about a token for sale unless I know<00:42:48.250> if<00:42:48.430> I'm<00:42:48.520> at<00:42:48.640> okay<00:42:48.880> so<00:42:49.210> basically<00:42:49.930> like 00:42:50.130 --> 00:42:50.140 align:start position:0% know if I'm at okay so basically like 00:42:50.140 --> 00:42:51.930 align:start position:0% know if I'm at okay so basically like you<00:42:50.320> have<00:42:50.470> created<00:42:50.980> a<00:42:51.160> situation<00:42:51.370> in<00:42:51.790> which 00:42:51.930 --> 00:42:51.940 align:start position:0% you have created a situation in which 00:42:51.940 --> 00:42:53.700 align:start position:0% you have created a situation in which you<00:42:52.180> have<00:42:52.210> you<00:42:53.170> know<00:42:53.290> foreign<00:42:53.530> key 00:42:53.700 --> 00:42:53.710 align:start position:0% you have you know foreign key 00:42:53.710 --> 00:42:54.810 align:start position:0% you have you know foreign key constraints<00:42:54.190> in<00:42:54.280> a<00:42:54.310> relational<00:42:54.700> database 00:42:54.810 --> 00:42:54.820 align:start position:0% constraints in a relational database 00:42:54.820 --> 00:42:57.900 align:start position:0% constraints in a relational database that<00:42:55.330> cannot<00:42:55.960> you<00:42:56.890> cannot<00:42:57.160> maintain<00:42:57.370> unless 00:42:57.900 --> 00:42:57.910 align:start position:0% that cannot you cannot maintain unless 00:42:57.910 --> 00:43:00.030 align:start position:0% that cannot you cannot maintain unless things<00:42:58.120> are<00:42:58.300> processed<00:42:59.110> and<00:42:59.230> in<00:42:59.350> order<00:42:59.740> to 00:43:00.030 --> 00:43:00.040 align:start position:0% things are processed and in order to 00:43:00.040 --> 00:43:02.550 align:start position:0% things are processed and in order to keep<00:43:00.970> those<00:43:01.150> quarantine<00:43:01.660> violations<00:43:02.200> sound 00:43:02.550 --> 00:43:02.560 align:start position:0% keep those quarantine violations sound 00:43:02.560 --> 00:43:05.370 align:start position:0% keep those quarantine violations sound and<00:43:03.280> so<00:43:03.580> this<00:43:04.300> is<00:43:04.450> particularly<00:43:04.810> useful<00:43:05.080> if 00:43:05.370 --> 00:43:05.380 align:start position:0% and so this is particularly useful if 00:43:05.380 --> 00:43:07.410 align:start position:0% and so this is particularly useful if you<00:43:05.530> want<00:43:05.680> to<00:43:05.770> not<00:43:06.040> run<00:43:06.340> against<00:43:06.850> like<00:43:07.120> a<00:43:07.150> full 00:43:07.410 --> 00:43:07.420 align:start position:0% you want to not run against like a full 00:43:07.420 --> 00:43:10.320 align:start position:0% you want to not run against like a full archive<00:43:07.750> node<00:43:08.080> where<00:43:09.070> so<00:43:09.850> like<00:43:10.000> if<00:43:10.120> you<00:43:10.180> want 00:43:10.320 --> 00:43:10.330 align:start position:0% archive node where so like if you want 00:43:10.330 --> 00:43:12.150 align:start position:0% archive node where so like if you want to<00:43:10.360> run<00:43:10.450> a<00:43:10.510> yeah<00:43:11.110> that's<00:43:11.410> not<00:43:11.620> a<00:43:11.650> big<00:43:11.980> problem 00:43:12.150 --> 00:43:12.160 align:start position:0% to run a yeah that's not a big problem 00:43:12.160 --> 00:43:15.080 align:start position:0% to run a yeah that's not a big problem if<00:43:12.340> you<00:43:12.490> if<00:43:12.730> you<00:43:12.820> have<00:43:12.940> a<00:43:12.970> full<00:43:13.180> are<00:43:13.830> cool 00:43:15.080 --> 00:43:15.090 align:start position:0% if you if you have a full are cool 00:43:15.090 --> 00:43:17.360 align:start position:0% if you if you have a full are cool you<00:43:15.420> can<00:43:15.630> do<00:43:16.080> whatever<00:43:16.290> contract<00:43:16.770> lookups<00:43:17.250> at 00:43:17.360 --> 00:43:17.370 align:start position:0% you can do whatever contract lookups at 00:43:17.370 --> 00:43:27.800 align:start position:0% you can do whatever contract lookups at whatever<00:43:17.490> point<00:43:17.790> in<00:43:17.940> time<00:43:18.170> for<00:43:19.170> example<00:43:26.630> if<00:43:27.630> I 00:43:27.800 --> 00:43:27.810 align:start position:0% whatever point in time for example if I 00:43:27.810 --> 00:43:35.960 align:start position:0% whatever point in time for example if I don't<00:43:28.200> have<00:43:28.410> a<00:43:30.560> sale 00:43:35.960 --> 00:43:35.970 align:start position:0% 00:43:35.970 --> 00:43:47.270 align:start position:0% [Music] 00:43:47.270 --> 00:43:47.280 align:start position:0% 00:43:47.280 --> 00:43:57.790 align:start position:0% [Music] 00:43:57.790 --> 00:43:57.800 align:start position:0% 00:43:57.800 --> 00:44:03.370 align:start position:0% [Music] 00:44:03.370 --> 00:44:03.380 align:start position:0% 00:44:03.380 --> 00:44:06.840 align:start position:0% [Applause]