WEBVTT
Kind: captions
Language: en

00:00:13.270 --> 00:00:16.330 align:start position:0%
 
quita<00:00:14.270><c> Broadwater</c><00:00:14.780><c> and</c><00:00:15.019><c> i'm</c><00:00:15.769><c> a</c><00:00:15.830><c> co-founder</c><00:00:16.010><c> of</c>

00:00:16.330 --> 00:00:16.340 align:start position:0%
quita Broadwater and i'm a co-founder of
 

00:00:16.340 --> 00:00:26.500 align:start position:0%
quita Broadwater and i'm a co-founder of
oxygen<00:00:16.939><c> AI</c><00:00:24.460><c> two</c><00:00:25.460><c> types</c><00:00:25.699><c> of</c><00:00:25.820><c> problems</c><00:00:26.150><c> I'd</c><00:00:26.300><c> say</c>

00:00:26.500 --> 00:00:26.510 align:start position:0%
oxygen AI two types of problems I'd say
 

00:00:26.510 --> 00:00:29.320 align:start position:0%
oxygen AI two types of problems I'd say
one<00:00:27.470><c> is</c><00:00:27.650><c> a</c><00:00:27.680><c> problem</c><00:00:28.340><c> I</c><00:00:28.400><c> think</c><00:00:28.460><c> every</c><00:00:28.940><c> data</c>

00:00:29.320 --> 00:00:29.330 align:start position:0%
one is a problem I think every data
 

00:00:29.330 --> 00:00:31.450 align:start position:0%
one is a problem I think every data
scientist<00:00:29.869><c> and</c><00:00:30.170><c> engineer</c><00:00:30.650><c> faces</c><00:00:31.039><c> it</c><00:00:31.190><c> which</c><00:00:31.310><c> is</c>

00:00:31.450 --> 00:00:31.460 align:start position:0%
scientist and engineer faces it which is
 

00:00:31.460 --> 00:00:34.630 align:start position:0%
scientist and engineer faces it which is
cleaning<00:00:32.119><c> data</c><00:00:32.359><c> having</c><00:00:33.260><c> good</c><00:00:33.350><c> input</c><00:00:33.559><c> data</c><00:00:33.920><c> for</c>

00:00:34.630 --> 00:00:34.640 align:start position:0%
cleaning data having good input data for
 

00:00:34.640 --> 00:00:37.619 align:start position:0%
cleaning data having good input data for
our<00:00:35.000><c> models</c><00:00:35.420><c> and</c><00:00:35.690><c> for</c><00:00:36.109><c> our</c><00:00:36.199><c> analyses</c>

00:00:37.619 --> 00:00:37.629 align:start position:0%
our models and for our analyses
 

00:00:37.629 --> 00:00:40.239 align:start position:0%
our models and for our analyses
sometimes<00:00:38.629><c> you</c><00:00:38.809><c> get</c><00:00:39.109><c> down</c><00:00:39.319><c> a</c><00:00:39.649><c> dead</c><00:00:39.890><c> end</c><00:00:40.069><c> you</c>

00:00:40.239 --> 00:00:40.249 align:start position:0%
sometimes you get down a dead end you
 

00:00:40.249 --> 00:00:44.099 align:start position:0%
sometimes you get down a dead end you
have<00:00:40.399><c> to</c><00:00:40.519><c> retrace</c><00:00:41.089><c> your</c><00:00:41.120><c> steps</c><00:00:41.949><c> the</c><00:00:42.949><c> other</c>

00:00:44.099 --> 00:00:44.109 align:start position:0%
have to retrace your steps the other
 

00:00:44.109 --> 00:00:46.840 align:start position:0%
have to retrace your steps the other
challenge<00:00:45.109><c> is</c><00:00:45.319><c> working</c><00:00:46.100><c> with</c><00:00:46.429><c> a</c><00:00:46.609><c> lot</c><00:00:46.819><c> of</c>

00:00:46.840 --> 00:00:46.850 align:start position:0%
challenge is working with a lot of
 

