WEBVTT
Kind: captions
Language: en

00:00:09.200 --> 00:00:11.430 align:start position:0%
 
So,<00:00:09.599><c> my</c><00:00:09.840><c> name</c><00:00:09.920><c> is</c><00:00:10.160><c> Michael</c><00:00:10.559><c> Maxmillion.</c><00:00:11.200><c> I</c><00:00:11.360><c> go</c>

00:00:11.430 --> 00:00:11.440 align:start position:0%
So, my name is Michael Maxmillion. I go
 

00:00:11.440 --> 00:00:15.509 align:start position:0%
So, my name is Michael Maxmillion. I go
by<00:00:11.679><c> Max,</c><00:00:13.120><c> sometimes</c><00:00:13.599><c> Dr.</c><00:00:13.920><c> Max.</c><00:00:14.719><c> But</c><00:00:14.880><c> I</c><00:00:15.120><c> used</c><00:00:15.280><c> to</c>

00:00:15.509 --> 00:00:15.519 align:start position:0%
by Max, sometimes Dr. Max. But I used to
 

00:00:15.519 --> 00:00:18.390 align:start position:0%
by Max, sometimes Dr. Max. But I used to
work<00:00:15.839><c> at</c><00:00:16.160><c> IBM</c><00:00:16.720><c> research</c><00:00:17.359><c> for</c><00:00:17.680><c> a</c><00:00:17.920><c> pretty</c><00:00:18.240><c> long</c>

00:00:18.390 --> 00:00:18.400 align:start position:0%
work at IBM research for a pretty long
 

00:00:18.400 --> 00:00:22.550 align:start position:0%
work at IBM research for a pretty long
time.<00:00:18.640><c> And</c><00:00:18.800><c> I</c><00:00:19.039><c> just</c><00:00:19.920><c> left</c><00:00:20.320><c> IBM</c><00:00:21.600><c> and</c><00:00:22.160><c> to</c><00:00:22.400><c> start</c>

00:00:22.550 --> 00:00:22.560 align:start position:0%
time. And I just left IBM and to start
 

00:00:22.560 --> 00:00:24.710 align:start position:0%
time. And I just left IBM and to start
my<00:00:22.800><c> own</c><00:00:22.960><c> company</c><00:00:23.279><c> and</c><00:00:23.519><c> of</c><00:00:23.680><c> course</c><00:00:24.000><c> uh</c><00:00:24.160><c> NAI</c>

00:00:24.710 --> 00:00:24.720 align:start position:0%
my own company and of course uh NAI
 

00:00:24.720 --> 00:00:27.830 align:start position:0%
my own company and of course uh NAI
company.<00:00:25.279><c> It's</c><00:00:25.600><c> uh</c><00:00:25.760><c> my</c><00:00:26.000><c> last</c><00:00:26.240><c> name.ai.</c><00:00:27.680><c> So,</c>

00:00:27.830 --> 00:00:27.840 align:start position:0%
company. It's uh my last name.ai. So,
 

00:00:27.840 --> 00:00:31.669 align:start position:0%
company. It's uh my last name.ai. So,
maxmillion.ai.<00:00:29.199><c> And</c><00:00:29.760><c> uh</c><00:00:30.480><c> yeah</c><00:00:30.960><c> so</c><00:00:31.279><c> I'm</c><00:00:31.519><c> a</c>

00:00:31.669 --> 00:00:31.679 align:start position:0%
maxmillion.ai. And uh yeah so I'm a
 

00:00:31.679 --> 00:00:33.750 align:start position:0%
maxmillion.ai. And uh yeah so I'm a
founder

00:00:33.750 --> 00:00:33.760 align:start position:0%
founder
 

00:00:33.760 --> 00:00:36.950 align:start position:0%
founder
you<00:00:33.920><c> know</c><00:00:34.160><c> when</c><00:00:34.399><c> I</c><00:00:34.640><c> when</c><00:00:34.960><c> I</c><00:00:35.280><c> did</c><00:00:35.840><c> uh</c><00:00:36.559><c> graduate</c>

00:00:36.950 --> 00:00:36.960 align:start position:0%
you know when I when I did uh graduate
 

00:00:36.960 --> 00:00:40.790 align:start position:0%
you know when I when I did uh graduate
school<00:00:37.680><c> 20</c><00:00:38.000><c> years</c><00:00:38.160><c> ago</c><00:00:39.440><c> um</c><00:00:39.840><c> one</c><00:00:40.079><c> of</c><00:00:40.160><c> the</c><00:00:40.399><c> topic</c>

00:00:40.790 --> 00:00:40.800 align:start position:0%
school 20 years ago um one of the topic
 

00:00:40.800 --> 00:00:44.709 align:start position:0%
school 20 years ago um one of the topic
I<00:00:41.520><c> focused</c><00:00:41.840><c> on</c><00:00:42.079><c> was</c><00:00:42.320><c> on</c><00:00:42.559><c> AI</c><00:00:42.960><c> agents</c><00:00:44.239><c> uh</c><00:00:44.399><c> as</c><00:00:44.640><c> a</c>

00:00:44.709 --> 00:00:44.719 align:start position:0%
I focused on was on AI agents uh as a
 

00:00:44.719 --> 00:00:47.510 align:start position:0%
I focused on was on AI agents uh as a
matter<00:00:44.879><c> of</c><00:00:44.960><c> fact</c><00:00:45.120><c> my</c><00:00:45.440><c> PhD</c><00:00:46.000><c> work</c><00:00:46.239><c> was</c><00:00:46.480><c> on</c><00:00:46.719><c> that</c>

00:00:47.510 --> 00:00:47.520 align:start position:0%
matter of fact my PhD work was on that
 

00:00:47.520 --> 00:00:50.869 align:start position:0%
matter of fact my PhD work was on that
uh<00:00:47.680><c> and</c><00:00:47.920><c> that</c><00:00:48.160><c> was</c><00:00:48.320><c> 20</c><00:00:48.480><c> years</c><00:00:48.640><c> ago.</c><00:00:49.520><c> So</c><00:00:50.559><c> for</c>

00:00:50.869 --> 00:00:50.879 align:start position:0%
uh and that was 20 years ago. So for
 

00:00:50.879 --> 00:00:53.590 align:start position:0%
uh and that was 20 years ago. So for
fast<00:00:51.200><c> forward</c><00:00:51.520><c> 20</c><00:00:51.840><c> years,</c><00:00:52.719><c> uh</c><00:00:53.120><c> two</c><00:00:53.280><c> or</c><00:00:53.440><c> three</c>

00:00:53.590 --> 00:00:53.600 align:start position:0%
fast forward 20 years, uh two or three
 

00:00:53.600 --> 00:00:56.310 align:start position:0%
fast forward 20 years, uh two or three
years<00:00:53.760><c> ago,</c><00:00:55.039><c> um</c><00:00:55.600><c> you</c><00:00:55.760><c> know,</c><00:00:55.920><c> of</c><00:00:56.079><c> course,</c>

00:00:56.310 --> 00:00:56.320 align:start position:0%
years ago, um you know, of course,
 

00:00:56.320 --> 00:00:58.950 align:start position:0%
years ago, um you know, of course,
agents<00:00:56.800><c> has</c><00:00:57.120><c> become</c><00:00:57.600><c> kind</c><00:00:57.840><c> of</c><00:00:57.920><c> like</c><00:00:58.160><c> the</c><00:00:58.480><c> the</c>

00:00:58.950 --> 00:00:58.960 align:start position:0%
agents has become kind of like the the
 

00:00:58.960 --> 00:01:01.750 align:start position:0%
agents has become kind of like the the
hot<00:00:59.199><c> thing</c><00:00:59.520><c> this</c><00:00:59.760><c> year,</c><00:01:00.079><c> but</c><00:01:00.399><c> it</c><00:01:01.039><c> slowly</c><00:01:01.520><c> was</c>

00:01:01.750 --> 00:01:01.760 align:start position:0%
hot thing this year, but it slowly was
 

00:01:01.760 --> 00:01:06.390 align:start position:0%
hot thing this year, but it slowly was
creeping<00:01:02.160><c> up.</c><00:01:03.199><c> And</c><00:01:03.760><c> uh</c><00:01:04.479><c> on</c><00:01:04.720><c> AI,</c><00:01:05.600><c> we</c><00:01:05.920><c> started</c><00:01:06.159><c> at</c>

