WEBVTT
Kind: captions
Language: en

00:00:11.730 --> 00:00:13.750 align:start position:0%
 
[Music]

00:00:13.750 --> 00:00:13.760 align:start position:0%
[Music]
 

00:00:13.760 --> 00:00:17.019 align:start position:0%
[Music]
my<00:00:14.600><c> name</c><00:00:14.750><c> is</c><00:00:14.870><c> Martin</c><00:00:15.200><c> Zapata</c><00:00:15.860><c> I'm</c><00:00:16.219><c> a</c><00:00:16.279><c> director</c>

00:00:17.019 --> 00:00:17.029 align:start position:0%
my name is Martin Zapata I'm a director
 

00:00:17.029 --> 00:00:19.300 align:start position:0%
my name is Martin Zapata I'm a director
of<00:00:17.180><c> engineering</c><00:00:17.359><c> at</c><00:00:17.930><c> fake</c><00:00:18.349><c> solutions</c><00:00:18.830><c> bomb</c>

00:00:19.300 --> 00:00:19.310 align:start position:0%
of engineering at fake solutions bomb
 

00:00:19.310 --> 00:00:28.960 align:start position:0%
of engineering at fake solutions bomb
tech<00:00:19.490><c> media</c><00:00:19.760><c> company</c><00:00:26.199><c> we're</c><00:00:27.199><c> building</c><00:00:27.970><c> or</c>

00:00:28.960 --> 00:00:28.970 align:start position:0%
tech media company we're building or
 

00:00:28.970 --> 00:00:31.480 align:start position:0%
tech media company we're building or
building<00:00:29.359><c> large-scale</c><00:00:30.130><c> extremely</c><00:00:31.130><c> reliable</c>

00:00:31.480 --> 00:00:31.490 align:start position:0%
building large-scale extremely reliable
 

00:00:31.490 --> 00:00:34.900 align:start position:0%
building large-scale extremely reliable
and<00:00:31.910><c> scalable</c><00:00:32.840><c> and</c><00:00:33.410><c> elastic</c><00:00:33.829><c> solutions</c><00:00:34.489><c> so</c>

00:00:34.900 --> 00:00:34.910 align:start position:0%
and scalable and elastic solutions so
 

00:00:34.910 --> 00:00:36.189 align:start position:0%
and scalable and elastic solutions so
we're<00:00:35.059><c> running</c><00:00:35.329><c> into</c><00:00:35.600><c> a</c><00:00:35.629><c> lot</c><00:00:35.929><c> of</c><00:00:35.989><c> problems</c>

00:00:36.189 --> 00:00:36.199 align:start position:0%
we're running into a lot of problems
 

00:00:36.199 --> 00:00:38.259 align:start position:0%
we're running into a lot of problems
associated<00:00:37.069><c> with</c><00:00:37.399><c> building</c><00:00:37.850><c> these</c><00:00:37.999><c> type</c><00:00:38.239><c> of</c>

00:00:38.259 --> 00:00:38.269 align:start position:0%
associated with building these type of
 

00:00:38.269 --> 00:00:41.979 align:start position:0%
associated with building these type of
systems<00:00:38.800><c> from</c><00:00:39.969><c> the</c><00:00:40.969><c> reliability</c><00:00:41.690><c> from</c>

00:00:41.979 --> 00:00:41.989 align:start position:0%
systems from the reliability from
 

00:00:41.989 --> 00:00:44.889 align:start position:0%
systems from the reliability from
resilience<00:00:42.559><c> the</c><00:00:42.979><c> cost</c><00:00:43.249><c> of</c><00:00:44.089><c> infrastructure</c><00:00:44.809><c> at</c>

00:00:44.889 --> 00:00:44.899 align:start position:0%
resilience the cost of infrastructure at
 

00:00:44.899 --> 00:00:47.979 align:start position:0%
resilience the cost of infrastructure at
that<00:00:45.079><c> scale</c><00:00:45.350><c> to</c><00:00:46.780><c> observability</c><00:00:47.780><c> of</c><00:00:47.870><c> the</c>