00:00:46.850 --> 00:00:50.950 align:start position:0%
challenge is working with a lot of
disparate<00:00:47.749><c> systems</c><00:00:48.440><c> and</c><00:00:48.949><c> tools</c><00:00:49.549><c> and</c><00:00:49.960><c> the</c>

00:00:50.950 --> 00:00:50.960 align:start position:0%
disparate systems and tools and the
 

00:00:50.960 --> 00:00:52.239 align:start position:0%
disparate systems and tools and the
project<00:00:51.350><c> that</c><00:00:51.440><c> I</c><00:00:51.499><c> spoke</c><00:00:51.739><c> about</c><00:00:52.010><c> at</c><00:00:52.159><c> the</c>

00:00:52.239 --> 00:00:52.249 align:start position:0%
project that I spoke about at the
 

00:00:52.249 --> 00:00:56.649 align:start position:0%
project that I spoke about at the
conference<00:00:52.479><c> I</c><00:00:53.479><c> had</c><00:00:54.469><c> to</c><00:00:54.709><c> patch</c><00:00:55.459><c> together</c><00:00:55.760><c> a</c><00:00:56.269><c> lot</c>

00:00:56.649 --> 00:00:56.659 align:start position:0%
conference I had to patch together a lot
 

00:00:56.659 --> 00:00:59.439 align:start position:0%
conference I had to patch together a lot
of<00:00:56.690><c> different</c><00:00:56.929><c> types</c><00:00:57.589><c> of</c><00:00:57.769><c> tools</c><00:00:58.239><c> having</c><00:00:59.239><c> to</c><00:00:59.329><c> do</c>

00:00:59.439 --> 00:00:59.449 align:start position:0%
of different types of tools having to do
 

00:00:59.449 --> 00:01:02.609 align:start position:0%
of different types of tools having to do
with<00:00:59.569><c> sensors</c><00:01:00.109><c> having</c><00:01:00.739><c> to</c><00:01:00.829><c> do</c><00:01:01.010><c> with</c><00:01:01.369><c> messaging</c>

00:01:02.609 --> 00:01:02.619 align:start position:0%
with sensors having to do with messaging
 

00:01:02.619 --> 00:01:07.360 align:start position:0%
with sensors having to do with messaging
systems<00:01:03.619><c> having</c><00:01:04.400><c> to</c><00:01:04.519><c> do</c><00:01:04.699><c> with</c><00:01:05.030><c> spark</c><00:01:06.020><c> and</c><00:01:06.950><c> the</c>

00:01:07.360 --> 00:01:07.370 align:start position:0%
systems having to do with spark and the
 

00:01:07.370 --> 00:01:11.190 align:start position:0%
systems having to do with spark and the
data<00:01:07.720><c> data</c><00:01:08.720><c> types</c><00:01:09.020><c> within</c><00:01:09.200><c> spark</c><00:01:09.680><c> so</c>

00:01:11.190 --> 00:01:11.200 align:start position:0%
data data types within spark so
 

00:01:11.200 --> 00:01:14.050 align:start position:0%
data data types within spark so
sometimes<00:01:12.200><c> piecing</c><00:01:13.190><c> them</c><00:01:13.460><c> together</c><00:01:13.580><c> and</c>

00:01:14.050 --> 00:01:14.060 align:start position:0%
sometimes piecing them together and
 

00:01:14.060 --> 00:01:16.390 align:start position:0%
sometimes piecing them together and
configuring<00:01:14.810><c> them</c><00:01:15.020><c> so</c><00:01:15.230><c> that</c><00:01:15.410><c> you</c><00:01:16.070><c> get</c><00:01:16.220><c> out</c>

00:01:16.390 --> 00:01:16.400 align:start position:0%
configuring them so that you get out
 

00:01:16.400 --> 00:01:21.830 align:start position:0%
configuring them so that you get out
what<00:01:16.580><c> you</c><00:01:16.700><c> really</c><00:01:16.910><c> want</c><00:01:17.240><c> is</c><00:01:18.170><c> a</c><00:01:18.560><c> big</c><00:01:18.800><c> challenge</c>

00:01:21.830 --> 00:01:21.840 align:start position:0%
 
 