00:01:06.390 --> 00:01:06.400 align:start position:0%
creeping up. And uh on AI, we started at
 

00:01:06.400 --> 00:01:10.789 align:start position:0%
creeping up. And uh on AI, we started at
IBM<00:01:07.119><c> a</c><00:01:07.439><c> group</c><00:01:08.320><c> called</c><00:01:08.880><c> AI</c><00:01:09.280><c> for</c><00:01:09.520><c> quantum</c><00:01:10.479><c> that</c>

00:01:10.789 --> 00:01:10.799 align:start position:0%
IBM a group called AI for quantum that
 

00:01:10.799 --> 00:01:12.870 align:start position:0%
IBM a group called AI for quantum that
essentially<00:01:11.280><c> helped</c><00:01:12.080><c> uh</c><00:01:12.240><c> the</c><00:01:12.400><c> quantum</c>

00:01:12.870 --> 00:01:12.880 align:start position:0%
essentially helped uh the quantum
 

00:01:12.880 --> 00:01:16.870 align:start position:0%
essentially helped uh the quantum
division<00:01:13.439><c> at</c><00:01:13.680><c> IBM</c><00:01:14.400><c> use</c><00:01:14.640><c> AI.</c><00:01:15.840><c> And</c><00:01:16.080><c> probably</c><00:01:16.560><c> the</c>

00:01:16.870 --> 00:01:16.880 align:start position:0%
division at IBM use AI. And probably the
 

00:01:16.880 --> 00:01:19.190 align:start position:0%
division at IBM use AI. And probably the
thing<00:01:16.960><c> that</c><00:01:17.119><c> I'm</c><00:01:17.360><c> most</c><00:01:18.080><c> proud</c><00:01:18.320><c> of</c><00:01:18.560><c> is</c><00:01:18.799><c> what</c><00:01:18.960><c> I'm</c>

00:01:19.190 --> 00:01:19.200 align:start position:0%
thing that I'm most proud of is what I'm
 

00:01:19.200 --> 00:01:21.350 align:start position:0%
thing that I'm most proud of is what I'm
showing<00:01:19.520><c> today</c><00:01:19.759><c> at</c><00:01:20.000><c> the</c><00:01:20.159><c> conference.</c><00:01:20.720><c> It's</c><00:01:20.960><c> a</c>

00:01:21.350 --> 00:01:21.360 align:start position:0%
showing today at the conference. It's a
 

00:01:21.360 --> 00:01:24.710 align:start position:0%
showing today at the conference. It's a
it's<00:01:21.680><c> a</c><00:01:22.000><c> tool</c><00:01:23.360><c> called</c><00:01:23.600><c> WeCave</c><00:01:24.000><c> CLI.</c><00:01:24.400><c> It's</c><00:01:24.560><c> an</c>

00:01:24.710 --> 00:01:24.720 align:start position:0%
it's a tool called WeCave CLI. It's an
 

00:01:24.720 --> 00:01:27.109 align:start position:0%
it's a tool called WeCave CLI. It's an
open<00:01:24.960><c> source</c><00:01:25.200><c> tool</c><00:01:26.080><c> that</c><00:01:26.560><c> basically</c>

00:01:27.109 --> 00:01:27.119 align:start position:0%
open source tool that basically
 

00:01:27.119 --> 00:01:30.789 align:start position:0%
open source tool that basically
standardizes<00:01:28.320><c> uh</c><00:01:28.400><c> vector</c><00:01:28.799><c> databases.</c><00:01:30.159><c> Uh</c><00:01:30.560><c> so</c>

00:01:30.789 --> 00:01:30.799 align:start position:0%
standardizes uh vector databases. Uh so
 

00:01:30.799 --> 00:01:34.710 align:start position:0%
standardizes uh vector databases. Uh so
it<00:01:31.119><c> allows</c><00:01:31.439><c> you</c><00:01:31.680><c> to</c><00:01:32.079><c> to</c><00:01:32.640><c> basically</c><00:01:33.200><c> manage</c><00:01:34.560><c> you</c>

00:01:34.710 --> 00:01:34.720 align:start position:0%
it allows you to to basically manage you
 

00:01:34.720 --> 00:01:37.590 align:start position:0%
it allows you to to basically manage you
know<00:01:35.280><c> in</c><00:01:35.600><c> development</c><00:01:36.240><c> test</c><00:01:36.560><c> and</c><00:01:36.799><c> production</c>

00:01:37.590 --> 00:01:37.600 align:start position:0%
know in development test and production
 

00:01:37.600 --> 00:01:40.469 align:start position:0%
know in development test and production
your<00:01:37.920><c> vector</c><00:01:38.320><c> database</c><00:01:39.520><c> and</c><00:01:39.759><c> it</c><00:01:40.000><c> does</c><00:01:40.159><c> it</c><00:01:40.320><c> in</c>

00:01:40.469 --> 00:01:40.479 align:start position:0%
your vector database and it does it in
 

00:01:40.479 --> 00:01:43.190 align:start position:0%
your vector database and it does it in
such<00:01:40.640><c> a</c><00:01:40.880><c> way</c><00:01:40.960><c> that</c><00:01:41.200><c> it's</c><00:01:41.360><c> it's</c><00:01:41.759><c> super</c><00:01:42.079><c> fast</c><00:01:42.640><c> and</c>

00:01:43.190 --> 00:01:43.200 align:start position:0%
such a way that it's it's super fast and
 

00:01:43.200 --> 00:01:45.350 align:start position:0%
such a way that it's it's super fast and
it's<00:01:43.680><c> compatible</c><00:01:44.240><c> with</c><00:01:44.720><c> different</c><00:01:45.040><c> vector</c>

00:01:45.350 --> 00:01:45.360 align:start position:0%
it's compatible with different vector
 

00:01:45.360 --> 00:01:47.910 align:start position:0%
it's compatible with different vector
database<00:01:45.840><c> right</c><00:01:46.000><c> now</c><00:01:46.960><c> and</c><00:01:47.200><c> it</c><00:01:47.360><c> makes</c><00:01:47.520><c> it</c><00:01:47.680><c> very</c>

00:01:47.910 --> 00:01:47.920 align:start position:0%
database right now and it makes it very
 

00:01:47.920 --> 00:01:50.069 align:start position:0%
database right now and it makes it very
easy<00:01:48.079><c> for</c><00:01:48.240><c> you</c><00:01:48.399><c> to</c><00:01:48.640><c> sort</c><00:01:48.799><c> of</c><00:01:49.040><c> experiment</c><00:01:49.759><c> with</c>

00:01:50.069 --> 00:01:50.079 align:start position:0%
easy for you to sort of experiment with
 

00:01:50.079 --> 00:01:52.950 align:start position:0%
easy for you to sort of experiment with
your<00:01:50.399><c> vector</c><00:01:50.799><c> database</c><00:01:51.680><c> your</c><00:01:51.920><c> embeddings</c><00:01:52.720><c> the</c>

00:01:52.950 --> 00:01:52.960 align:start position:0%
your vector database your embeddings the
 

00:01:52.960 --> 00:01:54.710 align:start position:0%
your vector database your embeddings the
queries<00:01:53.600><c> the</c><00:01:53.840><c> results</c><00:01:54.159><c> that</c><00:01:54.320><c> you're</c><00:01:54.560><c> getting</c>

00:01:54.710 --> 00:01:54.720 align:start position:0%
queries the results that you're getting
 

00:01:54.720 --> 00:01:56.149 align:start position:0%
queries the results that you're getting
and<00:01:54.880><c> so</c><00:01:55.040><c> on</c><00:01:55.200><c> so</c><00:01:55.360><c> that</c><00:01:55.520><c> when</c><00:01:55.680><c> you</c><00:01:55.759><c> build</c><00:01:55.920><c> your</c>

00:01:56.149 --> 00:01:56.159 align:start position:0%
and so on so that when you build your
 

00:01:56.159 --> 00:01:59.990 align:start position:0%
and so on so that when you build your
agents<00:01:57.119><c> you</c><00:01:57.360><c> can</c><00:01:57.520><c> have</c><00:01:57.600><c> the</c><00:01:57.920><c> best</c><00:01:58.320><c> data</c><00:01:59.200><c> uh</c><00:01:59.280><c> for</c>