00:00:47.979 --> 00:00:47.989 align:start position:0%
that scale to observability of the
 

00:00:47.989 --> 00:00:49.660 align:start position:0%
that scale to observability of the
system<00:00:48.289><c> in</c><00:00:48.379><c> production</c><00:00:48.829><c> to</c><00:00:48.949><c> making</c><00:00:49.249><c> sure</c><00:00:49.429><c> make</c>

00:00:49.660 --> 00:00:49.670 align:start position:0%
system in production to making sure make
 

00:00:49.670 --> 00:00:51.489 align:start position:0%
system in production to making sure make
sure<00:00:49.879><c> that</c><00:00:50.089><c> everything</c><00:00:50.479><c> works</c><00:00:50.690><c> as</c><00:00:50.929><c> as</c><00:00:51.229><c> it's</c>

00:00:51.489 --> 00:00:51.499 align:start position:0%
sure that everything works as as it's
 

00:00:51.499 --> 00:01:01.029 align:start position:0%
sure that everything works as as it's
supposed<00:00:51.769><c> to</c><00:00:58.690><c> there's</c><00:00:59.690><c> a</c><00:00:59.780><c> variety</c><00:01:00.289><c> of</c><00:01:00.649><c> issues</c>

00:01:01.029 --> 00:01:01.039 align:start position:0%
supposed to there's a variety of issues
 

00:01:01.039 --> 00:01:03.399 align:start position:0%
supposed to there's a variety of issues
with<00:01:01.909><c> building</c><00:01:02.239><c> systems</c><00:01:02.690><c> of</c><00:01:02.839><c> this</c><00:01:02.989><c> of</c><00:01:03.260><c> this</c>

00:01:03.399 --> 00:01:03.409 align:start position:0%
with building systems of this of this
 

00:01:03.409 --> 00:01:06.460 align:start position:0%
with building systems of this of this
quite<00:01:03.949><c> extreme</c><00:01:04.369><c> scale</c><00:01:04.840><c> some</c><00:01:05.840><c> of</c><00:01:05.869><c> them</c><00:01:06.140><c> include</c>

00:01:06.460 --> 00:01:06.470 align:start position:0%
quite extreme scale some of them include
 

00:01:06.470 --> 00:01:08.560 align:start position:0%
quite extreme scale some of them include
the<00:01:06.670><c> resiliency</c><00:01:07.670><c> and</c><00:01:07.760><c> reliability</c><00:01:08.330><c> of</c><00:01:08.450><c> the</c>

00:01:08.560 --> 00:01:08.570 align:start position:0%
the resiliency and reliability of the
 

00:01:08.570 --> 00:01:10.150 align:start position:0%
the resiliency and reliability of the
system<00:01:08.870><c> so</c><00:01:09.020><c> we</c><00:01:09.140><c> need</c><00:01:09.290><c> to</c><00:01:09.410><c> be</c><00:01:09.500><c> able</c><00:01:09.620><c> to</c><00:01:09.800><c> handle</c>

00:01:10.150 --> 00:01:10.160 align:start position:0%
system so we need to be able to handle
 

00:01:10.160 --> 00:01:12.910 align:start position:0%
system so we need to be able to handle
things<00:01:10.310><c> like</c><00:01:10.810><c> even</c><00:01:11.810><c> catastrophic</c><00:01:12.440><c> data</c>

00:01:12.910 --> 00:01:12.920 align:start position:0%
things like even catastrophic data
 

00:01:12.920 --> 00:01:15.540 align:start position:0%
things like even catastrophic data
center<00:01:13.280><c> failures</c><00:01:13.640><c> but</c><00:01:14.180><c> node</c><00:01:14.420><c> failures</c><00:01:14.870><c> and</c>

00:01:15.540 --> 00:01:15.550 align:start position:0%
center failures but node failures and
 