00:01:21.840 --> 00:01:26.520 align:start position:0%
 
[Music]

00:01:26.520 --> 00:01:26.530 align:start position:0%
[Music]
 

00:01:26.530 --> 00:01:31.090 align:start position:0%
[Music]
problems<00:01:27.530><c> with</c><00:01:27.680><c> scale</c><00:01:29.410><c> cleaning</c><00:01:30.410><c> data</c><00:01:30.680><c> that</c>

00:01:31.090 --> 00:01:31.100 align:start position:0%
problems with scale cleaning data that
 

00:01:31.100 --> 00:01:35.760 align:start position:0%
problems with scale cleaning data that
is<00:01:31.280><c> huge</c><00:01:32.260><c> cleaning</c><00:01:33.260><c> data</c><00:01:33.440><c> that</c><00:01:33.710><c> is</c><00:01:33.920><c> in</c><00:01:34.690><c> the</c>

00:01:35.760 --> 00:01:35.770 align:start position:0%
is huge cleaning data that is in the
 

00:01:35.770 --> 00:01:39.940 align:start position:0%
is huge cleaning data that is in the
Gigabyte<00:01:37.000><c> scale</c><00:01:38.290><c> can</c><00:01:39.290><c> be</c><00:01:39.350><c> challenging</c>

00:01:39.940 --> 00:01:39.950 align:start position:0%
Gigabyte scale can be challenging
 

00:01:39.950 --> 00:01:42.490 align:start position:0%
Gigabyte scale can be challenging
because<00:01:40.550><c> sometimes</c><00:01:41.120><c> there</c><00:01:41.390><c> you</c><00:01:41.750><c> sometimes</c>

00:01:42.490 --> 00:01:42.500 align:start position:0%
because sometimes there you sometimes
 

00:01:42.500 --> 00:01:46.540 align:start position:0%
because sometimes there you sometimes
that<00:01:42.620><c> are</c><00:01:42.650><c> corner</c><00:01:42.950><c> cases</c><00:01:45.190><c> sometimes</c><00:01:46.190><c> when</c><00:01:46.430><c> you</c>

00:01:46.540 --> 00:01:46.550 align:start position:0%
that are corner cases sometimes when you
 

00:01:46.550 --> 00:01:49.420 align:start position:0%
that are corner cases sometimes when you
have<00:01:46.760><c> problems</c><00:01:47.030><c> with</c><00:01:47.330><c> data</c><00:01:47.570><c> like</c><00:01:47.750><c> that</c><00:01:48.430><c> one</c>

00:01:49.420 --> 00:01:49.430 align:start position:0%
have problems with data like that one
 

00:01:49.430 --> 00:01:51.850 align:start position:0%
have problems with data like that one
way<00:01:49.730><c> to</c><00:01:49.760><c> solve</c><00:01:50.570><c> it</c><00:01:50.720><c> is</c><00:01:50.840><c> to</c><00:01:50.900><c> not</c><00:01:51.170><c> just</c><00:01:51.500><c> ignore</c>

00:01:51.850 --> 00:01:51.860 align:start position:0%
way to solve it is to not just ignore
 

00:01:51.860 --> 00:01:56.080 align:start position:0%
way to solve it is to not just ignore
the<00:01:52.310><c> the</c><00:01:52.600><c> corner</c><00:01:53.600><c> cases</c><00:01:54.550><c> but</c><00:01:55.550><c> there's</c><00:01:55.970><c> a</c>

00:01:56.080 --> 00:01:56.090 align:start position:0%
the the corner cases but there's a
 

00:01:56.090 --> 00:01:57.870 align:start position:0%
the the corner cases but there's a
desire<00:01:56.420><c> to</c><00:01:56.690><c> get</c><00:01:56.930><c> as</c><00:01:57.110><c> much</c><00:01:57.260><c> data</c><00:01:57.500><c> as</c><00:01:57.710><c> possible</c>

00:01:57.870 --> 00:01:57.880 align:start position:0%
desire to get as much data as possible
 

