WEBVTT Kind: captions Language: en 00:00:13.049 --> 00:00:15.539 align:start position:0% poor<00:00:14.049> body<00:00:14.350> I'm<00:00:14.650> electric<00:00:15.070> rubber<00:00:15.250> of<00:00:15.430> the 00:00:15.539 --> 00:00:15.549 align:start position:0% poor body I'm electric rubber of the 00:00:15.549 --> 00:00:17.760 align:start position:0% poor body I'm electric rubber of the organizer<00:00:16.000> of<00:00:16.119> excess<00:00:16.480> color<00:00:16.690> here<00:00:17.410> are<00:00:17.560> on 00:00:17.760 --> 00:00:17.770 align:start position:0% organizer of excess color here are on 00:00:17.770 --> 00:00:20.579 align:start position:0% organizer of excess color here are on location<00:00:17.890> at<00:00:18.699> fauna<00:00:19.060> and<00:00:19.390> look<00:00:19.420> at<00:00:20.259> just<00:00:20.470> for 00:00:20.579 --> 00:00:20.589 align:start position:0% location at fauna and look at just for 00:00:20.589 --> 00:00:22.560 align:start position:0% location at fauna and look at just for the<00:00:20.650> panel<00:00:20.980> infrastructure<00:00:21.880> after<00:00:22.390> dinner 00:00:22.560 --> 00:00:22.570 align:start position:0% the panel infrastructure after dinner 00:00:22.570 --> 00:00:25.769 align:start position:0% the panel infrastructure after dinner and<00:00:22.929> who<00:00:23.560> was<00:00:24.099> a<00:00:24.429> mark<00:00:24.759> mcbride<00:00:24.910> from<00:00:25.269> turbine 00:00:25.769 --> 00:00:25.779 align:start position:0% and who was a mark mcbride from turbine 00:00:25.779 --> 00:00:28.829 align:start position:0% and who was a mark mcbride from turbine hello<00:00:26.400> what<00:00:27.400> is<00:00:27.519> the<00:00:27.609> current<00:00:27.730> battle<00:00:27.970> I'm 00:00:28.829 --> 00:00:28.839 align:start position:0% hello what is the current battle I'm 00:00:28.839 --> 00:00:31.140 align:start position:0% hello what is the current battle I'm currently<00:00:29.259> CEO<00:00:29.529> and<00:00:30.039> co-founder<00:00:30.189> of<00:00:30.550> turbine 00:00:31.140 --> 00:00:31.150 align:start position:0% currently CEO and co-founder of turbine 00:00:31.150 --> 00:00:33.510 align:start position:0% currently CEO and co-founder of turbine labs<00:00:31.329> and<00:00:31.660> what<00:00:31.900> does<00:00:32.020> our<00:00:32.140> lives<00:00:32.439> so<00:00:33.220> turbine 00:00:33.510 --> 00:00:33.520 align:start position:0% labs and what does our lives so turbine 00:00:33.520 --> 00:00:35.970 align:start position:0% labs and what does our lives so turbine labs<00:00:33.730> is<00:00:34.120> a<00:00:34.660> product<00:00:35.170> that<00:00:35.350> helps<00:00:35.590> you<00:00:35.770> balance 00:00:35.970 --> 00:00:35.980 align:start position:0% labs is a product that helps you balance 00:00:35.980 --> 00:00:37.889 align:start position:0% labs is a product that helps you balance the<00:00:36.460> tension<00:00:36.760> between<00:00:36.910> iterating<00:00:37.750> your 00:00:37.889 --> 00:00:37.899 align:start position:0% the tension between iterating your 00:00:37.899 --> 00:00:39.660 align:start position:0% the tension between iterating your infrastructure<00:00:38.199> quickly<00:00:38.770> and<00:00:39.039> maintaining<00:00:39.550> a 00:00:39.660 --> 00:00:39.670 align:start position:0% infrastructure quickly and maintaining a 00:00:39.670 --> 00:00:42.299 align:start position:0% infrastructure quickly and maintaining a stable<00:00:39.910> customer<00:00:40.480> experience<00:00:40.930> so<00:00:41.739> we<00:00:41.859> built<00:00:42.039> a 00:00:42.299 --> 00:00:42.309 align:start position:0% stable customer experience so we built a 00:00:42.309 --> 00:00:44.580 align:start position:0% stable customer experience so we built a reverse<00:00:42.789> proxy<00:00:43.270> and<00:00:43.660> a<00:00:43.930> modern<00:00:44.230> management 00:00:44.580 --> 00:00:44.590 align:start position:0% reverse proxy and a modern management 00:00:44.590 --> 00:00:48.270 align:start position:0% reverse proxy and a modern management plane<00:00:45.039> to<00:00:46.000> allow<00:00:46.210> you<00:00:46.270> to<00:00:46.510> do<00:00:46.660> a<00:00:47.079> lot<00:00:47.680> of<00:00:47.710> sort 00:00:48.270 --> 00:00:48.280 align:start position:0% plane to allow you to do a lot of sort 00:00:48.280 --> 00:00:50.670 align:start position:0% plane to allow you to do a lot of sort of<00:00:48.370> modern<00:00:48.670> release<00:00:49.000> practices<00:00:49.559> testing<00:00:50.559> and 00:00:50.670 --> 00:00:50.680 align:start position:0% of modern release practices testing and 00:00:50.680 --> 00:00:52.229 align:start position:0% of modern release practices testing and production<00:00:50.800> Bluegreen<00:00:51.430> deploys<00:00:51.789> Canaries 00:00:52.229 --> 00:00:52.239 align:start position:0% production Bluegreen deploys Canaries 00:00:52.239 --> 00:00:54.840 align:start position:0% production Bluegreen deploys Canaries etc<00:00:52.690> in<00:00:52.899> a<00:00:53.350> way<00:00:53.500> that's<00:00:53.829> seamless<00:00:54.489> and<00:00:54.670> fits 00:00:54.840 --> 00:00:54.850 align:start position:0% etc in a way that's seamless and fits 00:00:54.850 --> 00:00:58.200 align:start position:0% etc in a way that's seamless and fits into<00:00:55.000> whatever<00:00:55.210> stack<00:00:55.570> you<00:00:55.780> have<00:00:55.960> mm-hmm<00:00:57.210> so 00:00:58.200 --> 00:00:58.210 align:start position:0% into whatever stack you have mm-hmm so 00:00:58.210 --> 00:00:59.930 align:start position:0% into whatever stack you have mm-hmm so it's<00:00:58.420> just<00:00:58.510> the<00:00:58.629> where<00:00:58.899> of<00:00:58.929> several<00:00:59.440> kind<00:00:59.800> of 00:00:59.930 --> 00:00:59.940 align:start position:0% it's just the where of several kind of 00:00:59.940 --> 00:01:02.369 align:start position:0% it's just the where of several kind of infrastructure<00:01:00.940> start<00:01:01.690> up<00:01:01.839> in<00:01:01.870> the<00:01:02.019> service 00:01:02.369 --> 00:01:02.379 align:start position:0% infrastructure start up in the service 00:01:02.379 --> 00:01:05.460 align:start position:0% infrastructure start up in the service yes<00:01:02.890> our<00:01:03.339> house<00:01:03.519> of<00:01:03.730> skyliner<00:01:04.150> and<00:01:04.570> lower<00:01:05.110> rent 00:01:05.460 --> 00:01:05.470 align:start position:0% yes our house of skyliner and lower rent 00:01:05.470 --> 00:01:07.380 align:start position:0% yes our house of skyliner and lower rent works<00:01:05.680> and<00:01:06.250> I<00:01:06.310> think<00:01:06.370> people<00:01:06.670> want<00:01:07.030> from 00:01:07.380 --> 00:01:07.390 align:start position:0% works and I think people want from 00:01:07.390 --> 00:01:09.210 align:start position:0% works and I think people want from different<00:01:07.690> angles<00:01:07.930> I<00:01:08.020> want<00:01:08.170> to<00:01:08.260> give<00:01:08.470> you<00:01:08.500> yes 00:01:09.210 --> 00:01:09.220 align:start position:0% different angles I want to give you yes 00:01:09.220 --> 00:01:13.140 align:start position:0% different angles I want to give you yes sure<00:01:09.610> the<00:01:09.880> whole<00:01:10.440> focus<00:01:11.440> on<00:01:11.560> structure<00:01:11.980> and<00:01:12.940> so 00:01:13.140 --> 00:01:13.150 align:start position:0% sure the whole focus on structure and so 00:01:13.150 --> 00:01:15.120 align:start position:0% sure the whole focus on structure and so as<00:01:13.540> I<00:01:13.660> think<00:01:13.870> that<00:01:13.990> is<00:01:14.140> that<00:01:14.290> developers<00:01:14.620> will 00:01:15.120 --> 00:01:15.130 align:start position:0% as I think that is that developers will 00:01:15.130 --> 00:01:17.010 align:start position:0% as I think that is that developers will just<00:01:15.460> you<00:01:15.610> know<00:01:15.730> pushed<00:01:16.060> up<00:01:16.210> to<00:01:16.390> github<00:01:16.570> rate 00:01:17.010 --> 00:01:17.020 align:start position:0% just you know pushed up to github rate 00:01:17.020 --> 00:01:19.770 align:start position:0% just you know pushed up to github rate as<00:01:17.230> a<00:01:17.410> magical<00:01:17.710> happen<00:01:18.130> so<00:01:18.970> what<00:01:19.180> is<00:01:19.210> kind<00:01:19.690> of 00:01:19.770 --> 00:01:19.780 align:start position:0% as a magical happen so what is kind of 00:01:19.780 --> 00:01:21.990 align:start position:0% as a magical happen so what is kind of your<00:01:19.990> specific<00:01:20.440> taken<00:01:20.710> last<00:01:20.800> year<00:01:20.920> so<00:01:21.580> I<00:01:21.610> think 00:01:21.990 --> 00:01:22.000 align:start position:0% your specific taken last year so I think 00:01:22.000 --> 00:01:23.790 align:start position:0% your specific taken last year so I think skyliner<00:01:22.420> is<00:01:22.570> great<00:01:22.780> we<00:01:22.990> followed<00:01:23.560> their 00:01:23.790 --> 00:01:23.800 align:start position:0% skyliner is great we followed their 00:01:23.800 --> 00:01:25.770 align:start position:0% skyliner is great we followed their trajectory<00:01:24.250> pretty<00:01:24.460> closely<00:01:24.640> and<00:01:25.150> I<00:01:25.510> think 00:01:25.770 --> 00:01:25.780 align:start position:0% trajectory pretty closely and I think 00:01:25.780 --> 00:01:28.320 align:start position:0% trajectory pretty closely and I think they're<00:01:25.990> really<00:01:26.620> good<00:01:27.430> at<00:01:27.670> getting<00:01:27.940> you<00:01:27.970> from 00:01:28.320 --> 00:01:28.330 align:start position:0% they're really good at getting you from 00:01:28.330 --> 00:01:30.060 align:start position:0% they're really good at getting you from like<00:01:28.540> a<00:01:28.570> raw<00:01:28.840> github<00:01:29.230> repository<00:01:29.800> to 00:01:30.060 --> 00:01:30.070 align:start position:0% like a raw github repository to 00:01:30.070 --> 00:01:32.040 align:start position:0% like a raw github repository to something<00:01:30.430> deployed<00:01:30.760> in<00:01:30.910> production<00:01:31.330> as<00:01:31.630> a<00:01:31.660> v1 00:01:32.040 --> 00:01:32.050 align:start position:0% something deployed in production as a v1 00:01:32.050 --> 00:01:34.470 align:start position:0% something deployed in production as a v1 and<00:01:32.890> I<00:01:33.010> think<00:01:33.310> you<00:01:33.640> know<00:01:33.760> they're<00:01:34.000> they're 00:01:34.470 --> 00:01:34.480 align:start position:0% and I think you know they're they're 00:01:34.480 --> 00:01:35.850 align:start position:0% and I think you know they're they're offering<00:01:34.780> a<00:01:34.930> lot<00:01:35.080> of<00:01:35.260> just<00:01:35.560> ops 00:01:35.850 --> 00:01:35.860 align:start position:0% offering a lot of just ops 00:01:35.860 --> 00:01:37.920 align:start position:0% offering a lot of just ops out-of-the-box<00:01:36.490> best<00:01:36.970> practices<00:01:37.480> honed<00:01:37.720> at 00:01:37.920 --> 00:01:37.930 align:start position:0% out-of-the-box best practices honed at 00:01:37.930 --> 00:01:42.060 align:start position:0% out-of-the-box best practices honed at stripe<00:01:38.310> and<00:01:39.310> Yammer<00:01:40.210> and<00:01:40.330> other<00:01:40.600> places<00:01:41.070> what 00:01:42.060 --> 00:01:42.070 align:start position:0% stripe and Yammer and other places what 00:01:42.070 --> 00:01:43.110 align:start position:0% stripe and Yammer and other places what we're<00:01:42.250> looking<00:01:42.370> at<00:01:42.580> is<00:01:42.700> really<00:01:42.820> for<00:01:43.090> people 00:01:43.110 --> 00:01:43.120 align:start position:0% we're looking at is really for people 00:01:43.120 --> 00:01:44.370 align:start position:0% we're looking at is really for people who<00:01:43.360> already<00:01:43.390> have<00:01:43.600> it<00:01:43.870> be<00:01:43.960> one<00:01:44.140> out<00:01:44.260> in 00:01:44.370 --> 00:01:44.380 align:start position:0% who already have it be one out in 00:01:44.380 --> 00:01:46.740 align:start position:0% who already have it be one out in production<00:01:44.800> when<00:01:45.670> they<00:01:45.790> reach<00:01:46.000> the<00:01:46.240> end<00:01:46.450> of 00:01:46.740 --> 00:01:46.750 align:start position:0% production when they reach the end of 00:01:46.750 --> 00:01:48.300 align:start position:0% production when they reach the end of the<00:01:46.900> natural<00:01:47.080> life<00:01:47.440> of<00:01:47.620> that<00:01:47.710> architecture 00:01:48.300 --> 00:01:48.310 align:start position:0% the natural life of that architecture 00:01:48.310 --> 00:01:50.610 align:start position:0% the natural life of that architecture how<00:01:48.760> do<00:01:48.820> they<00:01:49.000> move<00:01:49.120> to<00:01:49.270> what's<00:01:49.420> next<00:01:49.840> and<00:01:50.380> so 00:01:50.610 --> 00:01:50.620 align:start position:0% how do they move to what's next and so 00:01:50.620 --> 00:01:52.320 align:start position:0% how do they move to what's next and so you<00:01:51.100> know<00:01:51.130> microservices<00:01:51.850> are<00:01:52.000> a<00:01:52.030> big<00:01:52.150> thing 00:01:52.320 --> 00:01:52.330 align:start position:0% you know microservices are a big thing 00:01:52.330 --> 00:01:54.210 align:start position:0% you know microservices are a big thing now<00:01:52.510> a<00:01:52.900> lot<00:01:53.200> of<00:01:53.230> people<00:01:53.320> are<00:01:53.560> looking<00:01:53.710> to<00:01:54.010> move 00:01:54.210 --> 00:01:54.220 align:start position:0% now a lot of people are looking to move 00:01:54.220 --> 00:01:55.590 align:start position:0% now a lot of people are looking to move from<00:01:54.490> what<00:01:54.670> they<00:01:54.760> have<00:01:54.910> to<00:01:55.120> Cooper<00:01:55.360> Nettie's 00:01:55.590 --> 00:01:55.600 align:start position:0% from what they have to Cooper Nettie's 00:01:55.600 --> 00:01:57.750 align:start position:0% from what they have to Cooper Nettie's or<00:01:55.720> tomatoes<00:01:56.110> but<00:01:57.010> none<00:01:57.250> of<00:01:57.370> those<00:01:57.430> companies 00:01:57.750 --> 00:01:57.760 align:start position:0% or tomatoes but none of those companies 00:01:57.760 --> 00:01:59.550 align:start position:0% or tomatoes but none of those companies really<00:01:58.090> have<00:01:58.300> a<00:01:58.330> story<00:01:58.660> for<00:01:58.780> how<00:01:59.140> you<00:01:59.200> move 00:01:59.550 --> 00:01:59.560 align:start position:0% really have a story for how you move 00:01:59.560 --> 00:02:00.990 align:start position:0% really have a story for how you move from<00:01:59.770> what<00:01:59.950> you<00:02:00.070> have<00:02:00.220> today<00:02:00.310> into<00:02:00.850> that 00:02:00.990 --> 00:02:01.000 align:start position:0% from what you have today into that 00:02:01.000 --> 00:02:03.660 align:start position:0% from what you have today into that system<00:02:01.240> and<00:02:02.110> so<00:02:02.470> by<00:02:02.590> putting<00:02:02.770> the<00:02:02.980> proxy<00:02:03.370> is<00:02:03.550> an 00:02:03.660 --> 00:02:03.670 align:start position:0% system and so by putting the proxy is an 00:02:03.670 --> 00:02:05.490 align:start position:0% system and so by putting the proxy is an indirection<00:02:03.940> layer<00:02:04.360> between<00:02:04.630> your<00:02:05.020> customers 00:02:05.490 --> 00:02:05.500 align:start position:0% indirection layer between your customers 00:02:05.500 --> 00:02:07.110 align:start position:0% indirection layer between your customers and<00:02:05.530> their<00:02:05.710> experience<00:02:06.250> and<00:02:06.490> your 00:02:07.110 --> 00:02:07.120 align:start position:0% and their experience and your 00:02:07.120 --> 00:02:08.580 align:start position:0% and their experience and your infrastructure<00:02:07.540> you<00:02:07.840> allow<00:02:08.140> yourself<00:02:08.319> more 00:02:08.580 --> 00:02:08.590 align:start position:0% infrastructure you allow yourself more 00:02:08.590 --> 00:02:10.600 align:start position:0% infrastructure you allow yourself more flexibility<00:02:09.429> to<00:02:09.580> switch<00:02:09.789> that<00:02:09.970> up 00:02:10.600 --> 00:02:10.610 align:start position:0% flexibility to switch that up 00:02:10.610 --> 00:02:12.880 align:start position:0% flexibility to switch that up hmm<00:02:11.030> so<00:02:11.510> you<00:02:11.990> know<00:02:12.080> talking<00:02:12.290> over<00:02:12.590> with<00:02:12.770> some 00:02:12.880 --> 00:02:12.890 align:start position:0% hmm so you know talking over with some 00:02:12.890 --> 00:02:14.770 align:start position:0% hmm so you know talking over with some of<00:02:12.980> the<00:02:13.040> Skyliner<00:02:13.370> folks<00:02:13.640> there's<00:02:14.420> this<00:02:14.600> kind 00:02:14.770 --> 00:02:14.780 align:start position:0% of the Skyliner folks there's this kind 00:02:14.780 --> 00:02:17.170 align:start position:0% of the Skyliner folks there's this kind of<00:02:14.870> get<00:02:15.110> you<00:02:15.200> to<00:02:15.290> be<00:02:15.440> one<00:02:15.700> ours<00:02:16.700> is<00:02:16.850> get<00:02:17.060> you 00:02:17.170 --> 00:02:17.180 align:start position:0% of get you to be one ours is get you 00:02:17.180 --> 00:02:20.320 align:start position:0% of get you to be one ours is get you from<00:02:17.330> v1<00:02:17.660> to<00:02:17.690> v2<00:02:18.010> interesting<00:02:19.010> I<00:02:19.310> want<00:02:19.970> to<00:02:20.060> come 00:02:20.320 --> 00:02:20.330 align:start position:0% from v1 to v2 interesting I want to come 00:02:20.330 --> 00:02:23.290 align:start position:0% from v1 to v2 interesting I want to come the<00:02:20.450> thing<00:02:20.810> to<00:02:20.900> be<00:02:20.960> compiled<00:02:21.610> I<00:02:22.610> think<00:02:23.060> right 00:02:23.290 --> 00:02:23.300 align:start position:0% the thing to be compiled I think right 00:02:23.300 --> 00:02:24.940 align:start position:0% the thing to be compiled I think right now<00:02:23.480> Skyliners<00:02:24.080> opinionated<00:02:24.530> enough<00:02:24.830> it 00:02:24.940 --> 00:02:24.950 align:start position:0% now Skyliners opinionated enough it 00:02:24.950 --> 00:02:27.760 align:start position:0% now Skyliners opinionated enough it would<00:02:25.040> be<00:02:25.130> difficult<00:02:25.960> and<00:02:26.960> doesn't<00:02:27.320> fit<00:02:27.500> like 00:02:27.760 --> 00:02:27.770 align:start position:0% would be difficult and doesn't fit like 00:02:27.770 --> 00:02:29.470 align:start position:0% would be difficult and doesn't fit like seamlessly<00:02:28.340> into<00:02:28.550> their<00:02:28.700> into<00:02:29.090> their<00:02:29.210> stack 00:02:29.470 --> 00:02:29.480 align:start position:0% seamlessly into their into their stack 00:02:29.480 --> 00:02:31.810 align:start position:0% seamlessly into their into their stack because<00:02:29.720> they're<00:02:30.230> they're<00:02:30.980> using<00:02:31.340> docker<00:02:31.580> as 00:02:31.810 --> 00:02:31.820 align:start position:0% because they're they're using docker as 00:02:31.820 --> 00:02:33.880 align:start position:0% because they're they're using docker as a<00:02:31.850> unit<00:02:32.150> of<00:02:32.210> deployment<00:02:33.050> but<00:02:33.380> I<00:02:33.410> believe 00:02:33.880 --> 00:02:33.890 align:start position:0% a unit of deployment but I believe 00:02:33.890 --> 00:02:36.460 align:start position:0% a unit of deployment but I believe they're<00:02:34.190> fairly<00:02:34.400> opinionated<00:02:34.700> with<00:02:35.510> the<00:02:35.810> sort 00:02:36.460 --> 00:02:36.470 align:start position:0% they're fairly opinionated with the sort 00:02:36.470 --> 00:02:38.710 align:start position:0% they're fairly opinionated with the sort of<00:02:36.620> ancillary<00:02:37.310> stuff<00:02:37.640> they<00:02:37.760> do<00:02:37.820> around<00:02:38.060> ec2<00:02:38.510> to 00:02:38.710 --> 00:02:38.720 align:start position:0% of ancillary stuff they do around ec2 to 00:02:38.720 --> 00:02:41.020 align:start position:0% of ancillary stuff they do around ec2 to get<00:02:38.840> a<00:02:38.870> nice<00:02:39.080> stable<00:02:39.470> or<00:02:39.920> is<00:02:40.160> AWS<00:02:40.700> a<00:02:40.730> nice 00:02:41.020 --> 00:02:41.030 align:start position:0% get a nice stable or is AWS a nice 00:02:41.030 --> 00:02:43.780 align:start position:0% get a nice stable or is AWS a nice stable<00:02:41.300> operational<00:02:41.900> platform<00:02:42.370> I<00:02:43.370> think<00:02:43.730> in 00:02:43.780 --> 00:02:43.790 align:start position:0% stable operational platform I think in 00:02:43.790 --> 00:02:45.340 align:start position:0% stable operational platform I think in the<00:02:43.880> future<00:02:43.910> there<00:02:44.510> are<00:02:44.570> things<00:02:44.900> we<00:02:45.050> can<00:02:45.080> do 00:02:45.340 --> 00:02:45.350 align:start position:0% the future there are things we can do 00:02:45.350 --> 00:02:49.330 align:start position:0% the future there are things we can do that<00:02:45.620> probably<00:02:45.800> work<00:02:46.190> complimentary<00:02:47.030> Lee<00:02:48.340> in 00:02:49.330 --> 00:02:49.340 align:start position:0% that probably work complimentary Lee in 00:02:49.340 --> 00:02:51.400 align:start position:0% that probably work complimentary Lee in a<00:02:49.400> complementary<00:02:49.760> fashion<00:02:50.060> with<00:02:50.390> them<00:02:50.540> but 00:02:51.400 --> 00:02:51.410 align:start position:0% a complementary fashion with them but 00:02:51.410 --> 00:02:52.840 align:start position:0% a complementary fashion with them but right<00:02:51.500> now<00:02:51.560> like<00:02:51.980> our<00:02:52.100> focus<00:02:52.400> is<00:02:52.520> people<00:02:52.760> who 00:02:52.840 --> 00:02:52.850 align:start position:0% right now like our focus is people who 00:02:52.850 --> 00:02:54.850 align:start position:0% right now like our focus is people who are<00:02:52.940> kind<00:02:53.120> of<00:02:53.150> later<00:02:53.390> in<00:02:53.600> life<00:02:53.860> engineering 00:02:54.850 --> 00:02:54.860 align:start position:0% are kind of later in life engineering 00:02:54.860 --> 00:02:57.130 align:start position:0% are kind of later in life engineering wives<00:02:55.070> and<00:02:55.250> skyliner<00:02:55.640> is<00:02:55.880> well<00:02:56.330> call<00:02:56.690> is<00:02:56.900> this 00:02:57.130 --> 00:02:57.140 align:start position:0% wives and skyliner is well call is this 00:02:57.140 --> 00:02:59.410 align:start position:0% wives and skyliner is well call is this one<00:02:57.290> form<00:02:57.590> of<00:02:57.680> goondas<00:02:58.070> doing<00:02:58.280> so<00:02:58.910> the<00:02:59.000> buoyant 00:02:59.410 --> 00:02:59.420 align:start position:0% one form of goondas doing so the buoyant 00:02:59.420 --> 00:03:02.199 align:start position:0% one form of goondas doing so the buoyant is<00:02:59.480> really<00:02:59.690> focusing<00:03:00.170> on<00:03:00.440> our<00:03:00.739> PC<00:03:01.100> and<00:03:01.580> making 00:03:02.199 --> 00:03:02.209 align:start position:0% is really focusing on our PC and making 00:03:02.209 --> 00:03:04.600 align:start position:0% is really focusing on our PC and making those<00:03:02.390> deep<00:03:02.750> service<00:03:03.320> stacks<00:03:03.770> work 00:03:04.600 --> 00:03:04.610 align:start position:0% those deep service stacks work 00:03:04.610 --> 00:03:05.979 align:start position:0% those deep service stacks work effectively<00:03:05.090> and<00:03:05.420> a<00:03:05.480> Twitter<00:03:05.690> that<00:03:05.840> was<00:03:05.959> a 00:03:05.979 --> 00:03:05.989 align:start position:0% effectively and a Twitter that was a 00:03:05.989 --> 00:03:09.130 align:start position:0% effectively and a Twitter that was a huge<00:03:06.230> deal<00:03:06.970> you<00:03:07.970> know<00:03:08.120> as<00:03:08.270> I<00:03:08.600> think<00:03:08.780> William<00:03:09.050> in 00:03:09.130 --> 00:03:09.140 align:start position:0% huge deal you know as I think William in 00:03:09.140 --> 00:03:11.050 align:start position:0% huge deal you know as I think William in the<00:03:09.230> buoyant<00:03:09.680> literature<00:03:09.980> shows<00:03:10.310> once<00:03:10.910> you 00:03:11.050 --> 00:03:11.060 align:start position:0% the buoyant literature shows once you 00:03:11.060 --> 00:03:13.380 align:start position:0% the buoyant literature shows once you have<00:03:11.270> a<00:03:11.690> chain<00:03:12.020> where<00:03:12.260> there's<00:03:12.410> 10<00:03:12.650> RPC<00:03:13.040> calls 00:03:13.380 --> 00:03:13.390 align:start position:0% have a chain where there's 10 RPC calls 00:03:13.390 --> 00:03:15.430 align:start position:0% have a chain where there's 10 RPC calls failures<00:03:14.390> on<00:03:14.540> that<00:03:14.690> become<00:03:14.930> much<00:03:15.110> much<00:03:15.260> more 00:03:15.430 --> 00:03:15.440 align:start position:0% failures on that become much much more 00:03:15.440 --> 00:03:16.810 align:start position:0% failures on that become much much more likely<00:03:15.650> time<00:03:16.130> out<00:03:16.250> to<00:03:16.370> harder<00:03:16.580> to<00:03:16.670> manage 00:03:16.810 --> 00:03:16.820 align:start position:0% likely time out to harder to manage 00:03:16.820 --> 00:03:18.580 align:start position:0% likely time out to harder to manage deadlines<00:03:17.540> are<00:03:17.690> harder<00:03:17.870> to<00:03:17.900> manage<00:03:18.080> circuit 00:03:18.580 --> 00:03:18.590 align:start position:0% deadlines are harder to manage circuit 00:03:18.590 --> 00:03:20.140 align:start position:0% deadlines are harder to manage circuit breakers<00:03:18.860> retries<00:03:19.280> that's<00:03:19.549> all<00:03:19.700> that's<00:03:20.030> all 00:03:20.140 --> 00:03:20.150 align:start position:0% breakers retries that's all that's all 00:03:20.150 --> 00:03:23.289 align:start position:0% breakers retries that's all that's all really<00:03:20.360> difficult<00:03:21.730> we're<00:03:22.730> focused<00:03:22.850> more<00:03:23.180> at 00:03:23.289 --> 00:03:23.299 align:start position:0% really difficult we're focused more at 00:03:23.299 --> 00:03:25.240 align:start position:0% really difficult we're focused more at the<00:03:23.390> edge<00:03:23.540> and<00:03:23.959> allowing<00:03:24.410> you<00:03:24.560> to<00:03:24.799> mutate 00:03:25.240 --> 00:03:25.250 align:start position:0% the edge and allowing you to mutate 00:03:25.250 --> 00:03:26.949 align:start position:0% the edge and allowing you to mutate infrastructure<00:03:26.030> and<00:03:26.150> modulate<00:03:26.540> you<00:03:26.780> know<00:03:26.840> the 00:03:26.949 --> 00:03:26.959 align:start position:0% infrastructure and modulate you know the 00:03:26.959 --> 00:03:28.750 align:start position:0% infrastructure and modulate you know the deployment<00:03:27.530> topology<00:03:28.010> of<00:03:28.040> your<00:03:28.220> application 00:03:28.750 --> 00:03:28.760 align:start position:0% deployment topology of your application 00:03:28.760 --> 00:03:31.300 align:start position:0% deployment topology of your application in<00:03:29.209> a<00:03:29.570> way<00:03:29.690> that's<00:03:29.900> flexible<00:03:30.080> and<00:03:30.620> is<00:03:31.100> really 00:03:31.300 --> 00:03:31.310 align:start position:0% in a way that's flexible and is really 00:03:31.310 --> 00:03:33.400 align:start position:0% in a way that's flexible and is really low<00:03:31.580> risk<00:03:31.790> to<00:03:31.940> customers<00:03:32.330> and<00:03:32.600> so<00:03:33.230> while 00:03:33.400 --> 00:03:33.410 align:start position:0% low risk to customers and so while 00:03:33.410 --> 00:03:34.690 align:start position:0% low risk to customers and so while they're<00:03:33.560> dealing<00:03:33.890> more<00:03:34.040> with<00:03:34.100> kind<00:03:34.489> of<00:03:34.519> this 00:03:34.690 --> 00:03:34.700 align:start position:0% they're dealing more with kind of this 00:03:34.700 --> 00:03:38.229 align:start position:0% they're dealing more with kind of this core<00:03:35.590> you<00:03:36.590> know<00:03:36.680> fairly<00:03:37.070> complicated<00:03:37.580> service 00:03:38.229 --> 00:03:38.239 align:start position:0% core you know fairly complicated service 00:03:38.239 --> 00:03:39.820 align:start position:0% core you know fairly complicated service topology<00:03:38.750> and<00:03:38.930> helping<00:03:39.470> you<00:03:39.530> manage<00:03:39.680> that 00:03:39.820 --> 00:03:39.830 align:start position:0% topology and helping you manage that 00:03:39.830 --> 00:03:41.860 align:start position:0% topology and helping you manage that effectively<00:03:40.370> which<00:03:41.330> is<00:03:41.450> still<00:03:41.570> very 00:03:41.860 --> 00:03:41.870 align:start position:0% effectively which is still very 00:03:41.870 --> 00:03:43.390 align:start position:0% effectively which is still very important<00:03:42.350> we're<00:03:42.560> focused<00:03:42.950> more<00:03:43.100> at<00:03:43.190> the<00:03:43.280> edge 00:03:43.390 --> 00:03:43.400 align:start position:0% important we're focused more at the edge 00:03:43.400 --> 00:03:45.009 align:start position:0% important we're focused more at the edge and<00:03:43.430> managing<00:03:44.060> that<00:03:44.150> customer<00:03:44.570> experience 00:03:45.009 --> 00:03:45.019 align:start position:0% and managing that customer experience 00:03:45.019 --> 00:03:48.039 align:start position:0% and managing that customer experience more<00:03:45.260> effectively<00:03:45.650> mm-hmm<00:03:46.190> and<00:03:47.180> so<00:03:47.780> this<00:03:47.900> is 00:03:48.039 --> 00:03:48.049 align:start position:0% more effectively mm-hmm and so this is 00:03:48.049 --> 00:03:49.750 align:start position:0% more effectively mm-hmm and so this is kind<00:03:48.230> of<00:03:48.260> similar<00:03:48.470> to<00:03:48.620> saying<00:03:48.890> like<00:03:49.160> how<00:03:49.340> how 00:03:49.750 --> 00:03:49.760 align:start position:0% kind of similar to saying like how how 00:03:49.760 --> 00:03:50.800 align:start position:0% kind of similar to saying like how how does<00:03:49.820> boy<00:03:50.090> and<00:03:50.239> compared<00:03:50.510> to<00:03:50.600> cloud<00:03:50.780> player 00:03:50.800 --> 00:03:50.810 align:start position:0% does boy and compared to cloud player 00:03:50.810 --> 00:03:52.330 align:start position:0% does boy and compared to cloud player like<00:03:51.260> those<00:03:51.380> are<00:03:51.500> very<00:03:51.590> different<00:03:51.830> things<00:03:51.980> at 00:03:52.330 --> 00:03:52.340 align:start position:0% like those are very different things at 00:03:52.340 --> 00:03:53.199 align:start position:0% like those are very different things at very<00:03:52.519> different<00:03:52.549> parts<00:03:52.970> of<00:03:53.030> the<00:03:53.120> network 00:03:53.199 --> 00:03:53.209 align:start position:0% very different parts of the network 00:03:53.209 --> 00:03:55.420 align:start position:0% very different parts of the network stack<00:03:53.630> and<00:03:53.870> and<00:03:54.320> I<00:03:54.410> think<00:03:54.590> we<00:03:54.680> fit<00:03:55.010> in<00:03:55.190> between 00:03:55.420 --> 00:03:55.430 align:start position:0% stack and and I think we fit in between 00:03:55.430 --> 00:03:58.600 align:start position:0% stack and and I think we fit in between those<00:03:55.850> two<00:03:56.060> things<00:03:56.239> okay<00:03:56.930> so<00:03:57.620> it<00:03:58.190> makes<00:03:58.459> me 00:03:58.600 --> 00:03:58.610 align:start position:0% those two things okay so it makes me 00:03:58.610 --> 00:04:00.490 align:start position:0% those two things okay so it makes me super<00:03:59.060> curious<00:03:59.330> to<00:03:59.540> see<00:03:59.750> like<00:03:59.989> an<00:04:00.110> example 00:04:00.490 --> 00:04:00.500 align:start position:0% super curious to see like an example 00:04:00.500 --> 00:04:02.500 align:start position:0% super curious to see like an example Roger<00:04:01.040> might<00:04:01.340> become<00:04:01.610> common<00:04:01.940> give<00:04:02.120> us<00:04:02.239> a<00:04:02.269> folk 00:04:02.500 --> 00:04:02.510 align:start position:0% Roger might become common give us a folk 00:04:02.510 --> 00:04:05.020 align:start position:0% Roger might become common give us a folk I'm<00:04:02.750> sure<00:04:03.019> maybe<00:04:03.650> yeah<00:04:04.010> without<00:04:04.400> you<00:04:04.670> for 00:04:05.020 --> 00:04:05.030 align:start position:0% I'm sure maybe yeah without you for 00:04:05.030 --> 00:04:07.539 align:start position:0% I'm sure maybe yeah without you for example<00:04:05.390> one<00:04:05.540> person<00:04:05.840> I<00:04:05.989> wonder<00:04:06.410> right<00:04:06.680> so<00:04:07.040> you 00:04:07.539 --> 00:04:07.549 align:start position:0% example one person I wonder right so you 00:04:07.549 --> 00:04:09.460 align:start position:0% example one person I wonder right so you you<00:04:07.880> were<00:04:08.120> basically<00:04:08.510> leading<00:04:09.079> the<00:04:09.290> build 00:04:09.460 --> 00:04:09.470 align:start position:0% you were basically leading the build 00:04:09.470 --> 00:04:12.550 align:start position:0% you were basically leading the build team<00:04:09.709> a<00:04:09.970> Twitter<00:04:10.970> and<00:04:11.299> obviously<00:04:12.110> it's<00:04:12.350> all 00:04:12.550 --> 00:04:12.560 align:start position:0% team a Twitter and obviously it's all 00:04:12.560 --> 00:04:14.830 align:start position:0% team a Twitter and obviously it's all very<00:04:12.769> dramatic<00:04:13.370> and<00:04:13.489> so<00:04:14.090> usually<00:04:14.660> usually 00:04:14.830 --> 00:04:14.840 align:start position:0% very dramatic and so usually usually 00:04:14.840 --> 00:04:18.880 align:start position:0% very dramatic and so usually usually release<00:04:15.519> cycle<00:04:16.519> is<00:04:16.700> very<00:04:16.970> dramatic<00:04:17.570> tied<00:04:18.530> to 00:04:18.880 --> 00:04:18.890 align:start position:0% release cycle is very dramatic tied to 00:04:18.890 --> 00:04:20.710 align:start position:0% release cycle is very dramatic tied to the<00:04:19.039> culture<00:04:19.459> company<00:04:19.970> may<00:04:20.209> be<00:04:20.330> kind<00:04:20.570> of<00:04:20.630> all 00:04:20.710 --> 00:04:20.720 align:start position:0% the culture company may be kind of all 00:04:20.720 --> 00:04:22.010 align:start position:0% the culture company may be kind of all the<00:04:20.810> product<00:04:21.109> eyes 00:04:22.010 --> 00:04:22.020 align:start position:0% the product eyes 00:04:22.020 --> 00:04:24.840 align:start position:0% the product eyes best<00:04:23.020> practices<00:04:23.620> right<00:04:24.040> right<00:04:24.370> so<00:04:24.550> I<00:04:24.580> wonder 00:04:24.840 --> 00:04:24.850 align:start position:0% best practices right right so I wonder 00:04:24.850 --> 00:04:28.440 align:start position:0% best practices right right so I wonder how<00:04:25.060> do<00:04:25.120> you<00:04:25.450> see<00:04:25.930> that<00:04:26.200> you<00:04:26.740> know<00:04:27.180> work<00:04:28.180> in<00:04:28.360> the 00:04:28.440 --> 00:04:28.450 align:start position:0% how do you see that you know work in the 00:04:28.450 --> 00:04:29.900 align:start position:0% how do you see that you know work in the real<00:04:28.540> world<00:04:28.960> where<00:04:29.230> everybody<00:04:29.470> has<00:04:29.770> opinions 00:04:29.900 --> 00:04:29.910 align:start position:0% real world where everybody has opinions 00:04:29.910 --> 00:04:33.180 align:start position:0% real world where everybody has opinions has<00:04:30.910> already<00:04:31.120> some<00:04:31.420> kind<00:04:31.630> of<00:04:31.720> huge<00:04:32.260> processor 00:04:33.180 --> 00:04:33.190 align:start position:0% has already some kind of huge processor 00:04:33.190 --> 00:04:35.550 align:start position:0% has already some kind of huge processor and<00:04:33.430> entrenched<00:04:34.030> kind<00:04:34.600> of<00:04:34.690> habit<00:04:35.260> so<00:04:35.410> the 00:04:35.550 --> 00:04:35.560 align:start position:0% and entrenched kind of habit so the 00:04:35.560 --> 00:04:37.170 align:start position:0% and entrenched kind of habit so the world<00:04:35.740> so<00:04:36.370> I<00:04:36.400> think<00:04:36.640> there's<00:04:36.760> been<00:04:36.820> a<00:04:36.910> lot<00:04:37.150> of 00:04:37.170 --> 00:04:37.180 align:start position:0% world so I think there's been a lot of 00:04:37.180 --> 00:04:39.270 align:start position:0% world so I think there's been a lot of work<00:04:37.450> put<00:04:37.630> in<00:04:37.780> to<00:04:37.930> see<00:04:38.170> icd<00:04:38.590> recently<00:04:39.040> if<00:04:39.190> you 00:04:39.270 --> 00:04:39.280 align:start position:0% work put in to see icd recently if you 00:04:39.280 --> 00:04:41.520 align:start position:0% work put in to see icd recently if you look<00:04:39.460> at<00:04:39.580> like<00:04:39.730> Jenkins<00:04:39.970> was<00:04:40.510> a<00:04:40.570> fairly<00:04:41.080> novel 00:04:41.520 --> 00:04:41.530 align:start position:0% look at like Jenkins was a fairly novel 00:04:41.530 --> 00:04:43.350 align:start position:0% look at like Jenkins was a fairly novel thing<00:04:41.740> five<00:04:42.010> years<00:04:42.250> ago<00:04:42.370> and<00:04:42.760> now<00:04:43.120> there's<00:04:43.300> a 00:04:43.350 --> 00:04:43.360 align:start position:0% thing five years ago and now there's a 00:04:43.360 --> 00:04:44.850 align:start position:0% thing five years ago and now there's a bunch<00:04:43.510> of<00:04:43.600> Jenkins<00:04:43.930> clones<00:04:44.230> and<00:04:44.500> people<00:04:44.770> have 00:04:44.850 --> 00:04:44.860 align:start position:0% bunch of Jenkins clones and people have 00:04:44.860 --> 00:04:47.790 align:start position:0% bunch of Jenkins clones and people have pushed<00:04:45.100> more<00:04:45.310> from<00:04:45.550> CI<00:04:45.790> to<00:04:45.970> CD<00:04:46.330> mm-hmm<00:04:46.960> I<00:04:47.050> think 00:04:47.790 --> 00:04:47.800 align:start position:0% pushed more from CI to CD mm-hmm I think 00:04:47.800 --> 00:04:49.200 align:start position:0% pushed more from CI to CD mm-hmm I think the<00:04:47.860> question<00:04:48.130> we<00:04:48.250> asked<00:04:48.580> was<00:04:48.610> what<00:04:48.880> does<00:04:49.030> the 00:04:49.200 --> 00:04:49.210 align:start position:0% the question we asked was what does the 00:04:49.210 --> 00:04:51.660 align:start position:0% the question we asked was what does the D<00:04:49.390> and<00:04:49.630> C<00:04:49.810> D<00:04:49.960> mean<00:04:50.200> that<00:04:50.920> people<00:04:51.250> have<00:04:51.340> deployed 00:04:51.660 --> 00:04:51.670 align:start position:0% D and C D mean that people have deployed 00:04:51.670 --> 00:04:53.850 align:start position:0% D and C D mean that people have deployed or<00:04:51.880> delivery<00:04:52.270> or<00:04:52.420> what<00:04:52.570> have<00:04:52.690> you<00:04:52.740> but<00:04:53.740> even 00:04:53.850 --> 00:04:53.860 align:start position:0% or delivery or what have you but even 00:04:53.860 --> 00:04:55.980 align:start position:0% or delivery or what have you but even there<00:04:54.220> it's<00:04:54.550> like<00:04:54.730> a<00:04:54.760> really<00:04:55.030> sort<00:04:55.750> of<00:04:55.810> fuzzy 00:04:55.980 --> 00:04:55.990 align:start position:0% there it's like a really sort of fuzzy 00:04:55.990 --> 00:04:57.990 align:start position:0% there it's like a really sort of fuzzy notion<00:04:56.500> is<00:04:56.650> that<00:04:56.680> meaning<00:04:57.310> i<00:04:57.430> push<00:04:57.670> an<00:04:57.790> image 00:04:57.990 --> 00:04:58.000 align:start position:0% notion is that meaning i push an image 00:04:58.000 --> 00:04:59.610 align:start position:0% notion is that meaning i push an image to<00:04:58.150> docker<00:04:58.360> hub<00:04:58.480> does<00:04:58.990> it<00:04:59.170> mean<00:04:59.320> I<00:04:59.440> actually 00:04:59.610 --> 00:04:59.620 align:start position:0% to docker hub does it mean I actually 00:04:59.620 --> 00:05:01.620 align:start position:0% to docker hub does it mean I actually deploy<00:05:00.130> a<00:05:00.160> thing<00:05:00.490> on<00:05:00.670> to<00:05:00.850> infrastructure<00:05:01.090> does 00:05:01.620 --> 00:05:01.630 align:start position:0% deploy a thing on to infrastructure does 00:05:01.630 --> 00:05:03.300 align:start position:0% deploy a thing on to infrastructure does i<00:05:01.690> mean<00:05:01.870> i<00:05:02.170> deploy<00:05:02.530> and<00:05:02.770> it's<00:05:02.890> visible<00:05:03.130> to 00:05:03.300 --> 00:05:03.310 align:start position:0% i mean i deploy and it's visible to 00:05:03.310 --> 00:05:05.400 align:start position:0% i mean i deploy and it's visible to customers<00:05:03.700> yeah<00:05:04.150> we're<00:05:04.810> really<00:05:04.930> hoping<00:05:05.260> that 00:05:05.400 --> 00:05:05.410 align:start position:0% customers yeah we're really hoping that 00:05:05.410 --> 00:05:07.560 align:start position:0% customers yeah we're really hoping that people<00:05:05.560> sort<00:05:06.460> of<00:05:06.550> separate<00:05:06.940> deploy<00:05:07.300> from 00:05:07.560 --> 00:05:07.570 align:start position:0% people sort of separate deploy from 00:05:07.570 --> 00:05:09.450 align:start position:0% people sort of separate deploy from release<00:05:07.870> mm-hmm<00:05:08.830> getting<00:05:09.070> something<00:05:09.250> running 00:05:09.450 --> 00:05:09.460 align:start position:0% release mm-hmm getting something running 00:05:09.460 --> 00:05:11.130 align:start position:0% release mm-hmm getting something running on<00:05:09.640> compute<00:05:10.060> automate<00:05:10.660> the<00:05:10.750> hell<00:05:10.870> out<00:05:10.990> of<00:05:11.020> that 00:05:11.130 --> 00:05:11.140 align:start position:0% on compute automate the hell out of that 00:05:11.140 --> 00:05:13.530 align:start position:0% on compute automate the hell out of that mhm<00:05:11.650> and<00:05:11.860> I<00:05:12.400> think<00:05:12.460> that<00:05:12.820> can<00:05:12.970> be<00:05:13.000> fairly 00:05:13.530 --> 00:05:13.540 align:start position:0% mhm and I think that can be fairly 00:05:13.540 --> 00:05:15.120 align:start position:0% mhm and I think that can be fairly isolated<00:05:13.900> right<00:05:14.470> now<00:05:14.620> things<00:05:14.980> like 00:05:15.120 --> 00:05:15.130 align:start position:0% isolated right now things like 00:05:15.130 --> 00:05:17.940 align:start position:0% isolated right now things like namespaces<00:05:15.669> and<00:05:15.700> Cooper<00:05:15.940> Nettie's<00:05:16.950> what's 00:05:17.940 --> 00:05:17.950 align:start position:0% namespaces and Cooper Nettie's what's 00:05:17.950 --> 00:05:20.640 align:start position:0% namespaces and Cooper Nettie's what's harder<00:05:18.669> for<00:05:18.820> people<00:05:18.910> to<00:05:19.060> do<00:05:19.300> or<00:05:20.050> risky<00:05:20.470> for 00:05:20.640 --> 00:05:20.650 align:start position:0% harder for people to do or risky for 00:05:20.650 --> 00:05:22.140 align:start position:0% harder for people to do or risky for people<00:05:20.860> to<00:05:20.950> do<00:05:21.100> is<00:05:21.310> that<00:05:21.490> step<00:05:21.880> of<00:05:22.030> releasing 00:05:22.140 --> 00:05:22.150 align:start position:0% people to do is that step of releasing 00:05:22.150 --> 00:05:24.570 align:start position:0% people to do is that step of releasing new<00:05:22.630> code<00:05:22.810> to<00:05:22.960> customers<00:05:23.410> and<00:05:23.650> that's 00:05:24.570 --> 00:05:24.580 align:start position:0% new code to customers and that's 00:05:24.580 --> 00:05:25.530 align:start position:0% new code to customers and that's something<00:05:24.880> for<00:05:24.910> you<00:05:25.060> if<00:05:25.180> you<00:05:25.270> release 00:05:25.530 --> 00:05:25.540 align:start position:0% something for you if you release 00:05:25.540 --> 00:05:26.790 align:start position:0% something for you if you release something<00:05:25.750> that's<00:05:25.990> faulty<00:05:26.169> that<00:05:26.440> customers 00:05:26.790 --> 00:05:26.800 align:start position:0% something that's faulty that customers 00:05:26.800 --> 00:05:28.110 align:start position:0% something that's faulty that customers impacted<00:05:27.250> you're<00:05:27.400> going<00:05:27.520> to<00:05:27.580> get<00:05:27.669> called<00:05:27.910> and 00:05:28.110 --> 00:05:28.120 align:start position:0% impacted you're going to get called and 00:05:28.120 --> 00:05:30.750 align:start position:0% impacted you're going to get called and that's<00:05:28.510> bad<00:05:28.720> yes<00:05:29.110> and<00:05:29.350> so<00:05:29.950> to<00:05:30.010> the<00:05:30.280> extent<00:05:30.640> that 00:05:30.750 --> 00:05:30.760 align:start position:0% that's bad yes and so to the extent that 00:05:30.760 --> 00:05:33.030 align:start position:0% that's bad yes and so to the extent that you<00:05:30.970> can<00:05:31.000> observe<00:05:31.930> the<00:05:32.260> differences<00:05:32.680> in<00:05:32.710> old 00:05:33.030 --> 00:05:33.040 align:start position:0% you can observe the differences in old 00:05:33.040 --> 00:05:35.400 align:start position:0% you can observe the differences in old code<00:05:33.250> in<00:05:33.400> new<00:05:33.550> code<00:05:33.870> so<00:05:34.870> with<00:05:35.020> our<00:05:35.050> releases 00:05:35.400 --> 00:05:35.410 align:start position:0% code in new code so with our releases 00:05:35.410 --> 00:05:37.080 align:start position:0% code in new code so with our releases you<00:05:35.740> deploy<00:05:36.010> just<00:05:36.220> a<00:05:36.280> trickle<00:05:36.520> of<00:05:36.669> customers 00:05:37.080 --> 00:05:37.090 align:start position:0% you deploy just a trickle of customers 00:05:37.090 --> 00:05:38.880 align:start position:0% you deploy just a trickle of customers to<00:05:37.210> new<00:05:37.330> code<00:05:37.540> you<00:05:38.350> can<00:05:38.440> compare<00:05:38.770> the 00:05:38.880 --> 00:05:38.890 align:start position:0% to new code you can compare the 00:05:38.890 --> 00:05:40.230 align:start position:0% to new code you can compare the difference<00:05:39.190> in<00:05:39.310> experience<00:05:39.580> between<00:05:39.940> those 00:05:40.230 --> 00:05:40.240 align:start position:0% difference in experience between those 00:05:40.240 --> 00:05:42.030 align:start position:0% difference in experience between those two<00:05:40.360> versions<00:05:40.720> of<00:05:40.780> code<00:05:40.990> is<00:05:41.350> this<00:05:41.530> one<00:05:41.740> slower 00:05:42.030 --> 00:05:42.040 align:start position:0% two versions of code is this one slower 00:05:42.040 --> 00:05:44.730 align:start position:0% two versions of code is this one slower it's<00:05:42.729> a<00:05:42.880> throwing<00:05:43.180> errors<00:05:43.479> more<00:05:43.720> mmm<00:05:44.440> does<00:05:44.650> it 00:05:44.730 --> 00:05:44.740 align:start position:0% it's a throwing errors more mmm does it 00:05:44.740 --> 00:05:46.080 align:start position:0% it's a throwing errors more mmm does it have<00:05:44.830> a<00:05:44.860> different<00:05:45.040> behavior<00:05:45.310> than<00:05:45.820> the<00:05:45.910> one 00:05:46.080 --> 00:05:46.090 align:start position:0% have a different behavior than the one 00:05:46.090 --> 00:05:49.380 align:start position:0% have a different behavior than the one that<00:05:46.300> you<00:05:46.479> had<00:05:46.990> deployed<00:05:47.410> before<00:05:47.590> and<00:05:48.240> then<00:05:49.240> if 00:05:49.380 --> 00:05:49.390 align:start position:0% that you had deployed before and then if 00:05:49.390 --> 00:05:50.850 align:start position:0% that you had deployed before and then if you're<00:05:49.540> separating<00:05:50.110> deploy<00:05:50.380> from<00:05:50.530> release 00:05:50.850 --> 00:05:50.860 align:start position:0% you're separating deploy from release 00:05:50.860 --> 00:05:52.500 align:start position:0% you're separating deploy from release and<00:05:51.340> using<00:05:51.700> routing<00:05:52.060> as<00:05:52.180> your<00:05:52.300> release 00:05:52.500 --> 00:05:52.510 align:start position:0% and using routing as your release 00:05:52.510 --> 00:05:55.620 align:start position:0% and using routing as your release mechanism<00:05:53.110> if<00:05:53.830> you<00:05:54.010> notice<00:05:54.310> it's<00:05:54.460> bad<00:05:54.630> fixing 00:05:55.620 --> 00:05:55.630 align:start position:0% mechanism if you notice it's bad fixing 00:05:55.630 --> 00:05:57.420 align:start position:0% mechanism if you notice it's bad fixing that<00:05:55.720> becomes<00:05:56.140> a<00:05:56.380> fairly<00:05:56.680> trivial<00:05:56.860> step<00:05:57.280> of 00:05:57.420 --> 00:05:57.430 align:start position:0% that becomes a fairly trivial step of 00:05:57.430 --> 00:05:58.770 align:start position:0% that becomes a fairly trivial step of just<00:05:57.640> we<00:05:57.729> won't<00:05:57.910> route<00:05:58.090> to<00:05:58.240> that<00:05:58.360> new<00:05:58.479> version 00:05:58.770 --> 00:05:58.780 align:start position:0% just we won't route to that new version 00:05:58.780 --> 00:06:01.020 align:start position:0% just we won't route to that new version anymore<00:05:59.140> mm-hmm<00:05:59.560> so<00:06:00.310> to<00:06:00.430> the<00:06:00.520> extent<00:06:00.760> that<00:06:00.880> you 00:06:01.020 --> 00:06:01.030 align:start position:0% anymore mm-hmm so to the extent that you 00:06:01.030 --> 00:06:03.360 align:start position:0% anymore mm-hmm so to the extent that you can<00:06:01.180> make<00:06:01.360> that<00:06:01.660> sort<00:06:02.560> of<00:06:02.650> less<00:06:02.800> risky<00:06:03.190> by 00:06:03.360 --> 00:06:03.370 align:start position:0% can make that sort of less risky by 00:06:03.370 --> 00:06:05.400 align:start position:0% can make that sort of less risky by releasing<00:06:03.640> it<00:06:03.790> to<00:06:03.850> fewer<00:06:04.030> customers<00:06:04.410> quick 00:06:05.400 --> 00:06:05.410 align:start position:0% releasing it to fewer customers quick 00:06:05.410 --> 00:06:06.900 align:start position:0% releasing it to fewer customers quick detection<00:06:05.680> of<00:06:05.919> faults<00:06:06.250> because<00:06:06.400> you<00:06:06.700> can 00:06:06.900 --> 00:06:06.910 align:start position:0% detection of faults because you can 00:06:06.910 --> 00:06:09.120 align:start position:0% detection of faults because you can observe<00:06:07.210> old<00:06:07.630> versus<00:06:07.930> new<00:06:07.960> system<00:06:08.440> in<00:06:08.830> a<00:06:08.950> quick 00:06:09.120 --> 00:06:09.130 align:start position:0% observe old versus new system in a quick 00:06:09.130 --> 00:06:11.400 align:start position:0% observe old versus new system in a quick reversion<00:06:09.669> if<00:06:09.940> you<00:06:10.090> do<00:06:10.240> notice<00:06:10.450> a<00:06:10.600> fault<00:06:10.840> those 00:06:11.400 --> 00:06:11.410 align:start position:0% reversion if you do notice a fault those 00:06:11.410 --> 00:06:12.900 align:start position:0% reversion if you do notice a fault those releases<00:06:11.710> become<00:06:12.040> less<00:06:12.190> risky<00:06:12.550> and<00:06:12.669> you<00:06:12.760> can 00:06:12.900 --> 00:06:12.910 align:start position:0% releases become less risky and you can 00:06:12.910 --> 00:06:15.960 align:start position:0% releases become less risky and you can get<00:06:13.000> true<00:06:13.330> sort<00:06:13.810> of<00:06:13.930> the<00:06:14.740> dream<00:06:15.040> is<00:06:15.400> I<00:06:15.640> check<00:06:15.850> in 00:06:15.960 --> 00:06:15.970 align:start position:0% get true sort of the dream is I check in 00:06:15.970 --> 00:06:17.490 align:start position:0% get true sort of the dream is I check in to<00:06:16.060> get<00:06:16.210> and<00:06:16.479> it<00:06:16.630> goes<00:06:16.780> to<00:06:16.900> customers<00:06:17.260> if<00:06:17.380> it's 00:06:17.490 --> 00:06:17.500 align:start position:0% to get and it goes to customers if it's 00:06:17.500 --> 00:06:19.409 align:start position:0% to get and it goes to customers if it's good<00:06:17.680> mm-hmm<00:06:18.280> like<00:06:18.490> that's<00:06:18.700> everything<00:06:19.270> else 00:06:19.409 --> 00:06:19.419 align:start position:0% good mm-hmm like that's everything else 00:06:19.419 --> 00:06:21.030 align:start position:0% good mm-hmm like that's everything else is<00:06:19.600> so<00:06:19.720> it<00:06:19.840> would<00:06:20.260> be<00:06:20.350> fine<00:06:20.530> as<00:06:20.680> a<00:06:20.740> follicle 00:06:21.030 --> 00:06:21.040 align:start position:0% is so it would be fine as a follicle 00:06:21.040 --> 00:06:23.190 align:start position:0% is so it would be fine as a follicle bicycle<00:06:21.490> right<00:06:21.760> everything<00:06:22.690> else<00:06:22.840> is<00:06:23.020> sort<00:06:23.169> of 00:06:23.190 --> 00:06:23.200 align:start position:0% bicycle right everything else is sort of 00:06:23.200 --> 00:06:25.310 align:start position:0% bicycle right everything else is sort of attacks<00:06:23.530> in<00:06:23.710> between 00:06:25.310 --> 00:06:25.320 align:start position:0% attacks in between 00:06:25.320 --> 00:06:26.900 align:start position:0% attacks in between and<00:06:26.040> I<00:06:26.100> think<00:06:26.310> we're<00:06:26.400> in<00:06:26.430> pretty<00:06:26.490> good<00:06:26.700> shape 00:06:26.900 --> 00:06:26.910 align:start position:0% and I think we're in pretty good shape 00:06:26.910 --> 00:06:29.270 align:start position:0% and I think we're in pretty good shape there<00:06:27.090> I<00:06:27.150> think<00:06:27.380> strict<00:06:28.380> deployed<00:06:28.920> based 00:06:29.270 --> 00:06:29.280 align:start position:0% there I think strict deployed based 00:06:29.280 --> 00:06:31.910 align:start position:0% there I think strict deployed based approach<00:06:29.790> is<00:06:30.090> going<00:06:30.390> to<00:06:30.510> be<00:06:30.890> sort<00:06:31.890> of 00:06:31.910 --> 00:06:31.920 align:start position:0% approach is going to be sort of 00:06:31.920 --> 00:06:33.740 align:start position:0% approach is going to be sort of problematic<00:06:32.340> to<00:06:32.520> get<00:06:32.700> working<00:06:32.880> right<00:06:33.150> I'm 00:06:33.740 --> 00:06:33.750 align:start position:0% problematic to get working right I'm 00:06:33.750 --> 00:06:35.060 align:start position:0% problematic to get working right I'm treating<00:06:34.080> that<00:06:34.170> getting<00:06:34.740> it<00:06:34.830> running<00:06:34.890> on 00:06:35.060 --> 00:06:35.070 align:start position:0% treating that getting it running on 00:06:35.070 --> 00:06:37.070 align:start position:0% treating that getting it running on computer<00:06:35.520> versus<00:06:35.970> managing<00:06:36.540> the<00:06:36.690> release<00:06:36.930> to 00:06:37.070 --> 00:06:37.080 align:start position:0% computer versus managing the release to 00:06:37.080 --> 00:06:39.380 align:start position:0% computer versus managing the release to customers<00:06:37.500> is<00:06:37.830> a<00:06:38.250> good<00:06:38.550> separation<00:06:38.850> and 00:06:39.380 --> 00:06:39.390 align:start position:0% customers is a good separation and 00:06:39.390 --> 00:06:40.760 align:start position:0% customers is a good separation and something<00:06:39.900> we're<00:06:40.020> working<00:06:40.050> on<00:06:40.380> making<00:06:40.470> better 00:06:40.760 --> 00:06:40.770 align:start position:0% something we're working on making better 00:06:40.770 --> 00:06:43.730 align:start position:0% something we're working on making better right<00:06:41.610> so<00:06:42.000> I<00:06:42.030> I<00:06:42.420> don't<00:06:43.170> like<00:06:43.200> it<00:06:43.410> you<00:06:43.560> know<00:06:43.710> like 00:06:43.730 --> 00:06:43.740 align:start position:0% right so I I don't like it you know like 00:06:43.740 --> 00:06:45.170 align:start position:0% right so I I don't like it you know like you<00:06:44.040> know<00:06:44.130> I<00:06:44.160> wish<00:06:44.430> you<00:06:44.580> know<00:06:44.730> like<00:06:44.910> in<00:06:45.030> my 00:06:45.170 --> 00:06:45.180 align:start position:0% you know I wish you know like in my 00:06:45.180 --> 00:06:46.880 align:start position:0% you know I wish you know like in my previous<00:06:45.420> how<00:06:45.570> much<00:06:45.720> as<00:06:45.780> I<00:06:45.870> could<00:06:45.930> about<00:06:46.080> this 00:06:46.880 --> 00:06:46.890 align:start position:0% previous how much as I could about this 00:06:46.890 --> 00:06:49.880 align:start position:0% previous how much as I could about this so<00:06:47.430> how<00:06:47.910> easy<00:06:48.210> is<00:06:48.450> it<00:06:48.540> to<00:06:48.600> plug<00:06:48.900> into<00:06:49.080> existing 00:06:49.880 --> 00:06:49.890 align:start position:0% so how easy is it to plug into existing 00:06:49.890 --> 00:06:52.340 align:start position:0% so how easy is it to plug into existing companies<00:06:50.400> sure<00:06:50.850> so<00:06:51.180> most<00:06:52.020> people<00:06:52.140> already 00:06:52.340 --> 00:06:52.350 align:start position:0% companies sure so most people already 00:06:52.350 --> 00:06:53.780 align:start position:0% companies sure so most people already have<00:06:52.560> something<00:06:52.890> like<00:06:53.100> this<00:06:53.130> in<00:06:53.280> place<00:06:53.580> is 00:06:53.780 --> 00:06:53.790 align:start position:0% have something like this in place is 00:06:53.790 --> 00:06:55.490 align:start position:0% have something like this in place is just<00:06:53.940> crude<00:06:54.240> right<00:06:54.720> now<00:06:54.870> a<00:06:54.900> little<00:06:55.050> Jenkins 00:06:55.490 --> 00:06:55.500 align:start position:0% just crude right now a little Jenkins 00:06:55.500 --> 00:06:57.740 align:start position:0% just crude right now a little Jenkins was<00:06:55.560> also<00:06:55.860> like<00:06:56.190> some<00:06:56.310> so<00:06:57.030> it's<00:06:57.210> good<00:06:57.300> ones<00:06:57.600> who 00:06:57.740 --> 00:06:57.750 align:start position:0% was also like some so it's good ones who 00:06:57.750 --> 00:06:58.820 align:start position:0% was also like some so it's good ones who think<00:06:57.780> is<00:06:58.140> yeah<00:06:58.260> they<00:06:58.380> have<00:06:58.500> a<00:06:58.530> deployment 00:06:58.820 --> 00:06:58.830 align:start position:0% think is yeah they have a deployment 00:06:58.830 --> 00:07:01.190 align:start position:0% think is yeah they have a deployment tool<00:06:59.070> they<00:06:59.730> also<00:06:59.970> probably<00:07:00.780> have<00:07:00.990> a<00:07:01.020> load 00:07:01.190 --> 00:07:01.200 align:start position:0% tool they also probably have a load 00:07:01.200 --> 00:07:02.750 align:start position:0% tool they also probably have a load balancer<00:07:01.350> a<00:07:01.620> reverse<00:07:01.980> proxy<00:07:02.370> they're<00:07:02.520> using 00:07:02.750 --> 00:07:02.760 align:start position:0% balancer a reverse proxy they're using 00:07:02.760 --> 00:07:05.090 align:start position:0% balancer a reverse proxy they're using now<00:07:02.880> so<00:07:03.300> amazon<00:07:03.750> has<00:07:03.930> the<00:07:04.050> OBS<00:07:04.320> they<00:07:04.890> just 00:07:05.090 --> 00:07:05.100 align:start position:0% now so amazon has the OBS they just 00:07:05.100 --> 00:07:06.320 align:start position:0% now so amazon has the OBS they just released<00:07:05.370> a<00:07:05.490> lb<00:07:05.760> which<00:07:05.940> is<00:07:06.060> a<00:07:06.090> more 00:07:06.320 --> 00:07:06.330 align:start position:0% released a lb which is a more 00:07:06.330 --> 00:07:09.380 align:start position:0% released a lb which is a more sophisticated<00:07:06.510> version<00:07:07.350> WOB<00:07:08.070> and<00:07:08.280> so<00:07:09.090> we<00:07:09.210> see 00:07:09.380 --> 00:07:09.390 align:start position:0% sophisticated version WOB and so we see 00:07:09.390 --> 00:07:10.910 align:start position:0% sophisticated version WOB and so we see ourselves<00:07:09.510> as<00:07:09.870> a<00:07:09.930> better<00:07:10.140> back<00:07:10.410> half<00:07:10.680> of<00:07:10.830> the 00:07:10.910 --> 00:07:10.920 align:start position:0% ourselves as a better back half of the 00:07:10.920 --> 00:07:12.800 align:start position:0% ourselves as a better back half of the elb<00:07:11.160> mm-hmm<00:07:11.850> so<00:07:12.090> when<00:07:12.210> we<00:07:12.330> go<00:07:12.420> in<00:07:12.570> for<00:07:12.600> a 00:07:12.800 --> 00:07:12.810 align:start position:0% elb mm-hmm so when we go in for a 00:07:12.810 --> 00:07:14.690 align:start position:0% elb mm-hmm so when we go in for a deployed<00:07:13.110> so<00:07:13.530> i<00:07:13.590> still<00:07:13.830> use<00:07:13.950> your<00:07:14.010> lb<00:07:14.460> to<00:07:14.610> be 00:07:14.690 --> 00:07:14.700 align:start position:0% deployed so i still use your lb to be 00:07:14.700 --> 00:07:16.070 align:start position:0% deployed so i still use your lb to be that<00:07:14.880> armor<00:07:15.210> sort<00:07:15.690> of<00:07:15.780> on<00:07:15.900> the<00:07:16.050> edge 00:07:16.070 --> 00:07:16.080 align:start position:0% that armor sort of on the edge 00:07:16.080 --> 00:07:17.660 align:start position:0% that armor sort of on the edge protecting<00:07:16.830> your<00:07:16.950> infrastructure<00:07:17.220> from 00:07:17.660 --> 00:07:17.670 align:start position:0% protecting your infrastructure from 00:07:17.670 --> 00:07:20.600 align:start position:0% protecting your infrastructure from scary<00:07:18.030> internet<00:07:18.420> traffic<00:07:18.600> mm-hmm<00:07:19.320> but<00:07:19.830> have 00:07:20.600 --> 00:07:20.610 align:start position:0% scary internet traffic mm-hmm but have 00:07:20.610 --> 00:07:22.370 align:start position:0% scary internet traffic mm-hmm but have this<00:07:20.850> companion<00:07:21.420> that<00:07:21.660> the<00:07:21.780> software<00:07:21.960> based 00:07:22.370 --> 00:07:22.380 align:start position:0% this companion that the software based 00:07:22.380 --> 00:07:23.960 align:start position:0% this companion that the software based more<00:07:22.650> flexible<00:07:23.070> routing<00:07:23.370> engine<00:07:23.520> that<00:07:23.790> sits 00:07:23.960 --> 00:07:23.970 align:start position:0% more flexible routing engine that sits 00:07:23.970 --> 00:07:25.400 align:start position:0% more flexible routing engine that sits right<00:07:24.120> behind<00:07:24.270> it<00:07:24.600> to<00:07:24.810> really<00:07:25.050> direct 00:07:25.400 --> 00:07:25.410 align:start position:0% right behind it to really direct 00:07:25.410 --> 00:07:27.530 align:start position:0% right behind it to really direct customer<00:07:25.890> traffic<00:07:26.070> to<00:07:26.310> the<00:07:26.400> right<00:07:26.520> places<00:07:26.760> and 00:07:27.530 --> 00:07:27.540 align:start position:0% customer traffic to the right places and 00:07:27.540 --> 00:07:29.450 align:start position:0% customer traffic to the right places and if<00:07:28.290> you<00:07:28.470> have<00:07:28.710> that<00:07:28.950> and<00:07:29.220> the<00:07:29.310> right 00:07:29.450 --> 00:07:29.460 align:start position:0% if you have that and the right 00:07:29.460 --> 00:07:31.430 align:start position:0% if you have that and the right management<00:07:29.790> plane<00:07:30.120> is<00:07:30.450> a<00:07:30.480> point<00:07:30.840> to<00:07:31.080> observe 00:07:31.430 --> 00:07:31.440 align:start position:0% management plane is a point to observe 00:07:31.440 --> 00:07:33.170 align:start position:0% management plane is a point to observe customer<00:07:31.890> experience<00:07:32.310> the<00:07:32.550> point<00:07:32.760> to<00:07:32.880> affect 00:07:33.170 --> 00:07:33.180 align:start position:0% customer experience the point to affect 00:07:33.180 --> 00:07:35.630 align:start position:0% customer experience the point to affect control<00:07:33.600> and<00:07:34.230> it's<00:07:34.770> also<00:07:34.920> a<00:07:35.040> place<00:07:35.190> to<00:07:35.400> keep<00:07:35.520> a 00:07:35.630 --> 00:07:35.640 align:start position:0% control and it's also a place to keep a 00:07:35.640 --> 00:07:36.830 align:start position:0% control and it's also a place to keep a record<00:07:35.790> of<00:07:36.030> all<00:07:36.120> the<00:07:36.180> changes<00:07:36.660> made<00:07:36.690> to 00:07:36.830 --> 00:07:36.840 align:start position:0% record of all the changes made to 00:07:36.840 --> 00:07:39.800 align:start position:0% record of all the changes made to customer<00:07:37.290> experience<00:07:38.120> and<00:07:39.120> so<00:07:39.300> that's<00:07:39.510> sort 00:07:39.800 --> 00:07:39.810 align:start position:0% customer experience and so that's sort 00:07:39.810 --> 00:07:41.900 align:start position:0% customer experience and so that's sort of<00:07:39.900> where<00:07:40.050> we<00:07:40.170> slot<00:07:40.470> in<00:07:40.650> it's<00:07:41.430> not<00:07:41.610> that<00:07:41.670> we're 00:07:41.900 --> 00:07:41.910 align:start position:0% of where we slot in it's not that we're 00:07:41.910 --> 00:07:42.860 align:start position:0% of where we slot in it's not that we're adding<00:07:42.120> a<00:07:42.330> whole<00:07:42.480> new<00:07:42.630> piece<00:07:42.840> of 00:07:42.860 --> 00:07:42.870 align:start position:0% adding a whole new piece of 00:07:42.870 --> 00:07:44.780 align:start position:0% adding a whole new piece of infrastructure<00:07:43.140> we're<00:07:44.010> really<00:07:44.130> just<00:07:44.250> adding 00:07:44.780 --> 00:07:44.790 align:start position:0% infrastructure we're really just adding 00:07:44.790 --> 00:07:47.000 align:start position:0% infrastructure we're really just adding sort<00:07:45.210> of<00:07:45.330> an<00:07:45.660> extra<00:07:46.020> super<00:07:46.260> power<00:07:46.440> to<00:07:46.740> a<00:07:46.770> piece 00:07:47.000 --> 00:07:47.010 align:start position:0% sort of an extra super power to a piece 00:07:47.010 --> 00:07:48.800 align:start position:0% sort of an extra super power to a piece of<00:07:47.040> infrastructure<00:07:47.310> you<00:07:47.760> already<00:07:48.000> have<00:07:48.150> okay 00:07:48.800 --> 00:07:48.810 align:start position:0% of infrastructure you already have okay 00:07:48.810 --> 00:07:51.080 align:start position:0% of infrastructure you already have okay so<00:07:49.650> let's<00:07:49.830> all<00:07:50.160> super<00:07:50.430> exciting<00:07:50.790> you<00:07:50.940> know<00:07:51.000> i 00:07:51.080 --> 00:07:51.090 align:start position:0% so let's all super exciting you know i 00:07:51.090 --> 00:07:53.120 align:start position:0% so let's all super exciting you know i can't<00:07:51.240> wait<00:07:51.720> to<00:07:51.990> see<00:07:52.170> you<00:07:52.290> guys<00:07:52.350> present<00:07:52.950> all 00:07:53.120 --> 00:07:53.130 align:start position:0% can't wait to see you guys present all 00:07:53.130 --> 00:07:56.360 align:start position:0% can't wait to see you guys present all this<00:07:53.810> one<00:07:54.810> for<00:07:55.050> me<00:07:55.140> tops<00:07:55.290> all<00:07:55.740> right<00:07:55.890> maybe 00:07:56.360 --> 00:07:56.370 align:start position:0% this one for me tops all right maybe 00:07:56.370 --> 00:07:57.740 align:start position:0% this one for me tops all right maybe like<00:07:56.610> you<00:07:56.640> know<00:07:56.790> it's<00:07:57.030> kind<00:07:57.120> of<00:07:57.210> a<00:07:57.300> live<00:07:57.450> demo 00:07:57.740 --> 00:07:57.750 align:start position:0% like you know it's kind of a live demo 00:07:57.750 --> 00:07:59.420 align:start position:0% like you know it's kind of a live demo sure<00:07:58.170> and<00:07:58.470> that<00:07:58.860> will<00:07:58.980> do<00:07:59.130> really<00:07:59.310> cool 00:07:59.420 --> 00:07:59.430 align:start position:0% sure and that will do really cool 00:07:59.430 --> 00:08:00.410 align:start position:0% sure and that will do really cool because<00:07:59.550> i<00:07:59.730> think<00:07:59.880> a<00:07:59.940> lot<00:07:59.970> of<00:08:00.060> people<00:08:00.180> can 00:08:00.410 --> 00:08:00.420 align:start position:0% because i think a lot of people can 00:08:00.420 --> 00:08:02.870 align:start position:0% because i think a lot of people can actually<00:08:00.600> use<00:08:00.930> it<00:08:00.960> yeah<00:08:01.620> i<00:08:01.830> hope<00:08:02.070> so<00:08:02.130> cool<00:08:02.730> it 00:08:02.870 --> 00:08:02.880 align:start position:0% actually use it yeah i hope so cool it 00:08:02.880 --> 00:08:03.710 align:start position:0% actually use it yeah i hope so cool it was<00:08:02.970> great<00:08:03.120> to<00:08:03.240> have<00:08:03.360> you<00:08:03.450> back<00:08:03.480> in<00:08:03.600> the 00:08:03.710 --> 00:08:03.720 align:start position:0% was great to have you back in the 00:08:03.720 --> 00:08:05.690 align:start position:0% was great to have you back in the community<00:08:04.050> okay<00:08:04.290> yeah<00:08:04.410> yeah<00:08:04.890> and<00:08:05.520> we're 00:08:05.690 --> 00:08:05.700 align:start position:0% community okay yeah yeah and we're 00:08:05.700 --> 00:08:06.650 align:start position:0% community okay yeah yeah and we're neighbors<00:08:05.940> you<00:08:06.060> know<00:08:06.120> i'm<00:08:06.300> going<00:08:06.450> to<00:08:06.510> visit 00:08:06.650 --> 00:08:06.660 align:start position:0% neighbors you know i'm going to visit 00:08:06.660 --> 00:08:09.620 align:start position:0% neighbors you know i'm going to visit you<00:08:06.840> guys<00:08:07.110> know<00:08:07.380> me<00:08:07.560> too<00:08:07.680> nice<00:08:08.480> all<00:08:09.480> right 00:08:09.620 --> 00:08:09.630 align:start position:0% you guys know me too nice all right 00:08:09.630 --> 00:08:12.890 align:start position:0% you guys know me too nice all right thanks<00:08:10.470> thank<00:08:10.710> you<00:08:10.770> rush