00:01:15.550 --> 00:01:18.730 align:start position:0%
center failures but node failures and
things<00:01:16.550><c> like</c><00:01:16.700><c> that</c><00:01:16.760><c> are</c><00:01:17.030><c> extremely</c><00:01:17.690><c> common</c><00:01:17.900><c> so</c>

00:01:18.730 --> 00:01:18.740 align:start position:0%
things like that are extremely common so
 

00:01:18.740 --> 00:01:19.870 align:start position:0%
things like that are extremely common so
we<00:01:18.860><c> have</c><00:01:18.950><c> to</c><00:01:19.100><c> be</c><00:01:19.190><c> able</c><00:01:19.280><c> to</c><00:01:19.430><c> handle</c><00:01:19.730><c> those</c>

00:01:19.870 --> 00:01:19.880 align:start position:0%
we have to be able to handle those
 

00:01:19.880 --> 00:01:21.940 align:start position:0%
we have to be able to handle those
another<00:01:20.240><c> problem</c><00:01:20.780><c> a</c><00:01:20.930><c> common</c><00:01:21.320><c> one</c><00:01:21.500><c> I</c><00:01:21.530><c> think</c><00:01:21.650><c> is</c>

00:01:21.940 --> 00:01:21.950 align:start position:0%
another problem a common one I think is
 

00:01:21.950 --> 00:01:24.370 align:start position:0%
another problem a common one I think is
observability<00:01:22.700><c> of</c><00:01:22.820><c> the</c><00:01:22.970><c> system</c><00:01:23.330><c> we</c><00:01:24.200><c> need</c><00:01:24.320><c> to</c>

00:01:24.370 --> 00:01:24.380 align:start position:0%
observability of the system we need to
 

00:01:24.380 --> 00:01:25.780 align:start position:0%
observability of the system we need to
make<00:01:24.590><c> sure</c><00:01:24.800><c> that</c><00:01:24.920><c> we</c><00:01:25.100><c> understand</c><00:01:25.610><c> what</c><00:01:25.760><c> the</c>

00:01:25.780 --> 00:01:25.790 align:start position:0%
make sure that we understand what the
 

00:01:25.790 --> 00:01:28.090 align:start position:0%
make sure that we understand what the
system<00:01:26.180><c> is</c><00:01:26.270><c> doing</c><00:01:26.420><c> from</c><00:01:27.050><c> both</c><00:01:27.230><c> technical</c><00:01:27.920><c> and</c>

00:01:28.090 --> 00:01:28.100 align:start position:0%
system is doing from both technical and
 

00:01:28.100 --> 00:01:31.090 align:start position:0%
system is doing from both technical and
business<00:01:28.840><c> point</c><00:01:29.840><c> of</c><00:01:29.990><c> view</c><00:01:30.050><c> to</c><00:01:30.620><c> make</c><00:01:30.650><c> sure</c><00:01:30.950><c> that</c>

00:01:31.090 --> 00:01:31.100 align:start position:0%
business point of view to make sure that
 

00:01:31.100 --> 00:01:35.740 align:start position:0%
business point of view to make sure that
we<00:01:31.250><c> can</c><00:01:31.430><c> we</c><00:01:31.910><c> can</c><00:01:32.090><c> we</c><00:01:32.830><c> can</c><00:01:33.830><c> notice</c><00:01:34.190><c> and</c><00:01:35.060><c> fix</c><00:01:35.450><c> any</c>

00:01:35.740 --> 00:01:35.750 align:start position:0%
we can we can we can notice and fix any
 

00:01:35.750 --> 00:01:37.390 align:start position:0%
we can we can we can notice and fix any
potential<00:01:36.380><c> issues</c><00:01:36.470><c> that</c><00:01:37.010><c> happen</c><00:01:37.310><c> on</c>

00:01:37.390 --> 00:01:37.400 align:start position:0%
potential issues that happen on
 

