WEBVTT
00:00:00.000 --> 00:00:03.339
I, for a good chunk of the last decade, I was
00:00:03.339 --> 00:00:05.379
kind of the guy who's like, hey, how can I keep
00:00:05.379 --> 00:00:07.820
everything off of the cloud and keep all the
00:00:07.820 --> 00:00:10.699
data to myself? I don't want Zuckerberg knowing
00:00:10.699 --> 00:00:13.259
this about me. I don't want Google knowing this
00:00:13.259 --> 00:00:15.519
about me. Like, how can I keep everything on
00:00:15.519 --> 00:00:17.800
my own hard drive and keep as little information
00:00:17.800 --> 00:00:22.339
about me on the cloud? And with kind of this
00:00:22.339 --> 00:00:25.699
advent of AI, I feel like that's been softened
00:00:25.699 --> 00:00:28.050
because it's actually... If they have this information,
00:00:28.230 --> 00:00:31.250
it makes all this stuff so much easier. But I
00:00:31.250 --> 00:00:33.810
think there are a ton of security implications
00:00:33.810 --> 00:00:37.210
to that and societal implications to that, especially,
00:00:37.390 --> 00:00:40.630
I mean, this feels like 100 years ago now, but
00:00:40.630 --> 00:00:42.170
when thinking about the Cambridge Analytica stuff,
00:00:42.289 --> 00:00:46.009
when thinking about the way that with data, elections
00:00:46.009 --> 00:00:48.509
can be steered and society can be steered. And
00:00:48.509 --> 00:00:51.770
I think all that is still applicable, even though
00:00:51.770 --> 00:00:54.090
I don't hear as many people talking about it
00:00:54.090 --> 00:00:57.340
these days. Everything else that I'll say is
00:00:57.340 --> 00:01:00.820
that pretense of, hey, data security and data
00:01:00.820 --> 00:01:03.920
sovereignty is quite important. But that being
00:01:03.920 --> 00:01:08.359
said, man, if you can figure out ways to have
00:01:08.359 --> 00:01:13.640
these tools interface with your data in a helpful
00:01:13.640 --> 00:01:16.040
way, there's some super cool stuff that can happen
00:01:16.040 --> 00:01:18.099
with that. I've been exploring the possibility
00:01:18.099 --> 00:01:22.739
of having all my emails and all my text messages
00:01:22.739 --> 00:01:26.180
and even my calls be... put into a vector database
00:01:26.180 --> 00:01:29.219
so that if I had an AI agent and I wanted to
00:01:29.219 --> 00:01:32.340
say, Hey, who in the last month have I talked
00:01:32.340 --> 00:01:35.519
with about good coffee? Then it can be like,
00:01:35.579 --> 00:01:37.780
Hey, you were on this call with Daniel. And also
00:01:37.780 --> 00:01:40.359
you had this email and also this WhatsApp message.
00:01:40.739 --> 00:01:43.079
And that feels relatively simple. Really good
00:01:43.079 --> 00:01:45.719
semantic search is not a big deal. But if I wanted
00:01:45.719 --> 00:01:48.879
to then say, cool, I'm actually putting together
00:01:48.879 --> 00:01:52.079
this meeting of coffee nerds. Can you email an
00:01:52.079 --> 00:01:54.299
invite to each of them? And also double check
00:01:54.299 --> 00:01:55.980
to make sure that they haven't told me that there's
00:01:55.980 --> 00:01:58.439
something that they're busy with that day. Figure
00:01:58.439 --> 00:02:00.379
out what day would be the best. That's a possibility.
00:02:00.500 --> 00:02:03.299
And it can just go and do it. There's a few parts
00:02:03.299 --> 00:02:05.620
of it where it's not quite there, but it's pretty
00:02:05.620 --> 00:02:07.299
close. And it's going to get closer and closer
00:02:07.299 --> 00:02:10.639
as time goes on. And so I think, yeah, I think
00:02:10.639 --> 00:02:14.680
data management is kingdom stewardship, if in
00:02:14.680 --> 00:02:18.139
certain contexts. For kingdom focused people
00:02:18.139 --> 00:02:21.960
and organizations to be able to steward their
00:02:21.960 --> 00:02:24.830
data well. has potentially quite significant
00:02:24.830 --> 00:02:27.090
kingdom implications, especially when we think
00:02:27.090 --> 00:02:30.409
about applying these tools to it properly. And
00:02:30.409 --> 00:02:35.569
so, yeah, I think there is for people in organizations
00:02:35.569 --> 00:02:39.469
that can get their data set up in really good
00:02:39.469 --> 00:02:42.789
and solid ways. I think the sky is becoming the
00:02:42.789 --> 00:02:45.370
limit of what the applications of that can be.
00:02:46.909 --> 00:02:49.009
It is a long journey to be able to do that well.
00:02:49.129 --> 00:02:51.069
It's not a simple thing. And when you bring the
00:02:51.069 --> 00:02:53.189
data sovereignty privacy stuff into it, it gets
00:02:53.189 --> 00:02:57.370
even more complicated. So, yeah. I made this
00:02:57.370 --> 00:03:00.430
podcast because I want to be the person at the
00:03:00.430 --> 00:03:03.349
city gate to talk to every person coming in and
00:03:03.349 --> 00:03:05.969
out, doing great things with AI and find out
00:03:05.969 --> 00:03:09.169
what and why, and then share the learnings with
00:03:09.169 --> 00:03:12.009
everyone else. It would mean a lot if you could
00:03:12.009 --> 00:03:13.949
share the episode with someone that you think
00:03:13.949 --> 00:03:16.400
would like it. And if you know someone who would
00:03:16.400 --> 00:03:18.759
be a great person for me to talk to, let me know.
00:03:19.780 --> 00:03:23.180
Please reach out to me at Daniel Maneri on LinkedIn
00:03:23.180 --> 00:03:27.000
or shoot an email to Daniel at Maneri .house,
00:03:27.039 --> 00:03:33.300
which is Daniel at M -A -N -A -R -Y dot H -A
00:03:33.300 --> 00:03:35.800
-U -S. Thanks for listening.
00:00:00.000 --> 00:00:03.339
I, for a good chunk of the last decade, I was
00:00:03.339 --> 00:00:05.379
kind of the guy who's like, hey, how can I keep
00:00:05.379 --> 00:00:07.820
everything off of the cloud and keep all the
00:00:07.820 --> 00:00:10.699
data to myself? I don't want Zuckerberg knowing
00:00:10.699 --> 00:00:13.259
this about me. I don't want Google knowing this
00:00:13.259 --> 00:00:15.519
about me. Like, how can I keep everything on
00:00:15.519 --> 00:00:17.800
my own hard drive and keep as little information
00:00:17.800 --> 00:00:22.339
about me on the cloud? And with kind of this
00:00:22.339 --> 00:00:25.699
advent of AI, I feel like that's been softened
00:00:25.699 --> 00:00:28.050
because it's actually... If they have this information,
00:00:28.230 --> 00:00:31.250
it makes all this stuff so much easier. But I
00:00:31.250 --> 00:00:33.810
think there are a ton of security implications
00:00:33.810 --> 00:00:37.210
to that and societal implications to that, especially,
00:00:37.390 --> 00:00:40.630
I mean, this feels like 100 years ago now, but
00:00:40.630 --> 00:00:42.170
when thinking about the Cambridge Analytica stuff,
00:00:42.289 --> 00:00:46.009
when thinking about the way that with data, elections
00:00:46.009 --> 00:00:48.509
can be steered and society can be steered. And
00:00:48.509 --> 00:00:51.770
I think all that is still applicable, even though
00:00:51.770 --> 00:00:54.090
I don't hear as many people talking about it
00:00:54.090 --> 00:00:57.340
these days. Everything else that I'll say is
00:00:57.340 --> 00:01:00.820
that pretense of, hey, data security and data
00:01:00.820 --> 00:01:03.920
sovereignty is quite important. But that being
00:01:03.920 --> 00:01:08.359
said, man, if you can figure out ways to have
00:01:08.359 --> 00:01:13.640
these tools interface with your data in a helpful
00:01:13.640 --> 00:01:16.040
way, there's some super cool stuff that can happen
00:01:16.040 --> 00:01:18.099
with that. I've been exploring the possibility
00:01:18.099 --> 00:01:22.739
of having all my emails and all my text messages
00:01:22.739 --> 00:01:26.180
and even my calls be... put into a vector database
00:01:26.180 --> 00:01:29.219
so that if I had an AI agent and I wanted to
00:01:29.219 --> 00:01:32.340
say, Hey, who in the last month have I talked
00:01:32.340 --> 00:01:35.519
with about good coffee? Then it can be like,
00:01:35.579 --> 00:01:37.780
Hey, you were on this call with Daniel. And also
00:01:37.780 --> 00:01:40.359
you had this email and also this WhatsApp message.
00:01:40.739 --> 00:01:43.079
And that feels relatively simple. Really good
00:01:43.079 --> 00:01:45.719
semantic search is not a big deal. But if I wanted
00:01:45.719 --> 00:01:48.879
to then say, cool, I'm actually putting together
00:01:48.879 --> 00:01:52.079
this meeting of coffee nerds. Can you email an
00:01:52.079 --> 00:01:54.299
invite to each of them? And also double check
00:01:54.299 --> 00:01:55.980
to make sure that they haven't told me that there's
00:01:55.980 --> 00:01:58.439
something that they're busy with that day. Figure
00:01:58.439 --> 00:02:00.379
out what day would be the best. That's a possibility.
00:02:00.500 --> 00:02:03.299
And it can just go and do it. There's a few parts
00:02:03.299 --> 00:02:05.620
of it where it's not quite there, but it's pretty
00:02:05.620 --> 00:02:07.299
close. And it's going to get closer and closer
00:02:07.299 --> 00:02:10.639
as time goes on. And so I think, yeah, I think
00:02:10.639 --> 00:02:14.680
data management is kingdom stewardship, if in
00:02:14.680 --> 00:02:18.139
certain contexts. For kingdom focused people
00:02:18.139 --> 00:02:21.960
and organizations to be able to steward their
00:02:21.960 --> 00:02:24.830
data well. has potentially quite significant
00:02:24.830 --> 00:02:27.090
kingdom implications, especially when we think
00:02:27.090 --> 00:02:30.409
about applying these tools to it properly. And
00:02:30.409 --> 00:02:35.569
so, yeah, I think there is for people in organizations
00:02:35.569 --> 00:02:39.469
that can get their data set up in really good
00:02:39.469 --> 00:02:42.789
and solid ways. I think the sky is becoming the
00:02:42.789 --> 00:02:45.370
limit of what the applications of that can be.
00:02:46.909 --> 00:02:49.009
It is a long journey to be able to do that well.
00:02:49.129 --> 00:02:51.069
It's not a simple thing. And when you bring the
00:02:51.069 --> 00:02:53.189
data sovereignty privacy stuff into it, it gets
00:02:53.189 --> 00:02:57.370
even more complicated. So, yeah. I made this
00:02:57.370 --> 00:03:00.430
podcast because I want to be the person at the
00:03:00.430 --> 00:03:03.349
city gate to talk to every person coming in and
00:03:03.349 --> 00:03:05.969
out, doing great things with AI and find out
00:03:05.969 --> 00:03:09.169
what and why, and then share the learnings with
00:03:09.169 --> 00:03:12.009
everyone else. It would mean a lot if you could
00:03:12.009 --> 00:03:13.949
share the episode with someone that you think
00:03:13.949 --> 00:03:16.400
would like it. And if you know someone who would
00:03:16.400 --> 00:03:18.759
be a great person for me to talk to, let me know.
00:03:19.780 --> 00:03:23.180
Please reach out to me at Daniel Maneri on LinkedIn
00:03:23.180 --> 00:03:27.000
or shoot an email to Daniel at Maneri .house,
00:03:27.039 --> 00:03:33.300
which is Daniel at M -A -N -A -R -Y dot H -A
00:03:33.300 --> 00:03:35.800
-U -S. Thanks for listening.
