WEBVTT Kind: captions Language: en 00:00:05.390 --> 00:00:09.959 align:start position:0% let<00:00:06.290> me<00:00:06.439> know<00:00:06.560> what<00:00:06.850> your<00:00:07.850> prom<00:00:08.590> sound<00:00:09.590> good 00:00:09.959 --> 00:00:09.969 align:start position:0% let me know what your prom sound good 00:00:09.969 --> 00:00:15.060 align:start position:0% let me know what your prom sound good okay<00:00:12.190> sounds<00:00:13.190> good<00:00:13.309> alright<00:00:13.850> however<00:00:14.809> only 00:00:15.060 --> 00:00:15.070 align:start position:0% okay sounds good alright however only 00:00:15.070 --> 00:00:19.269 align:start position:0% okay sounds good alright however only okay<00:00:16.960> welcome<00:00:17.960> everybody<00:00:18.199> I'm<00:00:18.650> Alexa<00:00:19.070> crab 00:00:19.269 --> 00:00:19.279 align:start position:0% okay welcome everybody I'm Alexa crab 00:00:19.279 --> 00:00:21.400 align:start position:0% okay welcome everybody I'm Alexa crab Roe<00:00:19.460> the<00:00:19.609> organizer<00:00:20.090> of<00:00:20.420> reactive<00:00:20.990> systems 00:00:21.400 --> 00:00:21.410 align:start position:0% Roe the organizer of reactive systems 00:00:21.410 --> 00:00:23.579 align:start position:0% Roe the organizer of reactive systems meet<00:00:21.710> up<00:00:21.859> it's<00:00:22.070> a<00:00:22.189> new<00:00:22.220> meetup<00:00:22.609> about 00:00:23.579 --> 00:00:23.589 align:start position:0% meet up it's a new meetup about 00:00:23.589 --> 00:00:26.380 align:start position:0% meet up it's a new meetup about everything<00:00:24.759> explained<00:00:25.759> in<00:00:26.029> reactive 00:00:26.380 --> 00:00:26.390 align:start position:0% everything explained in reactive 00:00:26.390 --> 00:00:29.470 align:start position:0% everything explained in reactive manifest<00:00:27.429> everything<00:00:28.429> about<00:00:28.640> observable<00:00:29.269> so 00:00:29.470 --> 00:00:29.480 align:start position:0% manifest everything about observable so 00:00:29.480 --> 00:00:31.120 align:start position:0% manifest everything about observable so there's<00:00:29.689> a<00:00:29.749> whole<00:00:29.900> like<00:00:30.169> a<00:00:30.199> system<00:00:30.679> of 00:00:31.120 --> 00:00:31.130 align:start position:0% there's a whole like a system of 00:00:31.130 --> 00:00:32.920 align:start position:0% there's a whole like a system of reactive<00:00:31.550> systems<00:00:31.849> and<00:00:32.090> today<00:00:32.599> we<00:00:32.750> have<00:00:32.900> a 00:00:32.920 --> 00:00:32.930 align:start position:0% reactive systems and today we have a 00:00:32.930 --> 00:00:35.020 align:start position:0% reactive systems and today we have a vast<00:00:33.140> bankers<00:00:33.560> and<00:00:33.680> soon<00:00:33.860> he's<00:00:34.760> a<00:00:34.790> software 00:00:35.020 --> 00:00:35.030 align:start position:0% vast bankers and soon he's a software 00:00:35.030 --> 00:00:37.240 align:start position:0% vast bankers and soon he's a software engineer<00:00:35.420> at<00:00:35.510> Netflix<00:00:35.900> a<00:00:36.290> kiss<00:00:36.620> greater<00:00:36.829> forex 00:00:37.240 --> 00:00:37.250 align:start position:0% engineer at Netflix a kiss greater forex 00:00:37.250 --> 00:00:41.740 align:start position:0% engineer at Netflix a kiss greater forex Java<00:00:37.550> and<00:00:37.910> a<00:00:37.969> lot<00:00:38.629> of<00:00:39.789> applications<00:00:40.789> working 00:00:41.740 --> 00:00:41.750 align:start position:0% Java and a lot of applications working 00:00:41.750 --> 00:00:43.360 align:start position:0% Java and a lot of applications working with<00:00:41.870> this<00:00:42.020> we're<00:00:42.559> happy<00:00:42.829> to<00:00:43.010> have<00:00:43.100> you<00:00:43.160> been 00:00:43.360 --> 00:00:43.370 align:start position:0% with this we're happy to have you been 00:00:43.370 --> 00:00:46.479 align:start position:0% with this we're happy to have you been thank<00:00:43.760> you<00:00:43.850> thank<00:00:44.090> you<00:00:44.269> for<00:00:44.449> having<00:00:44.539> me<00:00:44.739> so<00:00:45.739> so 00:00:46.479 --> 00:00:46.489 align:start position:0% thank you thank you for having me so so 00:00:46.489 --> 00:00:51.549 align:start position:0% thank you thank you for having me so so you<00:00:46.640> are<00:00:46.760> on<00:00:47.030> h<00:00:48.489> systems<00:00:49.899> team<00:00:50.899> at<00:00:51.079> Atlas<00:00:51.379> can 00:00:51.549 --> 00:00:51.559 align:start position:0% you are on h systems team at Atlas can 00:00:51.559 --> 00:00:53.770 align:start position:0% you are on h systems team at Atlas can you<00:00:51.710> tell<00:00:52.219> us<00:00:52.250> a<00:00:52.370> little<00:00:52.429> bit<00:00:52.609> about<00:00:52.879> what<00:00:53.269> the 00:00:53.770 --> 00:00:53.780 align:start position:0% you tell us a little bit about what the 00:00:53.780 --> 00:00:55.770 align:start position:0% you tell us a little bit about what the team<00:00:53.960> is<00:00:54.050> doing<00:00:54.170> how<00:00:54.590> the<00:00:54.649> whole<00:00:55.160> reactive 00:00:55.770 --> 00:00:55.780 align:start position:0% team is doing how the whole reactive 00:00:55.780 --> 00:00:59.410 align:start position:0% team is doing how the whole reactive stack<00:00:56.780> came<00:00:57.170> to<00:00:57.649> be<00:00:57.739> sure<00:00:58.280> so<00:00:59.030> the<00:00:59.179> edge 00:00:59.410 --> 00:00:59.420 align:start position:0% stack came to be sure so the edge 00:00:59.420 --> 00:01:01.540 align:start position:0% stack came to be sure so the edge systems<00:00:59.839> team<00:01:00.050> in<00:01:00.199> netflix<00:01:00.559> is<00:01:00.800> responsible 00:01:01.540 --> 00:01:01.550 align:start position:0% systems team in netflix is responsible 00:01:01.550 --> 00:01:04.810 align:start position:0% systems team in netflix is responsible for<00:01:01.879> its<00:01:02.269> the<00:01:03.019> the<00:01:03.829> layer<00:01:04.040> of<00:01:04.370> server-side 00:01:04.810 --> 00:01:04.820 align:start position:0% for its the the layer of server-side 00:01:04.820 --> 00:01:07.540 align:start position:0% for its the the layer of server-side systems<00:01:05.390> that<00:01:06.110> faces<00:01:06.770> the<00:01:06.800> internet<00:01:07.190> so<00:01:07.400> all 00:01:07.540 --> 00:01:07.550 align:start position:0% systems that faces the internet so all 00:01:07.550 --> 00:01:09.550 align:start position:0% systems that faces the internet so all the<00:01:07.670> incoming<00:01:07.970> traffic<00:01:08.420> from<00:01:08.720> devices<00:01:09.230> from 00:01:09.550 --> 00:01:09.560 align:start position:0% the incoming traffic from devices from 00:01:09.560 --> 00:01:11.830 align:start position:0% the incoming traffic from devices from the<00:01:09.890> user<00:01:10.670> interfaces<00:01:11.240> and<00:01:11.329> clients<00:01:11.630> that<00:01:11.750> you 00:01:11.830 --> 00:01:11.840 align:start position:0% the user interfaces and clients that you 00:01:11.840 --> 00:01:13.990 align:start position:0% the user interfaces and clients that you play<00:01:12.020> playback<00:01:13.009> movies<00:01:13.310> and<00:01:13.460> TV<00:01:13.640> shows<00:01:13.670> on 00:01:13.990 --> 00:01:14.000 align:start position:0% play playback movies and TV shows on 00:01:14.000 --> 00:01:15.850 align:start position:0% play playback movies and TV shows on with<00:01:14.180> netflix<00:01:14.570> they<00:01:15.170> come<00:01:15.439> in<00:01:15.560> through<00:01:15.710> that 00:01:15.850 --> 00:01:15.860 align:start position:0% with netflix they come in through that 00:01:15.860 --> 00:01:19.149 align:start position:0% with netflix they come in through that layer<00:01:16.009> and<00:01:16.310> so<00:01:16.790> it's<00:01:16.909> the<00:01:17.030> routing<00:01:17.420> and<00:01:18.159> public 00:01:19.149 --> 00:01:19.159 align:start position:0% layer and so it's the routing and public 00:01:19.159 --> 00:01:21.249 align:start position:0% layer and so it's the routing and public api<00:01:19.460> s<00:01:19.579> and<00:01:20.030> the<00:01:20.689> hosting<00:01:21.020> of<00:01:21.049> all<00:01:21.170> the 00:01:21.249 --> 00:01:21.259 align:start position:0% api s and the hosting of all the 00:01:21.259 --> 00:01:23.289 align:start position:0% api s and the hosting of all the endpoints<00:01:21.740> for<00:01:21.950> all<00:01:22.520> basically<00:01:22.970> all<00:01:23.180> the 00:01:23.289 --> 00:01:23.299 align:start position:0% endpoints for all basically all the 00:01:23.299 --> 00:01:25.539 align:start position:0% endpoints for all basically all the functionality<00:01:23.869> for<00:01:23.990> netflix<00:01:24.350> so<00:01:25.130> i'm 00:01:25.539 --> 00:01:25.549 align:start position:0% functionality for netflix so i'm 00:01:25.549 --> 00:01:26.800 align:start position:0% functionality for netflix so i'm involved<00:01:25.850> in<00:01:26.060> the<00:01:26.240> architecture<00:01:26.720> and 00:01:26.800 --> 00:01:26.810 align:start position:0% involved in the architecture and 00:01:26.810 --> 00:01:28.330 align:start position:0% involved in the architecture and platform<00:01:27.229> and<00:01:27.500> infrastructure<00:01:28.070> of<00:01:28.189> those 00:01:28.330 --> 00:01:28.340 align:start position:0% platform and infrastructure of those 00:01:28.340 --> 00:01:33.160 align:start position:0% platform and infrastructure of those teams<00:01:29.979> started<00:01:30.979> those<00:01:31.100> systems<00:01:31.960> there<00:01:32.960> it's 00:01:33.160 --> 00:01:33.170 align:start position:0% teams started those systems there it's 00:01:33.170 --> 00:01:35.249 align:start position:0% teams started those systems there it's made<00:01:33.290> up<00:01:33.409> of<00:01:33.500> a<00:01:33.649> few<00:01:33.920> different<00:01:34.009> teams<00:01:34.340> and 00:01:35.249 --> 00:01:35.259 align:start position:0% made up of a few different teams and 00:01:35.259 --> 00:01:39.100 align:start position:0% made up of a few different teams and also<00:01:36.259> the<00:01:36.350> operations<00:01:36.829> of<00:01:36.950> it<00:01:37.100> okay<00:01:37.610> and<00:01:38.149> can 00:01:39.100 --> 00:01:39.110 align:start position:0% also the operations of it okay and can 00:01:39.110 --> 00:01:41.319 align:start position:0% also the operations of it okay and can it<00:01:39.140> tell<00:01:39.740> us<00:01:39.950> a<00:01:39.979> little<00:01:40.130> bit<00:01:40.340> for<00:01:40.880> folks<00:01:41.149> who 00:01:41.319 --> 00:01:41.329 align:start position:0% it tell us a little bit for folks who 00:01:41.329 --> 00:01:42.910 align:start position:0% it tell us a little bit for folks who don't<00:01:41.450> know<00:01:41.719> what<00:01:42.140> they're<00:01:42.259> active<00:01:42.530> systems 00:01:42.910 --> 00:01:42.920 align:start position:0% don't know what they're active systems 00:01:42.920 --> 00:01:46.330 align:start position:0% don't know what they're active systems are<00:01:43.159> and<00:01:43.430> how<00:01:44.740> networks<00:01:45.740> became<00:01:46.070> kind<00:01:46.219> of<00:01:46.250> a 00:01:46.330 --> 00:01:46.340 align:start position:0% are and how networks became kind of a 00:01:46.340 --> 00:01:48.550 align:start position:0% are and how networks became kind of a good<00:01:46.490> use<00:01:46.670> case<00:01:46.759> for<00:01:46.969> reactive<00:01:47.659> systems<00:01:47.990> sure 00:01:48.550 --> 00:01:48.560 align:start position:0% good use case for reactive systems sure 00:01:48.560 --> 00:01:53.590 align:start position:0% good use case for reactive systems sure so<00:01:49.340> reactive<00:01:49.759> systems<00:01:50.439> in<00:01:51.439> a<00:01:51.649> more<00:01:52.070> p<00:01:52.280> in<00:01:52.600> pure 00:01:53.590 --> 00:01:53.600 align:start position:0% so reactive systems in a more p in pure 00:01:53.600 --> 00:01:57.300 align:start position:0% so reactive systems in a more p in pure sense<00:01:54.049> or<00:01:54.350> ones<00:01:54.649> that<00:01:55.479> as<00:01:56.479> their<00:01:56.899> name<00:01:56.930> implies 00:01:57.300 --> 00:01:57.310 align:start position:0% sense or ones that as their name implies 00:01:57.310 --> 00:02:01.569 align:start position:0% sense or ones that as their name implies react<00:01:58.310> to<00:01:58.610> data<00:01:58.850> and<00:01:58.969> events<00:01:59.479> as<00:02:00.409> they<00:02:00.890> occur 00:02:01.569 --> 00:02:01.579 align:start position:0% react to data and events as they occur 00:02:01.579 --> 00:02:04.630 align:start position:0% react to data and events as they occur rather<00:02:02.570> than<00:02:03.049> imperative<00:02:03.950> lee<00:02:04.039> telling<00:02:04.460> it 00:02:04.630 --> 00:02:04.640 align:start position:0% rather than imperative lee telling it 00:02:04.640 --> 00:02:06.219 align:start position:0% rather than imperative lee telling it what<00:02:05.180> to<00:02:05.240> do<00:02:05.420> at<00:02:05.509> any<00:02:05.600> given<00:02:05.899> point<00:02:06.049> in<00:02:06.140> time 00:02:06.219 --> 00:02:06.229 align:start position:0% what to do at any given point in time 00:02:06.229 --> 00:02:10.779 align:start position:0% what to do at any given point in time and<00:02:07.180> in<00:02:08.180> practice<00:02:09.020> that<00:02:09.590> there's<00:02:10.039> a<00:02:10.100> broad 00:02:10.779 --> 00:02:10.789 align:start position:0% and in practice that there's a broad 00:02:10.789 --> 00:02:12.640 align:start position:0% and in practice that there's a broad spectrum<00:02:11.000> of<00:02:11.390> what<00:02:11.540> that<00:02:11.690> means<00:02:11.960> is<00:02:12.230> you<00:02:12.350> apply 00:02:12.640 --> 00:02:12.650 align:start position:0% spectrum of what that means is you apply 00:02:12.650 --> 00:02:16.030 align:start position:0% spectrum of what that means is you apply it<00:02:12.680> the<00:02:13.519> reason<00:02:13.849> why<00:02:13.970> it<00:02:14.440> became<00:02:15.440> interesting 00:02:16.030 --> 00:02:16.040 align:start position:0% it the reason why it became interesting 00:02:16.040 --> 00:02:17.880 align:start position:0% it the reason why it became interesting to<00:02:16.160> us<00:02:16.340> is<00:02:16.580> a<00:02:16.640> few<00:02:16.879> years<00:02:17.000> ago<00:02:17.209> we<00:02:17.540> were 00:02:17.880 --> 00:02:17.890 align:start position:0% to us is a few years ago we were 00:02:17.890 --> 00:02:19.770 align:start position:0% to us is a few years ago we were to<00:02:18.100> optimize<00:02:18.280> the<00:02:18.910> performance<00:02:19.240> in<00:02:19.690> our 00:02:19.770 --> 00:02:19.780 align:start position:0% to optimize the performance in our 00:02:19.780 --> 00:02:22.610 align:start position:0% to optimize the performance in our systems<00:02:20.170> we<00:02:20.740> realize<00:02:21.160> that<00:02:21.190> we<00:02:21.490> needed<00:02:21.700> to 00:02:22.610 --> 00:02:22.620 align:start position:0% systems we realize that we needed to 00:02:22.620 --> 00:02:28.440 align:start position:0% systems we realize that we needed to adopt<00:02:23.790> concurrency<00:02:25.560> primarily<00:02:26.560> for<00:02:27.010> i<00:02:27.400> 0<00:02:27.670> for 00:02:28.440 --> 00:02:28.450 align:start position:0% adopt concurrency primarily for i 0 for 00:02:28.450 --> 00:02:30.090 align:start position:0% adopt concurrency primarily for i 0 for concurrent<00:02:28.870> execution<00:02:28.930> of<00:02:29.440> various 00:02:30.090 --> 00:02:30.100 align:start position:0% concurrent execution of various 00:02:30.100 --> 00:02:32.070 align:start position:0% concurrent execution of various different<00:02:30.340> network<00:02:30.550> requests<00:02:31.120> to<00:02:31.690> compose 00:02:32.070 --> 00:02:32.080 align:start position:0% different network requests to compose 00:02:32.080 --> 00:02:35.090 align:start position:0% different network requests to compose together<00:02:32.530> the<00:02:33.250> back-end<00:02:33.640> systems<00:02:34.630> in<00:02:34.840> the 00:02:35.090 --> 00:02:35.100 align:start position:0% together the back-end systems in the 00:02:35.100 --> 00:02:37.260 align:start position:0% together the back-end systems in the primary<00:02:36.100> driving<00:02:36.370> factor<00:02:36.790> for<00:02:36.970> that<00:02:37.090> is<00:02:37.240> that 00:02:37.260 --> 00:02:37.270 align:start position:0% primary driving factor for that is that 00:02:37.270 --> 00:02:39.240 align:start position:0% primary driving factor for that is that we<00:02:37.480> were<00:02:37.570> trying<00:02:37.900> to<00:02:37.959> move<00:02:38.560> our<00:02:38.860> device 00:02:39.240 --> 00:02:39.250 align:start position:0% we were trying to move our device 00:02:39.250 --> 00:02:40.770 align:start position:0% we were trying to move our device traffic<00:02:39.790> patterns<00:02:40.120> to<00:02:40.240> be<00:02:40.330> more<00:02:40.510> coarse 00:02:40.770 --> 00:02:40.780 align:start position:0% traffic patterns to be more coarse 00:02:40.780 --> 00:02:42.570 align:start position:0% traffic patterns to be more coarse grained<00:02:41.050> so<00:02:41.470> they<00:02:41.740> would<00:02:41.890> fetch<00:02:42.070> more<00:02:42.310> data 00:02:42.570 --> 00:02:42.580 align:start position:0% grained so they would fetch more data 00:02:42.580 --> 00:02:44.550 align:start position:0% grained so they would fetch more data all<00:02:42.790> at<00:02:42.940> once<00:02:43.120> and<00:02:43.420> we<00:02:44.050> didn't<00:02:44.260> want<00:02:44.290> to<00:02:44.440> make 00:02:44.550 --> 00:02:44.560 align:start position:0% all at once and we didn't want to make 00:02:44.560 --> 00:02:45.840 align:start position:0% all at once and we didn't want to make that<00:02:44.680> I'll<00:02:44.800> be<00:02:44.920> sequential<00:02:45.400> and<00:02:45.489> increase<00:02:45.700> the 00:02:45.840 --> 00:02:45.850 align:start position:0% that I'll be sequential and increase the 00:02:45.850 --> 00:02:50.340 align:start position:0% that I'll be sequential and increase the user<00:02:46.030> latency<00:02:46.510> and<00:02:46.660> so<00:02:48.090> while<00:02:49.090> adopting<00:02:49.510> while 00:02:50.340 --> 00:02:50.350 align:start position:0% user latency and so while adopting while 00:02:50.350 --> 00:02:52.320 align:start position:0% user latency and so while adopting while pursuing<00:02:50.709> a<00:02:50.980> more<00:02:51.160> concurrent<00:02:51.520> approach<00:02:52.000> to 00:02:52.320 --> 00:02:52.330 align:start position:0% pursuing a more concurrent approach to 00:02:52.330 --> 00:02:54.800 align:start position:0% pursuing a more concurrent approach to implementing<00:02:52.930> our<00:02:53.260> web<00:02:53.560> service<00:02:53.860> endpoints 00:02:54.800 --> 00:02:54.810 align:start position:0% implementing our web service endpoints 00:02:54.810 --> 00:02:58.020 align:start position:0% implementing our web service endpoints we<00:02:55.810> decided<00:02:56.230> that<00:02:56.670> asynchrony<00:02:57.670> is<00:02:57.730> where<00:02:57.910> we 00:02:58.020 --> 00:02:58.030 align:start position:0% we decided that asynchrony is where we 00:02:58.030 --> 00:03:00.780 align:start position:0% we decided that asynchrony is where we needed<00:02:58.180> to<00:02:58.300> go<00:02:58.420> and<00:02:58.780> to<00:02:59.320> do<00:02:59.440> that<00:02:59.590> we<00:02:59.830> looked<00:03:00.550> at 00:03:00.780 --> 00:03:00.790 align:start position:0% needed to go and to do that we looked at 00:03:00.790 --> 00:03:04.470 align:start position:0% needed to go and to do that we looked at how<00:03:01.300> we<00:03:01.360> could<00:03:02.070> have<00:03:03.070> an<00:03:03.310> abstraction<00:03:04.150> for 00:03:04.470 --> 00:03:04.480 align:start position:0% how we could have an abstraction for 00:03:04.480 --> 00:03:06.270 align:start position:0% how we could have an abstraction for composing<00:03:04.810> those<00:03:05.230> that<00:03:05.800> wasn't<00:03:06.130> just 00:03:06.270 --> 00:03:06.280 align:start position:0% composing those that wasn't just 00:03:06.280 --> 00:03:09.090 align:start position:0% composing those that wasn't just callbacks<00:03:06.670> and<00:03:07.230> that<00:03:08.230> led<00:03:08.440> us<00:03:08.560> to<00:03:08.739> the 00:03:09.090 --> 00:03:09.100 align:start position:0% callbacks and that led us to the 00:03:09.100 --> 00:03:11.190 align:start position:0% callbacks and that led us to the reactive<00:03:09.820> model<00:03:10.120> and<00:03:10.360> over<00:03:10.720> the<00:03:10.840> years<00:03:10.870> we've 00:03:11.190 --> 00:03:11.200 align:start position:0% reactive model and over the years we've 00:03:11.200 --> 00:03:13.280 align:start position:0% reactive model and over the years we've matured<00:03:11.410> a<00:03:11.709> lot<00:03:11.860> in<00:03:12.040> our<00:03:12.160> thinking<00:03:12.430> and<00:03:12.730> our 00:03:13.280 --> 00:03:13.290 align:start position:0% matured a lot in our thinking and our 00:03:13.290 --> 00:03:18.270 align:start position:0% matured a lot in our thinking and our execution<00:03:14.290> of<00:03:14.350> that<00:03:15.600> so<00:03:16.600> how<00:03:16.750> much<00:03:16.780> of<00:03:17.320> Netflix 00:03:18.270 --> 00:03:18.280 align:start position:0% execution of that so how much of Netflix 00:03:18.280 --> 00:03:21.060 align:start position:0% execution of that so how much of Netflix is<00:03:18.400> now<00:03:18.550> using<00:03:18.820> your<00:03:19.360> reactive<00:03:19.690> stack<00:03:20.070> it 00:03:21.060 --> 00:03:21.070 align:start position:0% is now using your reactive stack it 00:03:21.070 --> 00:03:22.890 align:start position:0% is now using your reactive stack it depends<00:03:21.459> on<00:03:21.550> if<00:03:21.700> they<00:03:21.880> if<00:03:22.570> you<00:03:22.660> talk<00:03:22.870> about 00:03:22.890 --> 00:03:22.900 align:start position:0% depends on if they if you talk about 00:03:22.900 --> 00:03:26.190 align:start position:0% depends on if they if you talk about that<00:03:23.200> as<00:03:23.350> knowingly<00:03:23.769> or<00:03:24.220> unknowingly<00:03:25.200> so 00:03:26.190 --> 00:03:26.200 align:start position:0% that as knowingly or unknowingly so 00:03:26.200 --> 00:03:28.380 align:start position:0% that as knowingly or unknowingly so unknowingly<00:03:27.070> it's<00:03:27.489> actually<00:03:27.910> running<00:03:28.120> all 00:03:28.380 --> 00:03:28.390 align:start position:0% unknowingly it's actually running all 00:03:28.390 --> 00:03:30.479 align:start position:0% unknowingly it's actually running all over<00:03:28.420> the<00:03:28.780> place<00:03:28.989> because<00:03:29.200> it's<00:03:29.560> for<00:03:30.130> example 00:03:30.479 --> 00:03:30.489 align:start position:0% over the place because it's for example 00:03:30.489 --> 00:03:31.890 align:start position:0% over the place because it's for example hysterics<00:03:30.940> which<00:03:31.269> is<00:03:31.420> our<00:03:31.540> fault<00:03:31.720> tolerance 00:03:31.890 --> 00:03:31.900 align:start position:0% hysterics which is our fault tolerance 00:03:31.900 --> 00:03:34.080 align:start position:0% hysterics which is our fault tolerance layer<00:03:32.350> bulk<00:03:32.620> adding<00:03:32.860> layer<00:03:32.980> is<00:03:33.220> now<00:03:33.790> all 00:03:34.080 --> 00:03:34.090 align:start position:0% layer bulk adding layer is now all 00:03:34.090 --> 00:03:36.690 align:start position:0% layer bulk adding layer is now all implemented<00:03:34.690> using<00:03:34.870> the<00:03:35.769> reactive<00:03:36.310> patterns 00:03:36.690 --> 00:03:36.700 align:start position:0% implemented using the reactive patterns 00:03:36.700 --> 00:03:38.490 align:start position:0% implemented using the reactive patterns and<00:03:36.970> that's<00:03:37.420> used<00:03:37.690> throughout<00:03:37.989> the<00:03:38.170> company 00:03:38.490 --> 00:03:38.500 align:start position:0% and that's used throughout the company 00:03:38.500 --> 00:03:42.300 align:start position:0% and that's used throughout the company but<00:03:39.420> most<00:03:40.420> of<00:03:40.720> the<00:03:40.900> the<00:03:41.500> teams<00:03:41.769> still<00:03:42.100> don't 00:03:42.300 --> 00:03:42.310 align:start position:0% but most of the the teams still don't 00:03:42.310 --> 00:03:44.600 align:start position:0% but most of the the teams still don't actually<00:03:42.850> program<00:03:43.780> in<00:03:43.900> a<00:03:43.989> reactive<00:03:44.350> manner 00:03:44.600 --> 00:03:44.610 align:start position:0% actually program in a reactive manner 00:03:44.610 --> 00:03:47.190 align:start position:0% actually program in a reactive manner most<00:03:45.610> of<00:03:45.850> the<00:03:45.940> middle<00:03:46.180> tier<00:03:46.420> systems<00:03:46.900> that 00:03:47.190 --> 00:03:47.200 align:start position:0% most of the middle tier systems that 00:03:47.200 --> 00:03:49.680 align:start position:0% most of the middle tier systems that they<00:03:47.500> existed<00:03:48.400> long<00:03:48.790> before<00:03:48.850> we<00:03:49.420> chose<00:03:49.660> to 00:03:49.680 --> 00:03:49.690 align:start position:0% they existed long before we chose to 00:03:49.690 --> 00:03:51.750 align:start position:0% they existed long before we chose to start<00:03:49.930> adopting<00:03:50.170> and<00:03:50.590> the<00:03:51.040> migration<00:03:51.549> path 00:03:51.750 --> 00:03:51.760 align:start position:0% start adopting and the migration path 00:03:51.760 --> 00:03:54.539 align:start position:0% start adopting and the migration path from<00:03:52.200> the<00:03:53.200> imperative<00:03:54.010> style<00:03:54.250> to<00:03:54.459> the 00:03:54.539 --> 00:03:54.549 align:start position:0% from the imperative style to the 00:03:54.549 --> 00:03:57.050 align:start position:0% from the imperative style to the reactive<00:03:54.910> style<00:03:55.150> is<00:03:55.360> a<00:03:55.660> non-trivial<00:03:56.110> one<00:03:56.470> and 00:03:57.050 --> 00:03:57.060 align:start position:0% reactive style is a non-trivial one and 00:03:57.060 --> 00:03:59.759 align:start position:0% reactive style is a non-trivial one and the<00:03:58.060> majority<00:03:58.390> of<00:03:58.600> teams<00:03:58.900> have<00:03:59.200> not<00:03:59.350> decided 00:03:59.759 --> 00:03:59.769 align:start position:0% the majority of teams have not decided 00:03:59.769 --> 00:04:02.759 align:start position:0% the majority of teams have not decided that<00:04:00.070> it<00:04:00.190> is<00:04:00.310> worth<00:04:00.640> their<00:04:01.180> purse<00:04:01.780> than<00:04:02.590> making 00:04:02.759 --> 00:04:02.769 align:start position:0% that it is worth their purse than making 00:04:02.769 --> 00:04:05.610 align:start position:0% that it is worth their purse than making those<00:04:02.950> changes<00:04:03.450> however<00:04:04.450> at<00:04:04.930> the<00:04:05.230> edge 00:04:05.610 --> 00:04:05.620 align:start position:0% those changes however at the edge 00:04:05.620 --> 00:04:09.660 align:start position:0% those changes however at the edge systems<00:04:06.579> layer<00:04:06.910> we<00:04:07.500> if<00:04:08.500> you<00:04:08.680> were<00:04:08.799> to<00:04:09.370> split 00:04:09.660 --> 00:04:09.670 align:start position:0% systems layer we if you were to split 00:04:09.670 --> 00:04:11.789 align:start position:0% systems layer we if you were to split our<00:04:09.970> code<00:04:10.510> base<00:04:10.540> in<00:04:10.930> half<00:04:11.140> into<00:04:11.620> two 00:04:11.789 --> 00:04:11.799 align:start position:0% our code base in half into two 00:04:11.799 --> 00:04:13.830 align:start position:0% our code base in half into two horizontal<00:04:12.340> layers<00:04:12.549> the<00:04:13.120> bottom<00:04:13.450> half<00:04:13.690> is 00:04:13.830 --> 00:04:13.840 align:start position:0% horizontal layers the bottom half is 00:04:13.840 --> 00:04:16.529 align:start position:0% horizontal layers the bottom half is still<00:04:14.140> very<00:04:14.709> much<00:04:14.950> imperative<00:04:15.640> and<00:04:15.850> pull 00:04:16.529 --> 00:04:16.539 align:start position:0% still very much imperative and pull 00:04:16.539 --> 00:04:19.529 align:start position:0% still very much imperative and pull based<00:04:16.750> because<00:04:17.140> of<00:04:17.430> for<00:04:18.430> legacy<00:04:18.669> reasons<00:04:19.090> but 00:04:19.529 --> 00:04:19.539 align:start position:0% based because of for legacy reasons but 00:04:19.539 --> 00:04:20.969 align:start position:0% based because of for legacy reasons but then<00:04:19.660> we<00:04:19.780> layered<00:04:20.049> everything<00:04:20.470> on<00:04:20.560> top<00:04:20.769> is 00:04:20.969 --> 00:04:20.979 align:start position:0% then we layered everything on top is 00:04:20.979 --> 00:04:24.719 align:start position:0% then we layered everything on top is fully<00:04:21.519> reactive<00:04:22.000> solver<00:04:22.390> ap<00:04:22.750> is<00:04:22.840> our<00:04:23.729> reactive 00:04:24.719 --> 00:04:24.729 align:start position:0% fully reactive solver ap is our reactive 00:04:24.729 --> 00:04:27.810 align:start position:0% fully reactive solver ap is our reactive and<00:04:24.940> then<00:04:25.660> the<00:04:26.020> next<00:04:26.380> layer<00:04:26.530> down<00:04:26.560> of<00:04:27.010> our<00:04:27.340> the 00:04:27.810 --> 00:04:27.820 align:start position:0% and then the next layer down of our the 00:04:27.820 --> 00:04:29.880 align:start position:0% and then the next layer down of our the devices<00:04:28.240> and<00:04:28.390> clients<00:04:28.810> they<00:04:28.930> also<00:04:29.110> the 00:04:29.880 --> 00:04:29.890 align:start position:0% devices and clients they also the 00:04:29.890 --> 00:04:31.050 align:start position:0% devices and clients they also the majority<00:04:30.340> of<00:04:30.370> them<00:04:30.580> also 00:04:31.050 --> 00:04:31.060 align:start position:0% majority of them also 00:04:31.060 --> 00:04:35.580 align:start position:0% majority of them also use<00:04:31.180> reactive<00:04:32.050> patterns<00:04:32.730> in<00:04:33.730> JavaScript<00:04:34.590> in 00:04:35.580 --> 00:04:35.590 align:start position:0% use reactive patterns in JavaScript in 00:04:35.590 --> 00:04:37.800 align:start position:0% use reactive patterns in JavaScript in how<00:04:35.889> they<00:04:36.040> interact<00:04:36.490> with<00:04:36.730> us<00:04:36.910> through<00:04:37.720> the 00:04:37.800 --> 00:04:37.810 align:start position:0% how they interact with us through the 00:04:37.810 --> 00:04:40.080 align:start position:0% how they interact with us through the web<00:04:37.930> services<00:04:38.440> okay<00:04:39.070> okay<00:04:39.520> so<00:04:39.669> it's<00:04:39.940> a 00:04:40.080 --> 00:04:40.090 align:start position:0% web services okay okay so it's a 00:04:40.090 --> 00:04:42.990 align:start position:0% web services okay okay so it's a multilingual<00:04:40.630> kind<00:04:41.139> of<00:04:41.230> them<00:04:41.830> yeah<00:04:42.280> so<00:04:42.430> we<00:04:42.550> use 00:04:42.990 --> 00:04:43.000 align:start position:0% multilingual kind of them yeah so we use 00:04:43.000 --> 00:04:47.420 align:start position:0% multilingual kind of them yeah so we use the<00:04:43.210> reactive<00:04:43.630> patterns<00:04:43.960> in<00:04:44.260> Java<00:04:45.220> groovy<00:04:45.790> and 00:04:47.420 --> 00:04:47.430 align:start position:0% the reactive patterns in Java groovy and 00:04:47.430 --> 00:04:50.970 align:start position:0% the reactive patterns in Java groovy and JavaScript<00:04:48.720> so<00:04:49.720> I<00:04:49.750> noticed<00:04:50.650> you<00:04:50.770> guys<00:04:50.919> are 00:04:50.970 --> 00:04:50.980 align:start position:0% JavaScript so I noticed you guys are 00:04:50.980 --> 00:04:53.040 align:start position:0% JavaScript so I noticed you guys are basically<00:04:51.550> you<00:04:52.210> know<00:04:52.300> very<00:04:52.510> consistently 00:04:53.040 --> 00:04:53.050 align:start position:0% basically you know very consistently 00:04:53.050 --> 00:04:56.010 align:start position:0% basically you know very consistently improving<00:04:53.590> our<00:04:54.580> X<00:04:54.790> Java<00:04:55.240> like<00:04:55.389> a<00:04:55.480> system<00:04:55.810> so<00:04:55.990> we 00:04:56.010 --> 00:04:56.020 align:start position:0% improving our X Java like a system so we 00:04:56.020 --> 00:04:57.750 align:start position:0% improving our X Java like a system so we had<00:04:56.530> them<00:04:56.710> it<00:04:56.860> up<00:04:57.010> a<00:04:57.160> couple<00:04:57.250> years<00:04:57.430> ago<00:04:57.580> two 00:04:57.750 --> 00:04:57.760 align:start position:0% had them it up a couple years ago two 00:04:57.760 --> 00:05:00.030 align:start position:0% had them it up a couple years ago two subscales<00:04:58.180> Rackspace<00:04:58.870> and<00:04:59.139> since<00:04:59.800> then 00:05:00.030 --> 00:05:00.040 align:start position:0% subscales Rackspace and since then 00:05:00.040 --> 00:05:01.680 align:start position:0% subscales Rackspace and since then basically<00:05:00.310> succeeded<00:05:01.060> in<00:05:01.210> kind<00:05:01.389> of<00:05:01.480> you<00:05:01.630> know 00:05:01.680 --> 00:05:01.690 align:start position:0% basically succeeded in kind of you know 00:05:01.690 --> 00:05:03.360 align:start position:0% basically succeeded in kind of you know moving<00:05:02.500> this<00:05:02.710> technology<00:05:03.190> through 00:05:03.360 --> 00:05:03.370 align:start position:0% moving this technology through 00:05:03.370 --> 00:05:04.680 align:start position:0% moving this technology through organization<00:05:03.970> which<00:05:04.120> is<00:05:04.270> a<00:05:04.300> no<00:05:04.510> mean<00:05:04.660> feat 00:05:04.680 --> 00:05:04.690 align:start position:0% organization which is a no mean feat 00:05:04.690 --> 00:05:07.020 align:start position:0% organization which is a no mean feat like<00:05:05.080> network<00:05:05.500> is<00:05:05.620> a<00:05:05.710> big<00:05:05.919> company<00:05:06.790> we<00:05:06.880> know 00:05:07.020 --> 00:05:07.030 align:start position:0% like network is a big company we know 00:05:07.030 --> 00:05:10.409 align:start position:0% like network is a big company we know company<00:05:07.870> is<00:05:07.930> kind<00:05:08.200> of<00:05:08.290> not<00:05:09.180> you<00:05:10.180> know<00:05:10.300> the 00:05:10.409 --> 00:05:10.419 align:start position:0% company is kind of not you know the 00:05:10.419 --> 00:05:11.969 align:start position:0% company is kind of not you know the commercials<00:05:10.960> the<00:05:11.139> gross<00:05:11.320> I'm<00:05:11.590> just<00:05:11.800> very 00:05:11.969 --> 00:05:11.979 align:start position:0% commercials the gross I'm just very 00:05:11.979 --> 00:05:14.580 align:start position:0% commercials the gross I'm just very curious<00:05:12.130> how<00:05:12.460> did<00:05:12.729> you<00:05:13.000> manage<00:05:13.600> right 00:05:14.580 --> 00:05:14.590 align:start position:0% curious how did you manage right 00:05:14.590 --> 00:05:16.469 align:start position:0% curious how did you manage right introduced<00:05:15.100> this<00:05:15.250> complex<00:05:15.580> technology<00:05:16.270> to 00:05:16.469 --> 00:05:16.479 align:start position:0% introduced this complex technology to 00:05:16.479 --> 00:05:17.969 align:start position:0% introduced this complex technology to kind<00:05:16.660> of<00:05:16.690> evangelize<00:05:17.200> it<00:05:17.440> get<00:05:17.680> a<00:05:17.710> lot<00:05:17.950> of 00:05:17.969 --> 00:05:17.979 align:start position:0% kind of evangelize it get a lot of 00:05:17.979 --> 00:05:21.500 align:start position:0% kind of evangelize it get a lot of people<00:05:18.340> use<00:05:18.940> it<00:05:19.650> what<00:05:20.650> are<00:05:20.860> kind<00:05:21.100> of 00:05:21.500 --> 00:05:21.510 align:start position:0% people use it what are kind of 00:05:21.510 --> 00:05:23.520 align:start position:0% people use it what are kind of ingredients<00:05:22.510> that<00:05:22.660> the<00:05:22.960> success<00:05:23.290> of<00:05:23.320> this 00:05:23.520 --> 00:05:23.530 align:start position:0% ingredients that the success of this 00:05:23.530 --> 00:05:25.980 align:start position:0% ingredients that the success of this like<00:05:23.800> what<00:05:24.310> are<00:05:24.490> the<00:05:24.580> some<00:05:24.760> tricks<00:05:25.090> you<00:05:25.360> kind 00:05:25.980 --> 00:05:25.990 align:start position:0% like what are the some tricks you kind 00:05:25.990 --> 00:05:29.070 align:start position:0% like what are the some tricks you kind of<00:05:26.250> what<00:05:27.250> happens<00:05:27.520> which<00:05:28.330> enabled<00:05:28.960> you<00:05:29.050> to 00:05:29.070 --> 00:05:29.080 align:start position:0% of what happens which enabled you to 00:05:29.080 --> 00:05:30.980 align:start position:0% of what happens which enabled you to move<00:05:29.440> this<00:05:29.560> technology<00:05:29.979> through<00:05:30.220> the<00:05:30.340> company 00:05:30.980 --> 00:05:30.990 align:start position:0% move this technology through the company 00:05:30.990 --> 00:05:34.230 align:start position:0% move this technology through the company well<00:05:31.990> for<00:05:32.200> one<00:05:32.350> thing<00:05:32.380> we<00:05:33.100> never<00:05:33.280> attempted<00:05:34.090> to 00:05:34.230 --> 00:05:34.240 align:start position:0% well for one thing we never attempted to 00:05:34.240 --> 00:05:36.779 align:start position:0% well for one thing we never attempted to force<00:05:34.810> it<00:05:35.020> down<00:05:35.050> anyone's<00:05:35.530> throat<00:05:35.620> and<00:05:36.220> that's 00:05:36.779 --> 00:05:36.789 align:start position:0% force it down anyone's throat and that's 00:05:36.789 --> 00:05:39.990 align:start position:0% force it down anyone's throat and that's why<00:05:37.060> even<00:05:37.390> to<00:05:37.630> this<00:05:37.750> day<00:05:37.810> it's<00:05:38.680> not<00:05:38.950> every<00:05:39.820> team 00:05:39.990 --> 00:05:40.000 align:start position:0% why even to this day it's not every team 00:05:40.000 --> 00:05:44.460 align:start position:0% why even to this day it's not every team that's<00:05:40.030> using<00:05:40.539> it<00:05:42.360> so<00:05:43.360> the<00:05:43.630> important<00:05:44.110> factor 00:05:44.460 --> 00:05:44.470 align:start position:0% that's using it so the important factor 00:05:44.470 --> 00:05:46.440 align:start position:0% that's using it so the important factor is<00:05:44.560> that<00:05:44.680> we<00:05:44.830> we<00:05:45.250> applied<00:05:45.610> it<00:05:45.640> where<00:05:46.000> we<00:05:46.030> felt 00:05:46.440 --> 00:05:46.450 align:start position:0% is that we we applied it where we felt 00:05:46.450 --> 00:05:49.080 align:start position:0% is that we we applied it where we felt it<00:05:46.570> was<00:05:46.690> needed<00:05:46.840> we<00:05:47.229> demonstrated<00:05:48.090> the 00:05:49.080 --> 00:05:49.090 align:start position:0% it was needed we demonstrated the 00:05:49.090 --> 00:05:50.610 align:start position:0% it was needed we demonstrated the success<00:05:49.450> we<00:05:49.600> were<00:05:49.750> having<00:05:50.080> and<00:05:50.260> we<00:05:50.350> talked 00:05:50.610 --> 00:05:50.620 align:start position:0% success we were having and we talked 00:05:50.620 --> 00:05:53.969 align:start position:0% success we were having and we talked about<00:05:50.770> it<00:05:51.039> and<00:05:51.460> then<00:05:52.390> other<00:05:52.660> teams<00:05:53.050> either 00:05:53.969 --> 00:05:53.979 align:start position:0% about it and then other teams either 00:05:53.979 --> 00:05:56.040 align:start position:0% about it and then other teams either said<00:05:54.400> that's<00:05:54.640> interesting<00:05:55.240> but<00:05:55.539> we<00:05:55.870> don't 00:05:56.040 --> 00:05:56.050 align:start position:0% said that's interesting but we don't 00:05:56.050 --> 00:05:59.100 align:start position:0% said that's interesting but we don't really<00:05:56.110> need<00:05:57.010> to<00:05:57.280> to<00:05:57.820> adopt<00:05:58.120> that<00:05:58.210> or<00:05:58.570> some 00:05:59.100 --> 00:05:59.110 align:start position:0% really need to to adopt that or some 00:05:59.110 --> 00:06:00.510 align:start position:0% really need to to adopt that or some other<00:05:59.229> team<00:05:59.500> said<00:05:59.740> that's<00:05:59.950> great<00:06:00.250> and<00:06:00.430> they 00:06:00.510 --> 00:06:00.520 align:start position:0% other team said that's great and they 00:06:00.520 --> 00:06:03.260 align:start position:0% other team said that's great and they start<00:06:00.760> to<00:06:00.910> adopt<00:06:01.180> it<00:06:01.330> all<00:06:01.539> on<00:06:01.720> their<00:06:01.900> own<00:06:01.930> and 00:06:03.260 --> 00:06:03.270 align:start position:0% start to adopt it all on their own and 00:06:03.270 --> 00:06:06.300 align:start position:0% start to adopt it all on their own and to<00:06:04.270> make<00:06:04.450> that<00:06:04.690> so<00:06:04.960> that<00:06:05.080> it<00:06:05.200> scaled<00:06:05.889> we 00:06:06.300 --> 00:06:06.310 align:start position:0% to make that so that it scaled we 00:06:06.310 --> 00:06:09.270 align:start position:0% to make that so that it scaled we invested<00:06:07.000> quite<00:06:07.120> a<00:06:07.240> bit<00:06:07.479> in<00:06:08.280> documentation 00:06:09.270 --> 00:06:09.280 align:start position:0% invested quite a bit in documentation 00:06:09.280 --> 00:06:12.480 align:start position:0% invested quite a bit in documentation and<00:06:09.700> tutorials<00:06:10.690> on<00:06:10.750> such<00:06:11.020> things<00:06:11.289> in<00:06:11.889> fact<00:06:12.220> the 00:06:12.480 --> 00:06:12.490 align:start position:0% and tutorials on such things in fact the 00:06:12.490 --> 00:06:14.790 align:start position:0% and tutorials on such things in fact the very<00:06:13.270> thing<00:06:13.600> that<00:06:13.630> made<00:06:13.930> it<00:06:14.110> a<00:06:14.260> successful 00:06:14.790 --> 00:06:14.800 align:start position:0% very thing that made it a successful 00:06:14.800 --> 00:06:16.469 align:start position:0% very thing that made it a successful open<00:06:15.160> source<00:06:15.340> project<00:06:15.760> is<00:06:15.880> what<00:06:16.090> helped<00:06:16.360> us 00:06:16.469 --> 00:06:16.479 align:start position:0% open source project is what helped us 00:06:16.479 --> 00:06:18.779 align:start position:0% open source project is what helped us with<00:06:17.139> the<00:06:17.350> the<00:06:17.919> team's<00:06:18.160> internally<00:06:18.669> who 00:06:18.779 --> 00:06:18.789 align:start position:0% with the the team's internally who 00:06:18.789 --> 00:06:21.840 align:start position:0% with the the team's internally who wanted<00:06:19.030> to<00:06:19.180> adopt<00:06:19.389> it<00:06:19.660> and<00:06:19.810> use<00:06:20.020> it<00:06:20.050> because<00:06:20.850> in 00:06:21.840 --> 00:06:21.850 align:start position:0% wanted to adopt it and use it because in 00:06:21.850 --> 00:06:23.340 align:start position:0% wanted to adopt it and use it because in effect<00:06:22.240> we<00:06:22.419> actually<00:06:22.660> treated<00:06:22.930> them<00:06:23.080> the<00:06:23.200> same 00:06:23.340 --> 00:06:23.350 align:start position:0% effect we actually treated them the same 00:06:23.350 --> 00:06:24.960 align:start position:0% effect we actually treated them the same as<00:06:23.500> anyone<00:06:23.830> else<00:06:23.889> where<00:06:24.400> here's<00:06:24.910> the 00:06:24.960 --> 00:06:24.970 align:start position:0% as anyone else where here's the 00:06:24.970 --> 00:06:26.460 align:start position:0% as anyone else where here's the documentation<00:06:25.720> eat<00:06:25.870> here's<00:06:26.110> how<00:06:26.229> it<00:06:26.289> works 00:06:26.460 --> 00:06:26.470 align:start position:0% documentation eat here's how it works 00:06:26.470 --> 00:06:28.050 align:start position:0% documentation eat here's how it works here's<00:06:26.889> where<00:06:27.039> the<00:06:27.130> artifacts<00:06:27.550> live<00:06:27.820> and<00:06:28.000> how 00:06:28.050 --> 00:06:28.060 align:start position:0% here's where the artifacts live and how 00:06:28.060 --> 00:06:29.600 align:start position:0% here's where the artifacts live and how you<00:06:28.120> pull<00:06:28.360> it<00:06:28.450> into<00:06:28.539> your<00:06:28.690> code<00:06:28.810> base<00:06:28.840> mm-hmm 00:06:29.600 --> 00:06:29.610 align:start position:0% you pull it into your code base mm-hmm 00:06:29.610 --> 00:06:33.510 align:start position:0% you pull it into your code base mm-hmm and<00:06:30.610> then<00:06:31.240> the<00:06:31.360> the<00:06:31.389> other<00:06:31.870> way<00:06:32.110> is<00:06:32.520> just 00:06:33.510 --> 00:06:33.520 align:start position:0% and then the the other way is just 00:06:33.520 --> 00:06:35.760 align:start position:0% and then the the other way is just internal<00:06:34.419> training<00:06:34.660> we<00:06:35.050> spend<00:06:35.289> a<00:06:35.350> lot<00:06:35.380> of<00:06:35.620> time 00:06:35.760 --> 00:06:35.770 align:start position:0% internal training we spend a lot of time 00:06:35.770 --> 00:06:38.250 align:start position:0% internal training we spend a lot of time on<00:06:36.130> making<00:06:36.460> sure<00:06:36.490> that<00:06:36.669> we<00:06:36.729> provided<00:06:37.090> in<00:06:37.870> the 00:06:38.250 --> 00:06:38.260 align:start position:0% on making sure that we provided in the 00:06:38.260 --> 00:06:39.990 align:start position:0% on making sure that we provided in the early<00:06:38.560> days<00:06:38.770> not<00:06:38.979> so<00:06:39.099> much<00:06:39.250> any<00:06:39.400> longer<00:06:39.760> but<00:06:39.880> in 00:06:39.990 --> 00:06:40.000 align:start position:0% early days not so much any longer but in 00:06:40.000 --> 00:06:41.790 align:start position:0% early days not so much any longer but in the<00:06:40.060> early<00:06:40.090> days<00:06:40.479> we<00:06:40.690> would<00:06:40.810> have<00:06:41.020> work<00:06:41.380> like 00:06:41.790 --> 00:06:41.800 align:start position:0% the early days we would have work like 00:06:41.800 --> 00:06:43.780 align:start position:0% the early days we would have work like internal<00:06:42.130> workshops<00:06:42.580> and<00:06:42.789> tutorials 00:06:43.780 --> 00:06:43.790 align:start position:0% internal workshops and tutorials 00:06:43.790 --> 00:06:46.270 align:start position:0% internal workshops and tutorials and<00:06:43.880> sessions<00:06:44.780> like<00:06:44.990> that<00:06:45.200> I<00:06:45.440> remember<00:06:46.250> you 00:06:46.270 --> 00:06:46.280 align:start position:0% and sessions like that I remember you 00:06:46.280 --> 00:06:48.880 align:start position:0% and sessions like that I remember you invested<00:06:47.060> in<00:06:47.150> documentation<00:06:47.570> a<00:06:48.020> lot<00:06:48.410> yeah<00:06:48.680> in 00:06:48.880 --> 00:06:48.890 align:start position:0% invested in documentation a lot yeah in 00:06:48.890 --> 00:06:50.830 align:start position:0% invested in documentation a lot yeah in the<00:06:49.190> lead<00:06:49.430> did<00:06:49.610> you<00:06:49.640> hire<00:06:49.970> a<00:06:50.000> technical<00:06:50.690> writer 00:06:50.830 --> 00:06:50.840 align:start position:0% the lead did you hire a technical writer 00:06:50.840 --> 00:06:53.590 align:start position:0% the lead did you hire a technical writer yes<00:06:51.290> we<00:06:51.470> do<00:06:51.590> this<00:06:51.950> yeah<00:06:52.400> in<00:06:52.550> fact<00:06:52.670> he<00:06:52.850> we<00:06:53.300> still 00:06:53.590 --> 00:06:53.600 align:start position:0% yes we do this yeah in fact he we still 00:06:53.600 --> 00:06:56.410 align:start position:0% yes we do this yeah in fact he we still have<00:06:53.840> him<00:06:54.340> so<00:06:55.340> three<00:06:55.640> years<00:06:55.850> later<00:06:56.030> he's<00:06:56.390> still 00:06:56.410 --> 00:06:56.420 align:start position:0% have him so three years later he's still 00:06:56.420 --> 00:06:58.570 align:start position:0% have him so three years later he's still working<00:06:56.930> with<00:06:57.260> us<00:06:57.440> and<00:06:57.620> in<00:06:57.890> fact<00:06:58.070> if<00:06:58.490> you're 00:06:58.570 --> 00:06:58.580 align:start position:0% working with us and in fact if you're 00:06:58.580 --> 00:06:59.980 align:start position:0% working with us and in fact if you're gonna<00:06:58.670> do<00:06:58.820> an<00:06:58.910> open<00:06:59.150> source<00:06:59.300> projects<00:06:59.750> the<00:06:59.870> way 00:06:59.980 --> 00:06:59.990 align:start position:0% gonna do an open source projects the way 00:06:59.990 --> 00:07:02.440 align:start position:0% gonna do an open source projects the way to<00:07:00.050> do<00:07:00.260> it<00:07:00.410> we<00:07:00.890> commit<00:07:01.220> code<00:07:01.490> yes<00:07:02.000> he<00:07:02.210> comes 00:07:02.440 --> 00:07:02.450 align:start position:0% to do it we commit code yes he comes 00:07:02.450 --> 00:07:04.090 align:start position:0% to do it we commit code yes he comes through<00:07:02.720> and<00:07:02.870> fixes<00:07:03.260> all<00:07:03.380> of<00:07:03.440> our<00:07:03.530> bad<00:07:03.710> english 00:07:04.090 --> 00:07:04.100 align:start position:0% through and fixes all of our bad english 00:07:04.100 --> 00:07:08.500 align:start position:0% through and fixes all of our bad english and<00:07:05.530> finishes<00:07:06.530> flushing<00:07:06.950> it<00:07:07.040> out<00:07:07.160> and<00:07:07.510> it 00:07:08.500 --> 00:07:08.510 align:start position:0% and finishes flushing it out and it 00:07:08.510 --> 00:07:10.600 align:start position:0% and finishes flushing it out and it makes<00:07:09.290> a<00:07:09.410> huge<00:07:09.620> difference<00:07:09.890> so<00:07:10.400> you<00:07:10.460> have<00:07:10.580> a 00:07:10.600 --> 00:07:10.610 align:start position:0% makes a huge difference so you have a 00:07:10.610 --> 00:07:12.610 align:start position:0% makes a huge difference so you have a guitar<00:07:10.820> poof<00:07:11.180> bicycling<00:07:11.660> for<00:07:11.810> the<00:07:11.960> technical 00:07:12.610 --> 00:07:12.620 align:start position:0% guitar poof bicycling for the technical 00:07:12.620 --> 00:07:14.590 align:start position:0% guitar poof bicycling for the technical rider<00:07:12.980> to<00:07:13.400> come<00:07:13.640> in<00:07:13.760> that's<00:07:13.880> how<00:07:14.390> it<00:07:14.480> feels 00:07:14.590 --> 00:07:14.600 align:start position:0% rider to come in that's how it feels 00:07:14.600 --> 00:07:17.200 align:start position:0% rider to come in that's how it feels like<00:07:14.810> yes<00:07:15.190> yes<00:07:16.190> so<00:07:16.490> he's<00:07:16.700> got<00:07:16.880> commit 00:07:17.200 --> 00:07:17.210 align:start position:0% like yes yes so he's got commit 00:07:17.210 --> 00:07:19.740 align:start position:0% like yes yes so he's got commit privileges<00:07:17.690> and<00:07:17.870> so<00:07:18.050> he<00:07:18.410> just<00:07:18.890> sweeps<00:07:19.130> through 00:07:19.740 --> 00:07:19.750 align:start position:0% privileges and so he just sweeps through 00:07:19.750 --> 00:07:23.050 align:start position:0% privileges and so he just sweeps through takes<00:07:20.750> care<00:07:20.960> of<00:07:20.990> the<00:07:21.110> javadocs<00:07:21.760> diagrams<00:07:22.760> and 00:07:23.050 --> 00:07:23.060 align:start position:0% takes care of the javadocs diagrams and 00:07:23.060 --> 00:07:25.390 align:start position:0% takes care of the javadocs diagrams and the<00:07:23.240> wiki<00:07:23.480> pages<00:07:23.660> on<00:07:23.930> the<00:07:23.960> website<00:07:24.400> content 00:07:25.390 --> 00:07:25.400 align:start position:0% the wiki pages on the website content 00:07:25.400 --> 00:07:27.370 align:start position:0% the wiki pages on the website content this<00:07:25.910> is<00:07:26.000> great<00:07:26.090> so<00:07:26.450> this<00:07:26.630> is<00:07:26.780> I<00:07:26.990> think<00:07:27.020> this<00:07:27.320> is 00:07:27.370 --> 00:07:27.380 align:start position:0% this is great so this is I think this is 00:07:27.380 --> 00:07:28.930 align:start position:0% this is great so this is I think this is awesome<00:07:27.860> like<00:07:28.010> this<00:07:28.220> is<00:07:28.310> an<00:07:28.370> awesome<00:07:28.460> tip<00:07:28.760> that 00:07:28.930 --> 00:07:28.940 align:start position:0% awesome like this is an awesome tip that 00:07:28.940 --> 00:07:31.030 align:start position:0% awesome like this is an awesome tip that if<00:07:29.360> you<00:07:29.540> kind<00:07:30.080> of<00:07:30.200> invest<00:07:30.530> in<00:07:30.650> educational 00:07:31.030 --> 00:07:31.040 align:start position:0% if you kind of invest in educational 00:07:31.040 --> 00:07:32.920 align:start position:0% if you kind of invest in educational materials<00:07:31.490> yes<00:07:31.760> people<00:07:32.120> are<00:07:32.300> gonna<00:07:32.450> people 00:07:32.920 --> 00:07:32.930 align:start position:0% materials yes people are gonna people 00:07:32.930 --> 00:07:34.690 align:start position:0% materials yes people are gonna people get<00:07:33.110> not<00:07:33.230> kind<00:07:33.440> of<00:07:33.500> yeah<00:07:33.650> the<00:07:33.890> coding<00:07:34.490> of 00:07:34.690 --> 00:07:34.700 align:start position:0% get not kind of yeah the coding of 00:07:34.700 --> 00:07:36.280 align:start position:0% get not kind of yeah the coding of itself<00:07:35.030> you<00:07:35.210> can<00:07:35.240> have<00:07:35.480> great<00:07:35.720> code<00:07:35.960> but<00:07:36.170> it's 00:07:36.280 --> 00:07:36.290 align:start position:0% itself you can have great code but it's 00:07:36.290 --> 00:07:39.100 align:start position:0% itself you can have great code but it's not<00:07:36.470> accessible<00:07:36.770> usable<00:07:37.490> understandable<00:07:38.180> if 00:07:39.100 --> 00:07:39.110 align:start position:0% not accessible usable understandable if 00:07:39.110 --> 00:07:40.690 align:start position:0% not accessible usable understandable if you<00:07:39.200> don't<00:07:39.350> have<00:07:39.530> all<00:07:39.710> that<00:07:39.740> stuff<00:07:40.040> it<00:07:40.490> might 00:07:40.690 --> 00:07:40.700 align:start position:0% you don't have all that stuff it might 00:07:40.700 --> 00:07:42.100 align:start position:0% you don't have all that stuff it might as<00:07:40.760> well<00:07:40.880> not<00:07:41.000> exist<00:07:41.060> as<00:07:41.480> far<00:07:41.510> as<00:07:41.720> most<00:07:41.870> people 00:07:42.100 --> 00:07:42.110 align:start position:0% as well not exist as far as most people 00:07:42.110 --> 00:07:45.280 align:start position:0% as well not exist as far as most people are<00:07:42.170> concerned<00:07:42.440> how<00:07:43.160> much<00:07:43.400> of<00:07:44.090> external<00:07:44.960> teams 00:07:45.280 --> 00:07:45.290 align:start position:0% are concerned how much of external teams 00:07:45.290 --> 00:07:47.950 align:start position:0% are concerned how much of external teams do<00:07:45.500> you<00:07:45.590> see<00:07:45.800> kind<00:07:46.640> of<00:07:46.760> picking<00:07:47.390> this<00:07:47.510> up<00:07:47.690> and 00:07:47.950 --> 00:07:47.960 align:start position:0% do you see kind of picking this up and 00:07:47.960 --> 00:07:49.810 align:start position:0% do you see kind of picking this up and how<00:07:48.170> many<00:07:48.230> kind<00:07:48.710> of<00:07:48.800> question<00:07:49.460> do<00:07:49.610> you<00:07:49.640> see 00:07:49.810 --> 00:07:49.820 align:start position:0% how many kind of question do you see 00:07:49.820 --> 00:07:52.840 align:start position:0% how many kind of question do you see from<00:07:50.060> or<00:07:50.270> non<00:07:50.630> Netflix<00:07:51.050> people<00:07:51.850> implementing 00:07:52.840 --> 00:07:52.850 align:start position:0% from or non Netflix people implementing 00:07:52.850 --> 00:07:55.420 align:start position:0% from or non Netflix people implementing this<00:07:53.150> tag<00:07:53.420> actually<00:07:54.260> far<00:07:54.530> more<00:07:54.560> external<00:07:55.130> than 00:07:55.420 --> 00:07:55.430 align:start position:0% this tag actually far more external than 00:07:55.430 --> 00:07:58.930 align:start position:0% this tag actually far more external than internal<00:07:56.800> it's<00:07:57.800> especially<00:07:58.160> been<00:07:58.490> large<00:07:58.760> in 00:07:58.930 --> 00:07:58.940 align:start position:0% internal it's especially been large in 00:07:58.940 --> 00:08:00.940 align:start position:0% internal it's especially been large in the<00:07:59.030> android<00:07:59.330> community<00:07:59.480> mm-hmm<00:08:00.290> so<00:08:00.770> in<00:08:00.860> the 00:08:00.940 --> 00:08:00.950 align:start position:0% the android community mm-hmm so in the 00:08:00.950 --> 00:08:03.190 align:start position:0% the android community mm-hmm so in the android<00:08:01.280> community<00:08:01.660> like<00:08:02.660> there's<00:08:02.900> a<00:08:02.990> lot<00:08:03.140> of 00:08:03.190 --> 00:08:03.200 align:start position:0% android community like there's a lot of 00:08:03.200 --> 00:08:05.800 align:start position:0% android community like there's a lot of very<00:08:03.770> big<00:08:04.010> brand<00:08:04.460> names<00:08:04.610> that<00:08:05.120> the<00:08:05.660> people 00:08:05.800 --> 00:08:05.810 align:start position:0% very big brand names that the people 00:08:05.810 --> 00:08:07.480 align:start position:0% very big brand names that the people would<00:08:05.960> recognize<00:08:06.170> who<00:08:06.590> use<00:08:06.770> it<00:08:06.920> in<00:08:07.040> their<00:08:07.220> in 00:08:07.480 --> 00:08:07.490 align:start position:0% would recognize who use it in their in 00:08:07.490 --> 00:08:10.930 align:start position:0% would recognize who use it in their in their<00:08:07.550> applications<00:08:08.240> and<00:08:09.220> just<00:08:10.220> as<00:08:10.430> you<00:08:10.850> know 00:08:10.930 --> 00:08:10.940 align:start position:0% their applications and just as you know 00:08:10.940 --> 00:08:13.480 align:start position:0% their applications and just as you know as<00:08:11.060> examples<00:08:11.600> the<00:08:11.690> github<00:08:11.840> project<00:08:12.470> we've<00:08:13.340> had 00:08:13.480 --> 00:08:13.490 align:start position:0% as examples the github project we've had 00:08:13.490 --> 00:08:15.730 align:start position:0% as examples the github project we've had well<00:08:13.730> over<00:08:13.760> a<00:08:14.060> hundred<00:08:14.150> contributors<00:08:15.080> who've 00:08:15.730 --> 00:08:15.740 align:start position:0% well over a hundred contributors who've 00:08:15.740 --> 00:08:18.820 align:start position:0% well over a hundred contributors who've committed<00:08:16.010> code<00:08:16.400> to<00:08:16.640> it<00:08:17.140> there's<00:08:18.140> dozens<00:08:18.830> of 00:08:18.820 --> 00:08:18.830 align:start position:0% committed code to it there's dozens of 00:08:18.830 --> 00:08:21.340 align:start position:0% committed code to it there's dozens of people<00:08:19.070> who<00:08:19.460> have<00:08:19.820> written<00:08:20.630> blog<00:08:20.870> posts<00:08:21.290> and 00:08:21.340 --> 00:08:21.350 align:start position:0% people who have written blog posts and 00:08:21.350 --> 00:08:22.810 align:start position:0% people who have written blog posts and spoken<00:08:21.710> at<00:08:21.770> conferences<00:08:22.040> without<00:08:22.640> any 00:08:22.810 --> 00:08:22.820 align:start position:0% spoken at conferences without any 00:08:22.820 --> 00:08:24.940 align:start position:0% spoken at conferences without any instigation<00:08:23.480> from<00:08:23.660> our<00:08:23.780> Park<00:08:24.050> mm-hmm<00:08:24.620> it's 00:08:24.940 --> 00:08:24.950 align:start position:0% instigation from our Park mm-hmm it's 00:08:24.950 --> 00:08:28.870 align:start position:0% instigation from our Park mm-hmm it's got<00:08:25.480> thousands<00:08:26.480> of<00:08:26.570> stars<00:08:26.840> and<00:08:27.740> so<00:08:28.250> like<00:08:28.700> all 00:08:28.870 --> 00:08:28.880 align:start position:0% got thousands of stars and so like all 00:08:28.880 --> 00:08:31.390 align:start position:0% got thousands of stars and so like all of<00:08:29.090> that<00:08:29.300> it<00:08:29.990> then<00:08:30.170> led<00:08:30.830> a<00:08:30.860> vibrant<00:08:31.340> community 00:08:31.390 --> 00:08:31.400 align:start position:0% of that it then led a vibrant community 00:08:31.400 --> 00:08:34.020 align:start position:0% of that it then led a vibrant community on<00:08:31.850> stackoverflow<00:08:32.630> and<00:08:33.080> on<00:08:33.440> the<00:08:33.560> mailing<00:08:33.740> list 00:08:34.020 --> 00:08:34.030 align:start position:0% on stackoverflow and on the mailing list 00:08:34.030 --> 00:08:36.130 align:start position:0% on stackoverflow and on the mailing list github<00:08:35.030> issues<00:08:35.330> and<00:08:35.479> all<00:08:35.540> that<00:08:35.660> stuff<00:08:35.750> so<00:08:35.960> it's 00:08:36.130 --> 00:08:36.140 align:start position:0% github issues and all that stuff so it's 00:08:36.140 --> 00:08:37.330 align:start position:0% github issues and all that stuff so it's actually<00:08:36.260> become<00:08:36.680> a<00:08:36.890> pretty<00:08:37.130> vibrant 00:08:37.330 --> 00:08:37.340 align:start position:0% actually become a pretty vibrant 00:08:37.340 --> 00:08:39.430 align:start position:0% actually become a pretty vibrant community<00:08:37.910> so<00:08:38.510> the<00:08:38.599> local<00:08:38.810> how<00:08:38.960> do<00:08:39.020> you<00:08:39.260> manage 00:08:39.430 --> 00:08:39.440 align:start position:0% community so the local how do you manage 00:08:39.440 --> 00:08:43.390 align:start position:0% community so the local how do you manage to<00:08:39.890> support<00:08:40.310> all<00:08:40.460> this<00:08:40.990> all<00:08:41.990> I<00:08:42.050> say<00:08:42.320> I<00:08:42.349> ask<00:08:42.650> for 00:08:43.390 --> 00:08:43.400 align:start position:0% to support all this all I say I ask for 00:08:43.400 --> 00:08:46.210 align:start position:0% to support all this all I say I ask for people's<00:08:43.790> help<00:08:44.080> because<00:08:45.080> I'm<00:08:45.830> only<00:08:46.010> one 00:08:46.210 --> 00:08:46.220 align:start position:0% people's help because I'm only one 00:08:46.220 --> 00:08:47.680 align:start position:0% people's help because I'm only one person<00:08:46.250> there's<00:08:46.730> really<00:08:46.940> so<00:08:47.180> much<00:08:47.240> I<00:08:47.420> can<00:08:47.570> do 00:08:47.680 --> 00:08:47.690 align:start position:0% person there's really so much I can do 00:08:47.690 --> 00:08:50.910 align:start position:0% person there's really so much I can do and<00:08:47.930> so<00:08:48.170> it's<00:08:48.500> very<00:08:49.280> community<00:08:49.850> driven<00:08:50.060> in 00:08:50.910 --> 00:08:50.920 align:start position:0% and so it's very community driven in 00:08:50.920 --> 00:08:53.140 align:start position:0% and so it's very community driven in answering<00:08:51.920> each<00:08:52.070> other's<00:08:52.190> questions<00:08:52.520> and<00:08:53.000> so 00:08:53.140 --> 00:08:53.150 align:start position:0% answering each other's questions and so 00:08:53.150 --> 00:08:54.360 align:start position:0% answering each other's questions and so I<00:08:53.180> weigh<00:08:53.510> in<00:08:53.750> when<00:08:53.990> I 00:08:54.360 --> 00:08:54.370 align:start position:0% I weigh in when I 00:08:54.370 --> 00:08:55.860 align:start position:0% I weigh in when I when<00:08:54.760> I<00:08:54.790> can<00:08:55.089> or<00:08:55.270> when<00:08:55.390> I<00:08:55.450> see<00:08:55.660> something 00:08:55.860 --> 00:08:55.870 align:start position:0% when I can or when I see something 00:08:55.870 --> 00:08:58.260 align:start position:0% when I can or when I see something bubble<00:08:56.320> up<00:08:56.500> and<00:08:56.740> keep<00:08:57.370> can<00:08:57.790> becoming 00:08:58.260 --> 00:08:58.270 align:start position:0% bubble up and keep can becoming 00:08:58.270 --> 00:08:59.430 align:start position:0% bubble up and keep can becoming something<00:08:58.630> that<00:08:58.900> needs<00:08:59.080> a<00:08:59.140> little<00:08:59.260> more 00:08:59.430 --> 00:08:59.440 align:start position:0% something that needs a little more 00:08:59.440 --> 00:09:02.220 align:start position:0% something that needs a little more attention<00:08:59.560> but<00:09:00.100> in<00:09:00.279> general<00:09:00.720> over<00:09:01.720> the<00:09:01.839> built 00:09:02.220 --> 00:09:02.230 align:start position:0% attention but in general over the built 00:09:02.230 --> 00:09:04.590 align:start position:0% attention but in general over the built in<00:09:02.440> the<00:09:02.770> the<00:09:03.279> first<00:09:03.520> year<00:09:03.760> is<00:09:03.880> very<00:09:04.089> much<00:09:04.390> me 00:09:04.590 --> 00:09:04.600 align:start position:0% in the the first year is very much me 00:09:04.600 --> 00:09:06.930 align:start position:0% in the the first year is very much me driving<00:09:05.200> it<00:09:05.320> a<00:09:05.380> lot<00:09:05.589> in<00:09:06.160> the<00:09:06.220> last<00:09:06.310> year<00:09:06.790> and<00:09:06.820> a 00:09:06.930 --> 00:09:06.940 align:start position:0% driving it a lot in the last year and a 00:09:06.940 --> 00:09:10.380 align:start position:0% driving it a lot in the last year and a half<00:09:07.200> ish<00:09:08.200> it's<00:09:08.830> very<00:09:09.580> much<00:09:09.820> community-driven 00:09:10.380 --> 00:09:10.390 align:start position:0% half ish it's very much community-driven 00:09:10.390 --> 00:09:12.980 align:start position:0% half ish it's very much community-driven now<00:09:10.690> and<00:09:10.930> in<00:09:11.050> fact<00:09:11.350> in<00:09:11.650> the<00:09:11.770> last<00:09:11.800> six<00:09:12.310> months 00:09:12.980 --> 00:09:12.990 align:start position:0% now and in fact in the last six months 00:09:12.990 --> 00:09:15.960 align:start position:0% now and in fact in the last six months far<00:09:13.990> more<00:09:14.230> of<00:09:14.380> the<00:09:14.500> commits<00:09:14.890> the<00:09:15.250> the<00:09:15.550> code<00:09:15.760> is 00:09:15.960 --> 00:09:15.970 align:start position:0% far more of the commits the the code is 00:09:15.970 --> 00:09:17.610 align:start position:0% far more of the commits the the code is coming<00:09:16.270> from<00:09:16.540> the<00:09:16.720> community<00:09:16.870> than<00:09:17.350> it<00:09:17.470> is 00:09:17.610 --> 00:09:17.620 align:start position:0% coming from the community than it is 00:09:17.620 --> 00:09:19.710 align:start position:0% coming from the community than it is from<00:09:17.920> myself<00:09:18.190> or<00:09:18.520> anyone<00:09:18.670> at<00:09:18.850> Netflix<00:09:19.210> I<00:09:19.420> still 00:09:19.710 --> 00:09:19.720 align:start position:0% from myself or anyone at Netflix I still 00:09:19.720 --> 00:09:21.510 align:start position:0% from myself or anyone at Netflix I still check<00:09:19.930> it<00:09:20.050> out<00:09:20.140> still<00:09:20.350> by<00:09:20.500> far<00:09:20.529> the<00:09:21.040> lead 00:09:21.510 --> 00:09:21.520 align:start position:0% check it out still by far the lead 00:09:21.520 --> 00:09:23.880 align:start position:0% check it out still by far the lead commits<00:09:21.850> are<00:09:21.990> you<00:09:22.990> know<00:09:23.110> on<00:09:23.290> version<00:09:23.710> 2.x 00:09:23.880 --> 00:09:23.890 align:start position:0% commits are you know on version 2.x 00:09:23.890 --> 00:09:27.030 align:start position:0% commits are you know on version 2.x which<00:09:24.370> is<00:09:24.490> happening<00:09:24.900> David<00:09:25.900> Carnac<00:09:26.320> he 00:09:27.030 --> 00:09:27.040 align:start position:0% which is happening David Carnac he 00:09:27.040 --> 00:09:29.670 align:start position:0% which is happening David Carnac he basically<00:09:27.339> just<00:09:27.460> ported<00:09:27.940> everything<00:09:28.510> in<00:09:28.779> like 00:09:29.670 --> 00:09:29.680 align:start position:0% basically just ported everything in like 00:09:29.680 --> 00:09:32.160 align:start position:0% basically just ported everything in like three<00:09:29.950> weeks<00:09:29.980> so<00:09:30.400> on<00:09:30.970> the<00:09:31.120> 2x<00:09:31.600> per<00:09:31.750> inch<00:09:31.900> he 00:09:32.160 --> 00:09:32.170 align:start position:0% three weeks so on the 2x per inch he 00:09:32.170 --> 00:09:36.630 align:start position:0% three weeks so on the 2x per inch he will<00:09:32.320> far<00:09:32.650> and<00:09:32.770> away<00:09:32.860> be<00:09:33.220> the<00:09:33.370> lead<00:09:35.490> yes<00:09:36.490> the 00:09:36.630 --> 00:09:36.640 align:start position:0% will far and away be the lead yes the 00:09:36.640 --> 00:09:38.220 align:start position:0% will far and away be the lead yes the main<00:09:36.850> is<00:09:37.000> still<00:09:37.240> the<00:09:37.360> production<00:09:37.750> worthy<00:09:38.020> one 00:09:38.220 --> 00:09:38.230 align:start position:0% main is still the production worthy one 00:09:38.230 --> 00:09:41.130 align:start position:0% main is still the production worthy one where<00:09:38.589> we're<00:09:38.740> working<00:09:39.100> on<00:09:39.190> version<00:09:39.400> 2<00:09:39.960> and<00:09:40.960> so 00:09:41.130 --> 00:09:41.140 align:start position:0% where we're working on version 2 and so 00:09:41.140 --> 00:09:42.510 align:start position:0% where we're working on version 2 and so if<00:09:41.200> you<00:09:41.290> flip<00:09:41.560> over<00:09:41.650> to<00:09:41.800> that<00:09:42.010> and<00:09:42.220> take<00:09:42.310> a<00:09:42.339> look 00:09:42.510 --> 00:09:42.520 align:start position:0% if you flip over to that and take a look 00:09:42.520 --> 00:09:45.360 align:start position:0% if you flip over to that and take a look at<00:09:42.670> its<00:09:42.820> committer<00:09:43.120> it's<00:09:43.500> it's<00:09:44.500> all<00:09:44.740> david<00:09:45.220> car 00:09:45.360 --> 00:09:45.370 align:start position:0% at its committer it's it's all david car 00:09:45.370 --> 00:09:47.550 align:start position:0% at its committer it's it's all david car dock<00:09:45.870> we're<00:09:46.870> going<00:09:46.990> to<00:09:47.050> check<00:09:47.140> it<00:09:47.260> up<00:09:47.350> yeah 00:09:47.550 --> 00:09:47.560 align:start position:0% dock we're going to check it up yeah 00:09:47.560 --> 00:09:49.860 align:start position:0% dock we're going to check it up yeah well<00:09:48.070> so<00:09:48.610> i<00:09:48.640> think<00:09:48.940> my<00:09:49.180> last<00:09:49.420> question<00:09:49.570> will<00:09:49.839> be 00:09:49.860 --> 00:09:49.870 align:start position:0% well so i think my last question will be 00:09:49.870 --> 00:09:52.290 align:start position:0% well so i think my last question will be kind<00:09:50.410> of<00:09:50.500> this<00:09:50.800> is<00:09:50.980> a<00:09:51.220> very<00:09:51.490> interesting 00:09:52.290 --> 00:09:52.300 align:start position:0% kind of this is a very interesting 00:09:52.300 --> 00:09:55.769 align:start position:0% kind of this is a very interesting evolving<00:09:52.900> area<00:09:53.520> in<00:09:54.520> obviously<00:09:55.390> there<00:09:55.660> is<00:09:55.750> a 00:09:55.769 --> 00:09:55.779 align:start position:0% evolving area in obviously there is a 00:09:55.779 --> 00:09:58.350 align:start position:0% evolving area in obviously there is a lot<00:09:56.020> of<00:09:56.050> information<00:09:56.770> so<00:09:57.279> if<00:09:57.610> somebody<00:09:57.970> wants 00:09:58.350 --> 00:09:58.360 align:start position:0% lot of information so if somebody wants 00:09:58.360 --> 00:10:01.590 align:start position:0% lot of information so if somebody wants to<00:09:58.480> kind<00:09:58.630> of<00:09:58.779> play<00:09:59.140> with<00:09:59.230> this<00:09:59.560> right<00:10:00.600> should 00:10:01.590 --> 00:10:01.600 align:start position:0% to kind of play with this right should 00:10:01.600 --> 00:10:04.650 align:start position:0% to kind of play with this right should we<00:10:01.660> just<00:10:01.930> head<00:10:02.110> to<00:10:02.410> our<00:10:02.680> exam<00:10:03.180> repository<00:10:04.180> are 00:10:04.650 --> 00:10:04.660 align:start position:0% we just head to our exam repository are 00:10:04.660 --> 00:10:07.980 align:start position:0% we just head to our exam repository are there<00:10:05.110> kind<00:10:05.589> of<00:10:06.240> starter<00:10:07.240> projects<00:10:07.810> they're 00:10:07.980 --> 00:10:07.990 align:start position:0% there kind of starter projects they're 00:10:07.990 --> 00:10:09.420 align:start position:0% there kind of starter projects they're like<00:10:08.200> what's<00:10:08.380> a<00:10:08.470> good<00:10:08.589> entry<00:10:08.920> point<00:10:09.100> for 00:10:09.420 --> 00:10:09.430 align:start position:0% like what's a good entry point for 00:10:09.430 --> 00:10:11.070 align:start position:0% like what's a good entry point for newbies<00:10:09.790> school<00:10:10.120> kind<00:10:10.480> of<00:10:10.510> want<00:10:10.660> to<00:10:10.750> check<00:10:10.930> out 00:10:11.070 --> 00:10:11.080 align:start position:0% newbies school kind of want to check out 00:10:11.080 --> 00:10:15.030 align:start position:0% newbies school kind of want to check out the<00:10:11.230> reactive<00:10:11.560> systems<00:10:12.100> so<00:10:12.630> actually<00:10:14.040> there 00:10:15.030 --> 00:10:15.040 align:start position:0% the reactive systems so actually there 00:10:15.040 --> 00:10:17.810 align:start position:0% the reactive systems so actually there is<00:10:15.190> a<00:10:15.220> project<00:10:15.820> written<00:10:16.300> by<00:10:16.570> jophur<00:10:16.990> Hussein 00:10:17.810 --> 00:10:17.820 align:start position:0% is a project written by jophur Hussein 00:10:17.820 --> 00:10:19.980 align:start position:0% is a project written by jophur Hussein who<00:10:18.820> is<00:10:18.970> actually<00:10:19.300> the<00:10:19.360> one<00:10:19.420> who<00:10:19.570> introduced 00:10:19.980 --> 00:10:19.990 align:start position:0% who is actually the one who introduced 00:10:19.990 --> 00:10:22.860 align:start position:0% who is actually the one who introduced me<00:10:20.080> to<00:10:20.350> reactive<00:10:21.310> programming<00:10:21.490> and<00:10:21.970> it's<00:10:22.660> done 00:10:22.860 --> 00:10:22.870 align:start position:0% me to reactive programming and it's done 00:10:22.870 --> 00:10:24.630 align:start position:0% me to reactive programming and it's done in<00:10:22.990> JavaScript<00:10:23.589> so<00:10:23.680> it's<00:10:23.800> very<00:10:23.950> easy<00:10:24.279> to<00:10:24.459> get 00:10:24.630 --> 00:10:24.640 align:start position:0% in JavaScript so it's very easy to get 00:10:24.640 --> 00:10:25.890 align:start position:0% in JavaScript so it's very easy to get started<00:10:24.880> with<00:10:25.060> you<00:10:25.270> can<00:10:25.390> do<00:10:25.510> it<00:10:25.600> right<00:10:25.750> in<00:10:25.839> a 00:10:25.890 --> 00:10:25.900 align:start position:0% started with you can do it right in a 00:10:25.900 --> 00:10:29.250 align:start position:0% started with you can do it right in a browser<00:10:26.050> and<00:10:26.770> it's<00:10:27.130> at<00:10:27.400> the<00:10:27.970> github<00:10:28.570> com<00:10:28.660> / 00:10:29.250 --> 00:10:29.260 align:start position:0% browser and it's at the github com / 00:10:29.260 --> 00:10:32.850 align:start position:0% browser and it's at the github com / reactive<00:10:29.740> x<00:10:29.890> /<00:10:30.250> learn<00:10:30.580> RX<00:10:31.000> i<00:10:31.270> believe<00:10:32.080> and<00:10:32.709> it 00:10:32.850 --> 00:10:32.860 align:start position:0% reactive x / learn RX i believe and it 00:10:32.860 --> 00:10:35.760 align:start position:0% reactive x / learn RX i believe and it basically<00:10:33.040> is<00:10:33.730> a<00:10:34.529> walkthrough<00:10:35.529> in 00:10:35.760 --> 00:10:35.770 align:start position:0% basically is a walkthrough in 00:10:35.770 --> 00:10:39.810 align:start position:0% basically is a walkthrough in progressing<00:10:36.990> difficulty<00:10:37.990> and<00:10:38.260> it's<00:10:39.100> a<00:10:39.339> great 00:10:39.810 --> 00:10:39.820 align:start position:0% progressing difficulty and it's a great 00:10:39.820 --> 00:10:42.750 align:start position:0% progressing difficulty and it's a great way<00:10:39.880> to<00:10:40.750> step<00:10:41.740> into<00:10:41.920> it<00:10:42.130> and<00:10:42.220> it<00:10:42.339> starts 00:10:42.750 --> 00:10:42.760 align:start position:0% way to step into it and it starts 00:10:42.760 --> 00:10:45.810 align:start position:0% way to step into it and it starts actually<00:10:43.209> teaching<00:10:44.170> you<00:10:44.290> how<00:10:44.470> to<00:10:44.529> do<00:10:44.860> function 00:10:45.810 --> 00:10:45.820 align:start position:0% actually teaching you how to do function 00:10:45.820 --> 00:10:47.880 align:start position:0% actually teaching you how to do function composition<00:10:46.000> over<00:10:46.779> iterable<00:10:47.110> synchronously 00:10:47.880 --> 00:10:47.890 align:start position:0% composition over iterable synchronously 00:10:47.890 --> 00:10:50.970 align:start position:0% composition over iterable synchronously verbals<00:10:48.310> and<00:10:48.640> then<00:10:49.360> starts<00:10:50.020> to<00:10:50.050> flip<00:10:50.470> you<00:10:50.650> into 00:10:50.970 --> 00:10:50.980 align:start position:0% verbals and then starts to flip you into 00:10:50.980 --> 00:10:52.199 align:start position:0% verbals and then starts to flip you into showing<00:10:51.190> how<00:10:51.430> and<00:10:51.580> all<00:10:51.640> of<00:10:51.700> a<00:10:51.760> sudden<00:10:51.790> becomes 00:10:52.199 --> 00:10:52.209 align:start position:0% showing how and all of a sudden becomes 00:10:52.209 --> 00:10:54.390 align:start position:0% showing how and all of a sudden becomes a<00:10:52.360> sink<00:10:52.690> and<00:10:52.900> into<00:10:53.440> our<00:10:53.470> duels<00:10:53.860> of<00:10:54.010> each<00:10:54.160> other 00:10:54.390 --> 00:10:54.400 align:start position:0% a sink and into our duels of each other 00:10:54.400 --> 00:10:56.070 align:start position:0% a sink and into our duels of each other and<00:10:54.730> so<00:10:55.180> instead<00:10:55.420> of<00:10:55.480> trying<00:10:55.720> to<00:10:55.779> teach<00:10:55.930> you 00:10:56.070 --> 00:10:56.080 align:start position:0% and so instead of trying to teach you 00:10:56.080 --> 00:10:57.600 align:start position:0% and so instead of trying to teach you both<00:10:56.200> function<00:10:56.589> composition<00:10:56.740> in<00:10:57.250> a<00:10:57.339> sink 00:10:57.600 --> 00:10:57.610 align:start position:0% both function composition in a sink 00:10:57.610 --> 00:10:59.250 align:start position:0% both function composition in a sink running<00:10:57.700> at<00:10:57.850> the<00:10:57.910> same<00:10:58.060> time<00:10:58.270> it<00:10:58.570> starts<00:10:59.170> with 00:10:59.250 --> 00:10:59.260 align:start position:0% running at the same time it starts with 00:10:59.260 --> 00:11:01.170 align:start position:0% running at the same time it starts with function<00:10:59.620> composition<00:10:59.770> get<00:11:00.730> too<00:11:00.880> used<00:11:00.910> to 00:11:01.170 --> 00:11:01.180 align:start position:0% function composition get too used to 00:11:01.180 --> 00:11:02.850 align:start position:0% function composition get too used to things<00:11:01.420> like<00:11:01.570> map<00:11:01.810> and<00:11:02.050> flat<00:11:02.200> map<00:11:02.410> and<00:11:02.680> stuff 00:11:02.850 --> 00:11:02.860 align:start position:0% things like map and flat map and stuff 00:11:02.860 --> 00:11:04.380 align:start position:0% things like map and flat map and stuff and<00:11:03.220> then<00:11:03.339> all<00:11:03.459> of<00:11:03.490> a<00:11:03.550> sudden<00:11:03.579> flips<00:11:03.940> on<00:11:04.089> unit 00:11:04.380 --> 00:11:04.390 align:start position:0% and then all of a sudden flips on unit 00:11:04.390 --> 00:11:06.540 align:start position:0% and then all of a sudden flips on unit shows<00:11:04.600> you<00:11:04.780> wait<00:11:05.200> a<00:11:05.230> second<00:11:05.650> it's<00:11:05.740> the<00:11:06.220> exact 00:11:06.540 --> 00:11:06.550 align:start position:0% shows you wait a second it's the exact 00:11:06.550 --> 00:11:08.249 align:start position:0% shows you wait a second it's the exact same<00:11:06.579> coding<00:11:07.120> style<00:11:07.510> except<00:11:08.079> all 00:11:08.249 --> 00:11:08.259 align:start position:0% same coding style except all 00:11:08.259 --> 00:11:10.079 align:start position:0% same coding style except all son<00:11:08.439> it<00:11:08.529> just<00:11:08.559> became<00:11:08.889> a<00:11:09.040> sink<00:11:09.309> interesting<00:11:09.970> so 00:11:10.079 --> 00:11:10.089 align:start position:0% son it just became a sink interesting so 00:11:10.089 --> 00:11:13.699 align:start position:0% son it just became a sink interesting so actually<00:11:10.769> the<00:11:11.769> that<00:11:12.399> is<00:11:12.549> a<00:11:12.579> very<00:11:12.790> good<00:11:13.029> way<00:11:13.179> of 00:11:13.699 --> 00:11:13.709 align:start position:0% actually the that is a very good way of 00:11:13.709 --> 00:11:16.409 align:start position:0% actually the that is a very good way of learning<00:11:14.709> the<00:11:15.089> concepts<00:11:16.089> because<00:11:16.269> the 00:11:16.409 --> 00:11:16.419 align:start position:0% learning the concepts because the 00:11:16.419 --> 00:11:17.969 align:start position:0% learning the concepts because the concepts<00:11:16.839> that<00:11:16.929> applied<00:11:17.229> to<00:11:17.410> any<00:11:17.529> language 00:11:17.969 --> 00:11:17.979 align:start position:0% concepts that applied to any language 00:11:17.979 --> 00:11:21.719 align:start position:0% concepts that applied to any language you're<00:11:18.609> in<00:11:18.759> mm-hmm<00:11:19.389> on<00:11:19.989> the<00:11:20.199> RX<00:11:20.859> Java<00:11:21.129> side<00:11:21.399> we 00:11:21.719 --> 00:11:21.729 align:start position:0% you're in mm-hmm on the RX Java side we 00:11:21.729 --> 00:11:23.579 align:start position:0% you're in mm-hmm on the RX Java side we to<00:11:22.569> show<00:11:22.600> something<00:11:22.959> a<00:11:23.199> little<00:11:23.379> bit<00:11:23.529> more 00:11:23.579 --> 00:11:23.589 align:start position:0% to show something a little bit more 00:11:23.589 --> 00:11:27.029 align:start position:0% to show something a little bit more practical<00:11:24.339> for<00:11:24.549> people<00:11:25.289> reactive<00:11:26.289> lab<00:11:26.529> I<00:11:27.009> 0 00:11:27.029 --> 00:11:27.039 align:start position:0% practical for people reactive lab I 0 00:11:27.039 --> 00:11:30.419 align:start position:0% practical for people reactive lab I 0 points<00:11:27.729> to<00:11:27.850> a<00:11:27.879> github<00:11:28.119> repo<00:11:28.660> where<00:11:29.259> it's<00:11:29.619> kind 00:11:30.419 --> 00:11:30.429 align:start position:0% points to a github repo where it's kind 00:11:30.429 --> 00:11:32.159 align:start position:0% points to a github repo where it's kind of<00:11:30.489> demonstrates<00:11:31.029> how<00:11:31.209> we<00:11:31.269> typically<00:11:31.720> use<00:11:31.809> our 00:11:32.159 --> 00:11:32.169 align:start position:0% of demonstrates how we typically use our 00:11:32.169 --> 00:11:35.129 align:start position:0% of demonstrates how we typically use our X<00:11:32.289> job<00:11:32.499> at<00:11:32.679> Netflix<00:11:33.100> which<00:11:33.729> is<00:11:33.970> incoming<00:11:34.929> web 00:11:35.129 --> 00:11:35.139 align:start position:0% X job at Netflix which is incoming web 00:11:35.139 --> 00:11:36.929 align:start position:0% X job at Netflix which is incoming web services<00:11:35.649> that<00:11:35.859> compose<00:11:36.160> multiple<00:11:36.579> back<00:11:36.729> end 00:11:36.929 --> 00:11:36.939 align:start position:0% services that compose multiple back end 00:11:36.939 --> 00:11:38.759 align:start position:0% services that compose multiple back end web<00:11:37.059> services<00:11:37.539> and<00:11:38.049> it's<00:11:38.289> something<00:11:38.619> that<00:11:38.739> you 00:11:38.759 --> 00:11:38.769 align:start position:0% web services and it's something that you 00:11:38.769 --> 00:11:41.159 align:start position:0% web services and it's something that you can<00:11:38.949> actually<00:11:39.100> launch<00:11:39.429> on<00:11:39.609> your<00:11:39.729> laptop<00:11:40.169> it's 00:11:41.159 --> 00:11:41.169 align:start position:0% can actually launch on your laptop it's 00:11:41.169 --> 00:11:43.289 align:start position:0% can actually launch on your laptop it's got<00:11:41.350> like<00:11:41.499> eight<00:11:41.679> microservices<00:11:42.459> running<00:11:42.819> hmm 00:11:43.289 --> 00:11:43.299 align:start position:0% got like eight microservices running hmm 00:11:43.299 --> 00:11:45.029 align:start position:0% got like eight microservices running hmm and<00:11:43.449> shows<00:11:43.809> all<00:11:43.989> the<00:11:44.019> i/o<00:11:44.259> between<00:11:44.769> them<00:11:44.949> and 00:11:45.029 --> 00:11:45.039 align:start position:0% and shows all the i/o between them and 00:11:45.039 --> 00:11:47.999 align:start position:0% and shows all the i/o between them and composition<00:11:45.609> so<00:11:45.910> reactive<00:11:46.660> love<00:11:46.899> do<00:11:47.379> is<00:11:47.589> a 00:11:47.999 --> 00:11:48.009 align:start position:0% composition so reactive love do is a 00:11:48.009 --> 00:11:50.129 align:start position:0% composition so reactive love do is a good<00:11:48.309> one<00:11:48.489> for<00:11:48.669> the<00:11:48.789> Java<00:11:49.299> side<00:11:49.600> and<00:11:49.869> showing 00:11:50.129 --> 00:11:50.139 align:start position:0% good one for the Java side and showing 00:11:50.139 --> 00:11:51.449 align:start position:0% good one for the Java side and showing how<00:11:50.229> it<00:11:50.289> fits<00:11:50.470> into<00:11:50.619> more<00:11:50.799> real-world<00:11:51.009> use 00:11:51.449 --> 00:11:51.459 align:start position:0% how it fits into more real-world use 00:11:51.459 --> 00:11:53.340 align:start position:0% how it fits into more real-world use this<00:11:51.910> is<00:11:51.999> exciting<00:11:52.389> so<00:11:52.569> thank<00:11:52.959> you<00:11:53.049> very<00:11:53.079> much 00:11:53.340 --> 00:11:53.350 align:start position:0% this is exciting so thank you very much 00:11:53.350 --> 00:11:54.689 align:start position:0% this is exciting so thank you very much for<00:11:53.379> sharing<00:11:53.499> this<00:11:53.949> we<00:11:54.220> are<00:11:54.339> looking<00:11:54.429> forward 00:11:54.689 --> 00:11:54.699 align:start position:0% for sharing this we are looking forward 00:11:54.699 --> 00:11:56.189 align:start position:0% for sharing this we are looking forward to<00:11:54.879> a<00:11:54.910> talk<00:11:55.149> and<00:11:55.359> we<00:11:55.509> are<00:11:55.569> looking<00:11:55.839> forward<00:11:56.079> to 00:11:56.189 --> 00:11:56.199 align:start position:0% to a talk and we are looking forward to 00:11:56.199 --> 00:11:58.229 align:start position:0% to a talk and we are looking forward to kind<00:11:56.379> of<00:11:56.439> following<00:11:56.769> their<00:11:57.639> their<00:11:58.029> ex 00:11:58.229 --> 00:11:58.239 align:start position:0% kind of following their their ex 00:11:58.239 --> 00:12:08.070 align:start position:0% kind of following their their ex progress<00:11:58.689> at<00:11:58.809> Netflix<00:11:59.109> thank<00:11:59.410> you<00:11:59.529> that's<00:11:59.829> one 00:12:08.070 --> 00:12:08.080 align:start position:0% 00:12:08.080 --> 00:12:10.140 align:start position:0% you