00:01:37.400 --> 00:01:41.920 align:start position:0%
potential issues that happen on
production

00:01:41.920 --> 00:01:41.930 align:start position:0%
 
 

00:01:41.930 --> 00:01:44.590 align:start position:0%
 
[Music]

00:01:44.590 --> 00:01:44.600 align:start position:0%
[Music]
 

00:01:44.600 --> 00:01:48.139 align:start position:0%
[Music]
some<00:01:45.600><c> of</c><00:01:45.720><c> the</c><00:01:46.159><c> problems</c><00:01:47.159><c> that</c><00:01:47.280><c> the</c><00:01:47.729><c> industry</c>

00:01:48.139 --> 00:01:48.149 align:start position:0%
some of the problems that the industry
 

00:01:48.149 --> 00:01:50.240 align:start position:0%
some of the problems that the industry
needs<00:01:48.180><c> to</c><00:01:48.420><c> solve</c><00:01:48.720><c> around</c><00:01:49.140><c> scaling</c><00:01:49.860><c> is</c><00:01:49.979><c> again</c>

00:01:50.240 --> 00:01:50.250 align:start position:0%
needs to solve around scaling is again
 

00:01:50.250 --> 00:01:52.310 align:start position:0%
needs to solve around scaling is again
resiliency<00:01:51.090><c> and</c><00:01:51.240><c> make</c><00:01:51.450><c> it</c><00:01:51.600><c> and</c><00:01:51.869><c> being</c><00:01:52.020><c> able</c><00:01:52.170><c> to</c>

00:01:52.310 --> 00:01:52.320 align:start position:0%
resiliency and make it and being able to
 

00:01:52.320 --> 00:01:55.310 align:start position:0%
resiliency and make it and being able to
build<00:01:53.130><c> global</c><00:01:53.970><c> scale</c><00:01:54.240><c> systems</c><00:01:54.689><c> that</c><00:01:55.020><c> can</c>

00:01:55.310 --> 00:01:55.320 align:start position:0%
build global scale systems that can
 

00:01:55.320 --> 00:02:00.109 align:start position:0%
build global scale systems that can
handle<00:01:55.880><c> failures</c><00:01:56.960><c> and</c><00:01:58.549><c> also</c><00:01:59.549><c> performance</c>

00:02:00.109 --> 00:02:00.119 align:start position:0%
handle failures and also performance
 

00:02:00.119 --> 00:02:03.380 align:start position:0%
handle failures and also performance
also<00:02:00.690><c> be</c><00:02:00.810><c> able</c><00:02:00.899><c> to</c><00:02:01.490><c> be</c><00:02:02.490><c> performant</c><00:02:03.060><c> at</c><00:02:03.270><c> that</c>

00:02:03.380 --> 00:02:03.390 align:start position:0%
also be able to be performant at that
 

00:02:03.390 --> 00:02:06.649 align:start position:0%
also be able to be performant at that
extreme<00:02:03.810><c> scale</c><00:02:04.189><c> while</c><00:02:05.189><c> being</c><00:02:05.850><c> cost</c><00:02:06.149><c> efficient</c>

00:02:06.649 --> 00:02:06.659 align:start position:0%
extreme scale while being cost efficient
 

00:02:06.659 --> 00:02:08.150 align:start position:0%
extreme scale while being cost efficient
because<00:02:06.840><c> cost</c><00:02:07.380><c> efficiency</c><00:02:07.890><c> is</c><00:02:07.950><c> another</c>

00:02:08.150 --> 00:02:08.160 align:start position:0%
because cost efficiency is another
 

00:02:08.160 --> 00:02:10.309 align:start position:0%
because cost efficiency is another
problem<00:02:08.399><c> that</c><00:02:08.580><c> the</c><00:02:09.269><c> industry</c><00:02:09.660><c> industry</c><00:02:09.989><c> has</c>

00:02:10.309 --> 00:02:10.319 align:start position:0%
problem that the industry industry has
 