00:01:59.990 --> 00:02:00.000 align:start position:0%
agents you can have the best data uh for
 

00:02:00.000 --> 00:02:03.109 align:start position:0%
agents you can have the best data uh for
So<00:02:00.560><c> just</c><00:02:01.040><c> talking</c><00:02:01.439><c> about</c><00:02:01.680><c> this</c><00:02:02.159><c> weave</c><00:02:02.479><c> CLI.</c><00:02:02.880><c> So</c>

00:02:03.109 --> 00:02:03.119 align:start position:0%
So just talking about this weave CLI. So
 

00:02:03.119 --> 00:02:04.789 align:start position:0%
So just talking about this weave CLI. So
one<00:02:03.280><c> of</c><00:02:03.360><c> the</c><00:02:03.520><c> problems</c><00:02:03.840><c> that</c><00:02:04.079><c> you</c><00:02:04.320><c> end</c><00:02:04.479><c> up</c><00:02:04.560><c> with</c>

00:02:04.789 --> 00:02:04.799 align:start position:0%
one of the problems that you end up with
 

00:02:04.799 --> 00:02:06.630 align:start position:0%
one of the problems that you end up with
when<00:02:04.960><c> you</c><00:02:05.119><c> build</c><00:02:05.360><c> agents</c><00:02:06.000><c> like</c><00:02:06.240><c> for</c><00:02:06.399><c> instance</c>

00:02:06.630 --> 00:02:06.640 align:start position:0%
when you build agents like for instance
 

00:02:06.640 --> 00:02:09.589 align:start position:0%
when you build agents like for instance
a<00:02:06.880><c> rag</c><00:02:07.280><c> agents</c><00:02:07.759><c> so</c><00:02:08.319><c> retrieval</c><00:02:08.959><c> augmented</c>

00:02:09.589 --> 00:02:09.599 align:start position:0%
a rag agents so retrieval augmented
 

00:02:09.599 --> 00:02:12.710 align:start position:0%
a rag agents so retrieval augmented
generation<00:02:10.800><c> is</c><00:02:11.120><c> that</c><00:02:11.520><c> you</c><00:02:11.760><c> may</c><00:02:11.920><c> be</c><00:02:12.080><c> able</c><00:02:12.239><c> to</c>

00:02:12.710 --> 00:02:12.720 align:start position:0%
generation is that you may be able to
 

00:02:12.720 --> 00:02:16.630 align:start position:0%
generation is that you may be able to
query<00:02:13.200><c> it</c><00:02:13.840><c> on</c><00:02:14.560><c> a</c><00:02:14.800><c> collection</c><00:02:15.120><c> of</c><00:02:15.360><c> data</c><00:02:16.080><c> and</c><00:02:16.400><c> get</c>

00:02:16.630 --> 00:02:16.640 align:start position:0%
query it on a collection of data and get
 

00:02:16.640 --> 00:02:19.030 align:start position:0%
query it on a collection of data and get
different<00:02:16.959><c> results.</c><00:02:17.920><c> Okay.</c><00:02:18.560><c> And</c><00:02:18.720><c> now</c>

00:02:19.030 --> 00:02:19.040 align:start position:0%
different results. Okay. And now
 

00:02:19.040 --> 00:02:20.869 align:start position:0%
different results. Okay. And now
sometimes<00:02:19.360><c> that's</c><00:02:19.599><c> good</c><00:02:19.840><c> and</c><00:02:20.080><c> but</c><00:02:20.400><c> sometimes</c>

00:02:20.869 --> 00:02:20.879 align:start position:0%
sometimes that's good and but sometimes
 

00:02:20.879 --> 00:02:22.470 align:start position:0%
sometimes that's good and but sometimes
most<00:02:21.120><c> of</c><00:02:21.200><c> the</c><00:02:21.360><c> time</c><00:02:21.599><c> you</c><00:02:21.840><c> want</c><00:02:22.000><c> it</c><00:02:22.160><c> to</c><00:02:22.319><c> be</c>

00:02:22.470 --> 00:02:22.480 align:start position:0%
most of the time you want it to be
 

00:02:22.480 --> 00:02:25.830 align:start position:0%
most of the time you want it to be
pretty<00:02:22.959><c> precise</c><00:02:23.920><c> you</c><00:02:24.080><c> know.</c><00:02:24.319><c> So</c><00:02:25.040><c> in</c><00:02:25.200><c> the</c><00:02:25.440><c> cases</c>

00:02:25.830 --> 00:02:25.840 align:start position:0%
pretty precise you know. So in the cases
 

00:02:25.840 --> 00:02:28.949 align:start position:0%
pretty precise you know. So in the cases
where<00:02:26.239><c> you</c><00:02:26.560><c> want</c><00:02:26.720><c> your</c><00:02:27.040><c> agent</c><00:02:27.520><c> to</c><00:02:27.760><c> have</c><00:02:28.640><c> uh</c><00:02:28.879><c> at</c>

00:02:28.949 --> 00:02:28.959 align:start position:0%
where you want your agent to have uh at
 

00:02:28.959 --> 00:02:33.270 align:start position:0%
where you want your agent to have uh at
least<00:02:29.599><c> not</c><00:02:30.239><c> elucinate</c><00:02:30.879><c> a</c><00:02:31.120><c> lot</c><00:02:31.280><c> or</c><00:02:31.680><c> have</c><00:02:33.040><c> uh</c>

00:02:33.270 --> 00:02:33.280 align:start position:0%
least not elucinate a lot or have uh
 

00:02:33.280 --> 00:02:36.390 align:start position:0%
least not elucinate a lot or have uh
more<00:02:33.519><c> predictable</c><00:02:34.640><c> answers</c><00:02:35.760><c> then</c><00:02:36.080><c> you</c><00:02:36.239><c> have</c>

00:02:36.390 --> 00:02:36.400 align:start position:0%
more predictable answers then you have
 

00:02:36.400 --> 00:02:38.470 align:start position:0%
more predictable answers then you have
to<00:02:36.560><c> work</c><00:02:36.959><c> hard.</c><00:02:37.519><c> So</c><00:02:37.760><c> one</c><00:02:37.920><c> of</c><00:02:38.000><c> the</c><00:02:38.160><c> things</c><00:02:38.239><c> that</c>

00:02:38.470 --> 00:02:38.480 align:start position:0%
to work hard. So one of the things that
 

00:02:38.480 --> 00:02:40.550 align:start position:0%
to work hard. So one of the things that
I<00:02:38.640><c> try</c><00:02:38.800><c> to</c><00:02:38.879><c> do</c><00:02:39.040><c> with</c><00:02:39.200><c> weave</c><00:02:39.519><c> CLI</c><00:02:39.920><c> is</c><00:02:40.080><c> to</c><00:02:40.239><c> allow</c>

00:02:40.550 --> 00:02:40.560 align:start position:0%
I try to do with weave CLI is to allow
 

00:02:40.560 --> 00:02:43.270 align:start position:0%
I try to do with weave CLI is to allow
you<00:02:40.800><c> different</c><00:02:41.280><c> ways</c><00:02:41.599><c> for</c><00:02:41.840><c> you</c><00:02:42.080><c> to</c><00:02:42.239><c> do</c><00:02:42.400><c> your</c>

00:02:43.270 --> 00:02:43.280 align:start position:0%
you different ways for you to do your
 

00:02:43.280 --> 00:02:44.949 align:start position:0%
you different ways for you to do your
embedding.<00:02:43.920><c> So</c><00:02:44.080><c> you</c><00:02:44.239><c> can</c><00:02:44.400><c> experiment</c><00:02:44.800><c> with</c>

00:02:44.949 --> 00:02:44.959 align:start position:0%
embedding. So you can experiment with
 

00:02:44.959 --> 00:02:47.750 align:start position:0%
embedding. So you can experiment with
that.<00:02:45.519><c> You</c><00:02:45.680><c> can</c><00:02:45.840><c> experiment</c><00:02:46.400><c> also</c><00:02:46.800><c> on</c><00:02:47.120><c> how</c><00:02:47.519><c> the</c>

00:02:47.750 --> 00:02:47.760 align:start position:0%
that. You can experiment also on how the
 

