WEBVTT Kind: captions Language: en 00:00:15.559 --> 00:00:17.950 align:start position:0% hello<00:00:15.799> everybody<00:00:16.480> this<00:00:16.600> is<00:00:16.800> SF<00:00:17.199> text<00:00:17.760> this<00:00:17.880> is 00:00:17.950 --> 00:00:17.960 align:start position:0% hello everybody this is SF text this is 00:00:17.960 --> 00:00:20.029 align:start position:0% hello everybody this is SF text this is our<00:00:18.160> first<00:00:18.439> inaugural<00:00:18.920> metop<00:00:19.640> we're<00:00:19.840> on 00:00:20.029 --> 00:00:20.039 align:start position:0% our first inaugural metop we're on 00:00:20.039 --> 00:00:23.230 align:start position:0% our first inaugural metop we're on location<00:00:20.400> at<00:00:20.560> viglink<00:00:21.560> in<00:00:21.680> San<00:00:21.920> Francisco<00:00:22.640> and 00:00:23.230 --> 00:00:23.240 align:start position:0% location at viglink in San Francisco and 00:00:23.240 --> 00:00:25.429 align:start position:0% location at viglink in San Francisco and uh<00:00:23.560> one<00:00:23.760> of<00:00:23.880> our<00:00:24.119> speakers<00:00:24.560> tonight<00:00:25.000> is<00:00:25.199> gr 00:00:25.429 --> 00:00:25.439 align:start position:0% uh one of our speakers tonight is gr 00:00:25.439 --> 00:00:28.310 align:start position:0% uh one of our speakers tonight is gr anderol<00:00:26.439> the<00:00:26.519> CTO<00:00:26.920> of<00:00:27.000> lucid<00:00:27.320> Works<00:00:28.039> uh<00:00:28.160> the 00:00:28.310 --> 00:00:28.320 align:start position:0% anderol the CTO of lucid Works uh the 00:00:28.320 --> 00:00:31.749 align:start position:0% anderol the CTO of lucid Works uh the company<00:00:28.720> behind<00:00:29.359> uh<00:00:29.480> solar<00:00:30.199> and<00:00:30.439> Lucine<00:00:31.439> and 00:00:31.749 --> 00:00:31.759 align:start position:0% company behind uh solar and Lucine and 00:00:31.759 --> 00:00:34.910 align:start position:0% company behind uh solar and Lucine and as<00:00:32.119> uh<00:00:32.480> many<00:00:32.680> of<00:00:32.840> you<00:00:33.200> know<00:00:33.840> Lucine<00:00:34.280> is<00:00:34.440> mostly 00:00:34.910 --> 00:00:34.920 align:start position:0% as uh many of you know Lucine is mostly 00:00:34.920 --> 00:00:37.310 align:start position:0% as uh many of you know Lucine is mostly widely<00:00:35.239> used<00:00:35.520> and<00:00:35.719> deployed<00:00:36.200> open-<00:00:36.520> Source 00:00:37.310 --> 00:00:37.320 align:start position:0% widely used and deployed open- Source 00:00:37.320 --> 00:00:40.069 align:start position:0% widely used and deployed open- Source search<00:00:37.840> engine<00:00:38.840> uh<00:00:39.200> almost<00:00:39.520> every<00:00:39.760> company 00:00:40.069 --> 00:00:40.079 align:start position:0% search engine uh almost every company 00:00:40.079 --> 00:00:42.470 align:start position:0% search engine uh almost every company which<00:00:40.239> wants<00:00:40.480> to<00:00:40.640> have<00:00:40.800> search<00:00:41.120> on<00:00:41.280> their<00:00:41.520> site 00:00:42.470 --> 00:00:42.480 align:start position:0% which wants to have search on their site 00:00:42.480 --> 00:00:46.830 align:start position:0% which wants to have search on their site has<00:00:42.719> Lucen<00:00:43.600> somewhere<00:00:44.600> uh<00:00:44.800> so<00:00:45.800> uh<00:00:46.360> I<00:00:46.440> want<00:00:46.640> to 00:00:46.830 --> 00:00:46.840 align:start position:0% has Lucen somewhere uh so uh I want to 00:00:46.840 --> 00:00:48.830 align:start position:0% has Lucen somewhere uh so uh I want to ask<00:00:47.239> uh<00:00:47.360> first<00:00:47.520> of<00:00:47.559> all<00:00:47.719> welcome<00:00:48.000> Grant<00:00:48.680> thank 00:00:48.830 --> 00:00:48.840 align:start position:0% ask uh first of all welcome Grant thank 00:00:48.840 --> 00:00:51.350 align:start position:0% ask uh first of all welcome Grant thank you<00:00:49.199> glad<00:00:49.360> to<00:00:49.480> be<00:00:49.600> here<00:00:50.160> uh<00:00:50.320> it's<00:00:50.559> a<00:00:50.840> I<00:00:50.920> think 00:00:51.350 --> 00:00:51.360 align:start position:0% you glad to be here uh it's a I think 00:00:51.360 --> 00:00:53.630 align:start position:0% you glad to be here uh it's a I think search<00:00:51.879> is<00:00:52.239> a<00:00:52.480> common<00:00:52.760> theme<00:00:52.960> in<00:00:53.120> all<00:00:53.320> kind<00:00:53.480> of 00:00:53.630 --> 00:00:53.640 align:start position:0% search is a common theme in all kind of 00:00:53.640 --> 00:00:56.470 align:start position:0% search is a common theme in all kind of text<00:00:54.079> applications<00:00:54.800> and<00:00:55.320> our<00:00:55.840> general<00:00:56.239> theme 00:00:56.470 --> 00:00:56.480 align:start position:0% text applications and our general theme 00:00:56.480 --> 00:00:58.990 align:start position:0% text applications and our general theme is<00:00:56.680> text<00:00:57.399> everybody<00:00:57.760> needs<00:00:58.000> to<00:00:58.199> find<00:00:58.719> some 00:00:58.990 --> 00:00:59.000 align:start position:0% is text everybody needs to find some 00:00:59.000 --> 00:01:01.389 align:start position:0% is text everybody needs to find some some<00:00:59.199> text<00:00:59.600> there<00:01:00.039> looking<00:01:00.239> for<00:01:00.960> first<00:01:01.160> I<00:01:01.239> want 00:01:01.389 --> 00:01:01.399 align:start position:0% some text there looking for first I want 00:01:01.399 --> 00:01:04.350 align:start position:0% some text there looking for first I want to<00:01:01.559> ask<00:01:01.719> you<00:01:02.199> uh<00:01:02.559> how<00:01:03.160> did<00:01:03.359> you<00:01:03.879> uh<00:01:04.000> come<00:01:04.159> to 00:01:04.350 --> 00:01:04.360 align:start position:0% to ask you uh how did you uh come to 00:01:04.360 --> 00:01:07.149 align:start position:0% to ask you uh how did you uh come to Lucine<00:01:05.040> and<00:01:05.239> and<00:01:05.360> solar<00:01:06.200> in<00:01:06.320> the<00:01:06.479> first<00:01:06.799> place 00:01:07.149 --> 00:01:07.159 align:start position:0% Lucine and and solar in the first place 00:01:07.159 --> 00:01:09.749 align:start position:0% Lucine and and solar in the first place and<00:01:07.600> how<00:01:07.799> this<00:01:08.040> interest<00:01:08.479> evolved<00:01:09.080> over 00:01:09.749 --> 00:01:09.759 align:start position:0% and how this interest evolved over 00:01:09.759 --> 00:01:12.390 align:start position:0% and how this interest evolved over several<00:01:10.159> years<00:01:10.479> to<00:01:11.000> to<00:01:11.159> become<00:01:11.400> a<00:01:11.560> company<00:01:12.240> uh 00:01:12.390 --> 00:01:12.400 align:start position:0% several years to to become a company uh 00:01:12.400 --> 00:01:14.990 align:start position:0% several years to to become a company uh what's<00:01:12.600> the<00:01:12.759> trajectory<00:01:13.759> yeah<00:01:14.200> no<00:01:14.400> it's<00:01:14.680> a 00:01:14.990 --> 00:01:15.000 align:start position:0% what's the trajectory yeah no it's a 00:01:15.000 --> 00:01:16.270 align:start position:0% what's the trajectory yeah no it's a it's<00:01:15.119> a<00:01:15.240> great<00:01:15.479> question<00:01:15.680> I<00:01:15.759> mean<00:01:16.080> I<00:01:16.159> think 00:01:16.270 --> 00:01:16.280 align:start position:0% it's a great question I mean I think 00:01:16.280 --> 00:01:17.830 align:start position:0% it's a great question I mean I think you're<00:01:16.479> dead<00:01:16.680> on<00:01:16.840> that<00:01:16.960> Lucine<00:01:17.320> and<00:01:17.400> solar 00:01:17.830 --> 00:01:17.840 align:start position:0% you're dead on that Lucine and solar 00:01:17.840 --> 00:01:20.510 align:start position:0% you're dead on that Lucine and solar have<00:01:18.479> grown<00:01:18.880> so<00:01:19.080> much<00:01:19.520> uh<00:01:19.680> my<00:01:19.960> my<00:01:20.119> personal 00:01:20.510 --> 00:01:20.520 align:start position:0% have grown so much uh my my personal 00:01:20.520 --> 00:01:22.789 align:start position:0% have grown so much uh my my personal history<00:01:20.840> is<00:01:21.000> I<00:01:21.200> started<00:01:22.079> I<00:01:22.159> used<00:01:22.320> to<00:01:22.439> live<00:01:22.640> up 00:01:22.789 --> 00:01:22.799 align:start position:0% history is I started I used to live up 00:01:22.799 --> 00:01:24.870 align:start position:0% history is I started I used to live up in<00:01:23.079> uh<00:01:23.200> Syracuse<00:01:23.759> New<00:01:23.920> York<00:01:24.200> and<00:01:24.320> if<00:01:24.439> anybody's 00:01:24.870 --> 00:01:24.880 align:start position:0% in uh Syracuse New York and if anybody's 00:01:24.880 --> 00:01:26.069 align:start position:0% in uh Syracuse New York and if anybody's familiar<00:01:25.200> with<00:01:25.360> that<00:01:25.560> there<00:01:25.720> they<00:01:25.880> know 00:01:26.069 --> 00:01:26.079 align:start position:0% familiar with that there they know 00:01:26.079 --> 00:01:28.469 align:start position:0% familiar with that there they know Syracuse<00:01:26.640> University<00:01:27.439> which<00:01:27.840> uh<00:01:28.079> Dr 00:01:28.469 --> 00:01:28.479 align:start position:0% Syracuse University which uh Dr 00:01:28.479 --> 00:01:30.910 align:start position:0% Syracuse University which uh Dr Elizabeth<00:01:28.920> lyy<00:01:29.720> who<00:01:29.920> who<00:01:30.040> is<00:01:30.159> a<00:01:30.520> pretty<00:01:30.759> big 00:01:30.910 --> 00:01:30.920 align:start position:0% Elizabeth lyy who who is a pretty big 00:01:30.920 --> 00:01:33.190 align:start position:0% Elizabeth lyy who who is a pretty big name<00:01:31.159> in<00:01:31.400> the<00:01:31.880> the<00:01:32.040> text<00:01:32.320> in<00:01:32.479> natural<00:01:32.840> language 00:01:33.190 --> 00:01:33.200 align:start position:0% name in the the text in natural language 00:01:33.200 --> 00:01:34.950 align:start position:0% name in the the text in natural language processing<00:01:33.600> field<00:01:33.960> she<00:01:34.079> had<00:01:34.240> a<00:01:34.360> company<00:01:34.720> there 00:01:34.950 --> 00:01:34.960 align:start position:0% processing field she had a company there 00:01:34.960 --> 00:01:37.789 align:start position:0% processing field she had a company there called<00:01:35.240> text<00:01:35.680> wise<00:01:36.680> which<00:01:37.280> uh<00:01:37.479> happened<00:01:37.720> to 00:01:37.789 --> 00:01:37.799 align:start position:0% called text wise which uh happened to 00:01:37.799 --> 00:01:39.670 align:start position:0% called text wise which uh happened to have<00:01:37.960> a<00:01:38.119> job<00:01:38.320> when<00:01:38.520> I<00:01:38.640> was<00:01:38.799> looking<00:01:39.040> for<00:01:39.200> a<00:01:39.399> job 00:01:39.670 --> 00:01:39.680 align:start position:0% have a job when I was looking for a job 00:01:39.680 --> 00:01:41.789 align:start position:0% have a job when I was looking for a job I<00:01:39.759> had<00:01:39.840> never<00:01:40.040> done<00:01:40.360> text<00:01:40.840> in<00:01:41.280> college<00:01:41.640> or 00:01:41.789 --> 00:01:41.799 align:start position:0% I had never done text in college or 00:01:41.799 --> 00:01:44.950 align:start position:0% I had never done text in college or anything<00:01:42.200> like<00:01:42.439> that<00:01:43.240> uh<00:01:43.439> got<00:01:43.640> hired<00:01:43.960> to<00:01:44.200> build 00:01:44.950 --> 00:01:44.960 align:start position:0% anything like that uh got hired to build 00:01:44.960 --> 00:01:47.749 align:start position:0% anything like that uh got hired to build uh<00:01:45.759> a<00:01:46.000> cross<00:01:46.399> language<00:01:46.840> search<00:01:47.280> system 00:01:47.749 --> 00:01:47.759 align:start position:0% uh a cross language search system 00:01:47.759 --> 00:01:50.590 align:start position:0% uh a cross language search system between<00:01:48.360> English<00:01:49.079> French<00:01:49.520> German<00:01:50.079> Spanish 00:01:50.590 --> 00:01:50.600 align:start position:0% between English French German Spanish 00:01:50.600 --> 00:01:51.350 align:start position:0% between English French German Spanish and 00:01:51.350 --> 00:01:51.360 align:start position:0% and 00:01:51.360 --> 00:01:54.910 align:start position:0% and Japanese<00:01:52.360> uh<00:01:52.479> we<00:01:52.640> used<00:01:53.200> Oracle<00:01:54.079> context 00:01:54.910 --> 00:01:54.920 align:start position:0% Japanese uh we used Oracle context 00:01:54.920 --> 00:01:57.870 align:start position:0% Japanese uh we used Oracle context search<00:01:55.759> this<00:01:55.880> is<00:01:56.079> back<00:01:56.240> in<00:01:56.439> like 00:01:57.870 --> 00:01:57.880 align:start position:0% search this is back in like 00:01:57.880 --> 00:02:01.190 align:start position:0% search this is back in like 1999<00:01:58.880> I<00:01:59.000> believe<00:02:00.159> uh<00:02:00.399> so<00:02:00.600> that's<00:02:00.840> kind<00:02:00.920> of<00:02:01.039> my 00:02:01.190 --> 00:02:01.200 align:start position:0% 1999 I believe uh so that's kind of my 00:02:01.200 --> 00:02:04.429 align:start position:0% 1999 I believe uh so that's kind of my first<00:02:01.399> foray<00:02:01.920> into<00:02:02.200> search<00:02:02.479> in<00:02:02.680> NLP<00:02:03.560> Flash 00:02:04.429 --> 00:02:04.439 align:start position:0% first foray into search in NLP Flash 00:02:04.439 --> 00:02:10.469 align:start position:0% first foray into search in NLP Flash Forward<00:02:05.439> uh<00:02:05.840> to<00:02:07.160> 2004<00:02:08.160> I<00:02:08.360> had<00:02:08.599> left<00:02:09.599> text<00:02:10.080> wise 00:02:10.469 --> 00:02:10.479 align:start position:0% Forward uh to 2004 I had left text wise 00:02:10.479 --> 00:02:12.150 align:start position:0% Forward uh to 2004 I had left text wise went<00:02:10.720> off<00:02:10.920> and<00:02:11.120> did<00:02:11.319> some<00:02:11.520> other<00:02:11.800> stuff<00:02:12.040> and 00:02:12.150 --> 00:02:12.160 align:start position:0% went off and did some other stuff and 00:02:12.160 --> 00:02:15.190 align:start position:0% went off and did some other stuff and then<00:02:12.400> came<00:02:12.720> back<00:02:13.000> to<00:02:13.319> work<00:02:13.599> for<00:02:13.840> Liz<00:02:14.360> again<00:02:14.879> at 00:02:15.190 --> 00:02:15.200 align:start position:0% then came back to work for Liz again at 00:02:15.200 --> 00:02:17.190 align:start position:0% then came back to work for Liz again at the<00:02:15.760> University<00:02:16.400> this<00:02:16.560> time<00:02:16.720> in<00:02:16.840> a<00:02:17.000> place 00:02:17.190 --> 00:02:17.200 align:start position:0% the University this time in a place 00:02:17.200 --> 00:02:19.030 align:start position:0% the University this time in a place called<00:02:17.400> the<00:02:17.519> center<00:02:17.760> for<00:02:18.000> natural<00:02:18.360> language 00:02:19.030 --> 00:02:19.040 align:start position:0% called the center for natural language 00:02:19.040 --> 00:02:21.830 align:start position:0% called the center for natural language processing<00:02:20.040> I<00:02:20.120> was<00:02:20.280> hired<00:02:20.640> to<00:02:20.920> build<00:02:21.319> a 00:02:21.830 --> 00:02:21.840 align:start position:0% processing I was hired to build a 00:02:21.840 --> 00:02:23.910 align:start position:0% processing I was hired to build a English<00:02:22.280> Arabic<00:02:22.800> cross<00:02:23.160> language<00:02:23.519> search 00:02:23.910 --> 00:02:23.920 align:start position:0% English Arabic cross language search 00:02:23.920 --> 00:02:25.910 align:start position:0% English Arabic cross language search system<00:02:24.599> this<00:02:24.800> time<00:02:25.080> you<00:02:25.200> can<00:02:25.400> guess<00:02:25.599> who<00:02:25.760> was 00:02:25.910 --> 00:02:25.920 align:start position:0% system this time you can guess who was 00:02:25.920 --> 00:02:28.710 align:start position:0% system this time you can guess who was paying<00:02:26.200> for<00:02:26.400> that<00:02:26.760> right<00:02:27.319> and<00:02:27.879> uh<00:02:28.239> I<00:02:28.360> walked<00:02:28.599> in 00:02:28.710 --> 00:02:28.720 align:start position:0% paying for that right and uh I walked in 00:02:28.720 --> 00:02:30.309 align:start position:0% paying for that right and uh I walked in the<00:02:28.840> door<00:02:29.120> my<00:02:29.239> boss<00:02:29.440> said<00:02:29.640> hey<00:02:29.920> we<00:02:30.000> use<00:02:30.200> this 00:02:30.309 --> 00:02:30.319 align:start position:0% the door my boss said hey we use this 00:02:30.319 --> 00:02:32.270 align:start position:0% the door my boss said hey we use this thing<00:02:30.519> called<00:02:30.720> Lucine<00:02:31.319> I<00:02:31.400> said<00:02:31.680> great<00:02:31.959> let<00:02:32.080> me 00:02:32.270 --> 00:02:32.280 align:start position:0% thing called Lucine I said great let me 00:02:32.280 --> 00:02:35.509 align:start position:0% thing called Lucine I said great let me go<00:02:32.760> uh<00:02:32.879> look<00:02:33.040> up<00:02:33.239> what<00:02:33.440> that<00:02:33.720> is<00:02:34.720> and<00:02:35.360> uh 00:02:35.509 --> 00:02:35.519 align:start position:0% go uh look up what that is and uh 00:02:35.519 --> 00:02:38.070 align:start position:0% go uh look up what that is and uh started<00:02:36.200> playing<00:02:36.519> around<00:02:36.840> with<00:02:36.959> it<00:02:37.280> as<00:02:37.440> I<00:02:37.760> as<00:02:37.920> I 00:02:38.070 --> 00:02:38.080 align:start position:0% started playing around with it as I as I 00:02:38.080 --> 00:02:40.229 align:start position:0% started playing around with it as I as I started<00:02:38.360> building<00:02:38.760> out<00:02:39.040> this<00:02:39.319> system 00:02:40.229 --> 00:02:40.239 align:start position:0% started building out this system 00:02:40.239 --> 00:02:42.509 align:start position:0% started building out this system realized<00:02:40.760> that<00:02:40.920> I<00:02:41.040> needed<00:02:41.440> some<00:02:41.720> things<00:02:42.239> in 00:02:42.509 --> 00:02:42.519 align:start position:0% realized that I needed some things in 00:02:42.519 --> 00:02:45.270 align:start position:0% realized that I needed some things in Lucine<00:02:43.280> that<00:02:43.440> weren't<00:02:43.879> there<00:02:44.800> uh<00:02:44.959> started 00:02:45.270 --> 00:02:45.280 align:start position:0% Lucine that weren't there uh started 00:02:45.280 --> 00:02:47.910 align:start position:0% Lucine that weren't there uh started submitting<00:02:46.040> patches<00:02:47.040> and<00:02:47.360> kind<00:02:47.480> of<00:02:47.599> the<00:02:47.720> rest 00:02:47.910 --> 00:02:47.920 align:start position:0% submitting patches and kind of the rest 00:02:47.920 --> 00:02:50.670 align:start position:0% submitting patches and kind of the rest is<00:02:48.200> history<00:02:48.680> if<00:02:49.000> if<00:02:49.120> you<00:02:49.280> will<00:02:50.200> uh<00:02:50.319> Flash 00:02:50.670 --> 00:02:50.680 align:start position:0% is history if if you will uh Flash 00:02:50.680 --> 00:02:52.070 align:start position:0% is history if if you will uh Flash Forward<00:02:51.000> to 00:02:52.070 --> 00:02:52.080 align:start position:0% Forward to 00:02:52.080 --> 00:02:54.750 align:start position:0% Forward to 2007<00:02:53.080> founded<00:02:53.519> Lucid<00:02:53.959> Works<00:02:54.319> around<00:02:54.560> the 00:02:54.750 --> 00:02:54.760 align:start position:0% 2007 founded Lucid Works around the 00:02:54.760 --> 00:02:56.910 align:start position:0% 2007 founded Lucid Works around the premise<00:02:55.159> of<00:02:55.920> commercializing<00:02:56.720> the 00:02:56.910 --> 00:02:56.920 align:start position:0% premise of commercializing the 00:02:56.920 --> 00:02:59.830 align:start position:0% premise of commercializing the capabilities<00:02:57.680> around<00:02:58.200> solar<00:02:58.680> and<00:02:58.800> Lucine<00:02:59.440> and 00:02:59.830 --> 00:02:59.840 align:start position:0% capabilities around solar and Lucine and 00:02:59.840 --> 00:03:01.470 align:start position:0% capabilities around solar and Lucine and providing<00:03:00.280> product<00:03:00.599> and<00:03:00.760> all<00:03:00.920> of<00:03:01.080> that<00:03:01.360> kind 00:03:01.470 --> 00:03:01.480 align:start position:0% providing product and all of that kind 00:03:01.480 --> 00:03:04.270 align:start position:0% providing product and all of that kind of<00:03:01.760> on<00:03:02.080> top<00:03:02.280> of<00:03:02.440> it<00:03:03.040> and<00:03:03.200> of<00:03:03.360> course<00:03:03.599> it's<00:03:03.799> all 00:03:04.270 --> 00:03:04.280 align:start position:0% of on top of it and of course it's all 00:03:04.280 --> 00:03:07.589 align:start position:0% of on top of it and of course it's all exploded<00:03:04.959> since<00:03:05.319> then<00:03:05.680> as<00:03:05.840> well<00:03:06.599> so<00:03:07.200> a<00:03:07.280> lot<00:03:07.440> of 00:03:07.589 --> 00:03:07.599 align:start position:0% exploded since then as well so a lot of 00:03:07.599 --> 00:03:09.789 align:start position:0% exploded since then as well so a lot of luck<00:03:08.400> uh<00:03:08.640> right<00:03:08.840> place<00:03:09.159> right<00:03:09.360> time<00:03:09.560> and<00:03:09.720> a 00:03:09.789 --> 00:03:09.799 align:start position:0% luck uh right place right time and a 00:03:09.799 --> 00:03:12.190 align:start position:0% luck uh right place right time and a bunch<00:03:09.959> of<00:03:10.080> hard<00:03:10.280> work<00:03:10.599> as<00:03:10.760> well<00:03:11.200> but<00:03:11.920> that's 00:03:12.190 --> 00:03:12.200 align:start position:0% bunch of hard work as well but that's 00:03:12.200 --> 00:03:14.190 align:start position:0% bunch of hard work as well but that's great<00:03:12.640> yeah<00:03:12.799> I<00:03:12.920> remember<00:03:13.280> I<00:03:13.360> think<00:03:13.560> I<00:03:13.920> first 00:03:14.190 --> 00:03:14.200 align:start position:0% great yeah I remember I think I first 00:03:14.200 --> 00:03:18.430 align:start position:0% great yeah I remember I think I first saw<00:03:14.440> your<00:03:14.680> talk<00:03:15.400> at<00:03:15.640> Hado<00:03:16.000> Summit<00:03:16.360> in<00:03:17.200> 2012<00:03:18.200> and 00:03:18.430 --> 00:03:18.440 align:start position:0% saw your talk at Hado Summit in 2012 and 00:03:18.440 --> 00:03:19.949 align:start position:0% saw your talk at Hado Summit in 2012 and that<00:03:18.560> was<00:03:18.760> already<00:03:19.040> in<00:03:19.159> the<00:03:19.280> business<00:03:19.599> context 00:03:19.949 --> 00:03:19.959 align:start position:0% that was already in the business context 00:03:19.959 --> 00:03:22.550 align:start position:0% that was already in the business context and<00:03:20.080> you<00:03:20.280> basically<00:03:21.040> outline<00:03:21.720> big<00:03:22.159> picture 00:03:22.550 --> 00:03:22.560 align:start position:0% and you basically outline big picture 00:03:22.560 --> 00:03:24.550 align:start position:0% and you basically outline big picture and<00:03:22.799> big<00:03:23.000> compon<00:03:23.480> components<00:03:23.920> of<00:03:24.040> big<00:03:24.239> data<00:03:24.440> so 00:03:24.550 --> 00:03:24.560 align:start position:0% and big compon components of big data so 00:03:24.560 --> 00:03:27.750 align:start position:0% and big compon components of big data so it's<00:03:25.080> clearly<00:03:26.080> when<00:03:26.280> people<00:03:26.519> think<00:03:26.799> big<00:03:27.040> data 00:03:27.750 --> 00:03:27.760 align:start position:0% it's clearly when people think big data 00:03:27.760 --> 00:03:30.670 align:start position:0% it's clearly when people think big data solar<00:03:28.120> Lucin<00:03:28.519> comes<00:03:28.760> up<00:03:29.159> now<00:03:29.920> and<00:03:30.239> uh<00:03:30.400> so<00:03:30.560> I 00:03:30.670 --> 00:03:30.680 align:start position:0% solar Lucin comes up now and uh so I 00:03:30.680 --> 00:03:33.429 align:start position:0% solar Lucin comes up now and uh so I wonder<00:03:31.040> how<00:03:31.239> do<00:03:31.360> you<00:03:31.599> go<00:03:32.000> from<00:03:32.599> Lucine<00:03:33.239> which 00:03:33.429 --> 00:03:33.439 align:start position:0% wonder how do you go from Lucine which 00:03:33.439 --> 00:03:36.149 align:start position:0% wonder how do you go from Lucine which runs<00:03:33.680> on<00:03:33.879> single<00:03:34.200> Noe<00:03:34.560> to<00:03:34.760> solar<00:03:35.319> and<00:03:35.760> what<00:03:35.920> is 00:03:36.149 --> 00:03:36.159 align:start position:0% runs on single Noe to solar and what is 00:03:36.159 --> 00:03:38.710 align:start position:0% runs on single Noe to solar and what is the<00:03:36.439> landscape<00:03:37.000> in<00:03:37.120> terms<00:03:37.439> of<00:03:38.319> uh<00:03:38.560> uh 00:03:38.710 --> 00:03:38.720 align:start position:0% the landscape in terms of uh uh 00:03:38.720 --> 00:03:40.789 align:start position:0% the landscape in terms of uh uh distributed<00:03:39.280> systems<00:03:39.920> and<00:03:40.120> how<00:03:40.280> do<00:03:40.400> you<00:03:40.519> see 00:03:40.789 --> 00:03:40.799 align:start position:0% distributed systems and how do you see 00:03:40.799 --> 00:03:43.509 align:start position:0% distributed systems and how do you see that<00:03:41.080> area<00:03:41.439> evolve<00:03:42.319> yeah<00:03:42.680> no<00:03:42.840> it's<00:03:43.159> uh<00:03:43.319> it's 00:03:43.509 --> 00:03:43.519 align:start position:0% that area evolve yeah no it's uh it's 00:03:43.519 --> 00:03:45.030 align:start position:0% that area evolve yeah no it's uh it's really<00:03:43.720> been<00:03:43.959> interesting<00:03:44.400> over<00:03:44.560> the<00:03:44.680> years 00:03:45.030 --> 00:03:45.040 align:start position:0% really been interesting over the years 00:03:45.040 --> 00:03:47.190 align:start position:0% really been interesting over the years because<00:03:45.560> you<00:03:45.799> I<00:03:45.920> think<00:03:46.159> with<00:03:46.319> Lucine<00:03:46.920> you<00:03:47.000> know 00:03:47.190 --> 00:03:47.200 align:start position:0% because you I think with Lucine you know 00:03:47.200 --> 00:03:49.750 align:start position:0% because you I think with Lucine you know obviously<00:03:47.560> it's<00:03:47.720> just<00:03:47.879> a<00:03:48.280> set<00:03:48.480> of<00:03:48.680> java<00:03:49.080> apis 00:03:49.750 --> 00:03:49.760 align:start position:0% obviously it's just a set of java apis 00:03:49.760 --> 00:03:52.869 align:start position:0% obviously it's just a set of java apis and<00:03:50.200> that<00:03:50.480> provides<00:03:51.000> search<00:03:52.000> functionality 00:03:52.869 --> 00:03:52.879 align:start position:0% and that provides search functionality 00:03:52.879 --> 00:03:54.670 align:start position:0% and that provides search functionality things<00:03:53.159> like<00:03:53.400> obviously<00:03:53.840> matching<00:03:54.280> queries 00:03:54.670 --> 00:03:54.680 align:start position:0% things like obviously matching queries 00:03:54.680 --> 00:03:56.309 align:start position:0% things like obviously matching queries and<00:03:54.840> doing<00:03:55.079> fuzzy<00:03:55.439> matching<00:03:55.799> and<00:03:55.959> all<00:03:56.159> that 00:03:56.309 --> 00:03:56.319 align:start position:0% and doing fuzzy matching and all that 00:03:56.319 --> 00:03:57.949 align:start position:0% and doing fuzzy matching and all that kind<00:03:56.439> of<00:03:56.599> stuff<00:03:56.879> as<00:03:57.000> well<00:03:57.120> as<00:03:57.319> like<00:03:57.480> language 00:03:57.949 --> 00:03:57.959 align:start position:0% kind of stuff as well as like language 00:03:57.959 --> 00:04:00.550 align:start position:0% kind of stuff as well as like language analyzers<00:03:58.760> and<00:03:59.519> and<00:03:59.920> and<00:04:00.040> then<00:04:00.159> a<00:04:00.239> whole<00:04:00.360> bunch 00:04:00.550 --> 00:04:00.560 align:start position:0% analyzers and and and then a whole bunch 00:04:00.560 --> 00:04:02.830 align:start position:0% analyzers and and and then a whole bunch of<00:04:00.760> modules<00:04:01.319> that<00:04:01.519> kind<00:04:01.599> of<00:04:01.760> help<00:04:02.000> you<00:04:02.280> build 00:04:02.830 --> 00:04:02.840 align:start position:0% of modules that kind of help you build 00:04:02.840 --> 00:04:04.390 align:start position:0% of modules that kind of help you build you<00:04:02.920> know<00:04:03.040> a<00:04:03.159> kit<00:04:03.360> of<00:04:03.519> parts<00:04:03.840> to<00:04:04.000> build<00:04:04.280> a 00:04:04.390 --> 00:04:04.400 align:start position:0% you know a kit of parts to build a 00:04:04.400 --> 00:04:07.149 align:start position:0% you know a kit of parts to build a Search<00:04:04.879> application<00:04:05.879> Along<00:04:06.239> Came<00:04:06.519> solar<00:04:06.959> and 00:04:07.149 --> 00:04:07.159 align:start position:0% Search application Along Came solar and 00:04:07.159 --> 00:04:08.710 align:start position:0% Search application Along Came solar and really<00:04:07.480> kind<00:04:07.599> of<00:04:07.799> said<00:04:08.040> all<00:04:08.159> right<00:04:08.319> well<00:04:08.480> let's 00:04:08.710 --> 00:04:08.720 align:start position:0% really kind of said all right well let's 00:04:08.720 --> 00:04:10.470 align:start position:0% really kind of said all right well let's put<00:04:08.879> this<00:04:09.040> in<00:04:09.200> a<00:04:09.400> service<00:04:09.840> layer<00:04:10.159> and<00:04:10.319> let's 00:04:10.470 --> 00:04:10.480 align:start position:0% put this in a service layer and let's 00:04:10.480 --> 00:04:13.110 align:start position:0% put this in a service layer and let's make<00:04:10.640> it<00:04:10.840> easy<00:04:11.120> for<00:04:11.400> people<00:04:12.200> to<00:04:12.519> interact<00:04:13.000> with 00:04:13.110 --> 00:04:13.120 align:start position:0% make it easy for people to interact with 00:04:13.120 --> 00:04:16.030 align:start position:0% make it easy for people to interact with it<00:04:13.280> in<00:04:13.400> the<00:04:13.640> very<00:04:13.840> early<00:04:14.200> days<00:04:14.439> of<00:04:14.680> solar<00:04:15.680> the 00:04:16.030 --> 00:04:16.040 align:start position:0% it in the very early days of solar the 00:04:16.040 --> 00:04:18.789 align:start position:0% it in the very early days of solar the scaling<00:04:16.720> primarily<00:04:17.479> was<00:04:17.840> in<00:04:17.959> a<00:04:18.160> replicated 00:04:18.789 --> 00:04:18.799 align:start position:0% scaling primarily was in a replicated 00:04:18.799 --> 00:04:20.670 align:start position:0% scaling primarily was in a replicated model<00:04:19.199> for<00:04:19.639> query<00:04:20.040> volume<00:04:20.440> because 00:04:20.670 --> 00:04:20.680 align:start position:0% model for query volume because 00:04:20.680 --> 00:04:22.990 align:start position:0% model for query volume because essentially<00:04:21.359> you<00:04:21.479> know<00:04:21.600> nobody<00:04:21.919> really<00:04:22.280> had 00:04:22.990 --> 00:04:23.000 align:start position:0% essentially you know nobody really had 00:04:23.000 --> 00:04:25.189 align:start position:0% essentially you know nobody really had really<00:04:23.280> large<00:04:23.759> scale<00:04:24.400> problems<00:04:24.800> other<00:04:25.000> than 00:04:25.189 --> 00:04:25.199 align:start position:0% really large scale problems other than 00:04:25.199 --> 00:04:27.150 align:start position:0% really large scale problems other than you<00:04:25.280> know<00:04:25.600> the<00:04:25.880> the<00:04:25.960> internet<00:04:26.360> search<00:04:26.800> people 00:04:27.150 --> 00:04:27.160 align:start position:0% you know the the internet search people 00:04:27.160 --> 00:04:29.110 align:start position:0% you know the the internet search people like<00:04:27.360> Google<00:04:27.840> and<00:04:28.120> and<00:04:28.280> being<00:04:28.520> in<00:04:28.680> the<00:04:28.800> like 00:04:29.110 --> 00:04:29.120 align:start position:0% like Google and and being in the like 00:04:29.120 --> 00:04:30.670 align:start position:0% like Google and and being in the like because<00:04:29.400> they<00:04:29.520> were<00:04:29.720> were<00:04:30.160> and<00:04:30.360> of<00:04:30.479> course 00:04:30.670 --> 00:04:30.680 align:start position:0% because they were were and of course 00:04:30.680 --> 00:04:32.909 align:start position:0% because they were were and of course they<00:04:30.759> were<00:04:30.919> building<00:04:31.280> their<00:04:31.440> own<00:04:32.400> uh<00:04:32.600> so<00:04:32.800> you 00:04:32.909 --> 00:04:32.919 align:start position:0% they were building their own uh so you 00:04:32.919 --> 00:04:34.110 align:start position:0% they were building their own uh so you know<00:04:33.039> especially<00:04:33.320> in<00:04:33.400> the<00:04:33.520> e-commerce 00:04:34.110 --> 00:04:34.120 align:start position:0% know especially in the e-commerce 00:04:34.120 --> 00:04:35.430 align:start position:0% know especially in the e-commerce environment<00:04:34.600> you<00:04:34.680> know<00:04:34.800> it's<00:04:34.960> just<00:04:35.160> hey<00:04:35.320> I've 00:04:35.430 --> 00:04:35.440 align:start position:0% environment you know it's just hey I've 00:04:35.440 --> 00:04:37.029 align:start position:0% environment you know it's just hey I've got<00:04:35.560> a<00:04:35.680> lot<00:04:35.800> of<00:04:35.919> queries<00:04:36.360> but<00:04:36.479> I<00:04:36.520> don't<00:04:36.720> have<00:04:36.840> a 00:04:37.029 --> 00:04:37.039 align:start position:0% got a lot of queries but I don't have a 00:04:37.039 --> 00:04:39.670 align:start position:0% got a lot of queries but I don't have a big<00:04:37.240> index<00:04:37.840> so<00:04:38.320> let's<00:04:38.520> just<00:04:38.720> replicate<00:04:39.160> it<00:04:39.600> and 00:04:39.670 --> 00:04:39.680 align:start position:0% big index so let's just replicate it and 00:04:39.680 --> 00:04:41.110 align:start position:0% big index so let's just replicate it and then<00:04:39.840> you<00:04:39.919> know<00:04:40.039> Flash<00:04:40.320> Forward<00:04:40.639> a<00:04:40.759> few<00:04:40.919> more 00:04:41.110 --> 00:04:41.120 align:start position:0% then you know Flash Forward a few more 00:04:41.120 --> 00:04:42.950 align:start position:0% then you know Flash Forward a few more years<00:04:41.360> as<00:04:41.560> hadoop's<00:04:42.039> taking<00:04:42.360> off<00:04:42.680> which<00:04:42.840> you 00:04:42.950 --> 00:04:42.960 align:start position:0% years as hadoop's taking off which you 00:04:42.960 --> 00:04:44.510 align:start position:0% years as hadoop's taking off which you know<00:04:43.080> of<00:04:43.160> course<00:04:43.360> Hadoop<00:04:43.759> started<00:04:44.039> as<00:04:44.240> part<00:04:44.360> as 00:04:44.510 --> 00:04:44.520 align:start position:0% know of course Hadoop started as part as 00:04:44.520 --> 00:04:47.749 align:start position:0% know of course Hadoop started as part as the<00:04:44.639> Lucine<00:04:45.240> project<00:04:45.680> as<00:04:45.919> well<00:04:46.919> uh<00:04:47.160> was<00:04:47.560> okay 00:04:47.749 --> 00:04:47.759 align:start position:0% the Lucine project as well uh was okay 00:04:47.759 --> 00:04:49.870 align:start position:0% the Lucine project as well uh was okay well<00:04:48.039> we<00:04:48.199> now<00:04:48.360> need<00:04:48.560> to<00:04:48.720> scale<00:04:49.120> search<00:04:49.600> to 00:04:49.870 --> 00:04:49.880 align:start position:0% well we now need to scale search to 00:04:49.880 --> 00:04:52.189 align:start position:0% well we now need to scale search to match<00:04:50.759> those<00:04:51.039> kinds<00:04:51.240> of<00:04:51.360> needs<00:04:51.680> as<00:04:51.840> well<00:04:52.000> so 00:04:52.189 --> 00:04:52.199 align:start position:0% match those kinds of needs as well so 00:04:52.199 --> 00:04:53.870 align:start position:0% match those kinds of needs as well so not<00:04:52.320> only<00:04:52.520> do<00:04:52.639> we<00:04:52.759> need<00:04:52.880> to<00:04:53.000> scale<00:04:53.320> for<00:04:53.479> query 00:04:53.870 --> 00:04:53.880 align:start position:0% not only do we need to scale for query 00:04:53.880 --> 00:04:55.790 align:start position:0% not only do we need to scale for query volume<00:04:54.240> but<00:04:54.360> we<00:04:54.520> also<00:04:54.720> need<00:04:54.880> to<00:04:55.120> scale<00:04:55.479> for<00:04:55.680> a 00:04:55.790 --> 00:04:55.800 align:start position:0% volume but we also need to scale for a 00:04:55.800 --> 00:04:58.990 align:start position:0% volume but we also need to scale for a number<00:04:56.039> of<00:04:56.320> documents<00:04:56.960> and<00:04:57.240> so<00:04:58.240> uh<00:04:58.600> you<00:04:58.720> know<00:04:58.880> a 00:04:58.990 --> 00:04:59.000 align:start position:0% number of documents and so uh you know a 00:04:59.000 --> 00:05:01.430 align:start position:0% number of documents and so uh you know a lot<00:04:59.120> of<00:04:59.240> people<00:04:59.720> had<00:04:59.840> rolled<00:05:00.160> their<00:05:00.320> own<00:05:01.039> using 00:05:01.430 --> 00:05:01.440 align:start position:0% lot of people had rolled their own using 00:05:01.440 --> 00:05:03.870 align:start position:0% lot of people had rolled their own using solar<00:05:01.840> and<00:05:01.960> Lucine<00:05:02.520> over<00:05:02.720> the<00:05:02.840> years<00:05:03.560> and<00:05:03.680> so 00:05:03.870 --> 00:05:03.880 align:start position:0% solar and Lucine over the years and so 00:05:03.880 --> 00:05:04.830 align:start position:0% solar and Lucine over the years and so you<00:05:03.960> know<00:05:04.080> one<00:05:04.199> of<00:05:04.280> the<00:05:04.360> things<00:05:04.560> that<00:05:04.680> we 00:05:04.830 --> 00:05:04.840 align:start position:0% you know one of the things that we 00:05:04.840 --> 00:05:06.830 align:start position:0% you know one of the things that we really<00:05:05.080> focused<00:05:05.479> on<00:05:05.680> as<00:05:05.800> a<00:05:05.960> company<00:05:06.400> was<00:05:06.600> let's 00:05:06.830 --> 00:05:06.840 align:start position:0% really focused on as a company was let's 00:05:06.840 --> 00:05:08.870 align:start position:0% really focused on as a company was let's make<00:05:07.039> sure<00:05:07.360> that<00:05:07.680> solar<00:05:08.039> just<00:05:08.199> has<00:05:08.520> really 00:05:08.870 --> 00:05:08.880 align:start position:0% make sure that solar just has really 00:05:08.880 --> 00:05:11.270 align:start position:0% make sure that solar just has really good<00:05:09.479> distributed<00:05:10.039> search<00:05:10.520> capabilities<00:05:11.120> out 00:05:11.270 --> 00:05:11.280 align:start position:0% good distributed search capabilities out 00:05:11.280 --> 00:05:14.070 align:start position:0% good distributed search capabilities out of<00:05:11.440> the<00:05:11.600> box<00:05:12.320> solar<00:05:12.800> Cloud<00:05:13.120> was<00:05:13.240> born<00:05:13.919> for 00:05:14.070 --> 00:05:14.080 align:start position:0% of the box solar Cloud was born for 00:05:14.080 --> 00:05:15.469 align:start position:0% of the box solar Cloud was born for whatever<00:05:14.400> reason<00:05:14.639> I<00:05:14.720> don't<00:05:14.880> know<00:05:15.039> the<00:05:15.160> naming 00:05:15.469 --> 00:05:15.479 align:start position:0% whatever reason I don't know the naming 00:05:15.479 --> 00:05:17.430 align:start position:0% whatever reason I don't know the naming of<00:05:15.600> it<00:05:16.000> but<00:05:16.400> you<00:05:16.520> know<00:05:16.759> that<00:05:16.880> was<00:05:17.039> kind<00:05:17.160> of<00:05:17.280> the 00:05:17.430 --> 00:05:17.440 align:start position:0% of it but you know that was kind of the 00:05:17.440 --> 00:05:19.909 align:start position:0% of it but you know that was kind of the way<00:05:17.639> we<00:05:17.880> attacked<00:05:18.280> it<00:05:18.759> added<00:05:19.080> in<00:05:19.600> first 00:05:19.909 --> 00:05:19.919 align:start position:0% way we attacked it added in first 00:05:19.919 --> 00:05:21.830 align:start position:0% way we attacked it added in first distributed<00:05:20.520> search<00:05:20.960> capabilities<00:05:21.600> you<00:05:21.759> had 00:05:21.830 --> 00:05:21.840 align:start position:0% distributed search capabilities you had 00:05:21.840 --> 00:05:23.990 align:start position:0% distributed search capabilities you had to<00:05:21.960> do<00:05:22.080> the<00:05:22.199> indexing<00:05:22.720> yourself<00:05:23.280> and<00:05:23.440> then<00:05:23.840> uh 00:05:23.990 --> 00:05:24.000 align:start position:0% to do the indexing yourself and then uh 00:05:24.000 --> 00:05:26.909 align:start position:0% to do the indexing yourself and then uh with<00:05:24.160> solar<00:05:24.520> Ford<00:05:25.039> auto<00:05:26.039> uh<00:05:26.240> which<00:05:26.440> was<00:05:26.840> I 00:05:26.909 --> 00:05:26.919 align:start position:0% with solar Ford auto uh which was I 00:05:26.919 --> 00:05:28.150 align:start position:0% with solar Ford auto uh which was I don't<00:05:27.039> know<00:05:27.160> a<00:05:27.240> year<00:05:27.360> and<00:05:27.479> a<00:05:27.560> half<00:05:27.759> two<00:05:27.960> years 00:05:28.150 --> 00:05:28.160 align:start position:0% don't know a year and a half two years 00:05:28.160 --> 00:05:30.710 align:start position:0% don't know a year and a half two years ago<00:05:28.520> now<00:05:29.080> added<00:05:29.759> the<00:05:29.960> capability<00:05:30.360> to<00:05:30.440> do<00:05:30.560> all 00:05:30.710 --> 00:05:30.720 align:start position:0% ago now added the capability to do all 00:05:30.720 --> 00:05:32.629 align:start position:0% ago now added the capability to do all the<00:05:30.880> indexing<00:05:31.440> and<00:05:31.600> all<00:05:31.759> of<00:05:31.960> that<00:05:32.199> as<00:05:32.360> well 00:05:32.629 --> 00:05:32.639 align:start position:0% the indexing and all of that as well 00:05:32.639 --> 00:05:34.950 align:start position:0% the indexing and all of that as well such<00:05:32.919> that<00:05:33.120> you<00:05:33.360> know<00:05:34.360> I<00:05:34.440> think<00:05:34.560> I<00:05:34.639> was<00:05:34.759> at<00:05:34.840> a 00:05:34.950 --> 00:05:34.960 align:start position:0% such that you know I think I was at a 00:05:34.960 --> 00:05:37.309 align:start position:0% such that you know I think I was at a meet<00:05:35.160> up<00:05:35.680> just<00:05:35.919> recently<00:05:36.400> up<00:05:36.560> at<00:05:36.759> Salesforce 00:05:37.309 --> 00:05:37.319 align:start position:0% meet up just recently up at Salesforce 00:05:37.319 --> 00:05:39.790 align:start position:0% meet up just recently up at Salesforce in<00:05:37.520> Seattle<00:05:38.440> I<00:05:38.520> think<00:05:38.720> they<00:05:38.880> announced<00:05:39.400> their 00:05:39.790 --> 00:05:39.800 align:start position:0% in Seattle I think they announced their 00:05:39.800 --> 00:05:43.629 align:start position:0% in Seattle I think they announced their their<00:05:39.960> solar<00:05:40.720> deployment<00:05:41.720> somewhere<00:05:42.600> 200<00:05:42.919> 300 00:05:43.629 --> 00:05:43.639 align:start position:0% their solar deployment somewhere 200 300 00:05:43.639 --> 00:05:46.629 align:start position:0% their solar deployment somewhere 200 300 billion<00:05:44.639> uh<00:05:44.960> documents<00:05:45.479> in<00:05:45.680> it<00:05:46.000> you<00:05:46.120> know<00:05:46.360> so 00:05:46.629 --> 00:05:46.639 align:start position:0% billion uh documents in it you know so 00:05:46.639 --> 00:05:49.830 align:start position:0% billion uh documents in it you know so people<00:05:46.960> doing<00:05:47.840> really<00:05:48.160> large<00:05:48.600> scale<00:05:49.120> search 00:05:49.830 --> 00:05:49.840 align:start position:0% people doing really large scale search 00:05:49.840 --> 00:05:51.309 align:start position:0% people doing really large scale search you<00:05:49.919> know<00:05:50.120> across<00:05:50.560> you<00:05:50.680> know<00:05:50.840> hundreds<00:05:51.160> of 00:05:51.309 --> 00:05:51.319 align:start position:0% you know across you know hundreds of 00:05:51.319 --> 00:05:53.070 align:start position:0% you know across you know hundreds of billions<00:05:51.639> of<00:05:51.880> documents<00:05:52.400> it's<00:05:52.520> only<00:05:52.720> a<00:05:52.840> matter 00:05:53.070 --> 00:05:53.080 align:start position:0% billions of documents it's only a matter 00:05:53.080 --> 00:05:55.189 align:start position:0% billions of documents it's only a matter of<00:05:53.240> time<00:05:53.520> we<00:05:53.919> before<00:05:54.199> I'm<00:05:54.280> sure<00:05:54.440> we're<00:05:54.600> doing 00:05:55.189 --> 00:05:55.199 align:start position:0% of time we before I'm sure we're doing 00:05:55.199 --> 00:05:57.150 align:start position:0% of time we before I'm sure we're doing trillions<00:05:56.199> uh<00:05:56.360> and<00:05:56.520> so<00:05:56.759> you<00:05:56.880> know<00:05:57.000> you're 00:05:57.150 --> 00:05:57.160 align:start position:0% trillions uh and so you know you're 00:05:57.160 --> 00:05:59.909 align:start position:0% trillions uh and so you know you're seeing<00:05:57.680> just<00:05:57.880> this<00:05:58.720> massive<00:05:59.080> uptake<00:05:59.440> in<00:05:59.720> and<00:05:59.840> I 00:05:59.909 --> 00:05:59.919 align:start position:0% seeing just this massive uptake in and I 00:05:59.919 --> 00:06:01.029 align:start position:0% seeing just this massive uptake in and I think<00:06:00.039> the<00:06:00.120> other<00:06:00.280> interesting<00:06:00.680> thing<00:06:00.800> is 00:06:01.029 --> 00:06:01.039 align:start position:0% think the other interesting thing is 00:06:01.039 --> 00:06:03.029 align:start position:0% think the other interesting thing is people<00:06:01.280> are<00:06:01.680> asking<00:06:02.080> more<00:06:02.440> interesting 00:06:03.029 --> 00:06:03.039 align:start position:0% people are asking more interesting 00:06:03.039 --> 00:06:05.029 align:start position:0% people are asking more interesting questions<00:06:03.479> of<00:06:03.680> their<00:06:03.840> search<00:06:04.160> engine<00:06:04.600> as<00:06:04.759> well 00:06:05.029 --> 00:06:05.039 align:start position:0% questions of their search engine as well 00:06:05.039 --> 00:06:07.390 align:start position:0% questions of their search engine as well it's<00:06:05.199> not<00:06:05.400> just<00:06:05.680> hey<00:06:05.840> find<00:06:06.080> me<00:06:06.319> keywords<00:06:07.240> and 00:06:07.390 --> 00:06:07.400 align:start position:0% it's not just hey find me keywords and 00:06:07.400 --> 00:06:10.070 align:start position:0% it's not just hey find me keywords and get<00:06:07.680> back<00:06:08.039> results<00:06:08.560> it's<00:06:09.039> bring<00:06:09.360> in<00:06:09.800> you<00:06:09.919> know 00:06:10.070 --> 00:06:10.080 align:start position:0% get back results it's bring in you know 00:06:10.080 --> 00:06:12.150 align:start position:0% get back results it's bring in you know all<00:06:10.319> kinds<00:06:10.520> of<00:06:10.759> different<00:06:11.160> data<00:06:11.479> structures 00:06:12.150 --> 00:06:12.160 align:start position:0% all kinds of different data structures 00:06:12.160 --> 00:06:14.950 align:start position:0% all kinds of different data structures numbers<00:06:12.759> spatial<00:06:13.360> enumerated<00:06:14.039> types<00:06:14.720> how<00:06:14.800> do 00:06:14.950 --> 00:06:14.960 align:start position:0% numbers spatial enumerated types how do 00:06:14.960 --> 00:06:17.710 align:start position:0% numbers spatial enumerated types how do I<00:06:15.120> slice<00:06:15.599> and<00:06:15.800> dice<00:06:16.120> that<00:06:16.360> and<00:06:16.720> bring<00:06:17.000> me<00:06:17.319> back 00:06:17.710 --> 00:06:17.720 align:start position:0% I slice and dice that and bring me back 00:06:17.720 --> 00:06:19.749 align:start position:0% I slice and dice that and bring me back what's<00:06:18.039> important<00:06:19.039> right<00:06:19.160> ultimately<00:06:19.680> you 00:06:19.749 --> 00:06:19.759 align:start position:0% what's important right ultimately you 00:06:19.759 --> 00:06:21.430 align:start position:0% what's important right ultimately you know<00:06:20.000> shifting<00:06:20.400> from<00:06:20.560> it<00:06:20.720> just<00:06:20.880> being<00:06:21.160> kind<00:06:21.280> of 00:06:21.430 --> 00:06:21.440 align:start position:0% know shifting from it just being kind of 00:06:21.440 --> 00:06:23.749 align:start position:0% know shifting from it just being kind of traditional<00:06:21.919> keyword<00:06:22.319> search<00:06:22.720> to<00:06:22.880> being<00:06:23.599> all 00:06:23.749 --> 00:06:23.759 align:start position:0% traditional keyword search to being all 00:06:23.759 --> 00:06:26.150 align:start position:0% traditional keyword search to being all about<00:06:24.039> what's<00:06:24.360> important<00:06:24.880> in<00:06:25.080> my<00:06:25.319> data<00:06:25.919> yes 00:06:26.150 --> 00:06:26.160 align:start position:0% about what's important in my data yes 00:06:26.160 --> 00:06:27.670 align:start position:0% about what's important in my data yes and<00:06:26.360> then<00:06:26.639> you<00:06:26.720> know<00:06:26.880> shifting<00:06:27.319> through<00:06:27.560> you 00:06:27.670 --> 00:06:27.680 align:start position:0% and then you know shifting through you 00:06:27.680 --> 00:06:29.550 align:start position:0% and then you know shifting through you know<00:06:27.800> using<00:06:28.160> that<00:06:28.319> to<00:06:28.520> then<00:06:28.800> power<00:06:29.080> your 00:06:29.550 --> 00:06:29.560 align:start position:0% know using that to then power your 00:06:29.560 --> 00:06:32.430 align:start position:0% know using that to then power your Downstream<00:06:30.479> applications<00:06:31.479> yes<00:06:31.960> this<00:06:32.240> this 00:06:32.430 --> 00:06:32.440 align:start position:0% Downstream applications yes this this 00:06:32.440 --> 00:06:35.350 align:start position:0% Downstream applications yes this this actually<00:06:33.199> uh<00:06:33.360> connects<00:06:34.160> very<00:06:34.400> well<00:06:34.680> with<00:06:35.240> one 00:06:35.350 --> 00:06:35.360 align:start position:0% actually uh connects very well with one 00:06:35.360 --> 00:06:37.189 align:start position:0% actually uh connects very well with one of<00:06:35.479> the<00:06:35.599> themes<00:06:35.800> of<00:06:35.919> our<00:06:36.080> Meetup<00:06:36.520> because<00:06:37.080> we 00:06:37.189 --> 00:06:37.199 align:start position:0% of the themes of our Meetup because we 00:06:37.199 --> 00:06:39.990 align:start position:0% of the themes of our Meetup because we see<00:06:37.560> text<00:06:38.000> as<00:06:38.319> emerging<00:06:39.240> again<00:06:39.479> as<00:06:39.599> a<00:06:39.720> window 00:06:39.990 --> 00:06:40.000 align:start position:0% see text as emerging again as a window 00:06:40.000 --> 00:06:42.150 align:start position:0% see text as emerging again as a window into<00:06:40.240> human<00:06:40.479> intent<00:06:41.000> right<00:06:41.280> the<00:06:41.599> through<00:06:41.960> this 00:06:42.150 --> 00:06:42.160 align:start position:0% into human intent right the through this 00:06:42.160 --> 00:06:44.670 align:start position:0% into human intent right the through this little<00:06:42.479> box<00:06:43.440> uh<00:06:43.560> and<00:06:44.080> this<00:06:44.160> is<00:06:44.280> how<00:06:44.440> we<00:06:44.560> are 00:06:44.670 --> 00:06:44.680 align:start position:0% little box uh and this is how we are 00:06:44.680 --> 00:06:46.990 align:start position:0% little box uh and this is how we are used<00:06:44.919> to<00:06:45.039> do<00:06:45.199> search<00:06:45.680> but<00:06:45.880> now<00:06:46.479> if<00:06:46.560> you<00:06:46.680> go<00:06:46.800> to 00:06:46.990 --> 00:06:47.000 align:start position:0% used to do search but now if you go to 00:06:47.000 --> 00:06:50.070 align:start position:0% used to do search but now if you go to Google<00:06:47.319> and<00:06:47.479> you<00:06:47.599> enter<00:06:48.080> sf4<00:06:49.080> BOS<00:06:49.759> it<00:06:49.840> will 00:06:50.070 --> 00:06:50.080 align:start position:0% Google and you enter sf4 BOS it will 00:06:50.080 --> 00:06:52.670 align:start position:0% Google and you enter sf4 BOS it will give<00:06:50.199> you<00:06:50.400> tickets<00:06:51.319> probably<00:06:51.840> from<00:06:52.360> uh<00:06:52.440> San 00:06:52.670 --> 00:06:52.680 align:start position:0% give you tickets probably from uh San 00:06:52.680 --> 00:06:55.230 align:start position:0% give you tickets probably from uh San Francisco<00:06:53.120> to<00:06:53.280> Boston<00:06:54.240> uh<00:06:54.360> or<00:06:55.000> more 00:06:55.230 --> 00:06:55.240 align:start position:0% Francisco to Boston uh or more 00:06:55.240 --> 00:06:58.950 align:start position:0% Francisco to Boston uh or more structured<00:06:55.720> data<00:06:56.080> and<00:06:57.080> uh<00:06:57.639> uh<00:06:58.000> essentially 00:06:58.950 --> 00:06:58.960 align:start position:0% structured data and uh uh essentially 00:06:58.960 --> 00:07:01.189 align:start position:0% structured data and uh uh essentially search<00:06:59.280> Eng<00:06:59.919> ultimate<00:07:00.360> goal<00:07:00.599> is<00:07:00.720> to<00:07:00.879> figure 00:07:01.189 --> 00:07:01.199 align:start position:0% search Eng ultimate goal is to figure 00:07:01.199 --> 00:07:03.790 align:start position:0% search Eng ultimate goal is to figure out<00:07:01.599> what<00:07:01.800> was<00:07:01.960> our<00:07:02.240> original<00:07:02.639> intent<00:07:03.520> behind 00:07:03.790 --> 00:07:03.800 align:start position:0% out what was our original intent behind 00:07:03.800 --> 00:07:06.150 align:start position:0% out what was our original intent behind the<00:07:03.919> query<00:07:04.520> so<00:07:04.759> here<00:07:04.919> of<00:07:05.039> course<00:07:05.240> I<00:07:05.360> want<00:07:05.599> to 00:07:06.150 --> 00:07:06.160 align:start position:0% the query so here of course I want to 00:07:06.160 --> 00:07:07.950 align:start position:0% the query so here of course I want to ask<00:07:06.479> how<00:07:06.759> we<00:07:07.000> open<00:07:07.280> source<00:07:07.599> people<00:07:07.759> are<00:07:07.840> going 00:07:07.950 --> 00:07:07.960 align:start position:0% ask how we open source people are going 00:07:07.960 --> 00:07:09.230 align:start position:0% ask how we open source people are going to<00:07:08.039> compete<00:07:08.360> with<00:07:08.479> the<00:07:08.560> big<00:07:08.720> guys<00:07:09.080> right 00:07:09.230 --> 00:07:09.240 align:start position:0% to compete with the big guys right 00:07:09.240 --> 00:07:11.390 align:start position:0% to compete with the big guys right because<00:07:09.520> we<00:07:09.680> have<00:07:10.240> we<00:07:10.440> have<00:07:10.720> open<00:07:10.960> source<00:07:11.280> we 00:07:11.390 --> 00:07:11.400 align:start position:0% because we have we have open source we 00:07:11.400 --> 00:07:15.629 align:start position:0% because we have we have open source we have<00:07:11.520> the<00:07:11.800> community<00:07:12.800> uh<00:07:12.960> but<00:07:13.400> the<00:07:13.960> uh<00:07:14.800> kind<00:07:14.960> of 00:07:15.629 --> 00:07:15.639 align:start position:0% have the community uh but the uh kind of 00:07:15.639 --> 00:07:18.270 align:start position:0% have the community uh but the uh kind of structure<00:07:16.120> data<00:07:16.360> people<00:07:16.560> want<00:07:16.680> to<00:07:16.960> ask<00:07:17.879> uh<00:07:18.039> may 00:07:18.270 --> 00:07:18.280 align:start position:0% structure data people want to ask uh may 00:07:18.280 --> 00:07:22.670 align:start position:0% structure data people want to ask uh may have<00:07:18.440> semanti<00:07:19.039> content<00:07:20.039> and<00:07:20.800> um<00:07:21.440> how<00:07:21.639> do<00:07:21.919> we 00:07:22.670 --> 00:07:22.680 align:start position:0% have semanti content and um how do we 00:07:22.680 --> 00:07:25.510 align:start position:0% have semanti content and um how do we kind<00:07:22.840> of<00:07:23.160> map<00:07:23.560> this<00:07:24.199> uh<00:07:24.360> more<00:07:25.160> uh<00:07:25.280> with 00:07:25.510 --> 00:07:25.520 align:start position:0% kind of map this uh more uh with 00:07:25.520 --> 00:07:27.150 align:start position:0% kind of map this uh more uh with structure<00:07:25.960> data<00:07:26.199> which<00:07:26.319> you<00:07:26.479> mentioned<00:07:27.000> how 00:07:27.150 --> 00:07:27.160 align:start position:0% structure data which you mentioned how 00:07:27.160 --> 00:07:30.390 align:start position:0% structure data which you mentioned how do<00:07:27.319> we<00:07:27.840> kind<00:07:27.960> of<00:07:28.199> uncover<00:07:29.199> more<00:07:29.520> more<00:07:29.840> behind 00:07:30.390 --> 00:07:30.400 align:start position:0% do we kind of uncover more more behind 00:07:30.400 --> 00:07:32.749 align:start position:0% do we kind of uncover more more behind you<00:07:30.520> know<00:07:30.919> more<00:07:31.120> in<00:07:31.240> our<00:07:31.560> documents<00:07:32.520> what<00:07:32.680> do 00:07:32.749 --> 00:07:32.759 align:start position:0% you know more in our documents what do 00:07:32.759 --> 00:07:34.150 align:start position:0% you know more in our documents what do you<00:07:32.960> think<00:07:33.240> is<00:07:33.400> going<00:07:33.479> to<00:07:33.599> happen<00:07:33.800> here<00:07:33.919> in<00:07:34.039> the 00:07:34.150 --> 00:07:34.160 align:start position:0% you think is going to happen here in the 00:07:34.160 --> 00:07:35.909 align:start position:0% you think is going to happen here in the open<00:07:34.319> source<00:07:34.680> the<00:07:34.800> next<00:07:34.960> few<00:07:35.160> years<00:07:35.759> wow 00:07:35.909 --> 00:07:35.919 align:start position:0% open source the next few years wow 00:07:35.919 --> 00:07:37.629 align:start position:0% open source the next few years wow that's<00:07:36.280> a<00:07:36.360> lot<00:07:36.479> of<00:07:36.599> good<00:07:36.840> questions<00:07:37.199> in<00:07:37.400> there 00:07:37.629 --> 00:07:37.639 align:start position:0% that's a lot of good questions in there 00:07:37.639 --> 00:07:38.950 align:start position:0% that's a lot of good questions in there I<00:07:37.720> mean<00:07:37.879> I<00:07:38.000> think<00:07:38.319> you<00:07:38.440> know<00:07:38.560> obviously<00:07:38.879> I 00:07:38.950 --> 00:07:38.960 align:start position:0% I mean I think you know obviously I 00:07:38.960 --> 00:07:40.510 align:start position:0% I mean I think you know obviously I can't<00:07:39.160> predict<00:07:39.479> the<00:07:39.599> future<00:07:40.080> but<00:07:40.240> you<00:07:40.360> know 00:07:40.510 --> 00:07:40.520 align:start position:0% can't predict the future but you know 00:07:40.520 --> 00:07:42.830 align:start position:0% can't predict the future but you know what<00:07:40.639> you're<00:07:40.840> seeing<00:07:41.840> in<00:07:42.080> open<00:07:42.440> source<00:07:42.720> I 00:07:42.830 --> 00:07:42.840 align:start position:0% what you're seeing in open source I 00:07:42.840 --> 00:07:44.230 align:start position:0% what you're seeing in open source I think<00:07:42.960> in<00:07:43.080> the<00:07:43.360> you<00:07:43.479> know<00:07:43.639> kind<00:07:43.759> of<00:07:43.879> the<00:07:43.960> early 00:07:44.230 --> 00:07:44.240 align:start position:0% think in the you know kind of the early 00:07:44.240 --> 00:07:45.749 align:start position:0% think in the you know kind of the early days<00:07:44.599> especially<00:07:44.919> when<00:07:45.000> I<00:07:45.080> started<00:07:45.319> with<00:07:45.479> open 00:07:45.749 --> 00:07:45.759 align:start position:0% days especially when I started with open 00:07:45.759 --> 00:07:47.550 align:start position:0% days especially when I started with open source<00:07:46.039> open<00:07:46.280> source<00:07:46.520> was<00:07:46.720> primarily<00:07:47.159> focused 00:07:47.550 --> 00:07:47.560 align:start position:0% source open source was primarily focused 00:07:47.560 --> 00:07:48.950 align:start position:0% source open source was primarily focused on 00:07:48.950 --> 00:07:48.960 align:start position:0% on 00:07:48.960 --> 00:07:52.029 align:start position:0% on commoditizing<00:07:49.960> what<00:07:50.440> people<00:07:50.680> were<00:07:50.879> seeing<00:07:51.560> in 00:07:52.029 --> 00:07:52.039 align:start position:0% commoditizing what people were seeing in 00:07:52.039 --> 00:07:54.230 align:start position:0% commoditizing what people were seeing in the<00:07:52.240> proprietary<00:07:52.840> landscape<00:07:53.319> or<00:07:53.520> they<00:07:54.080> just 00:07:54.230 --> 00:07:54.240 align:start position:0% the proprietary landscape or they just 00:07:54.240 --> 00:07:56.149 align:start position:0% the proprietary landscape or they just got<00:07:54.479> tired<00:07:54.800> of<00:07:55.000> building<00:07:55.440> the<00:07:55.599> same<00:07:55.879> thing 00:07:56.149 --> 00:07:56.159 align:start position:0% got tired of building the same thing 00:07:56.159 --> 00:07:57.430 align:start position:0% got tired of building the same thing every<00:07:56.360> time<00:07:56.560> they<00:07:56.680> went<00:07:56.840> to<00:07:57.000> a<00:07:57.159> different 00:07:57.430 --> 00:07:57.440 align:start position:0% every time they went to a different 00:07:57.440 --> 00:07:59.589 align:start position:0% every time they went to a different company<00:07:57.759> so<00:07:58.000> they<00:07:58.120> said<00:07:58.720> you<00:07:58.840> know<00:07:59.520> the 00:07:59.589 --> 00:07:59.599 align:start position:0% company so they said you know the 00:07:59.599 --> 00:08:01.309 align:start position:0% company so they said you know the Forward<00:08:00.039> Thinking<00:08:00.400> people<00:08:00.599> were<00:08:00.800> able<00:08:01.000> to<00:08:01.120> say 00:08:01.309 --> 00:08:01.319 align:start position:0% Forward Thinking people were able to say 00:08:01.319 --> 00:08:03.110 align:start position:0% Forward Thinking people were able to say let's<00:08:01.560> open<00:08:01.879> source<00:08:02.199> this<00:08:02.400> such<00:08:02.639> that<00:08:02.840> I<00:08:02.919> can 00:08:03.110 --> 00:08:03.120 align:start position:0% let's open source this such that I can 00:08:03.120 --> 00:08:05.230 align:start position:0% let's open source this such that I can carry<00:08:03.360> it<00:08:03.520> with<00:08:03.720> me<00:08:04.240> whereas<00:08:04.599> nowadays<00:08:05.120> I 00:08:05.230 --> 00:08:05.240 align:start position:0% carry it with me whereas nowadays I 00:08:05.240 --> 00:08:07.189 align:start position:0% carry it with me whereas nowadays I think<00:08:05.400> you're<00:08:05.599> starting<00:08:05.960> to<00:08:06.120> see<00:08:06.520> just<00:08:06.879> a<00:08:07.000> lot 00:08:07.189 --> 00:08:07.199 align:start position:0% think you're starting to see just a lot 00:08:07.199 --> 00:08:10.869 align:start position:0% think you're starting to see just a lot more<00:08:07.560> Innovation<00:08:08.360> happening<00:08:09.360> right<00:08:09.560> in<00:08:09.919> open 00:08:10.869 --> 00:08:10.879 align:start position:0% more Innovation happening right in open 00:08:10.879 --> 00:08:13.430 align:start position:0% more Innovation happening right in open source<00:08:11.879> out<00:08:12.039> of<00:08:12.199> the<00:08:12.360> box<00:08:12.720> as<00:08:12.840> opposed<00:08:13.159> to 00:08:13.430 --> 00:08:13.440 align:start position:0% source out of the box as opposed to 00:08:13.440 --> 00:08:15.749 align:start position:0% source out of the box as opposed to having<00:08:13.759> you<00:08:13.879> know<00:08:14.639> being<00:08:14.919> cooked<00:08:15.199> up<00:08:15.319> in<00:08:15.520> some 00:08:15.749 --> 00:08:15.759 align:start position:0% having you know being cooked up in some 00:08:15.759 --> 00:08:17.990 align:start position:0% having you know being cooked up in some lab<00:08:16.080> somewhere<00:08:16.919> it's<00:08:17.159> now<00:08:17.360> being<00:08:17.639> done<00:08:17.840> in 00:08:17.990 --> 00:08:18.000 align:start position:0% lab somewhere it's now being done in 00:08:18.000 --> 00:08:19.670 align:start position:0% lab somewhere it's now being done in open<00:08:18.199> source<00:08:18.479> that<00:08:18.599> being<00:08:18.800> said<00:08:19.039> I<00:08:19.159> think<00:08:19.479> that 00:08:19.670 --> 00:08:19.680 align:start position:0% open source that being said I think that 00:08:19.680 --> 00:08:21.790 align:start position:0% open source that being said I think that especially<00:08:20.000> on<00:08:20.080> the<00:08:20.199> NLP<00:08:20.840> side<00:08:21.000> of<00:08:21.159> things 00:08:21.790 --> 00:08:21.800 align:start position:0% especially on the NLP side of things 00:08:21.800 --> 00:08:23.589 align:start position:0% especially on the NLP side of things it's<00:08:22.000> still<00:08:22.240> a<00:08:22.360> little<00:08:22.560> bit<00:08:22.759> trailing 00:08:23.589 --> 00:08:23.599 align:start position:0% it's still a little bit trailing 00:08:23.599 --> 00:08:25.230 align:start position:0% it's still a little bit trailing obviously<00:08:24.000> there's<00:08:24.159> a<00:08:24.319> lot<00:08:24.479> of<00:08:24.680> good<00:08:24.879> new 00:08:25.230 --> 00:08:25.240 align:start position:0% obviously there's a lot of good new 00:08:25.240 --> 00:08:27.070 align:start position:0% obviously there's a lot of good new projects<00:08:25.639> out<00:08:25.879> there<00:08:26.319> the<00:08:26.479> really<00:08:26.840> the<00:08:26.960> the 00:08:27.070 --> 00:08:27.080 align:start position:0% projects out there the really the the 00:08:27.080 --> 00:08:28.430 align:start position:0% projects out there the really the the biggest<00:08:27.360> challenge<00:08:27.680> for<00:08:27.840> open<00:08:28.080> source<00:08:28.360> I 00:08:28.430 --> 00:08:28.440 align:start position:0% biggest challenge for open source I 00:08:28.440 --> 00:08:30.270 align:start position:0% biggest challenge for open source I think<00:08:28.599> when<00:08:28.680> it<00:08:28.800> comes<00:08:29.000> to<00:08:29.120> n<00:08:29.639> P<00:08:29.840> not<00:08:29.960> so<00:08:30.120> much 00:08:30.270 --> 00:08:30.280 align:start position:0% think when it comes to n P not so much 00:08:30.280 --> 00:08:33.430 align:start position:0% think when it comes to n P not so much search<00:08:30.599> but<00:08:30.879> NLP<00:08:31.879> is<00:08:32.240> just<00:08:32.599> having<00:08:32.880> the<00:08:33.039> sheer 00:08:33.430 --> 00:08:33.440 align:start position:0% search but NLP is just having the sheer 00:08:33.440 --> 00:08:35.509 align:start position:0% search but NLP is just having the sheer amount<00:08:33.680> of<00:08:33.919> data<00:08:34.240> and<00:08:34.440> being<00:08:34.680> able<00:08:34.959> as<00:08:35.080> an<00:08:35.240> open 00:08:35.509 --> 00:08:35.519 align:start position:0% amount of data and being able as an open 00:08:35.519 --> 00:08:37.149 align:start position:0% amount of data and being able as an open source<00:08:35.800> Community<00:08:36.200> to<00:08:36.440> deal<00:08:36.800> with<00:08:37.000> the 00:08:37.149 --> 00:08:37.159 align:start position:0% source Community to deal with the 00:08:37.159 --> 00:08:40.029 align:start position:0% source Community to deal with the pedabytes<00:08:37.560> of<00:08:37.919> data<00:08:38.599> that<00:08:38.760> can<00:08:38.919> feed<00:08:39.320> into<00:08:39.919> you 00:08:40.029 --> 00:08:40.039 align:start position:0% pedabytes of data that can feed into you 00:08:40.039 --> 00:08:42.630 align:start position:0% pedabytes of data that can feed into you know<00:08:40.360> the<00:08:40.680> the<00:08:40.880> really<00:08:41.120> large<00:08:41.479> scale<00:08:42.080> models 00:08:42.630 --> 00:08:42.640 align:start position:0% know the the really large scale models 00:08:42.640 --> 00:08:45.110 align:start position:0% know the the really large scale models that<00:08:42.760> you're<00:08:42.919> going<00:08:43.120> to<00:08:43.320> build<00:08:44.120> around<00:08:44.920> uh<00:08:45.040> you 00:08:45.110 --> 00:08:45.120 align:start position:0% that you're going to build around uh you 00:08:45.120 --> 00:08:46.710 align:start position:0% that you're going to build around uh you know<00:08:45.240> whether<00:08:45.480> that's<00:08:45.640> machine<00:08:46.040> translation 00:08:46.710 --> 00:08:46.720 align:start position:0% know whether that's machine translation 00:08:46.720 --> 00:08:48.990 align:start position:0% know whether that's machine translation or<00:08:46.959> question<00:08:47.320> answering<00:08:47.800> or<00:08:48.000> whatever<00:08:48.279> it<00:08:48.440> is 00:08:48.990 --> 00:08:49.000 align:start position:0% or question answering or whatever it is 00:08:49.000 --> 00:08:51.670 align:start position:0% or question answering or whatever it is that<00:08:49.200> takes<00:08:50.000> a<00:08:50.200> lot<00:08:50.360> of<00:08:50.640> effort<00:08:51.040> and<00:08:51.200> a<00:08:51.320> lot<00:08:51.480> of 00:08:51.670 --> 00:08:51.680 align:start position:0% that takes a lot of effort and a lot of 00:08:51.680 --> 00:08:54.630 align:start position:0% that takes a lot of effort and a lot of compute<00:08:52.200> capabilities<00:08:52.880> and<00:08:53.080> as<00:08:53.279> like<00:08:54.200> uh<00:08:54.360> open 00:08:54.630 --> 00:08:54.640 align:start position:0% compute capabilities and as like uh open 00:08:54.640 --> 00:08:56.630 align:start position:0% compute capabilities and as like uh open source<00:08:54.920> Community<00:08:55.720> you<00:08:55.920> kind<00:08:56.040> of<00:08:56.160> have<00:08:56.279> to<00:08:56.399> beg 00:08:56.630 --> 00:08:56.640 align:start position:0% source Community you kind of have to beg 00:08:56.640 --> 00:08:58.750 align:start position:0% source Community you kind of have to beg and<00:08:56.839> borrow<00:08:57.279> to<00:08:57.480> get<00:08:57.720> that<00:08:57.959> kind<00:08:58.079> of<00:08:58.320> stuff 00:08:58.750 --> 00:08:58.760 align:start position:0% and borrow to get that kind of stuff 00:08:58.760 --> 00:09:00.630 align:start position:0% and borrow to get that kind of stuff together<00:08:59.160> right<00:08:59.480> so<00:08:59.920> those<00:09:00.079> are<00:09:00.279> I<00:09:00.360> think<00:09:00.519> some 00:09:00.630 --> 00:09:00.640 align:start position:0% together right so those are I think some 00:09:00.640 --> 00:09:02.630 align:start position:0% together right so those are I think some of<00:09:00.760> the<00:09:00.880> big<00:09:01.079> challenges<00:09:01.600> on<00:09:01.760> the<00:09:01.920> open<00:09:02.279> source 00:09:02.630 --> 00:09:02.640 align:start position:0% of the big challenges on the open source 00:09:02.640 --> 00:09:04.509 align:start position:0% of the big challenges on the open source side<00:09:03.240> that<00:09:03.399> being<00:09:03.600> said<00:09:03.839> you<00:09:03.920> know<00:09:04.120> I<00:09:04.160> mean 00:09:04.509 --> 00:09:04.519 align:start position:0% side that being said you know I mean 00:09:04.519 --> 00:09:06.030 align:start position:0% side that being said you know I mean there's<00:09:04.920> just<00:09:05.040> a<00:09:05.200> lot<00:09:05.360> of<00:09:05.519> interesting 00:09:06.030 --> 00:09:06.040 align:start position:0% there's just a lot of interesting 00:09:06.040 --> 00:09:08.269 align:start position:0% there's just a lot of interesting projects<00:09:06.440> out<00:09:06.680> there<00:09:06.880> with<00:09:07.040> NLP<00:09:07.720> such<00:09:07.920> that 00:09:08.269 --> 00:09:08.279 align:start position:0% projects out there with NLP such that 00:09:08.279 --> 00:09:09.910 align:start position:0% projects out there with NLP such that you<00:09:08.360> know<00:09:08.480> for<00:09:08.640> a<00:09:08.839> long<00:09:09.160> time<00:09:09.440> I<00:09:09.560> would<00:09:09.720> always 00:09:09.910 --> 00:09:09.920 align:start position:0% you know for a long time I would always 00:09:09.920 --> 00:09:11.750 align:start position:0% you know for a long time I would always say<00:09:10.160> oh<00:09:10.320> well<00:09:10.440> NLP<00:09:10.880> is<00:09:11.079> great<00:09:11.279> and<00:09:11.399> I<00:09:11.519> love 00:09:11.750 --> 00:09:11.760 align:start position:0% say oh well NLP is great and I love 00:09:11.760 --> 00:09:14.750 align:start position:0% say oh well NLP is great and I love working<00:09:12.120> on<00:09:12.279> it<00:09:12.600> but<00:09:13.480> put<00:09:13.680> it<00:09:13.800> in<00:09:14.040> practice<00:09:14.440> is 00:09:14.750 --> 00:09:14.760 align:start position:0% working on it but put it in practice is 00:09:14.760 --> 00:09:17.069 align:start position:0% working on it but put it in practice is really<00:09:15.079> challenging<00:09:15.880> and<00:09:16.279> and<00:09:16.519> you<00:09:16.640> know<00:09:16.920> it 00:09:17.069 --> 00:09:17.079 align:start position:0% really challenging and and you know it 00:09:17.079 --> 00:09:19.030 align:start position:0% really challenging and and you know it demos<00:09:17.560> very<00:09:17.800> well<00:09:18.079> but<00:09:18.200> it<00:09:18.360> doesn't<00:09:18.680> always 00:09:19.030 --> 00:09:19.040 align:start position:0% demos very well but it doesn't always 00:09:19.040 --> 00:09:21.269 align:start position:0% demos very well but it doesn't always perform<00:09:19.519> very<00:09:19.720> well<00:09:20.040> whereas<00:09:20.720> I<00:09:20.800> think<00:09:20.959> in<00:09:21.200> you 00:09:21.269 --> 00:09:21.279 align:start position:0% perform very well whereas I think in you 00:09:21.279 --> 00:09:24.350 align:start position:0% perform very well whereas I think in you know<00:09:21.440> say<00:09:21.720> the<00:09:22.279> last<00:09:23.279> I<00:09:23.399> don't<00:09:23.519> know<00:09:23.640> 3<00:09:23.839> to<00:09:24.040> 5 00:09:24.350 --> 00:09:24.360 align:start position:0% know say the last I don't know 3 to 5 00:09:24.360 --> 00:09:26.990 align:start position:0% know say the last I don't know 3 to 5 years<00:09:25.160> maybe<00:09:25.480> even<00:09:25.839> less<00:09:26.480> you're<00:09:26.720> really 00:09:26.990 --> 00:09:27.000 align:start position:0% years maybe even less you're really 00:09:27.000 --> 00:09:28.990 align:start position:0% years maybe even less you're really starting<00:09:27.360> to<00:09:27.519> see<00:09:27.959> really<00:09:28.240> large<00:09:28.600> scale 00:09:28.990 --> 00:09:29.000 align:start position:0% starting to see really large scale 00:09:29.000 --> 00:09:31.269 align:start position:0% starting to see really large scale practice<00:09:29.360> iCal<00:09:29.920> applications<00:09:30.760> where<00:09:31.000> people 00:09:31.269 --> 00:09:31.279 align:start position:0% practice iCal applications where people 00:09:31.279 --> 00:09:34.430 align:start position:0% practice iCal applications where people are<00:09:31.560> leveraging<00:09:32.160> NLP<00:09:32.760> on<00:09:32.880> a<00:09:33.079> daily<00:09:33.480> basis<00:09:34.279> and 00:09:34.430 --> 00:09:34.440 align:start position:0% are leveraging NLP on a daily basis and 00:09:34.440 --> 00:09:36.350 align:start position:0% are leveraging NLP on a daily basis and it's<00:09:34.760> it's<00:09:35.120> becoming<00:09:35.640> natural<00:09:36.120> whether 00:09:36.350 --> 00:09:36.360 align:start position:0% it's it's becoming natural whether 00:09:36.360 --> 00:09:38.470 align:start position:0% it's it's becoming natural whether that's<00:09:36.560> on<00:09:36.720> your<00:09:36.959> phone<00:09:37.360> or<00:09:37.519> on<00:09:37.640> a<00:09:37.800> website 00:09:38.470 --> 00:09:38.480 align:start position:0% that's on your phone or on a website 00:09:38.480 --> 00:09:40.470 align:start position:0% that's on your phone or on a website whatever<00:09:39.120> you're<00:09:39.320> able<00:09:39.560> to<00:09:39.800> interact<00:09:40.320> with 00:09:40.470 --> 00:09:40.480 align:start position:0% whatever you're able to interact with 00:09:40.480 --> 00:09:42.790 align:start position:0% whatever you're able to interact with the<00:09:40.600> machine<00:09:40.959> in<00:09:41.120> a<00:09:41.320> natural<00:09:41.760> way<00:09:42.360> speak<00:09:42.600> the 00:09:42.790 --> 00:09:42.800 align:start position:0% the machine in a natural way speak the 00:09:42.800 --> 00:09:45.030 align:start position:0% the machine in a natural way speak the language<00:09:43.360> right<00:09:44.120> um<00:09:44.360> the<00:09:44.480> other<00:09:44.640> interesting 00:09:45.030 --> 00:09:45.040 align:start position:0% language right um the other interesting 00:09:45.040 --> 00:09:47.670 align:start position:0% language right um the other interesting thing<00:09:45.240> I<00:09:45.399> think<00:09:45.680> is<00:09:46.279> uh<00:09:46.920> you<00:09:47.040> know<00:09:47.279> a<00:09:47.360> lot<00:09:47.519> of 00:09:47.670 --> 00:09:47.680 align:start position:0% thing I think is uh you know a lot of 00:09:47.680 --> 00:09:49.269 align:start position:0% thing I think is uh you know a lot of people<00:09:47.959> talk<00:09:48.519> your<00:09:48.720> question<00:09:49.040> about 00:09:49.269 --> 00:09:49.279 align:start position:0% people talk your question about 00:09:49.279 --> 00:09:51.670 align:start position:0% people talk your question about structured<00:09:49.800> and<00:09:50.320> unstructured<00:09:51.320> um<00:09:51.440> it's<00:09:51.560> one 00:09:51.670 --> 00:09:51.680 align:start position:0% structured and unstructured um it's one 00:09:51.680 --> 00:09:53.550 align:start position:0% structured and unstructured um it's one of<00:09:51.800> my<00:09:52.000> pet<00:09:52.240> peeve<00:09:52.560> terms<00:09:52.920> because<00:09:53.120> I<00:09:53.279> actually 00:09:53.550 --> 00:09:53.560 align:start position:0% of my pet peeve terms because I actually 00:09:53.560 --> 00:09:55.310 align:start position:0% of my pet peeve terms because I actually hate<00:09:53.760> the<00:09:53.839> word<00:09:54.079> unstructured<00:09:54.839> when<00:09:54.959> it<00:09:55.079> comes 00:09:55.310 --> 00:09:55.320 align:start position:0% hate the word unstructured when it comes 00:09:55.320 --> 00:09:57.470 align:start position:0% hate the word unstructured when it comes to<00:09:55.560> text<00:09:56.360> and<00:09:56.480> the<00:09:56.600> reason<00:09:56.920> why<00:09:57.079> is<00:09:57.240> if<00:09:57.320> you 00:09:57.470 --> 00:09:57.480 align:start position:0% to text and the reason why is if you 00:09:57.480 --> 00:09:58.990 align:start position:0% to text and the reason why is if you think<00:09:57.640> about<00:09:57.839> it<00:09:58.079> right<00:09:58.279> text<00:09:58.560> is<00:09:58.720> one<00:09:58.839> of<00:09:58.920> the 00:09:58.990 --> 00:09:59.000 align:start position:0% think about it right text is one of the 00:09:59.000 --> 00:10:01.590 align:start position:0% think about it right text is one of the most<00:09:59.399> highly<00:09:59.680> structured<00:10:00.200> things<00:10:00.480> we<00:10:00.720> have 00:10:01.590 --> 00:10:01.600 align:start position:0% most highly structured things we have 00:10:01.600 --> 00:10:03.269 align:start position:0% most highly structured things we have right<00:10:01.880> we're<00:10:02.079> just<00:10:02.279> not<00:10:02.519> very<00:10:02.839> good<00:10:03.079> at 00:10:03.269 --> 00:10:03.279 align:start position:0% right we're just not very good at 00:10:03.279 --> 00:10:05.910 align:start position:0% right we're just not very good at telling<00:10:03.640> the<00:10:03.959> computer<00:10:04.959> what<00:10:05.200> that<00:10:05.399> structure 00:10:05.910 --> 00:10:05.920 align:start position:0% telling the computer what that structure 00:10:05.920 --> 00:10:07.790 align:start position:0% telling the computer what that structure is<00:10:06.200> and<00:10:06.399> and<00:10:06.560> letting<00:10:06.880> the<00:10:07.000> computer<00:10:07.519> take 00:10:07.790 --> 00:10:07.800 align:start position:0% is and and letting the computer take 00:10:07.800 --> 00:10:10.389 align:start position:0% is and and letting the computer take advantage<00:10:08.200> of<00:10:08.399> those<00:10:08.760> right<00:10:09.040> the<00:10:09.120> grammar<00:10:09.519> and 00:10:10.389 --> 00:10:10.399 align:start position:0% advantage of those right the grammar and 00:10:10.399 --> 00:10:12.430 align:start position:0% advantage of those right the grammar and deal<00:10:10.560> with<00:10:10.680> the<00:10:10.839> grammars<00:10:11.480> and<00:10:12.079> and<00:10:12.279> the 00:10:12.430 --> 00:10:12.440 align:start position:0% deal with the grammars and and the 00:10:12.440 --> 00:10:14.430 align:start position:0% deal with the grammars and and the relationships<00:10:13.360> and<00:10:13.640> and<00:10:13.800> all<00:10:13.920> of<00:10:14.079> those<00:10:14.240> kinds 00:10:14.430 --> 00:10:14.440 align:start position:0% relationships and and all of those kinds 00:10:14.440 --> 00:10:17.350 align:start position:0% relationships and and all of those kinds of<00:10:14.560> things<00:10:14.880> the<00:10:15.480> ambiguity<00:10:16.480> um<00:10:17.079> that's<00:10:17.279> I 00:10:17.350 --> 00:10:17.360 align:start position:0% of things the ambiguity um that's I 00:10:17.360 --> 00:10:18.630 align:start position:0% of things the ambiguity um that's I think<00:10:17.519> one<00:10:17.640> of<00:10:17.720> the<00:10:17.839> cool<00:10:18.079> things<00:10:18.279> that's<00:10:18.440> been 00:10:18.630 --> 00:10:18.640 align:start position:0% think one of the cool things that's been 00:10:18.640 --> 00:10:20.550 align:start position:0% think one of the cool things that's been happening<00:10:19.040> as<00:10:19.160> well<00:10:19.399> is<00:10:19.600> more<00:10:19.839> and<00:10:20.040> more 00:10:20.550 --> 00:10:20.560 align:start position:0% happening as well is more and more 00:10:20.560 --> 00:10:23.190 align:start position:0% happening as well is more and more capabilities<00:10:21.279> are<00:10:21.920> coming<00:10:22.240> around<00:10:22.680> that<00:10:22.880> make 00:10:23.190 --> 00:10:23.200 align:start position:0% capabilities are coming around that make 00:10:23.200 --> 00:10:25.190 align:start position:0% capabilities are coming around that make that<00:10:23.560> easier<00:10:23.959> to<00:10:24.160> deal<00:10:24.519> with<00:10:24.880> right<00:10:25.000> and 00:10:25.190 --> 00:10:25.200 align:start position:0% that easier to deal with right and 00:10:25.200 --> 00:10:27.069 align:start position:0% that easier to deal with right and obviously<00:10:25.519> you<00:10:25.600> know<00:10:25.800> more<00:10:26.120> universities<00:10:26.800> are 00:10:27.069 --> 00:10:27.079 align:start position:0% obviously you know more universities are 00:10:27.079 --> 00:10:29.430 align:start position:0% obviously you know more universities are teaching<00:10:27.519> this<00:10:27.760> kind<00:10:27.920> of<00:10:28.120> stuff<00:10:28.800> more<00:10:29.000> people 00:10:29.430 --> 00:10:29.440 align:start position:0% teaching this kind of stuff more people 00:10:29.440 --> 00:10:32.150 align:start position:0% teaching this kind of stuff more people are<00:10:29.560> feeling<00:10:30.040> comfortable<00:10:30.800> dealing<00:10:31.360> with 00:10:32.150 --> 00:10:32.160 align:start position:0% are feeling comfortable dealing with 00:10:32.160 --> 00:10:34.590 align:start position:0% are feeling comfortable dealing with probabilities<00:10:33.000> and<00:10:33.279> statistics<00:10:34.040> as<00:10:34.240> opposed 00:10:34.590 --> 00:10:34.600 align:start position:0% probabilities and statistics as opposed 00:10:34.600 --> 00:10:36.069 align:start position:0% probabilities and statistics as opposed to<00:10:34.920> you<00:10:35.040> know<00:10:35.240> just<00:10:35.399> kind<00:10:35.519> of<00:10:35.639> the<00:10:35.760> pure 00:10:36.069 --> 00:10:36.079 align:start position:0% to you know just kind of the pure 00:10:36.079 --> 00:10:38.190 align:start position:0% to you know just kind of the pure relational<00:10:36.639> models<00:10:37.120> that<00:10:37.600> you<00:10:37.720> know<00:10:37.880> probably 00:10:38.190 --> 00:10:38.200 align:start position:0% relational models that you know probably 00:10:38.200 --> 00:10:39.990 align:start position:0% relational models that you know probably you<00:10:38.320> and<00:10:38.480> I<00:10:38.600> were<00:10:38.800> trained<00:10:39.160> on<00:10:39.440> way<00:10:39.639> back<00:10:39.839> when 00:10:39.990 --> 00:10:40.000 align:start position:0% you and I were trained on way back when 00:10:40.000 --> 00:10:43.269 align:start position:0% you and I were trained on way back when we<00:10:40.120> were<00:10:40.959> undergrads<00:10:41.959> uh<00:10:42.120> and<00:10:42.279> so<00:10:42.680> I<00:10:42.760> think<00:10:43.160> you 00:10:43.269 --> 00:10:43.279 align:start position:0% we were undergrads uh and so I think you 00:10:43.279 --> 00:10:44.870 align:start position:0% we were undergrads uh and so I think you know<00:10:43.480> as<00:10:43.600> you<00:10:43.760> get<00:10:43.959> that<00:10:44.200> Comfort<00:10:44.560> level 00:10:44.870 --> 00:10:44.880 align:start position:0% know as you get that Comfort level 00:10:44.880 --> 00:10:47.310 align:start position:0% know as you get that Comfort level raised<00:10:45.399> as<00:10:45.560> the<00:10:45.680> open<00:10:46.000> source<00:10:46.360> gets<00:10:46.639> better 00:10:47.310 --> 00:10:47.320 align:start position:0% raised as the open source gets better 00:10:47.320 --> 00:10:49.710 align:start position:0% raised as the open source gets better that<00:10:47.480> raises<00:10:47.959> the<00:10:48.160> bar<00:10:48.560> for<00:10:48.880> everybody<00:10:49.600> and 00:10:49.710 --> 00:10:49.720 align:start position:0% that raises the bar for everybody and 00:10:49.720 --> 00:10:51.269 align:start position:0% that raises the bar for everybody and that's<00:10:49.920> kind<00:10:50.040> of<00:10:50.240> you<00:10:50.320> know<00:10:50.760> in<00:10:50.880> my<00:10:51.040> book 00:10:51.269 --> 00:10:51.279 align:start position:0% that's kind of you know in my book 00:10:51.279 --> 00:10:53.550 align:start position:0% that's kind of you know in my book taming<00:10:51.639> text<00:10:51.920> to<00:10:52.079> try<00:10:52.279> to<00:10:52.760> address<00:10:53.279> that<00:10:53.440> kind 00:10:53.550 --> 00:10:53.560 align:start position:0% taming text to try to address that kind 00:10:53.560 --> 00:10:55.590 align:start position:0% taming text to try to address that kind of<00:10:53.720> crowd<00:10:54.040> of<00:10:54.279> people<00:10:54.600> who<00:10:54.760> are<00:10:55.040> getting<00:10:55.480> who 00:10:55.590 --> 00:10:55.600 align:start position:0% of crowd of people who are getting who 00:10:55.600 --> 00:10:57.990 align:start position:0% of crowd of people who are getting who are<00:10:55.800> new<00:10:56.040> to<00:10:56.240> all<00:10:56.519> this<00:10:56.720> stuff<00:10:57.279> how<00:10:57.360> do<00:10:57.560> I<00:10:57.760> start 00:10:57.990 --> 00:10:58.000 align:start position:0% are new to all this stuff how do I start 00:10:58.000 --> 00:11:00.470 align:start position:0% are new to all this stuff how do I start to<00:10:58.240> deal<00:10:58.560> with<00:10:58.720> the<00:10:58.920> fact<00:10:59.480> that<00:10:59.839> I<00:10:59.959> may<00:11:00.120> not<00:11:00.320> get 00:11:00.470 --> 00:11:00.480 align:start position:0% to deal with the fact that I may not get 00:11:00.480 --> 00:11:02.389 align:start position:0% to deal with the fact that I may not get the<00:11:00.639> same<00:11:00.920> answer<00:11:01.320> every<00:11:01.560> time<00:11:01.760> I<00:11:01.920> ask<00:11:02.160> the 00:11:02.389 --> 00:11:02.399 align:start position:0% the same answer every time I ask the 00:11:02.399 --> 00:11:03.870 align:start position:0% the same answer every time I ask the question<00:11:02.920> right<00:11:03.079> because<00:11:03.320> the<00:11:03.440> DAT<00:11:03.720> has 00:11:03.870 --> 00:11:03.880 align:start position:0% question right because the DAT has 00:11:03.880 --> 00:11:06.110 align:start position:0% question right because the DAT has changed<00:11:04.320> or<00:11:04.760> or<00:11:04.959> because<00:11:05.200> there's<00:11:05.399> some<00:11:05.600> fuzzy 00:11:06.110 --> 00:11:06.120 align:start position:0% changed or or because there's some fuzzy 00:11:06.120 --> 00:11:08.110 align:start position:0% changed or or because there's some fuzzy fuzziness<00:11:06.680> in<00:11:06.880> there<00:11:07.160> that<00:11:07.480> you<00:11:07.560> know<00:11:07.720> I<00:11:07.839> just 00:11:08.110 --> 00:11:08.120 align:start position:0% fuzziness in there that you know I just 00:11:08.120 --> 00:11:10.350 align:start position:0% fuzziness in there that you know I just I<00:11:08.240> I<00:11:08.360> haven't<00:11:08.639> accounted<00:11:09.040> for<00:11:09.839> uh<00:11:10.000> by<00:11:10.120> the<00:11:10.240> way 00:11:10.350 --> 00:11:10.360 align:start position:0% I I haven't accounted for uh by the way 00:11:10.360 --> 00:11:12.389 align:start position:0% I I haven't accounted for uh by the way you<00:11:10.440> know<00:11:10.880> uh<00:11:11.040> Tam<00:11:11.480> is<00:11:11.560> a<00:11:11.680> great<00:11:11.880> book<00:11:12.120> actually 00:11:12.389 --> 00:11:12.399 align:start position:0% you know uh Tam is a great book actually 00:11:12.399 --> 00:11:13.990 align:start position:0% you know uh Tam is a great book actually Tom<00:11:12.600> Morton<00:11:12.839> and<00:11:12.959> I<00:11:13.040> were<00:11:13.200> in<00:11:13.320> the<00:11:13.399> same<00:11:13.600> PD 00:11:13.990 --> 00:11:14.000 align:start position:0% Tom Morton and I were in the same PD 00:11:14.000 --> 00:11:16.509 align:start position:0% Tom Morton and I were in the same PD program<00:11:14.760> at<00:11:14.959> pen<00:11:15.279> and<00:11:15.519> kind<00:11:15.639> of<00:11:15.760> he<00:11:15.959> still<00:11:16.240> is 00:11:16.509 --> 00:11:16.519 align:start position:0% program at pen and kind of he still is 00:11:16.519 --> 00:11:19.069 align:start position:0% program at pen and kind of he still is there<00:11:17.360> uh<00:11:17.800> uh<00:11:17.920> working<00:11:18.160> for<00:11:18.399> Comcast<00:11:18.800> so<00:11:18.959> this 00:11:19.069 --> 00:11:19.079 align:start position:0% there uh uh working for Comcast so this 00:11:19.079 --> 00:11:21.269 align:start position:0% there uh uh working for Comcast so this is<00:11:19.279> interesting<00:11:20.040> connection<00:11:20.639> and<00:11:20.920> I<00:11:21.040> actually 00:11:21.269 --> 00:11:21.279 align:start position:0% is interesting connection and I actually 00:11:21.279 --> 00:11:24.629 align:start position:0% is interesting connection and I actually enjoyed<00:11:21.639> it<00:11:22.480> uh<00:11:22.720> I<00:11:22.880> yeah<00:11:23.000> I<00:11:23.160> wonder<00:11:24.160> uh<00:11:24.480> it's 00:11:24.629 --> 00:11:24.639 align:start position:0% enjoyed it uh I yeah I wonder uh it's 00:11:24.639 --> 00:11:26.150 align:start position:0% enjoyed it uh I yeah I wonder uh it's it's<00:11:24.760> a<00:11:24.880> very<00:11:25.040> useful<00:11:25.399> book<00:11:25.600> and<00:11:25.720> it's<00:11:25.839> a<00:11:25.959> good 00:11:26.150 --> 00:11:26.160 align:start position:0% it's a very useful book and it's a good 00:11:26.160 --> 00:11:30.030 align:start position:0% it's a very useful book and it's a good primer<00:11:27.160> uh<00:11:27.399> on<00:11:27.680> on<00:11:27.959> on<00:11:28.120> text<00:11:28.399> processing<00:11:29.680> uh<00:11:29.839> so 00:11:30.030 --> 00:11:30.040 align:start position:0% primer uh on on on text processing uh so 00:11:30.040 --> 00:11:31.870 align:start position:0% primer uh on on on text processing uh so I<00:11:30.120> wonder 00:11:31.870 --> 00:11:31.880 align:start position:0% I wonder 00:11:31.880 --> 00:11:35.430 align:start position:0% I wonder um<00:11:32.880> um<00:11:33.360> so<00:11:33.560> in<00:11:33.680> terms<00:11:33.920> of<00:11:34.079> scale<00:11:34.639> right<00:11:35.040> uh<00:11:35.160> so<00:11:35.320> I 00:11:35.430 --> 00:11:35.440 align:start position:0% um um so in terms of scale right uh so I 00:11:35.440 --> 00:11:38.750 align:start position:0% um um so in terms of scale right uh so I was<00:11:35.600> at<00:11:35.839> the<00:11:36.600> uh<00:11:36.959> 2007<00:11:37.959> machine<00:11:38.279> translation 00:11:38.750 --> 00:11:38.760 align:start position:0% was at the uh 2007 machine translation 00:11:38.760 --> 00:11:42.269 align:start position:0% was at the uh 2007 machine translation Summit<00:11:39.760> where<00:11:40.200> Google<00:11:41.040> uh<00:11:41.160> translate<00:11:41.959> talked 00:11:42.269 --> 00:11:42.279 align:start position:0% Summit where Google uh translate talked 00:11:42.279 --> 00:11:44.430 align:start position:0% Summit where Google uh translate talked for<00:11:42.440> the<00:11:42.600> first<00:11:42.920> time<00:11:43.720> and<00:11:43.839> France<00:11:44.160> o 00:11:44.430 --> 00:11:44.440 align:start position:0% for the first time and France o 00:11:44.440 --> 00:11:45.790 align:start position:0% for the first time and France o presented<00:11:44.760> the<00:11:44.959> model<00:11:45.200> and<00:11:45.360> he<00:11:45.440> said<00:11:45.639> it's 00:11:45.790 --> 00:11:45.800 align:start position:0% presented the model and he said it's 00:11:45.800 --> 00:11:46.949 align:start position:0% presented the model and he said it's very<00:11:45.959> simple<00:11:46.200> if<00:11:46.279> you<00:11:46.360> want<00:11:46.519> to<00:11:46.600> real<00:11:46.800> like 00:11:46.949 --> 00:11:46.959 align:start position:0% very simple if you want to real like 00:11:46.959 --> 00:11:48.710 align:start position:0% very simple if you want to real like your<00:11:47.120> translation<00:11:48.079> let's<00:11:48.279> just<00:11:48.440> collect 00:11:48.710 --> 00:11:48.720 align:start position:0% your translation let's just collect 00:11:48.720 --> 00:11:50.829 align:start position:0% your translation let's just collect several<00:11:49.040> trillion<00:11:49.519> words<00:11:50.079> and<00:11:50.240> let's<00:11:50.480> just<00:11:50.639> do 00:11:50.829 --> 00:11:50.839 align:start position:0% several trillion words and let's just do 00:11:50.839 --> 00:11:53.990 align:start position:0% several trillion words and let's just do seven<00:11:51.240> grams<00:11:52.079> right<00:11:52.279> and<00:11:52.920> essentially<00:11:53.720> that's 00:11:53.990 --> 00:11:54.000 align:start position:0% seven grams right and essentially that's 00:11:54.000 --> 00:11:55.590 align:start position:0% seven grams right and essentially that's how<00:11:54.440> how<00:11:54.560> you<00:11:54.680> solve<00:11:54.959> this<00:11:55.120> problem<00:11:55.360> so<00:11:55.480> I 00:11:55.590 --> 00:11:55.600 align:start position:0% how how you solve this problem so I 00:11:55.600 --> 00:11:58.310 align:start position:0% how how you solve this problem so I wonder<00:11:55.920> this<00:11:56.040> a<00:11:56.200> small<00:11:57.160> this<00:11:57.399> a<00:11:57.560> small<00:11:57.880> problem 00:11:58.310 --> 00:11:58.320 align:start position:0% wonder this a small this a small problem 00:11:58.320 --> 00:12:00.590 align:start position:0% wonder this a small this a small problem that's<00:11:58.560> right<00:11:58.880> so<00:11:59.279> I<00:11:59.360> wonder<00:12:00.120> uh<00:12:00.240> given<00:12:00.480> the 00:12:00.590 --> 00:12:00.600 align:start position:0% that's right so I wonder uh given the 00:12:00.600 --> 00:12:02.670 align:start position:0% that's right so I wonder uh given the scale<00:12:00.920> you<00:12:01.040> mentioned<00:12:01.560> at<00:12:01.920> sales<00:12:02.320> force 00:12:02.670 --> 00:12:02.680 align:start position:0% scale you mentioned at sales force 00:12:02.680 --> 00:12:05.389 align:start position:0% scale you mentioned at sales force deployment<00:12:03.680> uh<00:12:03.880> can<00:12:04.079> I<00:12:04.279> do<00:12:04.480> a<00:12:04.600> seven<00:12:04.920> G<00:12:05.160> model 00:12:05.389 --> 00:12:05.399 align:start position:0% deployment uh can I do a seven G model 00:12:05.399 --> 00:12:08.430 align:start position:0% deployment uh can I do a seven G model of<00:12:05.519> several<00:12:05.839> trillion<00:12:06.279> words<00:12:07.160> uh<00:12:07.600> with<00:12:08.040> solar 00:12:08.430 --> 00:12:08.440 align:start position:0% of several trillion words uh with solar 00:12:08.440 --> 00:12:13.350 align:start position:0% of several trillion words uh with solar Lucin<00:12:09.440> uh<00:12:10.200> uh<00:12:10.880> we<00:12:11.120> seven<00:12:11.440> trillion<00:12:11.880> words<00:12:12.360> in 00:12:13.350 --> 00:12:13.360 align:start position:0% Lucin uh uh we seven trillion words in 00:12:13.360 --> 00:12:17.310 align:start position:0% Lucin uh uh we seven trillion words in um<00:12:13.920> I<00:12:14.000> mean<00:12:14.279> I<00:12:14.360> think<00:12:14.560> you<00:12:14.959> can<00:12:15.959> well<00:12:16.480> I<00:12:16.560> mean 00:12:17.310 --> 00:12:17.320 align:start position:0% um I mean I think you can well I mean 00:12:17.320 --> 00:12:18.590 align:start position:0% um I mean I think you can well I mean it's<00:12:17.519> obviously<00:12:17.800> going<00:12:17.920> to<00:12:18.040> take<00:12:18.199> a<00:12:18.320> lot<00:12:18.440> of 00:12:18.590 --> 00:12:18.600 align:start position:0% it's obviously going to take a lot of 00:12:18.600 --> 00:12:20.910 align:start position:0% it's obviously going to take a lot of Hardware<00:12:19.120> there's<00:12:19.240> a<00:12:19.399> lot<00:12:19.639> more<00:12:19.920> involved<00:12:20.639> in 00:12:20.910 --> 00:12:20.920 align:start position:0% Hardware there's a lot more involved in 00:12:20.920 --> 00:12:24.910 align:start position:0% Hardware there's a lot more involved in than<00:12:21.160> just<00:12:21.360> the<00:12:21.600> pure<00:12:22.560> like<00:12:23.560> the<00:12:23.760> pure<00:12:24.600> uh 00:12:24.910 --> 00:12:24.920 align:start position:0% than just the pure like the pure uh 00:12:24.920 --> 00:12:26.670 align:start position:0% than just the pure like the pure uh programming<00:12:25.519> side<00:12:25.720> of<00:12:25.880> that<00:12:26.160> problem<00:12:26.440> in 00:12:26.670 --> 00:12:26.680 align:start position:0% programming side of that problem in 00:12:26.680 --> 00:12:29.629 align:start position:0% programming side of that problem in solar<00:12:27.360> right<00:12:28.360> um<00:12:28.680> you<00:12:28.800> know<00:12:29.000> there<00:12:29.279> certainly 00:12:29.629 --> 00:12:29.639 align:start position:0% solar right um you know there certainly 00:12:29.639 --> 00:12:31.590 align:start position:0% solar right um you know there certainly people<00:12:30.040> who<00:12:30.440> you<00:12:30.560> know<00:12:30.720> you<00:12:30.839> would<00:12:31.079> have<00:12:31.320> very 00:12:31.590 --> 00:12:31.600 align:start position:0% people who you know you would have very 00:12:31.600 --> 00:12:34.750 align:start position:0% people who you know you would have very very<00:12:31.880> large<00:12:32.240> indexes<00:12:33.000> and<00:12:33.360> and<00:12:34.000> and<00:12:34.519> you<00:12:34.600> know 00:12:34.750 --> 00:12:34.760 align:start position:0% very large indexes and and and you know 00:12:34.760 --> 00:12:35.790 align:start position:0% very large indexes and and and you know we've<00:12:34.920> worked<00:12:35.199> really<00:12:35.399> hard<00:12:35.560> in<00:12:35.680> the 00:12:35.790 --> 00:12:35.800 align:start position:0% we've worked really hard in the 00:12:35.800 --> 00:12:38.550 align:start position:0% we've worked really hard in the community<00:12:36.160> to<00:12:36.320> make<00:12:36.480> sure<00:12:36.720> we<00:12:36.880> can<00:12:37.600> scale<00:12:38.120> to 00:12:38.550 --> 00:12:38.560 align:start position:0% community to make sure we can scale to 00:12:38.560 --> 00:12:40.790 align:start position:0% community to make sure we can scale to very<00:12:38.800> large<00:12:39.079> sizes<00:12:39.519> can<00:12:39.639> we<00:12:39.839> do<00:12:40.120> 7even 00:12:40.790 --> 00:12:40.800 align:start position:0% very large sizes can we do 7even 00:12:40.800 --> 00:12:44.230 align:start position:0% very large sizes can we do 7even trillion<00:12:41.800> uh<00:12:41.959> n<00:12:42.560> seven<00:12:42.959> grams<00:12:43.639> uh<00:12:43.760> or<00:12:44.079> a 00:12:44.230 --> 00:12:44.240 align:start position:0% trillion uh n seven grams uh or a 00:12:44.240 --> 00:12:49.870 align:start position:0% trillion uh n seven grams uh or a trillion<00:12:44.760> s<00:12:45.680> war<00:12:46.680> and<00:12:47.639> um<00:12:48.160> you<00:12:48.600> know<00:12:49.600> give<00:12:49.720> me 00:12:49.870 --> 00:12:49.880 align:start position:0% trillion s war and um you know give me 00:12:49.880 --> 00:12:51.430 align:start position:0% trillion s war and um you know give me enough<00:12:50.120> Hardware<00:12:50.519> I'll<00:12:50.720> get<00:12:50.880> you<00:12:51.079> there<00:12:51.360> I 00:12:51.430 --> 00:12:51.440 align:start position:0% enough Hardware I'll get you there I 00:12:51.440 --> 00:12:53.430 align:start position:0% enough Hardware I'll get you there I don't<00:12:51.639> know<00:12:51.920> right<00:12:52.199> off<00:12:52.600> off<00:12:52.880> hand<00:12:53.160> I<00:12:53.240> would 00:12:53.430 --> 00:12:53.440 align:start position:0% don't know right off off hand I would 00:12:53.440 --> 00:12:55.310 align:start position:0% don't know right off off hand I would think<00:12:53.600> we<00:12:53.760> could<00:12:53.959> get<00:12:54.120> in<00:12:54.320> that<00:12:54.560> range<00:12:55.040> though 00:12:55.310 --> 00:12:55.320 align:start position:0% think we could get in that range though 00:12:55.320 --> 00:12:56.509 align:start position:0% think we could get in that range though that<00:12:55.440> it<00:12:55.560> would<00:12:55.760> be 00:12:56.509 --> 00:12:56.519 align:start position:0% that it would be 00:12:56.519 --> 00:12:58.670 align:start position:0% that it would be interesting<00:12:57.519> um<00:12:57.880> you<00:12:58.000> know<00:12:58.199> and<00:12:58.360> certainly 00:12:58.670 --> 00:12:58.680 align:start position:0% interesting um you know and certainly 00:12:58.680 --> 00:13:00.389 align:start position:0% interesting um you know and certainly when<00:12:58.760> you<00:12:58.880> bring<00:12:59.279> in<00:12:59.399> tools<00:12:59.680> like<00:12:59.800> Hadoop<00:13:00.240> and 00:13:00.389 --> 00:13:00.399 align:start position:0% when you bring in tools like Hadoop and 00:13:00.399 --> 00:13:02.509 align:start position:0% when you bring in tools like Hadoop and Spark<00:13:00.880> and<00:13:01.160> and<00:13:01.360> that<00:13:01.519> kind<00:13:01.680> of<00:13:01.920> stuff<00:13:02.440> you 00:13:02.509 --> 00:13:02.519 align:start position:0% Spark and and that kind of stuff you 00:13:02.519 --> 00:13:04.910 align:start position:0% Spark and and that kind of stuff you know<00:13:02.760> very<00:13:03.199> complimentary<00:13:04.199> you<00:13:04.279> know<00:13:04.519> go<00:13:04.680> off 00:13:04.910 --> 00:13:04.920 align:start position:0% know very complimentary you know go off 00:13:04.920 --> 00:13:07.590 align:start position:0% know very complimentary you know go off and<00:13:05.560> do<00:13:05.800> the<00:13:05.959> really<00:13:06.240> large<00:13:06.560> scale<00:13:06.959> stuff<00:13:07.399> in 00:13:07.590 --> 00:13:07.600 align:start position:0% and do the really large scale stuff in 00:13:07.600 --> 00:13:10.069 align:start position:0% and do the really large scale stuff in in<00:13:07.760> an<00:13:08.000> approach<00:13:08.519> like<00:13:08.880> that<00:13:09.519> and<00:13:09.720> then<00:13:09.959> you 00:13:10.069 --> 00:13:10.079 align:start position:0% in an approach like that and then you 00:13:10.079 --> 00:13:11.590 align:start position:0% in an approach like that and then you know<00:13:10.240> you're<00:13:10.440> reducing<00:13:10.839> it<00:13:11.040> down<00:13:11.279> into 00:13:11.590 --> 00:13:11.600 align:start position:0% know you're reducing it down into 00:13:11.600 --> 00:13:13.230 align:start position:0% know you're reducing it down into something<00:13:12.040> that<00:13:12.160> is<00:13:12.320> more<00:13:12.560> manageable<00:13:13.120> and 00:13:13.230 --> 00:13:13.240 align:start position:0% something that is more manageable and 00:13:13.240 --> 00:13:15.590 align:start position:0% something that is more manageable and then<00:13:13.399> use<00:13:13.720> search<00:13:14.120> to<00:13:14.399> kind<00:13:14.519> of<00:13:14.800> access<00:13:15.279> that 00:13:15.590 --> 00:13:15.600 align:start position:0% then use search to kind of access that 00:13:15.600 --> 00:13:18.829 align:start position:0% then use search to kind of access that and<00:13:15.920> and<00:13:16.760> you<00:13:16.920> know<00:13:17.519> query<00:13:17.920> around<00:13:18.199> it<00:13:18.399> and<00:13:18.720> and 00:13:18.829 --> 00:13:18.839 align:start position:0% and and you know query around it and and 00:13:18.839 --> 00:13:21.030 align:start position:0% and and you know query around it and and slice<00:13:19.199> and<00:13:19.360> dice<00:13:19.639> it<00:13:19.760> in<00:13:19.920> different<00:13:20.240> ways<00:13:20.760> in<00:13:20.920> a 00:13:21.030 --> 00:13:21.040 align:start position:0% slice and dice it in different ways in a 00:13:21.040 --> 00:13:24.110 align:start position:0% slice and dice it in different ways in a more<00:13:21.240> realtime<00:13:22.079> approach<00:13:23.040> right<00:13:23.560> but<00:13:23.720> yeah<00:13:23.880> no 00:13:24.110 --> 00:13:24.120 align:start position:0% more realtime approach right but yeah no 00:13:24.120 --> 00:13:25.310 align:start position:0% more realtime approach right but yeah no I<00:13:24.199> mean<00:13:24.399> I<00:13:24.480> don't<00:13:24.600> know<00:13:24.720> do<00:13:24.839> you<00:13:24.920> have<00:13:25.040> a<00:13:25.160> big 00:13:25.310 --> 00:13:25.320 align:start position:0% I mean I don't know do you have a big 00:13:25.320 --> 00:13:27.910 align:start position:0% I mean I don't know do you have a big enough<00:13:25.560> budget<00:13:25.839> for<00:13:26.000> us<00:13:26.120> to<00:13:26.320> do<00:13:27.279> I<00:13:27.639> I'm<00:13:27.760> just 00:13:27.910 --> 00:13:27.920 align:start position:0% enough budget for us to do I I'm just 00:13:27.920 --> 00:13:29.829 align:start position:0% enough budget for us to do I I'm just interested<00:13:28.480> in<00:13:28.920> kind<00:13:29.000> of<00:13:29.240> scale<00:13:29.519> because<00:13:29.720> you 00:13:29.829 --> 00:13:29.839 align:start position:0% interested in kind of scale because you 00:13:29.839 --> 00:13:33.269 align:start position:0% interested in kind of scale because you know<00:13:30.760> here<00:13:30.920> in<00:13:31.040> the<00:13:31.399> Salesforce<00:13:32.399> size<00:13:32.880> I<00:13:33.199> I 00:13:33.269 --> 00:13:33.279 align:start position:0% know here in the Salesforce size I I 00:13:33.279 --> 00:13:34.990 align:start position:0% know here in the Salesforce size I I think<00:13:33.440> that's<00:13:33.800> very<00:13:34.240> I<00:13:34.320> think<00:13:34.480> it's<00:13:34.639> getting 00:13:34.990 --> 00:13:35.000 align:start position:0% think that's very I think it's getting 00:13:35.000 --> 00:13:37.949 align:start position:0% think that's very I think it's getting really<00:13:35.560> there<00:13:36.399> uh<00:13:36.680> where<00:13:37.000> you<00:13:37.120> know<00:13:37.639> uh<00:13:37.760> big 00:13:37.949 --> 00:13:37.959 align:start position:0% really there uh where you know uh big 00:13:37.959 --> 00:13:40.790 align:start position:0% really there uh where you know uh big guys<00:13:38.120> are<00:13:38.240> playing<00:13:38.880> uh<00:13:39.279> so<00:13:39.959> uh<00:13:40.199> so<00:13:40.480> I'm<00:13:40.639> I'm 00:13:40.790 --> 00:13:40.800 align:start position:0% guys are playing uh so uh so I'm I'm 00:13:40.800 --> 00:13:44.269 align:start position:0% guys are playing uh so uh so I'm I'm curious<00:13:41.760> um<00:13:42.760> about<00:13:43.120> your<00:13:43.560> so<00:13:43.880> I<00:13:43.959> know<00:13:44.120> that 00:13:44.269 --> 00:13:44.279 align:start position:0% curious um about your so I know that 00:13:44.279 --> 00:13:46.829 align:start position:0% curious um about your so I know that your<00:13:44.639> technology<00:13:45.399> side<00:13:45.720> is<00:13:45.920> very<00:13:46.160> rigorous 00:13:46.829 --> 00:13:46.839 align:start position:0% your technology side is very rigorous 00:13:46.839 --> 00:13:49.030 align:start position:0% your technology side is very rigorous and<00:13:47.480> I<00:13:47.560> was<00:13:47.720> really<00:13:47.920> impressed<00:13:48.480> by<00:13:48.760> the<00:13:48.880> fact 00:13:49.030 --> 00:13:49.040 align:start position:0% and I was really impressed by the fact 00:13:49.040 --> 00:13:50.069 align:start position:0% and I was really impressed by the fact that<00:13:49.199> you<00:13:49.279> guys<00:13:49.440> are<00:13:49.560> running<00:13:49.800> your<00:13:49.920> own 00:13:50.069 --> 00:13:50.079 align:start position:0% that you guys are running your own 00:13:50.079 --> 00:13:52.629 align:start position:0% that you guys are running your own Jepson<00:13:50.519> tests<00:13:51.040> right<00:13:51.160> so<00:13:51.639> japson<00:13:52.079> is<00:13:52.320> this 00:13:52.629 --> 00:13:52.639 align:start position:0% Jepson tests right so japson is this 00:13:52.639 --> 00:13:56.189 align:start position:0% Jepson tests right so japson is this distributed<00:13:53.639> uh<00:13:53.759> system<00:13:54.600> uh<00:13:54.759> testing<00:13:55.680> uh<00:13:55.759> Su 00:13:56.189 --> 00:13:56.199 align:start position:0% distributed uh system uh testing uh Su 00:13:56.199 --> 00:13:57.629 align:start position:0% distributed uh system uh testing uh Su which<00:13:56.320> is<00:13:56.480> basically<00:13:56.920> integration<00:13:57.399> test 00:13:57.629 --> 00:13:57.639 align:start position:0% which is basically integration test 00:13:57.639 --> 00:13:59.629 align:start position:0% which is basically integration test which<00:13:58.079> it<00:13:58.279> tests<00:13:58.680> you<00:13:58.800> know<00:13:59.240> all<00:13:59.399> kinds<00:13:59.560> of 00:13:59.629 --> 00:13:59.639 align:start position:0% which it tests you know all kinds of 00:13:59.639 --> 00:14:03.189 align:start position:0% which it tests you know all kinds of failure<00:14:00.000> scenarios<00:14:00.560> so<00:14:01.279> and<00:14:01.720> and<00:14:02.320> uh<00:14:02.959> uh<00:14:03.079> it 00:14:03.189 --> 00:14:03.199 align:start position:0% failure scenarios so and and uh uh it 00:14:03.199 --> 00:14:07.030 align:start position:0% failure scenarios so and and uh uh it was<00:14:03.399> done<00:14:04.399> uh<00:14:05.160> as<00:14:05.399> as<00:14:05.600> as<00:14:05.680> a<00:14:05.839> series<00:14:06.120> of<00:14:06.360> of<00:14:06.560> of 00:14:07.030 --> 00:14:07.040 align:start position:0% was done uh as as as a series of of of 00:14:07.040 --> 00:14:10.069 align:start position:0% was done uh as as as a series of of of studies<00:14:08.040> uh<00:14:08.320> but<00:14:09.040> uh<00:14:09.360> uh<00:14:09.519> Lucid<00:14:09.839> Works 00:14:10.069 --> 00:14:10.079 align:start position:0% studies uh but uh uh Lucid Works 00:14:10.079 --> 00:14:12.949 align:start position:0% studies uh but uh uh Lucid Works maintains<00:14:10.480> its<00:14:10.639> own<00:14:11.160> jabson<00:14:12.160> uh<00:14:12.320> test<00:14:12.560> Suite 00:14:12.949 --> 00:14:12.959 align:start position:0% maintains its own jabson uh test Suite 00:14:12.959 --> 00:14:16.069 align:start position:0% maintains its own jabson uh test Suite so<00:14:13.240> I<00:14:13.639> I<00:14:13.759> wonder<00:14:14.600> and<00:14:14.720> and<00:14:14.959> apparently<00:14:15.959> it 00:14:16.069 --> 00:14:16.079 align:start position:0% so I I wonder and and apparently it 00:14:16.079 --> 00:14:18.710 align:start position:0% so I I wonder and and apparently it shows<00:14:16.680> that<00:14:17.000> you<00:14:17.160> guys<00:14:17.320> are<00:14:17.519> really<00:14:18.320> uh<00:14:18.440> paying 00:14:18.710 --> 00:14:18.720 align:start position:0% shows that you guys are really uh paying 00:14:18.720 --> 00:14:20.870 align:start position:0% shows that you guys are really uh paying attention<00:14:19.160> to<00:14:19.639> to<00:14:20.160> all<00:14:20.360> kinds<00:14:20.519> of<00:14:20.600> fa 00:14:20.870 --> 00:14:20.880 align:start position:0% attention to to all kinds of fa 00:14:20.880 --> 00:14:24.430 align:start position:0% attention to to all kinds of fa scenaries<00:14:21.320> I<00:14:21.440> wonder<00:14:22.040> how<00:14:22.279> do<00:14:22.839> you<00:14:23.839> uh<00:14:24.160> how<00:14:24.320> do 00:14:24.430 --> 00:14:24.440 align:start position:0% scenaries I wonder how do you uh how do 00:14:24.440 --> 00:14:26.430 align:start position:0% scenaries I wonder how do you uh how do you<00:14:24.720> make<00:14:24.920> sure<00:14:25.399> that<00:14:25.600> the<00:14:25.720> customers<00:14:26.079> are<00:14:26.240> not 00:14:26.430 --> 00:14:26.440 align:start position:0% you make sure that the customers are not 00:14:26.440 --> 00:14:29.629 align:start position:0% you make sure that the customers are not losing<00:14:27.440> data<00:14:28.320> and<00:14:28.560> and<00:14:28.720> you<00:14:28.839> know<00:14:29.120> how<00:14:29.279> do<00:14:29.399> you 00:14:29.629 --> 00:14:29.639 align:start position:0% losing data and and you know how do you 00:14:29.639 --> 00:14:31.310 align:start position:0% losing data and and you know how do you like<00:14:29.839> what<00:14:29.959> kind<00:14:30.079> of<00:14:30.199> tools<00:14:30.480> do<00:14:30.600> you<00:14:30.800> have<00:14:31.120> and 00:14:31.310 --> 00:14:31.320 align:start position:0% like what kind of tools do you have and 00:14:31.320 --> 00:14:32.790 align:start position:0% like what kind of tools do you have and and<00:14:31.600> what<00:14:31.720> kind<00:14:31.839> of<00:14:31.959> scenarios<00:14:32.360> do<00:14:32.440> you<00:14:32.560> see 00:14:32.790 --> 00:14:32.800 align:start position:0% and what kind of scenarios do you see 00:14:32.800 --> 00:14:34.910 align:start position:0% and what kind of scenarios do you see around<00:14:33.160> this<00:14:33.600> right<00:14:33.959> well<00:14:34.160> this<00:14:34.279> is<00:14:34.560> you<00:14:34.639> know 00:14:34.910 --> 00:14:34.920 align:start position:0% around this right well this is you know 00:14:34.920 --> 00:14:36.629 align:start position:0% around this right well this is you know I<00:14:35.000> mean<00:14:35.160> obviously<00:14:35.440> the<00:14:35.600> jeffson<00:14:35.959> work<00:14:36.440> happy 00:14:36.629 --> 00:14:36.639 align:start position:0% I mean obviously the jeffson work happy 00:14:36.639 --> 00:14:38.310 align:start position:0% I mean obviously the jeffson work happy to<00:14:36.720> get<00:14:36.839> into<00:14:37.440> I<00:14:37.480> mean<00:14:37.639> I<00:14:37.759> think<00:14:37.959> this<00:14:38.079> is<00:14:38.199> one 00:14:38.310 --> 00:14:38.320 align:start position:0% to get into I mean I think this is one 00:14:38.320 --> 00:14:40.189 align:start position:0% to get into I mean I think this is one of<00:14:38.440> the<00:14:38.560> beauties<00:14:39.079> of<00:14:39.279> the<00:14:39.399> open<00:14:39.720> source<00:14:40.000> is 00:14:40.189 --> 00:14:40.199 align:start position:0% of the beauties of the open source is 00:14:40.199 --> 00:14:42.629 align:start position:0% of the beauties of the open source is not<00:14:40.360> just<00:14:40.600> commod<00:14:41.440> commoditization<00:14:42.360> of 00:14:42.629 --> 00:14:42.639 align:start position:0% not just commod commoditization of 00:14:42.639 --> 00:14:45.069 align:start position:0% not just commod commoditization of functionality<00:14:43.440> but<00:14:43.920> commoditization<00:14:44.720> of 00:14:45.069 --> 00:14:45.079 align:start position:0% functionality but commoditization of 00:14:45.079 --> 00:14:47.030 align:start position:0% functionality but commoditization of test<00:14:45.399> across<00:14:45.720> a<00:14:46.000> large<00:14:46.360> number<00:14:46.600> of<00:14:46.759> people 00:14:47.030 --> 00:14:47.040 align:start position:0% test across a large number of people 00:14:47.040 --> 00:14:48.389 align:start position:0% test across a large number of people when<00:14:47.160> you're<00:14:47.320> the<00:14:47.480> most<00:14:47.720> widely<00:14:48.000> deployed 00:14:48.389 --> 00:14:48.399 align:start position:0% when you're the most widely deployed 00:14:48.399 --> 00:14:51.189 align:start position:0% when you're the most widely deployed search<00:14:48.920> technology<00:14:49.920> on<00:14:50.079> the<00:14:50.240> planet<00:14:50.839> right 00:14:51.189 --> 00:14:51.199 align:start position:0% search technology on the planet right 00:14:51.199 --> 00:14:52.710 align:start position:0% search technology on the planet right you<00:14:51.320> get<00:14:51.519> a<00:14:51.639> lot<00:14:51.800> of<00:14:51.959> people<00:14:52.240> kicking<00:14:52.560> the 00:14:52.710 --> 00:14:52.720 align:start position:0% you get a lot of people kicking the 00:14:52.720 --> 00:14:55.550 align:start position:0% you get a lot of people kicking the tires<00:14:53.120> and<00:14:53.320> coming<00:14:53.600> up<00:14:53.880> with<00:14:54.160> error<00:14:54.560> scenarios 00:14:55.550 --> 00:14:55.560 align:start position:0% tires and coming up with error scenarios 00:14:55.560 --> 00:14:57.150 align:start position:0% tires and coming up with error scenarios and<00:14:55.720> all<00:14:55.839> of<00:14:56.040> those<00:14:56.240> kinds<00:14:56.399> of<00:14:56.600> things<00:14:56.880> such 00:14:57.150 --> 00:14:57.160 align:start position:0% and all of those kinds of things such 00:14:57.160 --> 00:14:59.670 align:start position:0% and all of those kinds of things such that<00:14:57.360> it<00:14:57.920> gets<00:14:58.160> to<00:14:58.360> be<00:14:58.720> you<00:14:58.839> know<00:14:59.199> you<00:14:59.320> get<00:14:59.480> a 00:14:59.670 --> 00:14:59.680 align:start position:0% that it gets to be you know you get a 00:14:59.680 --> 00:15:01.870 align:start position:0% that it gets to be you know you get a lot<00:14:59.839> of<00:15:00.079> great<00:15:00.360> feedback<00:15:00.880> from<00:15:01.120> the<00:15:01.279> community 00:15:01.870 --> 00:15:01.880 align:start position:0% lot of great feedback from the community 00:15:01.880 --> 00:15:04.550 align:start position:0% lot of great feedback from the community at<00:15:02.279> at<00:15:02.440> the<00:15:02.759> Quality<00:15:03.160> Assurance<00:15:03.680> level<00:15:04.079> so<00:15:04.480> you 00:15:04.550 --> 00:15:04.560 align:start position:0% at at the Quality Assurance level so you 00:15:04.560 --> 00:15:06.550 align:start position:0% at at the Quality Assurance level so you know<00:15:04.680> you've<00:15:04.880> got<00:15:05.120> that<00:15:05.320> layer<00:15:06.000> then<00:15:06.160> we<00:15:06.320> as<00:15:06.440> a 00:15:06.550 --> 00:15:06.560 align:start position:0% know you've got that layer then we as a 00:15:06.560 --> 00:15:08.470 align:start position:0% know you've got that layer then we as a company<00:15:06.920> you<00:15:07.040> know<00:15:07.199> we<00:15:07.360> look<00:15:07.600> at<00:15:08.040> where<00:15:08.199> are 00:15:08.470 --> 00:15:08.480 align:start position:0% company you know we look at where are 00:15:08.480 --> 00:15:12.310 align:start position:0% company you know we look at where are areas<00:15:08.920> that<00:15:09.160> we<00:15:09.399> can<00:15:09.800> fund<00:15:10.680> efforts<00:15:11.320> around 00:15:12.310 --> 00:15:12.320 align:start position:0% areas that we can fund efforts around 00:15:12.320 --> 00:15:14.269 align:start position:0% areas that we can fund efforts around making<00:15:12.720> sure<00:15:13.240> that<00:15:13.519> you<00:15:13.680> know<00:15:14.000> we<00:15:14.120> can 00:15:14.269 --> 00:15:14.279 align:start position:0% making sure that you know we can 00:15:14.279 --> 00:15:15.670 align:start position:0% making sure that you know we can leverage<00:15:14.680> the<00:15:14.800> community<00:15:15.240> stuff<00:15:15.480> and<00:15:15.560> then 00:15:15.670 --> 00:15:15.680 align:start position:0% leverage the community stuff and then 00:15:15.680 --> 00:15:17.790 align:start position:0% leverage the community stuff and then feedback<00:15:16.240> our<00:15:16.360> own<00:15:16.600> capabilities<00:15:17.160> the<00:15:17.279> Jepson 00:15:17.790 --> 00:15:17.800 align:start position:0% feedback our own capabilities the Jepson 00:15:17.800 --> 00:15:19.790 align:start position:0% feedback our own capabilities the Jepson thing<00:15:18.600> uh<00:15:18.720> was<00:15:18.959> definitely<00:15:19.279> an<00:15:19.440> area<00:15:19.680> of 00:15:19.790 --> 00:15:19.800 align:start position:0% thing uh was definitely an area of 00:15:19.800 --> 00:15:21.590 align:start position:0% thing uh was definitely an area of Interest<00:15:20.120> we<00:15:20.240> wanted<00:15:20.519> to<00:15:20.839> we<00:15:20.959> already<00:15:21.199> knew 00:15:21.590 --> 00:15:21.600 align:start position:0% Interest we wanted to we already knew 00:15:21.600 --> 00:15:23.269 align:start position:0% Interest we wanted to we already knew like<00:15:21.759> solar<00:15:22.120> and<00:15:22.240> solar<00:15:22.519> Cloud<00:15:22.800> was<00:15:23.000> very 00:15:23.269 --> 00:15:23.279 align:start position:0% like solar and solar Cloud was very 00:15:23.279 --> 00:15:25.389 align:start position:0% like solar and solar Cloud was very robust<00:15:23.720> and<00:15:23.920> very<00:15:24.160> mature<00:15:24.880> and<00:15:25.000> you<00:15:25.120> know<00:15:25.240> to 00:15:25.389 --> 00:15:25.399 align:start position:0% robust and very mature and you know to 00:15:25.399 --> 00:15:26.990 align:start position:0% robust and very mature and you know to some<00:15:25.600> extent<00:15:25.880> we<00:15:25.959> needed<00:15:26.199> to<00:15:26.440> just<00:15:26.600> simply 00:15:26.990 --> 00:15:27.000 align:start position:0% some extent we needed to just simply 00:15:27.000 --> 00:15:29.230 align:start position:0% some extent we needed to just simply prove<00:15:27.240> it<00:15:27.800> by<00:15:28.000> going<00:15:28.240> through<00:15:28.519> you<00:15:28.600> know<00:15:29.120> what 00:15:29.230 --> 00:15:29.240 align:start position:0% prove it by going through you know what 00:15:29.240 --> 00:15:32.030 align:start position:0% prove it by going through you know what Jepson<00:15:29.680> does<00:15:29.920> is<00:15:30.319> simulate<00:15:31.319> uh<00:15:31.519> Network 00:15:32.030 --> 00:15:32.040 align:start position:0% Jepson does is simulate uh Network 00:15:32.040 --> 00:15:35.230 align:start position:0% Jepson does is simulate uh Network partitions<00:15:32.959> disc<00:15:33.399> failure<00:15:34.279> Hardware<00:15:34.720> failure 00:15:35.230 --> 00:15:35.240 align:start position:0% partitions disc failure Hardware failure 00:15:35.240 --> 00:15:36.949 align:start position:0% partitions disc failure Hardware failure all<00:15:35.360> of<00:15:35.519> these<00:15:35.720> kinds<00:15:35.920> of<00:15:36.079> things<00:15:36.279> in<00:15:36.440> a<00:15:36.600> nice 00:15:36.949 --> 00:15:36.959 align:start position:0% all of these kinds of things in a nice 00:15:36.959 --> 00:15:38.749 align:start position:0% all of these kinds of things in a nice self-contained<00:15:37.639> way<00:15:37.880> such<00:15:38.079> that<00:15:38.279> you<00:15:38.480> can 00:15:38.749 --> 00:15:38.759 align:start position:0% self-contained way such that you can 00:15:38.759 --> 00:15:41.749 align:start position:0% self-contained way such that you can test<00:15:39.680> whether<00:15:40.440> you<00:15:40.680> have<00:15:40.920> data<00:15:41.240> loss<00:15:41.560> because 00:15:41.749 --> 00:15:41.759 align:start position:0% test whether you have data loss because 00:15:41.759 --> 00:15:43.350 align:start position:0% test whether you have data loss because one<00:15:41.880> of<00:15:41.959> the<00:15:42.079> big<00:15:42.240> things<00:15:42.560> you<00:15:42.680> know<00:15:42.920> we<00:15:43.079> have 00:15:43.350 --> 00:15:43.360 align:start position:0% one of the big things you know we have 00:15:43.360 --> 00:15:45.150 align:start position:0% one of the big things you know we have companies<00:15:43.759> who<00:15:43.920> run<00:15:44.199> their<00:15:44.399> whole<00:15:44.639> business 00:15:45.150 --> 00:15:45.160 align:start position:0% companies who run their whole business 00:15:45.160 --> 00:15:47.749 align:start position:0% companies who run their whole business off<00:15:45.279> of<00:15:45.440> solar<00:15:45.959> right<00:15:46.079> so<00:15:46.279> data<00:15:46.560> loss<00:15:46.839> is<00:15:47.360> a 00:15:47.749 --> 00:15:47.759 align:start position:0% off of solar right so data loss is a 00:15:47.759 --> 00:15:49.949 align:start position:0% off of solar right so data loss is a huge<00:15:48.319> problem<00:15:48.600> for<00:15:48.839> them<00:15:49.040> if<00:15:49.160> it<00:15:49.399> happens 00:15:49.949 --> 00:15:49.959 align:start position:0% huge problem for them if it happens 00:15:49.959 --> 00:15:52.470 align:start position:0% huge problem for them if it happens right<00:15:50.680> and<00:15:50.800> so<00:15:51.440> in<00:15:51.600> fact<00:15:51.800> in<00:15:52.000> where<00:15:52.279> they're 00:15:52.470 --> 00:15:52.480 align:start position:0% right and so in fact in where they're 00:15:52.480 --> 00:15:54.590 align:start position:0% right and so in fact in where they're actually<00:15:52.720> using<00:15:53.240> solar<00:15:54.160> as<00:15:54.399> the 00:15:54.590 --> 00:15:54.600 align:start position:0% actually using solar as the 00:15:54.600 --> 00:15:56.990 align:start position:0% actually using solar as the authoritative<00:15:55.319> store<00:15:55.759> for<00:15:56.040> their<00:15:56.279> data<00:15:56.720> right 00:15:56.990 --> 00:15:57.000 align:start position:0% authoritative store for their data right 00:15:57.000 --> 00:15:59.110 align:start position:0% authoritative store for their data right so<00:15:57.480> we've<00:15:57.720> got<00:15:57.800> to<00:15:58.000> make<00:15:58.160> sure<00:15:58.360> that<00:15:58.480> it's<00:15:58.680> rock 00:15:59.110 --> 00:15:59.120 align:start position:0% so we've got to make sure that it's rock 00:15:59.120 --> 00:16:01.670 align:start position:0% so we've got to make sure that it's rock solid<00:15:59.560> under<00:15:59.839> all<00:16:00.279> conditions<00:16:00.639> now<00:16:00.880> obviously 00:16:01.670 --> 00:16:01.680 align:start position:0% solid under all conditions now obviously 00:16:01.680 --> 00:16:03.870 align:start position:0% solid under all conditions now obviously you<00:16:01.800> know<00:16:01.959> no<00:16:02.199> software<00:16:02.639> is<00:16:02.880> perfect<00:16:03.279> but<00:16:03.399> so 00:16:03.870 --> 00:16:03.880 align:start position:0% you know no software is perfect but so 00:16:03.880 --> 00:16:06.030 align:start position:0% you know no software is perfect but so we<00:16:04.000> want<00:16:04.160> to<00:16:04.360> make<00:16:04.519> sure<00:16:04.800> that<00:16:04.959> we<00:16:05.240> take<00:16:05.720> a<00:16:05.880> lot 00:16:06.030 --> 00:16:06.040 align:start position:0% we want to make sure that we take a lot 00:16:06.040 --> 00:16:07.829 align:start position:0% we want to make sure that we take a lot of<00:16:06.319> you<00:16:06.440> know<00:16:06.560> put<00:16:06.680> in<00:16:06.839> a<00:16:07.040> lot<00:16:07.199> of<00:16:07.360> effort<00:16:07.680> to 00:16:07.829 --> 00:16:07.839 align:start position:0% of you know put in a lot of effort to 00:16:07.839 --> 00:16:09.550 align:start position:0% of you know put in a lot of effort to make<00:16:08.000> sure<00:16:08.240> that<00:16:08.360> we're<00:16:08.600> doing<00:16:08.920> those<00:16:09.120> things 00:16:09.550 --> 00:16:09.560 align:start position:0% make sure that we're doing those things 00:16:09.560 --> 00:16:11.870 align:start position:0% make sure that we're doing those things the<00:16:09.680> jebson<00:16:10.240> example<00:16:10.759> is<00:16:10.880> a<00:16:11.079> is<00:16:11.199> a<00:16:11.399> great<00:16:11.639> one 00:16:11.870 --> 00:16:11.880 align:start position:0% the jebson example is a is a great one 00:16:11.880 --> 00:16:15.670 align:start position:0% the jebson example is a is a great one of<00:16:12.560> uh<00:16:12.720> actually<00:16:12.959> one<00:16:13.079> of<00:16:13.199> our<00:16:13.720> Engineers<00:16:14.720> uh 00:16:15.670 --> 00:16:15.680 align:start position:0% of uh actually one of our Engineers uh 00:16:15.680 --> 00:16:17.069 align:start position:0% of uh actually one of our Engineers uh you<00:16:15.759> know<00:16:16.160> one<00:16:16.240> of<00:16:16.360> the<00:16:16.480> things<00:16:16.680> that<00:16:16.839> people 00:16:17.069 --> 00:16:17.079 align:start position:0% you know one of the things that people 00:16:17.079 --> 00:16:19.069 align:start position:0% you know one of the things that people often<00:16:17.360> talk<00:16:17.600> about<00:16:18.160> with<00:16:18.399> with<00:16:18.519> solar<00:16:18.839> cloud 00:16:19.069 --> 00:16:19.079 align:start position:0% often talk about with with solar cloud 00:16:19.079 --> 00:16:20.870 align:start position:0% often talk about with with solar cloud is<00:16:19.199> oh<00:16:19.519> I've<00:16:19.680> got<00:16:19.839> this<00:16:20.079> extra<00:16:20.440> thing<00:16:20.680> that's 00:16:20.870 --> 00:16:20.880 align:start position:0% is oh I've got this extra thing that's 00:16:20.880 --> 00:16:22.710 align:start position:0% is oh I've got this extra thing that's called<00:16:21.079> zookeeper<00:16:21.800> and<00:16:22.160> and<00:16:22.279> that<00:16:22.399> makes<00:16:22.560> me 00:16:22.710 --> 00:16:22.720 align:start position:0% called zookeeper and and that makes me 00:16:22.720 --> 00:16:24.749 align:start position:0% called zookeeper and and that makes me have<00:16:22.839> to<00:16:23.040> do<00:16:23.199> a<00:16:23.319> little<00:16:23.480> bit<00:16:23.720> extra<00:16:24.040> work<00:16:24.639> one 00:16:24.749 --> 00:16:24.759 align:start position:0% have to do a little bit extra work one 00:16:24.759 --> 00:16:26.710 align:start position:0% have to do a little bit extra work one of<00:16:24.839> the<00:16:24.920> things<00:16:25.160> we<00:16:25.279> wanted<00:16:25.560> to<00:16:25.759> do<00:16:25.959> is<00:16:26.199> show 00:16:26.710 --> 00:16:26.720 align:start position:0% of the things we wanted to do is show 00:16:26.720 --> 00:16:28.550 align:start position:0% of the things we wanted to do is show why<00:16:26.959> that<00:16:27.120> was<00:16:27.360> such<00:16:27.519> an<00:16:27.720> advantage<00:16:28.240> because 00:16:28.550 --> 00:16:28.560 align:start position:0% why that was such an advantage because 00:16:28.560 --> 00:16:31.309 align:start position:0% why that was such an advantage because okay<00:16:29.040> got<00:16:29.160> this<00:16:29.319> extra<00:16:29.720> process<00:16:30.680> but<00:16:30.959> the 00:16:31.309 --> 00:16:31.319 align:start position:0% okay got this extra process but the 00:16:31.319 --> 00:16:34.230 align:start position:0% okay got this extra process but the thing<00:16:31.560> that<00:16:31.720> you<00:16:32.000> get<00:16:32.240> out<00:16:32.399> of<00:16:32.680> that<00:16:32.959> now<00:16:33.680> is 00:16:34.230 --> 00:16:34.240 align:start position:0% thing that you get out of that now is 00:16:34.240 --> 00:16:36.069 align:start position:0% thing that you get out of that now is you<00:16:34.360> know<00:16:35.079> okay<00:16:35.240> it's<00:16:35.360> a<00:16:35.480> little<00:16:35.639> bit<00:16:35.800> harder 00:16:36.069 --> 00:16:36.079 align:start position:0% you know okay it's a little bit harder 00:16:36.079 --> 00:16:38.509 align:start position:0% you know okay it's a little bit harder to<00:16:36.519> start<00:16:37.519> but<00:16:37.720> would<00:16:37.880> you<00:16:38.079> rather<00:16:38.319> have 00:16:38.509 --> 00:16:38.519 align:start position:0% to start but would you rather have 00:16:38.519 --> 00:16:41.230 align:start position:0% to start but would you rather have harder<00:16:38.839> to<00:16:39.319> or<00:16:39.440> easier<00:16:39.800> to<00:16:39.959> start<00:16:40.600> or<00:16:40.880> easier 00:16:41.230 --> 00:16:41.240 align:start position:0% harder to or easier to start or easier 00:16:41.240 --> 00:16:43.030 align:start position:0% harder to or easier to start or easier to<00:16:41.399> finish<00:16:41.959> I<00:16:42.040> don't<00:16:42.160> know<00:16:42.319> about<00:16:42.519> you<00:16:42.759> I<00:16:42.839> would 00:16:43.030 --> 00:16:43.040 align:start position:0% to finish I don't know about you I would 00:16:43.040 --> 00:16:45.550 align:start position:0% to finish I don't know about you I would rather<00:16:43.319> have<00:16:43.480> my<00:16:43.720> weekends<00:16:44.720> when<00:16:45.120> the<00:16:45.279> system 00:16:45.550 --> 00:16:45.560 align:start position:0% rather have my weekends when the system 00:16:45.560 --> 00:16:47.550 align:start position:0% rather have my weekends when the system is<00:16:45.720> up<00:16:45.839> and<00:16:46.000> in<00:16:46.199> production<00:16:46.880> and<00:16:47.079> all<00:16:47.199> of<00:16:47.399> that 00:16:47.550 --> 00:16:47.560 align:start position:0% is up and in production and all of that 00:16:47.560 --> 00:16:49.189 align:start position:0% is up and in production and all of that kind<00:16:47.680> of<00:16:47.880> stuff<00:16:48.319> then<00:16:48.560> you<00:16:48.680> know<00:16:48.839> a<00:16:48.920> little 00:16:49.189 --> 00:16:49.199 align:start position:0% kind of stuff then you know a little 00:16:49.199 --> 00:16:51.230 align:start position:0% kind of stuff then you know a little extra<00:16:49.519> work<00:16:49.720> to<00:16:49.839> set<00:16:50.040> up<00:16:50.199> zookeeper<00:16:50.759> up<00:16:50.959> front 00:16:51.230 --> 00:16:51.240 align:start position:0% extra work to set up zookeeper up front 00:16:51.240 --> 00:16:52.710 align:start position:0% extra work to set up zookeeper up front because<00:16:51.720> well<00:16:51.880> by<00:16:52.000> the<00:16:52.120> way<00:16:52.240> it's<00:16:52.360> not<00:16:52.600> that 00:16:52.710 --> 00:16:52.720 align:start position:0% because well by the way it's not that 00:16:52.720 --> 00:16:55.269 align:start position:0% because well by the way it's not that hard<00:16:53.199> anyway<00:16:53.720> so<00:16:54.160> we<00:16:54.279> as<00:16:54.399> a<00:16:54.519> company<00:16:54.839> wanted<00:16:55.120> to 00:16:55.269 --> 00:16:55.279 align:start position:0% hard anyway so we as a company wanted to 00:16:55.279 --> 00:16:58.350 align:start position:0% hard anyway so we as a company wanted to Showcase<00:16:56.079> why<00:16:56.319> we<00:16:56.519> chose<00:16:57.040> zookeeper<00:16:58.040> as<00:16:58.199> the 00:16:58.350 --> 00:16:58.360 align:start position:0% Showcase why we chose zookeeper as the 00:16:58.360 --> 00:17:00.949 align:start position:0% Showcase why we chose zookeeper as the distributor<00:16:59.120> coordination<00:16:59.800> service<00:17:00.560> for 00:17:00.949 --> 00:17:00.959 align:start position:0% distributor coordination service for 00:17:00.959 --> 00:17:03.710 align:start position:0% distributor coordination service for solar<00:17:01.759> and<00:17:02.079> show<00:17:02.680> and<00:17:02.880> demonstrate<00:17:03.480> very 00:17:03.710 --> 00:17:03.720 align:start position:0% solar and show and demonstrate very 00:17:03.720 --> 00:17:05.270 align:start position:0% solar and show and demonstrate very cleanly<00:17:04.199> especially<00:17:04.559> compared<00:17:04.919> to<00:17:05.039> our 00:17:05.270 --> 00:17:05.280 align:start position:0% cleanly especially compared to our 00:17:05.280 --> 00:17:07.669 align:start position:0% cleanly especially compared to our competition<00:17:05.880> of<00:17:06.559> how<00:17:06.720> you<00:17:06.919> can<00:17:07.120> avoid<00:17:07.480> things 00:17:07.669 --> 00:17:07.679 align:start position:0% competition of how you can avoid things 00:17:07.679 --> 00:17:09.870 align:start position:0% competition of how you can avoid things like<00:17:07.839> split<00:17:08.160> bent<00:17:08.400> brain<00:17:08.720> scenarios<00:17:09.400> Network 00:17:09.870 --> 00:17:09.880 align:start position:0% like split bent brain scenarios Network 00:17:09.880 --> 00:17:12.990 align:start position:0% like split bent brain scenarios Network partitions<00:17:10.600> data<00:17:10.919> loss<00:17:11.720> by<00:17:12.000> making<00:17:12.400> a<00:17:12.640> better 00:17:12.990 --> 00:17:13.000 align:start position:0% partitions data loss by making a better 00:17:13.000 --> 00:17:15.069 align:start position:0% partitions data loss by making a better decision<00:17:13.520> about<00:17:13.799> the<00:17:13.959> robust<00:17:14.480> you<00:17:14.600> know<00:17:14.760> about 00:17:15.069 --> 00:17:15.079 align:start position:0% decision about the robust you know about 00:17:15.079 --> 00:17:17.110 align:start position:0% decision about the robust you know about the<00:17:15.240> way<00:17:15.520> you<00:17:15.799> coordinate<00:17:16.280> your<00:17:16.480> distributed 00:17:17.110 --> 00:17:17.120 align:start position:0% the way you coordinate your distributed 00:17:17.120 --> 00:17:19.110 align:start position:0% the way you coordinate your distributed activities<00:17:17.919> so<00:17:18.079> for<00:17:18.319> people<00:17:18.520> who<00:17:18.640> don't<00:17:18.919> care 00:17:19.110 --> 00:17:19.120 align:start position:0% activities so for people who don't care 00:17:19.120 --> 00:17:21.150 align:start position:0% activities so for people who don't care about<00:17:19.360> data<00:17:19.679> loss<00:17:20.360> then<00:17:20.520> you<00:17:20.640> know<00:17:20.760> you<00:17:20.880> don't 00:17:21.150 --> 00:17:21.160 align:start position:0% about data loss then you know you don't 00:17:21.160 --> 00:17:22.870 align:start position:0% about data loss then you know you don't necessarily<00:17:21.799> care<00:17:22.000> about<00:17:22.240> zookeeper<00:17:22.720> and 00:17:22.870 --> 00:17:22.880 align:start position:0% necessarily care about zookeeper and 00:17:22.880 --> 00:17:24.470 align:start position:0% necessarily care about zookeeper and don't<00:17:23.000> get<00:17:23.079> me<00:17:23.240> wrong<00:17:23.439> there<00:17:23.559> are<00:17:23.760> use<00:17:24.120> cases 00:17:24.470 --> 00:17:24.480 align:start position:0% don't get me wrong there are use cases 00:17:24.480 --> 00:17:26.429 align:start position:0% don't get me wrong there are use cases for<00:17:24.760> that<00:17:24.959> you<00:17:25.079> know<00:17:25.720> if<00:17:25.839> it's<00:17:26.039> not<00:17:26.199> your 00:17:26.429 --> 00:17:26.439 align:start position:0% for that you know if it's not your 00:17:26.439 --> 00:17:29.110 align:start position:0% for that you know if it's not your authoritative<00:17:27.079> store<00:17:27.559> if<00:17:27.679> you're<00:17:27.839> just<00:17:28.000> doing 00:17:29.110 --> 00:17:29.120 align:start position:0% authoritative store if you're just doing 00:17:29.120 --> 00:17:30.870 align:start position:0% authoritative store if you're just doing uh<00:17:29.320> you<00:17:29.440> know<00:17:29.640> some<00:17:29.919> data<00:17:30.200> that<00:17:30.320> you<00:17:30.440> can<00:17:30.600> throw 00:17:30.870 --> 00:17:30.880 align:start position:0% uh you know some data that you can throw 00:17:30.880 --> 00:17:32.430 align:start position:0% uh you know some data that you can throw away<00:17:31.160> if<00:17:31.280> it<00:17:31.400> goes<00:17:31.640> away<00:17:31.880> or<00:17:32.000> you<00:17:32.120> can<00:17:32.280> just 00:17:32.430 --> 00:17:32.440 align:start position:0% away if it goes away or you can just 00:17:32.440 --> 00:17:34.870 align:start position:0% away if it goes away or you can just reindex<00:17:33.200> then<00:17:33.520> you<00:17:33.640> know<00:17:34.039> maybe<00:17:34.280> zookeeper 00:17:34.870 --> 00:17:34.880 align:start position:0% reindex then you know maybe zookeeper 00:17:34.880 --> 00:17:36.270 align:start position:0% reindex then you know maybe zookeeper isn't<00:17:35.120> your<00:17:35.320> thing<00:17:35.720> but<00:17:35.840> if<00:17:35.919> you're<00:17:36.039> going<00:17:36.120> to 00:17:36.270 --> 00:17:36.280 align:start position:0% isn't your thing but if you're going to 00:17:36.280 --> 00:17:38.270 align:start position:0% isn't your thing but if you're going to run<00:17:36.520> your<00:17:36.880> business<00:17:37.200> if<00:17:37.320> you're<00:17:37.520> doing<00:17:38.160> you 00:17:38.270 --> 00:17:38.280 align:start position:0% run your business if you're doing you 00:17:38.280 --> 00:17:40.510 align:start position:0% run your business if you're doing you know<00:17:38.440> $2<00:17:38.760> billion<00:17:39.200> dollar<00:17:39.520> a<00:17:39.720> year<00:17:40.120> in 00:17:40.510 --> 00:17:40.520 align:start position:0% know $2 billion dollar a year in 00:17:40.520 --> 00:17:42.669 align:start position:0% know $2 billion dollar a year in e-commerce<00:17:41.520> and<00:17:41.640> you<00:17:41.760> need<00:17:41.960> to<00:17:42.200> handle 00:17:42.669 --> 00:17:42.679 align:start position:0% e-commerce and you need to handle 00:17:42.679 --> 00:17:44.909 align:start position:0% e-commerce and you need to handle massive<00:17:43.280> scale<00:17:43.720> at<00:17:43.960> Christmas<00:17:44.400> time<00:17:44.600> or<00:17:44.760> the 00:17:44.909 --> 00:17:44.919 align:start position:0% massive scale at Christmas time or the 00:17:44.919 --> 00:17:47.270 align:start position:0% massive scale at Christmas time or the holiday<00:17:45.360> season<00:17:46.039> you<00:17:46.240> can't<00:17:46.559> afford<00:17:46.919> to<00:17:47.120> have 00:17:47.270 --> 00:17:47.280 align:start position:0% holiday season you can't afford to have 00:17:47.280 --> 00:17:49.710 align:start position:0% holiday season you can't afford to have data<00:17:47.600> loss<00:17:47.919> you<00:17:48.080> can't<00:17:48.360> afford<00:17:48.720> to<00:17:49.000> have<00:17:49.559> the 00:17:49.710 --> 00:17:49.720 align:start position:0% data loss you can't afford to have the 00:17:49.720 --> 00:17:51.390 align:start position:0% data loss you can't afford to have the kinds<00:17:49.960> of<00:17:50.200> problems<00:17:50.679> that<00:17:50.960> you<00:17:51.080> know 00:17:51.390 --> 00:17:51.400 align:start position:0% kinds of problems that you know 00:17:51.400 --> 00:17:54.510 align:start position:0% kinds of problems that you know zookeeper<00:17:52.039> helps<00:17:52.320> you<00:17:52.559> avoid<00:17:53.080> so<00:17:53.720> gladly<00:17:54.200> pay 00:17:54.510 --> 00:17:54.520 align:start position:0% zookeeper helps you avoid so gladly pay 00:17:54.520 --> 00:17:57.750 align:start position:0% zookeeper helps you avoid so gladly pay that<00:17:54.799> cost<00:17:55.320> because<00:17:56.000> it's<00:17:56.200> going<00:17:56.400> to<00:17:56.720> save<00:17:57.080> you 00:17:57.750 --> 00:17:57.760 align:start position:0% that cost because it's going to save you 00:17:57.760 --> 00:17:59.789 align:start position:0% that cost because it's going to save you you<00:17:57.919> know<00:17:58.159> in<00:17:58.320> the<00:17:58.440> long<00:17:58.640> run<00:17:58.919> on<00:17:59.559> uh<00:17:59.640> it's 00:17:59.789 --> 00:17:59.799 align:start position:0% you know in the long run on uh it's 00:17:59.799 --> 00:18:01.710 align:start position:0% you know in the long run on uh it's great<00:17:59.960> to<00:18:00.039> hear<00:18:00.240> this<00:18:00.400> I<00:18:00.440> mean<00:18:00.760> uh<00:18:00.880> you<00:18:01.000> know<00:18:01.280> I 00:18:01.710 --> 00:18:01.720 align:start position:0% great to hear this I mean uh you know I 00:18:01.720 --> 00:18:03.270 align:start position:0% great to hear this I mean uh you know I uh<00:18:01.919> come<00:18:02.120> from<00:18:02.320> a<00:18:02.440> distributed<00:18:02.960> systems 00:18:03.270 --> 00:18:03.280 align:start position:0% uh come from a distributed systems 00:18:03.280 --> 00:18:05.590 align:start position:0% uh come from a distributed systems Community<00:18:03.760> where<00:18:04.240> we<00:18:04.400> use<00:18:04.600> Scola<00:18:05.039> and<00:18:05.200> Spark 00:18:05.590 --> 00:18:05.600 align:start position:0% Community where we use Scola and Spark 00:18:05.600 --> 00:18:07.710 align:start position:0% Community where we use Scola and Spark and<00:18:05.840> a<00:18:06.120> and<00:18:06.400> tools<00:18:06.640> like<00:18:06.880> that<00:18:07.080> so<00:18:07.520> and<00:18:07.640> you 00:18:07.710 --> 00:18:07.720 align:start position:0% and a and tools like that so and you 00:18:07.720 --> 00:18:09.390 align:start position:0% and a and tools like that so and you know<00:18:07.880> meses<00:18:08.200> and<00:18:08.360> Aurora<00:18:08.760> of<00:18:08.880> course<00:18:09.039> and<00:18:09.240> all 00:18:09.390 --> 00:18:09.400 align:start position:0% know meses and Aurora of course and all 00:18:09.400 --> 00:18:11.149 align:start position:0% know meses and Aurora of course and all these<00:18:09.600> things<00:18:10.039> and<00:18:10.120> so<00:18:10.280> it<00:18:10.440> comes<00:18:10.919> you<00:18:11.000> know 00:18:11.149 --> 00:18:11.159 align:start position:0% these things and so it comes you know 00:18:11.159 --> 00:18:13.710 align:start position:0% these things and so it comes you know goes<00:18:11.360> without<00:18:11.720> saying<00:18:12.720> what<00:18:13.440> kind<00:18:13.600> of 00:18:13.710 --> 00:18:13.720 align:start position:0% goes without saying what kind of 00:18:13.720 --> 00:18:15.230 align:start position:0% goes without saying what kind of benefits<00:18:14.080> you<00:18:14.200> derive<00:18:14.480> from<00:18:14.600> zuker<00:18:15.039> but 00:18:15.230 --> 00:18:15.240 align:start position:0% benefits you derive from zuker but 00:18:15.240 --> 00:18:16.909 align:start position:0% benefits you derive from zuker but apparently<00:18:16.240> uh<00:18:16.360> you<00:18:16.440> know<00:18:16.600> it's<00:18:16.799> the 00:18:16.909 --> 00:18:16.919 align:start position:0% apparently uh you know it's the 00:18:16.919 --> 00:18:18.190 align:start position:0% apparently uh you know it's the knowledge<00:18:17.280> kind<00:18:17.400> of<00:18:17.520> you<00:18:17.640> know<00:18:17.760> spreading 00:18:18.190 --> 00:18:18.200 align:start position:0% knowledge kind of you know spreading 00:18:18.200 --> 00:18:19.510 align:start position:0% knowledge kind of you know spreading through<00:18:18.440> through<00:18:18.640> communities<00:18:19.240> different 00:18:19.510 --> 00:18:19.520 align:start position:0% through through communities different 00:18:19.520 --> 00:18:21.310 align:start position:0% through through communities different speed<00:18:20.200> uh<00:18:20.280> so<00:18:20.440> it's<00:18:20.600> it's<00:18:20.760> great<00:18:20.919> to<00:18:21.000> hear<00:18:21.200> that 00:18:21.310 --> 00:18:21.320 align:start position:0% speed uh so it's it's great to hear that 00:18:21.320 --> 00:18:23.070 align:start position:0% speed uh so it's it's great to hear that you<00:18:21.480> guys<00:18:21.880> you<00:18:21.960> know<00:18:22.159> rely<00:18:22.440> on<00:18:22.559> that<00:18:22.720> this<00:18:22.840> is 00:18:23.070 --> 00:18:23.080 align:start position:0% you guys you know rely on that this is 00:18:23.080 --> 00:18:24.950 align:start position:0% you guys you know rely on that this is proven<00:18:23.400> technology<00:18:24.280> right<00:18:24.400> which<00:18:24.520> is 00:18:24.950 --> 00:18:24.960 align:start position:0% proven technology right which is 00:18:24.960 --> 00:18:26.630 align:start position:0% proven technology right which is designed<00:18:25.320> to<00:18:25.480> actually<00:18:25.799> you<00:18:25.880> know<00:18:26.200> enable 00:18:26.630 --> 00:18:26.640 align:start position:0% designed to actually you know enable 00:18:26.640 --> 00:18:30.549 align:start position:0% designed to actually you know enable this<00:18:27.400> um<00:18:27.880> so<00:18:28.520> uh<00:18:28.799> so<00:18:29.240> you<00:18:29.360> mention<00:18:29.720> spark<00:18:30.240> and 00:18:30.549 --> 00:18:30.559 align:start position:0% this um so uh so you mention spark and 00:18:30.559 --> 00:18:33.669 align:start position:0% this um so uh so you mention spark and you<00:18:30.679> know<00:18:31.400> since<00:18:31.679> I<00:18:31.840> also<00:18:32.640> uh<00:18:32.760> organize<00:18:33.360> SF 00:18:33.669 --> 00:18:33.679 align:start position:0% you know since I also uh organize SF 00:18:33.679 --> 00:18:36.750 align:start position:0% you know since I also uh organize SF scol<00:18:33.960> mop<00:18:34.360> and<00:18:34.799> organize<00:18:35.280> spark<00:18:35.520> M<00:18:35.720> up<00:18:36.360> uh<00:18:36.520> I 00:18:36.750 --> 00:18:36.760 align:start position:0% scol mop and organize spark M up uh I 00:18:36.760 --> 00:18:39.350 align:start position:0% scol mop and organize spark M up uh I got<00:18:36.840> to<00:18:36.960> ask<00:18:37.120> about<00:18:37.360> this<00:18:37.919> uh<00:18:38.280> so<00:18:38.840> how<00:18:39.000> do<00:18:39.159> you 00:18:39.350 --> 00:18:39.360 align:start position:0% got to ask about this uh so how do you 00:18:39.360 --> 00:18:42.350 align:start position:0% got to ask about this uh so how do you guys<00:18:39.919> interoperate<00:18:40.840> with<00:18:41.200> uh<00:18:41.360> with<00:18:41.559> Scala<00:18:42.200> and 00:18:42.350 --> 00:18:42.360 align:start position:0% guys interoperate with uh with Scala and 00:18:42.360 --> 00:18:44.510 align:start position:0% guys interoperate with uh with Scala and Spark<00:18:42.760> and<00:18:42.960> given<00:18:43.280> that<00:18:43.679> spark<00:18:44.039> now<00:18:44.200> runs<00:18:44.400> on 00:18:44.510 --> 00:18:44.520 align:start position:0% Spark and given that spark now runs on 00:18:44.520 --> 00:18:47.149 align:start position:0% Spark and given that spark now runs on top<00:18:44.679> of<00:18:44.799> almost<00:18:45.080> any<00:18:45.240> distributed<00:18:45.919> system<00:18:46.919> uh 00:18:47.149 --> 00:18:47.159 align:start position:0% top of almost any distributed system uh 00:18:47.159 --> 00:18:49.149 align:start position:0% top of almost any distributed system uh you<00:18:47.240> know<00:18:47.720> should<00:18:47.919> I<00:18:48.080> be<00:18:48.200> able<00:18:48.400> to<00:18:48.520> run<00:18:48.760> spark 00:18:49.149 --> 00:18:49.159 align:start position:0% you know should I be able to run spark 00:18:49.159 --> 00:18:50.789 align:start position:0% you know should I be able to run spark on<00:18:49.280> top<00:18:49.440> of<00:18:49.520> solar<00:18:49.880> for<00:18:50.039> instance<00:18:50.280> and<00:18:50.440> open<00:18:50.679> up 00:18:50.789 --> 00:18:50.799 align:start position:0% on top of solar for instance and open up 00:18:50.799 --> 00:18:52.430 align:start position:0% on top of solar for instance and open up you<00:18:50.880> know<00:18:51.000> a<00:18:51.120> bunch<00:18:51.280> of<00:18:51.360> readers<00:18:52.000> read<00:18:52.200> a<00:18:52.280> bunch 00:18:52.430 --> 00:18:52.440 align:start position:0% you know a bunch of readers read a bunch 00:18:52.440 --> 00:18:54.149 align:start position:0% you know a bunch of readers read a bunch of<00:18:52.520> stuff<00:18:52.679> in<00:18:52.919> and<00:18:53.280> kind<00:18:53.440> of<00:18:53.640> do<00:18:53.799> something 00:18:54.149 --> 00:18:54.159 align:start position:0% of stuff in and kind of do something 00:18:54.159 --> 00:18:56.230 align:start position:0% of stuff in and kind of do something there<00:18:54.799> have<00:18:54.880> you<00:18:55.039> been<00:18:55.400> uh<00:18:55.520> listening<00:18:55.960> in<00:18:56.080> on 00:18:56.230 --> 00:18:56.240 align:start position:0% there have you been uh listening in on 00:18:56.240 --> 00:18:59.110 align:start position:0% there have you been uh listening in on our<00:18:56.440> meetings<00:18:57.440> at<00:18:57.640> work<00:18:57.880> at<00:18:58.000> Lucid<00:18:58.400> works<00:18:58.919> no<00:18:59.039> I 00:18:59.110 --> 00:18:59.120 align:start position:0% our meetings at work at Lucid works no I 00:18:59.120 --> 00:19:00.590 align:start position:0% our meetings at work at Lucid works no I mean<00:18:59.320> that's<00:18:59.440> a<00:18:59.559> great<00:18:59.760> question<00:19:00.039> now<00:19:00.280> we<00:19:00.400> just 00:19:00.590 --> 00:19:00.600 align:start position:0% mean that's a great question now we just 00:19:00.600 --> 00:19:02.870 align:start position:0% mean that's a great question now we just recently<00:19:01.080> actually<00:19:01.440> published<00:19:02.039> uh<00:19:02.520> solar 00:19:02.870 --> 00:19:02.880 align:start position:0% recently actually published uh solar 00:19:02.880 --> 00:19:04.830 align:start position:0% recently actually published uh solar spark<00:19:03.320> integration<00:19:03.919> it's<00:19:04.080> up<00:19:04.200> on<00:19:04.320> our<00:19:04.520> Lucid 00:19:04.830 --> 00:19:04.840 align:start position:0% spark integration it's up on our Lucid 00:19:04.840 --> 00:19:06.789 align:start position:0% spark integration it's up on our Lucid Works<00:19:05.159> GitHub<00:19:05.559> page<00:19:05.760> so<00:19:05.880> if<00:19:05.960> you<00:19:06.080> go<00:19:06.400> just<00:19:06.559> do 00:19:06.789 --> 00:19:06.799 align:start position:0% Works GitHub page so if you go just do 00:19:06.799 --> 00:19:09.110 align:start position:0% Works GitHub page so if you go just do Lucid<00:19:07.120> Works<00:19:07.400> GitHub<00:19:07.799> you'll<00:19:08.000> find<00:19:08.840> uh<00:19:08.960> a 00:19:09.110 --> 00:19:09.120 align:start position:0% Lucid Works GitHub you'll find uh a 00:19:09.120 --> 00:19:11.190 align:start position:0% Lucid Works GitHub you'll find uh a spark<00:19:09.480> solar<00:19:09.880> integration<00:19:10.440> there<00:19:10.640> all<00:19:10.880> open 00:19:11.190 --> 00:19:11.200 align:start position:0% spark solar integration there all open 00:19:11.200 --> 00:19:13.750 align:start position:0% spark solar integration there all open source<00:19:11.520> Apache<00:19:12.200> License<00:19:13.200> uh<00:19:13.360> and<00:19:13.440> so<00:19:13.600> that's 00:19:13.750 --> 00:19:13.760 align:start position:0% source Apache License uh and so that's 00:19:13.760 --> 00:19:15.149 align:start position:0% source Apache License uh and so that's kind<00:19:13.880> of<00:19:14.000> one<00:19:14.200> level<00:19:14.480> that's<00:19:14.799> essentially 00:19:15.149 --> 00:19:15.159 align:start position:0% kind of one level that's essentially 00:19:15.159 --> 00:19:16.870 align:start position:0% kind of one level that's essentially about<00:19:15.400> how<00:19:15.520> do<00:19:15.679> I<00:19:15.960> interact<00:19:16.400> with<00:19:16.600> getting 00:19:16.870 --> 00:19:16.880 align:start position:0% about how do I interact with getting 00:19:16.880 --> 00:19:19.350 align:start position:0% about how do I interact with getting data<00:19:17.159> in<00:19:17.320> and<00:19:17.480> out<00:19:17.640> of<00:19:17.799> solar<00:19:18.280> into<00:19:18.600> spark<00:19:19.000> and 00:19:19.350 --> 00:19:19.360 align:start position:0% data in and out of solar into spark and 00:19:19.360 --> 00:19:21.549 align:start position:0% data in and out of solar into spark and vice<00:19:19.640> versa<00:19:20.039> right<00:19:20.880> um<00:19:21.000> so<00:19:21.159> that's<00:19:21.360> kind<00:19:21.480> of 00:19:21.549 --> 00:19:21.559 align:start position:0% vice versa right um so that's kind of 00:19:21.559 --> 00:19:23.430 align:start position:0% vice versa right um so that's kind of the<00:19:21.720> one<00:19:21.960> level<00:19:22.200> of<00:19:22.360> thing<00:19:22.840> the<00:19:22.960> other<00:19:23.159> level 00:19:23.430 --> 00:19:23.440 align:start position:0% the one level of thing the other level 00:19:23.440 --> 00:19:26.350 align:start position:0% the one level of thing the other level is<00:19:23.640> in<00:19:24.000> in<00:19:24.280> actually<00:19:24.520> in<00:19:24.640> our<00:19:25.120> commercial<00:19:26.120> uh 00:19:26.350 --> 00:19:26.360 align:start position:0% is in in actually in our commercial uh 00:19:26.360 --> 00:19:29.310 align:start position:0% is in in actually in our commercial uh product<00:19:26.679> called<00:19:26.840> Lucid<00:19:27.200> Works<00:19:27.480> Fusion<00:19:28.360> we<00:19:28.840> are 00:19:29.310 --> 00:19:29.320 align:start position:0% product called Lucid Works Fusion we are 00:19:29.320 --> 00:19:31.669 align:start position:0% product called Lucid Works Fusion we are in<00:19:29.440> the<00:19:29.720> process<00:19:30.039> of<00:19:30.240> bringing<00:19:30.760> in<00:19:31.159> so<00:19:31.360> we<00:19:31.600> you 00:19:31.669 --> 00:19:31.679 align:start position:0% in the process of bringing in so we you 00:19:31.679 --> 00:19:33.230 align:start position:0% in the process of bringing in so we you know<00:19:31.799> with<00:19:31.919> Fusion<00:19:32.280> we<00:19:32.400> do<00:19:32.559> a<00:19:32.679> lot<00:19:32.799> of<00:19:32.960> things 00:19:33.230 --> 00:19:33.240 align:start position:0% know with Fusion we do a lot of things 00:19:33.240 --> 00:19:35.190 align:start position:0% know with Fusion we do a lot of things about<00:19:33.600> signal<00:19:34.080> capture<00:19:34.559> there<00:19:34.799> things<00:19:35.000> like 00:19:35.190 --> 00:19:35.200 align:start position:0% about signal capture there things like 00:19:35.200 --> 00:19:37.430 align:start position:0% about signal capture there things like click<00:19:35.440> stream<00:19:35.840> analysis<00:19:36.440> all<00:19:36.679> that<00:19:37.080> and<00:19:37.240> then 00:19:37.430 --> 00:19:37.440 align:start position:0% click stream analysis all that and then 00:19:37.440 --> 00:19:39.990 align:start position:0% click stream analysis all that and then turn<00:19:37.880> that<00:19:38.200> back<00:19:38.559> into<00:19:39.159> relevance<00:19:39.720> Fe<00:19:39.919> you 00:19:39.990 --> 00:19:40.000 align:start position:0% turn that back into relevance Fe you 00:19:40.000 --> 00:19:41.950 align:start position:0% turn that back into relevance Fe you know<00:19:40.200> back<00:19:40.360> into<00:19:40.799> relevance<00:19:41.320> gold<00:19:41.720> if<00:19:41.840> you 00:19:41.950 --> 00:19:41.960 align:start position:0% know back into relevance gold if you 00:19:41.960 --> 00:19:43.870 align:start position:0% know back into relevance gold if you will<00:19:42.440> so<00:19:42.600> if<00:19:42.720> you<00:19:42.880> take<00:19:43.080> all<00:19:43.360> the<00:19:43.520> click 00:19:43.870 --> 00:19:43.880 align:start position:0% will so if you take all the click 00:19:43.880 --> 00:19:45.190 align:start position:0% will so if you take all the click information<00:19:44.400> that<00:19:44.520> you're<00:19:44.720> getting<00:19:45.080> then 00:19:45.190 --> 00:19:45.200 align:start position:0% information that you're getting then 00:19:45.200 --> 00:19:47.230 align:start position:0% information that you're getting then turn<00:19:45.520> that<00:19:45.760> back<00:19:45.960> around<00:19:46.320> into<00:19:46.600> better<00:19:46.840> search 00:19:47.230 --> 00:19:47.240 align:start position:0% turn that back around into better search 00:19:47.240 --> 00:19:50.990 align:start position:0% turn that back around into better search results<00:19:48.159> right<00:19:48.760> so<00:19:49.760> we<00:19:49.960> do<00:19:50.159> a<00:19:50.280> lot<00:19:50.440> of<00:19:50.640> that<00:19:50.799> in 00:19:50.990 --> 00:19:51.000 align:start position:0% results right so we do a lot of that in 00:19:51.000 --> 00:19:53.149 align:start position:0% results right so we do a lot of that in solar<00:19:51.960> right<00:19:52.080> just<00:19:52.240> out<00:19:52.360> of<00:19:52.480> the<00:19:52.679> box<00:19:52.880> and<00:19:53.039> we 00:19:53.149 --> 00:19:53.159 align:start position:0% solar right just out of the box and we 00:19:53.159 --> 00:19:54.990 align:start position:0% solar right just out of the box and we can<00:19:53.440> query<00:19:53.760> solar<00:19:54.120> in<00:19:54.240> the<00:19:54.400> right<00:19:54.559> way<00:19:54.799> such 00:19:54.990 --> 00:19:55.000 align:start position:0% can query solar in the right way such 00:19:55.000 --> 00:19:56.230 align:start position:0% can query solar in the right way such that<00:19:55.200> we<00:19:55.320> can<00:19:55.520> do<00:19:55.799> things<00:19:56.039> like 00:19:56.230 --> 00:19:56.240 align:start position:0% that we can do things like 00:19:56.240 --> 00:19:57.909 align:start position:0% that we can do things like recommendation<00:19:56.960> engines<00:19:57.440> right<00:19:57.600> out<00:19:57.720> of 00:19:57.909 --> 00:19:57.919 align:start position:0% recommendation engines right out of 00:19:57.919 --> 00:19:59.710 align:start position:0% recommendation engines right out of solar<00:19:58.320> collab<00:19:58.799> of<00:19:58.880> filtering<00:19:59.320> all<00:19:59.480> that<00:19:59.600> kind 00:19:59.710 --> 00:19:59.720 align:start position:0% solar collab of filtering all that kind 00:19:59.720 --> 00:20:01.590 align:start position:0% solar collab of filtering all that kind of<00:19:59.880> stuff<00:20:00.360> where<00:20:00.480> it<00:20:00.640> then<00:20:00.840> gets<00:20:01.120> interesting 00:20:01.590 --> 00:20:01.600 align:start position:0% of stuff where it then gets interesting 00:20:01.600 --> 00:20:02.990 align:start position:0% of stuff where it then gets interesting is<00:20:01.799> essentially<00:20:02.240> those<00:20:02.360> are<00:20:02.559> all<00:20:02.760> like 00:20:02.990 --> 00:20:03.000 align:start position:0% is essentially those are all like 00:20:03.000 --> 00:20:05.110 align:start position:0% is essentially those are all like aggregation<00:20:03.799> problems<00:20:04.320> right<00:20:04.640> or<00:20:04.799> building 00:20:05.110 --> 00:20:05.120 align:start position:0% aggregation problems right or building 00:20:05.120 --> 00:20:07.590 align:start position:0% aggregation problems right or building up<00:20:05.360> models<00:20:06.080> and<00:20:06.200> they<00:20:06.360> often<00:20:06.720> require<00:20:07.240> large 00:20:07.590 --> 00:20:07.600 align:start position:0% up models and they often require large 00:20:07.600 --> 00:20:10.190 align:start position:0% up models and they often require large scale<00:20:08.080> batch<00:20:08.520> you<00:20:08.640> know<00:20:08.880> style<00:20:09.320> compute<00:20:10.080> this 00:20:10.190 --> 00:20:10.200 align:start position:0% scale batch you know style compute this 00:20:10.200 --> 00:20:12.310 align:start position:0% scale batch you know style compute this is<00:20:10.360> where<00:20:10.640> Spark<00:20:11.080> comes<00:20:11.320> in<00:20:11.520> as<00:20:11.679> if<00:20:12.000> in<00:20:12.120> the 00:20:12.310 --> 00:20:12.320 align:start position:0% is where Spark comes in as if in the 00:20:12.320 --> 00:20:15.390 align:start position:0% is where Spark comes in as if in the truly<00:20:12.720> large<00:20:13.120> cases<00:20:13.520> where<00:20:13.720> we<00:20:14.000> have<00:20:14.240> you<00:20:14.400> know 00:20:15.390 --> 00:20:15.400 align:start position:0% truly large cases where we have you know 00:20:15.400 --> 00:20:17.070 align:start position:0% truly large cases where we have you know uh<00:20:15.840> you<00:20:15.960> know<00:20:16.080> you're<00:20:16.240> doing<00:20:16.559> millions<00:20:16.919> and 00:20:17.070 --> 00:20:17.080 align:start position:0% uh you know you're doing millions and 00:20:17.080 --> 00:20:19.909 align:start position:0% uh you know you're doing millions and millions<00:20:17.480> of<00:20:17.960> events<00:20:18.360> an<00:20:18.600> hour<00:20:19.120> or<00:20:19.480> you<00:20:19.600> know<00:20:19.760> a 00:20:19.909 --> 00:20:19.919 align:start position:0% millions of events an hour or you know a 00:20:19.919 --> 00:20:21.510 align:start position:0% millions of events an hour or you know a day<00:20:20.159> Etc<00:20:20.559> and<00:20:20.640> you<00:20:20.720> get<00:20:20.840> a<00:20:21.000> really<00:20:21.200> large 00:20:21.510 --> 00:20:21.520 align:start position:0% day Etc and you get a really large 00:20:21.520 --> 00:20:23.669 align:start position:0% day Etc and you get a really large essentially<00:20:21.960> Matrix<00:20:22.799> spark<00:20:23.159> is<00:20:23.280> a<00:20:23.440> great 00:20:23.669 --> 00:20:23.679 align:start position:0% essentially Matrix spark is a great 00:20:23.679 --> 00:20:25.190 align:start position:0% essentially Matrix spark is a great place<00:20:23.840> to<00:20:24.000> come<00:20:24.159> in<00:20:24.320> and<00:20:24.480> do<00:20:24.679> that<00:20:24.880> machine 00:20:25.190 --> 00:20:25.200 align:start position:0% place to come in and do that machine 00:20:25.200 --> 00:20:27.110 align:start position:0% place to come in and do that machine learning<00:20:25.960> work<00:20:26.240> where<00:20:26.400> you're<00:20:26.559> building<00:20:26.919> a 00:20:27.110 --> 00:20:27.120 align:start position:0% learning work where you're building a 00:20:27.120 --> 00:20:30.390 align:start position:0% learning work where you're building a model<00:20:27.600> in<00:20:27.799> spark<00:20:28.480> and<00:20:28.880> then<00:20:29.320> you<00:20:29.720> you<00:20:29.880> plug<00:20:30.159> it 00:20:30.390 --> 00:20:30.400 align:start position:0% model in spark and then you you plug it 00:20:30.400 --> 00:20:32.830 align:start position:0% model in spark and then you you plug it back<00:20:30.600> in<00:20:31.159> Works<00:20:31.480> seamlessly<00:20:32.080> with<00:20:32.240> fusion<00:20:32.679> and 00:20:32.830 --> 00:20:32.840 align:start position:0% back in Works seamlessly with fusion and 00:20:32.840 --> 00:20:34.909 align:start position:0% back in Works seamlessly with fusion and then<00:20:32.960> you<00:20:33.039> can<00:20:33.280> go<00:20:33.720> and<00:20:34.120> you<00:20:34.200> know<00:20:34.360> query<00:20:34.760> that 00:20:34.909 --> 00:20:34.919 align:start position:0% then you can go and you know query that 00:20:34.919 --> 00:20:35.950 align:start position:0% then you can go and you know query that model<00:20:35.200> so<00:20:35.320> if<00:20:35.400> you're<00:20:35.520> building<00:20:35.799> a 00:20:35.950 --> 00:20:35.960 align:start position:0% model so if you're building a 00:20:35.960 --> 00:20:37.990 align:start position:0% model so if you're building a classification<00:20:36.720> model<00:20:37.039> if<00:20:37.159> you're<00:20:37.280> building 00:20:37.990 --> 00:20:38.000 align:start position:0% classification model if you're building 00:20:38.000 --> 00:20:41.510 align:start position:0% classification model if you're building a<00:20:38.159> recommender<00:20:38.880> etc<00:20:39.679> we<00:20:39.799> can<00:20:40.360> tie<00:20:40.640> that<00:20:40.840> all<00:20:41.080> in 00:20:41.510 --> 00:20:41.520 align:start position:0% a recommender etc we can tie that all in 00:20:41.520 --> 00:20:42.750 align:start position:0% a recommender etc we can tie that all in together<00:20:41.799> and<00:20:41.880> so<00:20:42.080> that's<00:20:42.240> going<00:20:42.360> to<00:20:42.640> that's 00:20:42.750 --> 00:20:42.760 align:start position:0% together and so that's going to that's 00:20:42.760 --> 00:20:44.230 align:start position:0% together and so that's going to that's going<00:20:42.880> to<00:20:42.960> be<00:20:43.120> part<00:20:43.240> of<00:20:43.360> our<00:20:43.600> product<00:20:43.919> here 00:20:44.230 --> 00:20:44.240 align:start position:0% going to be part of our product here 00:20:44.240 --> 00:20:46.230 align:start position:0% going to be part of our product here very<00:20:44.400> soon<00:20:44.799> as<00:20:45.000> well<00:20:45.200> so<00:20:45.520> so<00:20:45.720> yeah<00:20:45.880> we<00:20:46.000> love 00:20:46.230 --> 00:20:46.240 align:start position:0% very soon as well so so yeah we love 00:20:46.240 --> 00:20:48.430 align:start position:0% very soon as well so so yeah we love spark<00:20:46.960> uh<00:20:47.159> you<00:20:47.240> know<00:20:47.360> we<00:20:47.480> did<00:20:47.600> map<00:20:47.880> ruce<00:20:48.200> for<00:20:48.320> a 00:20:48.430 --> 00:20:48.440 align:start position:0% spark uh you know we did map ruce for a 00:20:48.440 --> 00:20:50.830 align:start position:0% spark uh you know we did map ruce for a long<00:20:48.679> time<00:20:48.919> saw<00:20:49.240> the<00:20:49.640> shortcomings<00:20:50.640> uh<00:20:50.720> you 00:20:50.830 --> 00:20:50.840 align:start position:0% long time saw the shortcomings uh you 00:20:50.840 --> 00:20:52.669 align:start position:0% long time saw the shortcomings uh you know<00:20:51.039> another<00:20:51.360> project<00:20:51.720> I'm<00:20:51.880> involved<00:20:52.320> with 00:20:52.669 --> 00:20:52.679 align:start position:0% know another project I'm involved with 00:20:52.679 --> 00:20:55.270 align:start position:0% know another project I'm involved with Mout<00:20:53.679> uh<00:20:53.919> that's<00:20:54.080> all<00:20:54.280> been<00:20:54.480> switching<00:20:54.960> over 00:20:55.270 --> 00:20:55.280 align:start position:0% Mout uh that's all been switching over 00:20:55.280 --> 00:20:58.789 align:start position:0% Mout uh that's all been switching over to<00:20:55.799> spark<00:20:56.200> and<00:20:56.400> Scala<00:20:57.080> as<00:20:57.280> well<00:20:58.240> I'm<00:20:58.360> not<00:20:58.679> as 00:20:58.789 --> 00:20:58.799 align:start position:0% to spark and Scala as well I'm not as 00:20:58.799 --> 00:21:01.510 align:start position:0% to spark and Scala as well I'm not as deeply<00:20:59.159> involved<00:20:59.640> there<00:20:59.799> as<00:20:59.919> I<00:21:00.080> once<00:21:00.360> was<00:21:01.360> uh 00:21:01.510 --> 00:21:01.520 align:start position:0% deeply involved there as I once was uh 00:21:01.520 --> 00:21:03.070 align:start position:0% deeply involved there as I once was uh but<00:21:01.640> you<00:21:01.720> know<00:21:01.840> a<00:21:01.960> lot<00:21:02.080> of<00:21:02.240> great<00:21:02.480> work<00:21:02.840> there 00:21:03.070 --> 00:21:03.080 align:start position:0% but you know a lot of great work there 00:21:03.080 --> 00:21:05.070 align:start position:0% but you know a lot of great work there about<00:21:03.360> bringing<00:21:03.840> more<00:21:04.120> machine<00:21:04.440> learning 00:21:05.070 --> 00:21:05.080 align:start position:0% about bringing more machine learning 00:21:05.080 --> 00:21:08.590 align:start position:0% about bringing more machine learning capabilities<00:21:06.080> into<00:21:06.559> sculla<00:21:07.080> and<00:21:07.240> into<00:21:07.640> spark 00:21:08.590 --> 00:21:08.600 align:start position:0% capabilities into sculla and into spark 00:21:08.600 --> 00:21:10.590 align:start position:0% capabilities into sculla and into spark uh<00:21:08.799> you<00:21:08.919> know<00:21:09.200> around<00:21:09.960> there's<00:21:10.120> some<00:21:10.320> really 00:21:10.590 --> 00:21:10.600 align:start position:0% uh you know around there's some really 00:21:10.600 --> 00:21:12.549 align:start position:0% uh you know around there's some really nice<00:21:11.080> uh<00:21:11.279> there's<00:21:11.400> a<00:21:11.520> really<00:21:11.720> nice<00:21:11.919> DSL<00:21:12.400> in 00:21:12.549 --> 00:21:12.559 align:start position:0% nice uh there's a really nice DSL in 00:21:12.559 --> 00:21:14.149 align:start position:0% nice uh there's a really nice DSL in there<00:21:12.679> for<00:21:12.840> building<00:21:13.240> generalized<00:21:13.799> linear 00:21:14.149 --> 00:21:14.159 align:start position:0% there for building generalized linear 00:21:14.159 --> 00:21:16.710 align:start position:0% there for building generalized linear models<00:21:14.640> now<00:21:15.480> uh<00:21:15.760> right<00:21:15.919> you<00:21:16.039> know<00:21:16.240> leverages 00:21:16.710 --> 00:21:16.720 align:start position:0% models now uh right you know leverages 00:21:16.720 --> 00:21:18.549 align:start position:0% models now uh right you know leverages skull<00:21:17.120> underneath<00:21:17.520> the<00:21:17.720> hood<00:21:18.080> and<00:21:18.240> and<00:21:18.360> makes 00:21:18.549 --> 00:21:18.559 align:start position:0% skull underneath the hood and and makes 00:21:18.559 --> 00:21:21.470 align:start position:0% skull underneath the hood and and makes it<00:21:18.760> super<00:21:19.039> easy<00:21:19.279> for<00:21:19.480> people<00:21:19.679> to<00:21:19.840> build<00:21:20.120> out<00:21:21.120> uh 00:21:21.470 --> 00:21:21.480 align:start position:0% it super easy for people to build out uh 00:21:21.480 --> 00:21:23.350 align:start position:0% it super easy for people to build out uh those<00:21:21.720> kinds<00:21:21.919> of<00:21:22.080> things<00:21:22.360> build<00:21:22.640> your<00:21:22.760> models 00:21:23.350 --> 00:21:23.360 align:start position:0% those kinds of things build your models 00:21:23.360 --> 00:21:25.310 align:start position:0% those kinds of things build your models and<00:21:23.480> that's<00:21:23.640> all<00:21:23.919> spark<00:21:24.240> and<00:21:24.440> scol<00:21:24.919> underneath 00:21:25.310 --> 00:21:25.320 align:start position:0% and that's all spark and scol underneath 00:21:25.320 --> 00:21:27.990 align:start position:0% and that's all spark and scol underneath the<00:21:25.440> hood<00:21:25.880> as<00:21:26.000> I<00:21:26.480> understand<00:21:26.640> it<00:21:26.919> so<00:21:27.760> uh<00:21:27.880> you 00:21:27.990 --> 00:21:28.000 align:start position:0% the hood as I understand it so uh you 00:21:28.000 --> 00:21:30.630 align:start position:0% the hood as I understand it so uh you know<00:21:28.799> I<00:21:29.039> myself<00:21:29.360> am<00:21:29.520> not<00:21:29.640> a<00:21:29.760> scholar<00:21:30.240> person 00:21:30.630 --> 00:21:30.640 align:start position:0% know I myself am not a scholar person 00:21:30.640 --> 00:21:32.870 align:start position:0% know I myself am not a scholar person but<00:21:31.039> uh<00:21:31.159> you<00:21:31.279> know<00:21:31.480> we<00:21:31.840> we<00:21:31.960> do<00:21:32.120> see<00:21:32.360> it<00:21:32.480> in<00:21:32.600> a<00:21:32.720> lot 00:21:32.870 --> 00:21:32.880 align:start position:0% but uh you know we we do see it in a lot 00:21:32.880 --> 00:21:34.630 align:start position:0% but uh you know we we do see it in a lot of<00:21:33.039> different<00:21:33.320> places<00:21:33.679> and<00:21:33.880> have<00:21:34.080> some<00:21:34.279> of<00:21:34.400> it 00:21:34.630 --> 00:21:34.640 align:start position:0% of different places and have some of it 00:21:34.640 --> 00:21:37.549 align:start position:0% of different places and have some of it within<00:21:35.440> the<00:21:35.640> company<00:21:36.120> as<00:21:36.320> well<00:21:36.799> so<00:21:37.320> that's 00:21:37.549 --> 00:21:37.559 align:start position:0% within the company as well so that's 00:21:37.559 --> 00:21:39.149 align:start position:0% within the company as well so that's great<00:21:37.720> to<00:21:37.840> hear<00:21:38.080> you<00:21:38.159> know<00:21:38.320> because<00:21:38.799> uh<00:21:38.919> I<00:21:39.000> can 00:21:39.149 --> 00:21:39.159 align:start position:0% great to hear you know because uh I can 00:21:39.159 --> 00:21:41.390 align:start position:0% great to hear you know because uh I can tell<00:21:39.360> you<00:21:39.520> you<00:21:39.640> know<00:21:40.000> kind<00:21:40.120> of<00:21:40.320> a<00:21:40.720> as<00:21:40.880> a 00:21:41.390 --> 00:21:41.400 align:start position:0% tell you you know kind of a as a 00:21:41.400 --> 00:21:44.789 align:start position:0% tell you you know kind of a as a developer<00:21:42.039> who<00:21:42.520> build<00:21:43.080> systems<00:21:44.080> uh<00:21:44.279> we<00:21:44.559> use 00:21:44.789 --> 00:21:44.799 align:start position:0% developer who build systems uh we use 00:21:44.799 --> 00:21:47.350 align:start position:0% developer who build systems uh we use both<00:21:45.039> search<00:21:45.799> and<00:21:46.120> and<00:21:46.360> NLP<00:21:46.799> machine<00:21:47.039> learning 00:21:47.350 --> 00:21:47.360 align:start position:0% both search and and NLP machine learning 00:21:47.360 --> 00:21:51.230 align:start position:0% both search and and NLP machine learning and<00:21:47.559> extraction<00:21:48.440> I<00:21:48.600> think<00:21:49.240> uh<00:21:49.919> uh<00:21:50.320> solar<00:21:51.039> and 00:21:51.230 --> 00:21:51.240 align:start position:0% and extraction I think uh uh solar and 00:21:51.240 --> 00:21:52.830 align:start position:0% and extraction I think uh uh solar and Spark<00:21:51.600> make<00:21:51.799> an<00:21:51.919> ideal<00:21:52.200> combination<00:21:52.640> because 00:21:52.830 --> 00:21:52.840 align:start position:0% Spark make an ideal combination because 00:21:52.840 --> 00:21:55.190 align:start position:0% Spark make an ideal combination because for<00:21:52.960> instance<00:21:53.400> if<00:21:53.559> I<00:21:53.720> round<00:21:53.960> up<00:21:54.080> of<00:21:54.200> a<00:21:54.320> database 00:21:55.190 --> 00:21:55.200 align:start position:0% for instance if I round up of a database 00:21:55.200 --> 00:21:56.510 align:start position:0% for instance if I round up of a database I<00:21:55.320> essentially<00:21:55.760> have<00:21:55.880> to<00:21:56.000> think<00:21:56.200> how<00:21:56.360> I'm 00:21:56.510 --> 00:21:56.520 align:start position:0% I essentially have to think how I'm 00:21:56.520 --> 00:21:57.990 align:start position:0% I essentially have to think how I'm representing<00:21:56.919> my<00:21:57.080> textual<00:21:57.480> data<00:21:57.720> in<00:21:57.840> the 00:21:57.990 --> 00:21:58.000 align:start position:0% representing my textual data in the 00:21:58.000 --> 00:21:59.110 align:start position:0% representing my textual data in the database 00:21:59.110 --> 00:21:59.120 align:start position:0% database 00:21:59.120 --> 00:22:00.669 align:start position:0% database right<00:21:59.320> and<00:21:59.600> you<00:21:59.760> guys<00:21:59.919> spend<00:22:00.159> a<00:22:00.279> lot<00:22:00.400> of<00:22:00.520> time 00:22:00.669 --> 00:22:00.679 align:start position:0% right and you guys spend a lot of time 00:22:00.679 --> 00:22:02.750 align:start position:0% right and you guys spend a lot of time thinking<00:22:00.960> how<00:22:01.120> you<00:22:01.279> do<00:22:01.480> that<00:22:02.000> so<00:22:02.360> so 00:22:02.750 --> 00:22:02.760 align:start position:0% thinking how you do that so so 00:22:02.760 --> 00:22:05.149 align:start position:0% thinking how you do that so so essentially<00:22:03.760> for<00:22:03.960> a<00:22:04.120> lot<00:22:04.240> of<00:22:04.400> applications 00:22:05.149 --> 00:22:05.159 align:start position:0% essentially for a lot of applications 00:22:05.159 --> 00:22:08.269 align:start position:0% essentially for a lot of applications we're<00:22:05.279> going<00:22:05.360> to<00:22:05.520> see<00:22:06.360> uh<00:22:06.760> uh<00:22:06.880> discuss<00:22:07.600> SE<00:22:07.880> text 00:22:08.269 --> 00:22:08.279 align:start position:0% we're going to see uh uh discuss SE text 00:22:08.279 --> 00:22:09.750 align:start position:0% we're going to see uh uh discuss SE text this<00:22:08.760> makes<00:22:09.120> actually<00:22:09.360> a<00:22:09.480> very<00:22:09.640> good 00:22:09.750 --> 00:22:09.760 align:start position:0% this makes actually a very good 00:22:09.760 --> 00:22:11.750 align:start position:0% this makes actually a very good combination<00:22:10.440> so<00:22:10.640> maybe<00:22:11.360> uh<00:22:11.440> since<00:22:11.600> you 00:22:11.750 --> 00:22:11.760 align:start position:0% combination so maybe uh since you 00:22:11.760 --> 00:22:13.750 align:start position:0% combination so maybe uh since you mentioned<00:22:12.240> you<00:22:12.480> guys<00:22:12.640> are<00:22:13.080> developing<00:22:13.559> this 00:22:13.750 --> 00:22:13.760 align:start position:0% mentioned you guys are developing this 00:22:13.760 --> 00:22:16.149 align:start position:0% mentioned you guys are developing this maybe<00:22:14.279> I<00:22:14.360> can<00:22:14.559> ask<00:22:14.720> you<00:22:14.799> to<00:22:14.960> come<00:22:15.159> back<00:22:15.480> and<00:22:15.960> and 00:22:16.149 --> 00:22:16.159 align:start position:0% maybe I can ask you to come back and and 00:22:16.159 --> 00:22:17.750 align:start position:0% maybe I can ask you to come back and and talk<00:22:16.360> about<00:22:16.559> it<00:22:16.760> when<00:22:16.919> you<00:22:17.120> guys<00:22:17.360> are 00:22:17.750 --> 00:22:17.760 align:start position:0% talk about it when you guys are 00:22:17.760 --> 00:22:20.310 align:start position:0% talk about it when you guys are developing<00:22:18.200> it<00:22:18.559> because<00:22:18.840> that's<00:22:19.240> certainly<00:22:20.039> a 00:22:20.310 --> 00:22:20.320 align:start position:0% developing it because that's certainly a 00:22:20.320 --> 00:22:21.909 align:start position:0% developing it because that's certainly a great<00:22:20.520> combination<00:22:20.880> of<00:22:21.000> Technologies<00:22:21.640> so<00:22:21.799> in 00:22:21.909 --> 00:22:21.919 align:start position:0% great combination of Technologies so in 00:22:21.919 --> 00:22:23.590 align:start position:0% great combination of Technologies so in the<00:22:22.000> last<00:22:22.200> question<00:22:22.400> I<00:22:22.440> want<00:22:22.600> to<00:22:22.760> ask<00:22:22.960> you<00:22:23.440> uh 00:22:23.590 --> 00:22:23.600 align:start position:0% the last question I want to ask you uh 00:22:23.600 --> 00:22:27.390 align:start position:0% the last question I want to ask you uh so<00:22:24.400> uh<00:22:24.919> the<00:22:25.919> I<00:22:26.000> think<00:22:26.159> you<00:22:26.400> really<00:22:26.960> present 00:22:27.390 --> 00:22:27.400 align:start position:0% so uh the I think you really present 00:22:27.400 --> 00:22:29.510 align:start position:0% so uh the I think you really present interesting<00:22:28.200> path<00:22:28.600> in<00:22:28.720> open<00:22:28.919> source<00:22:29.279> because 00:22:29.510 --> 00:22:29.520 align:start position:0% interesting path in open source because 00:22:29.520 --> 00:22:31.390 align:start position:0% interesting path in open source because you<00:22:29.760> you<00:22:30.080> you're<00:22:30.320> the<00:22:30.520> guy<00:22:30.679> who<00:22:30.840> interested<00:22:31.200> in 00:22:31.390 --> 00:22:31.400 align:start position:0% you you you're the guy who interested in 00:22:31.400 --> 00:22:33.590 align:start position:0% you you you're the guy who interested in specific<00:22:31.799> technology<00:22:32.480> Masters<00:22:32.919> it<00:22:33.400> very 00:22:33.590 --> 00:22:33.600 align:start position:0% specific technology Masters it very 00:22:33.600 --> 00:22:35.510 align:start position:0% specific technology Masters it very deeply<00:22:33.919> and<00:22:34.120> specifically<00:22:34.760> with<00:22:34.919> Lucine<00:22:35.360> and 00:22:35.510 --> 00:22:35.520 align:start position:0% deeply and specifically with Lucine and 00:22:35.520 --> 00:22:37.510 align:start position:0% deeply and specifically with Lucine and then<00:22:35.960> you<00:22:36.240> you<00:22:36.360> turn<00:22:36.600> it<00:22:36.720> into<00:22:36.880> a<00:22:37.000> successful 00:22:37.510 --> 00:22:37.520 align:start position:0% then you you turn it into a successful 00:22:37.520 --> 00:22:39.870 align:start position:0% then you you turn it into a successful business<00:22:38.480> right<00:22:38.720> which<00:22:38.880> is<00:22:39.080> basically<00:22:39.520> used 00:22:39.870 --> 00:22:39.880 align:start position:0% business right which is basically used 00:22:39.880 --> 00:22:42.029 align:start position:0% business right which is basically used by<00:22:40.080> by<00:22:40.200> a<00:22:40.279> lot<00:22:40.400> of<00:22:40.520> people<00:22:41.200> all<00:22:41.360> over<00:22:41.600> the<00:22:41.720> world 00:22:42.029 --> 00:22:42.039 align:start position:0% by by a lot of people all over the world 00:22:42.039 --> 00:22:43.909 align:start position:0% by by a lot of people all over the world so<00:22:42.520> uh<00:22:42.640> what<00:22:42.799> kind<00:22:42.919> of<00:22:43.080> advice<00:22:43.320> do<00:22:43.440> you<00:22:43.600> have<00:22:43.799> to 00:22:43.909 --> 00:22:43.919 align:start position:0% so uh what kind of advice do you have to 00:22:43.919 --> 00:22:45.909 align:start position:0% so uh what kind of advice do you have to open<00:22:44.159> source<00:22:44.480> people<00:22:45.120> who<00:22:45.400> who<00:22:45.520> want<00:22:45.640> to<00:22:45.760> do 00:22:45.909 --> 00:22:45.919 align:start position:0% open source people who who want to do 00:22:45.919 --> 00:22:47.630 align:start position:0% open source people who who want to do the<00:22:46.000> same<00:22:46.240> there<00:22:46.360> is<00:22:46.440> a<00:22:46.559> lot<00:22:46.720> of<00:22:47.080> uh<00:22:47.200> folks 00:22:47.630 --> 00:22:47.640 align:start position:0% the same there is a lot of uh folks 00:22:47.640 --> 00:22:49.830 align:start position:0% the same there is a lot of uh folks especially<00:22:48.120> in<00:22:48.279> the<00:22:49.000> uh<00:22:49.159> kind<00:22:49.320> of<00:22:49.679> uh 00:22:49.830 --> 00:22:49.840 align:start position:0% especially in the uh kind of uh 00:22:49.840 --> 00:22:53.070 align:start position:0% especially in the uh kind of uh technology<00:22:50.360> area<00:22:50.760> who<00:22:51.000> develop<00:22:51.400> tools<00:22:52.400> uh 00:22:53.070 --> 00:22:53.080 align:start position:0% technology area who develop tools uh 00:22:53.080 --> 00:22:54.909 align:start position:0% technology area who develop tools uh what<00:22:53.240> is<00:22:53.480> you<00:22:53.600> know<00:22:54.039> what<00:22:54.159> are<00:22:54.360> the<00:22:54.520> important 00:22:54.909 --> 00:22:54.919 align:start position:0% what is you know what are the important 00:22:54.919 --> 00:22:56.390 align:start position:0% what is you know what are the important things<00:22:55.159> you<00:22:55.320> have<00:22:55.440> to<00:22:55.600> pay<00:22:55.760> attention<00:22:56.080> to<00:22:56.279> if 00:22:56.390 --> 00:22:56.400 align:start position:0% things you have to pay attention to if 00:22:56.400 --> 00:22:58.470 align:start position:0% things you have to pay attention to if you<00:22:56.520> want<00:22:56.679> to<00:22:57.200> you<00:22:57.320> know<00:22:57.559> take<00:22:57.760> an<00:22:57.919> important 00:22:58.470 --> 00:22:58.480 align:start position:0% you want to you know take an important 00:22:58.480 --> 00:22:59.830 align:start position:0% you want to you know take an important open<00:22:58.640> source<00:22:58.919> technology<00:22:59.400> and<00:22:59.520> make<00:22:59.679> a 00:22:59.830 --> 00:22:59.840 align:start position:0% open source technology and make a 00:22:59.840 --> 00:23:02.909 align:start position:0% open source technology and make a business<00:23:00.120> out<00:23:00.279> of<00:23:00.440> it<00:23:01.120> wow<00:23:01.840> uh<00:23:02.200> that's<00:23:02.360> a<00:23:02.559> great 00:23:02.909 --> 00:23:02.919 align:start position:0% business out of it wow uh that's a great 00:23:02.919 --> 00:23:05.470 align:start position:0% business out of it wow uh that's a great question<00:23:03.760> um<00:23:04.279> you<00:23:04.400> know<00:23:04.600> I<00:23:04.640> mean<00:23:04.840> I<00:23:04.960> think 00:23:05.470 --> 00:23:05.480 align:start position:0% question um you know I mean I think 00:23:05.480 --> 00:23:07.390 align:start position:0% question um you know I mean I think there's<00:23:05.720> a<00:23:05.880> lot<00:23:06.039> of<00:23:06.200> lessons<00:23:06.640> learned<00:23:07.000> across 00:23:07.390 --> 00:23:07.400 align:start position:0% there's a lot of lessons learned across 00:23:07.400 --> 00:23:09.110 align:start position:0% there's a lot of lessons learned across so<00:23:07.559> many<00:23:07.840> things<00:23:08.240> you<00:23:08.320> know<00:23:08.559> I<00:23:08.640> mean<00:23:08.760> building 00:23:09.110 --> 00:23:09.120 align:start position:0% so many things you know I mean building 00:23:09.120 --> 00:23:10.950 align:start position:0% so many things you know I mean building a<00:23:09.279> business<00:23:09.600> is<00:23:09.760> so<00:23:09.919> much<00:23:10.080> more<00:23:10.320> than<00:23:10.520> just<00:23:10.720> the 00:23:10.950 --> 00:23:10.960 align:start position:0% a business is so much more than just the 00:23:10.960 --> 00:23:13.830 align:start position:0% a business is so much more than just the technology<00:23:11.799> right<00:23:12.520> uh<00:23:12.640> and<00:23:12.840> open<00:23:13.159> source<00:23:13.480> as<00:23:13.640> a 00:23:13.830 --> 00:23:13.840 align:start position:0% technology right uh and open source as a 00:23:13.840 --> 00:23:15.830 align:start position:0% technology right uh and open source as a business<00:23:14.200> model<00:23:14.880> has<00:23:15.000> a<00:23:15.120> lot<00:23:15.240> of<00:23:15.400> great<00:23:15.640> things 00:23:15.830 --> 00:23:15.840 align:start position:0% business model has a lot of great things 00:23:15.840 --> 00:23:17.909 align:start position:0% business model has a lot of great things and<00:23:16.039> a<00:23:16.159> lot<00:23:16.279> of<00:23:16.440> challenges<00:23:17.039> as<00:23:17.240> well<00:23:17.600> right<00:23:17.760> in 00:23:17.909 --> 00:23:17.919 align:start position:0% and a lot of challenges as well right in 00:23:17.919 --> 00:23:20.909 align:start position:0% and a lot of challenges as well right in terms<00:23:18.279> of<00:23:18.760> you<00:23:18.840> know<00:23:19.080> you've<00:23:19.400> got<00:23:20.400> uh<00:23:20.679> you<00:23:20.760> know 00:23:20.909 --> 00:23:20.919 align:start position:0% terms of you know you've got uh you know 00:23:20.919 --> 00:23:22.990 align:start position:0% terms of you know you've got uh you know for<00:23:21.080> us<00:23:21.240> it<00:23:21.400> was<00:23:21.559> interesting<00:23:22.080> like<00:23:22.400> uh<00:23:22.760> very 00:23:22.990 --> 00:23:23.000 align:start position:0% for us it was interesting like uh very 00:23:23.000 --> 00:23:25.190 align:start position:0% for us it was interesting like uh very early<00:23:23.320> on<00:23:23.600> you<00:23:23.720> know<00:23:23.880> we<00:23:24.000> were<00:23:24.240> like<00:23:24.720> uh<00:23:24.960> let's 00:23:25.190 --> 00:23:25.200 align:start position:0% early on you know we were like uh let's 00:23:25.200 --> 00:23:27.029 align:start position:0% early on you know we were like uh let's just<00:23:25.400> go<00:23:25.640> we<00:23:25.760> can<00:23:25.919> just<00:23:26.039> go<00:23:26.240> put<00:23:26.400> out<00:23:26.600> our<00:23:26.880> our 00:23:27.029 --> 00:23:27.039 align:start position:0% just go we can just go put out our our 00:23:27.039 --> 00:23:28.909 align:start position:0% just go we can just go put out our our welcome<00:23:27.440> mat<00:23:27.760> and<00:23:27.880> people<00:23:28.200> come<00:23:28.520> to<00:23:28.640> us<00:23:28.760> for 00:23:28.909 --> 00:23:28.919 align:start position:0% welcome mat and people come to us for 00:23:28.919 --> 00:23:31.549 align:start position:0% welcome mat and people come to us for solar<00:23:29.400> support<00:23:30.360> and<00:23:30.480> you<00:23:30.559> know<00:23:30.720> the<00:23:30.840> brake<00:23:31.120> fix 00:23:31.549 --> 00:23:31.559 align:start position:0% solar support and you know the brake fix 00:23:31.559 --> 00:23:34.110 align:start position:0% solar support and you know the brake fix hey<00:23:31.679> I<00:23:31.799> need<00:23:32.080> insurance<00:23:32.960> for<00:23:33.159> instance<00:23:33.679> off<00:23:33.840> of 00:23:34.110 --> 00:23:34.120 align:start position:0% hey I need insurance for instance off of 00:23:34.120 --> 00:23:36.230 align:start position:0% hey I need insurance for instance off of my<00:23:34.480> for<00:23:34.640> my<00:23:34.799> search<00:23:35.120> engine<00:23:35.559> right<00:23:36.000> and<00:23:36.080> we 00:23:36.230 --> 00:23:36.240 align:start position:0% my for my search engine right and we 00:23:36.240 --> 00:23:38.510 align:start position:0% my for my search engine right and we still<00:23:36.559> do<00:23:36.799> a<00:23:36.919> lot<00:23:37.080> of<00:23:37.240> that<00:23:37.480> business<00:23:38.159> but 00:23:38.510 --> 00:23:38.520 align:start position:0% still do a lot of that business but 00:23:38.520 --> 00:23:40.990 align:start position:0% still do a lot of that business but what's<00:23:38.760> interesting<00:23:39.720> is<00:23:40.080> that<00:23:40.279> solar<00:23:40.679> doesn't 00:23:40.990 --> 00:23:41.000 align:start position:0% what's interesting is that solar doesn't 00:23:41.000 --> 00:23:43.510 align:start position:0% what's interesting is that solar doesn't break<00:23:41.880> and<00:23:42.039> so<00:23:42.400> people<00:23:42.600> are<00:23:42.760> like<00:23:43.000> hey<00:23:43.279> that's 00:23:43.510 --> 00:23:43.520 align:start position:0% break and so people are like hey that's 00:23:43.520 --> 00:23:46.350 align:start position:0% break and so people are like hey that's great<00:23:43.720> we<00:23:43.880> love<00:23:44.120> solar<00:23:44.720> but<00:23:44.919> you<00:23:45.120> know<00:23:46.120> come 00:23:46.350 --> 00:23:46.360 align:start position:0% great we love solar but you know come 00:23:46.360 --> 00:23:48.149 align:start position:0% great we love solar but you know come renewal<00:23:46.840> time<00:23:47.279> hey<00:23:47.440> I<00:23:47.520> already<00:23:47.679> know<00:23:47.880> and<00:23:48.000> it 00:23:48.149 --> 00:23:48.159 align:start position:0% renewal time hey I already know and it 00:23:48.159 --> 00:23:50.029 align:start position:0% renewal time hey I already know and it works<00:23:48.440> and<00:23:48.600> I<00:23:48.720> haven't<00:23:49.000> had<00:23:49.159> any<00:23:49.360> trouble<00:23:49.919> and 00:23:50.029 --> 00:23:50.039 align:start position:0% works and I haven't had any trouble and 00:23:50.039 --> 00:23:51.269 align:start position:0% works and I haven't had any trouble and so<00:23:50.159> one<00:23:50.279> of<00:23:50.360> the<00:23:50.520> interesting<00:23:50.880> things<00:23:51.080> that 00:23:51.269 --> 00:23:51.279 align:start position:0% so one of the interesting things that 00:23:51.279 --> 00:23:53.350 align:start position:0% so one of the interesting things that we've<00:23:51.559> evolved<00:23:51.960> into<00:23:52.320> is<00:23:52.520> like<00:23:52.640> you've<00:23:52.880> got<00:23:53.000> to 00:23:53.350 --> 00:23:53.360 align:start position:0% we've evolved into is like you've got to 00:23:53.360 --> 00:23:56.390 align:start position:0% we've evolved into is like you've got to have<00:23:54.279> uh<00:23:54.559> capabilities<00:23:55.279> on<00:23:55.640> top<00:23:55.840> of<00:23:56.039> that<00:23:56.200> so 00:23:56.390 --> 00:23:56.400 align:start position:0% have uh capabilities on top of that so 00:23:56.400 --> 00:23:59.190 align:start position:0% have uh capabilities on top of that so when<00:23:56.559> we<00:23:56.799> think<00:23:57.080> about<00:23:57.880> how<00:23:58.159> we<00:23:58.640> engage<00:23:59.039> with 00:23:59.190 --> 00:23:59.200 align:start position:0% when we think about how we engage with 00:23:59.200 --> 00:24:01.470 align:start position:0% when we think about how we engage with our<00:23:59.480> customers<00:24:00.000> we've<00:24:00.200> shifted<00:24:00.720> very<00:24:00.960> much<00:24:01.159> to 00:24:01.470 --> 00:24:01.480 align:start position:0% our customers we've shifted very much to 00:24:01.480 --> 00:24:03.430 align:start position:0% our customers we've shifted very much to what<00:24:01.600> we<00:24:01.799> call<00:24:01.960> a<00:24:02.120> customer<00:24:02.600> success<00:24:03.039> model 00:24:03.430 --> 00:24:03.440 align:start position:0% what we call a customer success model 00:24:03.440 --> 00:24:05.350 align:start position:0% what we call a customer success model which<00:24:03.600> is<00:24:04.400> hey<00:24:04.559> you<00:24:04.679> know<00:24:04.880> we're<00:24:05.039> going<00:24:05.120> to<00:24:05.240> be 00:24:05.350 --> 00:24:05.360 align:start position:0% which is hey you know we're going to be 00:24:05.360 --> 00:24:07.510 align:start position:0% which is hey you know we're going to be there<00:24:05.480> for<00:24:05.600> the<00:24:05.760> break<00:24:06.039> fix<00:24:06.480> that's<00:24:06.679> one<00:24:06.960> thing 00:24:07.510 --> 00:24:07.520 align:start position:0% there for the break fix that's one thing 00:24:07.520 --> 00:24:09.269 align:start position:0% there for the break fix that's one thing but<00:24:07.679> in<00:24:07.880> reality<00:24:08.360> what<00:24:08.559> customers<00:24:09.039> kept 00:24:09.269 --> 00:24:09.279 align:start position:0% but in reality what customers kept 00:24:09.279 --> 00:24:11.990 align:start position:0% but in reality what customers kept coming<00:24:09.559> to<00:24:09.760> us<00:24:10.000> for<00:24:10.240> is<00:24:10.480> help<00:24:10.679> me<00:24:11.360> understand 00:24:11.990 --> 00:24:12.000 align:start position:0% coming to us for is help me understand 00:24:12.000 --> 00:24:14.149 align:start position:0% coming to us for is help me understand the<00:24:12.559> difficult<00:24:12.919> problems<00:24:13.480> better<00:24:13.840> you<00:24:14.039> guys 00:24:14.149 --> 00:24:14.159 align:start position:0% the difficult problems better you guys 00:24:14.159 --> 00:24:16.510 align:start position:0% the difficult problems better you guys are<00:24:14.520> expert<00:24:15.320> experts<00:24:15.679> in<00:24:15.840> search<00:24:16.159> you<00:24:16.279> know 00:24:16.510 --> 00:24:16.520 align:start position:0% are expert experts in search you know 00:24:16.520 --> 00:24:18.190 align:start position:0% are expert experts in search you know machine<00:24:16.799> learning<00:24:17.200> you<00:24:17.360> KN<00:24:17.640> know<00:24:17.840> natural 00:24:18.190 --> 00:24:18.200 align:start position:0% machine learning you KN know natural 00:24:18.200 --> 00:24:20.510 align:start position:0% machine learning you KN know natural language<00:24:18.640> processing<00:24:19.480> help<00:24:19.720> me<00:24:19.880> with<00:24:20.159> product 00:24:20.510 --> 00:24:20.520 align:start position:0% language processing help me with product 00:24:20.520 --> 00:24:22.470 align:start position:0% language processing help me with product in<00:24:20.640> terms<00:24:20.880> of<00:24:21.080> tools<00:24:21.520> that<00:24:21.679> make<00:24:21.919> my<00:24:22.120> life 00:24:22.470 --> 00:24:22.480 align:start position:0% in terms of tools that make my life 00:24:22.480 --> 00:24:24.909 align:start position:0% in terms of tools that make my life easier<00:24:22.840> to<00:24:22.960> do<00:24:23.240> those<00:24:23.440> things<00:24:23.960> but<00:24:24.120> then<00:24:24.440> also 00:24:24.909 --> 00:24:24.919 align:start position:0% easier to do those things but then also 00:24:24.919 --> 00:24:27.029 align:start position:0% easier to do those things but then also hey<00:24:25.399> how<00:24:25.520> do<00:24:25.679> I<00:24:25.880> make<00:24:26.120> this<00:24:26.360> better<00:24:26.679> how<00:24:26.799> do<00:24:26.919> I 00:24:27.029 --> 00:24:27.039 align:start position:0% hey how do I make this better how do I 00:24:27.039 --> 00:24:28.909 align:start position:0% hey how do I make this better how do I have<00:24:27.240> better<00:24:27.600> relevance<00:24:28.039> for 00:24:28.909 --> 00:24:28.919 align:start position:0% have better relevance for 00:24:28.919 --> 00:24:31.029 align:start position:0% have better relevance for how<00:24:29.039> do<00:24:29.200> I<00:24:29.399> scale<00:24:29.880> this<00:24:30.120> how<00:24:30.240> do<00:24:30.360> I<00:24:30.520> grow<00:24:30.840> with 00:24:31.029 --> 00:24:31.039 align:start position:0% how do I scale this how do I grow with 00:24:31.039 --> 00:24:32.830 align:start position:0% how do I scale this how do I grow with my<00:24:31.240> business<00:24:31.799> how<00:24:31.919> do<00:24:32.080> I<00:24:32.279> ask<00:24:32.520> more 00:24:32.830 --> 00:24:32.840 align:start position:0% my business how do I ask more 00:24:32.840 --> 00:24:35.590 align:start position:0% my business how do I ask more interesting<00:24:33.520> questions<00:24:34.120> of<00:24:34.399> my<00:24:34.640> data<00:24:35.200> and<00:24:35.320> so 00:24:35.590 --> 00:24:35.600 align:start position:0% interesting questions of my data and so 00:24:35.600 --> 00:24:38.070 align:start position:0% interesting questions of my data and so it<00:24:35.880> it<00:24:36.480> what<00:24:36.679> the<00:24:36.880> customer<00:24:37.360> success<00:24:37.760> model 00:24:38.070 --> 00:24:38.080 align:start position:0% it it what the customer success model 00:24:38.080 --> 00:24:39.830 align:start position:0% it it what the customer success model that<00:24:38.159> we've<00:24:38.360> put<00:24:38.520> in<00:24:38.720> place<00:24:39.360> you<00:24:39.480> know<00:24:39.640> like<00:24:39.760> I 00:24:39.830 --> 00:24:39.840 align:start position:0% that we've put in place you know like I 00:24:39.840 --> 00:24:41.669 align:start position:0% that we've put in place you know like I said<00:24:40.080> obviously<00:24:40.440> has<00:24:40.600> The<00:24:40.720> Brak<00:24:40.960> fixed<00:24:41.320> but<00:24:41.440> is 00:24:41.669 --> 00:24:41.679 align:start position:0% said obviously has The Brak fixed but is 00:24:41.679 --> 00:24:44.630 align:start position:0% said obviously has The Brak fixed but is also<00:24:42.000> really<00:24:42.399> geared<00:24:42.919> towards<00:24:43.880> making<00:24:44.240> sure 00:24:44.630 --> 00:24:44.640 align:start position:0% also really geared towards making sure 00:24:44.640 --> 00:24:46.830 align:start position:0% also really geared towards making sure customers<00:24:45.159> can<00:24:45.360> grow<00:24:45.640> and<00:24:45.799> be<00:24:46.120> successful 00:24:46.830 --> 00:24:46.840 align:start position:0% customers can grow and be successful 00:24:46.840 --> 00:24:49.470 align:start position:0% customers can grow and be successful together<00:24:47.159> with<00:24:47.320> us<00:24:47.640> so<00:24:48.080> you<00:24:48.200> know<00:24:48.799> open<00:24:49.159> source 00:24:49.470 --> 00:24:49.480 align:start position:0% together with us so you know open source 00:24:49.480 --> 00:24:52.430 align:start position:0% together with us so you know open source is<00:24:49.720> one<00:24:50.120> part<00:24:50.320> of<00:24:50.520> the<00:24:50.760> business<00:24:51.679> decision<00:24:52.200> is 00:24:52.430 --> 00:24:52.440 align:start position:0% is one part of the business decision is 00:24:52.440 --> 00:24:54.990 align:start position:0% is one part of the business decision is should<00:24:52.640> I<00:24:52.840> put<00:24:53.039> my<00:24:53.360> technology<00:24:54.360> out<00:24:54.600> in<00:24:54.799> the 00:24:54.990 --> 00:24:55.000 align:start position:0% should I put my technology out in the 00:24:55.000 --> 00:24:56.630 align:start position:0% should I put my technology out in the open<00:24:55.360> and<00:24:55.600> and<00:24:55.760> you<00:24:55.880> know<00:24:56.039> everybody's<00:24:56.520> going 00:24:56.630 --> 00:24:56.640 align:start position:0% open and and you know everybody's going 00:24:56.640 --> 00:24:59.070 align:start position:0% open and and you know everybody's going to<00:24:56.760> be<00:24:57.000> different<00:24:57.440> there<00:24:58.120> uh<00:24:58.480> but<00:24:58.600> you<00:24:58.679> know<00:24:59.000> I 00:24:59.070 --> 00:24:59.080 align:start position:0% to be different there uh but you know I 00:24:59.080 --> 00:25:01.789 align:start position:0% to be different there uh but you know I think<00:24:59.279> one<00:24:59.399> of<00:24:59.520> the<00:24:59.679> things<00:25:00.159> that<00:25:01.080> you<00:25:01.320> have<00:25:01.440> to 00:25:01.789 --> 00:25:01.799 align:start position:0% think one of the things that you have to 00:25:01.799 --> 00:25:03.830 align:start position:0% think one of the things that you have to think<00:25:02.039> about<00:25:02.399> is<00:25:02.880> you<00:25:03.000> know<00:25:03.279> is<00:25:03.520> this 00:25:03.830 --> 00:25:03.840 align:start position:0% think about is you know is this 00:25:03.840 --> 00:25:05.549 align:start position:0% think about is you know is this technology<00:25:04.600> something<00:25:04.880> that<00:25:05.080> has<00:25:05.200> a<00:25:05.360> big 00:25:05.549 --> 00:25:05.559 align:start position:0% technology something that has a big 00:25:05.559 --> 00:25:07.269 align:start position:0% technology something that has a big enough<00:25:05.840> base<00:25:06.120> that<00:25:06.279> I<00:25:06.399> can<00:25:06.600> actually<00:25:06.799> build<00:25:07.080> a 00:25:07.269 --> 00:25:07.279 align:start position:0% enough base that I can actually build a 00:25:07.279 --> 00:25:09.029 align:start position:0% enough base that I can actually build a company<00:25:07.640> around<00:25:08.120> obviously<00:25:08.720> you<00:25:08.799> know<00:25:08.919> it's 00:25:09.029 --> 00:25:09.039 align:start position:0% company around obviously you know it's 00:25:09.039 --> 00:25:10.590 align:start position:0% company around obviously you know it's got<00:25:09.159> to<00:25:09.279> be<00:25:09.399> more<00:25:09.640> than<00:25:09.840> just<00:25:10.000> your<00:25:10.279> pet 00:25:10.590 --> 00:25:10.600 align:start position:0% got to be more than just your pet 00:25:10.600 --> 00:25:12.470 align:start position:0% got to be more than just your pet project<00:25:11.000> or<00:25:11.240> you<00:25:11.399> and<00:25:11.520> your<00:25:11.640> buddy's<00:25:12.159> pet 00:25:12.470 --> 00:25:12.480 align:start position:0% project or you and your buddy's pet 00:25:12.480 --> 00:25:14.710 align:start position:0% project or you and your buddy's pet project<00:25:13.399> uh<00:25:13.520> and<00:25:13.640> it's<00:25:13.799> not<00:25:14.000> enough<00:25:14.360> just<00:25:14.559> just 00:25:14.710 --> 00:25:14.720 align:start position:0% project uh and it's not enough just just 00:25:14.720 --> 00:25:16.950 align:start position:0% project uh and it's not enough just just show<00:25:14.960> up<00:25:15.159> and<00:25:15.279> say<00:25:15.679> okay<00:25:15.919> well<00:25:16.120> hey<00:25:16.320> I've<00:25:16.520> got 00:25:16.950 --> 00:25:16.960 align:start position:0% show up and say okay well hey I've got 00:25:16.960 --> 00:25:18.389 align:start position:0% show up and say okay well hey I've got uh<00:25:17.200> you<00:25:17.320> know<00:25:17.440> kind<00:25:17.520> of<00:25:17.640> Open<00:25:17.880> Source<00:25:18.159> kind<00:25:18.240> of 00:25:18.389 --> 00:25:18.399 align:start position:0% uh you know kind of Open Source kind of 00:25:18.399 --> 00:25:19.909 align:start position:0% uh you know kind of Open Source kind of goes<00:25:18.600> through<00:25:18.799> these<00:25:19.000> phases<00:25:19.480> of<00:25:19.679> you<00:25:19.760> know 00:25:19.909 --> 00:25:19.919 align:start position:0% goes through these phases of you know 00:25:19.919 --> 00:25:21.950 align:start position:0% goes through these phases of you know it's<00:25:20.080> a<00:25:20.200> couple<00:25:20.440> of<00:25:20.760> guys<00:25:21.080> or<00:25:21.399> or<00:25:21.559> a<00:25:21.640> couple<00:25:21.840> of 00:25:21.950 --> 00:25:21.960 align:start position:0% it's a couple of guys or or a couple of 00:25:21.960 --> 00:25:24.190 align:start position:0% it's a couple of guys or or a couple of people<00:25:22.440> together<00:25:22.760> working<00:25:23.200> on<00:25:23.880> something 00:25:24.190 --> 00:25:24.200 align:start position:0% people together working on something 00:25:24.200 --> 00:25:25.909 align:start position:0% people together working on something that's<00:25:24.399> of<00:25:24.600> interesting<00:25:25.200> to<00:25:25.440> interest<00:25:25.720> to 00:25:25.909 --> 00:25:25.919 align:start position:0% that's of interesting to interest to 00:25:25.919 --> 00:25:28.029 align:start position:0% that's of interesting to interest to them<00:25:26.120> and<00:25:26.240> then<00:25:26.360> it<00:25:26.600> usually<00:25:26.919> evolves<00:25:27.480> to 00:25:28.029 --> 00:25:28.039 align:start position:0% them and then it usually evolves to 00:25:28.039 --> 00:25:29.750 align:start position:0% them and then it usually evolves to where<00:25:28.440> you<00:25:28.520> can<00:25:28.760> kind<00:25:28.919> of<00:25:29.159> support<00:25:29.520> an 00:25:29.750 --> 00:25:29.760 align:start position:0% where you can kind of support an 00:25:29.760 --> 00:25:32.789 align:start position:0% where you can kind of support an ecosystem<00:25:30.520> of<00:25:30.880> one-off<00:25:31.440> Consultants<00:25:32.039> who<00:25:32.240> can 00:25:32.789 --> 00:25:32.799 align:start position:0% ecosystem of one-off Consultants who can 00:25:32.799 --> 00:25:34.350 align:start position:0% ecosystem of one-off Consultants who can come<00:25:32.960> and<00:25:33.120> say<00:25:33.399> hey<00:25:33.600> I<00:25:33.679> can<00:25:33.880> help<00:25:34.039> you<00:25:34.200> with 00:25:34.350 --> 00:25:34.360 align:start position:0% come and say hey I can help you with 00:25:34.360 --> 00:25:36.269 align:start position:0% come and say hey I can help you with your<00:25:34.480> hard<00:25:34.919> problem<00:25:35.600> and<00:25:35.720> then<00:25:35.840> you<00:25:35.960> know<00:25:36.080> it 00:25:36.269 --> 00:25:36.279 align:start position:0% your hard problem and then you know it 00:25:36.279 --> 00:25:38.070 align:start position:0% your hard problem and then you know it gets<00:25:36.440> to<00:25:36.640> the<00:25:36.760> likes<00:25:37.080> of<00:25:37.240> the<00:25:37.480> dupes<00:25:37.840> and<00:25:37.960> the 00:25:38.070 --> 00:25:38.080 align:start position:0% gets to the likes of the dupes and the 00:25:38.080 --> 00:25:41.950 align:start position:0% gets to the likes of the dupes and the Sparks<00:25:38.640> and<00:25:38.919> the<00:25:39.240> the<00:25:39.480> solar<00:25:40.200> Etc<00:25:40.840> where<00:25:41.760> you 00:25:41.950 --> 00:25:41.960 align:start position:0% Sparks and the the solar Etc where you 00:25:41.960 --> 00:25:44.789 align:start position:0% Sparks and the the solar Etc where you can<00:25:42.240> sustain<00:25:43.080> multiple<00:25:43.720> businesses<00:25:44.399> around 00:25:44.789 --> 00:25:44.799 align:start position:0% can sustain multiple businesses around 00:25:44.799 --> 00:25:47.149 align:start position:0% can sustain multiple businesses around it<00:25:45.240> and<00:25:45.520> you<00:25:45.640> know<00:25:46.120> and<00:25:46.559> and<00:25:46.760> they<00:25:46.919> all 00:25:47.149 --> 00:25:47.159 align:start position:0% it and you know and and they all 00:25:47.159 --> 00:25:49.389 align:start position:0% it and you know and and they all contribute<00:25:47.720> back<00:25:47.880> to<00:25:48.080> the<00:25:48.240> core<00:25:48.840> but<00:25:49.000> they<00:25:49.120> all 00:25:49.389 --> 00:25:49.399 align:start position:0% contribute back to the core but they all 00:25:49.399 --> 00:25:51.230 align:start position:0% contribute back to the core but they all have<00:25:49.799> you<00:25:49.919> know<00:25:50.080> presumably<00:25:50.559> their<00:25:50.760> unique 00:25:51.230 --> 00:25:51.240 align:start position:0% have you know presumably their unique 00:25:51.240 --> 00:25:53.310 align:start position:0% have you know presumably their unique differentiator<00:25:52.039> and<00:25:52.200> I<00:25:52.360> think<00:25:52.919> you<00:25:53.039> know 00:25:53.310 --> 00:25:53.320 align:start position:0% differentiator and I think you know 00:25:53.320 --> 00:25:55.430 align:start position:0% differentiator and I think you know depending<00:25:53.720> on<00:25:54.120> where<00:25:54.399> that<00:25:54.720> project<00:25:55.120> is<00:25:55.279> and 00:25:55.430 --> 00:25:55.440 align:start position:0% depending on where that project is and 00:25:55.440 --> 00:25:57.710 align:start position:0% depending on where that project is and its<00:25:55.679> lifespan<00:25:56.320> will<00:25:56.640> determine<00:25:57.240> how<00:25:57.399> you<00:25:57.520> can 00:25:57.710 --> 00:25:57.720 align:start position:0% its lifespan will determine how you can 00:25:57.720 --> 00:26:00.750 align:start position:0% its lifespan will determine how you can go<00:25:57.919> about<00:25:58.600> uh<00:25:59.279> commercializing<00:26:00.279> uh<00:26:00.440> open- 00:26:00.750 --> 00:26:00.760 align:start position:0% go about uh commercializing uh open- 00:26:00.760 --> 00:26:03.350 align:start position:0% go about uh commercializing uh open- Source<00:26:01.600> technology<00:26:02.600> um<00:26:02.799> you<00:26:02.880> know<00:26:03.080> the<00:26:03.200> other 00:26:03.350 --> 00:26:03.360 align:start position:0% Source technology um you know the other 00:26:03.360 --> 00:26:04.830 align:start position:0% Source technology um you know the other thing<00:26:03.520> is<00:26:03.760> like<00:26:03.919> you<00:26:04.000> know<00:26:04.120> you<00:26:04.279> just<00:26:04.520> always 00:26:04.830 --> 00:26:04.840 align:start position:0% thing is like you know you just always 00:26:04.840 --> 00:26:06.630 align:start position:0% thing is like you know you just always have<00:26:04.960> to<00:26:05.200> keep<00:26:05.480> investing<00:26:06.000> in<00:26:06.279> the<00:26:06.399> open 00:26:06.630 --> 00:26:06.640 align:start position:0% have to keep investing in the open 00:26:06.640 --> 00:26:07.909 align:start position:0% have to keep investing in the open source<00:26:06.880> and<00:26:07.000> there's<00:26:07.200> always<00:26:07.399> this<00:26:07.679> kind<00:26:07.760> of 00:26:07.909 --> 00:26:07.919 align:start position:0% source and there's always this kind of 00:26:07.919 --> 00:26:10.029 align:start position:0% source and there's always this kind of delicate<00:26:08.480> Balancing<00:26:09.039> Act<00:26:09.320> of<00:26:09.720> you<00:26:09.840> know<00:26:09.960> at 00:26:10.029 --> 00:26:10.039 align:start position:0% delicate Balancing Act of you know at 00:26:10.039 --> 00:26:11.710 align:start position:0% delicate Balancing Act of you know at the<00:26:10.120> end<00:26:10.240> of<00:26:10.320> the<00:26:10.440> day<00:26:10.640> you<00:26:10.840> have<00:26:10.960> to<00:26:11.240> you<00:26:11.360> know 00:26:11.710 --> 00:26:11.720 align:start position:0% the end of the day you have to you know 00:26:11.720 --> 00:26:13.710 align:start position:0% the end of the day you have to you know quote<00:26:11.960> unquote<00:26:12.399> put<00:26:12.520> food<00:26:12.760> on<00:26:12.919> the<00:26:13.120> table<00:26:13.559> you 00:26:13.710 --> 00:26:13.720 align:start position:0% quote unquote put food on the table you 00:26:13.720 --> 00:26:15.470 align:start position:0% quote unquote put food on the table you have<00:26:13.840> to<00:26:13.960> pay<00:26:14.279> salaries<00:26:14.720> you<00:26:14.880> got<00:26:15.000> to<00:26:15.159> keep<00:26:15.320> the 00:26:15.470 --> 00:26:15.480 align:start position:0% have to pay salaries you got to keep the 00:26:15.480 --> 00:26:17.909 align:start position:0% have to pay salaries you got to keep the lights<00:26:15.760> on<00:26:16.080> Etc<00:26:16.600> so<00:26:17.080> there's<00:26:17.360> something<00:26:17.760> that 00:26:17.909 --> 00:26:17.919 align:start position:0% lights on Etc so there's something that 00:26:17.919 --> 00:26:21.149 align:start position:0% lights on Etc so there's something that you<00:26:18.240> have<00:26:18.399> to<00:26:19.240> be<00:26:20.120> uh<00:26:20.440> you<00:26:20.520> know<00:26:20.720> that<00:26:20.840> you<00:26:21.039> have 00:26:21.149 --> 00:26:21.159 align:start position:0% you have to be uh you know that you have 00:26:21.159 --> 00:26:23.430 align:start position:0% you have to be uh you know that you have to<00:26:21.320> be<00:26:21.480> able<00:26:21.679> to<00:26:21.880> monetize<00:26:22.799> but<00:26:22.919> at<00:26:23.039> the<00:26:23.200> same 00:26:23.430 --> 00:26:23.440 align:start position:0% to be able to monetize but at the same 00:26:23.440 --> 00:26:25.269 align:start position:0% to be able to monetize but at the same time<00:26:23.600> you<00:26:23.720> know<00:26:23.840> the<00:26:24.000> community<00:26:24.559> pressure<00:26:24.919> is 00:26:25.269 --> 00:26:25.279 align:start position:0% time you know the community pressure is 00:26:25.279 --> 00:26:28.029 align:start position:0% time you know the community pressure is often<00:26:26.159> how<00:26:26.320> do<00:26:26.640> I<00:26:27.120> you<00:26:27.240> know<00:26:27.399> I<00:26:27.480> want<00:26:27.760> all<00:26:27.880> of 00:26:28.029 --> 00:26:28.039 align:start position:0% often how do I you know I want all of 00:26:28.039 --> 00:26:29.830 align:start position:0% often how do I you know I want all of this<00:26:28.399> for<00:26:28.559> free<00:26:28.840> they<00:26:28.960> want<00:26:29.159> your<00:26:29.399> time<00:26:29.640> for 00:26:29.830 --> 00:26:29.840 align:start position:0% this for free they want your time for 00:26:29.840 --> 00:26:32.269 align:start position:0% this for free they want your time for free<00:26:30.200> they<00:26:30.279> want<00:26:30.440> your<00:26:30.679> code<00:26:30.919> for<00:26:31.120> free<00:26:31.399> Etc<00:26:32.039> so 00:26:32.269 --> 00:26:32.279 align:start position:0% free they want your code for free Etc so 00:26:32.279 --> 00:26:34.750 align:start position:0% free they want your code for free Etc so like<00:26:32.440> you<00:26:32.640> have<00:26:32.760> to<00:26:33.320> kind<00:26:33.440> of<00:26:34.000> work<00:26:34.480> together 00:26:34.750 --> 00:26:34.760 align:start position:0% like you have to kind of work together 00:26:34.760 --> 00:26:37.470 align:start position:0% like you have to kind of work together to<00:26:34.919> come<00:26:35.080> up<00:26:35.279> with<00:26:35.399> a<00:26:35.559> win-win<00:26:36.159> situation<00:26:37.000> for 00:26:37.470 --> 00:26:37.480 align:start position:0% to come up with a win-win situation for 00:26:37.480 --> 00:26:39.110 align:start position:0% to come up with a win-win situation for everybody<00:26:38.039> such<00:26:38.279> that<00:26:38.440> the<00:26:38.559> community<00:26:38.960> is 00:26:39.110 --> 00:26:39.120 align:start position:0% everybody such that the community is 00:26:39.120 --> 00:26:41.149 align:start position:0% everybody such that the community is benefiting<00:26:39.799> as<00:26:39.960> well<00:26:40.159> as<00:26:40.640> you<00:26:40.760> know<00:26:40.919> you're 00:26:41.149 --> 00:26:41.159 align:start position:0% benefiting as well as you know you're 00:26:41.159 --> 00:26:43.909 align:start position:0% benefiting as well as you know you're able<00:26:41.520> to<00:26:42.159> uh<00:26:42.480> to<00:26:42.679> pay<00:26:42.919> salaries<00:26:43.360> and<00:26:43.520> all<00:26:43.760> that 00:26:43.909 --> 00:26:43.919 align:start position:0% able to uh to pay salaries and all that 00:26:43.919 --> 00:26:45.830 align:start position:0% able to uh to pay salaries and all that kind<00:26:44.440> good<00:26:44.600> balance<00:26:44.960> between<00:26:45.240> contributions 00:26:45.830 --> 00:26:45.840 align:start position:0% kind good balance between contributions 00:26:45.840 --> 00:26:47.230 align:start position:0% kind good balance between contributions from<00:26:46.039> the<00:26:46.159> outside<00:26:46.559> community<00:26:46.919> and<00:26:47.039> the 00:26:47.230 --> 00:26:47.240 align:start position:0% from the outside community and the 00:26:47.240 --> 00:26:49.430 align:start position:0% from the outside community and the company<00:26:47.799> employees<00:26:48.480> and<00:26:48.559> so<00:26:48.760> like<00:26:48.919> for<00:26:49.159> us<00:26:49.360> you 00:26:49.430 --> 00:26:49.440 align:start position:0% company employees and so like for us you 00:26:49.440 --> 00:26:51.950 align:start position:0% company employees and so like for us you know<00:26:49.600> as<00:26:49.720> a<00:26:49.840> company<00:26:50.200> we<00:26:50.360> look<00:26:50.520> at<00:26:50.840> how<00:26:51.679> uh<00:26:51.840> we 00:26:51.950 --> 00:26:51.960 align:start position:0% know as a company we look at how uh we 00:26:51.960 --> 00:26:54.230 align:start position:0% know as a company we look at how uh we can<00:26:52.320> complement<00:26:52.760> and<00:26:52.960> extend<00:26:53.399> solar<00:26:53.799> we<00:26:53.919> still 00:26:54.230 --> 00:26:54.240 align:start position:0% can complement and extend solar we still 00:26:54.240 --> 00:26:56.669 align:start position:0% can complement and extend solar we still invest<00:26:54.600> a<00:26:54.840> lot<00:26:55.080> in<00:26:55.360> core<00:26:55.679> solar<00:26:56.200> I<00:26:56.279> think<00:26:56.399> we're 00:26:56.669 --> 00:26:56.679 align:start position:0% invest a lot in core solar I think we're 00:26:56.679 --> 00:26:58.710 align:start position:0% invest a lot in core solar I think we're the<00:26:56.919> single<00:26:57.279> largest<00:26:57.679> contributor<00:26:58.360> or<00:26:58.440> two 00:26:58.710 --> 00:26:58.720 align:start position:0% the single largest contributor or two 00:26:58.720 --> 00:27:01.230 align:start position:0% the single largest contributor or two solar<00:26:59.080> in<00:26:59.240> the<00:26:59.600> community<00:27:00.600> uh<00:27:00.799> but<00:27:00.919> then<00:27:01.080> we 00:27:01.230 --> 00:27:01.240 align:start position:0% solar in the community uh but then we 00:27:01.240 --> 00:27:03.149 align:start position:0% solar in the community uh but then we also<00:27:01.520> look<00:27:01.720> at<00:27:01.919> from<00:27:02.039> a<00:27:02.279> product<00:27:02.640> standpoint 00:27:03.149 --> 00:27:03.159 align:start position:0% also look at from a product standpoint 00:27:03.159 --> 00:27:07.470 align:start position:0% also look at from a product standpoint is<00:27:03.679> what<00:27:03.919> things<00:27:04.600> do<00:27:05.360> we<00:27:05.559> know<00:27:05.919> customers<00:27:06.600> want 00:27:07.470 --> 00:27:07.480 align:start position:0% is what things do we know customers want 00:27:07.480 --> 00:27:09.750 align:start position:0% is what things do we know customers want that<00:27:07.720> the<00:27:07.919> community<00:27:08.520> doesn't<00:27:08.919> do<00:27:09.360> so<00:27:09.559> for 00:27:09.750 --> 00:27:09.760 align:start position:0% that the community doesn't do so for 00:27:09.760 --> 00:27:11.590 align:start position:0% that the community doesn't do so for instance<00:27:10.120> you<00:27:10.240> know<00:27:10.360> solar<00:27:10.799> itself<00:27:11.200> doesn't 00:27:11.590 --> 00:27:11.600 align:start position:0% instance you know solar itself doesn't 00:27:11.600 --> 00:27:14.830 align:start position:0% instance you know solar itself doesn't do<00:27:12.039> connectors<00:27:12.760> to<00:27:13.640> you<00:27:13.760> know<00:27:13.919> crawl<00:27:14.279> the<00:27:14.440> web 00:27:14.830 --> 00:27:14.840 align:start position:0% do connectors to you know crawl the web 00:27:14.840 --> 00:27:17.510 align:start position:0% do connectors to you know crawl the web or<00:27:15.320> connect<00:27:15.640> to<00:27:15.840> Twitter<00:27:16.480> or<00:27:17.240> you<00:27:17.360> know 00:27:17.510 --> 00:27:17.520 align:start position:0% or connect to Twitter or you know 00:27:17.520 --> 00:27:20.110 align:start position:0% or connect to Twitter or you know SharePoint<00:27:18.279> or<00:27:18.799> whatever<00:27:19.240> file<00:27:19.640> system 00:27:20.110 --> 00:27:20.120 align:start position:0% SharePoint or whatever file system 00:27:20.120 --> 00:27:22.350 align:start position:0% SharePoint or whatever file system repository<00:27:21.000> there<00:27:21.159> is<00:27:21.320> out<00:27:21.520> there<00:27:21.720> so<00:27:22.200> that's 00:27:22.350 --> 00:27:22.360 align:start position:0% repository there is out there so that's 00:27:22.360 --> 00:27:25.029 align:start position:0% repository there is out there so that's a<00:27:22.760> gap<00:27:23.000> that<00:27:23.159> we<00:27:23.320> fill<00:27:23.720> as<00:27:23.799> a<00:27:24.000> company<00:27:24.520> right<00:27:24.799> or 00:27:25.029 --> 00:27:25.039 align:start position:0% a gap that we fill as a company right or 00:27:25.039 --> 00:27:27.470 align:start position:0% a gap that we fill as a company right or solar<00:27:25.440> is<00:27:25.679> primarily<00:27:26.120> made<00:27:26.320> up<00:27:26.480> of<00:27:26.679> developers 00:27:27.470 --> 00:27:27.480 align:start position:0% solar is primarily made up of developers 00:27:27.480 --> 00:27:29.710 align:start position:0% solar is primarily made up of developers who<00:27:27.640> are<00:27:27.799> Focus<00:27:28.399> on<00:27:28.520> the<00:27:28.720> back<00:27:28.919> end<00:27:29.320> you<00:27:29.440> know 00:27:29.710 --> 00:27:29.720 align:start position:0% who are Focus on the back end you know 00:27:29.720 --> 00:27:32.070 align:start position:0% who are Focus on the back end you know algorithms<00:27:30.399> and<00:27:30.960> and<00:27:31.200> core<00:27:31.600> search 00:27:32.070 --> 00:27:32.080 align:start position:0% algorithms and and core search 00:27:32.080 --> 00:27:34.230 align:start position:0% algorithms and and core search functionality<00:27:32.799> they<00:27:32.919> don't<00:27:33.200> really<00:27:33.919> care 00:27:34.230 --> 00:27:34.240 align:start position:0% functionality they don't really care 00:27:34.240 --> 00:27:37.070 align:start position:0% functionality they don't really care about<00:27:34.559> search<00:27:34.919> UI<00:27:35.480> so<00:27:35.760> we<00:27:36.039> come<00:27:36.279> in<00:27:36.399> and<00:27:36.600> bring 00:27:37.070 --> 00:27:37.080 align:start position:0% about search UI so we come in and bring 00:27:37.080 --> 00:27:39.909 align:start position:0% about search UI so we come in and bring user<00:27:37.440> interfaces<00:27:38.200> to<00:27:38.919> the<00:27:39.120> customers<00:27:39.720> that 00:27:39.909 --> 00:27:39.919 align:start position:0% user interfaces to the customers that 00:27:39.919 --> 00:27:42.389 align:start position:0% user interfaces to the customers that allow<00:27:40.320> them<00:27:40.480> to<00:27:40.720> work<00:27:41.039> with<00:27:41.240> Solar<00:27:42.080> without 00:27:42.389 --> 00:27:42.399 align:start position:0% allow them to work with Solar without 00:27:42.399 --> 00:27:44.669 align:start position:0% allow them to work with Solar without having<00:27:42.640> to<00:27:42.880> necessarily<00:27:43.480> write<00:27:43.840> Java<00:27:44.399> code 00:27:44.669 --> 00:27:44.679 align:start position:0% having to necessarily write Java code 00:27:44.679 --> 00:27:46.710 align:start position:0% having to necessarily write Java code right<00:27:45.080> they<00:27:45.279> probably<00:27:45.519> care<00:27:45.760> about<00:27:46.080> the<00:27:46.240> U<00:27:46.600> but 00:27:46.710 --> 00:27:46.720 align:start position:0% right they probably care about the U but 00:27:46.720 --> 00:27:48.630 align:start position:0% right they probably care about the U but not<00:27:46.840> about<00:27:47.039> building<00:27:47.360> the<00:27:47.480> US<00:27:47.880> exactly<00:27:48.559> and 00:27:48.630 --> 00:27:48.640 align:start position:0% not about building the US exactly and 00:27:48.640 --> 00:27:50.590 align:start position:0% not about building the US exactly and then<00:27:48.799> we<00:27:49.039> you<00:27:49.120> know<00:27:49.320> like<00:27:49.640> and<00:27:49.760> then<00:27:50.000> like<00:27:50.320> the 00:27:50.590 --> 00:27:50.600 align:start position:0% then we you know like and then like the 00:27:50.600 --> 00:27:52.549 align:start position:0% then we you know like and then like the the<00:27:50.720> other<00:27:51.000> part<00:27:51.159> of<00:27:51.360> how<00:27:51.519> we<00:27:51.640> are<00:27:51.880> with<00:27:52.159> solar 00:27:52.549 --> 00:27:52.559 align:start position:0% the other part of how we are with solar 00:27:52.559 --> 00:27:54.990 align:start position:0% the other part of how we are with solar really<00:27:52.799> is<00:27:53.360> how<00:27:53.480> do<00:27:53.600> we<00:27:53.840> ask<00:27:54.120> more<00:27:54.399> interesting 00:27:54.990 --> 00:27:55.000 align:start position:0% really is how do we ask more interesting 00:27:55.000 --> 00:27:57.070 align:start position:0% really is how do we ask more interesting questions<00:27:55.600> of<00:27:55.760> solar<00:27:56.159> so<00:27:56.399> we<00:27:56.519> want<00:27:56.640> to<00:27:56.799> drive 00:27:57.070 --> 00:27:57.080 align:start position:0% questions of solar so we want to drive 00:27:57.080 --> 00:27:58.669 align:start position:0% questions of solar so we want to drive more<00:27:57.360> data<00:27:57.600> into<00:27:57.880> solar 00:27:58.669 --> 00:27:58.679 align:start position:0% more data into solar 00:27:58.679 --> 00:28:00.509 align:start position:0% more data into solar such<00:27:58.880> that<00:27:59.039> we<00:27:59.159> can<00:27:59.399> ask<00:27:59.640> more<00:27:59.880> interesting 00:28:00.509 --> 00:28:00.519 align:start position:0% such that we can ask more interesting 00:28:00.519 --> 00:28:02.190 align:start position:0% such that we can ask more interesting questions<00:28:00.960> of<00:28:01.120> it<00:28:01.320> so<00:28:01.559> again<00:28:01.720> it's<00:28:01.919> kind<00:28:02.039> of 00:28:02.190 --> 00:28:02.200 align:start position:0% questions of it so again it's kind of 00:28:02.200 --> 00:28:05.190 align:start position:0% questions of it so again it's kind of that<00:28:02.440> complement<00:28:02.880> and<00:28:03.039> extend<00:28:04.039> model<00:28:04.519> of<00:28:04.799> Open 00:28:05.190 --> 00:28:05.200 align:start position:0% that complement and extend model of Open 00:28:05.200 --> 00:28:08.110 align:start position:0% that complement and extend model of Open Source<00:28:05.559> if<00:28:05.679> you<00:28:05.840> will<00:28:06.480> that<00:28:06.679> I<00:28:06.840> think<00:28:07.480> uh<00:28:08.000> you 00:28:08.110 --> 00:28:08.120 align:start position:0% Source if you will that I think uh you 00:28:08.120 --> 00:28:10.470 align:start position:0% Source if you will that I think uh you know<00:28:08.679> has<00:28:08.840> worked<00:28:09.159> well<00:28:09.360> for<00:28:09.600> us<00:28:09.919> and<00:28:10.200> and<00:28:10.360> you 00:28:10.470 --> 00:28:10.480 align:start position:0% know has worked well for us and and you 00:28:10.480 --> 00:28:12.430 align:start position:0% know has worked well for us and and you know<00:28:10.600> we're<00:28:10.799> continuing<00:28:11.279> to<00:28:11.480> invest<00:28:11.840> a<00:28:12.000> lot<00:28:12.240> in 00:28:12.430 --> 00:28:12.440 align:start position:0% know we're continuing to invest a lot in 00:28:12.440 --> 00:28:14.630 align:start position:0% know we're continuing to invest a lot in in<00:28:12.640> that<00:28:12.840> way<00:28:13.000> of<00:28:13.159> doing<00:28:13.559> things<00:28:14.200> oh<00:28:14.360> that's 00:28:14.630 --> 00:28:14.640 align:start position:0% in that way of doing things oh that's 00:28:14.640 --> 00:28:18.159 align:start position:0% in that way of doing things oh that's great<00:28:15.000> I<00:28:15.159> think