00:01:57.880 --> 00:02:00.070 align:start position:0%
desire to get as much data as possible
because<00:01:58.880><c> some</c><00:01:59.030><c> of</c><00:01:59.210><c> those</c><00:01:59.300><c> corner</c><00:01:59.540><c> cases</c><00:01:59.750><c> to</c><00:01:59.930><c> be</c>

00:02:00.070 --> 00:02:00.080 align:start position:0%
because some of those corner cases to be
 

00:02:00.080 --> 00:02:03.990 align:start position:0%
because some of those corner cases to be
important<00:02:00.830><c> so</c><00:02:01.700><c> it's</c><00:02:02.360><c> to</c><00:02:03.170><c> me</c><00:02:03.290><c> it's</c><00:02:03.320><c> cleaning</c>

00:02:03.990 --> 00:02:04.000 align:start position:0%
important so it's to me it's cleaning
 

00:02:04.000 --> 00:02:06.960 align:start position:0%
important so it's to me it's cleaning
data<00:02:05.000><c> sets</c><00:02:05.330><c> that</c><00:02:05.450><c> are</c><00:02:05.570><c> very</c><00:02:05.930><c> large</c><00:02:06.170><c> and</c><00:02:06.500><c> very</c>

00:02:06.960 --> 00:02:06.970 align:start position:0%
data sets that are very large and very
 

00:02:06.970 --> 00:02:12.350 align:start position:0%
data sets that are very large and very
diverse

00:02:12.350 --> 00:02:12.360 align:start position:0%
 
 

00:02:12.360 --> 00:02:15.250 align:start position:0%
 
[Music]

00:02:15.250 --> 00:02:15.260 align:start position:0%
[Music]
 

00:02:15.260 --> 00:02:17.869 align:start position:0%
[Music]
so<00:02:16.260><c> some</c><00:02:16.439><c> issues</c><00:02:16.709><c> that</c><00:02:16.860><c> may</c><00:02:17.129><c> come</c><00:02:17.340><c> up</c><00:02:17.370><c> we</c><00:02:17.760><c> need</c>

00:02:17.869 --> 00:02:17.879 align:start position:0%
so some issues that may come up we need
 

00:02:17.879 --> 00:02:20.589 align:start position:0%
so some issues that may come up we need
to<00:02:17.909><c> come</c><00:02:18.120><c> to</c><00:02:18.239><c> scale</c><00:02:18.450><c> in</c><00:02:18.599><c> the</c><00:02:18.659><c> next</c><00:02:18.900><c> year</c><00:02:19.110><c> is</c>

00:02:20.589 --> 00:02:20.599 align:start position:0%
to come to scale in the next year is
 

00:02:20.599 --> 00:02:23.600 align:start position:0%
to come to scale in the next year is
we're<00:02:21.599><c> transitioning</c><00:02:21.870><c> a</c><00:02:22.739><c> lot</c><00:02:23.069><c> of</c><00:02:23.189><c> our</c><00:02:23.340><c> core</c>

00:02:23.600 --> 00:02:23.610 align:start position:0%
we're transitioning a lot of our core
 

00:02:23.610 --> 00:02:27.170 align:start position:0%
we're transitioning a lot of our core
technology<00:02:24.260><c> from</c><00:02:25.260><c> solely</c><00:02:26.069><c> Python</c><00:02:26.819><c> Python</c>

00:02:27.170 --> 00:02:27.180 align:start position:0%
technology from solely Python Python
 

00:02:27.180 --> 00:02:32.360 align:start position:0%
technology from solely Python Python
house<00:02:27.569><c> to</c><00:02:28.700><c> Scala</c><00:02:30.349><c> so</c><00:02:31.349><c> I</c><00:02:31.739><c> think</c><00:02:31.860><c> I</c><00:02:32.159><c> can</c>

00:02:32.360 --> 00:02:32.370 align:start position:0%
house to Scala so I think I can
 

00:02:32.370 --> 00:02:34.160 align:start position:0%
house to Scala so I think I can
anticipate<00:02:32.700><c> some</c><00:02:33.090><c> challenges</c><00:02:33.629><c> and</c><00:02:33.780><c> making</c>