00:02:47.760 --> 00:02:49.910 align:start position:0%
that. You can experiment also on how the
data<00:02:48.080><c> is</c><00:02:48.239><c> being</c><00:02:48.480><c> chunked.</c><00:02:48.959><c> So</c><00:02:49.200><c> divide</c><00:02:49.440><c> it</c><00:02:49.680><c> into</c>

00:02:49.910 --> 00:02:49.920 align:start position:0%
data is being chunked. So divide it into
 

00:02:49.920 --> 00:02:52.630 align:start position:0%
data is being chunked. So divide it into
smaller<00:02:50.160><c> pieces</c><00:02:50.800><c> because</c><00:02:51.040><c> that</c><00:02:51.360><c> will</c><00:02:52.000><c> impact</c>

00:02:52.630 --> 00:02:52.640 align:start position:0%
smaller pieces because that will impact
 

00:02:52.640 --> 00:02:55.509 align:start position:0%
smaller pieces because that will impact
the<00:02:52.959><c> results</c><00:02:53.360><c> that</c><00:02:53.599><c> you</c><00:02:53.840><c> get</c><00:02:54.560><c> and</c><00:02:54.959><c> you</c><00:02:55.280><c> can</c>

00:02:55.509 --> 00:02:55.519 align:start position:0%
the results that you get and you can
 

00:02:55.519 --> 00:02:59.990 align:start position:0%
the results that you get and you can
also<00:02:56.480><c> uh</c><00:02:56.800><c> change</c><00:02:57.200><c> the</c><00:02:57.519><c> algorithms</c><00:02:58.800><c> that</c><00:02:59.760><c> uh</c>

00:02:59.990 --> 00:03:00.000 align:start position:0%
also uh change the algorithms that uh
 

00:03:00.000 --> 00:03:01.990 align:start position:0%
also uh change the algorithms that uh
the<00:03:00.239><c> agent</c><00:03:00.640><c> will</c><00:03:00.879><c> use</c><00:03:01.200><c> or</c><00:03:01.519><c> at</c><00:03:01.599><c> least</c><00:03:01.840><c> the</c>

00:03:01.990 --> 00:03:02.000 align:start position:0%
the agent will use or at least the
 

00:03:02.000 --> 00:03:03.750 align:start position:0%
the agent will use or at least the
vector<00:03:02.239><c> database</c><00:03:02.640><c> will</c><00:03:02.800><c> use</c><00:03:02.959><c> to</c><00:03:03.200><c> search.</c><00:03:03.599><c> So</c>

00:03:03.750 --> 00:03:03.760 align:start position:0%
vector database will use to search. So
 

00:03:03.760 --> 00:03:06.470 align:start position:0%
vector database will use to search. So
when<00:03:03.920><c> you</c><00:03:04.000><c> give</c><00:03:04.159><c> it</c><00:03:04.319><c> a</c><00:03:04.480><c> query</c><00:03:05.200><c> the</c><00:03:05.519><c> search</c><00:03:06.239><c> you</c>

00:03:06.470 --> 00:03:06.480 align:start position:0%
when you give it a query the search you
 

00:03:06.480 --> 00:03:09.190 align:start position:0%
when you give it a query the search you
can<00:03:06.720><c> change</c><00:03:07.280><c> the</c><00:03:07.519><c> the</c><00:03:07.680><c> the</c><00:03:08.159><c> parameters</c><00:03:08.959><c> and</c>

00:03:09.190 --> 00:03:09.200 align:start position:0%
can change the the the parameters and
 

00:03:09.200 --> 00:03:10.390 align:start position:0%
can change the the the parameters and
because<00:03:09.519><c> we're</c><00:03:09.840><c> supporting</c><00:03:10.159><c> different</c>

00:03:10.390 --> 00:03:10.400 align:start position:0%
because we're supporting different
 

00:03:10.400 --> 00:03:13.030 align:start position:0%
because we're supporting different
databases<00:03:11.120><c> you</c><00:03:11.360><c> can</c><00:03:11.760><c> run</c><00:03:12.000><c> the</c><00:03:12.319><c> same</c><00:03:12.640><c> test</c>

00:03:13.030 --> 00:03:13.040 align:start position:0%
databases you can run the same test
 

00:03:13.040 --> 00:03:15.509 align:start position:0%
databases you can run the same test
across<00:03:13.519><c> different</c><00:03:13.760><c> database.</c><00:03:14.239><c> Reliable</c><00:03:15.120><c> AI</c>

00:03:15.509 --> 00:03:15.519 align:start position:0%
across different database. Reliable AI
 

00:03:15.519 --> 00:03:19.110 align:start position:0%
across different database. Reliable AI
for<00:03:15.680><c> me</c><00:03:15.840><c> is</c><00:03:16.400><c> if</c><00:03:17.519><c> what</c><00:03:17.760><c> you're</c><00:03:18.000><c> building</c><00:03:18.879><c> you</c>

00:03:19.110 --> 00:03:19.120 align:start position:0%
for me is if what you're building you
 

00:03:19.120 --> 00:03:21.670 align:start position:0%
for me is if what you're building you
want<00:03:19.200><c> it</c><00:03:19.360><c> to</c><00:03:19.519><c> be</c><00:03:19.920><c> more</c><00:03:20.159><c> precise</c><00:03:21.120><c> then</c><00:03:21.360><c> you</c><00:03:21.519><c> can</c>

00:03:21.670 --> 00:03:21.680 align:start position:0%
want it to be more precise then you can
 

00:03:21.680 --> 00:03:23.750 align:start position:0%
want it to be more precise then you can
use<00:03:21.840><c> something</c><00:03:22.080><c> like</c><00:03:22.319><c> wave</c><00:03:22.640><c> CLI</c><00:03:23.519><c> to</c>

00:03:23.750 --> 00:03:23.760 align:start position:0%
use something like wave CLI to
 

00:03:23.760 --> 00:03:26.229 align:start position:0%
use something like wave CLI to
experiment<00:03:24.879><c> before</c><00:03:25.200><c> you</c><00:03:25.440><c> go</c><00:03:25.519><c> into</c><00:03:25.840><c> production</c>

00:03:26.229 --> 00:03:26.239 align:start position:0%
experiment before you go into production
 

00:03:26.239 --> 00:03:27.830 align:start position:0%
experiment before you go into production
so<00:03:26.400><c> that</c><00:03:26.640><c> when</c><00:03:26.800><c> you</c><00:03:26.879><c> go</c><00:03:26.959><c> in</c><00:03:27.200><c> production</c><00:03:27.599><c> the</c>

00:03:27.830 --> 00:03:27.840 align:start position:0%
so that when you go in production the
 

00:03:27.840 --> 00:03:29.589 align:start position:0%
so that when you go in production the
results<00:03:28.159><c> are</c><00:03:28.319><c> more</c><00:03:28.560><c> predictable.</c><00:03:29.360><c> So</c>

00:03:29.589 --> 00:03:29.599 align:start position:0%
results are more predictable. So
 

00:03:29.599 --> 00:03:32.309 align:start position:0%
results are more predictable. So
predictability<00:03:30.400><c> I</c><00:03:30.640><c> think</c><00:03:30.799><c> is</c><00:03:30.959><c> is</c><00:03:31.040><c> is</c><00:03:31.920><c> what</c>

00:03:32.309 --> 00:03:32.319 align:start position:0%
predictability I think is is is what
 

00:03:32.319 --> 00:03:34.470 align:start position:0%
predictability I think is is is what
reliability<00:03:32.959><c> is</c><00:03:33.440><c> for</c><00:03:33.599><c> me.</c><00:03:33.840><c> It's</c><00:03:34.000><c> a</c><00:03:34.159><c> big</c><00:03:34.319><c> part</c>

00:03:34.470 --> 00:03:34.480 align:start position:0%
reliability is for me. It's a big part
 

00:03:34.480 --> 00:03:37.670 align:start position:0%
reliability is for me. It's a big part
of<00:03:34.640><c> it.</c><00:03:35.519><c> Well</c><00:03:35.680><c> I</c><00:03:35.920><c> think</c><00:03:36.879><c> certainly</c><00:03:37.360><c> better</c>

00:03:37.670 --> 00:03:37.680 align:start position:0%
of it. Well I think certainly better
 

