WEBVTT Kind: captions Language: en 00:00:10.000 --> 00:00:13.509 align:start position:0% all<00:00:10.160> right<00:00:10.400> it's<00:00:10.480> time<00:00:10.639> to<00:00:10.719> get<00:00:10.880> started<00:00:11.200> again 00:00:13.509 --> 00:00:13.519 align:start position:0% 00:00:13.519 --> 00:00:16.150 align:start position:0% time<00:00:13.759> for<00:00:13.920> the<00:00:14.240> most<00:00:14.480> exciting<00:00:14.960> parts<00:00:15.920> and<00:00:16.080> the 00:00:16.150 --> 00:00:16.160 align:start position:0% time for the most exciting parts and the 00:00:16.160 --> 00:00:17.430 align:start position:0% time for the most exciting parts and the lightning<00:00:16.560> talks 00:00:17.430 --> 00:00:17.440 align:start position:0% lightning talks 00:00:17.440 --> 00:00:18.790 align:start position:0% lightning talks this<00:00:17.600> is<00:00:17.680> where<00:00:17.760> we<00:00:17.840> get<00:00:18.000> to<00:00:18.240> actually<00:00:18.560> get<00:00:18.720> a 00:00:18.790 --> 00:00:18.800 align:start position:0% this is where we get to actually get a 00:00:18.800 --> 00:00:20.470 align:start position:0% this is where we get to actually get a chance<00:00:19.039> to<00:00:19.279> see<00:00:19.920> what<00:00:20.080> people<00:00:20.240> have<00:00:20.320> been 00:00:20.470 --> 00:00:20.480 align:start position:0% chance to see what people have been 00:00:20.480 --> 00:00:22.630 align:start position:0% chance to see what people have been doing<00:00:20.800> that<00:00:20.960> may<00:00:21.199> have<00:00:21.439> uh<00:00:21.840> done<00:00:22.320> something 00:00:22.630 --> 00:00:22.640 align:start position:0% doing that may have uh done something 00:00:22.640 --> 00:00:24.630 align:start position:0% doing that may have uh done something actually<00:00:22.880> maybe<00:00:23.119> over<00:00:23.279> the<00:00:23.359> last<00:00:23.600> 24<00:00:24.000> hours<00:00:24.240> 48 00:00:24.630 --> 00:00:24.640 align:start position:0% actually maybe over the last 24 hours 48 00:00:24.640 --> 00:00:25.990 align:start position:0% actually maybe over the last 24 hours 48 hours 00:00:25.990 --> 00:00:26.000 align:start position:0% hours 00:00:26.000 --> 00:00:27.189 align:start position:0% hours and<00:00:26.080> go<00:00:26.240> through<00:00:26.400> some<00:00:26.480> really<00:00:26.720> cool<00:00:26.880> things 00:00:27.189 --> 00:00:27.199 align:start position:0% and go through some really cool things 00:00:27.199 --> 00:00:28.230 align:start position:0% and go through some really cool things that<00:00:27.279> have<00:00:27.359> been<00:00:27.519> happening<00:00:27.680> recently<00:00:28.160> we 00:00:28.230 --> 00:00:28.240 align:start position:0% that have been happening recently we 00:00:28.240 --> 00:00:30.630 align:start position:0% that have been happening recently we have<00:00:28.400> i<00:00:28.560> think<00:00:28.800> four<00:00:29.359> uh<00:00:29.519> lightning<00:00:29.840> socks<00:00:30.480> for 00:00:30.630 --> 00:00:30.640 align:start position:0% have i think four uh lightning socks for 00:00:30.640 --> 00:00:32.870 align:start position:0% have i think four uh lightning socks for this<00:00:30.800> afternoon<00:00:31.599> uh<00:00:31.840> the<00:00:31.920> first<00:00:32.160> one<00:00:32.399> up<00:00:32.640> is 00:00:32.870 --> 00:00:32.880 align:start position:0% this afternoon uh the first one up is 00:00:32.880 --> 00:00:35.430 align:start position:0% this afternoon uh the first one up is alex<00:00:33.840> he<00:00:34.079> uh<00:00:34.239> works 00:00:35.430 --> 00:00:35.440 align:start position:0% alex he uh works 00:00:35.440 --> 00:00:37.190 align:start position:0% alex he uh works with<00:00:35.520> me<00:00:35.600> at<00:00:35.680> relevance<00:00:36.480> has<00:00:36.880> the<00:00:36.960> most 00:00:37.190 --> 00:00:37.200 align:start position:0% with me at relevance has the most 00:00:37.200 --> 00:00:39.270 align:start position:0% with me at relevance has the most excellent<00:00:37.520> mohawk<00:00:37.920> on<00:00:38.079> the<00:00:38.160> planet<00:00:38.960> that<00:00:39.120> i 00:00:39.270 --> 00:00:39.280 align:start position:0% excellent mohawk on the planet that i 00:00:39.280 --> 00:00:41.110 align:start position:0% excellent mohawk on the planet that i think<00:00:39.600> might<00:00:39.920> uh 00:00:41.110 --> 00:00:41.120 align:start position:0% think might uh 00:00:41.120 --> 00:00:42.830 align:start position:0% think might uh kill<00:00:41.360> kind<00:00:41.520> of<00:00:41.600> thing 00:00:42.830 --> 00:00:42.840 align:start position:0% kill kind of thing 00:00:42.840 --> 00:00:45.110 align:start position:0% kill kind of thing awesome<00:00:43.040> dead<00:00:43.280> animal<00:00:43.600> then<00:00:43.840> animal<00:00:44.160> hawk<00:00:44.879> so 00:00:45.110 --> 00:00:45.120 align:start position:0% awesome dead animal then animal hawk so 00:00:45.120 --> 00:00:48.709 align:start position:0% awesome dead animal then animal hawk so uh<00:00:45.600> alex<00:00:46.399> all<00:00:46.559> right<00:00:47.280> i'm<00:00:47.440> love<00:00:47.680> machine 00:00:48.709 --> 00:00:48.719 align:start position:0% uh alex all right i'm love machine 00:00:48.719 --> 00:00:51.430 align:start position:0% uh alex all right i'm love machine i<00:00:48.879> like<00:00:49.120> ideas<00:00:49.600> i<00:00:49.680> like<00:00:49.920> ideas<00:00:50.399> because 00:00:51.430 --> 00:00:51.440 align:start position:0% i like ideas i like ideas because 00:00:51.440 --> 00:00:54.310 align:start position:0% i like ideas i like ideas because they're<00:00:51.760> uh 00:00:54.310 --> 00:00:54.320 align:start position:0% 00:00:54.320 --> 00:00:55.990 align:start position:0% they're<00:00:54.480> something<00:00:54.800> that<00:00:55.120> we<00:00:55.280> kind<00:00:55.440> of<00:00:55.840> share 00:00:55.990 --> 00:00:56.000 align:start position:0% they're something that we kind of share 00:00:56.000 --> 00:00:58.389 align:start position:0% they're something that we kind of share a<00:00:56.079> relationship<00:00:56.640> with<00:00:57.360> uh<00:00:57.680> humans<00:00:58.000> can<00:00:58.160> use 00:00:58.389 --> 00:00:58.399 align:start position:0% a relationship with uh humans can use 00:00:58.399 --> 00:01:01.510 align:start position:0% a relationship with uh humans can use ideas<00:00:59.199> but<00:00:59.440> ideas<00:00:59.760> can<00:00:59.920> also<00:01:00.160> use<00:01:00.399> humans 00:01:01.510 --> 00:01:01.520 align:start position:0% ideas but ideas can also use humans 00:01:01.520 --> 00:01:02.549 align:start position:0% ideas but ideas can also use humans uh 00:01:02.549 --> 00:01:02.559 align:start position:0% uh 00:01:02.559 --> 00:01:04.869 align:start position:0% uh one<00:01:02.719> way<00:01:02.879> the<00:01:03.440> idea<00:01:03.760> to<00:01:03.840> be<00:01:04.000> using<00:01:04.239> a<00:01:04.320> human<00:01:04.720> is 00:01:04.869 --> 00:01:04.879 align:start position:0% one way the idea to be using a human is 00:01:04.879 --> 00:01:06.710 align:start position:0% one way the idea to be using a human is that<00:01:05.360> an<00:01:05.519> idea<00:01:05.840> can<00:01:05.920> take<00:01:06.080> up<00:01:06.240> residence<00:01:06.640> in 00:01:06.710 --> 00:01:06.720 align:start position:0% that an idea can take up residence in 00:01:06.720 --> 00:01:09.670 align:start position:0% that an idea can take up residence in your<00:01:06.880> mind<00:01:07.280> it<00:01:07.439> can<00:01:08.000> burrow<00:01:08.479> in<00:01:09.040> and<00:01:09.360> hang<00:01:09.600> out 00:01:09.670 --> 00:01:09.680 align:start position:0% your mind it can burrow in and hang out 00:01:09.680 --> 00:01:11.670 align:start position:0% your mind it can burrow in and hang out there<00:01:09.920> for<00:01:10.080> years<00:01:10.400> and<00:01:10.560> years 00:01:11.670 --> 00:01:11.680 align:start position:0% there for years and years 00:01:11.680 --> 00:01:13.510 align:start position:0% there for years and years and<00:01:12.080> another<00:01:12.400> way<00:01:12.560> that<00:01:12.720> an<00:01:12.880> idea<00:01:13.200> can<00:01:13.280> use<00:01:13.439> a 00:01:13.510 --> 00:01:13.520 align:start position:0% and another way that an idea can use a 00:01:13.520 --> 00:01:15.670 align:start position:0% and another way that an idea can use a human<00:01:14.240> is<00:01:14.400> that<00:01:14.479> we<00:01:14.640> can<00:01:14.799> communicate<00:01:15.360> them<00:01:15.520> to 00:01:15.670 --> 00:01:15.680 align:start position:0% human is that we can communicate them to 00:01:15.680 --> 00:01:16.710 align:start position:0% human is that we can communicate them to each<00:01:15.840> other 00:01:16.710 --> 00:01:16.720 align:start position:0% each other 00:01:16.720 --> 00:01:18.630 align:start position:0% each other and<00:01:16.880> in<00:01:16.960> that<00:01:17.200> manner<00:01:17.759> the<00:01:17.920> ideas<00:01:18.320> are<00:01:18.400> using 00:01:18.630 --> 00:01:18.640 align:start position:0% and in that manner the ideas are using 00:01:18.640 --> 00:01:21.510 align:start position:0% and in that manner the ideas are using us<00:01:18.799> as<00:01:18.960> replicators<00:01:19.840> for<00:01:20.000> themselves 00:01:21.510 --> 00:01:21.520 align:start position:0% us as replicators for themselves 00:01:21.520 --> 00:01:22.950 align:start position:0% us as replicators for themselves i'd<00:01:21.680> like<00:01:21.840> to<00:01:21.920> talk<00:01:22.080> to<00:01:22.159> you<00:01:22.320> about<00:01:22.479> one<00:01:22.640> of<00:01:22.720> my 00:01:22.950 --> 00:01:22.960 align:start position:0% i'd like to talk to you about one of my 00:01:22.960 --> 00:01:26.710 align:start position:0% i'd like to talk to you about one of my ideas<00:01:23.759> which<00:01:23.920> is<00:01:24.159> on<00:01:24.400> cyclic<00:01:24.880> time<00:01:25.759> a<00:01:26.479> long 00:01:26.710 --> 00:01:26.720 align:start position:0% ideas which is on cyclic time a long 00:01:26.720 --> 00:01:28.789 align:start position:0% ideas which is on cyclic time a long time<00:01:26.880> ago<00:01:27.439> i<00:01:27.520> had<00:01:27.680> a<00:01:27.759> problem<00:01:28.000> where<00:01:28.159> i<00:01:28.240> had<00:01:28.400> to 00:01:28.789 --> 00:01:28.799 align:start position:0% time ago i had a problem where i had to 00:01:28.799 --> 00:01:30.710 align:start position:0% time ago i had a problem where i had to write<00:01:29.040> a<00:01:29.200> scheduling<00:01:29.600> mechanism 00:01:30.710 --> 00:01:30.720 align:start position:0% write a scheduling mechanism 00:01:30.720 --> 00:01:31.910 align:start position:0% write a scheduling mechanism i<00:01:30.799> think<00:01:30.960> that<00:01:31.119> there's<00:01:31.439> probably<00:01:31.600> a<00:01:31.680> lot<00:01:31.840> of 00:01:31.910 --> 00:01:31.920 align:start position:0% i think that there's probably a lot of 00:01:31.920 --> 00:01:33.270 align:start position:0% i think that there's probably a lot of people<00:01:32.159> in<00:01:32.240> the<00:01:32.320> room<00:01:32.479> who've<00:01:32.720> had<00:01:32.880> to<00:01:32.960> do<00:01:33.119> this 00:01:33.270 --> 00:01:33.280 align:start position:0% people in the room who've had to do this 00:01:33.280 --> 00:01:35.590 align:start position:0% people in the room who've had to do this but<00:01:33.840> sick<00:01:34.079> like<00:01:34.240> time<00:01:34.560> is<00:01:34.640> a<00:01:34.720> problem<00:01:35.439> it 00:01:35.590 --> 00:01:35.600 align:start position:0% but sick like time is a problem it 00:01:35.600 --> 00:01:37.749 align:start position:0% but sick like time is a problem it solves<00:01:36.000> a<00:01:36.079> lot<00:01:36.240> of<00:01:36.320> problems<00:01:37.040> or<00:01:37.280> it's<00:01:37.439> an<00:01:37.520> idea 00:01:37.749 --> 00:01:37.759 align:start position:0% solves a lot of problems or it's an idea 00:01:37.759 --> 00:01:38.789 align:start position:0% solves a lot of problems or it's an idea that<00:01:37.840> solves<00:01:38.079> a<00:01:38.079> lot<00:01:38.240> of<00:01:38.320> problems<00:01:38.560> right<00:01:38.720> it 00:01:38.789 --> 00:01:38.799 align:start position:0% that solves a lot of problems right it 00:01:38.799 --> 00:01:40.550 align:start position:0% that solves a lot of problems right it allows<00:01:39.040> you<00:01:39.119> to<00:01:39.200> do<00:01:39.360> scheduling<00:01:40.079> this<00:01:40.240> allows 00:01:40.550 --> 00:01:40.560 align:start position:0% allows you to do scheduling this allows 00:01:40.560 --> 00:01:42.630 align:start position:0% allows you to do scheduling this allows you<00:01:40.720> to<00:01:40.880> do<00:01:41.200> calendaring<00:01:41.920> applications<00:01:42.479> it 00:01:42.630 --> 00:01:42.640 align:start position:0% you to do calendaring applications it 00:01:42.640 --> 00:01:44.069 align:start position:0% you to do calendaring applications it allows<00:01:42.880> you<00:01:43.040> to<00:01:43.119> do<00:01:43.520> building<00:01:43.840> there's 00:01:44.069 --> 00:01:44.079 align:start position:0% allows you to do building there's 00:01:44.079 --> 00:01:45.990 align:start position:0% allows you to do building there's applications<00:01:44.720> for<00:01:44.960> this<00:01:45.200> idea<00:01:45.439> of<00:01:45.600> cyclic 00:01:45.990 --> 00:01:46.000 align:start position:0% applications for this idea of cyclic 00:01:46.000 --> 00:01:48.469 align:start position:0% applications for this idea of cyclic time<00:01:46.799> and<00:01:47.520> it's 00:01:48.469 --> 00:01:48.479 align:start position:0% time and it's 00:01:48.479 --> 00:01:50.950 align:start position:0% time and it's an<00:01:48.720> idea<00:01:49.280> if<00:01:49.360> you<00:01:49.520> can<00:01:49.759> pull<00:01:50.000> it<00:01:50.079> out<00:01:50.560> and<00:01:50.799> treat 00:01:50.950 --> 00:01:50.960 align:start position:0% an idea if you can pull it out and treat 00:01:50.960 --> 00:01:52.710 align:start position:0% an idea if you can pull it out and treat it<00:01:51.119> abstractly<00:01:52.000> you<00:01:52.159> can<00:01:52.240> start<00:01:52.479> building 00:01:52.710 --> 00:01:52.720 align:start position:0% it abstractly you can start building 00:01:52.720 --> 00:01:54.469 align:start position:0% it abstractly you can start building things<00:01:53.200> for<00:01:53.439> solving<00:01:53.759> all<00:01:53.920> these<00:01:54.079> problems<00:01:54.399> on 00:01:54.469 --> 00:01:54.479 align:start position:0% things for solving all these problems on 00:01:54.479 --> 00:01:57.030 align:start position:0% things for solving all these problems on top<00:01:54.720> of<00:01:54.799> that<00:01:54.960> idea 00:01:57.030 --> 00:01:57.040 align:start position:0% top of that idea 00:01:57.040 --> 00:01:58.550 align:start position:0% top of that idea so<00:01:57.360> i'd<00:01:57.439> like<00:01:57.680> to<00:01:57.759> do<00:01:57.920> a<00:01:58.000> little<00:01:58.240> bit<00:01:58.399> of<00:01:58.479> an 00:01:58.550 --> 00:01:58.560 align:start position:0% so i'd like to do a little bit of an 00:01:58.560 --> 00:02:01.830 align:start position:0% so i'd like to do a little bit of an audience<00:01:58.880> participation<00:01:59.680> session<00:02:00.399> um 00:02:01.830 --> 00:02:01.840 align:start position:0% audience participation session um 00:02:01.840 --> 00:02:04.069 align:start position:0% audience participation session um real<00:02:02.000> quick<00:02:02.320> just<00:02:02.640> by<00:02:02.880> show<00:02:03.119> of<00:02:03.280> hands<00:02:03.840> who 00:02:04.069 --> 00:02:04.079 align:start position:0% real quick just by show of hands who 00:02:04.079 --> 00:02:05.350 align:start position:0% real quick just by show of hands who here<00:02:04.240> has<00:02:04.399> ever<00:02:04.560> had<00:02:04.799> to<00:02:04.880> deal<00:02:05.119> with<00:02:05.280> a 00:02:05.350 --> 00:02:05.360 align:start position:0% here has ever had to deal with a 00:02:05.360 --> 00:02:08.070 align:start position:0% here has ever had to deal with a scheduling<00:02:05.840> problem 00:02:08.070 --> 00:02:08.080 align:start position:0% scheduling problem 00:02:08.080 --> 00:02:09.350 align:start position:0% scheduling problem all<00:02:08.239> right 00:02:09.350 --> 00:02:09.360 align:start position:0% all right 00:02:09.360 --> 00:02:12.869 align:start position:0% all right great<00:02:09.840> now<00:02:10.319> who<00:02:10.560> here<00:02:11.280> looked<00:02:11.520> at<00:02:11.599> kron<00:02:12.160> said 00:02:12.869 --> 00:02:12.879 align:start position:0% great now who here looked at kron said 00:02:12.879 --> 00:02:13.990 align:start position:0% great now who here looked at kron said man<00:02:13.120> i<00:02:13.280> really<00:02:13.440> don't<00:02:13.599> want<00:02:13.680> to<00:02:13.760> use<00:02:13.920> that 00:02:13.990 --> 00:02:14.000 align:start position:0% man i really don't want to use that 00:02:14.000 --> 00:02:18.470 align:start position:0% man i really don't want to use that because<00:02:14.160> it<00:02:14.319> looks<00:02:14.480> ugly 00:02:18.470 --> 00:02:18.480 align:start position:0% 00:02:18.480 --> 00:02:19.430 align:start position:0% all<00:02:18.640> right 00:02:19.430 --> 00:02:19.440 align:start position:0% all right 00:02:19.440 --> 00:02:21.350 align:start position:0% all right of<00:02:19.680> those<00:02:20.239> who<00:02:20.480> decided<00:02:20.879> you<00:02:21.040> know<00:02:21.120> what<00:02:21.280> i'm 00:02:21.350 --> 00:02:21.360 align:start position:0% of those who decided you know what i'm 00:02:21.360 --> 00:02:22.550 align:start position:0% of those who decided you know what i'm going<00:02:21.520> to<00:02:21.599> do<00:02:21.760> something<00:02:22.080> different<00:02:22.400> than 00:02:22.550 --> 00:02:22.560 align:start position:0% going to do something different than 00:02:22.560 --> 00:02:23.750 align:start position:0% going to do something different than crown<00:02:22.879> i'm<00:02:22.959> going<00:02:23.040> to<00:02:23.040> do<00:02:23.200> something<00:02:23.520> better 00:02:23.750 --> 00:02:23.760 align:start position:0% crown i'm going to do something better 00:02:23.760 --> 00:02:25.750 align:start position:0% crown i'm going to do something better than<00:02:24.000> crime 00:02:25.750 --> 00:02:25.760 align:start position:0% than crime 00:02:25.760 --> 00:02:29.030 align:start position:0% than crime who<00:02:25.920> succeeded 00:02:29.030 --> 00:02:29.040 align:start position:0% 00:02:29.040 --> 00:02:31.350 align:start position:0% okay<00:02:29.520> good<00:02:29.920> i'm<00:02:30.080> right<00:02:30.239> there<00:02:30.480> with<00:02:30.640> you 00:02:31.350 --> 00:02:31.360 align:start position:0% okay good i'm right there with you 00:02:31.360 --> 00:02:32.309 align:start position:0% okay good i'm right there with you uh 00:02:32.309 --> 00:02:32.319 align:start position:0% uh 00:02:32.319 --> 00:02:34.150 align:start position:0% uh about<00:02:32.640> seven<00:02:32.879> years<00:02:33.040> ago<00:02:33.200> i<00:02:33.280> had<00:02:33.440> the<00:02:33.599> uh<00:02:34.080> you 00:02:34.150 --> 00:02:34.160 align:start position:0% about seven years ago i had the uh you 00:02:34.160 --> 00:02:36.550 align:start position:0% about seven years ago i had the uh you know<00:02:34.319> i<00:02:34.400> wanted<00:02:34.640> to<00:02:34.800> beat<00:02:35.040> this<00:02:35.280> problem<00:02:36.080> and<00:02:36.480> i 00:02:36.550 --> 00:02:36.560 align:start position:0% know i wanted to beat this problem and i 00:02:36.560 --> 00:02:39.350 align:start position:0% know i wanted to beat this problem and i surrendered 00:02:39.350 --> 00:02:39.360 align:start position:0% 00:02:39.360 --> 00:02:41.110 align:start position:0% what<00:02:39.599> about<00:02:39.840> a<00:02:39.920> couple<00:02:40.160> months<00:02:40.400> ago<00:02:40.959> a 00:02:41.110 --> 00:02:41.120 align:start position:0% what about a couple months ago a 00:02:41.120 --> 00:02:42.790 align:start position:0% what about a couple months ago a gentleman<00:02:41.440> named<00:02:41.760> alan<00:02:42.000> dippert<00:02:42.319> who<00:02:42.480> i<00:02:42.560> work 00:02:42.790 --> 00:02:42.800 align:start position:0% gentleman named alan dippert who i work 00:02:42.800 --> 00:02:43.910 align:start position:0% gentleman named alan dippert who i work with 00:02:43.910 --> 00:02:43.920 align:start position:0% with 00:02:43.920 --> 00:02:45.589 align:start position:0% with was<00:02:44.160> talking<00:02:44.480> about<00:02:44.640> this<00:02:44.879> idea<00:02:45.120> of<00:02:45.200> cyclic 00:02:45.589 --> 00:02:45.599 align:start position:0% was talking about this idea of cyclic 00:02:45.599 --> 00:02:46.710 align:start position:0% was talking about this idea of cyclic time<00:02:45.760> with<00:02:45.920> me 00:02:46.710 --> 00:02:46.720 align:start position:0% time with me 00:02:46.720 --> 00:02:47.750 align:start position:0% time with me and 00:02:47.750 --> 00:02:47.760 align:start position:0% and 00:02:47.760 --> 00:02:48.830 align:start position:0% and i 00:02:48.830 --> 00:02:48.840 align:start position:0% i 00:02:48.840 --> 00:02:52.070 align:start position:0% i was<00:02:49.800> re-revisiting<00:02:50.800> my<00:02:51.040> ideas<00:02:51.360> about<00:02:51.680> cyclic 00:02:52.070 --> 00:02:52.080 align:start position:0% was re-revisiting my ideas about cyclic 00:02:52.080 --> 00:02:53.190 align:start position:0% was re-revisiting my ideas about cyclic time 00:02:53.190 --> 00:02:53.200 align:start position:0% time 00:02:53.200 --> 00:02:55.190 align:start position:0% time when<00:02:53.360> i<00:02:53.599> first<00:02:53.920> tried<00:02:54.080> to<00:02:54.160> solve<00:02:54.400> this<00:02:54.640> problem 00:02:55.190 --> 00:02:55.200 align:start position:0% when i first tried to solve this problem 00:02:55.200 --> 00:02:57.190 align:start position:0% when i first tried to solve this problem i<00:02:55.360> didn't<00:02:55.519> have<00:02:55.680> a<00:02:55.760> good<00:02:56.000> solution<00:02:56.879> and<00:02:57.120> i 00:02:57.190 --> 00:02:57.200 align:start position:0% i didn't have a good solution and i 00:02:57.200 --> 00:02:58.550 align:start position:0% i didn't have a good solution and i think<00:02:57.440> a<00:02:57.519> lot<00:02:57.599> of<00:02:57.760> the<00:02:57.840> reason<00:02:58.080> i<00:02:58.239> didn't<00:02:58.400> come 00:02:58.550 --> 00:02:58.560 align:start position:0% think a lot of the reason i didn't come 00:02:58.560 --> 00:02:59.830 align:start position:0% think a lot of the reason i didn't come to<00:02:58.640> the<00:02:58.720> right<00:02:58.959> solution<00:02:59.280> is<00:02:59.440> i<00:02:59.519> didn't<00:02:59.680> have 00:02:59.830 --> 00:02:59.840 align:start position:0% to the right solution is i didn't have 00:02:59.840 --> 00:03:01.750 align:start position:0% to the right solution is i didn't have the<00:02:59.920> right<00:03:00.159> tools 00:03:01.750 --> 00:03:01.760 align:start position:0% the right tools 00:03:01.760 --> 00:03:03.830 align:start position:0% the right tools when<00:03:02.000> we<00:03:02.080> started<00:03:02.319> thinking<00:03:02.720> about<00:03:02.959> it<00:03:03.040> again 00:03:03.830 --> 00:03:03.840 align:start position:0% when we started thinking about it again 00:03:03.840 --> 00:03:05.830 align:start position:0% when we started thinking about it again i've<00:03:04.000> been<00:03:04.239> educated<00:03:04.720> in<00:03:04.800> closure<00:03:05.519> and<00:03:05.599> i<00:03:05.680> was 00:03:05.830 --> 00:03:05.840 align:start position:0% i've been educated in closure and i was 00:03:05.840 --> 00:03:07.110 align:start position:0% i've been educated in closure and i was able<00:03:06.080> to<00:03:06.159> start<00:03:06.400> using<00:03:06.640> the<00:03:06.720> tools<00:03:07.040> the 00:03:07.110 --> 00:03:07.120 align:start position:0% able to start using the tools the 00:03:07.120 --> 00:03:09.750 align:start position:0% able to start using the tools the closure<00:03:07.519> provides<00:03:08.480> to<00:03:08.879> apply<00:03:09.200> them<00:03:09.360> to<00:03:09.519> this 00:03:09.750 --> 00:03:09.760 align:start position:0% closure provides to apply them to this 00:03:09.760 --> 00:03:12.149 align:start position:0% closure provides to apply them to this problem<00:03:10.560> and<00:03:11.040> i<00:03:11.200> came<00:03:11.440> home<00:03:11.599> with<00:03:11.680> something 00:03:12.149 --> 00:03:12.159 align:start position:0% problem and i came home with something 00:03:12.159 --> 00:03:13.110 align:start position:0% problem and i came home with something that 00:03:13.110 --> 00:03:13.120 align:start position:0% that 00:03:13.120 --> 00:03:15.030 align:start position:0% that it's<00:03:13.280> an<00:03:13.440> interesting<00:03:13.920> idea<00:03:14.319> i<00:03:14.640> haven't<00:03:14.879> been 00:03:15.030 --> 00:03:15.040 align:start position:0% it's an interesting idea i haven't been 00:03:15.040 --> 00:03:16.309 align:start position:0% it's an interesting idea i haven't been putting<00:03:15.280> it<00:03:15.360> into<00:03:15.519> production<00:03:16.000> i<00:03:16.080> haven't 00:03:16.309 --> 00:03:16.319 align:start position:0% putting it into production i haven't 00:03:16.319 --> 00:03:18.470 align:start position:0% putting it into production i haven't been<00:03:16.400> using<00:03:16.640> it<00:03:16.720> in<00:03:16.879> anger<00:03:17.599> but<00:03:18.239> it's<00:03:18.400> a 00:03:18.470 --> 00:03:18.480 align:start position:0% been using it in anger but it's a 00:03:18.480 --> 00:03:20.949 align:start position:0% been using it in anger but it's a scratch<00:03:18.800> that's<00:03:19.040> looking<00:03:19.280> for<00:03:19.360> an<00:03:19.519> inch 00:03:20.949 --> 00:03:20.959 align:start position:0% scratch that's looking for an inch 00:03:20.959 --> 00:03:22.790 align:start position:0% scratch that's looking for an inch when<00:03:21.120> i'm<00:03:21.200> thinking<00:03:21.519> about<00:03:21.680> cyclic<00:03:22.080> time<00:03:22.640> i 00:03:22.790 --> 00:03:22.800 align:start position:0% when i'm thinking about cyclic time i 00:03:22.800 --> 00:03:24.070 align:start position:0% when i'm thinking about cyclic time i like<00:03:22.959> to<00:03:23.040> think<00:03:23.200> about<00:03:23.360> it<00:03:23.519> in<00:03:23.599> these<00:03:23.760> kinds<00:03:24.000> of 00:03:24.070 --> 00:03:24.080 align:start position:0% like to think about it in these kinds of 00:03:24.080 --> 00:03:28.070 align:start position:0% like to think about it in these kinds of terms<00:03:24.879> time<00:03:25.280> is<00:03:25.599> a<00:03:25.760> single<00:03:26.000> dimension 00:03:28.070 --> 00:03:28.080 align:start position:0% terms time is a single dimension 00:03:28.080 --> 00:03:30.070 align:start position:0% terms time is a single dimension it's<00:03:28.319> uncountably<00:03:28.959> infinite<00:03:29.680> there<00:03:29.840> are 00:03:30.070 --> 00:03:30.080 align:start position:0% it's uncountably infinite there are 00:03:30.080 --> 00:03:31.910 align:start position:0% it's uncountably infinite there are apparently<00:03:30.720> many<00:03:31.200> infinitely<00:03:31.599> many 00:03:31.910 --> 00:03:31.920 align:start position:0% apparently many infinitely many 00:03:31.920 --> 00:03:33.830 align:start position:0% apparently many infinitely many instances<00:03:32.400> in<00:03:32.640> time 00:03:33.830 --> 00:03:33.840 align:start position:0% instances in time 00:03:33.840 --> 00:03:35.589 align:start position:0% instances in time and<00:03:34.080> that's<00:03:34.319> not<00:03:34.480> useful 00:03:35.589 --> 00:03:35.599 align:start position:0% and that's not useful 00:03:35.599 --> 00:03:37.350 align:start position:0% and that's not useful uh<00:03:35.840> we<00:03:36.000> can't<00:03:36.159> work<00:03:36.400> with<00:03:36.640> an<00:03:36.879> accountably 00:03:37.350 --> 00:03:37.360 align:start position:0% uh we can't work with an accountably 00:03:37.360 --> 00:03:39.589 align:start position:0% uh we can't work with an accountably infinite<00:03:37.760> set<00:03:37.920> of<00:03:38.080> time 00:03:39.589 --> 00:03:39.599 align:start position:0% infinite set of time 00:03:39.599 --> 00:03:41.350 align:start position:0% infinite set of time and<00:03:39.920> the<00:03:40.239> final<00:03:40.560> quality<00:03:40.879> of<00:03:41.040> time<00:03:41.200> that<00:03:41.280> i 00:03:41.350 --> 00:03:41.360 align:start position:0% and the final quality of time that i 00:03:41.360 --> 00:03:43.030 align:start position:0% and the final quality of time that i like<00:03:41.519> to<00:03:41.599> think<00:03:41.760> about<00:03:42.080> when<00:03:42.319> i'm 00:03:43.030 --> 00:03:43.040 align:start position:0% like to think about when i'm 00:03:43.040 --> 00:03:44.869 align:start position:0% like to think about when i'm working<00:03:43.280> with<00:03:43.440> this<00:03:43.599> problem<00:03:44.319> is<00:03:44.480> that<00:03:44.720> we 00:03:44.869 --> 00:03:44.879 align:start position:0% working with this problem is that we 00:03:44.879 --> 00:03:47.670 align:start position:0% working with this problem is that we tend<00:03:45.040> to<00:03:45.120> break<00:03:45.519> time<00:03:46.159> into<00:03:46.480> ranges<00:03:47.280> ranges 00:03:47.670 --> 00:03:47.680 align:start position:0% tend to break time into ranges ranges 00:03:47.680 --> 00:03:49.350 align:start position:0% tend to break time into ranges ranges between<00:03:47.920> one<00:03:48.159> instant<00:03:48.480> and<00:03:48.640> another<00:03:48.959> instant 00:03:49.350 --> 00:03:49.360 align:start position:0% between one instant and another instant 00:03:49.360 --> 00:03:51.350 align:start position:0% between one instant and another instant in<00:03:49.519> time 00:03:51.350 --> 00:03:51.360 align:start position:0% in time 00:03:51.360 --> 00:03:52.710 align:start position:0% in time this<00:03:51.519> is<00:03:51.680> useful 00:03:52.710 --> 00:03:52.720 align:start position:0% this is useful 00:03:52.720 --> 00:03:55.270 align:start position:0% this is useful this<00:03:52.959> is<00:03:53.040> a<00:03:53.120> useful<00:03:53.360> way<00:03:53.519> to<00:03:53.680> abstract<00:03:54.159> over<00:03:54.879> uh 00:03:55.270 --> 00:03:55.280 align:start position:0% this is a useful way to abstract over uh 00:03:55.280 --> 00:03:57.589 align:start position:0% this is a useful way to abstract over uh units<00:03:55.599> of<00:03:55.680> time<00:03:56.239> such<00:03:56.480> as<00:03:56.560> you<00:03:56.720> know<00:03:57.040> seconds 00:03:57.589 --> 00:03:57.599 align:start position:0% units of time such as you know seconds 00:03:57.599 --> 00:04:00.550 align:start position:0% units of time such as you know seconds minutes<00:03:58.239> hours<00:03:59.040> years<00:03:59.360> millennia<00:04:00.319> they're 00:04:00.550 --> 00:04:00.560 align:start position:0% minutes hours years millennia they're 00:04:00.560 --> 00:04:02.229 align:start position:0% minutes hours years millennia they're all<00:04:00.720> just<00:04:00.959> points<00:04:01.200> between<00:04:01.599> one<00:04:01.840> incident<00:04:02.159> and 00:04:02.229 --> 00:04:02.239 align:start position:0% all just points between one incident and 00:04:02.239 --> 00:04:05.830 align:start position:0% all just points between one incident and another<00:04:02.959> time 00:04:05.830 --> 00:04:05.840 align:start position:0% 00:04:05.840 --> 00:04:08.229 align:start position:0% so<00:04:06.159> when<00:04:06.400> i<00:04:06.480> was<00:04:06.879> wanting<00:04:07.120> to<00:04:07.280> work<00:04:07.439> with<00:04:07.840> time 00:04:08.229 --> 00:04:08.239 align:start position:0% so when i was wanting to work with time 00:04:08.239 --> 00:04:09.830 align:start position:0% so when i was wanting to work with time and<00:04:08.480> when<00:04:08.640> i<00:04:08.720> was<00:04:08.879> discussing<00:04:09.280> the<00:04:09.439> idea<00:04:09.680> of 00:04:09.830 --> 00:04:09.840 align:start position:0% and when i was discussing the idea of 00:04:09.840 --> 00:04:11.830 align:start position:0% and when i was discussing the idea of alan<00:04:10.239> there's<00:04:10.799> really<00:04:11.040> only<00:04:11.280> two<00:04:11.519> things<00:04:11.760> that 00:04:11.830 --> 00:04:11.840 align:start position:0% alan there's really only two things that 00:04:11.840 --> 00:04:13.990 align:start position:0% alan there's really only two things that i<00:04:12.080> want<00:04:12.239> to<00:04:12.319> be<00:04:12.400> concerned<00:04:12.799> with<00:04:12.959> when<00:04:13.200> i'm 00:04:13.990 --> 00:04:14.000 align:start position:0% i want to be concerned with when i'm 00:04:14.000 --> 00:04:15.910 align:start position:0% i want to be concerned with when i'm trying<00:04:14.239> to<00:04:14.480> conceive<00:04:14.879> of<00:04:14.959> cyclic<00:04:15.360> time 00:04:15.910 --> 00:04:15.920 align:start position:0% trying to conceive of cyclic time 00:04:15.920 --> 00:04:17.749 align:start position:0% trying to conceive of cyclic time periods<00:04:16.639> it's<00:04:16.799> a<00:04:16.880> range<00:04:17.199> between<00:04:17.519> two 00:04:17.749 --> 00:04:17.759 align:start position:0% periods it's a range between two 00:04:17.759 --> 00:04:19.990 align:start position:0% periods it's a range between two instances<00:04:18.560> and<00:04:18.720> if<00:04:18.799> we 00:04:19.990 --> 00:04:20.000 align:start position:0% instances and if we 00:04:20.000 --> 00:04:22.069 align:start position:0% instances and if we agree<00:04:20.320> upon<00:04:20.560> a<00:04:20.639> convention<00:04:21.199> for<00:04:21.440> expressing<00:04:21.919> a 00:04:22.069 --> 00:04:22.079 align:start position:0% agree upon a convention for expressing a 00:04:22.079 --> 00:04:23.430 align:start position:0% agree upon a convention for expressing a period<00:04:22.479> of<00:04:22.560> time 00:04:23.430 --> 00:04:23.440 align:start position:0% period of time 00:04:23.440 --> 00:04:25.909 align:start position:0% period of time uh<00:04:23.840> in<00:04:24.160> in<00:04:24.320> my<00:04:24.479> library<00:04:25.199> i'm<00:04:25.600> using<00:04:25.840> a 00:04:25.909 --> 00:04:25.919 align:start position:0% uh in in my library i'm using a 00:04:25.919 --> 00:04:27.749 align:start position:0% uh in in my library i'm using a convention<00:04:26.400> of<00:04:26.560> a<00:04:26.639> vector<00:04:26.960> that<00:04:27.199> has<00:04:27.360> a<00:04:27.440> start 00:04:27.749 --> 00:04:27.759 align:start position:0% convention of a vector that has a start 00:04:27.759 --> 00:04:29.749 align:start position:0% convention of a vector that has a start point<00:04:27.919> and<00:04:28.080> an<00:04:28.240> end<00:04:28.400> point<00:04:28.560> and<00:04:28.720> that's<00:04:28.960> it 00:04:29.749 --> 00:04:29.759 align:start position:0% point and an end point and that's it 00:04:29.759 --> 00:04:30.870 align:start position:0% point and an end point and that's it um 00:04:30.870 --> 00:04:30.880 align:start position:0% um 00:04:30.880 --> 00:04:33.510 align:start position:0% um and<00:04:31.280> the<00:04:31.440> idea<00:04:31.680> of<00:04:31.840> cycles<00:04:32.320> which<00:04:32.639> are 00:04:33.510 --> 00:04:33.520 align:start position:0% and the idea of cycles which are 00:04:33.520 --> 00:04:35.510 align:start position:0% and the idea of cycles which are repetitive<00:04:34.160> periods<00:04:34.720> uh<00:04:35.040> you<00:04:35.199> think<00:04:35.360> of 00:04:35.510 --> 00:04:35.520 align:start position:0% repetitive periods uh you think of 00:04:35.520 --> 00:04:37.749 align:start position:0% repetitive periods uh you think of cycles<00:04:36.000> as<00:04:36.240> being<00:04:36.560> a<00:04:36.720> generator<00:04:37.440> that<00:04:37.600> would 00:04:37.749 --> 00:04:37.759 align:start position:0% cycles as being a generator that would 00:04:37.759 --> 00:04:39.749 align:start position:0% cycles as being a generator that would create<00:04:38.080> multiple<00:04:38.479> periods<00:04:39.280> that<00:04:39.520> are 00:04:39.749 --> 00:04:39.759 align:start position:0% create multiple periods that are 00:04:39.759 --> 00:04:43.430 align:start position:0% create multiple periods that are self-similar 00:04:43.430 --> 00:04:43.440 align:start position:0% 00:04:43.440 --> 00:04:45.670 align:start position:0% and<00:04:43.759> the<00:04:43.919> real<00:04:44.080> problem<00:04:44.400> is 00:04:45.670 --> 00:04:45.680 align:start position:0% and the real problem is 00:04:45.680 --> 00:04:50.710 align:start position:0% and the real problem is time<00:04:45.919> i<00:04:46.160> think<00:04:46.479> is<00:04:46.639> in<00:04:46.720> these<00:04:46.960> cycles<00:04:47.440> because 00:04:50.710 --> 00:04:50.720 align:start position:0% 00:04:50.720 --> 00:04:52.629 align:start position:0% most<00:04:51.199> cycles<00:04:51.680> are<00:04:51.840> pretty<00:04:52.000> simple<00:04:52.320> right 00:04:52.629 --> 00:04:52.639 align:start position:0% most cycles are pretty simple right 00:04:52.639 --> 00:04:54.790 align:start position:0% most cycles are pretty simple right seconds<00:04:53.120> are<00:04:53.360> uniform<00:04:54.160> no<00:04:54.400> second<00:04:54.720> is 00:04:54.790 --> 00:04:54.800 align:start position:0% seconds are uniform no second is 00:04:54.800 --> 00:04:56.150 align:start position:0% seconds are uniform no second is different<00:04:55.040> from<00:04:55.199> another<00:04:55.520> second<00:04:55.840> in<00:04:55.919> terms 00:04:56.150 --> 00:04:56.160 align:start position:0% different from another second in terms 00:04:56.160 --> 00:04:59.510 align:start position:0% different from another second in terms of<00:04:56.240> the<00:04:56.400> actual<00:04:57.199> span<00:04:57.520> of<00:04:57.680> time<00:04:58.000> it's<00:04:58.320> uh 00:04:59.510 --> 00:04:59.520 align:start position:0% of the actual span of time it's uh 00:04:59.520 --> 00:05:01.830 align:start position:0% of the actual span of time it's uh it's<00:04:59.680> tracing<00:05:00.080> out<00:05:00.639> this<00:05:00.880> holds<00:05:01.199> true<00:05:01.680> all<00:05:01.840> the 00:05:01.830 --> 00:05:01.840 align:start position:0% it's tracing out this holds true all the 00:05:01.840 --> 00:05:03.270 align:start position:0% it's tracing out this holds true all the way<00:05:02.000> up<00:05:02.080> through<00:05:02.400> weeks<00:05:02.800> when<00:05:03.039> we<00:05:03.120> start 00:05:03.270 --> 00:05:03.280 align:start position:0% way up through weeks when we start 00:05:03.280 --> 00:05:04.790 align:start position:0% way up through weeks when we start getting<00:05:03.520> the<00:05:03.600> months<00:05:04.000> let's<00:05:04.240> get<00:05:04.479> really<00:05:04.639> kind 00:05:04.790 --> 00:05:04.800 align:start position:0% getting the months let's get really kind 00:05:04.800 --> 00:05:07.350 align:start position:0% getting the months let's get really kind of<00:05:04.880> fuzzy<00:05:05.440> they're<00:05:05.759> a<00:05:05.840> nasty<00:05:06.240> special<00:05:06.639> case<00:05:07.199> if 00:05:07.350 --> 00:05:07.360 align:start position:0% of fuzzy they're a nasty special case if 00:05:07.360 --> 00:05:08.790 align:start position:0% of fuzzy they're a nasty special case if we're<00:05:07.600> talking<00:05:07.840> about<00:05:08.160> months<00:05:08.400> the<00:05:08.479> way<00:05:08.639> that 00:05:08.790 --> 00:05:08.800 align:start position:0% we're talking about months the way that 00:05:08.800 --> 00:05:10.629 align:start position:0% we're talking about months the way that humans<00:05:09.120> talk<00:05:09.360> about<00:05:09.600> months<00:05:10.160> because<00:05:10.560> you 00:05:10.629 --> 00:05:10.639 align:start position:0% humans talk about months because you 00:05:10.639 --> 00:05:13.590 align:start position:0% humans talk about months because you know<00:05:10.800> february<00:05:11.280> has<00:05:11.520> 28<00:05:11.840> days 00:05:13.590 --> 00:05:13.600 align:start position:0% know february has 28 days 00:05:13.600 --> 00:05:16.230 align:start position:0% know february has 28 days each<00:05:13.840> month<00:05:14.080> has<00:05:14.560> a<00:05:14.800> very<00:05:15.120> slightly<00:05:15.520> different 00:05:16.230 --> 00:05:16.240 align:start position:0% each month has a very slightly different 00:05:16.240 --> 00:05:22.830 align:start position:0% each month has a very slightly different duration<00:05:17.120> and<00:05:17.440> that<00:05:17.680> makes<00:05:18.000> it<00:05:18.320> a<00:05:18.479> little<00:05:18.639> bit 00:05:22.830 --> 00:05:22.840 align:start position:0% 00:05:22.840 --> 00:05:25.110 align:start position:0% complex<00:05:23.919> but 00:05:25.110 --> 00:05:25.120 align:start position:0% complex but 00:05:25.120 --> 00:05:26.550 align:start position:0% complex but there's<00:05:25.440> a<00:05:25.520> nice<00:05:25.759> little<00:05:26.000> cheat<00:05:26.240> that<00:05:26.400> you<00:05:26.479> can 00:05:26.550 --> 00:05:26.560 align:start position:0% there's a nice little cheat that you can 00:05:26.560 --> 00:05:28.629 align:start position:0% there's a nice little cheat that you can do<00:05:27.039> it's<00:05:27.199> called<00:05:27.520> using<00:05:27.759> java<00:05:28.080> util<00:05:28.320> calendar 00:05:28.629 --> 00:05:28.639 align:start position:0% do it's called using java util calendar 00:05:28.639 --> 00:05:31.430 align:start position:0% do it's called using java util calendar which<00:05:28.880> handles<00:05:29.199> all<00:05:29.360> the<00:05:29.600> live<00:05:29.840> imports<00:05:30.560> um 00:05:31.430 --> 00:05:31.440 align:start position:0% which handles all the live imports um 00:05:31.440 --> 00:05:32.629 align:start position:0% which handles all the live imports um and<00:05:31.520> that's<00:05:31.759> basically<00:05:32.000> what<00:05:32.160> i<00:05:32.240> did<00:05:32.400> is<00:05:32.479> i 00:05:32.629 --> 00:05:32.639 align:start position:0% and that's basically what i did is i 00:05:32.639 --> 00:05:33.909 align:start position:0% and that's basically what i did is i built<00:05:32.880> up<00:05:33.039> uh 00:05:33.909 --> 00:05:33.919 align:start position:0% built up uh 00:05:33.919 --> 00:05:35.270 align:start position:0% built up uh this<00:05:34.160> idea<00:05:34.560> of 00:05:35.270 --> 00:05:35.280 align:start position:0% this idea of 00:05:35.280 --> 00:05:37.189 align:start position:0% this idea of cycles<00:05:35.680> and<00:05:35.840> periods<00:05:36.240> on<00:05:36.320> top<00:05:36.560> of<00:05:36.639> java<00:05:36.880> util 00:05:37.189 --> 00:05:37.199 align:start position:0% cycles and periods on top of java util 00:05:37.199 --> 00:05:39.990 align:start position:0% cycles and periods on top of java util calendar<00:05:37.600> and<00:05:37.680> i<00:05:37.840> know<00:05:38.000> that's<00:05:38.320> not<00:05:38.479> me 00:05:39.990 --> 00:05:40.000 align:start position:0% calendar and i know that's not me 00:05:40.000 --> 00:05:42.710 align:start position:0% calendar and i know that's not me there's<00:05:40.240> not<00:05:40.400> a<00:05:40.400> whole<00:05:40.560> lot<00:05:40.720> to<00:05:40.960> it<00:05:41.520> right<00:05:41.759> now 00:05:42.710 --> 00:05:42.720 align:start position:0% there's not a whole lot to it right now 00:05:42.720 --> 00:05:44.629 align:start position:0% there's not a whole lot to it right now i<00:05:42.880> think<00:05:43.039> the<00:05:43.199> main<00:05:43.440> points<00:05:43.919> are 00:05:44.629 --> 00:05:44.639 align:start position:0% i think the main points are 00:05:44.639 --> 00:05:46.070 align:start position:0% i think the main points are one<00:05:44.880> function<00:05:45.199> we<00:05:45.280> call<00:05:45.520> it<00:05:45.680> i<00:05:45.840> call<00:05:46.000> it 00:05:46.070 --> 00:05:46.080 align:start position:0% one function we call it i call it 00:05:46.080 --> 00:05:48.710 align:start position:0% one function we call it i call it periods<00:05:46.800> and<00:05:47.039> you<00:05:47.280> hand<00:05:47.440> it<00:05:47.520> a<00:05:47.600> keyword<00:05:48.160> saying 00:05:48.710 --> 00:05:48.720 align:start position:0% periods and you hand it a keyword saying 00:05:48.720 --> 00:05:50.390 align:start position:0% periods and you hand it a keyword saying what<00:05:48.880> do<00:05:49.039> you<00:05:49.120> want<00:05:49.600> the 00:05:50.390 --> 00:05:50.400 align:start position:0% what do you want the 00:05:50.400 --> 00:05:51.430 align:start position:0% what do you want the uh 00:05:51.430 --> 00:05:51.440 align:start position:0% uh 00:05:51.440 --> 00:05:53.430 align:start position:0% uh six<00:05:51.759> cycle<00:05:52.080> periods 00:05:53.430 --> 00:05:53.440 align:start position:0% six cycle periods 00:05:53.440 --> 00:05:55.510 align:start position:0% six cycle periods and<00:05:53.919> it<00:05:54.080> will<00:05:54.240> return<00:05:54.560> you<00:05:54.800> an<00:05:54.960> infinite<00:05:55.199> lazy 00:05:55.510 --> 00:05:55.520 align:start position:0% and it will return you an infinite lazy 00:05:55.520 --> 00:05:57.749 align:start position:0% and it will return you an infinite lazy sequence<00:05:56.080> of 00:05:57.749 --> 00:05:57.759 align:start position:0% sequence of 00:05:57.759 --> 00:05:59.830 align:start position:0% sequence of periods<00:05:58.240> just<00:05:58.479> these<00:05:58.639> vectors<00:05:59.199> of<00:05:59.600> two 00:05:59.830 --> 00:05:59.840 align:start position:0% periods just these vectors of two 00:05:59.840 --> 00:06:02.550 align:start position:0% periods just these vectors of two instances<00:06:00.720> uh<00:06:01.039> such<00:06:01.280> that<00:06:01.600> they 00:06:02.550 --> 00:06:02.560 align:start position:0% instances uh such that they 00:06:02.560 --> 00:06:06.070 align:start position:0% instances uh such that they dovetail<00:06:02.960> nicely<00:06:03.680> and<00:06:04.319> it<00:06:04.560> starts<00:06:04.800> with<00:06:05.280> the 00:06:06.070 --> 00:06:06.080 align:start position:0% dovetail nicely and it starts with the 00:06:06.080 --> 00:06:08.309 align:start position:0% dovetail nicely and it starts with the instant<00:06:06.560> you<00:06:06.639> call<00:06:06.880> the<00:06:06.960> function<00:06:07.600> by<00:06:07.759> default 00:06:08.309 --> 00:06:08.319 align:start position:0% instant you call the function by default 00:06:08.319 --> 00:06:09.830 align:start position:0% instant you call the function by default you<00:06:08.400> can<00:06:08.479> read<00:06:08.639> the<00:06:08.720> figure 00:06:09.830 --> 00:06:09.840 align:start position:0% you can read the figure 00:06:09.840 --> 00:06:11.670 align:start position:0% you can read the figure but<00:06:10.080> it<00:06:10.160> generates<00:06:10.560> this<00:06:10.720> infinite<00:06:11.039> sequence 00:06:11.670 --> 00:06:11.680 align:start position:0% but it generates this infinite sequence 00:06:11.680 --> 00:06:14.070 align:start position:0% but it generates this infinite sequence and<00:06:11.840> now<00:06:12.080> you<00:06:12.240> have<00:06:12.479> a<00:06:12.560> cyclic<00:06:12.880> generator 00:06:14.070 --> 00:06:14.080 align:start position:0% and now you have a cyclic generator 00:06:14.080 --> 00:06:17.029 align:start position:0% and now you have a cyclic generator and<00:06:14.639> the<00:06:15.199> other<00:06:15.520> i<00:06:15.680> think<00:06:16.319> important<00:06:16.720> tool 00:06:17.029 --> 00:06:17.039 align:start position:0% and the other i think important tool 00:06:17.039 --> 00:06:19.909 align:start position:0% and the other i think important tool here<00:06:17.520> is<00:06:17.840> bounded<00:06:18.240> cycles<00:06:18.639> in<00:06:19.120> uh<00:06:19.680> in<00:06:19.759> this 00:06:19.909 --> 00:06:19.919 align:start position:0% here is bounded cycles in uh in this 00:06:19.919 --> 00:06:21.189 align:start position:0% here is bounded cycles in uh in this example 00:06:21.189 --> 00:06:21.199 align:start position:0% example 00:06:21.199 --> 00:06:22.870 align:start position:0% example i<00:06:21.360> would<00:06:21.440> like<00:06:21.600> you<00:06:21.919> to<00:06:22.319> indulge<00:06:22.639> me<00:06:22.800> and 00:06:22.870 --> 00:06:22.880 align:start position:0% i would like you to indulge me and 00:06:22.880 --> 00:06:24.390 align:start position:0% i would like you to indulge me and pretend<00:06:23.199> that<00:06:23.280> november<00:06:23.680> was<00:06:23.840> bound<00:06:24.080> to<00:06:24.319> a 00:06:24.390 --> 00:06:24.400 align:start position:0% pretend that november was bound to a 00:06:24.400 --> 00:06:26.710 align:start position:0% pretend that november was bound to a vector<00:06:25.120> that<00:06:25.520> included<00:06:25.919> the<00:06:26.080> first<00:06:26.400> incident 00:06:26.710 --> 00:06:26.720 align:start position:0% vector that included the first incident 00:06:26.720 --> 00:06:28.230 align:start position:0% vector that included the first incident of<00:06:26.800> the<00:06:26.880> month<00:06:27.120> of<00:06:27.199> november<00:06:27.600> and<00:06:27.680> the<00:06:27.840> last 00:06:28.230 --> 00:06:28.240 align:start position:0% of the month of november and the last 00:06:28.240 --> 00:06:30.230 align:start position:0% of the month of november and the last instant<00:06:28.800> of<00:06:28.960> the<00:06:29.039> month<00:06:29.280> of<00:06:29.360> november<00:06:30.080> and 00:06:30.230 --> 00:06:30.240 align:start position:0% instant of the month of november and 00:06:30.240 --> 00:06:32.150 align:start position:0% instant of the month of november and what<00:06:30.639> about<00:06:30.880> the<00:06:30.960> cycle<00:06:31.280> does<00:06:31.520> is<00:06:31.759> it<00:06:31.840> breaks 00:06:32.150 --> 00:06:32.160 align:start position:0% what about the cycle does is it breaks 00:06:32.160 --> 00:06:35.270 align:start position:0% what about the cycle does is it breaks down<00:06:32.560> that<00:06:32.800> month<00:06:33.039> of<00:06:33.120> november<00:06:34.000> into<00:06:34.800> another 00:06:35.270 --> 00:06:35.280 align:start position:0% down that month of november into another 00:06:35.280 --> 00:06:37.909 align:start position:0% down that month of november into another of<00:06:35.919> another<00:06:36.319> series<00:06:36.720> of<00:06:36.880> periods<00:06:37.680> at<00:06:37.840> the 00:06:37.909 --> 00:06:37.919 align:start position:0% of another series of periods at the 00:06:37.919 --> 00:06:39.510 align:start position:0% of another series of periods at the resolution<00:06:38.400> of<00:06:38.560> days 00:06:39.510 --> 00:06:39.520 align:start position:0% resolution of days 00:06:39.520 --> 00:06:41.830 align:start position:0% resolution of days we've<00:06:39.759> now<00:06:39.919> got<00:06:40.000> a<00:06:40.080> sequence<00:06:40.639> of<00:06:41.199> all<00:06:41.360> the<00:06:41.520> days 00:06:41.830 --> 00:06:41.840 align:start position:0% we've now got a sequence of all the days 00:06:41.840 --> 00:06:44.629 align:start position:0% we've now got a sequence of all the days in<00:06:41.919> november<00:06:42.560> represented<00:06:43.520> using<00:06:43.759> periods 00:06:44.629 --> 00:06:44.639 align:start position:0% in november represented using periods 00:06:44.639 --> 00:06:47.110 align:start position:0% in november represented using periods and<00:06:45.039> we<00:06:45.199> can<00:06:45.360> start<00:06:45.600> doing<00:06:45.840> computation 00:06:47.110 --> 00:06:47.120 align:start position:0% and we can start doing computation 00:06:47.120 --> 00:06:48.790 align:start position:0% and we can start doing computation based<00:06:47.520> on 00:06:48.790 --> 00:06:48.800 align:start position:0% based on 00:06:48.800 --> 00:06:51.110 align:start position:0% based on what<00:06:48.960> days<00:06:49.280> are<00:06:49.440> important 00:06:51.110 --> 00:06:51.120 align:start position:0% what days are important 00:06:51.120 --> 00:06:52.790 align:start position:0% what days are important the<00:06:51.280> example<00:06:51.599> i<00:06:51.759> use<00:06:51.919> in<00:06:52.000> the<00:06:52.080> readme<00:06:52.479> for<00:06:52.639> this 00:06:52.790 --> 00:06:52.800 align:start position:0% the example i use in the readme for this 00:06:52.800 --> 00:06:55.670 align:start position:0% the example i use in the readme for this library<00:06:53.680> is<00:06:54.240> to<00:06:54.400> try<00:06:54.639> and<00:06:54.800> generate<00:06:55.280> all<00:06:55.520> of 00:06:55.670 --> 00:06:55.680 align:start position:0% library is to try and generate all of 00:06:55.680 --> 00:06:57.589 align:start position:0% library is to try and generate all of the<00:06:56.000> tri-closure<00:06:56.560> meetings 00:06:57.589 --> 00:06:57.599 align:start position:0% the tri-closure meetings 00:06:57.599 --> 00:06:58.870 align:start position:0% the tri-closure meetings that<00:06:57.759> relevance<00:06:58.160> holds<00:06:58.479> at<00:06:58.560> relevance 00:06:58.870 --> 00:06:58.880 align:start position:0% that relevance holds at relevance 00:06:58.880 --> 00:07:00.070 align:start position:0% that relevance holds at relevance headquarters 00:07:00.070 --> 00:07:00.080 align:start position:0% headquarters 00:07:00.080 --> 00:07:01.670 align:start position:0% headquarters they<00:07:00.240> occur<00:07:00.560> on<00:07:00.720> the<00:07:00.800> third<00:07:01.039> wednesday<00:07:01.520> of 00:07:01.670 --> 00:07:01.680 align:start position:0% they occur on the third wednesday of 00:07:01.680 --> 00:07:06.150 align:start position:0% they occur on the third wednesday of every<00:07:01.919> single<00:07:02.240> month<00:07:02.639> at<00:07:02.800> 6<00:07:03.039> 00<00:07:03.120> pm<00:07:03.919> uh<00:07:04.400> and<00:07:04.560> the 00:07:06.150 --> 00:07:06.160 align:start position:0% every single month at 6 00 pm uh and the 00:07:06.160 --> 00:07:07.589 align:start position:0% every single month at 6 00 pm uh and the way<00:07:06.479> that<00:07:06.639> i<00:07:06.720> basically<00:07:07.039> go<00:07:07.199> through<00:07:07.440> this 00:07:07.589 --> 00:07:07.599 align:start position:0% way that i basically go through this 00:07:07.599 --> 00:07:09.830 align:start position:0% way that i basically go through this process<00:07:08.160> is<00:07:08.720> decompose<00:07:09.280> the<00:07:09.360> months<00:07:09.599> into 00:07:09.830 --> 00:07:09.840 align:start position:0% process is decompose the months into 00:07:09.840 --> 00:07:12.230 align:start position:0% process is decompose the months into days<00:07:10.560> i<00:07:10.880> have<00:07:11.120> some<00:07:11.280> predicate<00:07:11.680> functions<00:07:12.080> so 00:07:12.230 --> 00:07:12.240 align:start position:0% days i have some predicate functions so 00:07:12.240 --> 00:07:14.390 align:start position:0% days i have some predicate functions so that<00:07:12.400> we<00:07:12.560> can<00:07:12.880> examine<00:07:13.360> whether<00:07:13.599> our<00:07:13.919> a<00:07:14.000> day<00:07:14.240> is 00:07:14.390 --> 00:07:14.400 align:start position:0% that we can examine whether our a day is 00:07:14.400 --> 00:07:16.550 align:start position:0% that we can examine whether our a day is wednesday<00:07:14.880> so<00:07:15.280> we<00:07:15.440> filter<00:07:15.840> all<00:07:16.000> the<00:07:16.160> days<00:07:16.400> down 00:07:16.550 --> 00:07:16.560 align:start position:0% wednesday so we filter all the days down 00:07:16.560 --> 00:07:18.309 align:start position:0% wednesday so we filter all the days down to<00:07:16.720> only<00:07:16.960> the<00:07:17.039> wednesdays<00:07:17.759> block<00:07:18.000> the<00:07:18.080> third 00:07:18.309 --> 00:07:18.319 align:start position:0% to only the wednesdays block the third 00:07:18.319 --> 00:07:20.150 align:start position:0% to only the wednesdays block the third one<00:07:18.479> out<00:07:18.639> of<00:07:18.720> there<00:07:19.360> uh 00:07:20.150 --> 00:07:20.160 align:start position:0% one out of there uh 00:07:20.160 --> 00:07:22.469 align:start position:0% one out of there uh find<00:07:20.720> all<00:07:20.880> the<00:07:21.039> hours<00:07:21.360> in<00:07:21.440> that<00:07:21.680> bag<00:07:22.080> pluck<00:07:22.400> out 00:07:22.469 --> 00:07:22.479 align:start position:0% find all the hours in that bag pluck out 00:07:22.479 --> 00:07:25.350 align:start position:0% find all the hours in that bag pluck out 6<00:07:22.720> p.m<00:07:23.039> and<00:07:23.120> now<00:07:23.360> we've<00:07:23.520> got<00:07:23.840> the<00:07:24.080> period<00:07:24.479> for 00:07:25.350 --> 00:07:25.360 align:start position:0% 6 p.m and now we've got the period for 00:07:25.360 --> 00:07:26.950 align:start position:0% 6 p.m and now we've got the period for when<00:07:25.759> the<00:07:25.919> tri-closure<00:07:26.400> meeting<00:07:26.639> is<00:07:26.800> going<00:07:26.880> to 00:07:26.950 --> 00:07:26.960 align:start position:0% when the tri-closure meeting is going to 00:07:26.960 --> 00:07:28.550 align:start position:0% when the tri-closure meeting is going to be<00:07:27.039> occurring 00:07:28.550 --> 00:07:28.560 align:start position:0% be occurring 00:07:28.560 --> 00:07:29.990 align:start position:0% be occurring i<00:07:28.639> think<00:07:28.800> this<00:07:28.960> is<00:07:29.120> a<00:07:29.199> useful<00:07:29.520> way<00:07:29.680> to<00:07:29.840> think 00:07:29.990 --> 00:07:30.000 align:start position:0% i think this is a useful way to think 00:07:30.000 --> 00:07:32.790 align:start position:0% i think this is a useful way to think about<00:07:30.720> recurring<00:07:31.280> cyclic<00:07:31.680> time 00:07:32.790 --> 00:07:32.800 align:start position:0% about recurring cyclic time 00:07:32.800 --> 00:07:35.270 align:start position:0% about recurring cyclic time but<00:07:33.440> it's<00:07:33.759> also<00:07:34.080> an<00:07:34.240> immature<00:07:34.639> idea<00:07:34.880> i<00:07:34.960> haven't 00:07:35.270 --> 00:07:35.280 align:start position:0% but it's also an immature idea i haven't 00:07:35.280 --> 00:07:39.909 align:start position:0% but it's also an immature idea i haven't spent<00:07:35.520> a<00:07:35.599> whole<00:07:35.759> lot<00:07:35.919> of<00:07:36.000> time<00:07:36.240> working<00:07:36.560> on 00:07:39.909 --> 00:07:39.919 align:start position:0% 00:07:39.919 --> 00:07:43.350 align:start position:0% but<00:07:40.560> these<00:07:40.800> are<00:07:40.960> these<00:07:41.199> are<00:07:41.599> the<00:07:42.240> kind<00:07:42.400> of 00:07:43.350 --> 00:07:43.360 align:start position:0% but these are these are the kind of 00:07:43.360 --> 00:07:45.029 align:start position:0% but these are these are the kind of tools<00:07:43.599> i<00:07:43.680> had<00:07:43.840> to<00:07:44.000> use<00:07:44.160> to<00:07:44.319> build<00:07:44.560> up<00:07:44.639> to<00:07:44.800> this 00:07:45.029 --> 00:07:45.039 align:start position:0% tools i had to use to build up to this 00:07:45.039 --> 00:07:46.950 align:start position:0% tools i had to use to build up to this point<00:07:45.759> uh 00:07:46.950 --> 00:07:46.960 align:start position:0% point uh 00:07:46.960 --> 00:07:48.550 align:start position:0% point uh one<00:07:47.120> of<00:07:47.199> them<00:07:47.440> is<00:07:47.520> retrieving<00:07:48.000> our<00:07:48.160> concepts 00:07:48.550 --> 00:07:48.560 align:start position:0% one of them is retrieving our concepts 00:07:48.560 --> 00:07:50.710 align:start position:0% one of them is retrieving our concepts of<00:07:48.720> what<00:07:48.960> are<00:07:49.120> natural<00:07:49.520> boundaries<00:07:50.400> you<00:07:50.479> can 00:07:50.710 --> 00:07:50.720 align:start position:0% of what are natural boundaries you can 00:07:50.720 --> 00:07:52.550 align:start position:0% of what are natural boundaries you can use<00:07:51.280> there<00:07:51.520> there<00:07:51.680> are<00:07:52.080> many<00:07:52.319> many 00:07:52.550 --> 00:07:52.560 align:start position:0% use there there are many many 00:07:52.560 --> 00:07:55.110 align:start position:0% use there there are many many milliseconds<00:07:53.120> out<00:07:53.280> there<00:07:53.840> uh<00:07:54.160> that<00:07:54.400> are<00:07:54.560> not 00:07:55.110 --> 00:07:55.120 align:start position:0% milliseconds out there uh that are not 00:07:55.120 --> 00:07:57.430 align:start position:0% milliseconds out there uh that are not cleanly<00:07:55.520> on<00:07:55.680> the<00:07:55.759> boundary<00:07:56.240> of<00:07:56.560> you<00:07:56.639> know<00:07:57.199> the 00:07:57.430 --> 00:07:57.440 align:start position:0% cleanly on the boundary of you know the 00:07:57.440 --> 00:07:59.670 align:start position:0% cleanly on the boundary of you know the instant<00:07:57.840> when<00:07:58.080> we<00:07:58.639> change<00:07:58.960> from<00:07:59.199> tuesday<00:07:59.520> to 00:07:59.670 --> 00:07:59.680 align:start position:0% instant when we change from tuesday to 00:07:59.680 --> 00:08:01.430 align:start position:0% instant when we change from tuesday to wednesday<00:08:00.160> for<00:08:00.400> example 00:08:01.430 --> 00:08:01.440 align:start position:0% wednesday for example 00:08:01.440 --> 00:08:03.909 align:start position:0% wednesday for example it's<00:08:01.599> useful<00:08:01.919> to<00:08:02.000> be<00:08:02.160> able<00:08:02.240> to<00:08:02.319> find<00:08:03.039> these 00:08:03.909 --> 00:08:03.919 align:start position:0% it's useful to be able to find these 00:08:03.919 --> 00:08:06.150 align:start position:0% it's useful to be able to find these cut<00:08:04.240> points<00:08:04.720> and<00:08:04.960> to<00:08:05.120> specify<00:08:05.680> periods 00:08:06.150 --> 00:08:06.160 align:start position:0% cut points and to specify periods 00:08:06.160 --> 00:08:08.230 align:start position:0% cut points and to specify periods relative<00:08:06.720> to<00:08:06.960> any<00:08:07.199> arbitrary<00:08:07.680> millisecond 00:08:08.230 --> 00:08:08.240 align:start position:0% relative to any arbitrary millisecond 00:08:08.240 --> 00:08:10.309 align:start position:0% relative to any arbitrary millisecond within<00:08:08.639> that<00:08:08.800> period 00:08:10.309 --> 00:08:10.319 align:start position:0% within that period 00:08:10.319 --> 00:08:11.990 align:start position:0% within that period we<00:08:10.479> have<00:08:10.720> predicates<00:08:11.120> for<00:08:11.280> testing<00:08:11.680> human 00:08:11.990 --> 00:08:12.000 align:start position:0% we have predicates for testing human 00:08:12.000 --> 00:08:14.309 align:start position:0% we have predicates for testing human names<00:08:12.639> for<00:08:12.879> things<00:08:13.360> like<00:08:13.599> you<00:08:13.759> know<00:08:14.160> the 00:08:14.309 --> 00:08:14.319 align:start position:0% names for things like you know the 00:08:14.319 --> 00:08:16.550 align:start position:0% names for things like you know the wednesday<00:08:14.879> and<00:08:14.960> some<00:08:15.199> week<00:08:15.599> or<00:08:15.919> is<00:08:16.000> this<00:08:16.240> month 00:08:16.550 --> 00:08:16.560 align:start position:0% wednesday and some week or is this month 00:08:16.560 --> 00:08:17.510 align:start position:0% wednesday and some week or is this month july 00:08:17.510 --> 00:08:17.520 align:start position:0% july 00:08:17.520 --> 00:08:19.589 align:start position:0% july and<00:08:18.240> sorry 00:08:19.589 --> 00:08:19.599 align:start position:0% and sorry 00:08:19.599 --> 00:08:22.629 align:start position:0% and sorry okay<00:08:20.240> uh<00:08:20.720> and<00:08:21.120> we<00:08:21.280> can<00:08:22.000> in<00:08:22.160> the<00:08:22.240> library 00:08:22.629 --> 00:08:22.639 align:start position:0% okay uh and we can in the library 00:08:22.639 --> 00:08:24.790 align:start position:0% okay uh and we can in the library consume<00:08:23.039> either<00:08:23.360> dates<00:08:23.680> or<00:08:23.919> longs<00:08:24.400> uh 00:08:24.790 --> 00:08:24.800 align:start position:0% consume either dates or longs uh 00:08:24.800 --> 00:08:26.629 align:start position:0% consume either dates or longs uh interchangeably<00:08:25.599> the<00:08:25.759> convention<00:08:26.319> being 00:08:26.629 --> 00:08:26.639 align:start position:0% interchangeably the convention being 00:08:26.639 --> 00:08:28.230 align:start position:0% interchangeably the convention being that 00:08:28.230 --> 00:08:28.240 align:start position:0% that 00:08:28.240 --> 00:08:31.270 align:start position:0% that we<00:08:28.479> basically<00:08:29.120> shove<00:08:29.520> lungs<00:08:29.840> into<00:08:30.160> dates<00:08:30.479> or 00:08:31.270 --> 00:08:31.280 align:start position:0% we basically shove lungs into dates or 00:08:31.280 --> 00:08:34.469 align:start position:0% we basically shove lungs into dates or fold<00:08:31.520> the<00:08:31.599> mill<00:08:31.759> seconds<00:08:32.080> off<00:08:32.240> dates 00:08:34.469 --> 00:08:34.479 align:start position:0% fold the mill seconds off dates 00:08:34.479 --> 00:08:36.550 align:start position:0% fold the mill seconds off dates and<00:08:35.120> that's<00:08:35.360> basically<00:08:35.760> my<00:08:36.000> you<00:08:36.080> know<00:08:36.320> i<00:08:36.399> just 00:08:36.550 --> 00:08:36.560 align:start position:0% and that's basically my you know i just 00:08:36.560 --> 00:08:37.990 align:start position:0% and that's basically my you know i just want<00:08:36.719> to<00:08:36.800> introduce<00:08:37.120> this<00:08:37.279> concept<00:08:37.599> to<00:08:37.760> you 00:08:37.990 --> 00:08:38.000 align:start position:0% want to introduce this concept to you 00:08:38.000 --> 00:08:39.829 align:start position:0% want to introduce this concept to you that<00:08:38.159> you're<00:08:38.320> thinking<00:08:38.640> about<00:08:38.880> it<00:08:39.360> um<00:08:39.760> i'd 00:08:39.829 --> 00:08:39.839 align:start position:0% that you're thinking about it um i'd 00:08:39.839 --> 00:08:41.430 align:start position:0% that you're thinking about it um i'd like<00:08:40.000> to<00:08:40.159> invite<00:08:40.399> you<00:08:40.560> to<00:08:40.640> play<00:08:40.800> with<00:08:41.279> me<00:08:41.360> i 00:08:41.430 --> 00:08:41.440 align:start position:0% like to invite you to play with me i 00:08:41.440 --> 00:08:43.589 align:start position:0% like to invite you to play with me i have<00:08:41.519> it<00:08:41.680> on<00:08:41.839> github<00:08:42.719> and 00:08:43.589 --> 00:08:43.599 align:start position:0% have it on github and 00:08:43.599 --> 00:08:45.590 align:start position:0% have it on github and you<00:08:43.680> can<00:08:44.159> add<00:08:44.560> it's<00:08:44.720> also<00:08:45.200> pushed<00:08:45.440> out<00:08:45.519> to 00:08:45.590 --> 00:08:45.600 align:start position:0% you can add it's also pushed out to 00:08:45.600 --> 00:08:47.030 align:start position:0% you can add it's also pushed out to clojars<00:08:46.080> so<00:08:46.240> if<00:08:46.320> you're<00:08:46.480> interested<00:08:46.880> you 00:08:47.030 --> 00:08:47.040 align:start position:0% clojars so if you're interested you 00:08:47.040 --> 00:08:48.870 align:start position:0% clojars so if you're interested you could<00:08:47.360> uh<00:08:47.920> add<00:08:48.160> it<00:08:48.240> to<00:08:48.320> your<00:08:48.399> projects<00:08:48.720> and 00:08:48.870 --> 00:08:48.880 align:start position:0% could uh add it to your projects and 00:08:48.880 --> 00:08:50.710 align:start position:0% could uh add it to your projects and start<00:08:49.120> playing<00:08:49.360> with<00:08:49.519> it 00:08:50.710 --> 00:08:50.720 align:start position:0% start playing with it 00:08:50.720 --> 00:08:53.269 align:start position:0% start playing with it if<00:08:50.880> you'd<00:08:51.040> like<00:08:51.200> to<00:08:51.360> fork<00:08:51.600> the<00:08:51.680> work 00:08:53.269 --> 00:08:53.279 align:start position:0% if you'd like to fork the work 00:08:53.279 --> 00:08:55.670 align:start position:0% if you'd like to fork the work submit<00:08:53.680> pull<00:08:53.839> requests<00:08:54.640> or<00:08:54.880> report<00:08:55.279> issues<00:08:55.600> on 00:08:55.670 --> 00:08:55.680 align:start position:0% submit pull requests or report issues on 00:08:55.680 --> 00:08:57.430 align:start position:0% submit pull requests or report issues on the<00:08:55.760> library<00:08:56.080> i'd<00:08:56.320> be<00:08:56.480> very<00:08:56.720> appreciative<00:08:57.279> of 00:08:57.430 --> 00:08:57.440 align:start position:0% the library i'd be very appreciative of 00:08:57.440 --> 00:08:59.430 align:start position:0% the library i'd be very appreciative of it<00:08:57.920> uh<00:08:58.160> but<00:08:58.480> finally<00:08:58.800> the<00:08:58.959> last<00:08:59.120> thing<00:08:59.279> i'd 00:08:59.430 --> 00:08:59.440 align:start position:0% it uh but finally the last thing i'd 00:08:59.440 --> 00:09:01.430 align:start position:0% it uh but finally the last thing i'd like<00:08:59.519> to<00:08:59.680> invite<00:08:59.920> you<00:09:00.080> to<00:09:00.240> do<00:09:00.800> is<00:09:01.040> to<00:09:01.200> go 00:09:01.430 --> 00:09:01.440 align:start position:0% like to invite you to do is to go 00:09:01.440 --> 00:09:02.870 align:start position:0% like to invite you to do is to go digging<00:09:01.760> through<00:09:01.920> your<00:09:02.080> old<00:09:02.320> ideas<00:09:02.640> in<00:09:02.720> the 00:09:02.870 --> 00:09:02.880 align:start position:0% digging through your old ideas in the 00:09:02.880 --> 00:09:04.550 align:start position:0% digging through your old ideas in the past 00:09:04.550 --> 00:09:04.560 align:start position:0% past 00:09:04.560 --> 00:09:05.910 align:start position:0% past particularly<00:09:05.120> you<00:09:05.200> know<00:09:05.360> if<00:09:05.440> you've<00:09:05.600> had<00:09:05.760> a 00:09:05.910 --> 00:09:05.920 align:start position:0% particularly you know if you've had a 00:09:05.920 --> 00:09:08.630 align:start position:0% particularly you know if you've had a problem<00:09:06.160> in<00:09:06.320> the<00:09:06.399> past<00:09:06.880> that's 00:09:08.630 --> 00:09:08.640 align:start position:0% problem in the past that's 00:09:08.640 --> 00:09:11.110 align:start position:0% problem in the past that's defeated<00:09:09.120> you<00:09:09.279> you've<00:09:09.440> surrendered<00:09:09.920> to<00:09:10.480> and 00:09:11.110 --> 00:09:11.120 align:start position:0% defeated you you've surrendered to and 00:09:11.120 --> 00:09:12.550 align:start position:0% defeated you you've surrendered to and use<00:09:11.279> what<00:09:11.440> you've<00:09:11.600> learned<00:09:12.000> working<00:09:12.320> with 00:09:12.550 --> 00:09:12.560 align:start position:0% use what you've learned working with 00:09:12.560 --> 00:09:14.790 align:start position:0% use what you've learned working with closure<00:09:13.360> to<00:09:13.519> try<00:09:13.680> playing<00:09:14.000> with<00:09:14.080> it<00:09:14.240> again 00:09:14.790 --> 00:09:14.800 align:start position:0% closure to try playing with it again 00:09:14.800 --> 00:09:17.110 align:start position:0% closure to try playing with it again think<00:09:14.959> about<00:09:15.279> what<00:09:15.440> kind<00:09:15.600> of<00:09:15.760> new<00:09:16.000> solutions 00:09:17.110 --> 00:09:17.120 align:start position:0% think about what kind of new solutions 00:09:17.120 --> 00:09:18.870 align:start position:0% think about what kind of new solutions uh<00:09:17.600> you<00:09:17.760> can<00:09:18.000> find 00:09:18.870 --> 00:09:18.880 align:start position:0% uh you can find 00:09:18.880 --> 00:09:20.630 align:start position:0% uh you can find by<00:09:19.120> using<00:09:19.360> the<00:09:19.519> toolbox<00:09:19.920> the<00:09:20.000> closure<00:09:20.399> gives 00:09:20.630 --> 00:09:20.640 align:start position:0% by using the toolbox the closure gives 00:09:20.640 --> 00:09:22.470 align:start position:0% by using the toolbox the closure gives you<00:09:20.880> in<00:09:21.040> my<00:09:21.200> particular<00:09:21.680> case 00:09:22.470 --> 00:09:22.480 align:start position:0% you in my particular case 00:09:22.480 --> 00:09:24.870 align:start position:0% you in my particular case uh<00:09:22.880> the<00:09:23.120> idea<00:09:23.440> of<00:09:23.600> lazy<00:09:23.920> sequences<00:09:24.720> was 00:09:24.870 --> 00:09:24.880 align:start position:0% uh the idea of lazy sequences was 00:09:24.880 --> 00:09:26.710 align:start position:0% uh the idea of lazy sequences was incredibly<00:09:25.360> useful<00:09:25.920> for<00:09:26.080> tackling<00:09:26.480> this 00:09:26.710 --> 00:09:26.720 align:start position:0% incredibly useful for tackling this 00:09:26.720 --> 00:09:28.710 align:start position:0% incredibly useful for tackling this problem<00:09:27.279> and<00:09:27.360> i<00:09:27.440> think<00:09:27.600> that<00:09:27.760> if<00:09:27.920> you<00:09:28.240> revisit 00:09:28.710 --> 00:09:28.720 align:start position:0% problem and i think that if you revisit 00:09:28.720 --> 00:09:30.550 align:start position:0% problem and i think that if you revisit some<00:09:28.880> of<00:09:29.040> your<00:09:29.200> old<00:09:29.360> problems<00:09:29.920> you<00:09:30.080> might<00:09:30.320> also 00:09:30.550 --> 00:09:30.560 align:start position:0% some of your old problems you might also 00:09:30.560 --> 00:09:33.030 align:start position:0% some of your old problems you might also find<00:09:30.800> some<00:09:31.200> really<00:09:31.440> good<00:09:31.600> solutions<00:09:32.160> in<00:09:32.720> the 00:09:33.030 --> 00:09:33.040 align:start position:0% find some really good solutions in the 00:09:33.040 --> 00:09:34.550 align:start position:0% find some really good solutions in the closure<00:09:33.360> toolbox<00:09:33.760> to<00:09:33.839> help<00:09:34.000> you<00:09:34.160> solve<00:09:34.399> those 00:09:34.550 --> 00:09:34.560 align:start position:0% closure toolbox to help you solve those 00:09:34.560 --> 00:09:35.590 align:start position:0% closure toolbox to help you solve those problems 00:09:35.590 --> 00:09:35.600 align:start position:0% problems 00:09:35.600 --> 00:09:40.550 align:start position:0% problems thank<00:09:35.760> you 00:09:40.550 --> 00:09:40.560 align:start position:0% 00:09:40.560 --> 00:09:42.550 align:start position:0% so<00:09:40.720> next<00:09:41.040> up<00:09:41.360> we<00:09:41.519> have<00:09:41.760> a<00:09:41.839> really<00:09:42.160> interesting 00:09:42.550 --> 00:09:42.560 align:start position:0% so next up we have a really interesting 00:09:42.560 --> 00:09:44.949 align:start position:0% so next up we have a really interesting treat<00:09:42.959> uh<00:09:43.440> there<00:09:43.760> is<00:09:44.080> a 00:09:44.949 --> 00:09:44.959 align:start position:0% treat uh there is a 00:09:44.959 --> 00:09:46.470 align:start position:0% treat uh there is a a<00:09:45.040> new<00:09:45.200> thing<00:09:45.440> that<00:09:45.600> has<00:09:45.680> entered<00:09:45.920> the<00:09:46.000> world 00:09:46.470 --> 00:09:46.480 align:start position:0% a new thing that has entered the world 00:09:46.480 --> 00:09:49.030 align:start position:0% a new thing that has entered the world uh<00:09:46.800> the<00:09:46.880> name<00:09:47.040> of<00:09:47.200> a<00:09:47.279> mutant<00:09:47.839> and 00:09:49.030 --> 00:09:49.040 align:start position:0% uh the name of a mutant and 00:09:49.040 --> 00:09:50.389 align:start position:0% uh the name of a mutant and i<00:09:49.360> uh 00:09:50.389 --> 00:09:50.399 align:start position:0% i uh 00:09:50.399 --> 00:09:53.350 align:start position:0% i uh don't<00:09:50.560> know<00:09:50.720> what<00:09:50.880> that<00:09:51.040> clicking<00:09:51.360> is 00:09:53.350 --> 00:09:53.360 align:start position:0% don't know what that clicking is 00:09:53.360 --> 00:09:55.269 align:start position:0% don't know what that clicking is okay 00:09:55.269 --> 00:09:55.279 align:start position:0% okay 00:09:55.279 --> 00:09:57.509 align:start position:0% okay uh<00:09:55.519> anyways<00:09:56.080> um<00:09:56.720> there<00:09:56.880> has<00:09:57.040> been<00:09:57.200> some<00:09:57.360> really 00:09:57.509 --> 00:09:57.519 align:start position:0% uh anyways um there has been some really 00:09:57.519 --> 00:09:59.750 align:start position:0% uh anyways um there has been some really interesting<00:09:57.839> work<00:09:58.160> in<00:09:58.640> uh<00:09:59.040> recently<00:09:59.440> done<00:09:59.680> in 00:09:59.750 --> 00:09:59.760 align:start position:0% interesting work in uh recently done in 00:09:59.760 --> 00:10:01.670 align:start position:0% interesting work in uh recently done in just<00:10:00.080> tying<00:10:00.480> together<00:10:00.959> uh<00:10:01.200> application 00:10:01.670 --> 00:10:01.680 align:start position:0% just tying together uh application 00:10:01.680 --> 00:10:04.389 align:start position:0% just tying together uh application servers<00:10:02.320> and<00:10:02.480> and<00:10:02.640> new<00:10:02.800> ways<00:10:03.040> of<00:10:03.200> deploying<00:10:04.160> uh 00:10:04.389 --> 00:10:04.399 align:start position:0% servers and and new ways of deploying uh 00:10:04.399 --> 00:10:06.550 align:start position:0% servers and and new ways of deploying uh your<00:10:04.560> closure<00:10:04.880> code<00:10:05.519> and<00:10:05.839> actually<00:10:06.240> allowing 00:10:06.550 --> 00:10:06.560 align:start position:0% your closure code and actually allowing 00:10:06.560 --> 00:10:08.470 align:start position:0% your closure code and actually allowing you<00:10:06.640> to<00:10:06.720> interact<00:10:07.040> with<00:10:07.360> with<00:10:07.519> other<00:10:07.920> uh 00:10:08.470 --> 00:10:08.480 align:start position:0% you to interact with with other uh 00:10:08.480 --> 00:10:11.990 align:start position:0% you to interact with with other uh non-closure<00:10:09.040> code<00:10:09.680> and<00:10:10.000> i<00:10:10.079> think<00:10:10.320> there's<00:10:10.720> uh 00:10:11.990 --> 00:10:12.000 align:start position:0% non-closure code and i think there's uh 00:10:12.000 --> 00:10:13.430 align:start position:0% non-closure code and i think there's uh a<00:10:12.240> whole<00:10:12.399> bunch<00:10:12.640> of<00:10:12.720> really<00:10:12.959> cool<00:10:13.120> stuff<00:10:13.360> that 00:10:13.430 --> 00:10:13.440 align:start position:0% a whole bunch of really cool stuff that 00:10:13.440 --> 00:10:14.710 align:start position:0% a whole bunch of really cool stuff that can<00:10:13.600> happen<00:10:13.760> here<00:10:14.000> and<00:10:14.079> kind<00:10:14.240> of<00:10:14.320> marrying 00:10:14.710 --> 00:10:14.720 align:start position:0% can happen here and kind of marrying 00:10:14.720 --> 00:10:17.269 align:start position:0% can happen here and kind of marrying closure<00:10:15.519> uh<00:10:15.920> and<00:10:16.240> and 00:10:17.269 --> 00:10:17.279 align:start position:0% closure uh and and 00:10:17.279 --> 00:10:18.790 align:start position:0% closure uh and and legacy<00:10:17.680> code<00:10:18.000> and<00:10:18.079> things<00:10:18.240> like<00:10:18.320> that<00:10:18.560> so<00:10:18.640> i'm 00:10:18.790 --> 00:10:18.800 align:start position:0% legacy code and things like that so i'm 00:10:18.800 --> 00:10:21.030 align:start position:0% legacy code and things like that so i'm gonna<00:10:19.440> let<00:10:19.600> jim<00:10:19.920> take<00:10:20.079> it<00:10:20.160> further<00:10:20.720> and<00:10:20.880> talk 00:10:21.030 --> 00:10:21.040 align:start position:0% gonna let jim take it further and talk 00:10:21.040 --> 00:10:22.470 align:start position:0% gonna let jim take it further and talk to<00:10:21.120> you<00:10:21.200> about<00:10:21.360> it 00:10:22.470 --> 00:10:22.480 align:start position:0% to you about it 00:10:22.480 --> 00:10:23.590 align:start position:0% to you about it all<00:10:22.640> right 00:10:23.590 --> 00:10:23.600 align:start position:0% all right 00:10:23.600 --> 00:10:26.069 align:start position:0% all right can<00:10:23.760> you<00:10:23.839> hear<00:10:24.000> me 00:10:26.069 --> 00:10:26.079 align:start position:0% can you hear me 00:10:26.079 --> 00:10:27.590 align:start position:0% can you hear me all<00:10:26.160> right 00:10:27.590 --> 00:10:27.600 align:start position:0% all right 00:10:27.600 --> 00:10:29.750 align:start position:0% all right so<00:10:27.920> we're<00:10:28.160> muting<00:10:28.640> an<00:10:28.800> application<00:10:29.360> server 00:10:29.750 --> 00:10:29.760 align:start position:0% so we're muting an application server 00:10:29.760 --> 00:10:31.670 align:start position:0% so we're muting an application server for<00:10:29.920> closure<00:10:30.399> i'm<00:10:30.640> sure<00:10:31.040> i'm<00:10:31.120> sure<00:10:31.279> that 00:10:31.670 --> 00:10:31.680 align:start position:0% for closure i'm sure i'm sure that 00:10:31.680 --> 00:10:34.470 align:start position:0% for closure i'm sure i'm sure that frightens<00:10:32.160> some<00:10:32.320> of<00:10:32.480> you<00:10:32.800> possibly 00:10:34.470 --> 00:10:34.480 align:start position:0% frightens some of you possibly 00:10:34.480 --> 00:10:36.069 align:start position:0% frightens some of you possibly so<00:10:34.640> let's<00:10:34.959> try<00:10:35.120> to<00:10:35.279> allay<00:10:35.600> some<00:10:35.760> of<00:10:35.839> those 00:10:36.069 --> 00:10:36.079 align:start position:0% so let's try to allay some of those 00:10:36.079 --> 00:10:37.190 align:start position:0% so let's try to allay some of those fears 00:10:37.190 --> 00:10:37.200 align:start position:0% fears 00:10:37.200 --> 00:10:39.269 align:start position:0% fears because<00:10:37.519> we<00:10:37.680> are<00:10:37.839> new<00:10:38.000> to<00:10:38.160> the<00:10:38.240> community<00:10:38.959> uh 00:10:39.269 --> 00:10:39.279 align:start position:0% because we are new to the community uh 00:10:39.279 --> 00:10:41.430 align:start position:0% because we are new to the community uh let<00:10:39.440> me<00:10:39.519> introduce<00:10:39.920> myself<00:10:40.240> i'm<00:10:40.399> jim<00:10:40.640> crossley 00:10:41.430 --> 00:10:41.440 align:start position:0% let me introduce myself i'm jim crossley 00:10:41.440 --> 00:10:44.389 align:start position:0% let me introduce myself i'm jim crossley toby<00:10:41.760> crawley<00:10:42.640> we<00:10:42.800> work<00:10:42.959> for<00:10:43.120> red<00:10:43.360> hat 00:10:44.389 --> 00:10:44.399 align:start position:0% toby crawley we work for red hat 00:10:44.399 --> 00:10:46.550 align:start position:0% toby crawley we work for red hat we<00:10:44.560> are<00:10:44.720> core<00:10:44.880> committers<00:10:45.440> on<00:10:45.760> torque<00:10:46.079> box 00:10:46.550 --> 00:10:46.560 align:start position:0% we are core committers on torque box 00:10:46.560 --> 00:10:48.550 align:start position:0% we are core committers on torque box which<00:10:46.800> is<00:10:47.360> if<00:10:47.519> you<00:10:47.600> hadn't<00:10:47.839> heard<00:10:48.000> torque<00:10:48.240> box 00:10:48.550 --> 00:10:48.560 align:start position:0% which is if you hadn't heard torque box 00:10:48.560 --> 00:10:50.630 align:start position:0% which is if you hadn't heard torque box torque<00:10:48.800> box<00:10:49.120> is<00:10:49.200> an<00:10:49.360> application<00:10:49.920> server<00:10:50.320> or 00:10:50.630 --> 00:10:50.640 align:start position:0% torque box is an application server or 00:10:50.640 --> 00:10:51.829 align:start position:0% torque box is an application server or ruby 00:10:51.829 --> 00:10:51.839 align:start position:0% ruby 00:10:51.839 --> 00:10:55.030 align:start position:0% ruby uh 00:10:55.030 --> 00:10:55.040 align:start position:0% 00:10:55.040 --> 00:10:58.150 align:start position:0% both<00:10:55.600> torque<00:10:55.920> box<00:10:56.240> and<00:10:56.399> a<00:10:56.480> mutant<00:10:57.120> are<00:10:57.279> enabled 00:10:58.150 --> 00:10:58.160 align:start position:0% both torque box and a mutant are enabled 00:10:58.160 --> 00:10:59.350 align:start position:0% both torque box and a mutant are enabled by 00:10:59.350 --> 00:10:59.360 align:start position:0% by 00:10:59.360 --> 00:11:01.750 align:start position:0% by the<00:10:59.600> jboss<00:11:00.320> as7 00:11:01.750 --> 00:11:01.760 align:start position:0% the jboss as7 00:11:01.760 --> 00:11:03.829 align:start position:0% the jboss as7 java<00:11:02.160> application<00:11:02.800> server 00:11:03.829 --> 00:11:03.839 align:start position:0% java application server 00:11:03.839 --> 00:11:04.870 align:start position:0% java application server now 00:11:04.870 --> 00:11:04.880 align:start position:0% now 00:11:04.880 --> 00:11:08.230 align:start position:0% now so<00:11:05.600> application<00:11:06.240> server<00:11:06.720> basically<00:11:07.200> means 00:11:08.230 --> 00:11:08.240 align:start position:0% so application server basically means 00:11:08.240 --> 00:11:09.509 align:start position:0% so application server basically means middleware 00:11:09.509 --> 00:11:09.519 align:start position:0% middleware 00:11:09.519 --> 00:11:11.350 align:start position:0% middleware middleware<00:11:10.640> is 00:11:11.350 --> 00:11:11.360 align:start position:0% middleware is 00:11:11.360 --> 00:11:14.069 align:start position:0% middleware is is<00:11:11.680> the<00:11:12.320> accidental<00:11:13.120> complexity<00:11:13.760> it's<00:11:14.000> all 00:11:14.069 --> 00:11:14.079 align:start position:0% is the accidental complexity it's all 00:11:14.079 --> 00:11:16.150 align:start position:0% is the accidental complexity it's all the<00:11:14.240> software<00:11:14.800> you<00:11:15.120> build 00:11:16.150 --> 00:11:16.160 align:start position:0% the software you build 00:11:16.160 --> 00:11:19.590 align:start position:0% the software you build or<00:11:16.560> configure<00:11:17.360> or<00:11:17.600> use<00:11:18.560> that<00:11:18.880> doesn't<00:11:19.360> have 00:11:19.590 --> 00:11:19.600 align:start position:0% or configure or use that doesn't have 00:11:19.600 --> 00:11:22.550 align:start position:0% or configure or use that doesn't have anything<00:11:20.000> to<00:11:20.160> do<00:11:20.640> with<00:11:21.040> the<00:11:21.200> problem<00:11:21.600> domain 00:11:22.550 --> 00:11:22.560 align:start position:0% anything to do with the problem domain 00:11:22.560 --> 00:11:24.069 align:start position:0% anything to do with the problem domain that<00:11:22.800> the<00:11:22.959> application<00:11:23.519> you're<00:11:23.680> trying<00:11:24.000> to 00:11:24.069 --> 00:11:24.079 align:start position:0% that the application you're trying to 00:11:24.079 --> 00:11:25.030 align:start position:0% that the application you're trying to build 00:11:25.030 --> 00:11:25.040 align:start position:0% build 00:11:25.040 --> 00:11:27.030 align:start position:0% build is<00:11:25.680> trying<00:11:25.920> to<00:11:26.079> solve 00:11:27.030 --> 00:11:27.040 align:start position:0% is trying to solve 00:11:27.040 --> 00:11:31.110 align:start position:0% is trying to solve so<00:11:28.240> an<00:11:28.880> application<00:11:29.519> server<00:11:29.839> done<00:11:30.160> well 00:11:31.110 --> 00:11:31.120 align:start position:0% so an application server done well 00:11:31.120 --> 00:11:32.550 align:start position:0% so an application server done well is<00:11:31.440> basically 00:11:32.550 --> 00:11:32.560 align:start position:0% is basically 00:11:32.560 --> 00:11:37.430 align:start position:0% is basically a<00:11:33.120> clean<00:11:33.600> shaven<00:11:34.000> yet 00:11:37.430 --> 00:11:37.440 align:start position:0% 00:11:37.440 --> 00:11:39.509 align:start position:0% and<00:11:37.519> that's<00:11:37.760> what<00:11:37.920> we're<00:11:38.079> trying<00:11:38.320> to<00:11:38.480> do 00:11:39.509 --> 00:11:39.519 align:start position:0% and that's what we're trying to do 00:11:39.519 --> 00:11:41.670 align:start position:0% and that's what we're trying to do it<00:11:39.760> is<00:11:39.920> very<00:11:40.240> easy<00:11:40.560> to<00:11:40.720> do<00:11:40.880> an<00:11:41.040> application 00:11:41.670 --> 00:11:41.680 align:start position:0% it is very easy to do an application 00:11:41.680 --> 00:11:42.470 align:start position:0% it is very easy to do an application server 00:11:42.470 --> 00:11:42.480 align:start position:0% server 00:11:42.480 --> 00:11:45.829 align:start position:0% server poorly<00:11:43.519> and<00:11:43.680> we<00:11:43.839> have<00:11:44.000> failed<00:11:44.320> if<00:11:44.399> we<00:11:44.560> do<00:11:44.800> that 00:11:45.829 --> 00:11:45.839 align:start position:0% poorly and we have failed if we do that 00:11:45.839 --> 00:11:46.790 align:start position:0% poorly and we have failed if we do that so 00:11:46.790 --> 00:11:46.800 align:start position:0% so 00:11:46.800 --> 00:11:48.389 align:start position:0% so even<00:11:47.040> though<00:11:47.200> i<00:11:47.279> just<00:11:47.440> said<00:11:47.680> that<00:11:47.920> clean<00:11:48.160> shape 00:11:48.389 --> 00:11:48.399 align:start position:0% even though i just said that clean shape 00:11:48.399 --> 00:11:50.069 align:start position:0% even though i just said that clean shape and<00:11:48.480> yak<00:11:48.720> what<00:11:48.880> does<00:11:48.959> that<00:11:49.120> mean 00:11:50.069 --> 00:11:50.079 align:start position:0% and yak what does that mean 00:11:50.079 --> 00:11:52.150 align:start position:0% and yak what does that mean what<00:11:50.320> is<00:11:50.480> an<00:11:50.639> application<00:11:51.120> server<00:11:51.760> it<00:11:51.920> is 00:11:52.150 --> 00:11:52.160 align:start position:0% what is an application server it is 00:11:52.160 --> 00:11:55.190 align:start position:0% what is an application server it is perfectly<00:11:52.639> correct<00:11:53.120> to<00:11:53.279> think<00:11:53.600> of<00:11:54.000> jboss 00:11:55.190 --> 00:11:55.200 align:start position:0% perfectly correct to think of jboss 00:11:55.200 --> 00:11:58.389 align:start position:0% perfectly correct to think of jboss at<00:11:55.440> just<00:11:55.760> as<00:11:55.920> you<00:11:56.079> would<00:11:56.399> jetty<00:11:56.720> or<00:11:56.880> tomcat 00:11:58.389 --> 00:11:58.399 align:start position:0% at just as you would jetty or tomcat 00:11:58.399 --> 00:11:59.910 align:start position:0% at just as you would jetty or tomcat so<00:11:58.639> just<00:11:58.880> as<00:11:59.040> you<00:11:59.200> would 00:11:59.910 --> 00:11:59.920 align:start position:0% so just as you would 00:11:59.920 --> 00:12:02.629 align:start position:0% so just as you would use<00:12:00.240> line<00:12:00.480> again<00:12:00.880> to<00:12:01.200> bring<00:12:01.440> up<00:12:01.680> jetty<00:12:02.079> to<00:12:02.399> run 00:12:02.629 --> 00:12:02.639 align:start position:0% use line again to bring up jetty to run 00:12:02.639 --> 00:12:04.870 align:start position:0% use line again to bring up jetty to run your<00:12:02.880> ring<00:12:03.120> based<00:12:03.440> application<00:12:04.399> you<00:12:04.560> do<00:12:04.720> the 00:12:04.870 --> 00:12:04.880 align:start position:0% your ring based application you do the 00:12:04.880 --> 00:12:08.150 align:start position:0% your ring based application you do the exact<00:12:05.200> same<00:12:05.440> thing<00:12:05.680> with<00:12:05.839> jvos 00:12:08.150 --> 00:12:08.160 align:start position:0% exact same thing with jvos 00:12:08.160 --> 00:12:09.750 align:start position:0% exact same thing with jvos but<00:12:08.320> in<00:12:08.480> addition<00:12:08.800> to<00:12:08.880> that<00:12:09.120> you<00:12:09.200> get<00:12:09.440> other 00:12:09.750 --> 00:12:09.760 align:start position:0% but in addition to that you get other 00:12:09.760 --> 00:12:12.790 align:start position:0% but in addition to that you get other services<00:12:10.560> we<00:12:10.800> uh<00:12:11.440> it's<00:12:11.680> an<00:12:11.839> integrated<00:12:12.399> all<00:12:12.639> of 00:12:12.790 --> 00:12:12.800 align:start position:0% services we uh it's an integrated all of 00:12:12.800 --> 00:12:14.310 align:start position:0% services we uh it's an integrated all of the<00:12:12.880> 10<00:12:13.200> solution 00:12:14.310 --> 00:12:14.320 align:start position:0% the 10 solution 00:12:14.320 --> 00:12:16.150 align:start position:0% the 10 solution we<00:12:14.480> provide<00:12:14.880> in<00:12:15.040> addition<00:12:15.440> to<00:12:15.519> the<00:12:15.680> web 00:12:16.150 --> 00:12:16.160 align:start position:0% we provide in addition to the web 00:12:16.160 --> 00:12:18.069 align:start position:0% we provide in addition to the web messaging<00:12:16.800> caching<00:12:17.360> messaging<00:12:17.920> through 00:12:18.069 --> 00:12:18.079 align:start position:0% messaging caching messaging through 00:12:18.079 --> 00:12:21.590 align:start position:0% messaging caching messaging through hornet<00:12:18.480> cube<00:12:18.959> jms<00:12:19.760> message<00:12:20.240> queue<00:12:20.880> uh<00:12:21.200> caching 00:12:21.590 --> 00:12:21.600 align:start position:0% hornet cube jms message queue uh caching 00:12:21.600 --> 00:12:23.430 align:start position:0% hornet cube jms message queue uh caching through<00:12:21.839> infinite<00:12:22.160> span<00:12:22.560> which<00:12:22.720> is<00:12:22.880> a<00:12:23.279> key 00:12:23.430 --> 00:12:23.440 align:start position:0% through infinite span which is a key 00:12:23.440 --> 00:12:25.829 align:start position:0% through infinite span which is a key value<00:12:23.920> store<00:12:24.560> data<00:12:24.880> grid 00:12:25.829 --> 00:12:25.839 align:start position:0% value store data grid 00:12:25.839 --> 00:12:29.990 align:start position:0% value store data grid all<00:12:26.160> kind<00:12:26.399> of<00:12:26.800> easily<00:12:27.200> replicated 00:12:29.990 --> 00:12:30.000 align:start position:0% 00:12:30.000 --> 00:12:31.030 align:start position:0% service 00:12:31.030 --> 00:12:31.040 align:start position:0% service 00:12:31.040 --> 00:12:33.190 align:start position:0% service clustering<00:12:31.680> again<00:12:32.240> all<00:12:32.399> the<00:12:32.560> standard<00:12:32.959> things 00:12:33.190 --> 00:12:33.200 align:start position:0% clustering again all the standard things 00:12:33.200 --> 00:12:35.910 align:start position:0% clustering again all the standard things that<00:12:33.279> you<00:12:33.440> would<00:12:33.600> expect<00:12:34.000> to<00:12:34.160> see<00:12:34.800> in 00:12:35.910 --> 00:12:35.920 align:start position:0% that you would expect to see in 00:12:35.920 --> 00:12:38.790 align:start position:0% that you would expect to see in the<00:12:36.160> e-word 00:12:38.790 --> 00:12:38.800 align:start position:0% the e-word 00:12:38.800 --> 00:12:39.990 align:start position:0% the e-word so 00:12:39.990 --> 00:12:40.000 align:start position:0% so 00:12:40.000 --> 00:12:42.230 align:start position:0% so to<00:12:40.480> get<00:12:40.959> all<00:12:41.120> the<00:12:41.279> advantages<00:12:41.839> of<00:12:42.000> those 00:12:42.230 --> 00:12:42.240 align:start position:0% to get all the advantages of those 00:12:42.240 --> 00:12:43.590 align:start position:0% to get all the advantages of those services 00:12:43.590 --> 00:12:43.600 align:start position:0% services 00:12:43.600 --> 00:12:47.030 align:start position:0% services traditionally<00:12:44.880> you've<00:12:45.279> had<00:12:45.839> to 00:12:47.030 --> 00:12:47.040 align:start position:0% traditionally you've had to 00:12:47.040 --> 00:12:50.150 align:start position:0% traditionally you've had to assemble<00:12:47.760> a<00:12:47.920> big<00:12:48.160> pile<00:12:48.560> of<00:12:48.720> annotated<00:12:49.680> java 00:12:50.150 --> 00:12:50.160 align:start position:0% assemble a big pile of annotated java 00:12:50.160 --> 00:12:52.870 align:start position:0% assemble a big pile of annotated java classes<00:12:50.560> and<00:12:50.839> xml<00:12:51.920> so 00:12:52.870 --> 00:12:52.880 align:start position:0% classes and xml so 00:12:52.880 --> 00:12:55.269 align:start position:0% classes and xml so torque<00:12:53.279> box<00:12:53.680> was<00:12:53.839> written<00:12:54.480> in<00:12:54.639> response<00:12:55.120> to 00:12:55.269 --> 00:12:55.279 align:start position:0% torque box was written in response to 00:12:55.279 --> 00:12:57.269 align:start position:0% torque box was written in response to that<00:12:55.680> to<00:12:55.839> say 00:12:57.269 --> 00:12:57.279 align:start position:0% that to say 00:12:57.279 --> 00:13:00.550 align:start position:0% that to say none<00:12:57.519> of<00:12:57.680> that<00:12:58.000> we<00:12:58.160> do<00:12:58.399> all<00:12:58.639> ruby<00:12:59.440> where 00:13:00.550 --> 00:13:00.560 align:start position:0% none of that we do all ruby where 00:13:00.560 --> 00:13:02.710 align:start position:0% none of that we do all ruby where you<00:13:00.639> know<00:13:00.800> we've<00:13:00.959> talked<00:13:01.200> about<00:13:01.600> rapping<00:13:02.160> as 00:13:02.710 --> 00:13:02.720 align:start position:0% you know we've talked about rapping as 00:13:02.720 --> 00:13:05.829 align:start position:0% you know we've talked about rapping as an<00:13:02.880> overloaded<00:13:03.440> term<00:13:04.240> but<00:13:04.480> we<00:13:04.800> are<00:13:05.440> we<00:13:05.600> are 00:13:05.829 --> 00:13:05.839 align:start position:0% an overloaded term but we are we are 00:13:05.839 --> 00:13:08.230 align:start position:0% an overloaded term but we are we are wrapping<00:13:06.240> with<00:13:06.560> malice<00:13:07.040> we<00:13:07.200> are<00:13:07.440> opinionated 00:13:08.230 --> 00:13:08.240 align:start position:0% wrapping with malice we are opinionated 00:13:08.240 --> 00:13:10.550 align:start position:0% wrapping with malice we are opinionated wrapping<00:13:09.040> we're<00:13:09.279> not<00:13:09.440> just<00:13:09.760> exposing<00:13:10.320> those 00:13:10.550 --> 00:13:10.560 align:start position:0% wrapping we're not just exposing those 00:13:10.560 --> 00:13:16.230 align:start position:0% wrapping we're not just exposing those job<00:13:10.880> services<00:13:11.360> via<00:13:11.680> jay<00:13:11.920> ruby<00:13:12.720> we<00:13:13.120> are 00:13:16.230 --> 00:13:16.240 align:start position:0% 00:13:16.240 --> 00:13:18.550 align:start position:0% adopting<00:13:16.720> that<00:13:16.959> policy<00:13:17.600> uh<00:13:17.920> or<00:13:18.079> embracing 00:13:18.550 --> 00:13:18.560 align:start position:0% adopting that policy uh or embracing 00:13:18.560 --> 00:13:20.629 align:start position:0% adopting that policy uh or embracing that<00:13:18.800> notion<00:13:19.120> of<00:13:19.279> configuration 00:13:20.629 --> 00:13:20.639 align:start position:0% that notion of configuration 00:13:20.639 --> 00:13:22.870 align:start position:0% that notion of configuration convention<00:13:21.200> over<00:13:21.440> configuration 00:13:22.870 --> 00:13:22.880 align:start position:0% convention over configuration 00:13:22.880 --> 00:13:24.310 align:start position:0% convention over configuration um 00:13:24.310 --> 00:13:24.320 align:start position:0% um 00:13:24.320 --> 00:13:27.269 align:start position:0% um and<00:13:24.480> jruby<00:13:25.440> basically<00:13:26.240> enables<00:13:26.720> us<00:13:26.880> to<00:13:26.959> be<00:13:27.120> the 00:13:27.269 --> 00:13:27.279 align:start position:0% and jruby basically enables us to be the 00:13:27.279 --> 00:13:30.230 align:start position:0% and jruby basically enables us to be the fastest<00:13:27.760> platform<00:13:28.480> for<00:13:29.200> any<00:13:29.360> kind<00:13:29.519> of<00:13:29.680> ruby 00:13:30.230 --> 00:13:30.240 align:start position:0% fastest platform for any kind of ruby 00:13:30.240 --> 00:13:32.470 align:start position:0% fastest platform for any kind of ruby web<00:13:30.480> app<00:13:30.720> development<00:13:31.200> that's<00:13:31.519> out<00:13:31.680> there<00:13:32.240> in 00:13:32.470 --> 00:13:32.480 align:start position:0% web app development that's out there in 00:13:32.480 --> 00:13:36.310 align:start position:0% web app development that's out there in google<00:13:32.880> for<00:13:33.279> torque<00:13:33.600> box<00:13:34.320> uh<00:13:34.800> benchmarks 00:13:36.310 --> 00:13:36.320 align:start position:0% google for torque box uh benchmarks 00:13:36.320 --> 00:13:37.430 align:start position:0% google for torque box uh benchmarks um 00:13:37.430 --> 00:13:37.440 align:start position:0% um 00:13:37.440 --> 00:13:39.829 align:start position:0% um to<00:13:37.600> see<00:13:37.760> that<00:13:37.920> for<00:13:38.160> yourself 00:13:39.829 --> 00:13:39.839 align:start position:0% to see that for yourself 00:13:39.839 --> 00:13:41.509 align:start position:0% to see that for yourself uh<00:13:40.079> so<00:13:40.560> basically<00:13:40.880> we're<00:13:40.959> just<00:13:41.120> replacing 00:13:41.509 --> 00:13:41.519 align:start position:0% uh so basically we're just replacing 00:13:41.519 --> 00:13:43.269 align:start position:0% uh so basically we're just replacing java<00:13:41.839> xml<00:13:42.240> with<00:13:42.320> ruby<00:13:42.720> and<00:13:42.800> yaml<00:13:43.120> and<00:13:43.199> we're 00:13:43.269 --> 00:13:43.279 align:start position:0% java xml with ruby and yaml and we're 00:13:43.279 --> 00:13:44.550 align:start position:0% java xml with ruby and yaml and we're very<00:13:43.440> excited<00:13:43.760> we've<00:13:43.760> got<00:13:43.920> numbers<00:13:44.320> to<00:13:44.399> come 00:13:44.550 --> 00:13:44.560 align:start position:0% very excited we've got numbers to come 00:13:44.560 --> 00:13:46.710 align:start position:0% very excited we've got numbers to come out<00:13:44.720> so<00:13:45.199> none<00:13:45.360> of<00:13:45.519> that<00:13:45.760> you're<00:13:45.920> interested<00:13:46.399> in 00:13:46.710 --> 00:13:46.720 align:start position:0% out so none of that you're interested in 00:13:46.720 --> 00:13:48.389 align:start position:0% out so none of that you're interested in when<00:13:46.880> we<00:13:47.040> talk<00:13:47.199> about<00:13:47.360> job<00:13:47.600> and<00:13:47.680> ruby<00:13:48.000> so<00:13:48.160> far 00:13:48.389 --> 00:13:48.399 align:start position:0% when we talk about job and ruby so far 00:13:48.399 --> 00:13:50.790 align:start position:0% when we talk about job and ruby so far let's<00:13:48.560> get<00:13:48.720> to<00:13:48.800> the<00:13:48.880> closure 00:13:50.790 --> 00:13:50.800 align:start position:0% let's get to the closure 00:13:50.800 --> 00:13:55.030 align:start position:0% let's get to the closure torque<00:13:51.040> box<00:13:51.760> inspired<00:13:52.320> the<00:13:52.480> idea<00:13:52.800> of<00:13:52.959> a<00:13:53.040> mutant 00:13:55.030 --> 00:13:55.040 align:start position:0% torque box inspired the idea of a mutant 00:13:55.040 --> 00:13:55.990 align:start position:0% torque box inspired the idea of a mutant so 00:13:55.990 --> 00:13:56.000 align:start position:0% so 00:13:56.000 --> 00:13:59.110 align:start position:0% so essentially<00:13:56.959> it's<00:13:57.199> a<00:13:57.360> dsl<00:13:58.079> to<00:13:58.240> describe<00:13:58.959> the 00:13:59.110 --> 00:13:59.120 align:start position:0% essentially it's a dsl to describe the 00:13:59.120 --> 00:14:01.030 align:start position:0% essentially it's a dsl to describe the middleware<00:13:59.680> that<00:13:59.839> your<00:14:00.160> application<00:14:00.800> would 00:14:01.030 --> 00:14:01.040 align:start position:0% middleware that your application would 00:14:01.040 --> 00:14:03.670 align:start position:0% middleware that your application would be 00:14:03.670 --> 00:14:03.680 align:start position:0% 00:14:03.680 --> 00:14:04.790 align:start position:0% bsl 00:14:04.790 --> 00:14:04.800 align:start position:0% bsl 00:14:04.800 --> 00:14:07.590 align:start position:0% bsl in<00:14:04.959> its<00:14:05.600> most<00:14:05.920> loose<00:14:06.240> definition 00:14:07.590 --> 00:14:07.600 align:start position:0% in its most loose definition 00:14:07.600 --> 00:14:08.870 align:start position:0% in its most loose definition uh 00:14:08.870 --> 00:14:08.880 align:start position:0% uh 00:14:08.880 --> 00:14:11.110 align:start position:0% uh so<00:14:09.199> far<00:14:09.600> we've<00:14:09.839> only<00:14:10.079> been<00:14:10.560> doing<00:14:10.800> this<00:14:10.880> for<00:14:11.040> a 00:14:11.110 --> 00:14:11.120 align:start position:0% so far we've only been doing this for a 00:14:11.120 --> 00:14:13.670 align:start position:0% so far we've only been doing this for a couple<00:14:11.360> of<00:14:11.519> months<00:14:11.839> and<00:14:12.000> so<00:14:12.320> far<00:14:12.639> we<00:14:12.800> had<00:14:13.199> web 00:14:13.670 --> 00:14:13.680 align:start position:0% couple of months and so far we had web 00:14:13.680 --> 00:14:16.389 align:start position:0% couple of months and so far we had web and<00:14:13.920> core<00:14:14.240> messaging<00:14:14.720> stuff<00:14:15.040> implemented 00:14:16.389 --> 00:14:16.399 align:start position:0% and core messaging stuff implemented 00:14:16.399 --> 00:14:17.829 align:start position:0% and core messaging stuff implemented because<00:14:16.639> we're<00:14:16.800> an<00:14:16.959> app<00:14:17.199> server<00:14:17.680> you 00:14:17.829 --> 00:14:17.839 align:start position:0% because we're an app server you 00:14:17.839 --> 00:14:19.910 align:start position:0% because we're an app server you typically<00:14:18.399> deploy<00:14:18.800> multiple<00:14:19.199> applications 00:14:19.910 --> 00:14:19.920 align:start position:0% typically deploy multiple applications 00:14:19.920 --> 00:14:22.710 align:start position:0% typically deploy multiple applications to<00:14:20.079> it<00:14:20.320> so<00:14:20.480> you<00:14:20.639> want<00:14:20.800> some<00:14:21.040> isolation 00:14:22.710 --> 00:14:22.720 align:start position:0% to it so you want some isolation 00:14:22.720 --> 00:14:24.790 align:start position:0% to it so you want some isolation we<00:14:22.880> have<00:14:23.120> that<00:14:23.600> working 00:14:24.790 --> 00:14:24.800 align:start position:0% we have that working 00:14:24.800 --> 00:14:27.110 align:start position:0% we have that working we're<00:14:25.040> trying<00:14:25.440> to<00:14:25.680> make<00:14:25.920> it<00:14:26.079> all<00:14:26.399> installable 00:14:27.110 --> 00:14:27.120 align:start position:0% we're trying to make it all installable 00:14:27.120 --> 00:14:28.230 align:start position:0% we're trying to make it all installable runnable 00:14:28.230 --> 00:14:28.240 align:start position:0% runnable 00:14:28.240 --> 00:14:30.949 align:start position:0% runnable deployable<00:14:28.959> using<00:14:29.519> uh<00:14:29.519> a<00:14:29.920> line<00:14:30.160> again<00:14:30.800> uh 00:14:30.949 --> 00:14:30.959 align:start position:0% deployable using uh a line again uh 00:14:30.959 --> 00:14:33.030 align:start position:0% deployable using uh a line again uh plugins<00:14:31.600> as<00:14:31.760> well 00:14:33.030 --> 00:14:33.040 align:start position:0% plugins as well 00:14:33.040 --> 00:14:34.790 align:start position:0% plugins as well so<00:14:33.199> here's<00:14:33.440> a<00:14:33.519> quick<00:14:33.760> example 00:14:34.790 --> 00:14:34.800 align:start position:0% so here's a quick example 00:14:34.800 --> 00:14:37.269 align:start position:0% so here's a quick example uh<00:14:35.360> you're<00:14:35.600> just<00:14:35.760> writing<00:14:36.160> your 00:14:37.269 --> 00:14:37.279 align:start position:0% uh you're just writing your 00:14:37.279 --> 00:14:38.870 align:start position:0% uh you're just writing your project<00:14:37.760> as<00:14:37.920> you<00:14:38.000> normally<00:14:38.320> would<00:14:38.560> in<00:14:38.639> line 00:14:38.870 --> 00:14:38.880 align:start position:0% project as you normally would in line 00:14:38.880 --> 00:14:39.750 align:start position:0% project as you normally would in line again 00:14:39.750 --> 00:14:39.760 align:start position:0% again 00:14:39.760 --> 00:14:41.990 align:start position:0% again but<00:14:39.920> when<00:14:40.079> you<00:14:40.320> deploy<00:14:40.720> it<00:14:40.880> to<00:14:41.040> a<00:14:41.120> human<00:14:41.680> youth 00:14:41.990 --> 00:14:42.000 align:start position:0% but when you deploy it to a human youth 00:14:42.000 --> 00:14:44.790 align:start position:0% but when you deploy it to a human youth is<00:14:42.079> looking<00:14:42.480> for<00:14:42.959> a<00:14:43.360> top<00:14:43.600> level<00:14:43.920> in<00:14:44.000> unc<00:14:44.399> lj 00:14:44.790 --> 00:14:44.800 align:start position:0% is looking for a top level in unc lj 00:14:44.800 --> 00:14:48.710 align:start position:0% is looking for a top level in unc lj file<00:14:45.600> here's<00:14:45.839> an<00:14:46.000> example<00:14:46.800> of<00:14:46.959> how<00:14:47.279> we<00:14:47.440> might 00:14:48.710 --> 00:14:48.720 align:start position:0% file here's an example of how we might 00:14:48.720 --> 00:14:49.990 align:start position:0% file here's an example of how we might uh 00:14:49.990 --> 00:14:50.000 align:start position:0% uh 00:14:50.000 --> 00:14:54.069 align:start position:0% uh there's<00:14:50.240> a<00:14:50.320> messaging<00:14:50.959> and<00:14:51.120> web<00:14:51.440> name<00:14:51.680> space 00:14:54.069 --> 00:14:54.079 align:start position:0% there's a messaging and web name space 00:14:54.079 --> 00:14:56.230 align:start position:0% there's a messaging and web name space here's<00:14:54.399> how<00:14:54.560> we're<00:14:54.880> starting<00:14:55.600> uh<00:14:56.000> just 00:14:56.230 --> 00:14:56.240 align:start position:0% here's how we're starting uh just 00:14:56.240 --> 00:15:00.949 align:start position:0% here's how we're starting uh just starting<00:14:56.560> a<00:14:56.720> cube<00:14:58.160> and<00:14:58.320> we<00:14:58.639> are<00:14:59.199> mapping<00:15:00.079> uh 00:15:00.949 --> 00:15:00.959 align:start position:0% starting a cube and we are mapping uh 00:15:00.959 --> 00:15:03.350 align:start position:0% starting a cube and we are mapping uh a<00:15:01.279> handler<00:15:02.079> to<00:15:02.240> receive<00:15:02.639> messages<00:15:03.120> that<00:15:03.279> are 00:15:03.350 --> 00:15:03.360 align:start position:0% a handler to receive messages that are 00:15:03.360 --> 00:15:05.430 align:start position:0% a handler to receive messages that are posted<00:15:03.760> thank<00:15:04.000> you<00:15:04.560> and<00:15:04.720> i'm<00:15:04.880> going<00:15:05.040> to<00:15:05.120> pause 00:15:05.430 --> 00:15:05.440 align:start position:0% posted thank you and i'm going to pause 00:15:05.440 --> 00:15:07.189 align:start position:0% posted thank you and i'm going to pause for<00:15:05.519> a<00:15:05.600> moment<00:15:06.079> while<00:15:06.320> each<00:15:06.560> of<00:15:06.639> you<00:15:06.800> say<00:15:07.120> in 00:15:07.189 --> 00:15:07.199 align:start position:0% for a moment while each of you say in 00:15:07.199 --> 00:15:08.310 align:start position:0% for a moment while each of you say in your<00:15:07.360> mind 00:15:08.310 --> 00:15:08.320 align:start position:0% your mind 00:15:08.320 --> 00:15:09.750 align:start position:0% your mind the<00:15:08.480> name<00:15:08.639> of<00:15:08.720> that<00:15:08.959> function<00:15:09.279> the<00:15:09.440> name<00:15:09.680> of 00:15:09.750 --> 00:15:09.760 align:start position:0% the name of that function the name of 00:15:09.760 --> 00:15:17.670 align:start position:0% the name of that function the name of that<00:15:09.920> handler 00:15:17.670 --> 00:15:17.680 align:start position:0% 00:15:17.680 --> 00:15:19.829 align:start position:0% all<00:15:17.839> right<00:15:18.240> so<00:15:18.560> uh<00:15:18.959> ring<00:15:19.199> handle<00:15:19.519> here's<00:15:19.680> the 00:15:19.829 --> 00:15:19.839 align:start position:0% all right so uh ring handle here's the 00:15:19.839 --> 00:15:22.629 align:start position:0% all right so uh ring handle here's the edge<00:15:20.320> we<00:15:20.480> support<00:15:20.800> any<00:15:20.959> kind<00:15:21.120> of 00:15:22.629 --> 00:15:22.639 align:start position:0% edge we support any kind of 00:15:22.639 --> 00:15:25.269 align:start position:0% edge we support any kind of ring-based<00:15:23.199> web<00:15:23.440> framework<00:15:23.920> that<00:15:24.079> there<00:15:24.320> is 00:15:25.269 --> 00:15:25.279 align:start position:0% ring-based web framework that there is 00:15:25.279 --> 00:15:27.110 align:start position:0% ring-based web framework that there is this<00:15:25.440> is<00:15:25.600> a<00:15:25.680> similar<00:15:26.480> handler<00:15:26.800> where<00:15:26.959> we're 00:15:27.110 --> 00:15:27.120 align:start position:0% this is a similar handler where we're 00:15:27.120 --> 00:15:30.310 align:start position:0% this is a similar handler where we're just<00:15:27.279> going<00:15:27.600> to<00:15:27.920> publish<00:15:28.399> to<00:15:28.639> our<00:15:28.800> work<00:15:29.120> queue 00:15:30.310 --> 00:15:30.320 align:start position:0% just going to publish to our work queue 00:15:30.320 --> 00:15:32.949 align:start position:0% just going to publish to our work queue any<00:15:30.560> composite<00:15:31.120> data<00:15:31.440> structure<00:15:31.920> we'd<00:15:32.160> like 00:15:32.949 --> 00:15:32.959 align:start position:0% any composite data structure we'd like 00:15:32.959 --> 00:15:34.230 align:start position:0% any composite data structure we'd like um 00:15:34.230 --> 00:15:34.240 align:start position:0% um 00:15:34.240 --> 00:15:37.189 align:start position:0% um it<00:15:34.399> just<00:15:34.560> has<00:15:34.800> to<00:15:34.880> be<00:15:35.120> understandable 00:15:37.189 --> 00:15:37.199 align:start position:0% it just has to be understandable 00:15:37.199 --> 00:15:39.189 align:start position:0% it just has to be understandable by<00:15:37.519> whoever's<00:15:38.000> going<00:15:38.160> to<00:15:38.240> receive<00:15:38.639> it<00:15:38.880> on<00:15:39.040> the 00:15:39.189 --> 00:15:39.199 align:start position:0% by whoever's going to receive it on the 00:15:39.199 --> 00:15:41.590 align:start position:0% by whoever's going to receive it on the other<00:15:39.519> end<00:15:40.240> if<00:15:40.480> it's 00:15:41.590 --> 00:15:41.600 align:start position:0% other end if it's 00:15:41.600 --> 00:15:43.990 align:start position:0% other end if it's another<00:15:42.000> closure<00:15:42.399> app<00:15:42.800> great 00:15:43.990 --> 00:15:44.000 align:start position:0% another closure app great 00:15:44.000 --> 00:15:45.509 align:start position:0% another closure app great we<00:15:44.160> just<00:15:44.399> print 00:15:45.509 --> 00:15:45.519 align:start position:0% we just print 00:15:45.519 --> 00:15:48.550 align:start position:0% we just print that<00:15:45.759> stuff<00:15:46.079> there 00:15:48.550 --> 00:15:48.560 align:start position:0% 00:15:48.560 --> 00:15:50.389 align:start position:0% and<00:15:48.959> you<00:15:49.120> associate<00:15:49.680> that<00:15:49.839> handle<00:15:50.160> with<00:15:50.320> a 00:15:50.389 --> 00:15:50.399 align:start position:0% and you associate that handle with a 00:15:50.399 --> 00:15:52.870 align:start position:0% and you associate that handle with a particular<00:15:50.880> web<00:15:51.120> context<00:15:51.920> just<00:15:52.160> your<00:15:52.399> typical 00:15:52.870 --> 00:15:52.880 align:start position:0% particular web context just your typical 00:15:52.880 --> 00:15:54.470 align:start position:0% particular web context just your typical way<00:15:53.040> you<00:15:53.199> would<00:15:53.600> uh 00:15:54.470 --> 00:15:54.480 align:start position:0% way you would uh 00:15:54.480 --> 00:15:58.550 align:start position:0% way you would uh do<00:15:54.639> that<00:15:54.880> with<00:15:55.519> uh<00:15:56.000> jetty 00:15:58.550 --> 00:15:58.560 align:start position:0% 00:15:58.560 --> 00:16:01.670 align:start position:0% um<00:15:59.040> so<00:15:59.519> that's<00:15:59.680> what<00:15:59.839> we<00:15:59.920> have<00:16:00.160> working<00:16:00.560> now 00:16:01.670 --> 00:16:01.680 align:start position:0% um so that's what we have working now 00:16:01.680 --> 00:16:03.430 align:start position:0% um so that's what we have working now but<00:16:01.839> we<00:16:02.000> also<00:16:02.240> have<00:16:02.399> a<00:16:02.480> vision<00:16:02.800> for<00:16:02.959> the<00:16:03.040> future 00:16:03.430 --> 00:16:03.440 align:start position:0% but we also have a vision for the future 00:16:03.440 --> 00:16:04.949 align:start position:0% but we also have a vision for the future because<00:16:03.680> we're<00:16:03.839> kind<00:16:04.079> of 00:16:04.949 --> 00:16:04.959 align:start position:0% because we're kind of 00:16:04.959 --> 00:16:06.790 align:start position:0% because we're kind of jboss<00:16:05.519> is<00:16:05.680> embracing<00:16:06.160> this<00:16:06.320> notion<00:16:06.720> of 00:16:06.790 --> 00:16:06.800 align:start position:0% jboss is embracing this notion of 00:16:06.800 --> 00:16:08.550 align:start position:0% jboss is embracing this notion of polyglot 00:16:08.550 --> 00:16:08.560 align:start position:0% polyglot 00:16:08.560 --> 00:16:10.069 align:start position:0% polyglot in<00:16:08.720> other<00:16:08.880> words 00:16:10.069 --> 00:16:10.079 align:start position:0% in other words 00:16:10.079 --> 00:16:12.629 align:start position:0% in other words you<00:16:10.399> use<00:16:10.639> the<00:16:10.800> best<00:16:11.040> framework<00:16:11.519> available 00:16:12.629 --> 00:16:12.639 align:start position:0% you use the best framework available 00:16:12.639 --> 00:16:14.629 align:start position:0% you use the best framework available on<00:16:12.800> the<00:16:12.959> jvm<00:16:13.680> regardless<00:16:14.240> of<00:16:14.320> what 00:16:14.629 --> 00:16:14.639 align:start position:0% on the jvm regardless of what 00:16:14.639 --> 00:16:15.910 align:start position:0% on the jvm regardless of what application 00:16:15.910 --> 00:16:15.920 align:start position:0% application 00:16:15.920 --> 00:16:19.110 align:start position:0% application it's<00:16:16.399> written<00:16:16.720> in<00:16:17.279> so<00:16:17.680> a<00:16:17.759> lot<00:16:17.920> of<00:16:18.079> people<00:16:18.880> have 00:16:19.110 --> 00:16:19.120 align:start position:0% it's written in so a lot of people have 00:16:19.120 --> 00:16:21.269 align:start position:0% it's written in so a lot of people have expertise<00:16:19.759> in<00:16:19.839> using<00:16:20.240> ruby<00:16:20.560> on<00:16:21.040> on<00:16:21.199> the 00:16:21.269 --> 00:16:21.279 align:start position:0% expertise in using ruby on on the 00:16:21.279 --> 00:16:22.949 align:start position:0% expertise in using ruby on on the website 00:16:22.949 --> 00:16:22.959 align:start position:0% website 00:16:22.959 --> 00:16:24.629 align:start position:0% website we<00:16:23.120> want<00:16:23.279> to<00:16:23.360> let<00:16:23.519> them<00:16:23.600> do<00:16:23.759> that<00:16:24.320> there<00:16:24.480> are 00:16:24.629 --> 00:16:24.639 align:start position:0% we want to let them do that there are 00:16:24.639 --> 00:16:27.110 align:start position:0% we want to let them do that there are great<00:16:24.880> analytics<00:16:25.440> packages<00:16:26.320> you<00:16:26.480> know<00:16:26.720> in 00:16:27.110 --> 00:16:27.120 align:start position:0% great analytics packages you know in 00:16:27.120 --> 00:16:34.069 align:start position:0% great analytics packages you know in closure<00:16:27.519> we<00:16:27.680> like<00:16:28.240> to<00:16:28.480> allow<00:16:28.880> them<00:16:29.519> to<00:16:29.839> easily 00:16:34.069 --> 00:16:34.079 align:start position:0% 00:16:34.079 --> 00:16:35.910 align:start position:0% exchange<00:16:34.639> messages<00:16:35.199> between<00:16:35.519> both<00:16:35.680> of<00:16:35.759> those 00:16:35.910 --> 00:16:35.920 align:start position:0% exchange messages between both of those 00:16:35.920 --> 00:16:39.670 align:start position:0% exchange messages between both of those producers<00:16:36.399> and<00:16:36.480> consumers 00:16:39.670 --> 00:16:39.680 align:start position:0% 00:16:39.680 --> 00:16:42.949 align:start position:0% currently<00:16:40.480> we<00:16:40.639> do<00:16:40.800> that<00:16:41.199> using 00:16:42.949 --> 00:16:42.959 align:start position:0% currently we do that using 00:16:42.959 --> 00:16:47.430 align:start position:0% currently we do that using json<00:16:43.680> encoding<00:16:44.399> but<00:16:44.560> we'd<00:16:44.800> love<00:16:45.120> to 00:16:47.430 --> 00:16:47.440 align:start position:0% 00:16:47.440 --> 00:16:51.030 align:start position:0% do<00:16:47.600> the<00:16:47.759> ruby<00:16:48.160> side<00:16:49.040> of<00:16:49.360> those<00:16:50.079> uh<00:16:50.480> tag-based 00:16:51.030 --> 00:16:51.040 align:start position:0% do the ruby side of those uh tag-based 00:16:51.040 --> 00:16:52.389 align:start position:0% do the ruby side of those uh tag-based serial<00:16:51.360> nation<00:16:51.600> stuff<00:16:51.839> that<00:16:51.920> brits<00:16:52.160> talked 00:16:52.389 --> 00:16:52.399 align:start position:0% serial nation stuff that brits talked 00:16:52.399 --> 00:16:54.790 align:start position:0% serial nation stuff that brits talked about<00:16:52.639> yesterday<00:16:53.600> um 00:16:54.790 --> 00:16:54.800 align:start position:0% about yesterday um 00:16:54.800 --> 00:16:56.710 align:start position:0% about yesterday um to<00:16:54.959> further<00:16:55.360> that 00:16:56.710 --> 00:16:56.720 align:start position:0% to further that 00:16:56.720 --> 00:16:58.470 align:start position:0% to further that so 00:16:58.470 --> 00:16:58.480 align:start position:0% so 00:16:58.480 --> 00:17:00.389 align:start position:0% so inner<00:16:58.720> language<00:16:59.120> messaging<00:17:00.079> you<00:17:00.240> know 00:17:00.389 --> 00:17:00.399 align:start position:0% inner language messaging you know 00:17:00.399 --> 00:17:02.150 align:start position:0% inner language messaging you know uniform<00:17:00.880> point<00:17:01.199> you<00:17:01.279> always<00:17:01.600> point<00:17:01.839> the<00:17:01.920> same 00:17:02.150 --> 00:17:02.160 align:start position:0% uniform point you always point the same 00:17:02.160 --> 00:17:03.829 align:start position:0% uniform point you always point the same way<00:17:02.720> you<00:17:02.800> know 00:17:03.829 --> 00:17:03.839 align:start position:0% way you know 00:17:03.839 --> 00:17:05.350 align:start position:0% way you know an<00:17:04.000> integrated<00:17:04.480> stack<00:17:04.799> you're<00:17:04.880> not<00:17:05.039> building 00:17:05.350 --> 00:17:05.360 align:start position:0% an integrated stack you're not building 00:17:05.360 --> 00:17:07.510 align:start position:0% an integrated stack you're not building up<00:17:05.520> your<00:17:05.600> stack<00:17:06.000> every<00:17:06.240> time 00:17:07.510 --> 00:17:07.520 align:start position:0% up your stack every time 00:17:07.520 --> 00:17:09.669 align:start position:0% up your stack every time and<00:17:07.679> we<00:17:07.839> get<00:17:08.240> a<00:17:08.559> very<00:17:08.880> simple<00:17:09.199> horizontal 00:17:09.669 --> 00:17:09.679 align:start position:0% and we get a very simple horizontal 00:17:09.679 --> 00:17:11.829 align:start position:0% and we get a very simple horizontal scaling<00:17:10.079> just<00:17:10.480> based<00:17:10.720> on<00:17:10.959> jboss's<00:17:11.520> built-in 00:17:11.829 --> 00:17:11.839 align:start position:0% scaling just based on jboss's built-in 00:17:11.839 --> 00:17:14.309 align:start position:0% scaling just based on jboss's built-in clustering<00:17:12.319> capabilities<00:17:13.360> to<00:17:13.520> where<00:17:13.839> you 00:17:14.309 --> 00:17:14.319 align:start position:0% clustering capabilities to where you 00:17:14.319 --> 00:17:17.189 align:start position:0% clustering capabilities to where you automatically<00:17:15.120> just<00:17:15.360> by<00:17:15.919> using<00:17:16.240> a<00:17:16.400> different 00:17:17.189 --> 00:17:17.199 align:start position:0% automatically just by using a different 00:17:17.199 --> 00:17:19.590 align:start position:0% automatically just by using a different command<00:17:17.600> line<00:17:18.000> option<00:17:18.720> you<00:17:18.880> get<00:17:19.120> automatic 00:17:19.590 --> 00:17:19.600 align:start position:0% command line option you get automatic 00:17:19.600 --> 00:17:22.069 align:start position:0% command line option you get automatic load<00:17:19.839> balancing<00:17:20.640> across<00:17:21.039> the<00:17:21.199> cluster<00:17:21.600> of<00:17:22.000> the 00:17:22.069 --> 00:17:22.079 align:start position:0% load balancing across the cluster of the 00:17:22.079 --> 00:17:23.829 align:start position:0% load balancing across the cluster of the mutants 00:17:23.829 --> 00:17:23.839 align:start position:0% mutants 00:17:23.839 --> 00:17:26.549 align:start position:0% mutants of<00:17:24.480> the<00:17:24.640> consumers<00:17:25.360> of<00:17:25.520> those<00:17:25.839> messages<00:17:26.400> that 00:17:26.549 --> 00:17:26.559 align:start position:0% of the consumers of those messages that 00:17:26.559 --> 00:17:29.669 align:start position:0% of the consumers of those messages that you<00:17:26.720> might<00:17:27.039> be<00:17:27.280> putting<00:17:27.600> on<00:17:27.760> whatever 00:17:29.669 --> 00:17:29.679 align:start position:0% you might be putting on whatever 00:17:29.679 --> 00:17:32.710 align:start position:0% you might be putting on whatever jms<00:17:30.160> destinations<00:17:30.880> there<00:17:31.039> are<00:17:31.520> so 00:17:32.710 --> 00:17:32.720 align:start position:0% jms destinations there are so 00:17:32.720 --> 00:17:35.909 align:start position:0% jms destinations there are so we<00:17:32.960> are<00:17:33.120> new<00:17:33.760> um<00:17:34.480> uh<00:17:34.720> we<00:17:35.120> we<00:17:35.280> love<00:17:35.440> the<00:17:35.520> help<00:17:35.760> for 00:17:35.909 --> 00:17:35.919 align:start position:0% we are new um uh we we love the help for 00:17:35.919 --> 00:17:39.669 align:start position:0% we are new um uh we we love the help for all<00:17:36.080> open<00:17:36.400> source 00:17:39.669 --> 00:17:39.679 align:start position:0% 00:17:39.679 --> 00:17:42.150 align:start position:0% either<00:17:40.000> by<00:17:40.559> helping<00:17:40.880> us<00:17:41.039> build<00:17:41.280> it<00:17:41.520> or<00:17:41.919> kind<00:17:42.080> of 00:17:42.150 --> 00:17:42.160 align:start position:0% either by helping us build it or kind of 00:17:42.160 --> 00:17:43.990 align:start position:0% either by helping us build it or kind of pull<00:17:42.480> us<00:17:42.640> in<00:17:42.720> a<00:17:42.799> direction<00:17:43.360> that<00:17:43.520> makes<00:17:43.760> sense 00:17:43.990 --> 00:17:44.000 align:start position:0% pull us in a direction that makes sense 00:17:44.000 --> 00:17:45.669 align:start position:0% pull us in a direction that makes sense for<00:17:44.080> your<00:17:44.240> organization 00:17:45.669 --> 00:17:45.679 align:start position:0% for your organization 00:17:45.679 --> 00:17:47.990 align:start position:0% for your organization free<00:17:45.840> note's<00:17:46.160> the<00:17:46.240> best<00:17:46.480> place<00:17:46.720> to<00:17:46.960> uh 00:17:47.990 --> 00:17:48.000 align:start position:0% free note's the best place to uh 00:17:48.000 --> 00:17:51.110 align:start position:0% free note's the best place to uh to<00:17:48.559> contact<00:17:49.120> us 00:17:51.110 --> 00:17:51.120 align:start position:0% to contact us 00:17:51.120 --> 00:17:52.230 align:start position:0% to contact us with<00:17:51.280> you 00:17:52.230 --> 00:17:52.240 align:start position:0% with you 00:17:52.240 --> 00:17:55.110 align:start position:0% with you contact<00:17:52.799> points.org 00:17:55.110 --> 00:17:55.120 align:start position:0% contact points.org 00:17:55.120 --> 00:18:08.549 align:start position:0% contact points.org that's<00:17:55.440> basically<00:17:55.760> all<00:17:55.919> i<00:17:56.000> got 00:18:08.549 --> 00:18:08.559 align:start position:0% 00:18:08.559 --> 00:18:12.549 align:start position:0% so<00:18:09.120> the<00:18:09.280> next<00:18:09.600> set<00:18:09.919> of<00:18:10.240> uh<00:18:10.799> presenters 00:18:12.549 --> 00:18:12.559 align:start position:0% so the next set of uh presenters 00:18:12.559 --> 00:18:13.750 align:start position:0% so the next set of uh presenters i<00:18:12.640> mean<00:18:12.799> i<00:18:12.799> guess<00:18:12.960> people<00:18:13.120> all<00:18:13.200> know<00:18:13.440> the<00:18:13.520> term 00:18:13.750 --> 00:18:13.760 align:start position:0% i mean i guess people all know the term 00:18:13.760 --> 00:18:16.230 align:start position:0% i mean i guess people all know the term hipster<00:18:14.320> uh<00:18:14.480> these<00:18:14.640> guys<00:18:14.799> are<00:18:14.960> lispsters<00:18:16.000> yeah 00:18:16.230 --> 00:18:16.240 align:start position:0% hipster uh these guys are lispsters yeah 00:18:16.240 --> 00:18:17.909 align:start position:0% hipster uh these guys are lispsters yeah use<00:18:16.400> that<00:18:16.559> ten<00:18:16.720> times<00:18:16.960> fast<00:18:17.280> and<00:18:17.440> uh<00:18:17.679> you<00:18:17.760> know 00:18:17.909 --> 00:18:17.919 align:start position:0% use that ten times fast and uh you know 00:18:17.919 --> 00:18:19.350 align:start position:0% use that ten times fast and uh you know make<00:18:18.080> your<00:18:18.240> brain<00:18:18.480> explode 00:18:19.350 --> 00:18:19.360 align:start position:0% make your brain explode 00:18:19.360 --> 00:18:20.789 align:start position:0% make your brain explode so<00:18:19.520> these<00:18:19.679> guys<00:18:20.000> uh 00:18:20.789 --> 00:18:20.799 align:start position:0% so these guys uh 00:18:20.799 --> 00:18:22.630 align:start position:0% so these guys uh uh<00:18:21.039> thoughts<00:18:21.440> that<00:18:21.679> uh<00:18:21.840> closure<00:18:22.240> was<00:18:22.320> cool<00:18:22.559> but 00:18:22.630 --> 00:18:22.640 align:start position:0% uh thoughts that uh closure was cool but 00:18:22.640 --> 00:18:24.310 align:start position:0% uh thoughts that uh closure was cool but they<00:18:22.799> want<00:18:22.880> to<00:18:22.960> do<00:18:23.120> something<00:18:23.360> cooler 00:18:24.310 --> 00:18:24.320 align:start position:0% they want to do something cooler 00:18:24.320 --> 00:18:25.909 align:start position:0% they want to do something cooler and<00:18:24.559> so<00:18:24.880> alan<00:18:25.200> and<00:18:25.280> john<00:18:25.440> are<00:18:25.520> gonna<00:18:25.679> talk<00:18:25.840> to 00:18:25.909 --> 00:18:25.919 align:start position:0% and so alan and john are gonna talk to 00:18:25.919 --> 00:18:28.950 align:start position:0% and so alan and john are gonna talk to you<00:18:26.000> about<00:18:26.320> uber<00:18:26.640> lisp 00:18:28.950 --> 00:18:28.960 align:start position:0% you about uber lisp 00:18:28.960 --> 00:18:31.190 align:start position:0% you about uber lisp um 00:18:31.190 --> 00:18:31.200 align:start position:0% um 00:18:31.200 --> 00:18:32.870 align:start position:0% um so<00:18:31.360> quick<00:18:31.520> show<00:18:31.760> hands<00:18:31.919> who's<00:18:32.160> familiar<00:18:32.559> with 00:18:32.870 --> 00:18:32.880 align:start position:0% so quick show hands who's familiar with 00:18:32.880 --> 00:18:36.070 align:start position:0% so quick show hands who's familiar with something<00:18:33.120> called<00:18:33.280> the<00:18:33.360> arduino 00:18:36.070 --> 00:18:36.080 align:start position:0% 00:18:36.080 --> 00:18:38.630 align:start position:0% oh<00:18:36.320> wow<00:18:36.960> okay 00:18:38.630 --> 00:18:38.640 align:start position:0% oh wow okay 00:18:38.640 --> 00:18:40.830 align:start position:0% oh wow okay so<00:18:38.880> for<00:18:39.039> the<00:18:39.120> two<00:18:39.280> people<00:18:39.520> that<00:18:39.600> haven't 00:18:40.830 --> 00:18:40.840 align:start position:0% so for the two people that haven't 00:18:40.840 --> 00:18:43.669 align:start position:0% so for the two people that haven't seen<00:18:41.919> it's<00:18:42.080> a<00:18:42.160> microcontroller 00:18:43.669 --> 00:18:43.679 align:start position:0% seen it's a microcontroller 00:18:43.679 --> 00:18:45.350 align:start position:0% seen it's a microcontroller it's<00:18:43.760> a<00:18:43.840> microcontroller<00:18:44.640> like<00:18:44.880> many<00:18:45.120> others 00:18:45.350 --> 00:18:45.360 align:start position:0% it's a microcontroller like many others 00:18:45.360 --> 00:18:47.350 align:start position:0% it's a microcontroller like many others with<00:18:46.080> capabilities<00:18:46.640> similar<00:18:46.960> to<00:18:47.039> many<00:18:47.200> other 00:18:47.350 --> 00:18:47.360 align:start position:0% with capabilities similar to many other 00:18:47.360 --> 00:18:49.110 align:start position:0% with capabilities similar to many other microcontrollers<00:18:48.080> like<00:18:48.240> the<00:18:48.320> pic<00:18:48.640> or<00:18:48.880> other 00:18:49.110 --> 00:18:49.120 align:start position:0% microcontrollers like the pic or other 00:18:49.120 --> 00:18:50.789 align:start position:0% microcontrollers like the pic or other things 00:18:50.789 --> 00:18:50.799 align:start position:0% things 00:18:50.799 --> 00:18:52.310 align:start position:0% things and<00:18:50.960> microcontroller<00:18:51.679> means<00:18:51.840> a<00:18:51.919> really<00:18:52.080> small 00:18:52.310 --> 00:18:52.320 align:start position:0% and microcontroller means a really small 00:18:52.320 --> 00:18:53.990 align:start position:0% and microcontroller means a really small computer<00:18:52.720> effectively 00:18:53.990 --> 00:18:54.000 align:start position:0% computer effectively 00:18:54.000 --> 00:18:55.510 align:start position:0% computer effectively the<00:18:54.160> differentiator<00:18:54.799> of<00:18:54.880> this<00:18:55.039> thing<00:18:55.280> is<00:18:55.440> that 00:18:55.510 --> 00:18:55.520 align:start position:0% the differentiator of this thing is that 00:18:55.520 --> 00:18:57.029 align:start position:0% the differentiator of this thing is that they're<00:18:55.760> cheap<00:18:56.320> the<00:18:56.400> cheapest<00:18:56.720> one<00:18:56.880> you<00:18:56.960> can 00:18:57.029 --> 00:18:57.039 align:start position:0% they're cheap the cheapest one you can 00:18:57.039 --> 00:18:59.430 align:start position:0% they're cheap the cheapest one you can get<00:18:57.280> is<00:18:57.440> about<00:18:57.600> ten<00:18:57.840> dollars<00:18:58.160> for<00:18:58.320> a<00:18:58.400> kit 00:18:59.430 --> 00:18:59.440 align:start position:0% get is about ten dollars for a kit 00:18:59.440 --> 00:19:00.710 align:start position:0% get is about ten dollars for a kit um 00:19:00.710 --> 00:19:00.720 align:start position:0% um 00:19:00.720 --> 00:19:01.750 align:start position:0% um the<00:19:00.799> other<00:19:00.960> thing<00:19:01.120> about<00:19:01.280> them<00:19:01.440> is<00:19:01.520> they<00:19:01.679> have 00:19:01.750 --> 00:19:01.760 align:start position:0% the other thing about them is they have 00:19:01.760 --> 00:19:03.909 align:start position:0% the other thing about them is they have easily<00:19:02.160> accessible<00:19:02.640> i<00:19:02.799> o<00:19:03.280> so<00:19:03.520> if<00:19:03.600> you're 00:19:03.909 --> 00:19:03.919 align:start position:0% easily accessible i o so if you're 00:19:03.919 --> 00:19:05.750 align:start position:0% easily accessible i o so if you're trying<00:19:04.160> to<00:19:04.480> do<00:19:04.799> any<00:19:04.960> kind<00:19:05.039> of<00:19:05.200> i<00:19:05.360> o<00:19:05.520> between 00:19:05.750 --> 00:19:05.760 align:start position:0% trying to do any kind of i o between 00:19:05.760 --> 00:19:07.190 align:start position:0% trying to do any kind of i o between your<00:19:05.919> computer<00:19:06.320> and<00:19:06.480> say 00:19:07.190 --> 00:19:07.200 align:start position:0% your computer and say 00:19:07.200 --> 00:19:08.710 align:start position:0% your computer and say your<00:19:07.440> toaster 00:19:08.710 --> 00:19:08.720 align:start position:0% your toaster 00:19:08.720 --> 00:19:10.310 align:start position:0% your toaster there's<00:19:08.880> not<00:19:09.039> like<00:19:09.200> a<00:19:09.280> usb<00:19:09.679> dude<00:19:10.000> that's<00:19:10.160> gonna 00:19:10.310 --> 00:19:10.320 align:start position:0% there's not like a usb dude that's gonna 00:19:10.320 --> 00:19:12.070 align:start position:0% there's not like a usb dude that's gonna do<00:19:10.480> that<00:19:10.640> for<00:19:10.799> you<00:19:11.039> that's<00:19:11.360> like<00:19:11.520> you<00:19:11.760> figuring 00:19:12.070 --> 00:19:12.080 align:start position:0% do that for you that's like you figuring 00:19:12.080 --> 00:19:14.230 align:start position:0% do that for you that's like you figuring out<00:19:12.240> the<00:19:12.320> usb<00:19:12.720> thingy<00:19:13.039> and<00:19:13.120> like<00:19:13.280> going<00:19:13.520> nuts 00:19:14.230 --> 00:19:14.240 align:start position:0% out the usb thingy and like going nuts 00:19:14.240 --> 00:19:16.870 align:start position:0% out the usb thingy and like going nuts um<00:19:14.480> the<00:19:14.640> arduino<00:19:15.120> has<00:19:15.360> rows<00:19:15.679> of<00:19:15.760> pins<00:19:16.640> plug 00:19:16.870 --> 00:19:16.880 align:start position:0% um the arduino has rows of pins plug 00:19:16.880 --> 00:19:18.390 align:start position:0% um the arduino has rows of pins plug wires<00:19:17.200> in<00:19:17.440> and<00:19:17.600> you<00:19:17.679> can<00:19:17.760> programmatically 00:19:18.390 --> 00:19:18.400 align:start position:0% wires in and you can programmatically 00:19:18.400 --> 00:19:19.750 align:start position:0% wires in and you can programmatically turn<00:19:18.559> those<00:19:18.720> things<00:19:19.039> on<00:19:19.280> and<00:19:19.440> off<00:19:19.600> with 00:19:19.750 --> 00:19:19.760 align:start position:0% turn those things on and off with 00:19:19.760 --> 00:19:21.029 align:start position:0% turn those things on and off with registers 00:19:21.029 --> 00:19:21.039 align:start position:0% registers 00:19:21.039 --> 00:19:23.029 align:start position:0% registers so<00:19:21.360> it's<00:19:21.520> a<00:19:21.600> great<00:19:21.760> little<00:19:22.000> platform<00:19:22.880> for 00:19:23.029 --> 00:19:23.039 align:start position:0% so it's a great little platform for 00:19:23.039 --> 00:19:25.430 align:start position:0% so it's a great little platform for doing<00:19:23.360> uh<00:19:23.520> prototyping<00:19:24.160> devices<00:19:24.880> that<00:19:25.360> you 00:19:25.430 --> 00:19:25.440 align:start position:0% doing uh prototyping devices that you 00:19:25.440 --> 00:19:26.950 align:start position:0% doing uh prototyping devices that you know<00:19:25.600> do<00:19:25.840> physical<00:19:26.160> or<00:19:26.400> electrical 00:19:26.950 --> 00:19:26.960 align:start position:0% know do physical or electrical 00:19:26.960 --> 00:19:29.510 align:start position:0% know do physical or electrical interactions<00:19:27.440> with<00:19:27.679> things<00:19:28.400> there's<00:19:28.640> a<00:19:29.280> huge 00:19:29.510 --> 00:19:29.520 align:start position:0% interactions with things there's a huge 00:19:29.520 --> 00:19:32.230 align:start position:0% interactions with things there's a huge hobby<00:19:29.840> community<00:19:30.160> around<00:19:30.480> these<00:19:30.640> things 00:19:32.230 --> 00:19:32.240 align:start position:0% hobby community around these things 00:19:32.240 --> 00:19:33.190 align:start position:0% hobby community around these things people<00:19:32.480> are<00:19:32.559> you<00:19:32.640> know<00:19:32.720> making<00:19:32.960> their<00:19:33.120> own 00:19:33.190 --> 00:19:33.200 align:start position:0% people are you know making their own 00:19:33.200 --> 00:19:35.350 align:start position:0% people are you know making their own garage<00:19:33.520> door<00:19:33.760> openers<00:19:34.240> and<00:19:34.400> you<00:19:34.559> know 00:19:35.350 --> 00:19:35.360 align:start position:0% garage door openers and you know 00:19:35.360 --> 00:19:36.950 align:start position:0% garage door openers and you know alarm<00:19:35.679> clocks<00:19:36.080> and<00:19:36.240> all<00:19:36.320> kinds<00:19:36.480> of<00:19:36.799> other 00:19:36.950 --> 00:19:36.960 align:start position:0% alarm clocks and all kinds of other 00:19:36.960 --> 00:19:41.750 align:start position:0% alarm clocks and all kinds of other really<00:19:37.200> mission<00:19:37.520> critically<00:19:37.840> useful<00:19:38.160> things 00:19:41.750 --> 00:19:41.760 align:start position:0% 00:19:41.760 --> 00:19:42.470 align:start position:0% so 00:19:42.470 --> 00:19:42.480 align:start position:0% so 00:19:42.480 --> 00:19:43.990 align:start position:0% so uh<00:19:42.720> i<00:19:42.799> got<00:19:42.960> into<00:19:43.200> this<00:19:43.280> thing<00:19:43.440> a<00:19:43.520> couple<00:19:43.760> years 00:19:43.990 --> 00:19:44.000 align:start position:0% uh i got into this thing a couple years 00:19:44.000 --> 00:19:45.750 align:start position:0% uh i got into this thing a couple years ago<00:19:44.400> and<00:19:44.720> you<00:19:44.799> know<00:19:44.960> i<00:19:45.039> bought<00:19:45.200> all<00:19:45.360> the<00:19:45.520> gear 00:19:45.750 --> 00:19:45.760 align:start position:0% ago and you know i bought all the gear 00:19:45.760 --> 00:19:47.270 align:start position:0% ago and you know i bought all the gear and<00:19:45.919> then<00:19:46.000> it<00:19:46.160> was<00:19:46.240> on<00:19:46.320> a<00:19:46.400> shelf<00:19:46.720> for<00:19:46.960> a<00:19:47.039> couple 00:19:47.270 --> 00:19:47.280 align:start position:0% and then it was on a shelf for a couple 00:19:47.280 --> 00:19:48.390 align:start position:0% and then it was on a shelf for a couple more<00:19:47.520> years 00:19:48.390 --> 00:19:48.400 align:start position:0% more years 00:19:48.400 --> 00:19:49.350 align:start position:0% more years and 00:19:49.350 --> 00:19:49.360 align:start position:0% and 00:19:49.360 --> 00:19:50.870 align:start position:0% and pulled<00:19:49.520> it<00:19:49.600> out<00:19:49.760> recently<00:19:50.400> uh<00:19:50.559> because<00:19:50.799> i 00:19:50.870 --> 00:19:50.880 align:start position:0% pulled it out recently uh because i 00:19:50.880 --> 00:19:52.390 align:start position:0% pulled it out recently uh because i wanted<00:19:51.039> to<00:19:51.120> make<00:19:51.280> some<00:19:51.440> cylon<00:19:51.840> lights<00:19:52.080> for<00:19:52.240> my 00:19:52.390 --> 00:19:52.400 align:start position:0% wanted to make some cylon lights for my 00:19:52.400 --> 00:19:56.470 align:start position:0% wanted to make some cylon lights for my pumpkins<00:19:52.799> around<00:19:52.960> halloween 00:19:56.470 --> 00:19:56.480 align:start position:0% 00:19:56.480 --> 00:19:58.950 align:start position:0% so<00:19:56.640> which<00:19:56.880> is<00:19:56.960> something<00:19:57.200> you<00:19:57.360> can<00:19:57.520> totally<00:19:57.840> do 00:19:58.950 --> 00:19:58.960 align:start position:0% so which is something you can totally do 00:19:58.960 --> 00:20:00.470 align:start position:0% so which is something you can totally do and<00:19:59.200> it's<00:19:59.360> pretty<00:19:59.520> straightforward<00:20:00.320> but 00:20:00.470 --> 00:20:00.480 align:start position:0% and it's pretty straightforward but 00:20:00.480 --> 00:20:01.750 align:start position:0% and it's pretty straightforward but here's<00:20:00.720> the<00:20:00.880> pickle 00:20:01.750 --> 00:20:01.760 align:start position:0% here's the pickle 00:20:01.760 --> 00:20:04.470 align:start position:0% here's the pickle uh<00:20:02.480> you<00:20:02.640> can't<00:20:02.799> do<00:20:02.960> it<00:20:03.120> in<00:20:03.200> lisp 00:20:04.470 --> 00:20:04.480 align:start position:0% uh you can't do it in lisp 00:20:04.480 --> 00:20:05.990 align:start position:0% uh you can't do it in lisp and<00:20:04.880> i<00:20:04.960> think<00:20:05.120> we<00:20:05.200> all<00:20:05.360> know<00:20:05.600> as<00:20:05.840> you<00:20:05.919> know 00:20:05.990 --> 00:20:06.000 align:start position:0% and i think we all know as you know 00:20:06.000 --> 00:20:07.750 align:start position:0% and i think we all know as you know people<00:20:06.240> who<00:20:06.559> are<00:20:06.720> just<00:20:06.960> obsessed<00:20:07.280> with<00:20:07.440> lisp 00:20:07.750 --> 00:20:07.760 align:start position:0% people who are just obsessed with lisp 00:20:07.760 --> 00:20:08.950 align:start position:0% people who are just obsessed with lisp and<00:20:07.919> sort<00:20:08.080> of<00:20:08.159> can<00:20:08.320> look<00:20:08.400> at<00:20:08.559> other<00:20:08.720> things<00:20:08.880> and 00:20:08.950 --> 00:20:08.960 align:start position:0% and sort of can look at other things and 00:20:08.960 --> 00:20:10.149 align:start position:0% and sort of can look at other things and be<00:20:09.039> like<00:20:09.280> yeah 00:20:10.149 --> 00:20:10.159 align:start position:0% be like yeah 00:20:10.159 --> 00:20:11.270 align:start position:0% be like yeah um 00:20:11.270 --> 00:20:11.280 align:start position:0% um 00:20:11.280 --> 00:20:12.870 align:start position:0% um i<00:20:11.440> really<00:20:11.600> miss<00:20:11.919> lisp 00:20:12.870 --> 00:20:12.880 align:start position:0% i really miss lisp 00:20:12.880 --> 00:20:14.230 align:start position:0% i really miss lisp uh<00:20:13.120> it's<00:20:13.280> kind<00:20:13.440> of<00:20:13.520> cool<00:20:13.760> you<00:20:13.840> can<00:20:13.919> do<00:20:14.080> this 00:20:14.230 --> 00:20:14.240 align:start position:0% uh it's kind of cool you can do this 00:20:14.240 --> 00:20:15.029 align:start position:0% uh it's kind of cool you can do this thing 00:20:15.029 --> 00:20:15.039 align:start position:0% thing 00:20:15.039 --> 00:20:15.750 align:start position:0% thing but 00:20:15.750 --> 00:20:15.760 align:start position:0% but 00:20:15.760 --> 00:20:17.830 align:start position:0% but it's<00:20:15.840> not<00:20:16.080> lisp<00:20:16.640> so 00:20:17.830 --> 00:20:17.840 align:start position:0% it's not lisp so 00:20:17.840 --> 00:20:20.149 align:start position:0% it's not lisp so um 00:20:20.149 --> 00:20:20.159 align:start position:0% um 00:20:20.159 --> 00:20:22.070 align:start position:0% um i<00:20:20.320> had<00:20:20.480> this<00:20:20.640> idea<00:20:21.039> to<00:20:21.200> write<00:20:21.360> a<00:20:21.520> list<00:20:21.919> that 00:20:22.070 --> 00:20:22.080 align:start position:0% i had this idea to write a list that 00:20:22.080 --> 00:20:24.070 align:start position:0% i had this idea to write a list that would<00:20:22.240> run<00:20:22.480> on<00:20:22.559> the<00:20:22.720> arduino<00:20:23.360> so<00:20:23.520> i<00:20:23.760> could<00:20:23.919> do 00:20:24.070 --> 00:20:24.080 align:start position:0% would run on the arduino so i could do 00:20:24.080 --> 00:20:25.590 align:start position:0% would run on the arduino so i could do the<00:20:24.159> same<00:20:24.400> kind<00:20:24.559> of<00:20:24.720> interactive<00:20:25.200> real-time 00:20:25.590 --> 00:20:25.600 align:start position:0% the same kind of interactive real-time 00:20:25.600 --> 00:20:27.510 align:start position:0% the same kind of interactive real-time development<00:20:26.080> on<00:20:26.240> a<00:20:26.320> microcontroller<00:20:27.360> that 00:20:27.510 --> 00:20:27.520 align:start position:0% development on a microcontroller that 00:20:27.520 --> 00:20:29.750 align:start position:0% development on a microcontroller that i'm<00:20:27.679> used<00:20:27.840> to<00:20:28.000> a<00:20:28.240> closure<00:20:28.559> replica 00:20:29.750 --> 00:20:29.760 align:start position:0% i'm used to a closure replica 00:20:29.760 --> 00:20:31.990 align:start position:0% i'm used to a closure replica um<00:20:30.480> i<00:20:30.640> wasn't<00:20:30.880> sure<00:20:31.039> if<00:20:31.120> it<00:20:31.200> was<00:20:31.360> possible<00:20:31.679> but 00:20:31.990 --> 00:20:32.000 align:start position:0% um i wasn't sure if it was possible but 00:20:32.000 --> 00:20:33.430 align:start position:0% um i wasn't sure if it was possible but i<00:20:32.159> started<00:20:32.480> anyway 00:20:33.430 --> 00:20:33.440 align:start position:0% i started anyway 00:20:33.440 --> 00:20:35.510 align:start position:0% i started anyway uh 00:20:35.510 --> 00:20:35.520 align:start position:0% uh 00:20:35.520 --> 00:20:37.590 align:start position:0% uh and<00:20:35.919> you<00:20:36.000> know<00:20:36.159> list<00:20:36.400> from<00:20:36.559> the<00:20:36.640> bottom<00:20:37.280> uh<00:20:37.440> if 00:20:37.590 --> 00:20:37.600 align:start position:0% and you know list from the bottom uh if 00:20:37.600 --> 00:20:39.430 align:start position:0% and you know list from the bottom uh if you<00:20:37.679> haven't<00:20:37.919> done<00:20:38.159> it<00:20:38.640> implemented<00:20:39.120> it<00:20:39.360> i 00:20:39.430 --> 00:20:39.440 align:start position:0% you haven't done it implemented it i 00:20:39.440 --> 00:20:40.870 align:start position:0% you haven't done it implemented it i think<00:20:39.600> this<00:20:39.760> paul<00:20:40.000> graham<00:20:40.320> talks<00:20:40.559> about<00:20:40.720> like 00:20:40.870 --> 00:20:40.880 align:start position:0% think this paul graham talks about like 00:20:40.880 --> 00:20:41.750 align:start position:0% think this paul graham talks about like the 00:20:41.750 --> 00:20:41.760 align:start position:0% the 00:20:41.760 --> 00:20:43.270 align:start position:0% the there's<00:20:42.080> like<00:20:42.320> these<00:20:42.559> two<00:20:42.799> things<00:20:43.039> that<00:20:43.200> are 00:20:43.270 --> 00:20:43.280 align:start position:0% there's like these two things that are 00:20:43.280 --> 00:20:45.029 align:start position:0% there's like these two things that are high<00:20:43.440> ground<00:20:43.760> see<00:20:44.000> on<00:20:44.080> one<00:20:44.320> end<00:20:44.480> and<00:20:44.640> list<00:20:44.960> on 00:20:45.029 --> 00:20:45.039 align:start position:0% high ground see on one end and list on 00:20:45.039 --> 00:20:45.990 align:start position:0% high ground see on one end and list on the<00:20:45.120> other 00:20:45.990 --> 00:20:46.000 align:start position:0% the other 00:20:46.000 --> 00:20:47.350 align:start position:0% the other it's<00:20:46.159> actually<00:20:46.320> a<00:20:46.400> really<00:20:46.559> cool<00:20:46.799> exercise<00:20:47.280> to 00:20:47.350 --> 00:20:47.360 align:start position:0% it's actually a really cool exercise to 00:20:47.360 --> 00:20:48.870 align:start position:0% it's actually a really cool exercise to kind<00:20:47.520> of<00:20:47.600> start<00:20:47.840> at<00:20:47.919> one<00:20:48.159> end<00:20:48.400> and<00:20:48.480> then<00:20:48.720> you 00:20:48.870 --> 00:20:48.880 align:start position:0% kind of start at one end and then you 00:20:48.880 --> 00:20:50.710 align:start position:0% kind of start at one end and then you kind<00:20:48.960> of<00:20:49.600> wade<00:20:49.840> through<00:20:50.000> the<00:20:50.080> morass<00:20:50.559> and<00:20:50.640> then 00:20:50.710 --> 00:20:50.720 align:start position:0% kind of wade through the morass and then 00:20:50.720 --> 00:20:52.630 align:start position:0% kind of wade through the morass and then you<00:20:50.799> kind<00:20:50.880> of<00:20:50.960> get<00:20:51.200> closer<00:20:51.520> to<00:20:51.520> the<00:20:51.600> lift<00:20:51.840> side 00:20:52.630 --> 00:20:52.640 align:start position:0% you kind of get closer to the lift side 00:20:52.640 --> 00:20:54.470 align:start position:0% you kind of get closer to the lift side and<00:20:52.799> like<00:20:53.440> you<00:20:53.600> can<00:20:53.679> start<00:20:53.919> to<00:20:54.000> see<00:20:54.159> the<00:20:54.240> sky 00:20:54.470 --> 00:20:54.480 align:start position:0% and like you can start to see the sky 00:20:54.480 --> 00:20:56.470 align:start position:0% and like you can start to see the sky again<00:20:54.880> and<00:20:54.960> then<00:20:55.280> you<00:20:55.440> have<00:20:55.520> a<00:20:55.600> lisp 00:20:56.470 --> 00:20:56.480 align:start position:0% again and then you have a lisp 00:20:56.480 --> 00:20:58.230 align:start position:0% again and then you have a lisp uh<00:20:56.799> so<00:20:57.120> if<00:20:57.280> you<00:20:57.360> haven't<00:20:57.520> made<00:20:57.679> your<00:20:57.840> own<00:20:57.919> list 00:20:58.230 --> 00:20:58.240 align:start position:0% uh so if you haven't made your own list 00:20:58.240 --> 00:21:00.390 align:start position:0% uh so if you haven't made your own list i<00:20:58.320> really<00:20:58.480> recommend<00:20:58.960> it<00:20:59.440> um<00:20:59.919> as<00:21:00.080> far<00:21:00.240> as<00:21:00.320> the 00:21:00.390 --> 00:21:00.400 align:start position:0% i really recommend it um as far as the 00:21:00.400 --> 00:21:03.029 align:start position:0% i really recommend it um as far as the rationale<00:21:00.880> for<00:21:01.039> doing<00:21:01.360> it<00:21:02.000> uh 00:21:03.029 --> 00:21:03.039 align:start position:0% rationale for doing it uh 00:21:03.039 --> 00:21:05.110 align:start position:0% rationale for doing it uh conspicuously<00:21:03.760> on<00:21:03.840> the<00:21:04.080> cloture.org<00:21:04.799> website 00:21:05.110 --> 00:21:05.120 align:start position:0% conspicuously on the cloture.org website 00:21:05.120 --> 00:21:06.870 align:start position:0% conspicuously on the cloture.org website on<00:21:05.200> the<00:21:05.280> rationale<00:21:06.000> which<00:21:06.400> says<00:21:06.640> you<00:21:06.720> know<00:21:06.799> i 00:21:06.870 --> 00:21:06.880 align:start position:0% on the rationale which says you know i 00:21:06.880 --> 00:21:08.789 align:start position:0% on the rationale which says you know i needed<00:21:07.120> it<00:21:07.200> for<00:21:07.360> functional<00:21:07.760> programming<00:21:08.720> all 00:21:08.789 --> 00:21:08.799 align:start position:0% needed it for functional programming all 00:21:08.799 --> 00:21:10.070 align:start position:0% needed it for functional programming all these<00:21:08.960> things<00:21:09.200> and<00:21:09.280> then<00:21:09.360> i<00:21:09.440> needed<00:21:09.679> a<00:21:09.760> list 00:21:10.070 --> 00:21:10.080 align:start position:0% these things and then i needed a list 00:21:10.080 --> 00:21:12.149 align:start position:0% these things and then i needed a list with<00:21:10.240> like<00:21:10.400> no<00:21:10.559> further<00:21:10.799> justification 00:21:12.149 --> 00:21:12.159 align:start position:0% with like no further justification 00:21:12.159 --> 00:21:12.950 align:start position:0% with like no further justification so 00:21:12.950 --> 00:21:12.960 align:start position:0% so 00:21:12.960 --> 00:21:15.510 align:start position:0% so if<00:21:13.120> this<00:21:13.360> truth<00:21:13.840> is<00:21:14.000> self-evident<00:21:15.120> just<00:21:15.280> go 00:21:15.510 --> 00:21:15.520 align:start position:0% if this truth is self-evident just go 00:21:15.520 --> 00:21:17.830 align:start position:0% if this truth is self-evident just go nuts<00:21:15.919> doesn't<00:21:16.159> matter<00:21:16.400> if<00:21:16.480> there's<00:21:16.640> a<00:21:16.720> problem 00:21:17.830 --> 00:21:17.840 align:start position:0% nuts doesn't matter if there's a problem 00:21:17.840 --> 00:21:19.029 align:start position:0% nuts doesn't matter if there's a problem uh<00:21:18.080> the<00:21:18.240> fact<00:21:18.400> that<00:21:18.480> you<00:21:18.640> haven't<00:21:18.799> written 00:21:19.029 --> 00:21:19.039 align:start position:0% uh the fact that you haven't written 00:21:19.039 --> 00:21:22.310 align:start position:0% uh the fact that you haven't written your<00:21:19.200> own<00:21:19.280> list<00:21:19.600> is<00:21:19.679> the<00:21:19.760> real<00:21:19.919> problem 00:21:22.310 --> 00:21:22.320 align:start position:0% 00:21:22.320 --> 00:21:24.549 align:start position:0% so<00:21:22.799> without<00:21:23.120> further<00:21:23.440> ado<00:21:23.840> uh<00:21:24.080> john's<00:21:24.400> gonna 00:21:24.549 --> 00:21:24.559 align:start position:0% so without further ado uh john's gonna 00:21:24.559 --> 00:21:25.990 align:start position:0% so without further ado uh john's gonna do<00:21:24.640> a<00:21:24.720> little<00:21:24.880> demo<00:21:25.200> here 00:21:25.990 --> 00:21:26.000 align:start position:0% do a little demo here 00:21:26.000 --> 00:21:27.430 align:start position:0% do a little demo here um 00:21:27.430 --> 00:21:27.440 align:start position:0% um 00:21:27.440 --> 00:21:29.510 align:start position:0% um quick<00:21:27.840> text<00:21:28.159> specs<00:21:28.480> and<00:21:28.559> highlights<00:21:29.200> so<00:21:29.360> this 00:21:29.510 --> 00:21:29.520 align:start position:0% quick text specs and highlights so this 00:21:29.520 --> 00:21:31.590 align:start position:0% quick text specs and highlights so this thing<00:21:29.760> has<00:21:29.919> 2k<00:21:30.400> of<00:21:30.480> ram 00:21:31.590 --> 00:21:31.600 align:start position:0% thing has 2k of ram 00:21:31.600 --> 00:21:33.510 align:start position:0% thing has 2k of ram that's<00:21:32.080> almost<00:21:32.559> 15<00:21:32.960> tweets<00:21:33.200> worth<00:21:33.440> of 00:21:33.510 --> 00:21:33.520 align:start position:0% that's almost 15 tweets worth of 00:21:33.520 --> 00:21:35.909 align:start position:0% that's almost 15 tweets worth of information 00:21:35.909 --> 00:21:35.919 align:start position:0% information 00:21:35.919 --> 00:21:37.909 align:start position:0% information we've<00:21:36.159> got<00:21:36.400> lexical<00:21:36.880> scope<00:21:37.440> first<00:21:37.679> cost 00:21:37.909 --> 00:21:37.919 align:start position:0% we've got lexical scope first cost 00:21:37.919 --> 00:21:39.830 align:start position:0% we've got lexical scope first cost functions<00:21:38.880> all<00:21:39.039> these<00:21:39.200> things<00:21:39.440> that<00:21:39.520> we<00:21:39.679> know 00:21:39.830 --> 00:21:39.840 align:start position:0% functions all these things that we know 00:21:39.840 --> 00:21:41.270 align:start position:0% functions all these things that we know and<00:21:39.919> love<00:21:40.559> and 00:21:41.270 --> 00:21:41.280 align:start position:0% and love and 00:21:41.280 --> 00:21:43.190 align:start position:0% and love and thanks<00:21:41.520> in<00:21:41.600> john's<00:21:41.919> health 00:21:43.190 --> 00:21:43.200 align:start position:0% thanks in john's health 00:21:43.200 --> 00:21:44.549 align:start position:0% thanks in john's health it<00:21:43.360> all<00:21:43.440> kind<00:21:43.520> of<00:21:43.679> works<00:21:43.919> i<00:21:44.000> told<00:21:44.159> him<00:21:44.320> about 00:21:44.549 --> 00:21:44.559 align:start position:0% it all kind of works i told him about 00:21:44.559 --> 00:21:46.310 align:start position:0% it all kind of works i told him about this<00:21:44.720> idea 00:21:46.310 --> 00:21:46.320 align:start position:0% this idea 00:21:46.320 --> 00:21:48.549 align:start position:0% this idea in<00:21:46.400> the<00:21:46.480> morning<00:21:46.880> after<00:21:47.200> i<00:21:47.520> saw<00:21:47.679> i<00:21:47.760> got<00:21:48.000> like<00:21:48.159> 10 00:21:48.549 --> 00:21:48.559 align:start position:0% in the morning after i saw i got like 10 00:21:48.559 --> 00:21:50.149 align:start position:0% in the morning after i saw i got like 10 emails<00:21:49.039> between<00:21:49.280> the<00:21:49.440> hours<00:21:49.600> of<00:21:49.760> midnight<00:21:50.080> at 00:21:50.149 --> 00:21:50.159 align:start position:0% emails between the hours of midnight at 00:21:50.159 --> 00:21:53.990 align:start position:0% emails between the hours of midnight at 5am<00:21:50.720> and<00:21:50.799> then<00:21:50.960> my<00:21:51.200> birthday 00:21:53.990 --> 00:21:54.000 align:start position:0% 00:21:54.000 --> 00:21:56.149 align:start position:0% he's<00:21:54.559> done<00:21:54.799> a<00:21:54.880> lot<00:21:55.200> with 00:21:56.149 --> 00:21:56.159 align:start position:0% he's done a lot with 00:21:56.159 --> 00:21:58.070 align:start position:0% he's done a lot with figuring<00:21:56.559> out<00:21:56.720> how<00:21:56.960> exactly<00:21:57.280> these<00:21:57.520> ideas<00:21:57.840> map 00:21:58.070 --> 00:21:58.080 align:start position:0% figuring out how exactly these ideas map 00:21:58.080 --> 00:21:59.430 align:start position:0% figuring out how exactly these ideas map the<00:21:58.159> lower<00:21:58.400> level<00:21:58.640> things<00:21:58.960> like<00:21:59.120> reading 00:21:59.430 --> 00:21:59.440 align:start position:0% the lower level things like reading 00:21:59.440 --> 00:22:01.430 align:start position:0% the lower level things like reading specs<00:21:59.760> and<00:21:59.919> data<00:22:00.240> sheets<00:22:00.559> and 00:22:01.430 --> 00:22:01.440 align:start position:0% specs and data sheets and 00:22:01.440 --> 00:22:03.350 align:start position:0% specs and data sheets and uh<00:22:01.919> he's<00:22:02.159> kind<00:22:02.320> of<00:22:02.400> the<00:22:02.480> wizard<00:22:02.799> between<00:22:03.200> how 00:22:03.350 --> 00:22:03.360 align:start position:0% uh he's kind of the wizard between how 00:22:03.360 --> 00:22:05.110 align:start position:0% uh he's kind of the wizard between how it<00:22:03.520> actually<00:22:03.760> works<00:22:04.080> my<00:22:04.240> initial 00:22:05.110 --> 00:22:05.120 align:start position:0% it actually works my initial 00:22:05.120 --> 00:22:07.029 align:start position:0% it actually works my initial my<00:22:05.280> initial<00:22:05.600> pass<00:22:05.840> was 00:22:07.029 --> 00:22:07.039 align:start position:0% my initial pass was 00:22:07.039 --> 00:22:24.789 align:start position:0% my initial pass was was<00:22:07.280> garbage<00:22:07.679> and<00:22:07.840> was<00:22:08.000> collected 00:22:24.789 --> 00:22:24.799 align:start position:0% 00:22:24.799 --> 00:22:30.470 align:start position:0% you 00:22:30.470 --> 00:22:30.480 align:start position:0% 00:22:30.480 --> 00:22:32.070 align:start position:0% microphone<00:22:30.960> works 00:22:32.070 --> 00:22:32.080 align:start position:0% microphone works 00:22:32.080 --> 00:22:35.510 align:start position:0% microphone works uh<00:22:32.559> so<00:22:33.120> this<00:22:33.280> thing's<00:22:33.600> written<00:22:33.840> in<00:22:34.000> c<00:22:34.400> uh 00:22:35.510 --> 00:22:35.520 align:start position:0% uh so this thing's written in c uh 00:22:35.520 --> 00:22:36.630 align:start position:0% uh so this thing's written in c uh i<00:22:35.600> don't<00:22:35.760> need<00:22:35.840> to<00:22:35.919> show<00:22:36.080> you<00:22:36.159> the<00:22:36.240> source<00:22:36.480> code 00:22:36.630 --> 00:22:36.640 align:start position:0% i don't need to show you the source code 00:22:36.640 --> 00:22:37.669 align:start position:0% i don't need to show you the source code right<00:22:36.799> now<00:22:36.960> but 00:22:37.669 --> 00:22:37.679 align:start position:0% right now but 00:22:37.679 --> 00:22:38.630 align:start position:0% right now but um 00:22:38.630 --> 00:22:38.640 align:start position:0% um 00:22:38.640 --> 00:22:41.029 align:start position:0% um it's<00:22:38.880> plugged<00:22:39.280> in<00:22:39.600> we<00:22:39.760> wrote<00:22:40.000> some<00:22:40.159> make<00:22:40.400> tasks 00:22:41.029 --> 00:22:41.039 align:start position:0% it's plugged in we wrote some make tasks 00:22:41.039 --> 00:22:42.470 align:start position:0% it's plugged in we wrote some make tasks that<00:22:41.360> uh 00:22:42.470 --> 00:22:42.480 align:start position:0% that uh 00:22:42.480 --> 00:22:44.549 align:start position:0% that uh build<00:22:42.799> and<00:22:42.960> flash<00:22:43.600> the<00:22:43.760> arduino<00:22:44.320> so<00:22:44.480> we're 00:22:44.549 --> 00:22:44.559 align:start position:0% build and flash the arduino so we're 00:22:44.559 --> 00:22:47.029 align:start position:0% build and flash the arduino so we're going<00:22:44.640> to<00:22:44.799> clean 00:22:47.029 --> 00:22:47.039 align:start position:0% going to clean 00:22:47.039 --> 00:22:48.230 align:start position:0% going to clean see 00:22:48.230 --> 00:22:48.240 align:start position:0% see 00:22:48.240 --> 00:22:51.830 align:start position:0% see i'm<00:22:48.400> running<00:22:48.640> this<00:22:48.880> on<00:22:48.960> a<00:22:49.200> do<00:22:49.440> a<00:22:49.600> millino 00:22:51.830 --> 00:22:51.840 align:start position:0% i'm running this on a do a millino 00:22:51.840 --> 00:22:53.430 align:start position:0% i'm running this on a do a millino because<00:22:52.159> i<00:22:52.320> like<00:22:52.559> the 00:22:53.430 --> 00:22:53.440 align:start position:0% because i like the 00:22:53.440 --> 00:22:55.990 align:start position:0% because i like the usb<00:22:53.919> to<00:22:54.080> serial<00:22:54.720> thing<00:22:54.960> better<00:22:55.520> than<00:22:55.679> the<00:22:55.760> one 00:22:55.990 --> 00:22:56.000 align:start position:0% usb to serial thing better than the one 00:22:56.000 --> 00:22:58.149 align:start position:0% usb to serial thing better than the one that<00:22:56.080> you<00:22:56.240> know<00:22:56.960> you<00:22:57.200> know<00:22:57.360> actually<00:22:57.840> is<00:22:58.080> a 00:22:58.149 --> 00:22:58.159 align:start position:0% that you know you know actually is a 00:22:58.159 --> 00:23:03.029 align:start position:0% that you know you know actually is a real<00:22:58.400> pain<00:22:58.640> to<00:22:58.720> deal<00:22:58.880> with 00:23:03.029 --> 00:23:03.039 align:start position:0% 00:23:03.039 --> 00:23:05.510 align:start position:0% so<00:23:03.200> here<00:23:03.360> we<00:23:03.440> go 00:23:05.510 --> 00:23:05.520 align:start position:0% so here we go 00:23:05.520 --> 00:23:10.549 align:start position:0% so here we go that's<00:23:05.840> flashing 00:23:10.549 --> 00:23:10.559 align:start position:0% 00:23:10.559 --> 00:23:11.990 align:start position:0% it<00:23:10.720> got<00:23:10.880> really<00:23:11.120> big<00:23:11.360> yesterday<00:23:11.760> when<00:23:11.919> i 00:23:11.990 --> 00:23:12.000 align:start position:0% it got really big yesterday when i 00:23:12.000 --> 00:23:13.590 align:start position:0% it got really big yesterday when i included<00:23:12.320> the<00:23:12.400> delay<00:23:12.799> library<00:23:13.280> i<00:23:13.360> don't<00:23:13.440> know 00:23:13.590 --> 00:23:13.600 align:start position:0% included the delay library i don't know 00:23:13.600 --> 00:23:15.990 align:start position:0% included the delay library i don't know why<00:23:14.080> i'll<00:23:14.240> figure<00:23:14.559> that<00:23:14.640> out<00:23:14.880> tomorrow 00:23:15.990 --> 00:23:16.000 align:start position:0% why i'll figure that out tomorrow 00:23:16.000 --> 00:23:17.190 align:start position:0% why i'll figure that out tomorrow so<00:23:16.159> here<00:23:16.320> we<00:23:16.400> go 00:23:17.190 --> 00:23:17.200 align:start position:0% so here we go 00:23:17.200 --> 00:23:18.950 align:start position:0% so here we go or<00:23:17.440> tonight 00:23:18.950 --> 00:23:18.960 align:start position:0% or tonight 00:23:18.960 --> 00:23:20.710 align:start position:0% or tonight uh<00:23:19.200> i<00:23:19.280> got<00:23:19.360> some<00:23:19.520> device 00:23:20.710 --> 00:23:20.720 align:start position:0% uh i got some device 00:23:20.720 --> 00:23:22.390 align:start position:0% uh i got some device we<00:23:20.880> basically<00:23:21.280> got<00:23:21.440> a<00:23:21.520> rebel<00:23:21.919> now<00:23:22.080> you<00:23:22.159> can<00:23:22.240> see 00:23:22.390 --> 00:23:22.400 align:start position:0% we basically got a rebel now you can see 00:23:22.400 --> 00:23:23.990 align:start position:0% we basically got a rebel now you can see at<00:23:22.480> the<00:23:22.559> top<00:23:22.720> we've<00:23:22.880> defined<00:23:23.360> all<00:23:23.600> those 00:23:23.990 --> 00:23:24.000 align:start position:0% at the top we've defined all those 00:23:24.000 --> 00:23:26.630 align:start position:0% at the top we've defined all those symbols<00:23:24.799> to<00:23:24.960> be<00:23:25.120> themselves<00:23:26.159> uh<00:23:26.400> because 00:23:26.630 --> 00:23:26.640 align:start position:0% symbols to be themselves uh because 00:23:26.640 --> 00:23:27.990 align:start position:0% symbols to be themselves uh because those<00:23:26.799> are<00:23:26.960> special 00:23:27.990 --> 00:23:28.000 align:start position:0% those are special 00:23:28.000 --> 00:23:29.190 align:start position:0% those are special um 00:23:29.190 --> 00:23:29.200 align:start position:0% um 00:23:29.200 --> 00:23:30.310 align:start position:0% um and 00:23:30.310 --> 00:23:30.320 align:start position:0% and 00:23:30.320 --> 00:23:32.149 align:start position:0% and let's<00:23:30.480> run<00:23:30.720> your<00:23:30.880> marks 00:23:32.149 --> 00:23:32.159 align:start position:0% let's run your marks 00:23:32.159 --> 00:23:34.310 align:start position:0% let's run your marks you<00:23:32.240> don't<00:23:32.480> have<00:23:32.640> to<00:23:32.880> type<00:23:33.200> anything 00:23:34.310 --> 00:23:34.320 align:start position:0% you don't have to type anything 00:23:34.320 --> 00:23:36.470 align:start position:0% you don't have to type anything we're<00:23:34.480> going<00:23:34.559> to<00:23:34.720> show<00:23:34.960> you<00:23:35.840> some<00:23:36.000> exciting 00:23:36.470 --> 00:23:36.480 align:start position:0% we're going to show you some exciting 00:23:36.480 --> 00:24:02.070 align:start position:0% we're going to show you some exciting things 00:24:02.070 --> 00:24:02.080 align:start position:0% 00:24:02.080 --> 00:24:04.789 align:start position:0% no<00:24:02.240> gc<00:24:02.640> either<00:24:02.960> yet<00:24:03.279> uh<00:24:03.600> so<00:24:03.919> we<00:24:04.080> can't<00:24:04.320> type<00:24:04.559> in 00:24:04.789 --> 00:24:04.799 align:start position:0% no gc either yet uh so we can't type in 00:24:04.799 --> 00:24:07.269 align:start position:0% no gc either yet uh so we can't type in very<00:24:04.960> much<00:24:05.120> stuff 00:24:07.269 --> 00:24:07.279 align:start position:0% very much stuff 00:24:07.279 --> 00:24:16.830 align:start position:0% very much stuff i<00:24:07.520> noticed<00:24:07.840> the<00:24:07.919> memory 00:24:16.830 --> 00:24:16.840 align:start position:0% 00:24:16.840 --> 00:24:37.269 align:start position:0% user<00:24:17.919> important 00:24:37.269 --> 00:24:37.279 align:start position:0% 00:24:37.279 --> 00:25:12.310 align:start position:0% rule<00:24:37.520> of<00:24:37.600> demons 00:25:12.310 --> 00:25:12.320 align:start position:0% 00:25:12.320 --> 00:25:25.430 align:start position:0% are<00:25:12.480> we<00:25:12.559> doing<00:25:12.720> it<00:25:12.799> on 00:25:25.430 --> 00:25:25.440 align:start position:0% 00:25:25.440 --> 00:25:36.230 align:start position:0% right 00:25:36.230 --> 00:25:36.240 align:start position:0% 00:25:36.240 --> 00:26:02.789 align:start position:0% that<00:25:36.400> works<00:25:36.799> e-max<00:25:37.200> is<00:25:37.279> a<00:25:37.360> problem 00:26:02.789 --> 00:26:02.799 align:start position:0% 00:26:02.799 --> 00:26:04.950 align:start position:0% yeah<00:26:03.360> all<00:26:03.520> right<00:26:03.760> so<00:26:04.080> i<00:26:04.240> gotta<00:26:04.400> type<00:26:04.640> this<00:26:04.720> real 00:26:04.950 --> 00:26:04.960 align:start position:0% yeah all right so i gotta type this real 00:26:04.960 --> 00:26:11.190 align:start position:0% yeah all right so i gotta type this real slow 00:26:11.190 --> 00:26:11.200 align:start position:0% 00:26:11.200 --> 00:26:12.310 align:start position:0% um 00:26:12.310 --> 00:26:12.320 align:start position:0% um 00:26:12.320 --> 00:26:14.549 align:start position:0% um okay<00:26:12.640> so<00:26:12.880> set<00:26:13.200> register 00:26:14.549 --> 00:26:14.559 align:start position:0% okay so set register 00:26:14.559 --> 00:26:16.470 align:start position:0% okay so set register fourth<00:26:14.960> b 00:26:16.470 --> 00:26:16.480 align:start position:0% fourth b 00:26:16.480 --> 00:26:20.230 align:start position:0% fourth b 255 00:26:20.230 --> 00:26:20.240 align:start position:0% 00:26:20.240 --> 00:26:22.549 align:start position:0% sleep<00:26:20.720> 100 00:26:22.549 --> 00:26:22.559 align:start position:0% sleep 100 00:26:22.559 --> 00:26:33.269 align:start position:0% sleep 100 set 00:26:33.269 --> 00:26:33.279 align:start position:0% 00:26:33.279 --> 00:26:36.870 align:start position:0% okay<00:26:33.840> and<00:26:33.919> then<00:26:34.080> we<00:26:34.240> have<00:26:34.320> to<00:26:34.480> set<00:26:35.200> pdrp 00:26:36.870 --> 00:26:36.880 align:start position:0% okay and then we have to set pdrp 00:26:36.880 --> 00:26:43.669 align:start position:0% okay and then we have to set pdrp to 00:26:43.669 --> 00:26:43.679 align:start position:0% 00:26:43.679 --> 00:26:45.510 align:start position:0% look 00:26:45.510 --> 00:26:45.520 align:start position:0% look 00:26:45.520 --> 00:26:47.029 align:start position:0% look it's<00:26:45.679> not<00:26:45.919> sleeping<00:26:46.159> 100<00:26:46.480> milliseconds<00:26:46.960> i 00:26:47.029 --> 00:26:47.039 align:start position:0% it's not sleeping 100 milliseconds i 00:26:47.039 --> 00:26:48.149 align:start position:0% it's not sleeping 100 milliseconds i don't<00:26:47.120> know<00:26:47.200> why<00:26:47.360> it's<00:26:47.440> so<00:26:47.600> slow<00:26:47.919> but<00:26:48.080> it 00:26:48.149 --> 00:26:48.159 align:start position:0% don't know why it's so slow but it 00:26:48.159 --> 00:27:05.110 align:start position:0% don't know why it's so slow but it should<00:26:48.320> be<00:26:48.400> blinking<00:26:48.880> list<00:26:49.120> is<00:26:49.200> slow 00:27:05.110 --> 00:27:05.120 align:start position:0% 00:27:05.120 --> 00:27:07.029 align:start position:0% question<00:27:05.440> do<00:27:05.520> you<00:27:05.600> have<00:27:05.679> a<00:27:05.840> trampoline 00:27:07.029 --> 00:27:07.039 align:start position:0% question do you have a trampoline 00:27:07.039 --> 00:27:08.310 align:start position:0% question do you have a trampoline uh<00:27:07.279> no 00:27:08.310 --> 00:27:08.320 align:start position:0% uh no 00:27:08.320 --> 00:27:10.230 align:start position:0% uh no okay<00:27:08.480> so<00:27:08.880> that's<00:27:09.039> gonna<00:27:09.279> overflow<00:27:09.760> eventually 00:27:10.230 --> 00:27:10.240 align:start position:0% okay so that's gonna overflow eventually 00:27:10.240 --> 00:27:14.310 align:start position:0% okay so that's gonna overflow eventually though<00:27:10.400> oh<00:27:10.640> absolutely 00:27:14.310 --> 00:27:14.320 align:start position:0% 00:27:14.320 --> 00:27:33.269 align:start position:0% way<00:27:14.559> after<00:27:14.799> we're<00:27:14.960> done<00:27:15.279> so 00:27:33.269 --> 00:27:33.279 align:start position:0% 00:27:33.279 --> 00:27:35.269 align:start position:0% for<00:27:33.440> symbols<00:27:34.159> um<00:27:34.480> which<00:27:34.720> means<00:27:35.039> if<00:27:35.200> your 00:27:35.269 --> 00:27:35.279 align:start position:0% for symbols um which means if your 00:27:35.279 --> 00:27:36.870 align:start position:0% for symbols um which means if your symbols<00:27:35.600> are<00:27:35.760> four<00:27:36.000> characters<00:27:36.320> or<00:27:36.480> fewer 00:27:36.870 --> 00:27:36.880 align:start position:0% symbols are four characters or fewer 00:27:36.880 --> 00:27:38.230 align:start position:0% symbols are four characters or fewer they're<00:27:37.039> just<00:27:37.200> the<00:27:37.360> characters<00:27:37.760> literally<00:27:38.159> in 00:27:38.230 --> 00:27:38.240 align:start position:0% they're just the characters literally in 00:27:38.240 --> 00:27:40.310 align:start position:0% they're just the characters literally in a<00:27:38.320> row<00:27:38.720> except<00:27:39.039> that<00:27:39.120> we<00:27:39.279> set<00:27:39.440> the<00:27:39.600> high<00:27:39.840> bit<00:27:40.159> on 00:27:40.310 --> 00:27:40.320 align:start position:0% a row except that we set the high bit on 00:27:40.320 --> 00:27:42.310 align:start position:0% a row except that we set the high bit on the<00:27:40.399> fourth<00:27:40.720> character<00:27:41.120> to<00:27:41.279> one<00:27:41.840> so<00:27:42.080> you<00:27:42.159> know 00:27:42.310 --> 00:27:42.320 align:start position:0% the fourth character to one so you know 00:27:42.320 --> 00:27:43.350 align:start position:0% the fourth character to one so you know you're<00:27:42.399> looking<00:27:42.640> at<00:27:42.720> a<00:27:42.799> four<00:27:43.039> character 00:27:43.350 --> 00:27:43.360 align:start position:0% you're looking at a four character 00:27:43.360 --> 00:27:46.149 align:start position:0% you're looking at a four character symbol<00:27:44.159> for<00:27:44.640> up<00:27:44.799> to<00:27:45.039> six<00:27:45.279> characters<00:27:45.840> you<00:27:46.000> can 00:27:46.149 --> 00:27:46.159 align:start position:0% symbol for up to six characters you can 00:27:46.159 --> 00:27:48.950 align:start position:0% symbol for up to six characters you can use<00:27:46.480> any<00:27:46.640> characters<00:27:47.120> a<00:27:47.440> z<00:27:47.919> and<00:27:48.080> any<00:27:48.320> non<00:27:48.640> a<00:27:48.799> to 00:27:48.950 --> 00:27:48.960 align:start position:0% use any characters a z and any non a to 00:27:48.960 --> 00:27:50.630 align:start position:0% use any characters a z and any non a to z<00:27:49.200> character<00:27:49.600> that<00:27:49.840> automatically<00:27:50.320> becomes 00:27:50.630 --> 00:27:50.640 align:start position:0% z character that automatically becomes 00:27:50.640 --> 00:27:55.029 align:start position:0% z character that automatically becomes underscore 00:27:55.029 --> 00:27:55.039 align:start position:0% 00:27:55.039 --> 00:27:57.990 align:start position:0% condensed<00:27:55.600> down<00:27:55.840> to<00:27:56.000> five<00:27:56.320> bits<00:27:56.799> and<00:27:57.120> sort<00:27:57.279> of 00:27:57.990 --> 00:27:58.000 align:start position:0% condensed down to five bits and sort of 00:27:58.000 --> 00:28:00.310 align:start position:0% condensed down to five bits and sort of crammed<00:27:58.480> into<00:27:58.720> the<00:27:58.799> four<00:27:59.120> bytes 00:28:00.310 --> 00:28:00.320 align:start position:0% crammed into the four bytes 00:28:00.320 --> 00:28:03.350 align:start position:0% crammed into the four bytes and<00:28:00.399> then<00:28:01.039> decompressed<00:28:01.840> at<00:28:01.919> the<00:28:02.080> other<00:28:02.320> end 00:28:03.350 --> 00:28:03.360 align:start position:0% and then decompressed at the other end 00:28:03.360 --> 00:28:05.190 align:start position:0% and then decompressed at the other end um<00:28:03.840> so<00:28:04.000> yeah<00:28:04.159> only<00:28:04.399> capital<00:28:04.799> errors<00:28:05.039> because 00:28:05.190 --> 00:28:05.200 align:start position:0% um so yeah only capital errors because 00:28:05.200 --> 00:28:15.029 align:start position:0% um so yeah only capital errors because lowercase<00:28:05.600> letters<00:28:05.919> are<00:28:06.159> too<00:28:06.480> big 00:28:15.029 --> 00:28:15.039 align:start position:0% 00:28:15.039 --> 00:28:16.389 align:start position:0% oh<00:28:15.360> and<00:28:15.520> uh 00:28:16.389 --> 00:28:16.399 align:start position:0% oh and uh 00:28:16.399 --> 00:28:18.549 align:start position:0% oh and uh so<00:28:16.720> uh<00:28:17.440> i<00:28:17.520> guess<00:28:17.760> i<00:28:17.760> had<00:28:17.919> two<00:28:18.080> small<00:28:18.240> things<00:28:18.399> to 00:28:18.549 --> 00:28:18.559 align:start position:0% so uh i guess i had two small things to 00:28:18.559 --> 00:28:20.789 align:start position:0% so uh i guess i had two small things to add<00:28:18.960> one<00:28:19.200> is<00:28:19.360> that<00:28:19.440> the<00:28:19.520> ibm<00:28:19.919> 704<00:28:20.480> which<00:28:20.640> is<00:28:20.720> the 00:28:20.789 --> 00:28:20.799 align:start position:0% add one is that the ibm 704 which is the 00:28:20.799 --> 00:28:22.470 align:start position:0% add one is that the ibm 704 which is the first<00:28:21.039> thing<00:28:21.279> john<00:28:21.440> mccarthy's<00:28:22.240> steve 00:28:22.470 --> 00:28:22.480 align:start position:0% first thing john mccarthy's steve 00:28:22.480 --> 00:28:24.789 align:start position:0% first thing john mccarthy's steve russell<00:28:22.799> did<00:28:22.960> list<00:28:23.120> bond<00:28:23.440> had<00:28:23.600> about<00:28:23.760> 32k<00:28:24.559> of 00:28:24.789 --> 00:28:24.799 align:start position:0% russell did list bond had about 32k of 00:28:24.799 --> 00:28:26.630 align:start position:0% russell did list bond had about 32k of ram<00:28:25.440> so 00:28:26.630 --> 00:28:26.640 align:start position:0% ram so 00:28:26.640 --> 00:28:30.470 align:start position:0% ram so huh 00:28:30.470 --> 00:28:30.480 align:start position:0% 00:28:30.480 --> 00:28:32.149 align:start position:0% the<00:28:30.640> other<00:28:30.799> thing<00:28:30.960> is<00:28:31.279> uh<00:28:31.520> since<00:28:31.760> this<00:28:31.919> is<00:28:32.080> a 00:28:32.149 --> 00:28:32.159 align:start position:0% the other thing is uh since this is a 00:28:32.159 --> 00:28:34.070 align:start position:0% the other thing is uh since this is a very<00:28:32.399> simple<00:28:32.880> list<00:28:33.200> implementation<00:28:33.840> and<00:28:33.919> we 00:28:34.070 --> 00:28:34.080 align:start position:0% very simple list implementation and we 00:28:34.080 --> 00:28:35.909 align:start position:0% very simple list implementation and we are<00:28:34.240> very<00:28:34.399> humble<00:28:34.720> guys<00:28:35.360> uh<00:28:35.520> we<00:28:35.600> called<00:28:35.760> it 00:28:35.909 --> 00:28:35.919 align:start position:0% are very humble guys uh we called it 00:28:35.919 --> 00:28:37.269 align:start position:0% are very humble guys uh we called it uber<00:28:36.159> list 00:28:37.269 --> 00:28:37.279 align:start position:0% uber list 00:28:37.279 --> 00:28:39.190 align:start position:0% uber list and<00:28:37.840> you<00:28:38.000> can<00:28:38.080> google<00:28:38.399> for<00:28:38.559> it<00:28:38.720> it'll<00:28:38.880> pop<00:28:39.039> up 00:28:39.190 --> 00:28:39.200 align:start position:0% and you can google for it it'll pop up 00:28:39.200 --> 00:28:41.350 align:start position:0% and you can google for it it'll pop up it's<00:28:39.360> on<00:28:39.440> the<00:28:39.520> github<00:28:40.320> um<00:28:40.640> next<00:28:40.880> big<00:28:41.039> thing<00:28:41.279> is 00:28:41.350 --> 00:28:41.360 align:start position:0% it's on the github um next big thing is 00:28:41.360 --> 00:28:43.510 align:start position:0% it's on the github um next big thing is gc<00:28:41.840> so<00:28:42.240> you<00:28:42.399> have<00:28:42.559> the<00:28:42.640> chops<00:28:42.960> come<00:28:43.120> on<00:28:43.279> down 00:28:43.510 --> 00:28:43.520 align:start position:0% gc so you have the chops come on down 00:28:43.520 --> 00:28:57.110 align:start position:0% gc so you have the chops come on down let's<00:28:43.840> compute<00:28:44.720> so<00:28:44.880> thanks<00:28:45.120> everybody 00:28:57.110 --> 00:28:57.120 align:start position:0% 00:28:57.120 --> 00:29:00.070 align:start position:0% i'm<00:28:57.200> looking<00:28:57.440> for<00:28:57.600> a<00:28:57.679> chris<00:28:58.000> ranger 00:29:00.070 --> 00:29:00.080 align:start position:0% i'm looking for a chris ranger 00:29:00.080 --> 00:29:01.669 align:start position:0% i'm looking for a chris ranger oh<00:29:00.320> there<00:29:00.480> he<00:29:00.640> is 00:29:01.669 --> 00:29:01.679 align:start position:0% oh there he is 00:29:01.679 --> 00:29:02.389 align:start position:0% oh there he is so 00:29:02.389 --> 00:29:02.399 align:start position:0% so 00:29:02.399 --> 00:29:05.430 align:start position:0% so our<00:29:03.039> uh<00:29:03.360> next<00:29:03.600> lightning<00:29:04.080> talk<00:29:04.320> presenter<00:29:04.960> is 00:29:05.430 --> 00:29:05.440 align:start position:0% our uh next lightning talk presenter is 00:29:05.440 --> 00:29:07.110 align:start position:0% our uh next lightning talk presenter is i<00:29:05.600> think<00:29:05.840> a<00:29:05.919> machine<00:29:06.399> i'm<00:29:06.559> not<00:29:06.720> sure<00:29:06.880> if<00:29:07.039> he 00:29:07.110 --> 00:29:07.120 align:start position:0% i think a machine i'm not sure if he 00:29:07.120 --> 00:29:09.430 align:start position:0% i think a machine i'm not sure if he actually<00:29:07.440> sleeps<00:29:07.760> or<00:29:07.840> not<00:29:08.480> but<00:29:08.640> he<00:29:08.880> has<00:29:08.960> been 00:29:09.430 --> 00:29:09.440 align:start position:0% actually sleeps or not but he has been 00:29:09.440 --> 00:29:12.149 align:start position:0% actually sleeps or not but he has been just<00:29:09.840> uh<00:29:10.559> just<00:29:10.960> sending<00:29:11.279> out<00:29:11.360> libraries<00:29:12.000> for 00:29:12.149 --> 00:29:12.159 align:start position:0% just uh just sending out libraries for 00:29:12.159 --> 00:29:13.269 align:start position:0% just uh just sending out libraries for us<00:29:12.399> all<00:29:12.559> to 00:29:13.269 --> 00:29:13.279 align:start position:0% us all to 00:29:13.279 --> 00:29:16.389 align:start position:0% us all to to<00:29:13.440> use<00:29:13.760> uh<00:29:14.000> noir<00:29:14.559> pino<00:29:15.039> and<00:29:15.200> now<00:29:15.600> uh<00:29:16.080> something 00:29:16.389 --> 00:29:16.399 align:start position:0% to use uh noir pino and now uh something 00:29:16.399 --> 00:29:19.029 align:start position:0% to use uh noir pino and now uh something just<00:29:16.559> recently<00:29:17.120> uh<00:29:17.360> for<00:29:17.600> sql<00:29:18.080> and<00:29:18.240> i<00:29:18.559> will<00:29:18.640> let 00:29:19.029 --> 00:29:19.039 align:start position:0% just recently uh for sql and i will let 00:29:19.039 --> 00:29:30.310 align:start position:0% just recently uh for sql and i will let chris<00:29:19.440> tell<00:29:19.600> you<00:29:19.760> a<00:29:19.840> little<00:29:20.000> bit<00:29:20.080> more<00:29:20.240> about 00:29:30.310 --> 00:29:30.320 align:start position:0% 00:29:30.320 --> 00:29:31.830 align:start position:0% all<00:29:30.480> right<00:29:30.640> yeah<00:29:30.960> so 00:29:31.830 --> 00:29:31.840 align:start position:0% all right yeah so 00:29:31.840 --> 00:29:33.750 align:start position:0% all right yeah so i'm<00:29:32.159> chris<00:29:32.399> granger<00:29:32.720> like<00:29:32.880> you<00:29:33.039> said<00:29:33.279> and<00:29:33.600> i 00:29:33.750 --> 00:29:33.760 align:start position:0% i'm chris granger like you said and i 00:29:33.760 --> 00:29:36.310 align:start position:0% i'm chris granger like you said and i recently<00:29:34.640> uh 00:29:36.310 --> 00:29:36.320 align:start position:0% recently uh 00:29:36.320 --> 00:29:37.430 align:start position:0% recently uh started<00:29:36.559> working<00:29:36.799> on<00:29:36.880> a<00:29:36.960> project<00:29:37.279> that 00:29:37.430 --> 00:29:37.440 align:start position:0% started working on a project that 00:29:37.440 --> 00:29:39.750 align:start position:0% started working on a project that required<00:29:37.840> a<00:29:37.840> lot<00:29:38.000> of<00:29:38.080> sql<00:29:38.480> work<00:29:38.799> and<00:29:39.520> one<00:29:39.679> of 00:29:39.750 --> 00:29:39.760 align:start position:0% required a lot of sql work and one of 00:29:39.760 --> 00:29:41.669 align:start position:0% required a lot of sql work and one of the<00:29:39.919> things<00:29:40.240> that<00:29:40.480> i<00:29:40.559> had<00:29:40.720> done<00:29:40.960> previously 00:29:41.669 --> 00:29:41.679 align:start position:0% the things that i had done previously 00:29:41.679 --> 00:29:43.510 align:start position:0% the things that i had done previously when<00:29:41.919> i<00:29:42.399> had<00:29:42.559> written<00:29:42.880> frameworks<00:29:43.279> actually 00:29:43.510 --> 00:29:43.520 align:start position:0% when i had written frameworks actually 00:29:43.520 --> 00:29:45.669 align:start position:0% when i had written frameworks actually in<00:29:43.600> php<00:29:44.000> was<00:29:44.240> i<00:29:44.320> wrote<00:29:44.559> an<00:29:44.720> orf 00:29:45.669 --> 00:29:45.679 align:start position:0% in php was i wrote an orf 00:29:45.679 --> 00:29:47.510 align:start position:0% in php was i wrote an orf and<00:29:45.840> as<00:29:46.080> i<00:29:46.159> did<00:29:46.320> that<00:29:46.559> i<00:29:46.640> realized<00:29:47.120> hey<00:29:47.440> you 00:29:47.510 --> 00:29:47.520 align:start position:0% and as i did that i realized hey you 00:29:47.520 --> 00:29:50.470 align:start position:0% and as i did that i realized hey you know<00:29:47.840> rms<00:29:48.320> are<00:29:48.399> kind<00:29:48.559> of<00:29:48.640> cool<00:29:48.880> they<00:29:49.039> seem<00:29:49.440> nice 00:29:50.470 --> 00:29:50.480 align:start position:0% know rms are kind of cool they seem nice 00:29:50.480 --> 00:29:52.230 align:start position:0% know rms are kind of cool they seem nice but<00:29:50.640> it<00:29:50.720> turns<00:29:50.960> out<00:29:51.039> that<00:29:51.279> orms<00:29:51.760> in<00:29:51.919> the<00:29:52.000> long 00:29:52.230 --> 00:29:52.240 align:start position:0% but it turns out that orms in the long 00:29:52.240 --> 00:29:53.430 align:start position:0% but it turns out that orms in the long run<00:29:52.399> end<00:29:52.559> up<00:29:52.720> actually<00:29:52.960> being<00:29:53.200> kind<00:29:53.360> of 00:29:53.430 --> 00:29:53.440 align:start position:0% run end up actually being kind of 00:29:53.440 --> 00:29:54.549 align:start position:0% run end up actually being kind of problematic 00:29:54.549 --> 00:29:54.559 align:start position:0% problematic 00:29:54.559 --> 00:29:56.230 align:start position:0% problematic uh<00:29:54.880> you<00:29:55.039> end<00:29:55.200> up<00:29:55.360> fighting<00:29:55.679> against<00:29:56.000> them<00:29:56.159> you 00:29:56.230 --> 00:29:56.240 align:start position:0% uh you end up fighting against them you 00:29:56.240 --> 00:29:57.909 align:start position:0% uh you end up fighting against them you end<00:29:56.399> up<00:29:56.559> needing<00:29:56.799> to<00:29:56.960> do<00:29:57.200> more<00:29:57.440> than<00:29:57.679> their 00:29:57.909 --> 00:29:57.919 align:start position:0% end up needing to do more than their 00:29:57.919 --> 00:29:59.750 align:start position:0% end up needing to do more than their abstraction<00:29:58.399> allows<00:29:58.720> you<00:29:58.880> to<00:29:59.039> do 00:29:59.750 --> 00:29:59.760 align:start position:0% abstraction allows you to do 00:29:59.760 --> 00:30:02.149 align:start position:0% abstraction allows you to do and<00:29:59.919> so<00:30:00.080> what<00:30:00.240> i<00:30:00.320> wanted<00:30:00.640> to<00:30:00.720> do<00:30:01.039> was<00:30:01.440> work<00:30:01.760> with 00:30:02.149 --> 00:30:02.159 align:start position:0% and so what i wanted to do was work with 00:30:02.159 --> 00:30:04.549 align:start position:0% and so what i wanted to do was work with a<00:30:02.320> really<00:30:02.559> nice<00:30:02.880> abstraction<00:30:03.600> for<00:30:03.760> sql<00:30:04.240> on 00:30:04.549 --> 00:30:04.559 align:start position:0% a really nice abstraction for sql on 00:30:04.559 --> 00:30:06.389 align:start position:0% a really nice abstraction for sql on closure 00:30:06.389 --> 00:30:06.399 align:start position:0% closure 00:30:06.399 --> 00:30:08.470 align:start position:0% closure and<00:30:06.640> so<00:30:06.960> this<00:30:07.200> is<00:30:07.279> kind<00:30:07.440> of<00:30:07.600> what<00:30:07.840> cormo<00:30:08.240> looks 00:30:08.470 --> 00:30:08.480 align:start position:0% and so this is kind of what cormo looks 00:30:08.480 --> 00:30:10.470 align:start position:0% and so this is kind of what cormo looks like<00:30:08.640> you<00:30:08.880> define<00:30:09.279> a<00:30:09.360> database<00:30:10.000> can<00:30:10.240> everyone 00:30:10.470 --> 00:30:10.480 align:start position:0% like you define a database can everyone 00:30:10.480 --> 00:30:13.110 align:start position:0% like you define a database can everyone see<00:30:10.640> that<00:30:10.799> out<00:30:10.880> of<00:30:10.960> curiosity 00:30:13.110 --> 00:30:13.120 align:start position:0% see that out of curiosity 00:30:13.120 --> 00:30:15.430 align:start position:0% see that out of curiosity uh<00:30:13.360> you<00:30:13.520> define<00:30:13.919> a<00:30:14.000> database<00:30:14.720> you<00:30:14.799> know<00:30:14.960> i<00:30:15.120> i 00:30:15.430 --> 00:30:15.440 align:start position:0% uh you define a database you know i i 00:30:15.440 --> 00:30:18.070 align:start position:0% uh you define a database you know i i give<00:30:15.679> a<00:30:15.840> set<00:30:16.000> of<00:30:16.240> really<00:30:16.480> simple<00:30:16.880> helpers<00:30:17.760> uh 00:30:18.070 --> 00:30:18.080 align:start position:0% give a set of really simple helpers uh 00:30:18.080 --> 00:30:20.950 align:start position:0% give a set of really simple helpers uh to<00:30:18.880> create<00:30:19.200> sort<00:30:19.360> of<00:30:19.440> these<00:30:19.760> maps<00:30:20.240> that<00:30:20.640> uh 00:30:20.950 --> 00:30:20.960 align:start position:0% to create sort of these maps that uh 00:30:20.960 --> 00:30:22.630 align:start position:0% to create sort of these maps that uh represent<00:30:21.440> your<00:30:21.600> database<00:30:22.000> connections 00:30:22.630 --> 00:30:22.640 align:start position:0% represent your database connections 00:30:22.640 --> 00:30:23.669 align:start position:0% represent your database connections right 00:30:23.669 --> 00:30:23.679 align:start position:0% right 00:30:23.679 --> 00:30:25.510 align:start position:0% right and<00:30:23.840> under<00:30:24.080> the<00:30:24.159> covers<00:30:24.559> here<00:30:25.039> i<00:30:25.200> wanted<00:30:25.440> to 00:30:25.510 --> 00:30:25.520 align:start position:0% and under the covers here i wanted to 00:30:25.520 --> 00:30:26.710 align:start position:0% and under the covers here i wanted to make<00:30:25.679> sure<00:30:25.840> that<00:30:26.000> you<00:30:26.080> don't<00:30:26.320> have<00:30:26.399> to<00:30:26.480> think 00:30:26.710 --> 00:30:26.720 align:start position:0% make sure that you don't have to think 00:30:26.720 --> 00:30:28.630 align:start position:0% make sure that you don't have to think about<00:30:26.960> some<00:30:27.120> things<00:30:27.600> uh 00:30:28.630 --> 00:30:28.640 align:start position:0% about some things uh 00:30:28.640 --> 00:30:29.830 align:start position:0% about some things uh that<00:30:28.799> you<00:30:28.960> would<00:30:29.120> otherwise<00:30:29.520> have<00:30:29.600> to<00:30:29.679> think 00:30:29.830 --> 00:30:29.840 align:start position:0% that you would otherwise have to think 00:30:29.840 --> 00:30:31.669 align:start position:0% that you would otherwise have to think about<00:30:30.000> if<00:30:30.159> you<00:30:30.240> were<00:30:30.399> using<00:30:30.640> just<00:30:30.880> straight<00:30:31.360> uh 00:30:31.669 --> 00:30:31.679 align:start position:0% about if you were using just straight uh 00:30:31.679 --> 00:30:33.990 align:start position:0% about if you were using just straight uh java<00:30:32.000> jdbc<00:30:32.640> things<00:30:32.799> like<00:30:32.960> connection<00:30:33.360> porn<00:30:33.840> as 00:30:33.990 --> 00:30:34.000 align:start position:0% java jdbc things like connection porn as 00:30:34.000 --> 00:30:35.750 align:start position:0% java jdbc things like connection porn as an<00:30:34.159> example<00:30:34.640> right<00:30:35.120> you<00:30:35.279> know<00:30:35.440> one<00:30:35.600> of<00:30:35.679> the 00:30:35.750 --> 00:30:35.760 align:start position:0% an example right you know one of the 00:30:35.760 --> 00:30:37.029 align:start position:0% an example right you know one of the things<00:30:36.000> that<00:30:36.159> i<00:30:36.320> didn't<00:30:36.480> realize<00:30:36.799> when<00:30:36.880> i 00:30:37.029 --> 00:30:37.039 align:start position:0% things that i didn't realize when i 00:30:37.039 --> 00:30:39.430 align:start position:0% things that i didn't realize when i started<00:30:37.360> using<00:30:37.840> jdbc<00:30:38.720> was<00:30:38.880> that<00:30:39.039> i<00:30:39.200> was<00:30:39.360> going 00:30:39.430 --> 00:30:39.440 align:start position:0% started using jdbc was that i was going 00:30:39.440 --> 00:30:40.630 align:start position:0% started using jdbc was that i was going to<00:30:39.520> have<00:30:39.679> to<00:30:39.760> manage<00:30:40.080> that<00:30:40.240> connection 00:30:40.630 --> 00:30:40.640 align:start position:0% to have to manage that connection 00:30:40.640 --> 00:30:42.950 align:start position:0% to have to manage that connection explicitly<00:30:41.440> so<00:30:41.600> this<00:30:41.840> uses<00:30:42.159> a<00:30:42.240> library<00:30:42.640> called 00:30:42.950 --> 00:30:42.960 align:start position:0% explicitly so this uses a library called 00:30:42.960 --> 00:30:45.029 align:start position:0% explicitly so this uses a library called c3po<00:30:44.000> that<00:30:44.159> does<00:30:44.399> all<00:30:44.480> that<00:30:44.640> connection 00:30:45.029 --> 00:30:45.039 align:start position:0% c3po that does all that connection 00:30:45.039 --> 00:30:47.029 align:start position:0% c3po that does all that connection pooling<00:30:45.440> for<00:30:45.600> you<00:30:45.840> so<00:30:46.080> you<00:30:46.640> just<00:30:46.880> start 00:30:47.029 --> 00:30:47.039 align:start position:0% pooling for you so you just start 00:30:47.039 --> 00:30:48.870 align:start position:0% pooling for you so you just start writing<00:30:47.360> queries 00:30:48.870 --> 00:30:48.880 align:start position:0% writing queries 00:30:48.880 --> 00:30:51.350 align:start position:0% writing queries and<00:30:48.960> what<00:30:49.120> you<00:30:49.279> can<00:30:49.440> see<00:30:49.600> here 00:30:51.350 --> 00:30:51.360 align:start position:0% and what you can see here 00:30:51.360 --> 00:30:53.190 align:start position:0% and what you can see here is<00:30:51.520> i<00:30:51.600> have<00:30:51.840> a<00:30:51.919> thing<00:30:52.159> called<00:30:52.480> deaf<00:30:52.720> entity 00:30:53.190 --> 00:30:53.200 align:start position:0% is i have a thing called deaf entity 00:30:53.200 --> 00:30:55.350 align:start position:0% is i have a thing called deaf entity this<00:30:53.360> is<00:30:53.440> something<00:30:53.760> just<00:30:54.000> maps<00:30:54.640> directly<00:30:55.120> to 00:30:55.350 --> 00:30:55.360 align:start position:0% this is something just maps directly to 00:30:55.360 --> 00:30:57.350 align:start position:0% this is something just maps directly to a<00:30:55.440> table<00:30:55.760> more<00:30:56.000> or<00:30:56.159> less<00:30:56.399> but<00:30:56.480> allows<00:30:56.799> you<00:30:56.960> to 00:30:57.350 --> 00:30:57.360 align:start position:0% a table more or less but allows you to 00:30:57.360 --> 00:30:59.750 align:start position:0% a table more or less but allows you to specify<00:30:58.399> you<00:30:58.559> know<00:30:58.799> some<00:30:59.039> properties<00:30:59.600> of 00:30:59.750 --> 00:30:59.760 align:start position:0% specify you know some properties of 00:30:59.760 --> 00:31:01.269 align:start position:0% specify you know some properties of these<00:31:00.000> things<00:31:00.159> so<00:31:00.399> you<00:31:00.480> can<00:31:00.640> do<00:31:00.880> interesting 00:31:01.269 --> 00:31:01.279 align:start position:0% these things so you can do interesting 00:31:01.279 --> 00:31:03.909 align:start position:0% these things so you can do interesting things<00:31:01.519> with<00:31:01.679> them<00:31:01.760> later<00:31:02.480> so<00:31:02.720> for<00:31:02.880> example<00:31:03.760> i 00:31:03.909 --> 00:31:03.919 align:start position:0% things with them later so for example i 00:31:03.919 --> 00:31:06.070 align:start position:0% things with them later so for example i have<00:31:04.080> a<00:31:04.159> query<00:31:04.480> here<00:31:04.880> where<00:31:05.039> i<00:31:05.120> want<00:31:05.279> to<00:31:05.360> select 00:31:06.070 --> 00:31:06.080 align:start position:0% have a query here where i want to select 00:31:06.080 --> 00:31:08.070 align:start position:0% have a query here where i want to select you<00:31:06.240> know<00:31:06.480> all<00:31:06.640> my<00:31:06.880> users<00:31:07.600> with<00:31:07.840> their 00:31:08.070 --> 00:31:08.080 align:start position:0% you know all my users with their 00:31:08.080 --> 00:31:09.909 align:start position:0% you know all my users with their addresses<00:31:08.960> since<00:31:09.200> i've<00:31:09.360> defined<00:31:09.840> a 00:31:09.909 --> 00:31:09.919 align:start position:0% addresses since i've defined a 00:31:09.919 --> 00:31:11.909 align:start position:0% addresses since i've defined a relationship<00:31:10.640> between<00:31:11.039> my<00:31:11.200> entities<00:31:11.679> i<00:31:11.760> can 00:31:11.909 --> 00:31:11.919 align:start position:0% relationship between my entities i can 00:31:11.919 --> 00:31:14.710 align:start position:0% relationship between my entities i can do<00:31:12.159> that<00:31:12.399> and<00:31:12.960> on<00:31:13.120> the<00:31:13.279> back<00:31:13.519> end<00:31:14.159> korma<00:31:14.559> is 00:31:14.710 --> 00:31:14.720 align:start position:0% do that and on the back end korma is 00:31:14.720 --> 00:31:16.470 align:start position:0% do that and on the back end korma is simply<00:31:15.360> you<00:31:15.440> know<00:31:15.600> writing<00:31:15.919> out<00:31:16.080> joints<00:31:16.399> it's 00:31:16.470 --> 00:31:16.480 align:start position:0% simply you know writing out joints it's 00:31:16.480 --> 00:31:18.230 align:start position:0% simply you know writing out joints it's not<00:31:16.640> doing<00:31:16.799> anything<00:31:17.200> particularly<00:31:17.760> special 00:31:18.230 --> 00:31:18.240 align:start position:0% not doing anything particularly special 00:31:18.240 --> 00:31:19.029 align:start position:0% not doing anything particularly special here 00:31:19.029 --> 00:31:19.039 align:start position:0% here 00:31:19.039 --> 00:31:20.310 align:start position:0% here for<00:31:19.200> the<00:31:19.200> most<00:31:19.440> part<00:31:19.679> it's<00:31:19.760> just<00:31:19.919> writing<00:31:20.240> out 00:31:20.310 --> 00:31:20.320 align:start position:0% for the most part it's just writing out 00:31:20.320 --> 00:31:22.149 align:start position:0% for the most part it's just writing out the<00:31:20.480> join<00:31:20.720> so<00:31:20.880> that<00:31:20.960> you<00:31:21.120> don't<00:31:21.279> have<00:31:21.440> to<00:31:22.000> so 00:31:22.149 --> 00:31:22.159 align:start position:0% the join so that you don't have to so 00:31:22.159 --> 00:31:25.269 align:start position:0% the join so that you don't have to so this<00:31:22.320> isn't<00:31:22.559> an<00:31:22.720> orm<00:31:23.279> in<00:31:23.440> the<00:31:24.080> large<00:31:24.559> hibernate 00:31:25.269 --> 00:31:25.279 align:start position:0% this isn't an orm in the large hibernate 00:31:25.279 --> 00:31:26.789 align:start position:0% this isn't an orm in the large hibernate sense<00:31:25.519> where<00:31:25.679> it's<00:31:25.840> doing<00:31:26.080> all<00:31:26.159> this<00:31:26.399> crazy 00:31:26.789 --> 00:31:26.799 align:start position:0% sense where it's doing all this crazy 00:31:26.799 --> 00:31:28.789 align:start position:0% sense where it's doing all this crazy magic<00:31:27.200> on<00:31:27.360> the<00:31:27.440> back<00:31:27.679> end<00:31:28.080> for<00:31:28.240> the<00:31:28.320> most<00:31:28.559> part 00:31:28.789 --> 00:31:28.799 align:start position:0% magic on the back end for the most part 00:31:28.799 --> 00:31:30.789 align:start position:0% magic on the back end for the most part it's<00:31:28.880> just<00:31:29.039> helping<00:31:29.360> you<00:31:29.519> write<00:31:30.080> queries<00:31:30.559> more 00:31:30.789 --> 00:31:30.799 align:start position:0% it's just helping you write queries more 00:31:30.799 --> 00:31:32.549 align:start position:0% it's just helping you write queries more efficiently<00:31:31.440> right<00:31:31.679> at<00:31:31.760> the<00:31:31.919> end<00:31:32.159> he's<00:31:32.399> just 00:31:32.549 --> 00:31:32.559 align:start position:0% efficiently right at the end he's just 00:31:32.559 --> 00:31:35.430 align:start position:0% efficiently right at the end he's just writing<00:31:32.880> very<00:31:33.120> simple<00:31:33.440> sql 00:31:35.430 --> 00:31:35.440 align:start position:0% writing very simple sql 00:31:35.440 --> 00:31:38.230 align:start position:0% writing very simple sql um<00:31:35.840> i<00:31:36.080> think<00:31:36.320> the<00:31:36.480> advantage<00:31:37.519> or<00:31:37.760> rather<00:31:38.000> the 00:31:38.230 --> 00:31:38.240 align:start position:0% um i think the advantage or rather the 00:31:38.240 --> 00:31:39.990 align:start position:0% um i think the advantage or rather the power<00:31:38.559> of<00:31:38.720> karma<00:31:39.200> though 00:31:39.990 --> 00:31:40.000 align:start position:0% power of karma though 00:31:40.000 --> 00:31:42.470 align:start position:0% power of karma though is<00:31:40.159> not<00:31:40.320> so<00:31:40.480> much<00:31:40.720> in<00:31:41.200> just<00:31:41.600> the<00:31:41.760> abstraction 00:31:42.470 --> 00:31:42.480 align:start position:0% is not so much in just the abstraction 00:31:42.480 --> 00:31:43.590 align:start position:0% is not so much in just the abstraction it's<00:31:42.640> nice<00:31:42.880> to<00:31:42.880> be<00:31:43.039> able<00:31:43.120> to<00:31:43.200> write<00:31:43.360> it<00:31:43.519> you 00:31:43.590 --> 00:31:43.600 align:start position:0% it's nice to be able to write it you 00:31:43.600 --> 00:31:46.230 align:start position:0% it's nice to be able to write it you know<00:31:43.760> succinctly<00:31:44.399> and<00:31:44.640> cleanly<00:31:45.120> and<00:31:45.279> clearly 00:31:46.230 --> 00:31:46.240 align:start position:0% know succinctly and cleanly and clearly 00:31:46.240 --> 00:31:47.909 align:start position:0% know succinctly and cleanly and clearly but<00:31:46.399> i<00:31:46.480> think<00:31:46.640> the<00:31:46.799> real<00:31:47.120> power<00:31:47.360> of<00:31:47.519> korma 00:31:47.909 --> 00:31:47.919 align:start position:0% but i think the real power of korma 00:31:47.919 --> 00:31:50.149 align:start position:0% but i think the real power of korma comes<00:31:48.159> in<00:31:48.240> the<00:31:48.320> fact<00:31:48.559> that<00:31:49.120> uh<00:31:49.440> much<00:31:49.679> like<00:31:49.840> play 00:31:50.149 --> 00:31:50.159 align:start position:0% comes in the fact that uh much like play 00:31:50.159 --> 00:31:54.149 align:start position:0% comes in the fact that uh much like play casco<00:31:50.559> log<00:31:51.279> it<00:31:51.519> is<00:31:52.000> entirely<00:31:52.720> composable 00:31:54.149 --> 00:31:54.159 align:start position:0% casco log it is entirely composable 00:31:54.159 --> 00:31:56.310 align:start position:0% casco log it is entirely composable right<00:31:54.640> you<00:31:54.880> can<00:31:55.440> in<00:31:55.519> this<00:31:55.760> case<00:31:56.000> instead<00:31:56.240> of 00:31:56.310 --> 00:31:56.320 align:start position:0% right you can in this case instead of 00:31:56.320 --> 00:31:59.350 align:start position:0% right you can in this case instead of using<00:31:56.720> the<00:31:56.880> select<00:31:57.279> macro<00:31:57.679> you<00:31:57.919> select<00:31:58.240> star 00:31:59.350 --> 00:31:59.360 align:start position:0% using the select macro you select star 00:31:59.360 --> 00:32:01.590 align:start position:0% using the select macro you select star and<00:31:59.440> then<00:31:59.679> start<00:32:00.000> building<00:32:00.399> up<00:32:00.559> a<00:32:00.640> query<00:32:01.519> and 00:32:01.590 --> 00:32:01.600 align:start position:0% and then start building up a query and 00:32:01.600 --> 00:32:03.350 align:start position:0% and then start building up a query and then<00:32:01.760> you<00:32:02.080> add<00:32:02.399> more<00:32:02.559> to<00:32:02.720> the<00:32:02.799> query<00:32:03.120> and<00:32:03.200> then 00:32:03.350 --> 00:32:03.360 align:start position:0% then you add more to the query and then 00:32:03.360 --> 00:32:04.789 align:start position:0% then you add more to the query and then you<00:32:03.440> add<00:32:03.679> more<00:32:03.840> to<00:32:04.000> the<00:32:04.080> query<00:32:04.399> all<00:32:04.640> you're 00:32:04.789 --> 00:32:04.799 align:start position:0% you add more to the query all you're 00:32:04.799 --> 00:32:06.549 align:start position:0% you add more to the query all you're doing<00:32:05.120> here<00:32:05.360> is<00:32:05.519> actually<00:32:05.760> manipulating<00:32:06.480> a 00:32:06.549 --> 00:32:06.559 align:start position:0% doing here is actually manipulating a 00:32:06.559 --> 00:32:07.509 align:start position:0% doing here is actually manipulating a map 00:32:07.509 --> 00:32:07.519 align:start position:0% map 00:32:07.519 --> 00:32:09.590 align:start position:0% map and<00:32:07.679> what<00:32:07.840> corma<00:32:08.320> really<00:32:08.640> is<00:32:08.960> if<00:32:09.120> you<00:32:09.200> want<00:32:09.360> to 00:32:09.590 --> 00:32:09.600 align:start position:0% and what corma really is if you want to 00:32:09.600 --> 00:32:11.190 align:start position:0% and what corma really is if you want to break<00:32:09.760> it<00:32:09.840> down<00:32:10.080> into<00:32:10.320> its<00:32:10.559> constituent 00:32:11.190 --> 00:32:11.200 align:start position:0% break it down into its constituent 00:32:11.200 --> 00:32:13.430 align:start position:0% break it down into its constituent pieces<00:32:11.840> is<00:32:12.000> actually<00:32:12.320> a<00:32:12.399> sql<00:32:12.799> generation 00:32:13.430 --> 00:32:13.440 align:start position:0% pieces is actually a sql generation 00:32:13.440 --> 00:32:16.149 align:start position:0% pieces is actually a sql generation engine<00:32:14.240> right<00:32:14.880> and<00:32:14.960> then<00:32:15.279> a<00:32:15.440> nice<00:32:15.760> way<00:32:16.000> of 00:32:16.149 --> 00:32:16.159 align:start position:0% engine right and then a nice way of 00:32:16.159 --> 00:32:17.990 align:start position:0% engine right and then a nice way of writing<00:32:16.480> out<00:32:16.640> the<00:32:16.720> maps<00:32:17.039> that<00:32:17.120> go<00:32:17.279> to<00:32:17.440> it 00:32:17.990 --> 00:32:18.000 align:start position:0% writing out the maps that go to it 00:32:18.000 --> 00:32:19.509 align:start position:0% writing out the maps that go to it that's<00:32:18.240> all<00:32:18.399> it<00:32:18.559> is 00:32:19.509 --> 00:32:19.519 align:start position:0% that's all it is 00:32:19.519 --> 00:32:21.909 align:start position:0% that's all it is now<00:32:20.000> when<00:32:20.159> you<00:32:20.320> start<00:32:20.720> thinking<00:32:21.120> of<00:32:21.279> libraries 00:32:21.909 --> 00:32:21.919 align:start position:0% now when you start thinking of libraries 00:32:21.919 --> 00:32:24.230 align:start position:0% now when you start thinking of libraries in<00:32:22.080> that<00:32:22.320> way<00:32:22.720> where<00:32:23.039> you<00:32:23.360> always<00:32:23.760> have<00:32:24.000> sort 00:32:24.230 --> 00:32:24.240 align:start position:0% in that way where you always have sort 00:32:24.240 --> 00:32:26.630 align:start position:0% in that way where you always have sort of<00:32:24.320> this<00:32:24.559> one<00:32:24.799> thing<00:32:25.440> that<00:32:25.600> can<00:32:25.760> take 00:32:26.630 --> 00:32:26.640 align:start position:0% of this one thing that can take 00:32:26.640 --> 00:32:29.269 align:start position:0% of this one thing that can take basically<00:32:27.039> any<00:32:27.360> arbitrary<00:32:28.080> um<00:32:28.720> map<00:32:28.960> that<00:32:29.039> you 00:32:29.269 --> 00:32:29.279 align:start position:0% basically any arbitrary um map that you 00:32:29.279 --> 00:32:31.750 align:start position:0% basically any arbitrary um map that you create<00:32:29.840> for<00:32:30.080> it<00:32:30.320> and<00:32:30.399> then<00:32:30.640> generate<00:32:31.120> sql<00:32:31.600> out 00:32:31.750 --> 00:32:31.760 align:start position:0% create for it and then generate sql out 00:32:31.760 --> 00:32:33.909 align:start position:0% create for it and then generate sql out of<00:32:31.919> it<00:32:32.399> um<00:32:32.640> this<00:32:32.799> allows<00:32:33.120> you<00:32:33.200> to<00:32:33.519> literally 00:32:33.909 --> 00:32:33.919 align:start position:0% of it um this allows you to literally 00:32:33.919 --> 00:32:36.149 align:start position:0% of it um this allows you to literally completely<00:32:34.399> replace<00:32:34.720> my<00:32:34.880> syntax<00:32:35.840> that's 00:32:36.149 --> 00:32:36.159 align:start position:0% completely replace my syntax that's 00:32:36.159 --> 00:32:38.950 align:start position:0% completely replace my syntax that's syntax<00:32:37.120> my<00:32:37.600> the<00:32:37.840> the<00:32:38.159> the 00:32:38.950 --> 00:32:38.960 align:start position:0% syntax my the the the 00:32:38.960 --> 00:32:41.909 align:start position:0% syntax my the the the api<00:32:39.760> i<00:32:40.000> provided<00:32:40.480> here<00:32:40.799> you<00:32:40.960> could<00:32:41.360> you<00:32:41.519> know 00:32:41.909 --> 00:32:41.919 align:start position:0% api i provided here you could you know 00:32:41.919 --> 00:32:43.509 align:start position:0% api i provided here you could you know you<00:32:42.080> don't<00:32:42.240> like<00:32:42.399> select<00:32:42.880> write<00:32:43.120> some<00:32:43.360> other 00:32:43.509 --> 00:32:43.519 align:start position:0% you don't like select write some other 00:32:43.519 --> 00:32:45.509 align:start position:0% you don't like select write some other thing<00:32:43.760> that<00:32:43.919> creates<00:32:44.480> you<00:32:44.559> know<00:32:44.880> a<00:32:45.039> map<00:32:45.360> that 00:32:45.509 --> 00:32:45.519 align:start position:0% thing that creates you know a map that 00:32:45.519 --> 00:32:47.509 align:start position:0% thing that creates you know a map that represents<00:32:46.080> a<00:32:46.159> select<00:32:46.480> query<00:32:47.039> you<00:32:47.200> wouldn't 00:32:47.509 --> 00:32:47.519 align:start position:0% represents a select query you wouldn't 00:32:47.519 --> 00:32:49.029 align:start position:0% represents a select query you wouldn't actually<00:32:47.760> have<00:32:47.919> to<00:32:48.080> rewrite<00:32:48.399> all<00:32:48.480> that<00:32:48.640> sql 00:32:49.029 --> 00:32:49.039 align:start position:0% actually have to rewrite all that sql 00:32:49.039 --> 00:32:51.990 align:start position:0% actually have to rewrite all that sql generation<00:32:49.519> stuff<00:32:50.080> so<00:32:50.320> this<00:32:50.480> enables<00:32:50.960> you<00:32:51.279> to 00:32:51.990 --> 00:32:52.000 align:start position:0% generation stuff so this enables you to 00:32:52.000 --> 00:32:53.750 align:start position:0% generation stuff so this enables you to actually<00:32:52.480> add<00:32:52.720> to<00:32:52.880> korma<00:32:53.279> in<00:32:53.360> interesting 00:32:53.750 --> 00:32:53.760 align:start position:0% actually add to korma in interesting 00:32:53.760 --> 00:32:57.029 align:start position:0% actually add to korma in interesting ways<00:32:54.559> so<00:32:55.120> i<00:32:55.360> provide<00:32:55.760> a<00:32:56.000> relatively<00:32:56.640> simple 00:32:57.029 --> 00:32:57.039 align:start position:0% ways so i provide a relatively simple 00:32:57.039 --> 00:32:59.190 align:start position:0% ways so i provide a relatively simple set<00:32:57.519> of<00:32:58.000> um 00:32:59.190 --> 00:32:59.200 align:start position:0% set of um 00:32:59.200 --> 00:33:01.269 align:start position:0% set of um of<00:32:59.440> relationships<00:33:00.320> but<00:33:00.480> you<00:33:00.640> can<00:33:00.799> imagine 00:33:01.269 --> 00:33:01.279 align:start position:0% of relationships but you can imagine 00:33:01.279 --> 00:33:04.149 align:start position:0% of relationships but you can imagine actually<00:33:01.679> creating<00:33:02.320> a<00:33:02.880> property<00:33:03.279> or<00:33:03.440> a<00:33:03.679> method 00:33:04.149 --> 00:33:04.159 align:start position:0% actually creating a property or a method 00:33:04.159 --> 00:33:05.830 align:start position:0% actually creating a property or a method rather<00:33:04.480> or<00:33:04.640> function 00:33:05.830 --> 00:33:05.840 align:start position:0% rather or function 00:33:05.840 --> 00:33:08.870 align:start position:0% rather or function for<00:33:06.080> deaf<00:33:06.399> entity<00:33:07.279> that<00:33:07.760> creates 00:33:08.870 --> 00:33:08.880 align:start position:0% for deaf entity that creates 00:33:08.880 --> 00:33:10.950 align:start position:0% for deaf entity that creates all<00:33:09.039> the<00:33:09.200> relationships<00:33:09.760> for<00:33:10.080> just<00:33:10.320> a<00:33:10.559> chain 00:33:10.950 --> 00:33:10.960 align:start position:0% all the relationships for just a chain 00:33:10.960 --> 00:33:13.509 align:start position:0% all the relationships for just a chain let's<00:33:11.120> say<00:33:11.279> you're<00:33:11.519> constantly<00:33:12.320> um<00:33:13.039> using<00:33:13.279> one 00:33:13.509 --> 00:33:13.519 align:start position:0% let's say you're constantly um using one 00:33:13.519 --> 00:33:15.430 align:start position:0% let's say you're constantly um using one entity<00:33:13.840> and<00:33:13.919> you<00:33:14.000> want<00:33:14.399> you<00:33:14.480> know<00:33:14.880> something 00:33:15.430 --> 00:33:15.440 align:start position:0% entity and you want you know something 00:33:15.440 --> 00:33:17.430 align:start position:0% entity and you want you know something that's<00:33:15.600> like<00:33:15.760> eight<00:33:16.000> levels<00:33:16.399> nested<00:33:16.880> right 00:33:17.430 --> 00:33:17.440 align:start position:0% that's like eight levels nested right 00:33:17.440 --> 00:33:19.029 align:start position:0% that's like eight levels nested right you<00:33:17.600> don't<00:33:17.679> want<00:33:17.840> to<00:33:17.919> constantly<00:33:18.559> write<00:33:18.799> those 00:33:19.029 --> 00:33:19.039 align:start position:0% you don't want to constantly write those 00:33:19.039 --> 00:33:20.789 align:start position:0% you don't want to constantly write those joins<00:33:19.440> out<00:33:19.760> as<00:33:19.919> a<00:33:19.919> matter<00:33:20.080> of<00:33:20.159> fact<00:33:20.399> you<00:33:20.480> may<00:33:20.640> do 00:33:20.789 --> 00:33:20.799 align:start position:0% joins out as a matter of fact you may do 00:33:20.799 --> 00:33:21.830 align:start position:0% joins out as a matter of fact you may do that<00:33:20.880> all<00:33:21.039> the<00:33:21.120> time<00:33:21.279> so<00:33:21.440> you<00:33:21.519> don't<00:33:21.600> want<00:33:21.760> to 00:33:21.830 --> 00:33:21.840 align:start position:0% that all the time so you don't want to 00:33:21.840 --> 00:33:23.350 align:start position:0% that all the time so you don't want to write<00:33:22.240> you<00:33:22.320> know<00:33:22.480> like<00:33:22.640> i've<00:33:22.799> done<00:33:23.039> here<00:33:23.200> where 00:33:23.350 --> 00:33:23.360 align:start position:0% write you know like i've done here where 00:33:23.360 --> 00:33:25.110 align:start position:0% write you know like i've done here where you're<00:33:23.519> writing<00:33:24.000> essentially<00:33:24.559> functions<00:33:24.960> to 00:33:25.110 --> 00:33:25.120 align:start position:0% you're writing essentially functions to 00:33:25.120 --> 00:33:27.110 align:start position:0% you're writing essentially functions to add<00:33:25.279> that<00:33:25.519> each<00:33:25.760> time<00:33:26.240> you<00:33:26.399> could<00:33:26.640> actually 00:33:27.110 --> 00:33:27.120 align:start position:0% add that each time you could actually 00:33:27.120 --> 00:33:29.350 align:start position:0% add that each time you could actually add<00:33:27.360> it<00:33:27.600> to<00:33:27.760> korma<00:33:28.159> itself<00:33:28.559> you<00:33:28.720> could<00:33:29.039> go<00:33:29.200> up 00:33:29.350 --> 00:33:29.360 align:start position:0% add it to korma itself you could go up 00:33:29.360 --> 00:33:31.909 align:start position:0% add it to korma itself you could go up here<00:33:29.919> right<00:33:30.399> and<00:33:30.559> in<00:33:30.640> your<00:33:30.799> deaf<00:33:31.039> entity<00:33:31.440> say 00:33:31.909 --> 00:33:31.919 align:start position:0% here right and in your deaf entity say 00:33:31.919 --> 00:33:34.470 align:start position:0% here right and in your deaf entity say you<00:33:32.080> know<00:33:32.399> chained<00:33:32.960> address<00:33:33.600> to 00:33:34.470 --> 00:33:34.480 align:start position:0% you know chained address to 00:33:34.480 --> 00:33:36.630 align:start position:0% you know chained address to state<00:33:35.120> to<00:33:35.440> whatever<00:33:35.840> else<00:33:36.080> you<00:33:36.159> may<00:33:36.320> have<00:33:36.480> to 00:33:36.630 --> 00:33:36.640 align:start position:0% state to whatever else you may have to 00:33:36.640 --> 00:33:39.269 align:start position:0% state to whatever else you may have to zip<00:33:36.960> code<00:33:37.279> to<00:33:37.600> blah<00:33:37.600> blah<00:33:38.000> blah 00:33:39.269 --> 00:33:39.279 align:start position:0% zip code to blah blah blah 00:33:39.279 --> 00:33:41.269 align:start position:0% zip code to blah blah blah and<00:33:39.440> then<00:33:39.840> cormac<00:33:40.240> can<00:33:40.399> then 00:33:41.269 --> 00:33:41.279 align:start position:0% and then cormac can then 00:33:41.279 --> 00:33:42.070 align:start position:0% and then cormac can then uh 00:33:42.070 --> 00:33:42.080 align:start position:0% uh 00:33:42.080 --> 00:33:43.990 align:start position:0% uh you<00:33:42.240> know<00:33:42.399> you<00:33:42.480> could<00:33:42.640> then<00:33:43.360> use<00:33:43.600> that<00:33:43.840> in 00:33:43.990 --> 00:33:44.000 align:start position:0% you know you could then use that in 00:33:44.000 --> 00:33:45.830 align:start position:0% you know you could then use that in widths<00:33:44.480> and<00:33:45.039> enable<00:33:45.440> yourself<00:33:45.760> to 00:33:45.830 --> 00:33:45.840 align:start position:0% widths and enable yourself to 00:33:45.840 --> 00:33:47.350 align:start position:0% widths and enable yourself to essentially<00:33:46.320> write<00:33:46.559> out<00:33:46.720> all<00:33:46.799> those<00:33:47.039> joints 00:33:47.350 --> 00:33:47.360 align:start position:0% essentially write out all those joints 00:33:47.360 --> 00:33:50.310 align:start position:0% essentially write out all those joints for<00:33:47.600> you<00:33:47.840> so<00:33:48.000> it's<00:33:48.399> a<00:33:48.480> really<00:33:48.880> extensible<00:33:49.519> way 00:33:50.310 --> 00:33:50.320 align:start position:0% for you so it's a really extensible way 00:33:50.320 --> 00:33:53.669 align:start position:0% for you so it's a really extensible way of<00:33:50.799> dealing<00:33:51.279> with<00:33:51.519> sql<00:33:52.000> in<00:33:52.159> general 00:33:53.669 --> 00:33:53.679 align:start position:0% of dealing with sql in general 00:33:53.679 --> 00:33:55.110 align:start position:0% of dealing with sql in general um 00:33:55.110 --> 00:33:55.120 align:start position:0% um 00:33:55.120 --> 00:33:56.630 align:start position:0% um another<00:33:55.440> thing<00:33:55.679> that<00:33:55.760> i<00:33:55.840> wanted<00:33:56.080> to<00:33:56.159> make<00:33:56.320> sure 00:33:56.630 --> 00:33:56.640 align:start position:0% another thing that i wanted to make sure 00:33:56.640 --> 00:33:59.590 align:start position:0% another thing that i wanted to make sure was<00:33:57.039> that<00:33:57.519> um<00:33:58.159> it<00:33:58.240> was<00:33:58.720> flexible<00:33:59.279> in<00:33:59.360> a<00:33:59.440> way 00:33:59.590 --> 00:33:59.600 align:start position:0% was that um it was flexible in a way 00:33:59.600 --> 00:34:01.909 align:start position:0% was that um it was flexible in a way that<00:33:59.760> wasn't<00:34:00.080> annoying<00:34:00.720> right<00:34:00.960> so<00:34:01.440> hibernate 00:34:01.909 --> 00:34:01.919 align:start position:0% that wasn't annoying right so hibernate 00:34:01.919 --> 00:34:03.590 align:start position:0% that wasn't annoying right so hibernate has<00:34:02.000> gotten<00:34:02.240> a<00:34:02.480> lot<00:34:02.720> lot<00:34:02.960> better<00:34:03.279> over<00:34:03.440> the 00:34:03.590 --> 00:34:03.600 align:start position:0% has gotten a lot lot better over the 00:34:03.600 --> 00:34:05.350 align:start position:0% has gotten a lot lot better over the years<00:34:03.919> but<00:34:04.159> i<00:34:04.320> remember<00:34:04.720> the<00:34:04.880> first<00:34:05.120> few 00:34:05.350 --> 00:34:05.360 align:start position:0% years but i remember the first few 00:34:05.360 --> 00:34:07.990 align:start position:0% years but i remember the first few versions<00:34:05.679> it<00:34:05.760> was<00:34:06.000> like<00:34:06.640> pages<00:34:07.120> and<00:34:07.360> pages<00:34:07.840> and 00:34:07.990 --> 00:34:08.000 align:start position:0% versions it was like pages and pages and 00:34:08.000 --> 00:34:09.750 align:start position:0% versions it was like pages and pages and pages<00:34:08.320> of<00:34:08.480> xml<00:34:08.960> files<00:34:09.280> where<00:34:09.440> you<00:34:09.520> had<00:34:09.679> to 00:34:09.750 --> 00:34:09.760 align:start position:0% pages of xml files where you had to 00:34:09.760 --> 00:34:11.829 align:start position:0% pages of xml files where you had to configure<00:34:10.480> everything 00:34:11.829 --> 00:34:11.839 align:start position:0% configure everything 00:34:11.839 --> 00:34:14.230 align:start position:0% configure everything while<00:34:12.560> you<00:34:12.720> do<00:34:12.879> need<00:34:13.040> to<00:34:13.119> do<00:34:13.280> that<00:34:13.679> at<00:34:14.000> some 00:34:14.230 --> 00:34:14.240 align:start position:0% while you do need to do that at some 00:34:14.240 --> 00:34:15.990 align:start position:0% while you do need to do that at some times<00:34:14.639> right<00:34:14.800> you<00:34:14.960> shouldn't<00:34:15.280> always<00:34:15.679> have<00:34:15.839> to 00:34:15.990 --> 00:34:16.000 align:start position:0% times right you shouldn't always have to 00:34:16.000 --> 00:34:18.230 align:start position:0% times right you shouldn't always have to do<00:34:16.159> that<00:34:16.639> there's<00:34:16.960> value<00:34:17.359> in<00:34:17.440> the<00:34:17.599> things<00:34:17.919> that 00:34:18.230 --> 00:34:18.240 align:start position:0% do that there's value in the things that 00:34:18.240 --> 00:34:20.069 align:start position:0% do that there's value in the things that that<00:34:18.480> ruby<00:34:18.800> on<00:34:18.960> rails<00:34:19.280> presented<00:34:19.679> which<00:34:19.760> is 00:34:20.069 --> 00:34:20.079 align:start position:0% that ruby on rails presented which is 00:34:20.079 --> 00:34:22.230 align:start position:0% that ruby on rails presented which is you<00:34:20.159> know<00:34:20.320> this<00:34:20.480> notion<00:34:20.800> of<00:34:21.280> convention<00:34:21.839> over 00:34:22.230 --> 00:34:22.240 align:start position:0% you know this notion of convention over 00:34:22.240 --> 00:34:24.069 align:start position:0% you know this notion of convention over over<00:34:22.560> customization 00:34:24.069 --> 00:34:24.079 align:start position:0% over customization 00:34:24.079 --> 00:34:25.829 align:start position:0% over customization but<00:34:24.240> you<00:34:24.399> need<00:34:24.560> to<00:34:24.639> be<00:34:24.800> able<00:34:24.960> to<00:34:25.359> sort<00:34:25.520> of<00:34:25.679> get 00:34:25.829 --> 00:34:25.839 align:start position:0% but you need to be able to sort of get 00:34:25.839 --> 00:34:27.909 align:start position:0% but you need to be able to sort of get out<00:34:26.000> of<00:34:26.079> it<00:34:26.240> if<00:34:26.320> you<00:34:26.399> need<00:34:26.560> to<00:34:26.879> so<00:34:27.040> for<00:34:27.280> example 00:34:27.909 --> 00:34:27.919 align:start position:0% out of it if you need to so for example 00:34:27.919 --> 00:34:30.790 align:start position:0% out of it if you need to so for example i<00:34:28.079> used<00:34:28.240> to<00:34:28.320> work<00:34:28.560> on<00:34:29.040> a<00:34:29.520> massive<00:34:30.079> project<00:34:30.560> that 00:34:30.790 --> 00:34:30.800 align:start position:0% i used to work on a massive project that 00:34:30.800 --> 00:34:33.190 align:start position:0% i used to work on a massive project that had<00:34:31.040> a<00:34:31.280> wine<00:34:31.520> database<00:34:32.480> for 00:34:33.190 --> 00:34:33.200 align:start position:0% had a wine database for 00:34:33.200 --> 00:34:35.190 align:start position:0% had a wine database for literally<00:34:33.679> millions<00:34:34.000> upon<00:34:34.240> millions<00:34:34.639> of 00:34:35.190 --> 00:34:35.200 align:start position:0% literally millions upon millions of 00:34:35.200 --> 00:34:36.790 align:start position:0% literally millions upon millions of wines<00:34:35.520> and<00:34:35.679> everything<00:34:36.159> you<00:34:36.240> could<00:34:36.399> ever<00:34:36.639> want 00:34:36.790 --> 00:34:36.800 align:start position:0% wines and everything you could ever want 00:34:36.800 --> 00:34:38.629 align:start position:0% wines and everything you could ever want to<00:34:36.879> know<00:34:37.040> about<00:34:37.280> them<00:34:37.760> but<00:34:37.919> that<00:34:38.079> database<00:34:38.480> was 00:34:38.629 --> 00:34:38.639 align:start position:0% to know about them but that database was 00:34:38.639 --> 00:34:40.470 align:start position:0% to know about them but that database was built<00:34:38.879> up<00:34:39.040> over<00:34:39.280> many<00:34:39.599> years<00:34:40.000> by<00:34:40.159> many 00:34:40.470 --> 00:34:40.480 align:start position:0% built up over many years by many 00:34:40.480 --> 00:34:42.710 align:start position:0% built up over many years by many different<00:34:40.720> companies<00:34:41.280> and<00:34:41.359> so<00:34:41.520> we<00:34:41.679> had<00:34:42.159> a<00:34:42.320> wine 00:34:42.710 --> 00:34:42.720 align:start position:0% different companies and so we had a wine 00:34:42.720 --> 00:34:45.349 align:start position:0% different companies and so we had a wine table<00:34:43.359> an<00:34:43.520> underscore<00:34:44.159> wine<00:34:44.480> table<00:34:45.200> an 00:34:45.349 --> 00:34:45.359 align:start position:0% table an underscore wine table an 00:34:45.359 --> 00:34:47.909 align:start position:0% table an underscore wine table an underscore<00:34:46.000> underscore<00:34:46.560> one<00:34:46.960> table<00:34:47.359> right<00:34:47.520> we 00:34:47.909 --> 00:34:47.919 align:start position:0% underscore underscore one table right we 00:34:47.919 --> 00:34:49.510 align:start position:0% underscore underscore one table right we had<00:34:48.159> all<00:34:48.320> these<00:34:48.560> weird 00:34:49.510 --> 00:34:49.520 align:start position:0% had all these weird 00:34:49.520 --> 00:34:51.990 align:start position:0% had all these weird sort<00:34:49.760> of<00:34:50.000> names<00:34:50.560> and<00:34:50.960> none<00:34:51.119> of<00:34:51.200> the<00:34:51.440> keys<00:34:51.760> would 00:34:51.990 --> 00:34:52.000 align:start position:0% sort of names and none of the keys would 00:34:52.000 --> 00:34:53.990 align:start position:0% sort of names and none of the keys would match<00:34:52.720> and<00:34:52.879> so<00:34:53.119> another<00:34:53.359> thing<00:34:53.520> that<00:34:53.679> i<00:34:53.760> wanted 00:34:53.990 --> 00:34:54.000 align:start position:0% match and so another thing that i wanted 00:34:54.000 --> 00:34:55.990 align:start position:0% match and so another thing that i wanted to<00:34:54.079> make<00:34:54.320> sure<00:34:54.800> uh<00:34:55.040> when<00:34:55.280> i<00:34:55.359> wrote<00:34:55.599> corman<00:34:55.919> that 00:34:55.990 --> 00:34:56.000 align:start position:0% to make sure uh when i wrote corman that 00:34:56.000 --> 00:34:58.390 align:start position:0% to make sure uh when i wrote corman that was<00:34:56.240> built<00:34:56.480> for<00:34:56.639> real<00:34:56.800> world<00:34:57.119> stuff 00:34:58.390 --> 00:34:58.400 align:start position:0% was built for real world stuff 00:34:58.400 --> 00:35:00.230 align:start position:0% was built for real world stuff right<00:34:58.720> i<00:34:58.800> don't<00:34:59.040> make<00:34:59.280> assumptions<00:34:59.920> and<00:35:00.079> when 00:35:00.230 --> 00:35:00.240 align:start position:0% right i don't make assumptions and when 00:35:00.240 --> 00:35:01.990 align:start position:0% right i don't make assumptions and when i<00:35:00.400> do<00:35:00.560> make<00:35:00.800> assumptions<00:35:01.200> you<00:35:01.359> can<00:35:01.440> override 00:35:01.990 --> 00:35:02.000 align:start position:0% i do make assumptions you can override 00:35:02.000 --> 00:35:03.589 align:start position:0% i do make assumptions you can override them<00:35:02.640> and<00:35:02.720> that's<00:35:02.960> that's<00:35:03.200> i<00:35:03.280> think<00:35:03.440> an 00:35:03.589 --> 00:35:03.599 align:start position:0% them and that's that's i think an 00:35:03.599 --> 00:35:06.390 align:start position:0% them and that's that's i think an important<00:35:04.000> part<00:35:04.640> of<00:35:04.880> being<00:35:05.359> really<00:35:05.599> useful<00:35:06.240> in 00:35:06.390 --> 00:35:06.400 align:start position:0% important part of being really useful in 00:35:06.400 --> 00:35:08.310 align:start position:0% important part of being really useful in this<00:35:06.640> space 00:35:08.310 --> 00:35:08.320 align:start position:0% this space 00:35:08.320 --> 00:35:09.589 align:start position:0% this space um 00:35:09.589 --> 00:35:09.599 align:start position:0% um 00:35:09.599 --> 00:35:11.109 align:start position:0% um so<00:35:09.760> i<00:35:09.839> mean<00:35:10.160> there's<00:35:10.320> lots<00:35:10.560> of<00:35:10.640> interesting 00:35:11.109 --> 00:35:11.119 align:start position:0% so i mean there's lots of interesting 00:35:11.119 --> 00:35:13.190 align:start position:0% so i mean there's lots of interesting things<00:35:11.359> here<00:35:11.760> it's<00:35:12.079> actually<00:35:12.480> really<00:35:12.720> small 00:35:13.190 --> 00:35:13.200 align:start position:0% things here it's actually really small 00:35:13.200 --> 00:35:14.630 align:start position:0% things here it's actually really small so<00:35:13.359> if<00:35:13.440> you<00:35:13.520> want<00:35:13.680> to<00:35:13.760> see<00:35:13.920> how<00:35:14.079> you<00:35:14.240> might 00:35:14.630 --> 00:35:14.640 align:start position:0% so if you want to see how you might 00:35:14.640 --> 00:35:16.550 align:start position:0% so if you want to see how you might write<00:35:14.800> a<00:35:14.960> sequel<00:35:15.280> generating<00:35:15.680> engine 00:35:16.550 --> 00:35:16.560 align:start position:0% write a sequel generating engine 00:35:16.560 --> 00:35:18.630 align:start position:0% write a sequel generating engine that<00:35:16.800> runs<00:35:17.040> off<00:35:17.200> of<00:35:17.280> maps<00:35:17.760> take<00:35:17.920> a<00:35:18.000> look<00:35:18.240> at<00:35:18.400> the 00:35:18.630 --> 00:35:18.640 align:start position:0% that runs off of maps take a look at the 00:35:18.640 --> 00:35:20.310 align:start position:0% that runs off of maps take a look at the take<00:35:18.880> a<00:35:18.960> look<00:35:19.040> at<00:35:19.119> the<00:35:19.280> source 00:35:20.310 --> 00:35:20.320 align:start position:0% take a look at the source 00:35:20.320 --> 00:35:21.349 align:start position:0% take a look at the source um 00:35:21.349 --> 00:35:21.359 align:start position:0% um 00:35:21.359 --> 00:35:22.870 align:start position:0% um yeah<00:35:21.599> i<00:35:21.680> don't<00:35:21.839> want<00:35:22.000> to<00:35:22.240> take<00:35:22.480> them<00:35:22.560> any<00:35:22.720> more 00:35:22.870 --> 00:35:22.880 align:start position:0% yeah i don't want to take them any more 00:35:22.880 --> 00:35:24.550 align:start position:0% yeah i don't want to take them any more time<00:35:23.200> so<00:35:23.280> if<00:35:23.440> you<00:35:23.520> have<00:35:23.599> any<00:35:23.839> questions<00:35:24.320> if<00:35:24.480> i 00:35:24.550 --> 00:35:24.560 align:start position:0% time so if you have any questions if i 00:35:24.560 --> 00:35:25.829 align:start position:0% time so if you have any questions if i have<00:35:24.720> time 00:35:25.829 --> 00:35:25.839 align:start position:0% have time 00:35:25.839 --> 00:35:28.390 align:start position:0% have time feel<00:35:26.079> free 00:35:28.390 --> 00:35:28.400 align:start position:0% 00:35:28.400 --> 00:35:31.510 align:start position:0% yeah<00:35:28.720> you<00:35:29.040> do<00:35:29.200> your<00:35:30.000> your<00:35:30.160> joins<00:35:30.560> all<00:35:30.720> in<00:35:30.880> one 00:35:31.510 --> 00:35:31.520 align:start position:0% yeah you do your your joins all in one 00:35:31.520 --> 00:35:33.109 align:start position:0% yeah you do your your joins all in one swipe<00:35:32.079> or<00:35:32.320> if<00:35:32.480> you 00:35:33.109 --> 00:35:33.119 align:start position:0% swipe or if you 00:35:33.119 --> 00:35:34.069 align:start position:0% swipe or if you uh 00:35:34.069 --> 00:35:34.079 align:start position:0% uh 00:35:34.079 --> 00:35:35.750 align:start position:0% uh like<00:35:34.480> you<00:35:34.560> know<00:35:34.800> hibernate<00:35:35.280> you<00:35:35.359> could<00:35:35.440> do<00:35:35.599> a 00:35:35.750 --> 00:35:35.760 align:start position:0% like you know hibernate you could do a 00:35:35.760 --> 00:35:38.069 align:start position:0% like you know hibernate you could do a cascading<00:35:36.400> so<00:35:36.880> like<00:35:37.119> the<00:35:37.200> first<00:35:37.440> layer<00:35:38.000> and 00:35:38.069 --> 00:35:38.079 align:start position:0% cascading so like the first layer and 00:35:38.079 --> 00:35:40.069 align:start position:0% cascading so like the first layer and then<00:35:38.320> do<00:35:38.800> the<00:35:38.960> second 00:35:40.069 --> 00:35:40.079 align:start position:0% then do the second 00:35:40.079 --> 00:35:42.870 align:start position:0% then do the second level<00:35:40.320> of<00:35:41.200> indirection<00:35:41.760> laserly<00:35:42.480> or<00:35:42.640> you<00:35:42.720> know 00:35:42.870 --> 00:35:42.880 align:start position:0% level of indirection laserly or you know 00:35:42.880 --> 00:35:45.750 align:start position:0% level of indirection laserly or you know on<00:35:42.960> demand<00:35:43.359> do<00:35:43.359> you<00:35:44.320> do<00:35:44.480> that<00:35:44.720> or<00:35:44.960> no<00:35:45.359> so<00:35:45.520> by 00:35:45.750 --> 00:35:45.760 align:start position:0% on demand do you do that or no so by 00:35:45.760 --> 00:35:48.310 align:start position:0% on demand do you do that or no so by default<00:35:46.560> my<00:35:46.720> has<00:35:47.040> many<00:35:47.359> relationship<00:35:48.079> right 00:35:48.310 --> 00:35:48.320 align:start position:0% default my has many relationship right 00:35:48.320 --> 00:35:49.990 align:start position:0% default my has many relationship right because<00:35:48.640> that<00:35:48.800> can<00:35:48.960> be<00:35:49.040> a<00:35:49.200> multiplicative<00:35:49.839> set 00:35:49.990 --> 00:35:50.000 align:start position:0% because that can be a multiplicative set 00:35:50.000 --> 00:35:51.829 align:start position:0% because that can be a multiplicative set as<00:35:50.160> you<00:35:50.240> go<00:35:50.400> down<00:35:50.720> you<00:35:50.800> don't<00:35:51.040> want<00:35:51.200> to<00:35:51.440> do<00:35:51.599> that 00:35:51.829 --> 00:35:51.839 align:start position:0% as you go down you don't want to do that 00:35:51.839 --> 00:35:53.190 align:start position:0% as you go down you don't want to do that all<00:35:52.000> really<00:35:52.240> in<00:35:52.320> one<00:35:52.480> query<00:35:52.720> most<00:35:52.880> of<00:35:52.960> the<00:35:53.040> time 00:35:53.190 --> 00:35:53.200 align:start position:0% all really in one query most of the time 00:35:53.200 --> 00:35:54.550 align:start position:0% all really in one query most of the time and<00:35:53.280> you<00:35:53.359> want<00:35:53.520> to<00:35:53.599> do<00:35:53.680> it<00:35:53.839> lazily<00:35:54.320> like<00:35:54.480> you 00:35:54.550 --> 00:35:54.560 align:start position:0% and you want to do it lazily like you 00:35:54.560 --> 00:35:56.710 align:start position:0% and you want to do it lazily like you said<00:35:55.119> my<00:35:55.280> has<00:35:55.520> many<00:35:55.760> does<00:35:56.000> exactly<00:35:56.320> that<00:35:56.640> and 00:35:56.710 --> 00:35:56.720 align:start position:0% said my has many does exactly that and 00:35:56.720 --> 00:35:58.950 align:start position:0% said my has many does exactly that and you<00:35:56.880> could<00:35:57.040> write<00:35:57.680> very<00:35:57.920> very<00:35:58.160> similar<00:35:58.640> things 00:35:58.950 --> 00:35:58.960 align:start position:0% you could write very very similar things 00:35:58.960 --> 00:36:01.670 align:start position:0% you could write very very similar things that<00:35:59.440> do<00:35:59.599> that<00:35:59.839> there's<00:36:00.079> a<00:36:00.640> notion<00:36:00.960> of<00:36:01.119> a<00:36:01.280> post 00:36:01.670 --> 00:36:01.680 align:start position:0% that do that there's a notion of a post 00:36:01.680 --> 00:36:03.349 align:start position:0% that do that there's a notion of a post query<00:36:02.000> essentially<00:36:02.480> where<00:36:02.640> you<00:36:02.720> say<00:36:02.880> oh<00:36:03.200> do 00:36:03.349 --> 00:36:03.359 align:start position:0% query essentially where you say oh do 00:36:03.359 --> 00:36:04.870 align:start position:0% query essentially where you say oh do this<00:36:03.599> with<00:36:03.760> the<00:36:03.920> id<00:36:04.160> you<00:36:04.240> know<00:36:04.400> the<00:36:04.480> primary 00:36:04.870 --> 00:36:04.880 align:start position:0% this with the id you know the primary 00:36:04.880 --> 00:36:06.870 align:start position:0% this with the id you know the primary key<00:36:05.040> of<00:36:05.119> this<00:36:05.280> other<00:36:05.520> thing<00:36:05.839> and<00:36:06.400> it<00:36:06.480> makes<00:36:06.720> it 00:36:06.870 --> 00:36:06.880 align:start position:0% key of this other thing and it makes it 00:36:06.880 --> 00:36:08.950 align:start position:0% key of this other thing and it makes it easy<00:36:07.200> actually<00:36:07.520> to<00:36:07.920> add<00:36:08.400> if<00:36:08.560> you<00:36:08.640> don't<00:36:08.800> like 00:36:08.950 --> 00:36:08.960 align:start position:0% easy actually to add if you don't like 00:36:08.960 --> 00:36:11.349 align:start position:0% easy actually to add if you don't like what<00:36:09.119> i've<00:36:09.280> done<00:36:09.680> even<00:36:10.000> add<00:36:10.320> more<00:36:10.880> complex 00:36:11.349 --> 00:36:11.359 align:start position:0% what i've done even add more complex 00:36:11.359 --> 00:36:16.470 align:start position:0% what i've done even add more complex ways<00:36:11.599> of<00:36:11.680> doing<00:36:12.000> it<00:36:12.320> yeah 00:36:16.470 --> 00:36:16.480 align:start position:0% 00:36:16.480 --> 00:36:19.030 align:start position:0% about<00:36:16.720> how<00:36:16.880> much<00:36:17.200> code<00:36:17.520> is<00:36:17.680> dedicated<00:36:18.320> to<00:36:18.800> the 00:36:19.030 --> 00:36:19.040 align:start position:0% about how much code is dedicated to the 00:36:19.040 --> 00:36:22.550 align:start position:0% about how much code is dedicated to the differences<00:36:19.440> between<00:36:20.320> syntax<00:36:20.960> and<00:36:21.200> different 00:36:22.550 --> 00:36:22.560 align:start position:0% differences between syntax and different 00:36:22.560 --> 00:36:24.150 align:start position:0% differences between syntax and different databases 00:36:24.150 --> 00:36:24.160 align:start position:0% databases 00:36:24.160 --> 00:36:26.950 align:start position:0% databases well<00:36:24.720> not<00:36:25.040> a<00:36:25.119> ton<00:36:25.359> right<00:36:25.599> now<00:36:26.079> um<00:36:26.320> and<00:36:26.480> i'm<00:36:26.720> i'm 00:36:26.950 --> 00:36:26.960 align:start position:0% well not a ton right now um and i'm i'm 00:36:26.960 --> 00:36:29.030 align:start position:0% well not a ton right now um and i'm i'm sure<00:36:27.119> there<00:36:27.280> are<00:36:27.520> bugs<00:36:27.760> in<00:36:27.839> this<00:36:28.160> because<00:36:28.640> i 00:36:29.030 --> 00:36:29.040 align:start position:0% sure there are bugs in this because i 00:36:29.040 --> 00:36:30.870 align:start position:0% sure there are bugs in this because i only<00:36:29.280> use<00:36:29.520> a<00:36:29.599> few<00:36:29.760> databases<00:36:30.320> i<00:36:30.480> have<00:36:30.640> not 00:36:30.870 --> 00:36:30.880 align:start position:0% only use a few databases i have not 00:36:30.880 --> 00:36:32.870 align:start position:0% only use a few databases i have not tested<00:36:31.200> against<00:36:31.520> a<00:36:31.599> lot<00:36:31.760> of<00:36:31.839> them<00:36:32.160> so<00:36:32.640> once 00:36:32.870 --> 00:36:32.880 align:start position:0% tested against a lot of them so once 00:36:32.880 --> 00:36:34.550 align:start position:0% tested against a lot of them so once people<00:36:33.200> start<00:36:33.359> using<00:36:33.599> it<00:36:33.760> i'll<00:36:33.920> start<00:36:34.160> sussing 00:36:34.550 --> 00:36:34.560 align:start position:0% people start using it i'll start sussing 00:36:34.560 --> 00:36:37.510 align:start position:0% people start using it i'll start sussing that<00:36:34.720> out<00:36:35.200> now<00:36:35.520> to<00:36:35.680> be<00:36:36.079> to<00:36:36.240> be<00:36:36.640> um<00:36:37.040> clear<00:36:37.280> though 00:36:37.510 --> 00:36:37.520 align:start position:0% that out now to be to be um clear though 00:36:37.520 --> 00:36:40.230 align:start position:0% that out now to be to be um clear though it<00:36:37.680> does<00:36:37.839> use<00:36:38.160> jdbc<00:36:38.800> on<00:36:38.960> the<00:36:39.040> backend<00:36:39.520> right<00:36:39.760> so 00:36:40.230 --> 00:36:40.240 align:start position:0% it does use jdbc on the backend right so 00:36:40.240 --> 00:36:42.630 align:start position:0% it does use jdbc on the backend right so some<00:36:40.400> of<00:36:40.560> that<00:36:40.720> is<00:36:40.880> handled<00:36:41.520> purely<00:36:41.839> by<00:36:42.000> jdbc 00:36:42.630 --> 00:36:42.640 align:start position:0% some of that is handled purely by jdbc 00:36:42.640 --> 00:36:44.310 align:start position:0% some of that is handled purely by jdbc somebody<00:36:42.960> who's<00:36:43.680> done<00:36:43.839> this<00:36:44.000> for<00:36:44.160> a<00:36:44.160> lot 00:36:44.310 --> 00:36:44.320 align:start position:0% somebody who's done this for a lot 00:36:44.320 --> 00:36:45.829 align:start position:0% somebody who's done this for a lot longer<00:36:44.560> than<00:36:44.720> i<00:36:44.880> have<00:36:45.040> and<00:36:45.119> i<00:36:45.200> don't<00:36:45.359> have<00:36:45.520> to 00:36:45.829 --> 00:36:45.839 align:start position:0% longer than i have and i don't have to 00:36:45.839 --> 00:36:48.950 align:start position:0% longer than i have and i don't have to you<00:36:45.920> know<00:36:46.000> i<00:36:46.160> know<00:36:46.320> if<00:36:46.640> they're<00:36:47.040> correct 00:36:48.950 --> 00:36:48.960 align:start position:0% you know i know if they're correct 00:36:48.960 --> 00:36:51.190 align:start position:0% you know i know if they're correct uh<00:36:49.359> just<00:36:49.520> like<00:36:49.760> parameterized<00:36:50.480> queries<00:36:50.960> as<00:36:51.040> an 00:36:51.190 --> 00:36:51.200 align:start position:0% uh just like parameterized queries as an 00:36:51.200 --> 00:36:53.109 align:start position:0% uh just like parameterized queries as an example<00:36:51.599> right<00:36:51.760> all<00:36:51.920> that<00:36:52.160> is<00:36:52.320> to<00:36:52.400> make<00:36:52.560> sure 00:36:53.109 --> 00:36:53.119 align:start position:0% example right all that is to make sure 00:36:53.119 --> 00:36:54.870 align:start position:0% example right all that is to make sure it's<00:36:53.359> safe<00:36:53.680> i<00:36:53.760> don't<00:36:53.920> want<00:36:54.000> to<00:36:54.079> touch<00:36:54.400> that<00:36:54.720> as 00:36:54.870 --> 00:36:54.880 align:start position:0% it's safe i don't want to touch that as 00:36:54.880 --> 00:36:57.430 align:start position:0% it's safe i don't want to touch that as much<00:36:55.040> as<00:36:55.200> i<00:36:55.280> can 00:36:57.430 --> 00:36:57.440 align:start position:0% much as i can 00:36:57.440 --> 00:36:58.950 align:start position:0% much as i can i<00:36:57.599> should<00:36:57.839> also<00:36:58.079> mention<00:36:58.400> you<00:36:58.560> can<00:36:58.720> actually 00:36:58.950 --> 00:36:58.960 align:start position:0% i should also mention you can actually 00:36:58.960 --> 00:37:00.790 align:start position:0% i should also mention you can actually like<00:36:59.280> get<00:36:59.440> the<00:36:59.599> sequel<00:37:00.079> out<00:37:00.160> of<00:37:00.240> this<00:37:00.480> and<00:37:00.640> do 00:37:00.790 --> 00:37:00.800 align:start position:0% like get the sequel out of this and do 00:37:00.800 --> 00:37:02.150 align:start position:0% like get the sequel out of this and do stuff<00:37:01.040> with<00:37:01.200> it<00:37:01.359> if<00:37:01.440> you<00:37:01.520> want<00:37:01.760> so<00:37:01.920> you<00:37:02.000> don't 00:37:02.150 --> 00:37:02.160 align:start position:0% stuff with it if you want so you don't 00:37:02.160 --> 00:37:03.589 align:start position:0% stuff with it if you want so you don't actually<00:37:02.400> have<00:37:02.560> to<00:37:02.640> use<00:37:02.800> it<00:37:02.880> to<00:37:03.040> execute<00:37:03.520> you 00:37:03.589 --> 00:37:03.599 align:start position:0% actually have to use it to execute you 00:37:03.599 --> 00:37:05.190 align:start position:0% actually have to use it to execute you don't<00:37:03.760> even<00:37:03.920> like<00:37:04.160> that<00:37:04.400> you<00:37:04.560> could<00:37:04.880> if<00:37:05.040> you're 00:37:05.190 --> 00:37:05.200 align:start position:0% don't even like that you could if you're 00:37:05.200 --> 00:37:06.390 align:start position:0% don't even like that you could if you're working<00:37:05.440> in<00:37:05.520> another<00:37:05.839> project<00:37:06.160> you<00:37:06.240> could 00:37:06.390 --> 00:37:06.400 align:start position:0% working in another project you could 00:37:06.400 --> 00:37:08.470 align:start position:0% working in another project you could actually<00:37:06.800> use<00:37:07.359> closure<00:37:07.760> to<00:37:07.920> generate<00:37:08.320> your 00:37:08.470 --> 00:37:08.480 align:start position:0% actually use closure to generate your 00:37:08.480 --> 00:37:09.990 align:start position:0% actually use closure to generate your queries<00:37:08.960> for<00:37:09.040> that<00:37:09.280> other<00:37:09.440> project<00:37:09.760> in<00:37:09.839> a 00:37:09.990 --> 00:37:10.000 align:start position:0% queries for that other project in a 00:37:10.000 --> 00:37:14.790 align:start position:0% queries for that other project in a different<00:37:10.320> language<00:37:10.800> and<00:37:10.880> then<00:37:11.280> you<00:37:11.359> know 00:37:14.790 --> 00:37:14.800 align:start position:0% 00:37:14.800 --> 00:37:18.550 align:start position:0% any<00:37:15.040> other<00:37:15.200> questions 00:37:18.550 --> 00:37:18.560 align:start position:0% 00:37:18.560 --> 00:37:21.720 align:start position:0% all<00:37:18.720> right