00:02:34.160 --> 00:02:34.170 align:start position:0%
anticipate some challenges and making
 

00:02:34.170 --> 00:02:38.360 align:start position:0%
anticipate some challenges and making
that<00:02:34.290><c> transition</c><00:02:35.299><c> and</c><00:02:36.299><c> getting</c><00:02:37.019><c> down</c><00:02:37.200><c> a</c><00:02:37.650><c> good</c>

00:02:38.360 --> 00:02:38.370 align:start position:0%
that transition and getting down a good
 

00:02:38.370 --> 00:02:41.630 align:start position:0%
that transition and getting down a good
set<00:02:38.730><c> of</c><00:02:38.760><c> procedures</c><00:02:39.720><c> to</c><00:02:40.680><c> systematically</c><00:02:41.370><c> deal</c>

00:02:41.630 --> 00:02:41.640 align:start position:0%
set of procedures to systematically deal
 

00:02:41.640 --> 00:02:43.009 align:start position:0%
set of procedures to systematically deal
with<00:02:41.879><c> new</c><00:02:42.090><c> clients</c><00:02:42.450><c> and</c><00:02:42.780><c> new</c><00:02:42.840><c> customers</c>

00:02:43.009 --> 00:02:43.019 align:start position:0%
with new clients and new customers
 

00:02:43.019 --> 00:02:46.009 align:start position:0%
with new clients and new customers
problems<00:02:43.709><c> right</c><00:02:44.579><c> now</c><00:02:44.609><c> we're</c><00:02:45.510><c> so</c><00:02:45.720><c> used</c><00:02:45.900><c> to</c>

00:02:46.009 --> 00:02:46.019 align:start position:0%
problems right now we're so used to
 

00:02:46.019 --> 00:02:47.930 align:start position:0%
problems right now we're so used to
Python<00:02:46.440><c> and</c><00:02:46.709><c> doing</c><00:02:47.010><c> things</c><00:02:47.190><c> in</c><00:02:47.370><c> the</c><00:02:47.489><c> pythonic</c>

00:02:47.930 --> 00:02:47.940 align:start position:0%
Python and doing things in the pythonic
 

00:02:47.940 --> 00:02:51.259 align:start position:0%
Python and doing things in the pythonic
way<00:02:48.090><c> that</c><00:02:49.400><c> it's</c><00:02:50.400><c> like</c><00:02:50.940><c> second</c><00:02:51.239><c> nature</c>

00:02:51.259 --> 00:02:51.269 align:start position:0%
way that it's like second nature
 

00:02:51.269 --> 00:02:54.199 align:start position:0%
way that it's like second nature
sometimes<00:02:51.930><c> and</c><00:02:52.200><c> I</c><00:02:52.650><c> can</c><00:02:53.010><c> see</c><00:02:53.159><c> it</c><00:02:53.250><c> I</c><00:02:53.489><c> can</c><00:02:53.819><c> see</c><00:02:54.120><c> us</c>

00:02:54.199 --> 00:02:54.209 align:start position:0%
sometimes and I can see it I can see us
 

00:02:54.209 --> 00:02:56.360 align:start position:0%
sometimes and I can see it I can see us
losing<00:02:54.540><c> time</c><00:02:54.720><c> on</c><00:02:54.930><c> some</c><00:02:55.049><c> projects</c><00:02:55.500><c> just</c><00:02:56.220><c> in</c>

00:02:56.360 --> 00:02:56.370 align:start position:0%
losing time on some projects just in
 

00:02:56.370 --> 00:03:06.949 align:start position:0%
losing time on some projects just in
doing<00:02:57.000><c> that</c><00:02:57.090><c> transition</c><00:03:04.159><c> so</c><00:03:05.959><c> functional</c>

00:03:06.949 --> 00:03:06.959 align:start position:0%
doing that transition so functional
 

00:03:06.959 --> 00:03:09.110 align:start position:0%
doing that transition so functional
programming<00:03:07.319><c> how</c><00:03:07.530><c> does</c><00:03:07.650><c> it</c><00:03:07.739><c> help</c><00:03:07.799><c> this</c><00:03:08.120><c> it's</c>