00:03:37.680 --> 00:03:40.070 align:start position:0%
of it. Well I think certainly better
data<00:03:38.400><c> better</c><00:03:38.799><c> processing</c><00:03:39.280><c> of</c><00:03:39.440><c> that</c><00:03:39.599><c> data</c><00:03:39.920><c> just</c>

00:03:40.070 --> 00:03:40.080 align:start position:0%
data better processing of that data just
 

00:03:40.080 --> 00:03:41.990 align:start position:0%
data better processing of that data just
like<00:03:40.239><c> I'm</c><00:03:40.400><c> trying</c><00:03:40.560><c> to</c><00:03:40.640><c> do</c><00:03:40.799><c> with</c><00:03:41.040><c> weave</c><00:03:41.440><c> is</c><00:03:41.599><c> is</c>

00:03:41.990 --> 00:03:42.000 align:start position:0%
like I'm trying to do with weave is is
 

00:03:42.000 --> 00:03:46.390 align:start position:0%
like I'm trying to do with weave is is
important.<00:03:43.280><c> um</c><00:03:44.400><c> security</c><00:03:45.280><c> is</c><00:03:45.519><c> is</c><00:03:46.000><c> super</c>

00:03:46.390 --> 00:03:46.400 align:start position:0%
important. um security is is super
 

00:03:46.400 --> 00:03:50.149 align:start position:0%
important. um security is is super
important.<00:03:46.879><c> So</c><00:03:47.200><c> having</c><00:03:48.239><c> much</c><00:03:48.560><c> more</c><00:03:48.879><c> secure</c><00:03:50.000><c> uh</c>

00:03:50.149 --> 00:03:50.159 align:start position:0%
important. So having much more secure uh
 

00:03:50.159 --> 00:03:51.670 align:start position:0%
important. So having much more secure uh
protocols.<00:03:50.720><c> So</c><00:03:50.879><c> like</c><00:03:51.040><c> for</c><00:03:51.120><c> instance</c><00:03:51.360><c> I</c><00:03:51.519><c> know</c>

00:03:51.670 --> 00:03:51.680 align:start position:0%
protocols. So like for instance I know
 

00:03:51.680 --> 00:03:55.509 align:start position:0%
protocols. So like for instance I know
MCP<00:03:52.720><c> added</c><00:03:53.519><c> security</c><00:03:54.640><c> uh</c><00:03:54.720><c> to</c><00:03:55.040><c> make</c><00:03:55.120><c> it</c><00:03:55.360><c> a</c>

00:03:55.509 --> 00:03:55.519 align:start position:0%
MCP added security uh to make it a
 

00:03:55.519 --> 00:03:59.830 align:start position:0%
MCP added security uh to make it a
little<00:03:55.599><c> bit</c><00:03:56.720><c> um</c><00:03:56.959><c> more</c><00:03:58.400><c> you</c><00:03:58.560><c> know</c><00:03:58.879><c> I</c><00:03:59.120><c> guess</c><00:03:59.439><c> uh</c>

00:03:59.830 --> 00:03:59.840 align:start position:0%
little bit um more you know I guess uh
 

00:03:59.840 --> 00:04:02.390 align:start position:0%
little bit um more you know I guess uh
uh

00:04:02.390 --> 00:04:02.400 align:start position:0%
uh
 

00:04:02.400 --> 00:04:05.270 align:start position:0%
uh
like<00:04:02.720><c> to</c><00:04:02.879><c> to</c><00:04:03.519><c> catch</c><00:04:03.840><c> it</c><00:04:04.000><c> up</c><00:04:04.319><c> with</c><00:04:04.640><c> what</c><00:04:04.959><c> exists</c>

00:04:05.270 --> 00:04:05.280 align:start position:0%
like to to catch it up with what exists
 

00:04:05.280 --> 00:04:07.190 align:start position:0%
like to to catch it up with what exists
in<00:04:05.439><c> the</c><00:04:05.599><c> web</c><00:04:05.840><c> right</c><00:04:06.080><c> now.</c><00:04:06.640><c> I</c><00:04:06.799><c> think</c><00:04:06.959><c> that's</c>

00:04:07.190 --> 00:04:07.200 align:start position:0%
in the web right now. I think that's
 

00:04:07.200 --> 00:04:09.830 align:start position:0%
in the web right now. I think that's
important.<00:04:07.680><c> I</c><00:04:07.920><c> think</c><00:04:08.239><c> because</c><00:04:08.799><c> agents</c><00:04:09.519><c> have</c>

00:04:09.830 --> 00:04:09.840 align:start position:0%
important. I think because agents have
 

00:04:09.840 --> 00:04:12.949 align:start position:0%
important. I think because agents have
agency<00:04:10.400><c> by</c><00:04:10.720><c> definition.</c><00:04:11.680><c> I</c><00:04:12.000><c> think</c><00:04:12.080><c> a</c><00:04:12.400><c> big</c><00:04:12.640><c> part</c>

00:04:12.949 --> 00:04:12.959 align:start position:0%
agency by definition. I think a big part
 

00:04:12.959 --> 00:04:17.110 align:start position:0%
agency by definition. I think a big part
of<00:04:13.120><c> what</c><00:04:13.360><c> we</c><00:04:13.680><c> need</c><00:04:14.159><c> is</c><00:04:14.720><c> a</c><00:04:15.040><c> system</c><00:04:15.519><c> for</c><00:04:16.799><c> uh</c>

00:04:17.110 --> 00:04:17.120 align:start position:0%
of what we need is a system for uh
 

00:04:17.120 --> 00:04:20.069 align:start position:0%
of what we need is a system for uh
reputation<00:04:18.000><c> across</c><00:04:18.479><c> agents</c><00:04:19.120><c> because</c><00:04:19.840><c> like</c>

00:04:20.069 --> 00:04:20.079 align:start position:0%
reputation across agents because like
 

00:04:20.079 --> 00:04:22.150 align:start position:0%
reputation across agents because like
for<00:04:20.239><c> instance</c><00:04:20.639><c> eBay</c>

00:04:22.150 --> 00:04:22.160 align:start position:0%
for instance eBay
 

00:04:22.160 --> 00:04:24.150 align:start position:0%
for instance eBay
is<00:04:22.400><c> a</c><00:04:22.639><c> great</c><00:04:22.800><c> example</c><00:04:23.040><c> of</c><00:04:23.199><c> this,</c><00:04:23.520><c> right?</c><00:04:23.840><c> So</c><00:04:24.000><c> if</c>

00:04:24.150 --> 00:04:24.160 align:start position:0%
is a great example of this, right? So if
 

00:04:24.160 --> 00:04:27.430 align:start position:0%
is a great example of this, right? So if
you<00:04:24.320><c> think</c><00:04:24.479><c> of</c><00:04:24.800><c> every</c><00:04:25.919><c> seller</c><00:04:26.560><c> and</c><00:04:26.960><c> buyer</c><00:04:27.199><c> on</c>

00:04:27.430 --> 00:04:27.440 align:start position:0%
you think of every seller and buyer on
 

00:04:27.440 --> 00:04:29.749 align:start position:0%
you think of every seller and buyer on
eBay<00:04:27.680><c> as</c><00:04:27.919><c> agents,</c><00:04:28.560><c> they</c><00:04:28.880><c> each</c><00:04:29.120><c> have</c><00:04:29.280><c> agency,</c>

00:04:29.749 --> 00:04:29.759 align:start position:0%
eBay as agents, they each have agency,
 

00:04:29.759 --> 00:04:32.469 align:start position:0%
eBay as agents, they each have agency,
they<00:04:29.919><c> each</c><00:04:30.160><c> have</c><00:04:30.320><c> goals.</c><00:04:31.520><c> The</c><00:04:31.759><c> reason</c><00:04:32.000><c> eBay</c>

00:04:32.469 --> 00:04:32.479 align:start position:0%
they each have goals. The reason eBay
 

00:04:32.479 --> 00:04:35.830 align:start position:0%
they each have goals. The reason eBay
works<00:04:33.360><c> and</c><00:04:33.680><c> has</c><00:04:34.080><c> survived</c><00:04:34.639><c> so</c><00:04:34.880><c> long</c><00:04:35.440><c> is</c>

00:04:35.830 --> 00:04:35.840 align:start position:0%
works and has survived so long is
 