00:02:10.319 --> 00:02:11.930 align:start position:0%
problem that the industry industry has
to<00:02:10.440><c> solve</c><00:02:10.709><c> because</c><00:02:11.370><c> building</c><00:02:11.730><c> these</c>

00:02:11.930 --> 00:02:11.940 align:start position:0%
to solve because building these
 

00:02:11.940 --> 00:02:13.759 align:start position:0%
to solve because building these
extremely<00:02:12.750><c> large</c><00:02:12.870><c> scale</c><00:02:13.110><c> systems</c><00:02:13.470><c> becomes</c>

00:02:13.759 --> 00:02:13.769 align:start position:0%
extremely large scale systems becomes
 

00:02:13.769 --> 00:02:16.850 align:start position:0%
extremely large scale systems becomes
expensive<00:02:14.630><c> the</c><00:02:15.630><c> problems</c><00:02:16.110><c> are</c><00:02:16.319><c> amplified</c><00:02:16.830><c> by</c>

00:02:16.850 --> 00:02:16.860 align:start position:0%
expensive the problems are amplified by
 

00:02:16.860 --> 00:02:19.930 align:start position:0%
expensive the problems are amplified by
the<00:02:17.489><c> scale</c><00:02:17.850><c> of</c><00:02:18.030><c> the</c><00:02:18.269><c> problem</c><00:02:18.630><c> so</c><00:02:19.350><c> solving</c><00:02:19.739><c> that</c>

00:02:19.930 --> 00:02:19.940 align:start position:0%
the scale of the problem so solving that
 

00:02:19.940 --> 00:02:22.220 align:start position:0%
the scale of the problem so solving that
solving<00:02:20.940><c> the</c><00:02:20.970><c> cost</c><00:02:21.299><c> efficiency</c><00:02:21.540><c> I</c><00:02:21.870><c> think</c><00:02:22.140><c> is</c>

00:02:22.220 --> 00:02:22.230 align:start position:0%
solving the cost efficiency I think is
 

00:02:22.230 --> 00:02:23.660 align:start position:0%
solving the cost efficiency I think is
another<00:02:22.440><c> another</c><00:02:22.890><c> really</c><00:02:23.130><c> important</c><00:02:23.580><c> feature</c>

00:02:23.660 --> 00:02:23.670 align:start position:0%
another another really important feature
 

00:02:23.670 --> 00:02:26.900 align:start position:0%
another another really important feature
that<00:02:24.660><c> will</c><00:02:25.470><c> have</c><00:02:25.890><c> to</c><00:02:26.040><c> handle</c><00:02:26.190><c> or</c><00:02:26.549><c> we're</c>

00:02:26.900 --> 00:02:26.910 align:start position:0%
that will have to handle or we're
 

00:02:26.910 --> 00:02:28.490 align:start position:0%
that will have to handle or we're
already<00:02:27.239><c> handling</c><00:02:27.690><c> and</c><00:02:27.900><c> will</c><00:02:28.049><c> be</c><00:02:28.170><c> handling</c>

00:02:28.490 --> 00:02:28.500 align:start position:0%
already handling and will be handling
 

00:02:28.500 --> 00:02:30.350 align:start position:0%
already handling and will be handling
more<00:02:28.620><c> in</c><00:02:28.739><c> the</c><00:02:28.830><c> future</c>

00:02:30.350 --> 00:02:30.360 align:start position:0%
more in the future
 

00:02:30.360 --> 00:02:36.449 align:start position:0%
more in the future
[Music]

00:02:36.449 --> 00:02:36.459 align:start position:0%
 
 

00:02:36.459 --> 00:02:39.300 align:start position:0%
 
we<00:02:37.329><c> use</c><00:02:37.540><c> we</c><00:02:38.230><c> use</c><00:02:38.379><c> functional</c><00:02:38.680><c> programming</c>

00:02:39.300 --> 00:02:39.310 align:start position:0%
we use we use functional programming
 