00:03:09.110 --> 00:03:09.120 align:start position:0%
programming how does it help this it's
 

00:03:09.120 --> 00:03:12.500 align:start position:0%
programming how does it help this it's
helped<00:03:09.599><c> us</c><00:03:09.750><c> in</c><00:03:09.930><c> being</c><00:03:10.739><c> able</c><00:03:10.920><c> to</c><00:03:11.099><c> use</c><00:03:11.510><c> some</c>

00:03:12.500 --> 00:03:12.510 align:start position:0%
helped us in being able to use some
 

00:03:12.510 --> 00:03:15.530 align:start position:0%
helped us in being able to use some
tools<00:03:12.780><c> more</c><00:03:13.409><c> efficiently</c><00:03:13.859><c> so</c><00:03:14.099><c> the</c><00:03:15.090><c> reason</c><00:03:15.419><c> I</c>

00:03:15.530 --> 00:03:15.540 align:start position:0%
tools more efficiently so the reason I
 

00:03:15.540 --> 00:03:18.650 align:start position:0%
tools more efficiently so the reason I
got<00:03:15.780><c> into</c><00:03:15.840><c> functional</c><00:03:16.709><c> programming</c><00:03:17.280><c> is</c><00:03:17.660><c> to</c>

00:03:18.650 --> 00:03:18.660 align:start position:0%
got into functional programming is to
 

00:03:18.660 --> 00:03:23.360 align:start position:0%
got into functional programming is to
take<00:03:19.109><c> advantage</c><00:03:19.470><c> of</c><00:03:19.590><c> spark</c><00:03:20.209><c> so</c><00:03:21.209><c> I</c><00:03:22.139><c> think</c><00:03:22.889><c> Scala</c>

00:03:23.360 --> 00:03:23.370 align:start position:0%
take advantage of spark so I think Scala
 

00:03:23.370 --> 00:03:25.240 align:start position:0%
take advantage of spark so I think Scala
is<00:03:23.609><c> a</c><00:03:23.639><c> very</c><00:03:24.120><c> good</c><00:03:24.329><c> and</c><00:03:24.540><c> efficient</c><00:03:24.930><c> way</c><00:03:24.989><c> to</c><00:03:25.019><c> use</c>

00:03:25.240 --> 00:03:25.250 align:start position:0%
is a very good and efficient way to use
 

00:03:25.250 --> 00:03:29.930 align:start position:0%
is a very good and efficient way to use
spark<00:03:26.250><c> right</c><00:03:27.060><c> now</c><00:03:27.829><c> I'm</c><00:03:28.829><c> still</c><00:03:29.340><c> transitioning</c>

00:03:29.930 --> 00:03:29.940 align:start position:0%
spark right now I'm still transitioning
 

00:03:29.940 --> 00:03:33.530 align:start position:0%
spark right now I'm still transitioning
to<00:03:30.660><c> being</c><00:03:31.079><c> full</c><00:03:31.849><c> full</c><00:03:32.849><c> scholarship</c><00:03:33.269><c> developer</c>

00:03:33.530 --> 00:03:33.540 align:start position:0%
to being full full scholarship developer
 

00:03:33.540 --> 00:03:34.849 align:start position:0%
to being full full scholarship developer
and<00:03:33.660><c> a</c><00:03:33.690><c> lot</c><00:03:33.840><c> of</c><00:03:33.870><c> the</c><00:03:34.290><c> projects</c><00:03:34.680><c> that</c><00:03:34.709><c> I</c><00:03:34.829><c> think</c>

00:03:34.849 --> 00:03:34.859 align:start position:0%
and a lot of the projects that I think
 

00:03:34.859 --> 00:03:37.849 align:start position:0%
and a lot of the projects that I think
call<00:03:35.220><c> for</c><00:03:35.430><c> it</c><00:03:35.519><c> and</c><00:03:35.790><c> I'm</c><00:03:36.750><c> using</c><00:03:36.989><c> PI</c><00:03:37.349><c> spark</c><00:03:37.680><c> it's</c>