00:04:35.840 --> 00:04:37.510 align:start position:0%
works and has survived so long is
because<00:04:36.160><c> of</c><00:04:36.320><c> the</c><00:04:36.560><c> reputation</c><00:04:37.040><c> system</c><00:04:37.280><c> that</c>

00:04:37.510 --> 00:04:37.520 align:start position:0%
because of the reputation system that
 

00:04:37.520 --> 00:04:38.950 align:start position:0%
because of the reputation system that
they<00:04:37.680><c> established.</c><00:04:38.160><c> So</c><00:04:38.320><c> basically</c><00:04:38.639><c> the</c>

00:04:38.950 --> 00:04:38.960 align:start position:0%
they established. So basically the
 

00:04:38.960 --> 00:04:41.030 align:start position:0%
they established. So basically the
ranking<00:04:39.360><c> mechanism</c><00:04:40.160><c> and</c><00:04:40.400><c> the</c><00:04:40.639><c> fact</c><00:04:40.720><c> that</c>

00:04:41.030 --> 00:04:41.040 align:start position:0%
ranking mechanism and the fact that
 

00:04:41.040 --> 00:04:44.870 align:start position:0%
ranking mechanism and the fact that
sellers<00:04:41.520><c> know</c><00:04:41.759><c> that</c><00:04:42.000><c> if</c><00:04:42.320><c> they</c><00:04:43.199><c> advertise</c><00:04:44.560><c> a</c>

00:04:44.870 --> 00:04:44.880 align:start position:0%
sellers know that if they advertise a
 

00:04:44.880 --> 00:04:48.550 align:start position:0%
sellers know that if they advertise a
product<00:04:45.520><c> on</c><00:04:45.759><c> eBay</c><00:04:46.400><c> and</c><00:04:46.720><c> they</c><00:04:47.120><c> end</c><00:04:47.360><c> up</c><00:04:48.240><c> doing</c>

00:04:48.550 --> 00:04:48.560 align:start position:0%
product on eBay and they end up doing
 

00:04:48.560 --> 00:04:50.790 align:start position:0%
product on eBay and they end up doing
something,<00:04:49.440><c> you</c><00:04:49.600><c> know,</c><00:04:50.000><c> like</c><00:04:50.240><c> sending</c><00:04:50.560><c> you</c>

00:04:50.790 --> 00:04:50.800 align:start position:0%
something, you know, like sending you
 

00:04:50.800 --> 00:04:54.070 align:start position:0%
something, you know, like sending you
crap,<00:04:51.680><c> they're</c><00:04:52.000><c> going</c><00:04:52.080><c> to</c><00:04:52.240><c> get</c><00:04:52.639><c> a</c><00:04:53.040><c> bad</c><00:04:53.360><c> rating</c>

00:04:54.070 --> 00:04:54.080 align:start position:0%
crap, they're going to get a bad rating
 

00:04:54.080 --> 00:04:55.990 align:start position:0%
crap, they're going to get a bad rating
which<00:04:54.320><c> will</c><00:04:54.720><c> immediately</c><00:04:55.440><c> impact</c><00:04:55.759><c> their</c>

00:04:55.990 --> 00:04:56.000 align:start position:0%
which will immediately impact their
 

00:04:56.000 --> 00:04:59.110 align:start position:0%
which will immediately impact their
reputation<00:04:57.280><c> and</c><00:04:57.840><c> when</c><00:04:58.160><c> somebody</c><00:04:58.479><c> goes</c><00:04:58.800><c> to</c><00:04:58.960><c> buy</c>

00:04:59.110 --> 00:04:59.120 align:start position:0%
reputation and when somebody goes to buy
 

00:04:59.120 --> 00:05:00.310 align:start position:0%
reputation and when somebody goes to buy
the<00:04:59.280><c> next</c><00:04:59.520><c> product,</c><00:04:59.840><c> they</c><00:05:00.080><c> will</c><00:05:00.160><c> see</c>

00:05:00.310 --> 00:05:00.320 align:start position:0%
the next product, they will see
 

00:05:00.320 --> 00:05:02.629 align:start position:0%
the next product, they will see
immediately<00:05:01.040><c> that</c><00:05:01.360><c> something</c><00:05:01.680><c> happened.</c><00:05:02.400><c> I</c>

00:05:02.629 --> 00:05:02.639 align:start position:0%
immediately that something happened. I
 

00:05:02.639 --> 00:05:04.070 align:start position:0%
immediately that something happened. I
feel<00:05:02.720><c> like</c><00:05:02.960><c> agents</c><00:05:03.360><c> will</c><00:05:03.600><c> have</c><00:05:03.680><c> to</c><00:05:03.840><c> get</c><00:05:03.919><c> to</c>

00:05:04.070 --> 00:05:04.080 align:start position:0%
feel like agents will have to get to
 

00:05:04.080 --> 00:05:05.990 align:start position:0%
feel like agents will have to get to
that<00:05:04.320><c> too.</c><00:05:04.800><c> There's</c><00:05:05.120><c> going</c><00:05:05.280><c> to</c><00:05:05.360><c> need</c><00:05:05.680><c> there's</c>

00:05:05.990 --> 00:05:06.000 align:start position:0%
that too. There's going to need there's
 

00:05:06.000 --> 00:05:07.749 align:start position:0%
that too. There's going to need there's
going<00:05:06.160><c> to</c><00:05:06.240><c> need</c><00:05:06.479><c> to</c><00:05:06.639><c> be</c><00:05:06.720><c> a</c><00:05:06.880><c> way</c><00:05:07.199><c> probably</c><00:05:07.440><c> not</c>

00:05:07.749 --> 00:05:07.759 align:start position:0%
going to need to be a way probably not
 

00:05:07.759 --> 00:05:09.749 align:start position:0%
going to need to be a way probably not
exactly<00:05:08.080><c> the</c><00:05:08.320><c> way</c><00:05:08.560><c> eBay</c><00:05:08.960><c> works,</c><00:05:09.360><c> but</c><00:05:09.600><c> there</c>

00:05:09.749 --> 00:05:09.759 align:start position:0%
exactly the way eBay works, but there
 

00:05:09.759 --> 00:05:12.790 align:start position:0%
exactly the way eBay works, but there
needs<00:05:10.000><c> to</c><00:05:10.080><c> be</c><00:05:10.160><c> a</c><00:05:10.400><c> way</c><00:05:10.560><c> for</c><00:05:11.120><c> agents</c><00:05:12.240><c> to</c><00:05:12.560><c> have</c>

00:05:12.790 --> 00:05:12.800 align:start position:0%
needs to be a way for agents to have
 

00:05:12.800 --> 00:05:15.430 align:start position:0%
needs to be a way for agents to have
some<00:05:13.120><c> reputation</c><00:05:13.600><c> mechanism</c><00:05:14.160><c> across</c><00:05:14.639><c> them</c><00:05:15.280><c> so</c>

00:05:15.430 --> 00:05:15.440 align:start position:0%
some reputation mechanism across them so
 

00:05:15.440 --> 00:05:16.790 align:start position:0%
some reputation mechanism across them so
that<00:05:15.680><c> you</c><00:05:15.840><c> know</c><00:05:16.000><c> that</c><00:05:16.240><c> when</c><00:05:16.400><c> you're</c><00:05:16.560><c> talking</c>

00:05:16.790 --> 00:05:16.800 align:start position:0%
that you know that when you're talking
 

00:05:16.800 --> 00:05:21.510 align:start position:0%
that you know that when you're talking
to<00:05:16.960><c> this</c><00:05:17.199><c> agent,</c><00:05:17.919><c> it</c><00:05:18.240><c> has</c><00:05:18.479><c> a</c><00:05:18.800><c> reliable</c><00:05:20.080><c> uh</c><00:05:20.560><c> um</c>

00:05:21.510 --> 00:05:21.520 align:start position:0%
to this agent, it has a reliable uh um
 

00:05:21.520 --> 00:05:23.909 align:start position:0%
to this agent, it has a reliable uh um
way<00:05:21.759><c> of</c><00:05:22.000><c> operating</c><00:05:23.120><c> that</c><00:05:23.440><c> it's</c><00:05:23.680><c> not</c>

00:05:23.909 --> 00:05:23.919 align:start position:0%
way of operating that it's not
 