00:02:39.310 --> 00:02:42.690 align:start position:0%
we use we use functional programming
heavily<00:02:40.030><c> and</c><00:02:40.239><c> I</c><00:02:40.900><c> see</c><00:02:41.170><c> benefits</c><00:02:41.890><c> at</c><00:02:42.069><c> multiple</c>

00:02:42.690 --> 00:02:42.700 align:start position:0%
heavily and I see benefits at multiple
 

00:02:42.700 --> 00:02:46.309 align:start position:0%
heavily and I see benefits at multiple
levels<00:02:42.790><c> one</c><00:02:43.659><c> is</c><00:02:43.810><c> the</c><00:02:43.989><c> the</c><00:02:44.650><c> lower</c><00:02:45.040><c> level</c><00:02:45.519><c> so</c>

00:02:46.309 --> 00:02:46.319 align:start position:0%
levels one is the the lower level so
 

00:02:46.319 --> 00:02:48.509 align:start position:0%
levels one is the the lower level so
referential<00:02:47.319><c> transparency</c><00:02:47.680><c> equation</c>

00:02:48.509 --> 00:02:48.519 align:start position:0%
referential transparency equation
 

00:02:48.519 --> 00:02:52.009 align:start position:0%
referential transparency equation
reasoning<00:02:49.030><c> type</c><00:02:50.019><c> safety</c><00:02:50.469><c> as</c><00:02:50.769><c> well</c><00:02:51.219><c> as</c>

00:02:52.009 --> 00:02:52.019 align:start position:0%
reasoning type safety as well as
 

00:02:52.019 --> 00:02:56.459 align:start position:0%
reasoning type safety as well as
interest<00:02:53.019><c> of</c><00:02:53.319><c> of</c><00:02:53.980><c> engineers</c><00:02:54.930><c> but</c><00:02:55.930><c> also</c><00:02:56.109><c> at</c><00:02:56.349><c> the</c>

00:02:56.459 --> 00:02:56.469 align:start position:0%
interest of of engineers but also at the
 

00:02:56.469 --> 00:02:57.089 align:start position:0%
interest of of engineers but also at the
system<00:02:56.799><c> level</c>

00:02:57.089 --> 00:02:57.099 align:start position:0%
system level
 

00:02:57.099 --> 00:02:59.309 align:start position:0%
system level
so<00:02:57.519><c> because</c><00:02:58.060><c> functional</c><00:02:58.629><c> programming</c>

00:02:59.309 --> 00:02:59.319 align:start position:0%
so because functional programming
 

00:02:59.319 --> 00:03:03.149 align:start position:0%
so because functional programming
provides<00:02:59.969><c> correctness</c><00:03:00.969><c> and</c><00:03:01.389><c> safety</c><00:03:02.040><c> which</c><00:03:03.040><c> is</c>

00:03:03.149 --> 00:03:03.159 align:start position:0%
provides correctness and safety which is
 

00:03:03.159 --> 00:03:07.440 align:start position:0%
provides correctness and safety which is
really<00:03:03.430><c> useful</c><00:03:03.549><c> because</c><00:03:03.879><c> it</c><00:03:04.209><c> handles</c><00:03:05.200><c> a</c><00:03:06.450><c> part</c>

00:03:07.440 --> 00:03:07.450 align:start position:0%
really useful because it handles a part
 

00:03:07.450 --> 00:03:09.839 align:start position:0%
really useful because it handles a part
of<00:03:07.689><c> the</c><00:03:08.260><c> problems</c><00:03:08.709><c> it</c><00:03:09.040><c> solves</c><00:03:09.250><c> part</c><00:03:09.639><c> of</c><00:03:09.760><c> the</c>

00:03:09.839 --> 00:03:09.849 align:start position:0%
of the problems it solves part of the
 

00:03:09.849 --> 00:03:12.030 align:start position:0%
of the problems it solves part of the
problems<00:03:10.269><c> that</c><00:03:10.359><c> we</c><00:03:10.569><c> we</c><00:03:11.109><c> have</c><00:03:11.290><c> to</c><00:03:11.319><c> solve</c><00:03:11.650><c> when</c>

