WEBVTT Kind: captions Language: en 00:00:02.470 --> 00:00:12.959 align:start position:0% [Music] 00:00:12.959 --> 00:00:12.969 align:start position:0% 00:00:12.969 --> 00:00:15.240 align:start position:0% hello<00:00:13.780> everybody<00:00:13.929> my<00:00:14.259> name<00:00:14.410> is<00:00:14.620> Alexa<00:00:14.919> crabber 00:00:15.240 --> 00:00:15.250 align:start position:0% hello everybody my name is Alexa crabber 00:00:15.250 --> 00:00:17.040 align:start position:0% hello everybody my name is Alexa crabber from<00:00:15.459> the<00:00:15.639> founder<00:00:16.090> and<00:00:16.119> organizer<00:00:16.720> of<00:00:16.810> the 00:00:17.040 --> 00:00:17.050 align:start position:0% from the founder and organizer of the 00:00:17.050 --> 00:00:19.290 align:start position:0% from the founder and organizer of the era<00:00:17.230> AI<00:00:17.470> and<00:00:18.189> we<00:00:18.400> have<00:00:18.520> a<00:00:18.610> joint<00:00:18.880> meet<00:00:19.150> up 00:00:19.290 --> 00:00:19.300 align:start position:0% era AI and we have a joint meet up 00:00:19.300 --> 00:00:23.600 align:start position:0% era AI and we have a joint meet up tonight<00:00:19.779> at<00:00:20.619> D<00:00:21.130> 2aq<00:00:21.730> a<00:00:22.000> well-known<00:00:22.840> company 00:00:23.600 --> 00:00:23.610 align:start position:0% tonight at D 2aq a well-known company 00:00:23.610 --> 00:00:26.310 align:start position:0% tonight at D 2aq a well-known company basically<00:00:24.610> doing<00:00:24.820> data<00:00:25.180> orchestration<00:00:25.989> and<00:00:26.110> I 00:00:26.310 --> 00:00:26.320 align:start position:0% basically doing data orchestration and I 00:00:26.320 --> 00:00:28.260 align:start position:0% basically doing data orchestration and I think<00:00:26.470> it's<00:00:26.590> very<00:00:26.680> fitting<00:00:26.919> we<00:00:27.880> have<00:00:28.029> a<00:00:28.060> jury 00:00:28.260 --> 00:00:28.270 align:start position:0% think it's very fitting we have a jury 00:00:28.270 --> 00:00:30.510 align:start position:0% think it's very fitting we have a jury made<00:00:28.419> up<00:00:28.509> of<00:00:28.660> multiple<00:00:28.869> meetups<00:00:29.500> and<00:00:29.739> the 00:00:30.510 --> 00:00:30.520 align:start position:0% made up of multiple meetups and the 00:00:30.520 --> 00:00:33.450 align:start position:0% made up of multiple meetups and the topic<00:00:31.329> of<00:00:31.419> this<00:00:31.509> meetup<00:00:31.840> is<00:00:32.410> machine<00:00:32.860> learning 00:00:33.450 --> 00:00:33.460 align:start position:0% topic of this meetup is machine learning 00:00:33.460 --> 00:00:37.340 align:start position:0% topic of this meetup is machine learning models<00:00:34.420> and<00:00:34.840> specifically<00:00:36.090> versioning<00:00:37.090> and 00:00:37.340 --> 00:00:37.350 align:start position:0% models and specifically versioning and 00:00:37.350 --> 00:00:41.340 align:start position:0% models and specifically versioning and monitoring<00:00:38.350> we<00:00:38.469> have<00:00:38.649> two<00:00:38.770> talks<00:00:39.120> and<00:00:40.350> the 00:00:41.340 --> 00:00:41.350 align:start position:0% monitoring we have two talks and the 00:00:41.350 --> 00:00:43.410 align:start position:0% monitoring we have two talks and the monitoring<00:00:42.129> is<00:00:42.370> with<00:00:42.700> hundreds<00:00:43.059> upon 00:00:43.410 --> 00:00:43.420 align:start position:0% monitoring is with hundreds upon 00:00:43.420 --> 00:00:46.200 align:start position:0% monitoring is with hundreds upon pushkaryova<00:00:44.020> and<00:00:44.200> the<00:00:44.699> versioning<00:00:45.699> is<00:00:45.909> with 00:00:46.200 --> 00:00:46.210 align:start position:0% pushkaryova and the versioning is with 00:00:46.210 --> 00:00:48.739 align:start position:0% pushkaryova and the versioning is with mono<00:00:46.480> severe<00:00:46.839> talk<00:00:47.050> who<00:00:47.379> is<00:00:47.559> the<00:00:47.859> CEO<00:00:48.100> of<00:00:48.370> Verta 00:00:48.739 --> 00:00:48.749 align:start position:0% mono severe talk who is the CEO of Verta 00:00:48.749 --> 00:00:52.410 align:start position:0% mono severe talk who is the CEO of Verta III<00:00:50.489> recent<00:00:51.489> startup 00:00:52.410 --> 00:00:52.420 align:start position:0% III recent startup 00:00:52.420 --> 00:00:54.599 align:start position:0% III recent startup so<00:00:52.899> welcome<00:00:53.289> mama<00:00:53.469> C<00:00:53.679> thank<00:00:54.039> you<00:00:54.159> thank<00:00:54.579> you 00:00:54.599 --> 00:00:54.609 align:start position:0% so welcome mama C thank you thank you 00:00:54.609 --> 00:00:56.160 align:start position:0% so welcome mama C thank you thank you for<00:00:54.699> having<00:00:54.850> me<00:00:55.120> tell<00:00:55.539> us<00:00:55.719> a<00:00:55.749> little<00:00:55.870> bit<00:00:56.050> about 00:00:56.160 --> 00:00:56.170 align:start position:0% for having me tell us a little bit about 00:00:56.170 --> 00:00:58.380 align:start position:0% for having me tell us a little bit about yourself<00:00:56.739> why<00:00:57.249> did<00:00:57.429> you<00:00:57.550> decide<00:00:57.940> to<00:00:57.969> start 00:00:58.380 --> 00:00:58.390 align:start position:0% yourself why did you decide to start 00:00:58.390 --> 00:00:59.989 align:start position:0% yourself why did you decide to start Verta<00:00:58.899> and<00:00:59.170> what<00:00:59.409> this<00:00:59.649> is<00:00:59.800> all<00:00:59.890> about 00:00:59.989 --> 00:00:59.999 align:start position:0% Verta and what this is all about 00:00:59.999 --> 00:01:06.180 align:start position:0% Verta and what this is all about absolutely<00:01:01.030> so<00:01:01.780> I<00:01:02.260> am<00:01:02.800> a<00:01:03.720> technical<00:01:04.720> founder<00:01:05.530> I 00:01:06.180 --> 00:01:06.190 align:start position:0% absolutely so I am a technical founder I 00:01:06.190 --> 00:01:09.450 align:start position:0% absolutely so I am a technical founder I did<00:01:06.700> my<00:01:06.850> PhD<00:01:06.909> at<00:01:07.390> MIT<00:01:07.479> worked<00:01:08.470> on<00:01:08.650> data<00:01:09.010> systems 00:01:09.450 --> 00:01:09.460 align:start position:0% did my PhD at MIT worked on data systems 00:01:09.460 --> 00:01:11.760 align:start position:0% did my PhD at MIT worked on data systems all<00:01:09.880> throughout<00:01:10.150> grad<00:01:10.390> school<00:01:10.659> so<00:01:10.900> one<00:01:11.590> of<00:01:11.620> the 00:01:11.760 --> 00:01:11.770 align:start position:0% all throughout grad school so one of the 00:01:11.770 --> 00:01:14.430 align:start position:0% all throughout grad school so one of the systems<00:01:12.100> I<00:01:12.220> built<00:01:12.460> was<00:01:12.729> modeled<00:01:13.299> TB<00:01:13.570> we 00:01:14.430 --> 00:01:14.440 align:start position:0% systems I built was modeled TB we 00:01:14.440 --> 00:01:17.190 align:start position:0% systems I built was modeled TB we started<00:01:15.040> looking<00:01:15.159> at<00:01:15.729> how<00:01:16.510> data<00:01:16.780> scientists 00:01:17.190 --> 00:01:17.200 align:start position:0% started looking at how data scientists 00:01:17.200 --> 00:01:19.650 align:start position:0% started looking at how data scientists work<00:01:17.380> and<00:01:17.770> what<00:01:18.010> were<00:01:18.130> challenges<00:01:18.970> and<00:01:19.270> this 00:01:19.650 --> 00:01:19.660 align:start position:0% work and what were challenges and this 00:01:19.660 --> 00:01:22.620 align:start position:0% work and what were challenges and this was<00:01:20.050> around<00:01:20.800> the<00:01:20.950> time<00:01:21.010> one<00:01:21.520> Alex<00:01:22.030> net<00:01:22.270> and<00:01:22.540> all 00:01:22.620 --> 00:01:22.630 align:start position:0% was around the time one Alex net and all 00:01:22.630 --> 00:01:24.930 align:start position:0% was around the time one Alex net and all of<00:01:22.780> the<00:01:22.900> deep<00:01:23.050> learning<00:01:23.490> models<00:01:24.490> were<00:01:24.640> really 00:01:24.930 --> 00:01:24.940 align:start position:0% of the deep learning models were really 00:01:24.940 --> 00:01:27.510 align:start position:0% of the deep learning models were really becoming<00:01:25.320> significant<00:01:26.320> I<00:01:26.470> realized<00:01:27.100> that<00:01:27.310> the 00:01:27.510 --> 00:01:27.520 align:start position:0% becoming significant I realized that the 00:01:27.520 --> 00:01:28.920 align:start position:0% becoming significant I realized that the things<00:01:27.700> that<00:01:27.760> we<00:01:27.970> take<00:01:28.150> granted<00:01:28.510> for<00:01:28.690> software 00:01:28.920 --> 00:01:28.930 align:start position:0% things that we take granted for software 00:01:28.930 --> 00:01:30.600 align:start position:0% things that we take granted for software I<00:01:29.020> like<00:01:29.260> get<00:01:29.560> type<00:01:29.860> versioning<00:01:30.250> systems 00:01:30.600 --> 00:01:30.610 align:start position:0% I like get type versioning systems 00:01:30.610 --> 00:01:33.000 align:start position:0% I like get type versioning systems deployment<00:01:31.450> debugging<00:01:32.200> were<00:01:32.440> all<00:01:32.590> missing 00:01:33.000 --> 00:01:33.010 align:start position:0% deployment debugging were all missing 00:01:33.010 --> 00:01:35.340 align:start position:0% deployment debugging were all missing for<00:01:33.310> models<00:01:33.640> and<00:01:33.940> so<00:01:34.120> we<00:01:34.870> ended<00:01:35.140> up<00:01:35.200> building 00:01:35.340 --> 00:01:35.350 align:start position:0% for models and so we ended up building 00:01:35.350 --> 00:01:37.590 align:start position:0% for models and so we ended up building model<00:01:35.740> DB<00:01:36.010> which<00:01:36.310> became<00:01:36.640> a<00:01:36.940> popular<00:01:37.180> open 00:01:37.590 --> 00:01:37.600 align:start position:0% model DB which became a popular open 00:01:37.600 --> 00:01:39.540 align:start position:0% model DB which became a popular open source<00:01:37.630> project<00:01:38.200> and<00:01:38.500> then<00:01:38.650> further<00:01:38.890> evolved 00:01:39.540 --> 00:01:39.550 align:start position:0% source project and then further evolved 00:01:39.550 --> 00:01:44.130 align:start position:0% source project and then further evolved from<00:01:39.730> that<00:01:39.870> nice<00:01:40.870> and<00:01:41.770> so<00:01:42.000> I'm<00:01:43.000> curious<00:01:43.360> so<00:01:44.080> you 00:01:44.130 --> 00:01:44.140 align:start position:0% from that nice and so I'm curious so you 00:01:44.140 --> 00:01:47.400 align:start position:0% from that nice and so I'm curious so you were<00:01:44.470> a<00:01:44.500> researcher<00:01:45.130> to<00:01:45.160> me<00:01:45.760> right<00:01:46.420> was<00:01:46.900> very 00:01:47.400 --> 00:01:47.410 align:start position:0% were a researcher to me right was very 00:01:47.410 --> 00:01:50.220 align:start position:0% were a researcher to me right was very soft<00:01:47.710> regime<00:01:48.160> before<00:01:48.400> that<00:01:48.670> how<00:01:48.880> the<00:01:49.630> specific 00:01:50.220 --> 00:01:50.230 align:start position:0% soft regime before that how the specific 00:01:50.230 --> 00:01:53.910 align:start position:0% soft regime before that how the specific topic<00:01:50.950> came<00:01:51.130> up<00:01:51.340> yeah<00:01:52.170> so<00:01:53.170> I<00:01:53.200> did<00:01:53.470> I<00:01:53.620> worked<00:01:53.800> at 00:01:53.910 --> 00:01:53.920 align:start position:0% topic came up yeah so I did I worked at 00:01:53.920 --> 00:01:55.680 align:start position:0% topic came up yeah so I did I worked at Microsoft<00:01:54.040> between<00:01:54.610> undergrad<00:01:55.150> and<00:01:55.390> grad 00:01:55.680 --> 00:01:55.690 align:start position:0% Microsoft between undergrad and grad 00:01:55.690 --> 00:01:58.680 align:start position:0% Microsoft between undergrad and grad school<00:01:55.990> um<00:01:56.380> my<00:01:56.980> PhD<00:01:57.940> was<00:01:58.120> also<00:01:58.450> in<00:01:58.600> the 00:01:58.680 --> 00:01:58.690 align:start position:0% school um my PhD was also in the 00:01:58.690 --> 00:02:00.930 align:start position:0% school um my PhD was also in the database<00:01:59.080> group<00:01:59.410> from<00:01:59.890> which<00:02:00.100> came<00:02:00.460> post 00:02:00.930 --> 00:02:00.940 align:start position:0% database group from which came post 00:02:00.940 --> 00:02:02.700 align:start position:0% database group from which came post grass<00:02:01.180> and<00:02:01.360> verdict<00:02:01.660> also<00:02:01.960> like<00:02:02.110> we<00:02:02.470> built 00:02:02.700 --> 00:02:02.710 align:start position:0% grass and verdict also like we built 00:02:02.710 --> 00:02:06.180 align:start position:0% grass and verdict also like we built systems<00:02:02.910> and<00:02:03.910> so<00:02:04.090> it<00:02:04.600> just<00:02:04.740> we<00:02:05.740> write<00:02:06.010> software 00:02:06.180 --> 00:02:06.190 align:start position:0% systems and so it just we write software 00:02:06.190 --> 00:02:09.089 align:start position:0% systems and so it just we write software all<00:02:06.430> day<00:02:06.750> it<00:02:07.750> was<00:02:07.930> a<00:02:07.960> clear<00:02:08.259> and<00:02:08.649> natural 00:02:09.089 --> 00:02:09.099 align:start position:0% all day it was a clear and natural 00:02:09.099 --> 00:02:09.779 align:start position:0% all day it was a clear and natural direction 00:02:09.779 --> 00:02:09.789 align:start position:0% direction 00:02:09.789 --> 00:02:12.990 align:start position:0% direction nice<00:02:10.390> but<00:02:10.869> obviously<00:02:12.010> machine<00:02:12.730> learning 00:02:12.990 --> 00:02:13.000 align:start position:0% nice but obviously machine learning 00:02:13.000 --> 00:02:15.180 align:start position:0% nice but obviously machine learning model<00:02:13.300> also<00:02:13.450> very<00:02:13.599> different<00:02:13.810> beasts<00:02:14.379> do<00:02:15.099> you 00:02:15.180 --> 00:02:15.190 align:start position:0% model also very different beasts do you 00:02:15.190 --> 00:02:17.490 align:start position:0% model also very different beasts do you have<00:02:15.430> specific<00:02:16.150> issues<00:02:16.540> in<00:02:16.720> machine<00:02:17.050> learning 00:02:17.490 --> 00:02:17.500 align:start position:0% have specific issues in machine learning 00:02:17.500 --> 00:02:19.740 align:start position:0% have specific issues in machine learning how<00:02:18.459> did<00:02:18.670> this<00:02:18.790> come<00:02:19.000> about<00:02:19.209> yeah<00:02:19.569> absolutely 00:02:19.740 --> 00:02:19.750 align:start position:0% how did this come about yeah absolutely 00:02:19.750 --> 00:02:23.400 align:start position:0% how did this come about yeah absolutely so<00:02:20.130> my<00:02:21.130> interests<00:02:21.490> are<00:02:21.550> between<00:02:22.390> data<00:02:22.990> systems 00:02:23.400 --> 00:02:23.410 align:start position:0% so my interests are between data systems 00:02:23.410 --> 00:02:25.040 align:start position:0% so my interests are between data systems nml<00:02:24.130> my<00:02:24.550> under 00:02:25.040 --> 00:02:25.050 align:start position:0% nml my under 00:02:25.050 --> 00:02:27.050 align:start position:0% nml my under with<00:02:25.200> CS<00:02:25.650> and<00:02:26.010> math<00:02:26.220> so<00:02:26.520> I<00:02:26.580> also<00:02:26.730> write 00:02:27.050 --> 00:02:27.060 align:start position:0% with CS and math so I also write 00:02:27.060 --> 00:02:28.940 align:start position:0% with CS and math so I also write algorithms<00:02:27.540> and<00:02:27.900> things<00:02:28.050> like<00:02:28.140> that<00:02:28.200> I<00:02:28.560> used 00:02:28.940 --> 00:02:28.950 align:start position:0% algorithms and things like that I used 00:02:28.950 --> 00:02:30.290 align:start position:0% algorithms and things like that I used to<00:02:29.010> be<00:02:29.070> part<00:02:29.310> of<00:02:29.370> the<00:02:29.460> feed<00:02:29.610> ranking<00:02:29.940> team<00:02:30.120> at 00:02:30.290 --> 00:02:30.300 align:start position:0% to be part of the feed ranking team at 00:02:30.300 --> 00:02:32.210 align:start position:0% to be part of the feed ranking team at Twitter<00:02:30.510> also<00:02:31.080> worked<00:02:31.290> on<00:02:31.500> dynamic<00:02:32.070> ad 00:02:32.210 --> 00:02:32.220 align:start position:0% Twitter also worked on dynamic ad 00:02:32.220 --> 00:02:34.190 align:start position:0% Twitter also worked on dynamic ad targeting<00:02:32.520> at<00:02:32.850> Google<00:02:33.180> so<00:02:33.330> that<00:02:33.450> was<00:02:33.570> applied 00:02:34.190 --> 00:02:34.200 align:start position:0% targeting at Google so that was applied 00:02:34.200 --> 00:02:36.740 align:start position:0% targeting at Google so that was applied ml<00:02:34.560> and<00:02:34.770> that<00:02:35.100> gave<00:02:35.280> a<00:02:35.520> good<00:02:35.700> balance<00:02:36.060> to<00:02:36.150> the 00:02:36.740 --> 00:02:36.750 align:start position:0% ml and that gave a good balance to the 00:02:36.750 --> 00:02:40.040 align:start position:0% ml and that gave a good balance to the systems<00:02:37.170> building<00:02:37.410> and<00:02:37.860> advert<00:02:38.760> up<00:02:38.940> my<00:02:39.690> CTO 00:02:40.040 --> 00:02:40.050 align:start position:0% systems building and advert up my CTO 00:02:40.050 --> 00:02:41.510 align:start position:0% systems building and advert up my CTO actually<00:02:40.320> comes<00:02:40.470> from<00:02:40.650> Twitter<00:02:40.890> and<00:02:41.160> NVIDIA 00:02:41.510 --> 00:02:41.520 align:start position:0% actually comes from Twitter and NVIDIA 00:02:41.520 --> 00:02:43.640 align:start position:0% actually comes from Twitter and NVIDIA we<00:02:41.940> both<00:02:42.090> work<00:02:42.300> together<00:02:42.450> Twitter<00:02:42.900> is<00:02:43.080> like<00:02:43.260> it 00:02:43.640 --> 00:02:43.650 align:start position:0% we both work together Twitter is like it 00:02:43.650 --> 00:02:45.410 align:start position:0% we both work together Twitter is like it also<00:02:43.800> brings<00:02:44.070> a<00:02:44.190> lot<00:02:44.340> of<00:02:44.490> significant<00:02:45.060> chops 00:02:45.410 --> 00:02:45.420 align:start position:0% also brings a lot of significant chops 00:02:45.420 --> 00:02:48.050 align:start position:0% also brings a lot of significant chops in<00:02:46.260> the<00:02:46.320> production<00:02:47.190> of<00:02:47.340> asian<00:02:47.640> of<00:02:47.670> models 00:02:48.050 --> 00:02:48.060 align:start position:0% in the production of asian of models 00:02:48.060 --> 00:02:50.030 align:start position:0% in the production of asian of models very<00:02:48.510> cool<00:02:48.720> very<00:02:49.080> cool<00:02:49.200> so<00:02:49.470> the<00:02:49.620> you<00:02:49.740> can<00:02:49.950> have 00:02:50.030 --> 00:02:50.040 align:start position:0% very cool very cool so the you can have 00:02:50.040 --> 00:02:51.650 align:start position:0% very cool very cool so the you can have brilliant<00:02:50.220> this<00:02:50.430> two<00:02:50.610> worlds<00:02:51.030> right<00:02:51.210> song<00:02:51.420> I'm 00:02:51.650 --> 00:02:51.660 align:start position:0% brilliant this two worlds right song I'm 00:02:51.660 --> 00:02:54.020 align:start position:0% brilliant this two worlds right song I'm know<00:02:52.290> I'm<00:02:52.320> curious<00:02:52.860> right<00:02:53.520> because<00:02:53.820> you're 00:02:54.020 --> 00:02:54.030 align:start position:0% know I'm curious right because you're 00:02:54.030 --> 00:02:55.700 align:start position:0% know I'm curious right because you're clearly<00:02:54.330> in<00:02:54.660> the<00:02:54.870> camp<00:02:55.200> of<00:02:55.410> software 00:02:55.700 --> 00:02:55.710 align:start position:0% clearly in the camp of software 00:02:55.710 --> 00:02:57.920 align:start position:0% clearly in the camp of software engineers<00:02:56.070> which<00:02:56.820> most<00:02:57.090> of<00:02:57.330> our<00:02:57.600> meetup 00:02:57.920 --> 00:02:57.930 align:start position:0% engineers which most of our meetup 00:02:57.930 --> 00:03:01.220 align:start position:0% engineers which most of our meetup members<00:02:58.620> are<00:02:58.770> right<00:02:59.100> so<00:02:59.460> we<00:03:00.360> kind<00:03:00.540> of<00:03:00.660> so<00:03:00.930> the 00:03:01.220 --> 00:03:01.230 align:start position:0% members are right so we kind of so the 00:03:01.230 --> 00:03:03.500 align:start position:0% members are right so we kind of so the the<00:03:01.530> theory<00:03:01.980> which<00:03:02.250> kind<00:03:02.460> of<00:03:02.520> most<00:03:02.760> I<00:03:03.030> see 00:03:03.500 --> 00:03:03.510 align:start position:0% the theory which kind of most I see 00:03:03.510 --> 00:03:05.570 align:start position:0% the theory which kind of most I see working<00:03:03.990> in<00:03:04.200> in<00:03:04.500> the<00:03:04.530> area<00:03:05.040> if<00:03:05.430> you<00:03:05.550> have 00:03:05.570 --> 00:03:05.580 align:start position:0% working in in the area if you have 00:03:05.580 --> 00:03:07.340 align:start position:0% working in in the area if you have working<00:03:05.850> company<00:03:06.300> you<00:03:07.020> know<00:03:07.170> machine 00:03:07.340 --> 00:03:07.350 align:start position:0% working company you know machine 00:03:07.350 --> 00:03:08.630 align:start position:0% working company you know machine learning<00:03:07.440> is<00:03:07.650> a<00:03:07.710> commodity<00:03:07.920> you<00:03:08.280> take<00:03:08.430> it<00:03:08.520> off 00:03:08.630 --> 00:03:08.640 align:start position:0% learning is a commodity you take it off 00:03:08.640 --> 00:03:11.210 align:start position:0% learning is a commodity you take it off itself<00:03:08.940> you're<00:03:09.150> not<00:03:09.390> you<00:03:09.690> know<00:03:09.950> working<00:03:10.950> Geoff 00:03:11.210 --> 00:03:11.220 align:start position:0% itself you're not you know working Geoff 00:03:11.220 --> 00:03:13.760 align:start position:0% itself you're not you know working Geoff Kimpton<00:03:11.370> next<00:03:12.030> deploring<00:03:13.020> iteration<00:03:13.530> you<00:03:13.740> are 00:03:13.760 --> 00:03:13.770 align:start position:0% Kimpton next deploring iteration you are 00:03:13.770 --> 00:03:16.430 align:start position:0% Kimpton next deploring iteration you are a<00:03:14.460> grunt<00:03:14.970> deploying<00:03:15.780> models<00:03:16.080> making<00:03:16.260> sure 00:03:16.430 --> 00:03:16.440 align:start position:0% a grunt deploying models making sure 00:03:16.440 --> 00:03:17.900 align:start position:0% a grunt deploying models making sure that<00:03:16.560> make<00:03:16.710> money<00:03:16.890> or<00:03:17.040> don't<00:03:17.220> lose<00:03:17.370> money<00:03:17.610> and 00:03:17.900 --> 00:03:17.910 align:start position:0% that make money or don't lose money and 00:03:17.910 --> 00:03:21.020 align:start position:0% that make money or don't lose money and and<00:03:18.210> your<00:03:18.570> job<00:03:18.780> depends<00:03:19.200> on<00:03:19.320> them<00:03:19.560> being<00:03:20.280> you 00:03:21.020 --> 00:03:21.030 align:start position:0% and your job depends on them being you 00:03:21.030 --> 00:03:23.420 align:start position:0% and your job depends on them being you know<00:03:21.180> in<00:03:21.660> production<00:03:22.170> right<00:03:22.410> and<00:03:23.010> so<00:03:23.160> like 00:03:23.420 --> 00:03:23.430 align:start position:0% know in production right and so like 00:03:23.430 --> 00:03:25.220 align:start position:0% know in production right and so like versioning<00:03:23.910> is<00:03:24.030> beautiful<00:03:24.480> it<00:03:24.900> sounds<00:03:25.110> like 00:03:25.220 --> 00:03:25.230 align:start position:0% versioning is beautiful it sounds like 00:03:25.230 --> 00:03:27.710 align:start position:0% versioning is beautiful it sounds like music<00:03:25.350> to<00:03:25.830> our<00:03:25.860> ears<00:03:26.400> because<00:03:26.760> if<00:03:27.420> something 00:03:27.710 --> 00:03:27.720 align:start position:0% music to our ears because if something 00:03:27.720 --> 00:03:29.780 align:start position:0% music to our ears because if something bad<00:03:27.870> happens<00:03:28.260> you<00:03:28.380> need<00:03:28.530> to<00:03:28.620> find<00:03:28.800> out<00:03:28.920> and<00:03:29.370> so 00:03:29.780 --> 00:03:29.790 align:start position:0% bad happens you need to find out and so 00:03:29.790 --> 00:03:32.360 align:start position:0% bad happens you need to find out and so can<00:03:30.060> we<00:03:30.150> understand<00:03:30.570> get<00:03:31.050> and<00:03:31.380> and<00:03:31.739> continuous 00:03:32.360 --> 00:03:32.370 align:start position:0% can we understand get and and continuous 00:03:32.370 --> 00:03:35.060 align:start position:0% can we understand get and and continuous integration<00:03:32.459> like<00:03:33.120> so<00:03:33.600> but<00:03:34.230> but<00:03:34.590> a<00:03:34.620> lot<00:03:35.040> of 00:03:35.060 --> 00:03:35.070 align:start position:0% integration like so but but a lot of 00:03:35.070 --> 00:03:37.940 align:start position:0% integration like so but but a lot of data<00:03:35.580> science<00:03:36.090> development<00:03:37.050> is<00:03:37.440> done<00:03:37.650> by 00:03:37.940 --> 00:03:37.950 align:start position:0% data science development is done by 00:03:37.950 --> 00:03:41.870 align:start position:0% data science development is done by folks<00:03:38.790> who<00:03:38.989> do<00:03:39.989> Python<00:03:40.560> and<00:03:40.830> do<00:03:41.670> it<00:03:41.730> in<00:03:41.820> a 00:03:41.870 --> 00:03:41.880 align:start position:0% folks who do Python and do it in a 00:03:41.880 --> 00:03:44.420 align:start position:0% folks who do Python and do it in a notebook<00:03:42.090> they're<00:03:42.600> not<00:03:42.780> in<00:03:43.170> production<00:03:44.010> so 00:03:44.420 --> 00:03:44.430 align:start position:0% notebook they're not in production so 00:03:44.430 --> 00:03:47.030 align:start position:0% notebook they're not in production so how<00:03:44.670> do<00:03:44.730> you<00:03:45.150> address<00:03:45.959> those<00:03:46.320> guys<00:03:46.590> like<00:03:46.920> how 00:03:47.030 --> 00:03:47.040 align:start position:0% how do you address those guys like how 00:03:47.040 --> 00:03:49.400 align:start position:0% how do you address those guys like how do<00:03:47.100> you<00:03:47.220> interact<00:03:47.430> with<00:03:47.700> engineers<00:03:48.410> versus 00:03:49.400 --> 00:03:49.410 align:start position:0% do you interact with engineers versus 00:03:49.410 --> 00:03:51.680 align:start position:0% do you interact with engineers versus the<00:03:49.680> designers<00:03:50.190> versus<00:03:50.610> business<00:03:51.090> owners 00:03:51.680 --> 00:03:51.690 align:start position:0% the designers versus business owners 00:03:51.690 --> 00:03:53.930 align:start position:0% the designers versus business owners right<00:03:52.230> I<00:03:52.500> will<00:03:52.980> see<00:03:53.010> all<00:03:53.160> these<00:03:53.430> metrics<00:03:53.610> in 00:03:53.930 --> 00:03:53.940 align:start position:0% right I will see all these metrics in 00:03:53.940 --> 00:03:56.570 align:start position:0% right I will see all these metrics in the<00:03:54.060> hundred<00:03:54.750> person<00:03:54.989> um<00:03:55.200> so<00:03:55.650> for<00:03:56.070> us<00:03:56.340> the 00:03:56.570 --> 00:03:56.580 align:start position:0% the hundred person um so for us the 00:03:56.580 --> 00:03:58.520 align:start position:0% the hundred person um so for us the fundamentals<00:03:56.910> of<00:03:57.300> our<00:03:57.480> product<00:03:57.959> don't<00:03:58.230> change 00:03:58.520 --> 00:03:58.530 align:start position:0% fundamentals of our product don't change 00:03:58.530 --> 00:04:01.610 align:start position:0% fundamentals of our product don't change for<00:03:59.100> us<00:03:59.790> a<00:03:59.820> model<00:04:00.150> version<00:04:00.480> consists<00:04:01.170> of<00:04:01.290> as<00:04:01.500> I 00:04:01.610 --> 00:04:01.620 align:start position:0% for us a model version consists of as I 00:04:01.620 --> 00:04:03.530 align:start position:0% for us a model version consists of as I will<00:04:01.770> talk<00:04:02.040> about<00:04:02.160> the<00:04:02.940> code<00:04:03.180> the<00:04:03.390> data 00:04:03.530 --> 00:04:03.540 align:start position:0% will talk about the code the data 00:04:03.540 --> 00:04:06.199 align:start position:0% will talk about the code the data configured<00:04:04.440> environment<00:04:04.890> together<00:04:05.190> now<00:04:06.060> if 00:04:06.199 --> 00:04:06.209 align:start position:0% configured environment together now if 00:04:06.209 --> 00:04:08.360 align:start position:0% configured environment together now if I'm<00:04:06.360> a<00:04:06.420> data<00:04:06.660> scientist<00:04:07.260> I<00:04:07.560> am<00:04:07.590> in<00:04:07.950> a<00:04:08.040> Jupiter 00:04:08.360 --> 00:04:08.370 align:start position:0% I'm a data scientist I am in a Jupiter 00:04:08.370 --> 00:04:11.180 align:start position:0% I'm a data scientist I am in a Jupiter notebook<00:04:08.760> or<00:04:08.970> our<00:04:09.209> studio<00:04:09.720> and<00:04:10.410> the<00:04:10.890> way<00:04:11.010> that 00:04:11.180 --> 00:04:11.190 align:start position:0% notebook or our studio and the way that 00:04:11.190 --> 00:04:13.310 align:start position:0% notebook or our studio and the way that they<00:04:11.310> access<00:04:11.670> our<00:04:11.850> product<00:04:12.300> is<00:04:12.510> via<00:04:12.720> very<00:04:13.080> easy 00:04:13.310 --> 00:04:13.320 align:start position:0% they access our product is via very easy 00:04:13.320 --> 00:04:16.159 align:start position:0% they access our product is via very easy to<00:04:13.500> use<00:04:13.650> api's<00:04:14.160> or<00:04:14.580> gooeys<00:04:15.000> mm-hmm<00:04:15.810> now<00:04:15.900> if 00:04:16.159 --> 00:04:16.169 align:start position:0% to use api's or gooeys mm-hmm now if 00:04:16.169 --> 00:04:17.780 align:start position:0% to use api's or gooeys mm-hmm now if you're<00:04:16.290> a<00:04:16.320> software<00:04:16.709> engineer<00:04:17.130> and<00:04:17.400> or<00:04:17.640> you're 00:04:17.780 --> 00:04:17.790 align:start position:0% you're a software engineer and or you're 00:04:17.790 --> 00:04:19.940 align:start position:0% you're a software engineer and or you're a<00:04:17.850> DevOps<00:04:18.150> person<00:04:18.660> then<00:04:18.900> you<00:04:18.989> care<00:04:19.200> about<00:04:19.560> your 00:04:19.940 --> 00:04:19.950 align:start position:0% a DevOps person then you care about your 00:04:19.950 --> 00:04:21.620 align:start position:0% a DevOps person then you care about your SaaS<00:04:20.280> throughput<00:04:20.970> how's<00:04:21.239> your<00:04:21.419> model 00:04:21.620 --> 00:04:21.630 align:start position:0% SaaS throughput how's your model 00:04:21.630 --> 00:04:23.570 align:start position:0% SaaS throughput how's your model behaving<00:04:22.080> then<00:04:22.590> you<00:04:22.860> can<00:04:23.040> access<00:04:23.340> it<00:04:23.520> directly 00:04:23.570 --> 00:04:23.580 align:start position:0% behaving then you can access it directly 00:04:23.580 --> 00:04:26.440 align:start position:0% behaving then you can access it directly through<00:04:24.180> kubernetes<00:04:24.990> sort<00:04:25.380> of<00:04:25.470> coop<00:04:25.680> control 00:04:26.440 --> 00:04:26.450 align:start position:0% through kubernetes sort of coop control 00:04:26.450 --> 00:04:29.210 align:start position:0% through kubernetes sort of coop control use<00:04:27.450> the<00:04:27.810> yeah<00:04:27.930> no<00:04:27.990> files<00:04:28.350> integrated<00:04:29.010> into 00:04:29.210 --> 00:04:29.220 align:start position:0% use the yeah no files integrated into 00:04:29.220 --> 00:04:31.640 align:start position:0% use the yeah no files integrated into Jenkins<00:04:29.669> do<00:04:30.090> the<00:04:30.360> software<00:04:30.660> route<00:04:30.960> and<00:04:31.530> then 00:04:31.640 --> 00:04:31.650 align:start position:0% Jenkins do the software route and then 00:04:31.650 --> 00:04:33.230 align:start position:0% Jenkins do the software route and then if<00:04:31.770> you're<00:04:31.890> a<00:04:31.919> business<00:04:32.250> owner<00:04:32.400> then<00:04:32.940> you're 00:04:33.230 --> 00:04:33.240 align:start position:0% if you're a business owner then you're 00:04:33.240 --> 00:04:36.230 align:start position:0% if you're a business owner then you're only<00:04:33.479> looking<00:04:33.840> at<00:04:34.200> our<00:04:34.700> part<00:04:35.700> of<00:04:35.760> the<00:04:35.820> product 00:04:36.230 --> 00:04:36.240 align:start position:0% only looking at our part of the product 00:04:36.240 --> 00:04:37.980 align:start position:0% only looking at our part of the product so<00:04:36.720> there's<00:04:36.900> the<00:04:36.960> same<00:04:37.169> fundamental 00:04:37.980 --> 00:04:37.990 align:start position:0% so there's the same fundamental 00:04:37.990 --> 00:04:40.440 align:start position:0% so there's the same fundamental very<00:04:38.140> similar<00:04:38.410> to<00:04:38.530> say<00:04:38.730> github<00:04:39.730> if<00:04:40.090> you<00:04:40.270> only 00:04:40.440 --> 00:04:40.450 align:start position:0% very similar to say github if you only 00:04:40.450 --> 00:04:42.870 align:start position:0% very similar to say github if you only look<00:04:40.750> at<00:04:40.870> the<00:04:41.050> UI<00:04:41.200> that<00:04:41.740> maybe<00:04:42.010> a<00:04:42.340> business 00:04:42.870 --> 00:04:42.880 align:start position:0% look at the UI that maybe a business 00:04:42.880 --> 00:04:43.980 align:start position:0% look at the UI that maybe a business owner<00:04:43.000> or<00:04:43.120> a<00:04:43.180> project<00:04:43.360> manager<00:04:43.870> can 00:04:43.980 --> 00:04:43.990 align:start position:0% owner or a project manager can 00:04:43.990 --> 00:04:45.570 align:start position:0% owner or a project manager can understand<00:04:44.470> it<00:04:44.620> versus<00:04:45.340> if<00:04:45.460> you're<00:04:45.550> a 00:04:45.570 --> 00:04:45.580 align:start position:0% understand it versus if you're a 00:04:45.580 --> 00:04:46.800 align:start position:0% understand it versus if you're a software<00:04:45.820> developer<00:04:46.270> you<00:04:46.360> have<00:04:46.390> the<00:04:46.540> command 00:04:46.800 --> 00:04:46.810 align:start position:0% software developer you have the command 00:04:46.810 --> 00:04:48.690 align:start position:0% software developer you have the command line<00:04:46.990> name<00:04:47.170> you're<00:04:47.410> doing<00:04:47.650> merges<00:04:48.010> and<00:04:48.040> pulls 00:04:48.690 --> 00:04:48.700 align:start position:0% line name you're doing merges and pulls 00:04:48.700 --> 00:04:49.470 align:start position:0% line name you're doing merges and pulls all<00:04:48.910> the<00:04:49.030> time 00:04:49.470 --> 00:04:49.480 align:start position:0% all the time 00:04:49.480 --> 00:04:51.390 align:start position:0% all the time so<00:04:49.600> here's<00:04:49.810> kind<00:04:49.870> of<00:04:50.050> an<00:04:50.260> EVE<00:04:50.470> scenario<00:04:51.070> right 00:04:51.390 --> 00:04:51.400 align:start position:0% so here's kind of an EVE scenario right 00:04:51.400 --> 00:04:53.010 align:start position:0% so here's kind of an EVE scenario right so<00:04:51.550> I'm<00:04:51.700> a<00:04:51.730> business<00:04:52.060> owner<00:04:52.240> and<00:04:52.600> I<00:04:52.750> run<00:04:52.930> an 00:04:53.010 --> 00:04:53.020 align:start position:0% so I'm a business owner and I run an 00:04:53.020 --> 00:04:54.780 align:start position:0% so I'm a business owner and I run an online<00:04:53.140> shop<00:04:53.560> right<00:04:53.830> now<00:04:53.980> my<00:04:54.130> data<00:04:54.310> scientists 00:04:54.780 --> 00:04:54.790 align:start position:0% online shop right now my data scientists 00:04:54.790 --> 00:04:56.730 align:start position:0% online shop right now my data scientists are<00:04:54.880> kind<00:04:55.060> of<00:04:55.150> doing<00:04:55.360> the<00:04:56.290> upselling 00:04:56.730 --> 00:04:56.740 align:start position:0% are kind of doing the upselling 00:04:56.740 --> 00:05:00.450 align:start position:0% are kind of doing the upselling customers<00:04:57.520> on<00:04:57.940> shopping<00:04:58.780> carts<00:04:59.080> right<00:04:59.800> or 00:05:00.450 --> 00:05:00.460 align:start position:0% customers on shopping carts right or 00:05:00.460 --> 00:05:02.820 align:start position:0% customers on shopping carts right or they're<00:05:01.150> basically<00:05:01.570> like<00:05:02.140> I'm<00:05:02.290> watching<00:05:02.710> it 00:05:02.820 --> 00:05:02.830 align:start position:0% they're basically like I'm watching it 00:05:02.830 --> 00:05:04.710 align:start position:0% they're basically like I'm watching it they're<00:05:02.950> coming<00:05:03.190> back<00:05:03.370> and<00:05:03.580> so<00:05:03.730> you<00:05:03.970> know<00:05:04.420> the 00:05:04.710 --> 00:05:04.720 align:start position:0% they're coming back and so you know the 00:05:04.720 --> 00:05:07.020 align:start position:0% they're coming back and so you know the the<00:05:04.930> model<00:05:05.260> basically<00:05:05.440> does<00:05:05.920> it<00:05:06.130> and<00:05:06.310> so<00:05:06.520> I 00:05:07.020 --> 00:05:07.030 align:start position:0% the model basically does it and so I 00:05:07.030 --> 00:05:08.850 align:start position:0% the model basically does it and so I have<00:05:07.240> a<00:05:07.270> metric<00:05:07.720> how<00:05:07.840> much<00:05:08.080> do<00:05:08.290> they<00:05:08.440> upsell 00:05:08.850 --> 00:05:08.860 align:start position:0% have a metric how much do they upsell 00:05:08.860 --> 00:05:13.130 align:start position:0% have a metric how much do they upsell each<00:05:09.580> checkout<00:05:10.360> and<00:05:10.930> and<00:05:11.680> and<00:05:12.010> so<00:05:12.160> so<00:05:12.610> can<00:05:12.880> you 00:05:13.130 --> 00:05:13.140 align:start position:0% each checkout and and and so so can you 00:05:13.140 --> 00:05:15.780 align:start position:0% each checkout and and and so so can you kind<00:05:14.140> of<00:05:14.230> can<00:05:14.560> we<00:05:14.770> is<00:05:14.950> the<00:05:15.130> field<00:05:15.430> this<00:05:15.730> is 00:05:15.780 --> 00:05:15.790 align:start position:0% kind of can we is the field this is 00:05:15.790 --> 00:05:18.180 align:start position:0% kind of can we is the field this is necessary<00:05:16.270> reach<00:05:16.420> the<00:05:16.600> point<00:05:16.780> where<00:05:17.140> I<00:05:17.530> am<00:05:18.070> the 00:05:18.180 --> 00:05:18.190 align:start position:0% necessary reach the point where I am the 00:05:18.190 --> 00:05:19.890 align:start position:0% necessary reach the point where I am the shop<00:05:18.370> owner<00:05:18.610> I<00:05:18.970> have<00:05:19.180> no<00:05:19.330> idea<00:05:19.660> what<00:05:19.780> that 00:05:19.890 --> 00:05:19.900 align:start position:0% shop owner I have no idea what that 00:05:19.900 --> 00:05:21.150 align:start position:0% shop owner I have no idea what that assigns<00:05:20.200> as<00:05:20.350> the<00:05:20.440> programmers<00:05:20.770> are<00:05:20.830> doing<00:05:21.040> I 00:05:21.150 --> 00:05:21.160 align:start position:0% assigns as the programmers are doing I 00:05:21.160 --> 00:05:22.320 align:start position:0% assigns as the programmers are doing I wake<00:05:21.310> up<00:05:21.340> in<00:05:21.550> the<00:05:21.580> middle<00:05:21.700> of<00:05:21.850> the<00:05:21.910> night<00:05:22.090> I 00:05:22.320 --> 00:05:22.330 align:start position:0% wake up in the middle of the night I 00:05:22.330 --> 00:05:25.080 align:start position:0% wake up in the middle of the night I wish<00:05:22.900> how<00:05:23.170> much<00:05:23.550> every<00:05:24.550> checkout<00:05:24.910> is 00:05:25.080 --> 00:05:25.090 align:start position:0% wish how much every checkout is 00:05:25.090 --> 00:05:26.730 align:start position:0% wish how much every checkout is upsetting<00:05:25.420> and<00:05:25.660> suddenly<00:05:25.990> because<00:05:26.560> the 00:05:26.730 --> 00:05:26.740 align:start position:0% upsetting and suddenly because the 00:05:26.740 --> 00:05:29.250 align:start position:0% upsetting and suddenly because the previous<00:05:27.160> night<00:05:27.550> some<00:05:27.970> somebody<00:05:28.720> messed<00:05:29.050> up 00:05:29.250 --> 00:05:29.260 align:start position:0% previous night some somebody messed up 00:05:29.260 --> 00:05:30.990 align:start position:0% previous night some somebody messed up and<00:05:29.440> the<00:05:29.560> models<00:05:29.860> really<00:05:30.040> bad<00:05:30.370> and<00:05:30.670> like<00:05:30.820> I'm 00:05:30.990 --> 00:05:31.000 align:start position:0% and the models really bad and like I'm 00:05:31.000 --> 00:05:34.230 align:start position:0% and the models really bad and like I'm something<00:05:31.150> really<00:05:32.190> plunged<00:05:33.190> can<00:05:33.850> I<00:05:34.000> push<00:05:34.210> a 00:05:34.230 --> 00:05:34.240 align:start position:0% something really plunged can I push a 00:05:34.240 --> 00:05:37.230 align:start position:0% something really plunged can I push a button<00:05:34.540> to<00:05:34.930> rollback<00:05:35.170> like<00:05:35.620> is<00:05:35.980> it<00:05:36.910> at<00:05:37.090> the 00:05:37.230 --> 00:05:37.240 align:start position:0% button to rollback like is it at the 00:05:37.240 --> 00:05:39.780 align:start position:0% button to rollback like is it at the level<00:05:37.660> where<00:05:37.990> you<00:05:38.590> can<00:05:38.740> give<00:05:38.950> this<00:05:39.070> tool<00:05:39.430> to<00:05:39.730> a 00:05:39.780 --> 00:05:39.790 align:start position:0% level where you can give this tool to a 00:05:39.790 --> 00:05:41.430 align:start position:0% level where you can give this tool to a business<00:05:40.030> owner<00:05:40.210> who<00:05:40.480> which<00:05:40.930> is<00:05:41.110> a<00:05:41.140> clear 00:05:41.430 --> 00:05:41.440 align:start position:0% business owner who which is a clear 00:05:41.440 --> 00:05:43.980 align:start position:0% business owner who which is a clear business<00:05:41.800> metric<00:05:42.220> and<00:05:42.610> he<00:05:43.360> will<00:05:43.540> be<00:05:43.690> alerted 00:05:43.980 --> 00:05:43.990 align:start position:0% business metric and he will be alerted 00:05:43.990 --> 00:05:46.590 align:start position:0% business metric and he will be alerted or<00:05:44.380> is<00:05:44.530> it<00:05:44.650> the<00:05:44.770> job<00:05:45.040> of<00:05:45.310> an<00:05:45.400> engineer<00:05:45.820> I<00:05:46.030> mean 00:05:46.590 --> 00:05:46.600 align:start position:0% or is it the job of an engineer I mean 00:05:46.600 --> 00:05:48.180 align:start position:0% or is it the job of an engineer I mean are<00:05:46.780> we<00:05:46.810> gonna<00:05:46.960> involve<00:05:47.380> somebody<00:05:47.980> who 00:05:48.180 --> 00:05:48.190 align:start position:0% are we gonna involve somebody who 00:05:48.190 --> 00:05:50.220 align:start position:0% are we gonna involve somebody who understands<00:05:48.610> the<00:05:48.730> business<00:05:48.880> metric<00:05:49.570> should 00:05:50.220 --> 00:05:50.230 align:start position:0% understands the business metric should 00:05:50.230 --> 00:05:52.440 align:start position:0% understands the business metric should it<00:05:50.380> be<00:05:50.560> a<00:05:50.590> pet<00:05:51.040> religion<00:05:51.460> level<00:05:51.730> thing<00:05:51.970> for<00:05:52.270> an 00:05:52.440 --> 00:05:52.450 align:start position:0% it be a pet religion level thing for an 00:05:52.450 --> 00:05:54.600 align:start position:0% it be a pet religion level thing for an engineer<00:05:52.870> or<00:05:52.990> can<00:05:53.200> you<00:05:53.470> let<00:05:53.740> like<00:05:54.250> reach<00:05:54.460> the 00:05:54.600 --> 00:05:54.610 align:start position:0% engineer or can you let like reach the 00:05:54.610 --> 00:05:55.920 align:start position:0% engineer or can you let like reach the point<00:05:54.760> where<00:05:55.000> a<00:05:55.030> business<00:05:55.300> owner<00:05:55.600> will<00:05:55.750> be 00:05:55.920 --> 00:05:55.930 align:start position:0% point where a business owner will be 00:05:55.930 --> 00:05:58.230 align:start position:0% point where a business owner will be able<00:05:56.110> to<00:05:56.380> to<00:05:56.920> say<00:05:57.100> no<00:05:57.280> this<00:05:57.640> doesn't<00:05:57.940> work 00:05:58.230 --> 00:05:58.240 align:start position:0% able to to say no this doesn't work 00:05:58.240 --> 00:06:01.560 align:start position:0% able to to say no this doesn't work because<00:05:59.200> you<00:05:59.650> know<00:05:59.770> he<00:06:00.340> cares<00:06:00.700> he<00:06:01.060> wakes<00:06:01.330> up 00:06:01.560 --> 00:06:01.570 align:start position:0% because you know he cares he wakes up 00:06:01.570 --> 00:06:04.140 align:start position:0% because you know he cares he wakes up and<00:06:01.750> he<00:06:01.930> does<00:06:02.140> a<00:06:02.170> rollback<00:06:02.620> is<00:06:02.830> it<00:06:02.980> possible<00:06:03.340> I 00:06:04.140 --> 00:06:04.150 align:start position:0% and he does a rollback is it possible I 00:06:04.150 --> 00:06:06.690 align:start position:0% and he does a rollback is it possible I would<00:06:04.540> say<00:06:04.960> that<00:06:05.200> in<00:06:05.560> this<00:06:05.800> sense<00:06:06.160> our<00:06:06.250> models 00:06:06.690 --> 00:06:06.700 align:start position:0% would say that in this sense our models 00:06:06.700 --> 00:06:08.400 align:start position:0% would say that in this sense our models are<00:06:06.820> not<00:06:07.030> different<00:06:07.330> from<00:06:07.630> existing<00:06:08.230> software 00:06:08.400 --> 00:06:08.410 align:start position:0% are not different from existing software 00:06:08.410 --> 00:06:11.040 align:start position:0% are not different from existing software if<00:06:08.980> I'm<00:06:09.130> a<00:06:09.250> product<00:06:09.670> owner<00:06:09.880> and<00:06:10.180> say<00:06:10.780> it's<00:06:10.930> my 00:06:11.040 --> 00:06:11.050 align:start position:0% if I'm a product owner and say it's my 00:06:11.050 --> 00:06:12.660 align:start position:0% if I'm a product owner and say it's my mobile<00:06:11.230> app<00:06:11.500> and<00:06:11.710> I<00:06:11.770> see<00:06:11.980> something<00:06:12.400> wrong 00:06:12.660 --> 00:06:12.670 align:start position:0% mobile app and I see something wrong 00:06:12.670 --> 00:06:13.050 align:start position:0% mobile app and I see something wrong with<00:06:12.880> it 00:06:13.050 --> 00:06:13.060 align:start position:0% with it 00:06:13.060 --> 00:06:14.670 align:start position:0% with it I<00:06:13.150> don't<00:06:13.420> go<00:06:13.660> to<00:06:13.720> our<00:06:13.900> dashboard<00:06:14.110> and<00:06:14.380> roll<00:06:14.560> it 00:06:14.670 --> 00:06:14.680 align:start position:0% I don't go to our dashboard and roll it 00:06:14.680 --> 00:06:17.430 align:start position:0% I don't go to our dashboard and roll it back<00:06:15.100> I<00:06:15.130> hurt<00:06:15.550> my<00:06:15.820> engineer<00:06:16.480> to<00:06:16.660> do<00:06:16.780> it<00:06:16.930> yes<00:06:17.290> so 00:06:17.430 --> 00:06:17.440 align:start position:0% back I hurt my engineer to do it yes so 00:06:17.440 --> 00:06:18.810 align:start position:0% back I hurt my engineer to do it yes so I<00:06:17.470> don't<00:06:17.740> think<00:06:17.920> ml<00:06:18.250> models<00:06:18.580> for<00:06:18.670> any 00:06:18.810 --> 00:06:18.820 align:start position:0% I don't think ml models for any 00:06:18.820 --> 00:06:20.490 align:start position:0% I don't think ml models for any different<00:06:19.240> we<00:06:19.450> would<00:06:19.630> escalate<00:06:19.900> it<00:06:20.110> via<00:06:20.260> page 00:06:20.490 --> 00:06:20.500 align:start position:0% different we would escalate it via page 00:06:20.500 --> 00:06:22.890 align:start position:0% different we would escalate it via page or<00:06:20.650> duty<00:06:20.890> they<00:06:21.370> can<00:06:21.520> provide<00:06:21.790> input<00:06:22.120> into<00:06:22.750> why 00:06:22.890 --> 00:06:22.900 align:start position:0% or duty they can provide input into why 00:06:22.900 --> 00:06:25.440 align:start position:0% or duty they can provide input into why they<00:06:23.140> think<00:06:23.380> a<00:06:23.470> metric<00:06:23.770> is<00:06:23.920> off<00:06:24.160> but<00:06:24.850> we<00:06:25.270> don't 00:06:25.440 --> 00:06:25.450 align:start position:0% they think a metric is off but we don't 00:06:25.450 --> 00:06:26.730 align:start position:0% they think a metric is off but we don't think<00:06:25.660> they're<00:06:25.780> the<00:06:25.900> right<00:06:26.020> people<00:06:26.380> to<00:06:26.560> roll 00:06:26.730 --> 00:06:26.740 align:start position:0% think they're the right people to roll 00:06:26.740 --> 00:06:28.860 align:start position:0% think they're the right people to roll back<00:06:26.920> a<00:06:26.950> production<00:06:27.460> system<00:06:27.610> okay<00:06:28.240> all<00:06:28.690> right 00:06:28.860 --> 00:06:28.870 align:start position:0% back a production system okay all right 00:06:28.870 --> 00:06:31.890 align:start position:0% back a production system okay all right cool<00:06:29.530> and<00:06:29.800> so<00:06:30.040> I'm<00:06:30.190> kind<00:06:30.730> of<00:06:30.850> very<00:06:31.420> curious 00:06:31.890 --> 00:06:31.900 align:start position:0% cool and so I'm kind of very curious 00:06:31.900 --> 00:06:34.140 align:start position:0% cool and so I'm kind of very curious about<00:06:32.020> this<00:06:32.950> specialization 00:06:34.140 --> 00:06:34.150 align:start position:0% about this specialization 00:06:34.150 --> 00:06:36.270 align:start position:0% about this specialization right<00:06:34.360> so<00:06:34.540> not<00:06:35.020> only<00:06:35.170> we<00:06:35.380> get<00:06:35.530> a<00:06:35.620> bunch<00:06:35.890> of<00:06:36.070> em 00:06:36.270 --> 00:06:36.280 align:start position:0% right so not only we get a bunch of em 00:06:36.280 --> 00:06:39.000 align:start position:0% right so not only we get a bunch of em elopes<00:06:36.700> startups<00:06:37.600> dealing<00:06:38.470> with<00:06:38.560> other<00:06:38.800> BOTS 00:06:39.000 --> 00:06:39.010 align:start position:0% elopes startups dealing with other BOTS 00:06:39.010 --> 00:06:42.720 align:start position:0% elopes startups dealing with other BOTS now<00:06:39.160> have<00:06:39.490> you<00:06:40.030> know<00:06:40.830> monitoring<00:06:41.830> versioning 00:06:42.720 --> 00:06:42.730 align:start position:0% now have you know monitoring versioning 00:06:42.730 --> 00:06:45.810 align:start position:0% now have you know monitoring versioning and<00:06:42.880> tuning<00:06:43.570> as<00:06:44.110> specialties<00:06:44.830> of<00:06:45.130> different 00:06:45.810 --> 00:06:45.820 align:start position:0% and tuning as specialties of different 00:06:45.820 --> 00:06:47.940 align:start position:0% and tuning as specialties of different companies<00:06:46.150> so<00:06:46.330> do<00:06:46.810> you<00:06:46.900> think<00:06:47.260> and<00:06:47.560> obviously 00:06:47.940 --> 00:06:47.950 align:start position:0% companies so do you think and obviously 00:06:47.950 --> 00:06:49.280 align:start position:0% companies so do you think and obviously if<00:06:48.010> you<00:06:48.100> if<00:06:48.310> we<00:06:48.490> go<00:06:48.640> this<00:06:48.850> route<00:06:49.030> and 00:06:49.280 --> 00:06:49.290 align:start position:0% if you if we go this route and 00:06:49.290 --> 00:06:50.890 align:start position:0% if you if we go this route and standardization 00:06:50.890 --> 00:06:50.900 align:start position:0% standardization 00:06:50.900 --> 00:06:52.210 align:start position:0% standardization when<00:06:50.990> you<00:06:51.050> can<00:06:51.199> really<00:06:51.320> agree<00:06:51.830> what<00:06:52.070> these 00:06:52.210 --> 00:06:52.220 align:start position:0% when you can really agree what these 00:06:52.220 --> 00:06:54.159 align:start position:0% when you can really agree what these models<00:06:52.550> are<00:06:52.729> yeah<00:06:53.090> because<00:06:53.449> right<00:06:53.750> like<00:06:53.930> if<00:06:54.050> we 00:06:54.159 --> 00:06:54.169 align:start position:0% models are yeah because right like if we 00:06:54.169 --> 00:06:55.360 align:start position:0% models are yeah because right like if we really<00:06:54.229> want<00:06:54.530> be<00:06:54.620> like<00:06:54.650> do<00:06:55.009> you<00:06:55.100> think<00:06:55.280> it's 00:06:55.360 --> 00:06:55.370 align:start position:0% really want be like do you think it's 00:06:55.370 --> 00:06:57.400 align:start position:0% really want be like do you think it's going<00:06:55.520> that<00:06:55.699> way<00:06:55.850> that<00:06:56.180> you<00:06:56.360> know<00:06:56.660> we<00:06:56.810> have<00:06:56.990> or 00:06:57.400 --> 00:06:57.410 align:start position:0% going that way that you know we have or 00:06:57.410 --> 00:06:58.689 align:start position:0% going that way that you know we have or like<00:06:57.620> language<00:06:57.979> used<00:06:58.130> to<00:06:58.160> describe<00:06:58.220> it<00:06:58.610> and 00:06:58.689 --> 00:06:58.699 align:start position:0% like language used to describe it and 00:06:58.699 --> 00:07:00.520 align:start position:0% like language used to describe it and models<00:06:59.060> are<00:06:59.419> we<00:06:59.570> gonna<00:06:59.690> go<00:06:59.870> this<00:07:00.080> route<00:07:00.259> of 00:07:00.520 --> 00:07:00.530 align:start position:0% models are we gonna go this route of 00:07:00.530 --> 00:07:03.550 align:start position:0% models are we gonna go this route of kind<00:07:01.039> of<00:07:01.210> thousand<00:07:02.210> flowers<00:07:02.389> or<00:07:03.080> isn't<00:07:03.440> gonna 00:07:03.550 --> 00:07:03.560 align:start position:0% kind of thousand flowers or isn't gonna 00:07:03.560 --> 00:07:05.890 align:start position:0% kind of thousand flowers or isn't gonna be<00:07:03.650> polite<00:07:04.160> platforms<00:07:04.820> which<00:07:05.539> their<00:07:05.810> own 00:07:05.890 --> 00:07:05.900 align:start position:0% be polite platforms which their own 00:07:05.900 --> 00:07:08.520 align:start position:0% be polite platforms which their own clothes<00:07:06.199> tools<00:07:06.610> because<00:07:07.610> like<00:07:07.729> for<00:07:08.000> if<00:07:08.150> the<00:07:08.449> a 00:07:08.520 --> 00:07:08.530 align:start position:0% clothes tools because like for if the a 00:07:08.530 --> 00:07:10.719 align:start position:0% clothes tools because like for if the a standardization<00:07:09.530> and<00:07:09.919> open<00:07:10.250> market<00:07:10.550> them 00:07:10.719 --> 00:07:10.729 align:start position:0% standardization and open market them 00:07:10.729 --> 00:07:13.270 align:start position:0% standardization and open market them it's<00:07:11.090> really<00:07:11.570> good<00:07:11.750> for<00:07:11.870> star<00:07:12.020> laws<00:07:12.199> if<00:07:12.860> it's 00:07:13.270 --> 00:07:13.280 align:start position:0% it's really good for star laws if it's 00:07:13.280 --> 00:07:16.060 align:start position:0% it's really good for star laws if it's all<00:07:13.490> kind<00:07:13.850> of<00:07:13.910> inside<00:07:14.530> things<00:07:15.530> and<00:07:15.710> then<00:07:15.830> say 00:07:16.060 --> 00:07:16.070 align:start position:0% all kind of inside things and then say 00:07:16.070 --> 00:07:19.450 align:start position:0% all kind of inside things and then say sure<00:07:16.330> Amazon<00:07:17.330> and<00:07:17.750> Google<00:07:18.229> like<00:07:18.710> what<00:07:19.280> do<00:07:19.370> you 00:07:19.450 --> 00:07:19.460 align:start position:0% sure Amazon and Google like what do you 00:07:19.460 --> 00:07:20.920 align:start position:0% sure Amazon and Google like what do you think<00:07:19.610> this<00:07:19.729> is<00:07:19.970> going<00:07:20.180> I'm<00:07:20.449> going<00:07:20.630> to<00:07:20.720> see<00:07:20.810> my 00:07:20.920 --> 00:07:20.930 align:start position:0% think this is going I'm going to see my 00:07:20.930 --> 00:07:23.650 align:start position:0% think this is going I'm going to see my specialization<00:07:21.410> or<00:07:21.650> not<00:07:21.919> I<00:07:22.910> would<00:07:23.330> say<00:07:23.479> we're 00:07:23.650 --> 00:07:23.660 align:start position:0% specialization or not I would say we're 00:07:23.660 --> 00:07:25.750 align:start position:0% specialization or not I would say we're going<00:07:23.900> towards<00:07:24.139> standardization<00:07:24.710> and<00:07:25.490> we 00:07:25.750 --> 00:07:25.760 align:start position:0% going towards standardization and we 00:07:25.760 --> 00:07:26.980 align:start position:0% going towards standardization and we have<00:07:25.910> been<00:07:26.060> involved<00:07:26.389> in<00:07:26.600> some<00:07:26.810> of<00:07:26.840> these 00:07:26.980 --> 00:07:26.990 align:start position:0% have been involved in some of these 00:07:26.990 --> 00:07:29.110 align:start position:0% have been involved in some of these efforts<00:07:27.229> through<00:07:27.830> model<00:07:28.220> DB<00:07:28.520> through<00:07:28.880> verda 00:07:29.110 --> 00:07:29.120 align:start position:0% efforts through model DB through verda 00:07:29.120 --> 00:07:31.390 align:start position:0% efforts through model DB through verda where<00:07:29.840> we're<00:07:30.169> trying<00:07:30.289> to<00:07:30.440> find<00:07:30.740> what<00:07:31.190> does<00:07:31.370> a 00:07:31.390 --> 00:07:31.400 align:start position:0% where we're trying to find what does a 00:07:31.400 --> 00:07:33.400 align:start position:0% where we're trying to find what does a model<00:07:31.789> need<00:07:32.120> to<00:07:32.240> have<00:07:32.419> with<00:07:32.750> it<00:07:32.930> what<00:07:33.139> kind<00:07:33.350> of 00:07:33.400 --> 00:07:33.410 align:start position:0% model need to have with it what kind of 00:07:33.410 --> 00:07:35.260 align:start position:0% model need to have with it what kind of descriptors<00:07:33.979> doesn't<00:07:34.370> need<00:07:34.460> to<00:07:34.520> have<00:07:34.699> how 00:07:35.260 --> 00:07:35.270 align:start position:0% descriptors doesn't need to have how 00:07:35.270 --> 00:07:37.570 align:start position:0% descriptors doesn't need to have how does<00:07:35.479> a<00:07:35.510> model<00:07:35.900> package<00:07:36.620> get<00:07:36.949> defined<00:07:37.250> and 00:07:37.570 --> 00:07:37.580 align:start position:0% does a model package get defined and 00:07:37.580 --> 00:07:40.240 align:start position:0% does a model package get defined and things<00:07:37.699> like<00:07:37.820> that<00:07:37.880> so<00:07:38.570> I<00:07:38.960> don't<00:07:39.260> think<00:07:39.650> just 00:07:40.240 --> 00:07:40.250 align:start position:0% things like that so I don't think just 00:07:40.250 --> 00:07:42.610 align:start position:0% things like that so I don't think just as<00:07:40.460> in<00:07:40.880> software<00:07:41.330> we<00:07:41.479> now<00:07:41.780> have<00:07:42.020> reached<00:07:42.260> a 00:07:42.610 --> 00:07:42.620 align:start position:0% as in software we now have reached a 00:07:42.620 --> 00:07:44.620 align:start position:0% as in software we now have reached a conclusion<00:07:42.919> on<00:07:43.370> what<00:07:43.550> a<00:07:43.610> Jenkins<00:07:44.060> file<00:07:44.300> should 00:07:44.620 --> 00:07:44.630 align:start position:0% conclusion on what a Jenkins file should 00:07:44.630 --> 00:07:47.050 align:start position:0% conclusion on what a Jenkins file should look<00:07:44.810> like<00:07:45.010> so<00:07:46.010> we<00:07:46.400> are<00:07:46.610> going<00:07:46.820> to<00:07:46.880> approach 00:07:47.050 --> 00:07:47.060 align:start position:0% look like so we are going to approach 00:07:47.060 --> 00:07:48.700 align:start position:0% look like so we are going to approach that<00:07:47.150> stage<00:07:47.570> with<00:07:47.780> models<00:07:48.110> we're<00:07:48.410> just 00:07:48.700 --> 00:07:48.710 align:start position:0% that stage with models we're just 00:07:48.710 --> 00:07:50.860 align:start position:0% that stage with models we're just getting<00:07:49.370> there<00:07:49.520> slowly<00:07:49.699> and<00:07:50.180> the<00:07:50.300> startups<00:07:50.750> I 00:07:50.860 --> 00:07:50.870 align:start position:0% getting there slowly and the startups I 00:07:50.870 --> 00:07:52.629 align:start position:0% getting there slowly and the startups I think<00:07:51.080> are<00:07:51.229> providing<00:07:51.620> a<00:07:51.680> lot<00:07:51.830> of<00:07:51.860> impetus<00:07:52.250> for 00:07:52.629 --> 00:07:52.639 align:start position:0% think are providing a lot of impetus for 00:07:52.639 --> 00:07:55.300 align:start position:0% think are providing a lot of impetus for that<00:07:52.699> there's<00:07:53.180> gonna<00:07:53.300> be<00:07:53.389> a<00:07:53.449> bunch<00:07:53.599> of<00:07:53.690> llamó 00:07:55.300 --> 00:07:55.310 align:start position:0% that there's gonna be a bunch of llamó 00:07:55.310 --> 00:08:02.370 align:start position:0% that there's gonna be a bunch of llamó [Laughter] 00:08:02.370 --> 00:08:02.380 align:start position:0% 00:08:02.380 --> 00:08:05.080 align:start position:0% so<00:08:03.380> we<00:08:03.470> can<00:08:03.590> check<00:08:03.770> in<00:08:03.949> yeah<00:08:04.610> that<00:08:04.910> would<00:08:05.060> be 00:08:05.080 --> 00:08:05.090 align:start position:0% so we can check in yeah that would be 00:08:05.090 --> 00:08:05.740 align:start position:0% so we can check in yeah that would be wonderful 00:08:05.740 --> 00:08:05.750 align:start position:0% wonderful 00:08:05.750 --> 00:08:08.710 align:start position:0% wonderful very<00:08:06.289> wonderful<00:08:06.860> yes<00:08:07.190> yes<00:08:07.550> but<00:08:08.510> I<00:08:08.570> think 00:08:08.710 --> 00:08:08.720 align:start position:0% very wonderful yes yes but I think 00:08:08.720 --> 00:08:10.089 align:start position:0% very wonderful yes yes but I think Corinne<00:08:09.050> that<00:08:09.169> he<00:08:09.260> says<00:08:09.409> doesn't<00:08:09.770> really<00:08:09.889> got 00:08:10.089 --> 00:08:10.099 align:start position:0% Corinne that he says doesn't really got 00:08:10.099 --> 00:08:12.399 align:start position:0% Corinne that he says doesn't really got a<00:08:10.130> good<00:08:10.490> job<00:08:10.669> in<00:08:10.940> popularizing<00:08:11.360> yamo<00:08:11.930> as<00:08:12.229> well 00:08:12.399 --> 00:08:12.409 align:start position:0% a good job in popularizing yamo as well 00:08:12.409 --> 00:08:14.860 align:start position:0% a good job in popularizing yamo as well as<00:08:12.560> having<00:08:12.740> api's<00:08:13.220> and<00:08:13.639> we've<00:08:13.909> pulled<00:08:14.539> some<00:08:14.750> of 00:08:14.860 --> 00:08:14.870 align:start position:0% as having api's and we've pulled some of 00:08:14.870 --> 00:08:17.409 align:start position:0% as having api's and we've pulled some of those<00:08:15.020> designs<00:08:15.560> and<00:08:15.949> sort<00:08:16.159> of<00:08:16.250> ideas<00:08:17.240> from 00:08:17.409 --> 00:08:17.419 align:start position:0% those designs and sort of ideas from 00:08:17.419 --> 00:08:17.770 align:start position:0% those designs and sort of ideas from there 00:08:17.770 --> 00:08:17.780 align:start position:0% there 00:08:17.780 --> 00:08:20.469 align:start position:0% there we<00:08:17.870> seem<00:08:18.050> to<00:08:18.080> be<00:08:18.139> working<00:08:18.349> well<00:08:19.150> so<00:08:20.150> what<00:08:20.330> is 00:08:20.469 --> 00:08:20.479 align:start position:0% we seem to be working well so what is 00:08:20.479 --> 00:08:22.390 align:start position:0% we seem to be working well so what is the<00:08:20.630> hardest<00:08:20.960> challenge<00:08:21.020> for<00:08:21.590> you<00:08:21.710> and<00:08:22.039> you 00:08:22.390 --> 00:08:22.400 align:start position:0% the hardest challenge for you and you 00:08:22.400 --> 00:08:24.129 align:start position:0% the hardest challenge for you and you know<00:08:22.580> left<00:08:23.060> onto<00:08:23.270> the<00:08:23.389> next<00:08:23.570> year<00:08:23.900> were<00:08:24.020> like 00:08:24.129 --> 00:08:24.139 align:start position:0% know left onto the next year were like 00:08:24.139 --> 00:08:26.350 align:start position:0% know left onto the next year were like what's<00:08:24.349> the<00:08:24.470> your<00:08:24.800> current<00:08:25.250> you<00:08:26.120> know<00:08:26.150> what 00:08:26.350 --> 00:08:26.360 align:start position:0% what's the your current you know what 00:08:26.360 --> 00:08:27.580 align:start position:0% what's the your current you know what keeps<00:08:26.570> you<00:08:26.690> up<00:08:26.750> at<00:08:26.870> night<00:08:26.930> what<00:08:27.320> do<00:08:27.409> you<00:08:27.470> want 00:08:27.580 --> 00:08:27.590 align:start position:0% keeps you up at night what do you want 00:08:27.590 --> 00:08:30.100 align:start position:0% keeps you up at night what do you want to<00:08:27.710> solve<00:08:28.280> with<00:08:28.639> this<00:08:28.909> kind<00:08:29.419> of<00:08:29.510> coming<00:08:29.870> year 00:08:30.100 --> 00:08:30.110 align:start position:0% to solve with this kind of coming year 00:08:30.110 --> 00:08:32.230 align:start position:0% to solve with this kind of coming year for<00:08:30.139> Virgil<00:08:30.789> when<00:08:31.789> you're<00:08:31.909> a<00:08:31.970> small<00:08:32.209> start-up 00:08:32.230 --> 00:08:32.240 align:start position:0% for Virgil when you're a small start-up 00:08:32.240 --> 00:08:34.269 align:start position:0% for Virgil when you're a small start-up there's<00:08:32.750> lots<00:08:32.990> of<00:08:33.080> challenges<00:08:33.260> as<00:08:33.919> you<00:08:34.070> might 00:08:34.269 --> 00:08:34.279 align:start position:0% there's lots of challenges as you might 00:08:34.279 --> 00:08:36.670 align:start position:0% there's lots of challenges as you might imagine<00:08:34.510> this<00:08:35.510> move<00:08:35.810> this<00:08:36.110> field<00:08:36.260> moves<00:08:36.560> very 00:08:36.670 --> 00:08:36.680 align:start position:0% imagine this move this field moves very 00:08:36.680 --> 00:08:38.860 align:start position:0% imagine this move this field moves very fast<00:08:36.800> as<00:08:37.400> you<00:08:37.520> might<00:08:37.669> imagine<00:08:37.789> and<00:08:38.539> so<00:08:38.690> there's 00:08:38.860 --> 00:08:38.870 align:start position:0% fast as you might imagine and so there's 00:08:38.870 --> 00:08:41.440 align:start position:0% fast as you might imagine and so there's always<00:08:39.050> either<00:08:39.950> a<00:08:40.130> new<00:08:40.550> algorithm<00:08:40.849> you'd<00:08:41.270> have 00:08:41.440 --> 00:08:41.450 align:start position:0% always either a new algorithm you'd have 00:08:41.450 --> 00:08:44.079 align:start position:0% always either a new algorithm you'd have of<00:08:41.539> doing<00:08:41.690> things<00:08:42.110> or<00:08:42.700> there<00:08:43.700> are<00:08:43.880> new 00:08:44.079 --> 00:08:44.089 align:start position:0% of doing things or there are new 00:08:44.089 --> 00:08:46.269 align:start position:0% of doing things or there are new companies<00:08:44.480> out<00:08:44.690> there<00:08:44.720> so<00:08:45.230> for<00:08:45.860> us<00:08:46.040> it's 00:08:46.269 --> 00:08:46.279 align:start position:0% companies out there so for us it's 00:08:46.279 --> 00:08:48.790 align:start position:0% companies out there so for us it's always<00:08:46.520> finding<00:08:47.209> what<00:08:48.020> is<00:08:48.140> the<00:08:48.320> thing<00:08:48.529> that<00:08:48.560> we 00:08:48.790 --> 00:08:48.800 align:start position:0% always finding what is the thing that we 00:08:48.800 --> 00:08:51.010 align:start position:0% always finding what is the thing that we can<00:08:48.980> do<00:08:49.130> especially<00:08:49.459> well<00:08:49.940> compared<00:08:50.480> to<00:08:50.510> other 00:08:51.010 --> 00:08:51.020 align:start position:0% can do especially well compared to other 00:08:51.020 --> 00:08:53.710 align:start position:0% can do especially well compared to other companies<00:08:51.980> and<00:08:52.430> at<00:08:53.000> the<00:08:53.120> end<00:08:53.240> of<00:08:53.330> the<00:08:53.390> day<00:08:53.510> for 00:08:53.710 --> 00:08:53.720 align:start position:0% companies and at the end of the day for 00:08:53.720 --> 00:08:55.570 align:start position:0% companies and at the end of the day for us<00:08:53.900> are<00:08:54.140> we<00:08:54.529> making<00:08:54.890> a<00:08:55.010> difference<00:08:55.040> for<00:08:55.400> the 00:08:55.570 --> 00:08:55.580 align:start position:0% us are we making a difference for the 00:08:55.580 --> 00:08:57.910 align:start position:0% us are we making a difference for the customers<00:08:55.940> that<00:08:56.000> we<00:08:56.120> work<00:08:56.390> for<00:08:56.560> if<00:08:57.560> we're 00:08:57.910 --> 00:08:57.920 align:start position:0% customers that we work for if we're 00:08:57.920 --> 00:08:59.510 align:start position:0% customers that we work for if we're moving<00:08:58.220> the<00:08:58.310> needle<00:08:58.459> for<00:08:58.730> them<00:08:58.880> then<00:08:59.180> that's 00:08:59.510 --> 00:08:59.520 align:start position:0% moving the needle for them then that's 00:08:59.520 --> 00:09:00.980 align:start position:0% moving the needle for them then that's a<00:08:59.550> huge<00:08:59.760> one<00:08:59.910> for<00:08:59.970> us<00:09:00.210> and<00:09:00.450> that's<00:09:00.600> what<00:09:00.780> we'll 00:09:00.980 --> 00:09:00.990 align:start position:0% a huge one for us and that's what we'll 00:09:00.990 --> 00:09:03.320 align:start position:0% a huge one for us and that's what we'll focus<00:09:01.350> on<00:09:01.500> sounds<00:09:02.430> awesome<00:09:02.580> we<00:09:02.880> wish<00:09:03.030> you<00:09:03.150> all 00:09:03.320 --> 00:09:03.330 align:start position:0% focus on sounds awesome we wish you all 00:09:03.330 --> 00:09:04.460 align:start position:0% focus on sounds awesome we wish you all the<00:09:03.360> luck<00:09:03.630> and<00:09:03.660> they're<00:09:03.930> looking<00:09:04.200> forward<00:09:04.380> to 00:09:04.460 --> 00:09:04.470 align:start position:0% the luck and they're looking forward to 00:09:04.470 --> 00:09:08.040 align:start position:0% the luck and they're looking forward to my<00:09:04.620> talk<00:09:04.830> thank<00:09:05.340> you<00:09:05.430> very<00:09:05.550> much<00:09:05.730> thank<00:09:06.060> you 00:09:08.040 --> 00:09:08.050 align:start position:0% my talk thank you very much thank you 00:09:08.050 --> 00:09:11.179 align:start position:0% my talk thank you very much thank you [Music]