00:05:23.919 --> 00:05:25.590 align:start position:0%
way of operating that it's not
advertising<00:05:24.800><c> giving</c><00:05:25.039><c> you</c><00:05:25.280><c> false</c>

00:05:25.590 --> 00:05:25.600 align:start position:0%
advertising giving you false
 

00:05:25.600 --> 00:05:27.189 align:start position:0%
advertising giving you false
advertisement<00:05:26.160><c> in</c><00:05:26.400><c> terms</c><00:05:26.560><c> of</c><00:05:26.639><c> what</c><00:05:26.800><c> it</c><00:05:27.039><c> can</c>

00:05:27.189 --> 00:05:27.199 align:start position:0%
advertisement in terms of what it can
 

00:05:27.199 --> 00:05:29.110 align:start position:0%
advertisement in terms of what it can
do.<00:05:27.759><c> So</c><00:05:27.919><c> I</c><00:05:28.160><c> think</c><00:05:28.240><c> all</c><00:05:28.400><c> of</c><00:05:28.560><c> this</c><00:05:28.720><c> is</c><00:05:28.960><c> going</c><00:05:29.039><c> to</c>

00:05:29.110 --> 00:05:29.120 align:start position:0%
do. So I think all of this is going to
 

00:05:29.120 --> 00:05:30.870 align:start position:0%
do. So I think all of this is going to
be<00:05:29.280><c> important</c><00:05:29.600><c> but</c><00:05:29.840><c> that's</c><00:05:30.160><c> mostly</c><00:05:30.560><c> for</c><00:05:30.720><c> the</c>

00:05:30.870 --> 00:05:30.880 align:start position:0%
be important but that's mostly for the
 

00:05:30.880 --> 00:05:33.189 align:start position:0%
be important but that's mostly for the
future.<00:05:31.199><c> So</c><00:05:31.680><c> obviously</c><00:05:32.080><c> for</c><00:05:32.400><c> the</c><00:05:32.720><c> immediate</c>

00:05:33.189 --> 00:05:33.199 align:start position:0%
future. So obviously for the immediate
 

00:05:33.199 --> 00:05:35.670 align:start position:0%
future. So obviously for the immediate
present,<00:05:33.600><c> it's</c><00:05:33.840><c> about</c><00:05:34.800><c> figuring</c><00:05:35.199><c> out</c><00:05:35.360><c> how</c><00:05:35.520><c> to</c>

00:05:35.670 --> 00:05:35.680 align:start position:0%
present, it's about figuring out how to
 

00:05:35.680 --> 00:05:38.950 align:start position:0%
present, it's about figuring out how to
get<00:05:35.840><c> the</c><00:05:36.080><c> data</c><00:05:36.400><c> as</c><00:05:37.199><c> kosher</c><00:05:37.680><c> and</c><00:05:37.919><c> as</c><00:05:38.320><c> correct</c><00:05:38.720><c> as</c>

00:05:38.950 --> 00:05:38.960 align:start position:0%
get the data as kosher and as correct as
 

00:05:38.960 --> 00:05:41.590 align:start position:0%
get the data as kosher and as correct as
possible.<00:05:39.919><c> It's</c><00:05:40.160><c> about</c><00:05:40.720><c> having</c><00:05:40.960><c> the</c><00:05:41.199><c> basic</c>

00:05:41.590 --> 00:05:41.600 align:start position:0%
possible. It's about having the basic
 

00:05:41.600 --> 00:05:43.909 align:start position:0%
possible. It's about having the basic
security<00:05:42.320><c> features</c><00:05:42.720><c> that</c><00:05:42.960><c> we</c><00:05:43.280><c> enjoy</c><00:05:43.600><c> in</c><00:05:43.759><c> the</c>

00:05:43.909 --> 00:05:43.919 align:start position:0%
security features that we enjoy in the
 

00:05:43.919 --> 00:05:46.310 align:start position:0%
security features that we enjoy in the
web<00:05:44.560><c> so</c><00:05:44.800><c> that</c><00:05:44.960><c> you</c><00:05:45.199><c> can</c><00:05:45.360><c> make</c><00:05:45.520><c> sure</c><00:05:45.680><c> that</c><00:05:46.000><c> the</c>

00:05:46.310 --> 00:05:46.320 align:start position:0%
web so that you can make sure that the
 

00:05:46.320 --> 00:05:49.110 align:start position:0%
web so that you can make sure that the
communication<00:05:46.880><c> is</c><00:05:47.039><c> is</c><00:05:47.280><c> is</c><00:05:47.840><c> secure</c><00:05:48.240><c> and</c><00:05:48.800><c> and</c>

00:05:49.110 --> 00:05:49.120 align:start position:0%
communication is is is secure and and
 

00:05:49.120 --> 00:05:50.629 align:start position:0%
communication is is is secure and and
that<00:05:49.280><c> your</c><00:05:49.520><c> data</c><00:05:49.680><c> is</c><00:05:49.840><c> not</c><00:05:50.000><c> being</c><00:05:50.160><c> leaked</c><00:05:50.479><c> and</c>

00:05:50.629 --> 00:05:50.639 align:start position:0%
that your data is not being leaked and
 

00:05:50.639 --> 00:05:52.550 align:start position:0%
that your data is not being leaked and
so<00:05:50.800><c> on</c><00:05:51.039><c> so</c><00:05:51.199><c> forth.</c><00:05:51.520><c> So</c><00:05:51.759><c> those</c><00:05:52.000><c> are</c><00:05:52.160><c> the</c><00:05:52.400><c> first</c>

00:05:52.550 --> 00:05:52.560 align:start position:0%
so on so forth. So those are the first
 

00:05:52.560 --> 00:05:54.310 align:start position:0%
so on so forth. So those are the first
steps<00:05:52.880><c> but</c><00:05:53.199><c> eventually</c><00:05:53.680><c> we're</c><00:05:53.919><c> going</c><00:05:54.000><c> to</c><00:05:54.160><c> need</c>

00:05:54.310 --> 00:05:54.320 align:start position:0%
steps but eventually we're going to need
 

00:05:54.320 --> 00:05:56.950 align:start position:0%
steps but eventually we're going to need
to<00:05:54.479><c> get</c><00:05:54.639><c> to</c><00:05:55.520><c> uh</c><00:05:55.680><c> reputation</c><00:05:56.240><c> mechanism</c><00:05:56.800><c> I</c>

00:05:56.950 --> 00:05:56.960 align:start position:0%
to get to uh reputation mechanism I
 

00:05:56.960 --> 00:05:59.990 align:start position:0%
to get to uh reputation mechanism I
think.<00:05:57.759><c> So</c><00:05:58.080><c> first</c><00:05:58.320><c> thing</c><00:05:58.479><c> is</c><00:05:58.720><c> I</c><00:05:58.960><c> would</c><00:05:59.120><c> say</c><00:05:59.759><c> it</c>

00:05:59.990 --> 00:06:00.000 align:start position:0%
think. So first thing is I would say it
 

00:06:00.000 --> 00:06:01.110 align:start position:0%
think. So first thing is I would say it
will<00:06:00.160><c> be</c><00:06:00.240><c> a</c><00:06:00.400><c> little</c><00:06:00.479><c> bit</c><00:06:00.639><c> different</c><00:06:00.800><c> than</c><00:06:00.960><c> what</c>

00:06:01.110 --> 00:06:01.120 align:start position:0%
will be a little bit different than what
 

00:06:01.120 --> 00:06:04.390 align:start position:0%
will be a little bit different than what
we<00:06:01.280><c> have</c><00:06:01.440><c> right</c><00:06:01.600><c> now.</c><00:06:01.759><c> I'm</c><00:06:02.000><c> actually</c><00:06:03.039><c> in</c><00:06:03.360><c> my</c>

00:06:04.390 --> 00:06:04.400 align:start position:0%
we have right now. I'm actually in my
 

00:06:04.400 --> 00:06:07.670 align:start position:0%
we have right now. I'm actually in my
company<00:06:05.680><c> uh</c><00:06:06.000><c> changing</c><00:06:06.720><c> my</c><00:06:06.960><c> stack.</c><00:06:07.280><c> So</c><00:06:07.440><c> I</c>

00:06:07.670 --> 00:06:07.680 align:start position:0%
company uh changing my stack. So I
 