00:03:12.030 --> 00:03:12.040 align:start position:0%
problems that we we have to solve when
 

00:03:12.040 --> 00:03:14.220 align:start position:0%
problems that we we have to solve when
building<00:03:12.280><c> a</c><00:03:12.430><c> large-scale</c><00:03:12.669><c> systems</c><00:03:13.299><c> so</c><00:03:14.200><c> that</c>

00:03:14.220 --> 00:03:14.230 align:start position:0%
building a large-scale systems so that
 

00:03:14.230 --> 00:03:16.500 align:start position:0%
building a large-scale systems so that
we<00:03:14.769><c> don't</c><00:03:15.040><c> have</c><00:03:15.129><c> to</c><00:03:15.250><c> worry</c><00:03:15.939><c> about</c><00:03:16.209><c> that</c>

00:03:16.500 --> 00:03:16.510 align:start position:0%
we don't have to worry about that
 

00:03:16.510 --> 00:03:18.569 align:start position:0%
we don't have to worry about that
particular<00:03:16.930><c> area</c><00:03:17.109><c> and</c><00:03:17.409><c> we</c><00:03:17.500><c> can</c><00:03:17.650><c> focus</c><00:03:17.859><c> on</c><00:03:18.250><c> the</c>

00:03:18.569 --> 00:03:18.579 align:start position:0%
particular area and we can focus on the
 

00:03:18.579 --> 00:03:20.429 align:start position:0%
particular area and we can focus on the
other<00:03:18.730><c> things</c><00:03:18.970><c> that</c><00:03:19.030><c> matter</c><00:03:19.329><c> because</c><00:03:20.200><c> it</c>

00:03:20.429 --> 00:03:20.439 align:start position:0%
other things that matter because it
 

00:03:20.439 --> 00:03:22.890 align:start position:0%
other things that matter because it
solves<00:03:20.680><c> these</c><00:03:20.769><c> problems</c><00:03:21.239><c> compile</c><00:03:22.239><c> time</c><00:03:22.480><c> so</c><00:03:22.780><c> we</c>

00:03:22.890 --> 00:03:22.900 align:start position:0%
solves these problems compile time so we
 

00:03:22.900 --> 00:03:25.199 align:start position:0%
solves these problems compile time so we
don't<00:03:23.019><c> run</c><00:03:23.290><c> into</c><00:03:23.530><c> them</c><00:03:23.879><c> during</c><00:03:24.879><c> during</c>

00:03:25.199 --> 00:03:25.209 align:start position:0%
don't run into them during during
 

00:03:25.209 --> 00:03:33.869 align:start position:0%
don't run into them during during
runtime<00:03:25.510><c> I</c><00:03:32.340><c> really</c><00:03:33.340><c> like</c><00:03:33.519><c> that</c><00:03:33.669><c> the</c>

00:03:33.869 --> 00:03:33.879 align:start position:0%
runtime I really like that the
 

00:03:33.879 --> 00:03:35.309 align:start position:0%
runtime I really like that the
conference<00:03:34.299><c> brings</c><00:03:34.599><c> together</c><00:03:34.840><c> people</c><00:03:35.139><c> from</c>

00:03:35.309 --> 00:03:35.319 align:start position:0%
conference brings together people from
 

00:03:35.319 --> 00:03:37.649 align:start position:0%
conference brings together people from
multiple<00:03:36.010><c> areas</c><00:03:36.250><c> that</c><00:03:36.819><c> are</c><00:03:36.969><c> sold</c><00:03:37.239><c> sort</c><00:03:37.569><c> of</c>

00:03:37.649 --> 00:03:37.659 align:start position:0%
multiple areas that are sold sort of
 