00:03:37.849 --> 00:03:37.859 align:start position:0%
call for it and I'm using PI spark it's
 

00:03:37.859 --> 00:03:41.539 align:start position:0%
call for it and I'm using PI spark it's
kind<00:03:38.010><c> of</c><00:03:38.069><c> a</c><00:03:38.900><c> transition</c><00:03:39.900><c> type</c><00:03:40.440><c> of</c><00:03:40.590><c> tool</c><00:03:41.040><c> for</c><00:03:41.459><c> me</c>

00:03:41.539 --> 00:03:41.549 align:start position:0%
kind of a transition type of tool for me
 

00:03:41.549 --> 00:03:44.449 align:start position:0%
kind of a transition type of tool for me
but<00:03:42.480><c> I</c><00:03:42.930><c> think</c><00:03:43.410><c> if</c><00:03:43.590><c> I</c><00:03:43.799><c> could</c><00:03:43.859><c> have</c><00:03:44.190><c> everything</c>

00:03:44.449 --> 00:03:44.459 align:start position:0%
but I think if I could have everything
 

00:03:44.459 --> 00:03:46.819 align:start position:0%
but I think if I could have everything
in<00:03:44.669><c> Scala</c><00:03:45.060><c> I</c><00:03:45.209><c> could</c><00:03:45.690><c> have</c><00:03:45.840><c> much</c><00:03:46.290><c> cleaner</c><00:03:46.560><c> code</c>

00:03:46.819 --> 00:03:46.829 align:start position:0%
in Scala I could have much cleaner code
 

00:03:46.829 --> 00:03:50.180 align:start position:0%
in Scala I could have much cleaner code
and<00:03:47.419><c> much</c><00:03:48.419><c> more</c><00:03:48.629><c> efficient</c><00:03:49.129><c> much</c><00:03:50.129><c> more</c>

00:03:50.180 --> 00:03:50.190 align:start position:0%
and much more efficient much more
 

00:03:50.190 --> 00:03:52.930 align:start position:0%
and much more efficient much more
efficient<00:03:50.760><c> algorithms</c>

00:03:52.930 --> 00:03:52.940 align:start position:0%
efficient algorithms
 

00:03:52.940 --> 00:03:58.140 align:start position:0%
efficient algorithms
[Music]

00:03:58.140 --> 00:03:58.150 align:start position:0%
 
 

00:03:58.150 --> 00:04:01.330 align:start position:0%
 
I<00:03:59.150><c> went</c><00:03:59.720><c> to</c><00:03:59.840><c> the</c><00:04:00.200><c> one</c><00:04:00.710><c> iteration</c><00:04:01.160><c> of</c><00:04:01.220><c> this</c>

00:04:01.330 --> 00:04:01.340 align:start position:0%
I went to the one iteration of this
 

00:04:01.340 --> 00:04:04.330 align:start position:0%
I went to the one iteration of this
conference<00:04:01.760><c> last</c><00:04:01.910><c> year</c><00:04:02.170><c> so</c><00:04:03.170><c> I</c><00:04:03.680><c> like</c><00:04:04.130><c> the</c>

00:04:04.330 --> 00:04:04.340 align:start position:0%
conference last year so I like the
 

00:04:04.340 --> 00:04:06.100 align:start position:0%
conference last year so I like the
diversity<00:04:04.850><c> of</c><00:04:05.180><c> speakers</c><00:04:05.600><c> I</c><00:04:05.780><c> like</c><00:04:05.900><c> to</c><00:04:05.990><c> hear</c>

00:04:06.100 --> 00:04:06.110 align:start position:0%
diversity of speakers I like to hear
 

00:04:06.110 --> 00:04:08.230 align:start position:0%
diversity of speakers I like to hear
what<00:04:06.230><c> other</c><00:04:06.380><c> people</c><00:04:06.440><c> are</c><00:04:06.740><c> doing</c><00:04:06.800><c> I</c><00:04:07.250><c> like</c><00:04:08.120><c> to</c>