00:06:07.680 --> 00:06:09.990 align:start position:0%
company uh changing my stack. So I
started<00:06:07.919><c> with</c><00:06:08.160><c> the</c><00:06:08.400><c> basic</c><00:06:08.880><c> Python</c><00:06:09.440><c> stack</c><00:06:09.759><c> that</c>

00:06:09.990 --> 00:06:10.000 align:start position:0%
started with the basic Python stack that
 

00:06:10.000 --> 00:06:13.590 align:start position:0%
started with the basic Python stack that
everybody<00:06:10.400><c> uses</c><00:06:11.440><c> and</c><00:06:11.680><c> then</c><00:06:12.080><c> start</c>

00:06:13.590 --> 00:06:13.600 align:start position:0%
everybody uses and then start
 

00:06:13.600 --> 00:06:16.150 align:start position:0%
everybody uses and then start
you<00:06:13.759><c> know</c><00:06:13.919><c> adding</c><00:06:14.240><c> some</c><00:06:14.880><c> UI</c><00:06:15.360><c> on</c><00:06:15.520><c> top</c><00:06:15.600><c> of</c><00:06:15.680><c> it.</c><00:06:16.000><c> So</c>

00:06:16.150 --> 00:06:16.160 align:start position:0%
you know adding some UI on top of it. So
 

00:06:16.160 --> 00:06:17.830 align:start position:0%
you know adding some UI on top of it. So
JavaScript<00:06:16.560><c> and</c><00:06:16.800><c> stuff</c><00:06:16.960><c> like</c><00:06:17.120><c> that</c><00:06:17.280><c> and</c><00:06:17.440><c> I</c><00:06:17.680><c> got</c>

00:06:17.830 --> 00:06:17.840 align:start position:0%
JavaScript and stuff like that and I got
 

00:06:17.840 --> 00:06:20.390 align:start position:0%
JavaScript and stuff like that and I got
rid<00:06:17.919><c> of</c><00:06:18.080><c> all</c><00:06:18.319><c> that.</c><00:06:18.880><c> I</c><00:06:19.120><c> think</c><00:06:19.520><c> Python</c><00:06:19.919><c> is</c><00:06:20.160><c> great</c>

00:06:20.390 --> 00:06:20.400 align:start position:0%
rid of all that. I think Python is great
 

00:06:20.400 --> 00:06:23.510 align:start position:0%
rid of all that. I think Python is great
for<00:06:20.880><c> for</c><00:06:21.759><c> experimentation.</c><00:06:22.880><c> It's</c><00:06:23.120><c> great</c><00:06:23.280><c> also</c>

00:06:23.510 --> 00:06:23.520 align:start position:0%
for for experimentation. It's great also
 

00:06:23.520 --> 00:06:25.909 align:start position:0%
for for experimentation. It's great also
for<00:06:23.840><c> maybe</c><00:06:24.160><c> training</c><00:06:25.120><c> but</c><00:06:25.360><c> it's</c><00:06:25.600><c> not</c><00:06:25.759><c> good</c>

00:06:25.909 --> 00:06:25.919 align:start position:0%
for maybe training but it's not good
 

00:06:25.919 --> 00:06:27.749 align:start position:0%
for maybe training but it's not good
enough<00:06:26.240><c> for</c><00:06:26.639><c> production.</c><00:06:27.199><c> I</c><00:06:27.360><c> think</c><00:06:27.520><c> for</c>

00:06:27.749 --> 00:06:27.759 align:start position:0%
enough for production. I think for
 

00:06:27.759 --> 00:06:30.469 align:start position:0%
enough for production. I think for
production<00:06:28.240><c> you</c><00:06:28.479><c> need</c><00:06:29.199><c> better</c><00:06:29.919><c> language,</c>

00:06:30.469 --> 00:06:30.479 align:start position:0%
production you need better language,
 

00:06:30.479 --> 00:06:32.790 align:start position:0%
production you need better language,
better<00:06:30.720><c> system,</c><00:06:31.199><c> better</c><00:06:31.440><c> libraries.</c><00:06:32.400><c> So</c><00:06:32.560><c> I</c>

00:06:32.790 --> 00:06:32.800 align:start position:0%
better system, better libraries. So I
 

00:06:32.800 --> 00:06:35.590 align:start position:0%
better system, better libraries. So I
switched<00:06:32.960><c> to</c><00:06:33.120><c> Golang</c><00:06:34.160><c> uh</c><00:06:34.400><c> which</c><00:06:34.880><c> I</c><00:06:35.120><c> think</c><00:06:35.199><c> is</c><00:06:35.440><c> a</c>

00:06:35.590 --> 00:06:35.600 align:start position:0%
switched to Golang uh which I think is a
 

00:06:35.600 --> 00:06:39.590 align:start position:0%
switched to Golang uh which I think is a
proven<00:06:37.039><c> uh</c><00:06:37.520><c> environment</c><00:06:38.000><c> for</c><00:06:38.240><c> the</c><00:06:38.479><c> cloud.</c><00:06:39.120><c> U</c>

00:06:39.590 --> 00:06:39.600 align:start position:0%
proven uh environment for the cloud. U
 

00:06:39.600 --> 00:06:41.749 align:start position:0%
proven uh environment for the cloud. U
you<00:06:39.759><c> know</c><00:06:39.919><c> Kubernetes</c><00:06:40.479><c> is</c><00:06:40.639><c> built</c><00:06:40.800><c> in</c><00:06:40.880><c> Golang.</c>

00:06:41.749 --> 00:06:41.759 align:start position:0%
you know Kubernetes is built in Golang.
 

00:06:41.759 --> 00:06:45.029 align:start position:0%
you know Kubernetes is built in Golang.
My<00:06:42.080><c> stack</c><00:06:42.400><c> now</c><00:06:42.560><c> is</c><00:06:42.720><c> Golang</c><00:06:43.440><c> for</c><00:06:43.759><c> the</c><00:06:44.000><c> back</c><00:06:44.160><c> end</c>

00:06:45.029 --> 00:06:45.039 align:start position:0%
My stack now is Golang for the back end
 

00:06:45.039 --> 00:06:47.189 align:start position:0%
My stack now is Golang for the back end
and<00:06:45.360><c> on</c><00:06:45.520><c> the</c><00:06:45.680><c> front</c><00:06:45.840><c> end</c><00:06:46.080><c> I</c><00:06:46.240><c> use</c><00:06:46.319><c> TypeScript</c>

00:06:47.189 --> 00:06:47.199 align:start position:0%
and on the front end I use TypeScript
 

00:06:47.199 --> 00:06:49.029 align:start position:0%
and on the front end I use TypeScript
which<00:06:47.440><c> is</c><00:06:47.759><c> essentially</c><00:06:48.160><c> JavaScript</c><00:06:48.720><c> but</c>

00:06:49.029 --> 00:06:49.039 align:start position:0%
which is essentially JavaScript but
 

00:06:49.039 --> 00:06:52.230 align:start position:0%
which is essentially JavaScript but
typed<00:06:50.000><c> and</c><00:06:51.199><c> that</c><00:06:51.520><c> gives</c><00:06:51.680><c> you</c><00:06:51.840><c> a</c><00:06:52.000><c> lot</c><00:06:52.080><c> of</c>

00:06:52.230 --> 00:06:52.240 align:start position:0%
typed and that gives you a lot of
 

00:06:52.240 --> 00:06:54.309 align:start position:0%
typed and that gives you a lot of
advantages<00:06:52.880><c> makes</c><00:06:53.120><c> it</c><00:06:53.199><c> a</c><00:06:53.360><c> little</c><00:06:53.440><c> bit</c><00:06:53.680><c> harder</c>

00:06:54.309 --> 00:06:54.319 align:start position:0%
advantages makes it a little bit harder
 

00:06:54.319 --> 00:06:56.629 align:start position:0%
advantages makes it a little bit harder
for<00:06:54.639><c> some</c><00:06:54.880><c> cases</c><00:06:55.280><c> but</c><00:06:55.600><c> basically</c><00:06:56.000><c> my</c><00:06:56.240><c> stack</c><00:06:56.479><c> is</c>

00:06:56.629 --> 00:06:56.639 align:start position:0%
for some cases but basically my stack is
 

00:06:56.639 --> 00:06:59.360 align:start position:0%
for some cases but basically my stack is
go<00:06:56.960><c> TypeScript</c>