00:03:37.659 --> 00:03:39.959 align:start position:0%
multiple areas that are sold sort of
connected<00:03:38.079><c> also</c><00:03:38.799><c> functional</c><00:03:39.579><c> programming</c>

00:03:39.959 --> 00:03:39.969 align:start position:0%
connected also functional programming
 

00:03:39.969 --> 00:03:42.890 align:start position:0%
connected also functional programming
machine<00:03:40.959><c> learning</c><00:03:41.319><c> and</c><00:03:41.590><c> data</c><00:03:42.069><c> science</c><00:03:42.639><c> and</c>

00:03:42.890 --> 00:03:42.900 align:start position:0%
machine learning and data science and
 

00:03:42.900 --> 00:03:45.390 align:start position:0%
machine learning and data science and
reactive<00:03:43.900><c> because</c><00:03:44.319><c> they</c><00:03:44.590><c> work</c><00:03:45.099><c> really</c>

00:03:45.390 --> 00:03:45.400 align:start position:0%
reactive because they work really
 

00:03:45.400 --> 00:03:47.399 align:start position:0%
reactive because they work really
closely<00:03:45.790><c> together</c><00:03:46.120><c> although</c><00:03:46.810><c> they</c><00:03:47.169><c> may</c><00:03:47.379><c> not</c>

00:03:47.399 --> 00:03:47.409 align:start position:0%
closely together although they may not
 

00:03:47.409 --> 00:03:49.860 align:start position:0%
closely together although they may not
not<00:03:47.769><c> be</c><00:03:47.949><c> realizing</c><00:03:48.459><c> it</c><00:03:48.549><c> immediately</c><00:03:48.909><c> so</c><00:03:49.840><c> I</c>

00:03:49.860 --> 00:03:49.870 align:start position:0%
not be realizing it immediately so I
 

00:03:49.870 --> 00:03:53.099 align:start position:0%
not be realizing it immediately so I
like<00:03:50.079><c> and</c><00:03:50.620><c> the</c><00:03:50.979><c> other</c><00:03:51.099><c> thing</c><00:03:51.280><c> I</c><00:03:51.370><c> like</c><00:03:51.579><c> is</c><00:03:52.109><c> there</c>

00:03:53.099 --> 00:03:53.109 align:start position:0%
like and the other thing I like is there
 

00:03:53.109 --> 00:03:54.689 align:start position:0%
like and the other thing I like is there
are<00:03:53.260><c> many</c><00:03:53.560><c> interesting</c><00:03:53.979><c> talks</c><00:03:54.459><c> and</c>

00:03:54.689 --> 00:03:54.699 align:start position:0%
are many interesting talks and
 

00:03:54.699 --> 00:03:56.819 align:start position:0%
are many interesting talks and
conversations<00:03:54.760><c> about</c><00:03:55.510><c> new</c><00:03:55.930><c> technologies</c><00:03:56.560><c> and</c>

00:03:56.819 --> 00:03:56.829 align:start position:0%
conversations about new technologies and
 

00:03:56.829 --> 00:03:59.610 align:start position:0%
conversations about new technologies and
and<00:03:57.159><c> new</c><00:03:57.489><c> niche</c><00:03:57.879><c> markets</c><00:03:58.840><c> and</c><00:03:59.079><c> and</c><00:03:59.409><c> new</c>

00:03:59.610 --> 00:03:59.620 align:start position:0%
and new niche markets and and new
 

00:03:59.620 --> 00:04:01.530 align:start position:0%
and new niche markets and and new
upcoming<00:04:00.129><c> solutions</c><00:04:00.639><c> and</c><00:04:00.849><c> the</c><00:04:00.939><c> future</c><00:04:01.299><c> which</c>

00:04:01.530 --> 00:04:01.540 align:start position:0%
upcoming solutions and the future which
 

00:04:01.540 --> 00:04:04.439 align:start position:0%
upcoming solutions and the future which
is<00:04:01.569><c> really</c><00:04:02.019><c> really</c><00:04:02.139><c> interesting</c>