00:04:08.230 --> 00:04:08.240 align:start position:0%
what other people are doing I like to
 

00:04:08.240 --> 00:04:09.580 align:start position:0%
what other people are doing I like to
factor<00:04:08.540><c> the</c><00:04:08.660><c> projects</c><00:04:09.050><c> that</c><00:04:09.080><c> people</c><00:04:09.260><c> talk</c>

00:04:09.580 --> 00:04:09.590 align:start position:0%
factor the projects that people talk
 

00:04:09.590 --> 00:04:11.500 align:start position:0%
factor the projects that people talk
about<00:04:09.830><c> or</c><00:04:09.980><c> not</c><00:04:10.100><c> marketing</c><00:04:10.760><c> presentations</c>

00:04:11.500 --> 00:04:11.510 align:start position:0%
about or not marketing presentations
 

00:04:11.510 --> 00:04:13.660 align:start position:0%
about or not marketing presentations
that<00:04:11.690><c> are</c><00:04:11.750><c> hands-on</c><00:04:12.370><c> presentations</c><00:04:13.370><c> and</c><00:04:13.580><c> they</c>

00:04:13.660 --> 00:04:13.670 align:start position:0%
that are hands-on presentations and they
 

00:04:13.670 --> 00:04:15.340 align:start position:0%
that are hands-on presentations and they
talk<00:04:13.880><c> about</c><00:04:14.000><c> real</c><00:04:14.300><c> problems</c><00:04:14.570><c> that</c><00:04:14.840><c> they</c><00:04:14.930><c> have</c>

00:04:15.340 --> 00:04:15.350 align:start position:0%
talk about real problems that they have
 

00:04:15.350 --> 00:04:18.190 align:start position:0%
talk about real problems that they have
sometimes<00:04:16.310><c> there</c><00:04:16.880><c> there</c><00:04:17.390><c> are</c><00:04:17.510><c> things</c><00:04:17.750><c> that</c>

00:04:18.190 --> 00:04:18.200 align:start position:0%
sometimes there there are things that
 

00:04:18.200 --> 00:04:20.590 align:start position:0%
sometimes there there are things that
aren't<00:04:18.650><c> very</c><00:04:18.890><c> relevant</c><00:04:19.250><c> for</c><00:04:19.400><c> me</c><00:04:19.640><c> but</c>

00:04:20.590 --> 00:04:20.600 align:start position:0%
aren't very relevant for me but
 

00:04:20.600 --> 00:04:23.350 align:start position:0%
aren't very relevant for me but
sometimes<00:04:20.989><c> something</c><00:04:21.830><c> strikes</c><00:04:22.790><c> a</c><00:04:22.910><c> nerve</c><00:04:23.060><c> and</c>

00:04:23.350 --> 00:04:23.360 align:start position:0%
sometimes something strikes a nerve and
 

00:04:23.360 --> 00:04:25.330 align:start position:0%
sometimes something strikes a nerve and
there's<00:04:24.350><c> some</c><00:04:24.500><c> insight</c><00:04:24.830><c> that</c><00:04:24.950><c> someone</c><00:04:25.190><c> has</c><00:04:25.310><c> a</c>

00:04:25.330 --> 00:04:25.340 align:start position:0%
there's some insight that someone has a
 

00:04:25.340 --> 00:04:27.430 align:start position:0%
there's some insight that someone has a
completely<00:04:25.850><c> different</c><00:04:25.970><c> project</c><00:04:26.360><c> that</c><00:04:27.290><c> could</c>

00:04:27.430 --> 00:04:27.440 align:start position:0%
completely different project that could
 

00:04:27.440 --> 00:04:35.000 align:start position:0%
completely different project that could
bear<00:04:27.620><c> some</c><00:04:27.980><c> relevance</c><00:04:28.820><c> on</c><00:04:29.090><c> what</c><00:04:29.870><c> I'm</c><00:04:30.020><c> doing</c>

00:04:35.000 --> 00:04:35.010 align:start position:0%
 
 

00:04:35.010 --> 00:04:38.130 align:start position:0%
 
[Music]