WEBVTT Kind: captions Language: en 00:00:00.400 --> 00:00:04.950 align:start position:0% Jev,<00:00:00.960> Jev,<00:00:01.600> Jev.<00:00:02.399> Welcome<00:00:02.879> to<00:00:03.760> Jev<00:00:04.240> week<00:00:04.560> on 00:00:04.950 --> 00:00:04.960 align:start position:0% Jev, Jev, Jev. Welcome to Jev week on 00:00:04.960 --> 00:00:09.190 align:start position:0% Jev, Jev, Jev. Welcome to Jev week on how<00:00:05.440> I<00:00:05.839> AI.<00:00:07.040> We<00:00:07.359> have<00:00:07.600> seen<00:00:08.000> a<00:00:08.480> lot<00:00:08.720> of<00:00:08.960> new 00:00:09.190 --> 00:00:09.200 align:start position:0% how I AI. We have seen a lot of new 00:00:09.200 --> 00:00:13.509 align:start position:0% how I AI. We have seen a lot of new models<00:00:09.679> be<00:00:09.920> released<00:00:10.400> in<00:00:10.719> the<00:00:10.960> last<00:00:12.160> 5<00:00:12.559> days. 00:00:13.509 --> 00:00:13.519 align:start position:0% models be released in the last 5 days. 00:00:13.519 --> 00:00:17.990 align:start position:0% models be released in the last 5 days. We<00:00:13.759> saw<00:00:14.000> Opus<00:00:14.559> 55.<00:00:15.200> We<00:00:15.360> saw<00:00:15.679> GPT6<00:00:16.560> Soul,<00:00:17.119> GPT6 00:00:17.990 --> 00:00:18.000 align:start position:0% We saw Opus 55. We saw GPT6 Soul, GPT6 00:00:18.000 --> 00:00:21.029 align:start position:0% We saw Opus 55. We saw GPT6 Soul, GPT6 Luna.<00:00:18.960> Muse<00:00:19.279> is<00:00:19.520> blowing<00:00:19.920> up<00:00:20.080> the<00:00:20.240> timeline. 00:00:21.029 --> 00:00:21.039 align:start position:0% Luna. Muse is blowing up the timeline. 00:00:21.039 --> 00:00:23.590 align:start position:0% Luna. Muse is blowing up the timeline. Everybody<00:00:21.439> still<00:00:21.760> loves<00:00:22.000> their<00:00:22.240> Grock<00:00:22.640> bots. 00:00:23.590 --> 00:00:23.600 align:start position:0% Everybody still loves their Grock bots. 00:00:23.600 --> 00:00:26.870 align:start position:0% Everybody still loves their Grock bots. And<00:00:23.840> yet<00:00:24.160> there<00:00:24.400> is<00:00:24.800> one<00:00:25.359> thing<00:00:26.160> that<00:00:26.480> I<00:00:26.720> want 00:00:26.870 --> 00:00:26.880 align:start position:0% And yet there is one thing that I want 00:00:26.880 --> 00:00:29.509 align:start position:0% And yet there is one thing that I want to<00:00:26.960> talk<00:00:27.119> about<00:00:27.359> in<00:00:27.680> AI<00:00:28.080> right<00:00:28.240> now<00:00:28.960> and<00:00:29.199> that 00:00:29.509 --> 00:00:29.519 align:start position:0% to talk about in AI right now and that 00:00:29.519 --> 00:00:35.910 align:start position:0% to talk about in AI right now and that is<00:00:30.480> this<00:00:31.039> fast<00:00:32.399> cheap<00:00:33.840> doesn't<00:00:34.239> speak<00:00:35.360> system 00:00:35.910 --> 00:00:35.920 align:start position:0% is this fast cheap doesn't speak system 00:00:35.920 --> 00:00:41.110 align:start position:0% is this fast cheap doesn't speak system one<00:00:37.040> decision<00:00:37.520> model<00:00:38.160> from<00:00:38.719> Typesafe<00:00:39.520> AI.<00:00:40.800> As 00:00:41.110 --> 00:00:41.120 align:start position:0% one decision model from Typesafe AI. As 00:00:41.120 --> 00:00:44.150 align:start position:0% one decision model from Typesafe AI. As soon<00:00:41.280> as<00:00:41.440> I<00:00:41.600> saw<00:00:41.840> this<00:00:42.079> trending<00:00:43.200> on<00:00:43.520> X,<00:00:43.920> as 00:00:44.150 --> 00:00:44.160 align:start position:0% soon as I saw this trending on X, as 00:00:44.160 --> 00:00:47.350 align:start position:0% soon as I saw this trending on X, as soon<00:00:44.320> as<00:00:44.399> I<00:00:44.559> saw<00:00:44.719> it<00:00:44.960> launched,<00:00:46.079> I<00:00:46.559> immediately 00:00:47.350 --> 00:00:47.360 align:start position:0% soon as I saw it launched, I immediately 00:00:47.360 --> 00:00:49.510 align:start position:0% soon as I saw it launched, I immediately started<00:00:47.840> testing<00:00:48.239> it.<00:00:48.480> Now,<00:00:48.800> what<00:00:48.960> I<00:00:49.120> will<00:00:49.280> say 00:00:49.510 --> 00:00:49.520 align:start position:0% started testing it. Now, what I will say 00:00:49.520 --> 00:00:51.670 align:start position:0% started testing it. Now, what I will say is<00:00:50.239> more<00:00:50.480> than<00:00:50.640> any<00:00:50.879> other<00:00:51.120> model<00:00:51.440> I've 00:00:51.670 --> 00:00:51.680 align:start position:0% is more than any other model I've 00:00:51.680 --> 00:00:54.069 align:start position:0% is more than any other model I've experienced<00:00:52.160> lately,<00:00:52.960> Jev<00:00:53.440> has<00:00:53.600> been<00:00:53.760> the<00:00:53.920> one 00:00:54.069 --> 00:00:54.079 align:start position:0% experienced lately, Jev has been the one 00:00:54.079 --> 00:00:56.310 align:start position:0% experienced lately, Jev has been the one that<00:00:54.320> has<00:00:54.800> exploded 00:00:56.310 --> 00:00:56.320 align:start position:0% that has exploded 00:00:56.320 --> 00:00:58.630 align:start position:0% that has exploded use<00:00:56.640> cases,<00:00:57.360> personal<00:00:57.840> productivity<00:00:58.399> use 00:00:58.630 --> 00:00:58.640 align:start position:0% use cases, personal productivity use 00:00:58.640 --> 00:01:01.750 align:start position:0% use cases, personal productivity use cases,<00:00:59.600> code<00:00:59.920> use<00:01:00.160> cases,<00:01:01.120> product<00:01:01.520> use 00:01:01.750 --> 00:01:01.760 align:start position:0% cases, code use cases, product use 00:01:01.760 --> 00:01:03.750 align:start position:0% cases, code use cases, product use cases.<00:01:02.559> Today<00:01:02.879> I'm<00:01:03.120> going<00:01:03.199> to<00:01:03.280> give<00:01:03.359> you<00:01:03.520> a 00:01:03.750 --> 00:01:03.760 align:start position:0% cases. Today I'm going to give you a 00:01:03.760 --> 00:01:06.310 align:start position:0% cases. Today I'm going to give you a very<00:01:04.080> quick<00:01:04.320> whirlwind<00:01:04.879> tour<00:01:05.119> of<00:01:05.600> what<00:01:05.920> Jeb 00:01:06.310 --> 00:01:06.320 align:start position:0% very quick whirlwind tour of what Jeb 00:01:06.320 --> 00:01:08.630 align:start position:0% very quick whirlwind tour of what Jeb is,<00:01:07.040> what<00:01:07.280> it<00:01:07.439> will<00:01:07.520> give<00:01:07.680> you<00:01:07.840> back<00:01:08.159> and<00:01:08.400> what 00:01:08.630 --> 00:01:08.640 align:start position:0% is, what it will give you back and what 00:01:08.640 --> 00:01:11.990 align:start position:0% is, what it will give you back and what it<00:01:08.799> won't,<00:01:09.760> and<00:01:10.000> then<00:01:10.560> how<00:01:10.880> I<00:01:11.200> have<00:01:11.360> used<00:01:11.600> it 00:01:11.990 --> 00:01:12.000 align:start position:0% it won't, and then how I have used it 00:01:12.000 --> 00:01:14.789 align:start position:0% it won't, and then how I have used it over<00:01:12.240> the<00:01:12.479> last<00:01:13.119> week<00:01:13.520> to<00:01:13.760> do<00:01:14.000> work<00:01:14.240> that<00:01:14.479> I 00:01:14.789 --> 00:01:14.799 align:start position:0% over the last week to do work that I 00:01:14.799 --> 00:01:17.350 align:start position:0% over the last week to do work that I think<00:01:14.960> is<00:01:15.200> worth<00:01:15.920> hundreds<00:01:16.400> of<00:01:16.560> thousands<00:01:17.119> if 00:01:17.350 --> 00:01:17.360 align:start position:0% think is worth hundreds of thousands if 00:01:17.360 --> 00:01:20.230 align:start position:0% think is worth hundreds of thousands if not<00:01:17.759> millions<00:01:18.400> of<00:01:18.720> dollars.<00:01:19.360> And<00:01:19.680> I<00:01:20.000> have 00:01:20.230 --> 00:01:20.240 align:start position:0% not millions of dollars. And I have 00:01:20.240 --> 00:01:24.789 align:start position:0% not millions of dollars. And I have probably<00:01:20.720> spent<00:01:21.759> sub<00:01:22.320> $10<00:01:22.960> on<00:01:23.280> Jev<00:01:23.680> tokens.<00:01:24.560> A 00:01:24.789 --> 00:01:24.799 align:start position:0% probably spent sub $10 on Jev tokens. A 00:01:24.799 --> 00:01:26.310 align:start position:0% probably spent sub $10 on Jev tokens. A lot<00:01:24.880> of<00:01:24.960> it<00:01:25.119> has<00:01:25.280> been<00:01:25.439> subsidized<00:01:26.000> because 00:01:26.310 --> 00:01:26.320 align:start position:0% lot of it has been subsidized because 00:01:26.320 --> 00:01:28.789 align:start position:0% lot of it has been subsidized because Jeb<00:01:26.720> is<00:01:26.880> currently<00:01:27.200> free<00:01:27.439> on<00:01:27.600> the<00:01:27.680> AI<00:01:28.400> gateway 00:01:28.789 --> 00:01:28.799 align:start position:0% Jeb is currently free on the AI gateway 00:01:28.799 --> 00:01:32.870 align:start position:0% Jeb is currently free on the AI gateway by<00:01:29.040> Versel.<00:01:30.159> But<00:01:30.720> even<00:01:31.040> at<00:01:31.360> list<00:01:31.680> price,<00:01:32.560> it<00:01:32.799> is 00:01:32.870 --> 00:01:32.880 align:start position:0% by Versel. But even at list price, it is 00:01:32.880 --> 00:01:35.030 align:start position:0% by Versel. But even at list price, it is a<00:01:33.040> very<00:01:33.360> inexpensive<00:01:34.079> model.<00:01:34.400> It<00:01:34.640> is<00:01:34.720> a<00:01:34.880> very 00:01:35.030 --> 00:01:35.040 align:start position:0% a very inexpensive model. It is a very 00:01:35.040 --> 00:01:37.510 align:start position:0% a very inexpensive model. It is a very effective<00:01:35.439> model<00:01:35.759> and<00:01:36.000> it<00:01:36.400> is<00:01:36.720> going<00:01:36.960> to<00:01:37.200> be<00:01:37.280> in 00:01:37.510 --> 00:01:37.520 align:start position:0% effective model and it is going to be in 00:01:37.520 --> 00:01:39.270 align:start position:0% effective model and it is going to be in the<00:01:37.680> middle<00:01:37.840> of<00:01:38.159> almost<00:01:38.479> everything<00:01:38.799> I<00:01:39.040> build 00:01:39.270 --> 00:01:39.280 align:start position:0% the middle of almost everything I build 00:01:39.280 --> 00:01:41.190 align:start position:0% the middle of almost everything I build from<00:01:39.439> here<00:01:39.600> on<00:01:39.759> out.<00:01:40.216> [music]<00:01:40.400> So,<00:01:40.799> let's<00:01:41.119> get 00:01:41.190 --> 00:01:41.200 align:start position:0% from here on out. [music] So, let's get 00:01:41.200 --> 00:01:44.149 align:start position:0% from here on out. [music] So, let's get to<00:01:41.360> it.<00:01:41.920> This<00:01:42.400> episode<00:01:42.799> is<00:01:43.119> brought<00:01:43.360> to<00:01:43.520> you<00:01:43.759> by 00:01:44.149 --> 00:01:44.159 align:start position:0% to it. This episode is brought to you by 00:01:44.159 --> 00:01:47.109 align:start position:0% to it. This episode is brought to you by Open<00:01:44.560> Art<00:01:44.880> Arena,<00:01:45.840> the<00:01:46.079> global<00:01:46.479> leaderboard 00:01:47.109 --> 00:01:47.119 align:start position:0% Open Art Arena, the global leaderboard 00:01:47.119 --> 00:01:50.149 align:start position:0% Open Art Arena, the global leaderboard for<00:01:47.520> creative<00:01:48.079> intelligence.<00:01:49.360> Every<00:01:49.759> week, 00:01:50.149 --> 00:01:50.159 align:start position:0% for creative intelligence. Every week, 00:01:50.159 --> 00:01:52.870 align:start position:0% for creative intelligence. Every week, new<00:01:50.399> AI<00:01:50.880> models<00:01:51.200> launch,<00:01:51.680> and<00:01:52.159> everyone 00:01:52.870 --> 00:01:52.880 align:start position:0% new AI models launch, and everyone 00:01:52.880 --> 00:01:56.550 align:start position:0% new AI models launch, and everyone claims<00:01:53.280> to<00:01:53.439> be<00:01:53.600> the<00:01:53.840> best.<00:01:54.479> But<00:01:55.040> best<00:01:55.360> at<00:01:55.600> what? 00:01:56.550 --> 00:01:56.560 align:start position:0% claims to be the best. But best at what? 00:01:56.560 --> 00:01:58.789 align:start position:0% claims to be the best. But best at what? Open<00:01:56.960> Art<00:01:57.200> Arena<00:01:57.680> is<00:01:57.840> built<00:01:58.079> to<00:01:58.320> answer<00:01:58.560> the 00:01:58.789 --> 00:01:58.799 align:start position:0% Open Art Arena is built to answer the 00:01:58.799 --> 00:02:01.109 align:start position:0% Open Art Arena is built to answer the question<00:01:59.040> that<00:01:59.360> actually<00:01:59.759> matters.<00:02:00.799> Which 00:02:01.109 --> 00:02:01.119 align:start position:0% question that actually matters. Which 00:02:01.119 --> 00:02:03.510 align:start position:0% question that actually matters. Which model<00:02:01.600> is<00:02:01.831> [music]<00:02:01.920> best<00:02:02.240> for<00:02:02.560> your<00:02:02.960> specific 00:02:03.510 --> 00:02:03.520 align:start position:0% model is [music] best for your specific 00:02:03.520 --> 00:02:06.310 align:start position:0% model is [music] best for your specific job?<00:02:04.399> Instead<00:02:04.719> of<00:02:04.880> one<00:02:05.200> overall<00:02:05.600> winner,<00:02:06.079> Open 00:02:06.310 --> 00:02:06.320 align:start position:0% job? Instead of one overall winner, Open 00:02:06.320 --> 00:02:09.270 align:start position:0% job? Instead of one overall winner, Open Art<00:02:06.560> Arena<00:02:07.119> ranks<00:02:07.600> models<00:02:08.080> across<00:02:08.720> real 00:02:09.270 --> 00:02:09.280 align:start position:0% Art Arena ranks models across real 00:02:09.280 --> 00:02:12.309 align:start position:0% Art Arena ranks models across real creative<00:02:09.759> tasks<00:02:10.720> from<00:02:11.120> advertising<00:02:11.760> and<00:02:12.080> film 00:02:12.309 --> 00:02:12.319 align:start position:0% creative tasks from advertising and film 00:02:12.319 --> 00:02:15.110 align:start position:0% creative tasks from advertising and film to<00:02:12.640> animation,<00:02:13.520> product,<00:02:14.160> graphic<00:02:14.640> design, 00:02:15.110 --> 00:02:15.120 align:start position:0% to animation, product, graphic design, 00:02:15.120 --> 00:02:16.790 align:start position:0% to animation, product, graphic design, editing,<00:02:15.680> and<00:02:15.920> lip-sync<00:02:16.241> [music] 00:02:16.790 --> 00:02:16.800 align:start position:0% editing, and lip-sync [music] 00:02:16.800 --> 00:02:19.750 align:start position:0% editing, and lip-sync [music] covering<00:02:17.200> both<00:02:17.520> image<00:02:18.080> and<00:02:18.480> video.<00:02:19.280> And<00:02:19.520> these 00:02:19.750 --> 00:02:19.760 align:start position:0% covering both image and video. And these 00:02:19.760 --> 00:02:21.670 align:start position:0% covering both image and video. And these rankings<00:02:20.160> aren't<00:02:20.480> based<00:02:20.720> on<00:02:20.959> hype.<00:02:21.440> They're 00:02:21.670 --> 00:02:21.680 align:start position:0% rankings aren't based on hype. They're 00:02:21.680 --> 00:02:23.430 align:start position:0% rankings aren't based on hype. They're judged<00:02:21.920> by<00:02:22.160> professionals,<00:02:22.959> industry 00:02:23.430 --> 00:02:23.440 align:start position:0% judged by professionals, industry 00:02:23.440 --> 00:02:25.270 align:start position:0% judged by professionals, industry leaders,<00:02:23.920> and<00:02:24.160> working<00:02:24.480> creators<00:02:24.959> through 00:02:25.270 --> 00:02:25.280 align:start position:0% leaders, and working creators through 00:02:25.280 --> 00:02:28.229 align:start position:0% leaders, and working creators through blind<00:02:25.760> evaluations.<00:02:27.040> So<00:02:27.280> judges<00:02:27.760> never<00:02:28.080> know 00:02:28.229 --> 00:02:28.239 align:start position:0% blind evaluations. So judges never know 00:02:28.239 --> 00:02:30.630 align:start position:0% blind evaluations. So judges never know which<00:02:28.560> model<00:02:28.879> produced<00:02:29.360> which<00:02:29.599> output.<00:02:30.400> That 00:02:30.630 --> 00:02:30.640 align:start position:0% which model produced which output. That 00:02:30.640 --> 00:02:32.790 align:start position:0% which model produced which output. That means<00:02:30.879> you<00:02:31.120> can<00:02:31.200> see<00:02:31.360> how<00:02:31.599> models<00:02:32.239> actually 00:02:32.790 --> 00:02:32.800 align:start position:0% means you can see how models actually 00:02:32.800 --> 00:02:34.630 align:start position:0% means you can see how models actually perform<00:02:33.280> when<00:02:33.519> it<00:02:33.680> comes<00:02:33.840> to<00:02:34.000> the<00:02:34.239> creative 00:02:34.630 --> 00:02:34.640 align:start position:0% perform when it comes to the creative 00:02:34.640 --> 00:02:36.790 align:start position:0% perform when it comes to the creative work<00:02:34.879> you're<00:02:35.200> doing.<00:02:35.920> So<00:02:36.160> stop<00:02:36.480> guessing 00:02:36.790 --> 00:02:36.800 align:start position:0% work you're doing. So stop guessing 00:02:36.800 --> 00:02:39.190 align:start position:0% work you're doing. So stop guessing which<00:02:37.040> model<00:02:37.280> to<00:02:37.519> use.<00:02:38.160> Explore<00:02:38.720> rankings 00:02:39.190 --> 00:02:39.200 align:start position:0% which model to use. Explore rankings 00:02:39.200 --> 00:02:41.589 align:start position:0% which model to use. Explore rankings based<00:02:39.519> on<00:02:39.840> real<00:02:40.239> creative<00:02:40.720> work<00:02:40.959> and<00:02:41.200> find<00:02:41.360> the 00:02:41.589 --> 00:02:41.599 align:start position:0% based on real creative work and find the 00:02:41.599 --> 00:02:44.070 align:start position:0% based on real creative work and find the right<00:02:41.840> model<00:02:42.160> for<00:02:42.400> your<00:02:42.800> project<00:02:43.440> and<00:02:43.760> save 00:02:44.070 --> 00:02:44.080 align:start position:0% right model for your project and save 00:02:44.080 --> 00:02:48.150 align:start position:0% right model for your project and save time<00:02:44.879> and<00:02:45.200> cost.<00:02:46.319> See<00:02:46.560> the<00:02:46.720> rankings<00:02:47.280> at<00:02:47.760> Open 00:02:48.150 --> 00:02:48.160 align:start position:0% time and cost. See the rankings at Open 00:02:48.160 --> 00:02:50.790 align:start position:0% time and cost. See the rankings at Open Art<00:02:48.720> Arena.<00:02:49.599> So<00:02:49.760> if<00:02:49.920> I<00:02:50.000> were<00:02:50.160> to<00:02:50.239> explain<00:02:50.480> Jev 00:02:50.790 --> 00:02:50.800 align:start position:0% Art Arena. So if I were to explain Jev 00:02:50.800 --> 00:02:52.309 align:start position:0% Art Arena. So if I were to explain Jev to<00:02:50.959> you,<00:02:51.120> I<00:02:51.280> would<00:02:51.360> go<00:02:51.519> to<00:02:51.599> this<00:02:51.760> table<00:02:52.000> on<00:02:52.160> the 00:02:52.309 --> 00:02:52.319 align:start position:0% to you, I would go to this table on the 00:02:52.319 --> 00:02:54.949 align:start position:0% to you, I would go to this table on the type<00:02:53.040> blog<00:02:53.360> post<00:02:53.680> announcing<00:02:54.160> Jev.<00:02:54.560> And<00:02:54.720> it 00:02:54.949 --> 00:02:54.959 align:start position:0% type blog post announcing Jev. And it 00:02:54.959 --> 00:02:57.430 align:start position:0% type blog post announcing Jev. And it basically<00:02:55.280> compares<00:02:56.239> normal<00:02:56.560> LLMs<00:02:57.200> on<00:02:57.360> the 00:02:57.430 --> 00:02:57.440 align:start position:0% basically compares normal LLMs on the 00:02:57.440 --> 00:03:00.710 align:start position:0% basically compares normal LLMs on the left,<00:02:58.000> Jev<00:02:58.400> style<00:02:58.720> LLMs<00:02:59.360> on<00:02:59.519> the<00:02:59.599> right.<00:03:00.400> Both 00:03:00.710 --> 00:03:00.720 align:start position:0% left, Jev style LLMs on the right. Both 00:03:00.720 --> 00:03:02.630 align:start position:0% left, Jev style LLMs on the right. Both take<00:03:00.879> in<00:03:01.120> unstructured<00:03:01.760> data<00:03:01.920> as<00:03:02.159> inputs. 00:03:02.630 --> 00:03:02.640 align:start position:0% take in unstructured data as inputs. 00:03:02.640 --> 00:03:04.550 align:start position:0% take in unstructured data as inputs. Both<00:03:02.800> take<00:03:02.959> in<00:03:03.280> text<00:03:03.519> as<00:03:03.680> inputs.<00:03:04.080> Jev<00:03:04.400> does 00:03:04.550 --> 00:03:04.560 align:start position:0% Both take in text as inputs. Jev does 00:03:04.560 --> 00:03:06.949 align:start position:0% Both take in text as inputs. Jev does not<00:03:04.720> take<00:03:04.800> in<00:03:05.120> images,<00:03:06.080> but<00:03:06.239> it<00:03:06.400> takes<00:03:06.560> in<00:03:06.800> text 00:03:06.949 --> 00:03:06.959 align:start position:0% not take in images, but it takes in text 00:03:06.959 --> 00:03:08.630 align:start position:0% not take in images, but it takes in text and<00:03:07.120> it<00:03:07.200> takes<00:03:07.360> in<00:03:07.599> text<00:03:07.840> descriptions<00:03:08.400> of 00:03:08.630 --> 00:03:08.640 align:start position:0% and it takes in text descriptions of 00:03:08.640 --> 00:03:10.470 align:start position:0% and it takes in text descriptions of images<00:03:08.959> if<00:03:09.120> you<00:03:09.200> really<00:03:09.440> need<00:03:09.599> to<00:03:09.680> get<00:03:09.840> there. 00:03:10.470 --> 00:03:10.480 align:start position:0% images if you really need to get there. 00:03:10.480 --> 00:03:12.390 align:start position:0% images if you really need to get there. The<00:03:10.800> outputs<00:03:11.280> though<00:03:11.519> are<00:03:11.680> very<00:03:12.000> different. 00:03:12.390 --> 00:03:12.400 align:start position:0% The outputs though are very different. 00:03:12.400 --> 00:03:14.309 align:start position:0% The outputs though are very different. With<00:03:12.720> the<00:03:12.959> standard<00:03:13.280> LLMs<00:03:13.840> that<00:03:13.920> you're<00:03:14.159> used 00:03:14.309 --> 00:03:14.319 align:start position:0% With the standard LLMs that you're used 00:03:14.319 --> 00:03:16.390 align:start position:0% With the standard LLMs that you're used to<00:03:14.480> working<00:03:14.720> with,<00:03:15.120> you<00:03:15.360> are<00:03:15.599> getting<00:03:16.000> strings 00:03:16.390 --> 00:03:16.400 align:start position:0% to working with, you are getting strings 00:03:16.400 --> 00:03:17.990 align:start position:0% to working with, you are getting strings and<00:03:16.640> generated<00:03:17.120> text<00:03:17.360> out.<00:03:17.599> So<00:03:17.760> you're 00:03:17.990 --> 00:03:18.000 align:start position:0% and generated text out. So you're 00:03:18.000 --> 00:03:20.790 align:start position:0% and generated text out. So you're getting<00:03:18.400> text<00:03:18.720> in,<00:03:19.120> text<00:03:19.440> out.<00:03:20.080> With<00:03:20.319> Jev, 00:03:20.790 --> 00:03:20.800 align:start position:0% getting text in, text out. With Jev, 00:03:20.800 --> 00:03:23.430 align:start position:0% getting text in, text out. With Jev, you're<00:03:21.120> getting<00:03:21.280> text<00:03:21.599> in,<00:03:22.560> type<00:03:22.879> safe<00:03:23.120> values 00:03:23.430 --> 00:03:23.440 align:start position:0% you're getting text in, type safe values 00:03:23.440 --> 00:03:25.270 align:start position:0% you're getting text in, type safe values out.<00:03:23.680> And<00:03:23.760> what<00:03:23.920> I<00:03:24.080> mean<00:03:24.159> by<00:03:24.319> type<00:03:24.640> safe<00:03:24.959> values 00:03:25.270 --> 00:03:25.280 align:start position:0% out. And what I mean by type safe values 00:03:25.280 --> 00:03:27.830 align:start position:0% out. And what I mean by type safe values is<00:03:25.519> these<00:03:25.760> are<00:03:25.920> values<00:03:26.319> that<00:03:26.480> are<00:03:26.720> predefined 00:03:27.830 --> 00:03:27.840 align:start position:0% is these are values that are predefined 00:03:27.840 --> 00:03:30.309 align:start position:0% is these are values that are predefined that<00:03:28.080> then<00:03:28.319> Jev<00:03:28.800> picks<00:03:29.120> from<00:03:29.360> and<00:03:29.680> selects<00:03:30.080> and 00:03:30.309 --> 00:03:30.319 align:start position:0% that then Jev picks from and selects and 00:03:30.319 --> 00:03:32.390 align:start position:0% that then Jev picks from and selects and returns<00:03:30.720> to<00:03:30.879> you.<00:03:31.680> We<00:03:31.840> will<00:03:32.000> show<00:03:32.080> you<00:03:32.239> what 00:03:32.390 --> 00:03:32.400 align:start position:0% returns to you. We will show you what 00:03:32.400 --> 00:03:33.670 align:start position:0% returns to you. We will show you what those<00:03:32.560> values<00:03:32.879> are,<00:03:33.040> but<00:03:33.360> essentially 00:03:33.670 --> 00:03:33.680 align:start position:0% those values are, but essentially 00:03:33.680 --> 00:03:36.470 align:start position:0% those values are, but essentially they're<00:03:33.920> like<00:03:34.799> it's<00:03:35.120> this<00:03:35.360> or<00:03:35.519> that.<00:03:36.080> It's<00:03:36.319> yes 00:03:36.470 --> 00:03:36.480 align:start position:0% they're like it's this or that. It's yes 00:03:36.480 --> 00:03:38.869 align:start position:0% they're like it's this or that. It's yes or<00:03:36.720> no.<00:03:37.280> It's<00:03:37.519> 1<00:03:37.760> through<00:03:38.000> 10.<00:03:38.319> Like<00:03:38.560> it's 00:03:38.869 --> 00:03:38.879 align:start position:0% or no. It's 1 through 10. Like it's 00:03:38.879 --> 00:03:41.589 align:start position:0% or no. It's 1 through 10. Like it's pretty<00:03:39.760> simple.<00:03:40.159> Now<00:03:40.400> it<00:03:40.720> sounds<00:03:41.040> simple,<00:03:41.440> but 00:03:41.589 --> 00:03:41.599 align:start position:0% pretty simple. Now it sounds simple, but 00:03:41.599 --> 00:03:44.390 align:start position:0% pretty simple. Now it sounds simple, but it<00:03:41.840> is<00:03:42.080> incredibly<00:03:42.879> powerful<00:03:43.760> when<00:03:44.080> you<00:03:44.239> put 00:03:44.390 --> 00:03:44.400 align:start position:0% it is incredibly powerful when you put 00:03:44.400 --> 00:03:47.030 align:start position:0% it is incredibly powerful when you put it<00:03:44.640> against<00:03:45.040> the<00:03:45.280> right<00:03:45.680> problem. 00:03:47.030 --> 00:03:47.040 align:start position:0% it against the right problem. 00:03:47.040 --> 00:03:49.509 align:start position:0% it against the right problem. The<00:03:47.360> other<00:03:47.599> thing<00:03:47.680> that<00:03:48.000> you<00:03:48.239> will<00:03:48.480> notice 00:03:49.509 --> 00:03:49.519 align:start position:0% The other thing that you will notice 00:03:49.519 --> 00:03:53.350 align:start position:0% The other thing that you will notice about<00:03:49.920> Jeff<00:03:50.319> is<00:03:50.560> it<00:03:50.799> is<00:03:51.120> cheap<00:03:51.599> AF<00:03:52.640> and<00:03:52.879> it<00:03:53.120> is 00:03:53.350 --> 00:03:53.360 align:start position:0% about Jeff is it is cheap AF and it is 00:03:53.360 --> 00:03:56.789 align:start position:0% about Jeff is it is cheap AF and it is fast<00:03:53.920> AF.<00:03:54.640> And<00:03:54.879> so<00:03:55.680> if<00:03:55.920> you<00:03:56.080> look<00:03:56.319> at<00:03:56.480> the 00:03:56.789 --> 00:03:56.799 align:start position:0% fast AF. And so if you look at the 00:03:56.799 --> 00:03:58.789 align:start position:0% fast AF. And so if you look at the current<00:03:57.040> cost<00:03:57.280> of<00:03:57.519> input<00:03:57.840> and<00:03:58.000> output<00:03:58.319> tokens, 00:03:58.789 --> 00:03:58.799 align:start position:0% current cost of input and output tokens, 00:03:58.799 --> 00:04:01.910 align:start position:0% current cost of input and output tokens, it<00:03:58.959> can<00:03:59.120> be<00:03:59.360> pennies<00:03:59.840> to<00:04:00.239> tens<00:04:01.120> or<00:04:01.439> hundreds<00:04:01.760> of 00:04:01.910 --> 00:04:01.920 align:start position:0% it can be pennies to tens or hundreds of 00:04:01.920 --> 00:04:04.710 align:start position:0% it can be pennies to tens or hundreds of dollars<00:04:02.239> per<00:04:02.480> million<00:04:02.799> output<00:04:03.200> tokens. 00:04:04.710 --> 00:04:04.720 align:start position:0% dollars per million output tokens. 00:04:04.720 --> 00:04:06.789 align:start position:0% dollars per million output tokens. Jev<00:04:05.120> only<00:04:05.360> charges<00:04:05.760> you<00:04:05.920> on<00:04:06.159> input<00:04:06.480> tokens 00:04:06.789 --> 00:04:06.799 align:start position:0% Jev only charges you on input tokens 00:04:06.799 --> 00:04:10.390 align:start position:0% Jev only charges you on input tokens because<00:04:06.959> it<00:04:07.120> barely<00:04:07.519> outputs<00:04:08.319> anything.<00:04:09.599> And 00:04:10.390 --> 00:04:10.400 align:start position:0% because it barely outputs anything. And 00:04:10.400 --> 00:04:14.710 align:start position:0% because it barely outputs anything. And it<00:04:10.720> is<00:04:11.920> 4<00:04:12.239> cents<00:04:12.799> per<00:04:13.120> million<00:04:13.760> input<00:04:14.239> tokens. 00:04:14.710 --> 00:04:14.720 align:start position:0% it is 4 cents per million input tokens. 00:04:14.720 --> 00:04:18.069 align:start position:0% it is 4 cents per million input tokens. It<00:04:14.959> is<00:04:15.040> like<00:04:15.519> dirt<00:04:16.400> freaking<00:04:17.040> cheap.<00:04:17.840> And 00:04:18.069 --> 00:04:18.079 align:start position:0% It is like dirt freaking cheap. And 00:04:18.079 --> 00:04:21.749 align:start position:0% It is like dirt freaking cheap. And because<00:04:19.040> they<00:04:19.440> output<00:04:20.799> basically<00:04:21.359> nothing, 00:04:21.749 --> 00:04:21.759 align:start position:0% because they output basically nothing, 00:04:21.759 --> 00:04:24.230 align:start position:0% because they output basically nothing, they<00:04:21.919> don't<00:04:22.079> even<00:04:22.320> charge<00:04:22.639> you<00:04:23.280> for<00:04:23.600> output 00:04:24.230 --> 00:04:24.240 align:start position:0% they don't even charge you for output 00:04:24.240 --> 00:04:27.510 align:start position:0% they don't even charge you for output tokens.<00:04:25.120> Um<00:04:25.600> whereas<00:04:26.240> the<00:04:26.639> standard<00:04:26.960> LM<00:04:27.360> are 00:04:27.510 --> 00:04:27.520 align:start position:0% tokens. Um whereas the standard LM are 00:04:27.520 --> 00:04:30.550 align:start position:0% tokens. Um whereas the standard LM are going<00:04:27.600> to<00:04:27.680> charge<00:04:27.919> you<00:04:28.639> tons<00:04:29.120> for<00:04:29.520> the<00:04:29.759> output 00:04:30.550 --> 00:04:30.560 align:start position:0% going to charge you tons for the output 00:04:30.560 --> 00:04:32.550 align:start position:0% going to charge you tons for the output tokens.<00:04:31.199> And<00:04:31.360> then<00:04:31.440> I'll<00:04:31.680> go<00:04:31.759> into<00:04:32.000> use<00:04:32.160> cases, 00:04:32.550 --> 00:04:32.560 align:start position:0% tokens. And then I'll go into use cases, 00:04:32.560 --> 00:04:33.670 align:start position:0% tokens. And then I'll go into use cases, which<00:04:32.720> is<00:04:32.800> how<00:04:32.960> you<00:04:33.120> would<00:04:33.280> use<00:04:33.360> like<00:04:33.520> a 00:04:33.670 --> 00:04:33.680 align:start position:0% which is how you would use like a 00:04:33.680 --> 00:04:35.590 align:start position:0% which is how you would use like a standard<00:04:33.919> LLM<00:04:34.560> versus<00:04:34.960> why<00:04:35.199> you<00:04:35.360> would<00:04:35.440> use 00:04:35.590 --> 00:04:35.600 align:start position:0% standard LLM versus why you would use 00:04:35.600 --> 00:04:38.390 align:start position:0% standard LLM versus why you would use Jev.<00:04:36.400> You<00:04:36.560> know,<00:04:36.800> standard<00:04:37.120> LMS,<00:04:37.759> chat<00:04:38.000> bots 00:04:38.390 --> 00:04:38.400 align:start position:0% Jev. You know, standard LMS, chat bots 00:04:38.400 --> 00:04:39.749 align:start position:0% Jev. You know, standard LMS, chat bots where<00:04:38.560> you<00:04:38.639> want<00:04:38.800> text<00:04:38.960> in,<00:04:39.280> you<00:04:39.360> want<00:04:39.440> text 00:04:39.749 --> 00:04:39.759 align:start position:0% where you want text in, you want text 00:04:39.759 --> 00:04:42.150 align:start position:0% where you want text in, you want text out.<00:04:40.320> Coding<00:04:40.960> where<00:04:41.199> you<00:04:41.360> want,<00:04:41.759> you<00:04:41.919> know, 00:04:42.150 --> 00:04:42.160 align:start position:0% out. Coding where you want, you know, 00:04:42.160 --> 00:04:45.350 align:start position:0% out. Coding where you want, you know, code<00:04:42.560> to<00:04:42.800> be<00:04:43.040> produced.<00:04:44.160> Um,<00:04:44.479> and<00:04:44.720> so<00:04:45.040> it's 00:04:45.350 --> 00:04:45.360 align:start position:0% code to be produced. Um, and so it's 00:04:45.360 --> 00:04:47.830 align:start position:0% code to be produced. Um, and so it's it's<00:04:45.759> great<00:04:46.000> for<00:04:46.400> things<00:04:46.639> where<00:04:46.960> you<00:04:47.199> need 00:04:47.830 --> 00:04:47.840 align:start position:0% it's great for things where you need 00:04:47.840 --> 00:04:51.430 align:start position:0% it's great for things where you need stuff<00:04:48.320> generated,<00:04:49.600> but<00:04:50.000> Jev<00:04:50.479> is<00:04:50.720> really<00:04:51.040> great 00:04:51.430 --> 00:04:51.440 align:start position:0% stuff generated, but Jev is really great 00:04:51.440 --> 00:04:54.070 align:start position:0% stuff generated, but Jev is really great for<00:04:52.400> making<00:04:52.720> decisions.<00:04:53.360> That's<00:04:53.680> ultimately 00:04:54.070 --> 00:04:54.080 align:start position:0% for making decisions. That's ultimately 00:04:54.080 --> 00:04:55.189 align:start position:0% for making decisions. That's ultimately I've<00:04:54.240> been<00:04:54.400> calling<00:04:54.560> this<00:04:54.800> it's<00:04:54.960> like<00:04:55.040> a 00:04:55.189 --> 00:04:55.199 align:start position:0% I've been calling this it's like a 00:04:55.199 --> 00:04:57.189 align:start position:0% I've been calling this it's like a decision<00:04:55.520> model.<00:04:56.160> So<00:04:56.320> you<00:04:56.720> give<00:04:56.880> it<00:04:57.040> a 00:04:57.189 --> 00:04:57.199 align:start position:0% decision model. So you give it a 00:04:57.199 --> 00:04:59.430 align:start position:0% decision model. So you give it a decision<00:04:57.520> and<00:04:57.759> it<00:04:58.000> makes<00:04:58.240> a<00:04:58.479> decision<00:04:58.720> and<00:04:59.040> and 00:04:59.430 --> 00:04:59.440 align:start position:0% decision and it makes a decision and and 00:04:59.440 --> 00:05:02.150 align:start position:0% decision and it makes a decision and and it's<00:04:59.680> high<00:05:00.000> agency<00:05:00.560> I<00:05:00.720> would<00:05:00.880> say.<00:05:01.520> So<00:05:01.680> if<00:05:01.919> you 00:05:02.150 --> 00:05:02.160 align:start position:0% it's high agency I would say. So if you 00:05:02.160 --> 00:05:05.830 align:start position:0% it's high agency I would say. So if you need<00:05:02.800> smart<00:05:03.759> if<00:05:04.320> statements,<00:05:05.280> should<00:05:05.520> I<00:05:05.680> go 00:05:05.830 --> 00:05:05.840 align:start position:0% need smart if statements, should I go 00:05:05.840 --> 00:05:09.029 align:start position:0% need smart if statements, should I go left<00:05:06.000> or<00:05:06.240> right?<00:05:06.880> If<00:05:07.120> it's<00:05:07.680> good,<00:05:08.639> put<00:05:08.800> it<00:05:08.880> to 00:05:09.029 --> 00:05:09.039 align:start position:0% left or right? If it's good, put it to 00:05:09.039 --> 00:05:10.629 align:start position:0% left or right? If it's good, put it to this<00:05:09.280> person.<00:05:09.520> If<00:05:09.680> it's<00:05:09.840> bad,<00:05:10.160> send<00:05:10.320> it<00:05:10.400> to 00:05:10.629 --> 00:05:10.639 align:start position:0% this person. If it's bad, send it to 00:05:10.639 --> 00:05:12.870 align:start position:0% this person. If it's bad, send it to support.<00:05:11.600> All<00:05:11.759> that<00:05:11.919> kind<00:05:12.080> of<00:05:12.160> stuff<00:05:12.479> Jeff<00:05:12.720> is 00:05:12.870 --> 00:05:12.880 align:start position:0% support. All that kind of stuff Jeff is 00:05:12.880 --> 00:05:14.310 align:start position:0% support. All that kind of stuff Jeff is really<00:05:13.039> good<00:05:13.120> at.<00:05:13.440> It's<00:05:13.759> really<00:05:14.000> good<00:05:14.080> at 00:05:14.310 --> 00:05:14.320 align:start position:0% really good at. It's really good at 00:05:14.320 --> 00:05:15.749 align:start position:0% really good at. It's really good at classifying<00:05:14.880> data.<00:05:15.199> That's<00:05:15.360> a<00:05:15.440> lot<00:05:15.520> of<00:05:15.600> what 00:05:15.749 --> 00:05:15.759 align:start position:0% classifying data. That's a lot of what 00:05:15.759 --> 00:05:17.189 align:start position:0% classifying data. That's a lot of what I'm<00:05:15.919> going<00:05:15.919> to<00:05:16.000> talk<00:05:16.160> to<00:05:16.240> you<00:05:16.400> about<00:05:16.560> today. 00:05:17.189 --> 00:05:17.199 align:start position:0% I'm going to talk to you about today. 00:05:17.199 --> 00:05:19.749 align:start position:0% I'm going to talk to you about today. And<00:05:17.280> it's<00:05:17.600> really<00:05:17.840> good<00:05:18.160> at<00:05:18.800> real<00:05:19.039> time.<00:05:19.520> So, 00:05:19.749 --> 00:05:19.759 align:start position:0% And it's really good at real time. So, 00:05:19.759 --> 00:05:21.749 align:start position:0% And it's really good at real time. So, it<00:05:20.000> is<00:05:20.240> fast,<00:05:20.560> fast,<00:05:20.800> fast.<00:05:21.120> So,<00:05:21.280> you<00:05:21.440> can<00:05:21.600> put 00:05:21.749 --> 00:05:21.759 align:start position:0% it is fast, fast, fast. So, you can put 00:05:21.759 --> 00:05:24.710 align:start position:0% it is fast, fast, fast. So, you can put an<00:05:22.000> LLM<00:05:22.880> in<00:05:23.120> a<00:05:23.280> real-time<00:05:23.680> loop<00:05:24.000> in<00:05:24.160> a<00:05:24.320> way<00:05:24.400> that 00:05:24.710 --> 00:05:24.720 align:start position:0% an LLM in a real-time loop in a way that 00:05:24.720 --> 00:05:27.670 align:start position:0% an LLM in a real-time loop in a way that was<00:05:24.960> not<00:05:25.199> performant<00:05:25.759> enough<00:05:26.720> with<00:05:27.280> these 00:05:27.670 --> 00:05:27.680 align:start position:0% was not performant enough with these 00:05:27.680 --> 00:05:30.070 align:start position:0% was not performant enough with these other<00:05:27.919> models.<00:05:28.720> I<00:05:28.960> do<00:05:29.120> want<00:05:29.280> to<00:05:29.440> explain 00:05:30.070 --> 00:05:30.080 align:start position:0% other models. I do want to explain 00:05:30.080 --> 00:05:32.950 align:start position:0% other models. I do want to explain exactly<00:05:30.720> what<00:05:31.360> Jev<00:05:31.840> outputs.<00:05:32.479> And<00:05:32.639> so,<00:05:32.800> I 00:05:32.950 --> 00:05:32.960 align:start position:0% exactly what Jev outputs. And so, I 00:05:32.960 --> 00:05:34.070 align:start position:0% exactly what Jev outputs. And so, I would<00:05:33.120> highly<00:05:33.440> recommend<00:05:33.680> if<00:05:33.840> you're<00:05:34.000> going 00:05:34.070 --> 00:05:34.080 align:start position:0% would highly recommend if you're going 00:05:34.080 --> 00:05:36.230 align:start position:0% would highly recommend if you're going to<00:05:34.160> use<00:05:34.240> Jev,<00:05:34.720> go<00:05:34.880> to<00:05:34.960> their<00:05:35.199> docs.<00:05:35.840> The<00:05:36.080> two 00:05:36.230 --> 00:05:36.240 align:start position:0% to use Jev, go to their docs. The two 00:05:36.240 --> 00:05:38.150 align:start position:0% to use Jev, go to their docs. The two places<00:05:36.560> that<00:05:36.720> I'm<00:05:36.960> using<00:05:37.120> the<00:05:37.360> most<00:05:37.680> are<00:05:37.919> the 00:05:38.150 --> 00:05:38.160 align:start position:0% places that I'm using the most are the 00:05:38.160 --> 00:05:40.070 align:start position:0% places that I'm using the most are the primitives,<00:05:38.800> so<00:05:39.039> what<00:05:39.199> it<00:05:39.360> returns.<00:05:39.840> And<00:05:39.919> then 00:05:40.070 --> 00:05:40.080 align:start position:0% primitives, so what it returns. And then 00:05:40.080 --> 00:05:42.550 align:start position:0% primitives, so what it returns. And then I<00:05:40.240> use<00:05:40.320> some<00:05:40.479> of<00:05:40.560> the<00:05:40.720> patterns<00:05:41.039> in<00:05:41.280> cookbooks. 00:05:42.550 --> 00:05:42.560 align:start position:0% I use some of the patterns in cookbooks. 00:05:42.560 --> 00:05:44.310 align:start position:0% I use some of the patterns in cookbooks. So<00:05:42.880> what<00:05:43.120> will<00:05:43.280> Jev<00:05:43.600> return<00:05:43.840> to<00:05:43.919> you?<00:05:44.160> It<00:05:44.240> will 00:05:44.310 --> 00:05:44.320 align:start position:0% So what will Jev return to you? It will 00:05:44.320 --> 00:05:45.749 align:start position:0% So what will Jev return to you? It will essentially<00:05:44.720> return<00:05:45.039> one<00:05:45.199> of<00:05:45.360> three<00:05:45.520> things. 00:05:45.749 --> 00:05:45.759 align:start position:0% essentially return one of three things. 00:05:45.759 --> 00:05:47.510 align:start position:0% essentially return one of three things. It<00:05:45.919> will<00:05:46.080> return<00:05:46.320> a<00:05:46.479> choice<00:05:46.800> which<00:05:47.039> means<00:05:47.280> you 00:05:47.510 --> 00:05:47.520 align:start position:0% It will return a choice which means you 00:05:47.520 --> 00:05:50.629 align:start position:0% It will return a choice which means you can<00:05:47.600> give<00:05:47.759> it<00:05:48.400> text,<00:05:49.280> you<00:05:49.440> can<00:05:49.520> give<00:05:49.680> it<00:05:50.080> a<00:05:50.400> list 00:05:50.629 --> 00:05:50.639 align:start position:0% can give it text, you can give it a list 00:05:50.639 --> 00:05:53.909 align:start position:0% can give it text, you can give it a list of<00:05:50.880> choices<00:05:51.360> and<00:05:51.520> it<00:05:51.680> will<00:05:51.919> pick<00:05:52.720> a<00:05:53.039> choice. 00:05:53.909 --> 00:05:53.919 align:start position:0% of choices and it will pick a choice. 00:05:53.919 --> 00:05:57.670 align:start position:0% of choices and it will pick a choice. So,<00:05:54.880> if<00:05:55.280> my<00:05:55.919> question<00:05:56.320> is,<00:05:57.039> what<00:05:57.360> should<00:05:57.520> I 00:05:57.670 --> 00:05:57.680 align:start position:0% So, if my question is, what should I 00:05:57.680 --> 00:06:00.870 align:start position:0% So, if my question is, what should I wear<00:05:57.919> on<00:05:58.080> this<00:05:58.320> date<00:05:59.120> and<00:05:59.360> my<00:05:59.600> choice<00:06:00.000> is<00:06:00.560> a 00:06:00.870 --> 00:06:00.880 align:start position:0% wear on this date and my choice is a 00:06:00.880 --> 00:06:06.150 align:start position:0% wear on this date and my choice is a dress,<00:06:02.160> jeans,<00:06:03.199> workout<00:06:03.680> clothes,<00:06:04.800> ski<00:06:05.199> gear, 00:06:06.150 --> 00:06:06.160 align:start position:0% dress, jeans, workout clothes, ski gear, 00:06:06.160 --> 00:06:09.110 align:start position:0% dress, jeans, workout clothes, ski gear, or<00:06:07.440> nothing, 00:06:09.110 --> 00:06:09.120 align:start position:0% or nothing, 00:06:09.120 --> 00:06:12.550 align:start position:0% or nothing, it'll<00:06:09.520> like<00:06:09.759> maybe<00:06:10.160> pick<00:06:11.120> the<00:06:11.440> dress,<00:06:11.919> right? 00:06:12.550 --> 00:06:12.560 align:start position:0% it'll like maybe pick the dress, right? 00:06:12.560 --> 00:06:17.029 align:start position:0% it'll like maybe pick the dress, right? And<00:06:12.720> so<00:06:12.960> that<00:06:13.280> is<00:06:14.240> choice.<00:06:15.199> If<00:06:15.520> I<00:06:16.160> select 00:06:17.029 --> 00:06:17.039 align:start position:0% And so that is choice. If I select 00:06:17.039 --> 00:06:20.070 align:start position:0% And so that is choice. If I select score,<00:06:18.240> it's<00:06:18.479> going<00:06:18.639> to<00:06:18.800> say<00:06:18.960> like<00:06:19.280> how<00:06:19.520> severe 00:06:20.070 --> 00:06:20.080 align:start position:0% score, it's going to say like how severe 00:06:20.080 --> 00:06:22.950 align:start position:0% score, it's going to say like how severe is<00:06:20.240> this<00:06:20.560> or<00:06:20.800> on<00:06:21.120> a<00:06:21.440> score<00:06:21.680> from<00:06:21.919> one<00:06:22.160> to<00:06:22.639> five, 00:06:22.950 --> 00:06:22.960 align:start position:0% is this or on a score from one to five, 00:06:22.960 --> 00:06:24.950 align:start position:0% is this or on a score from one to five, what<00:06:23.120> it<00:06:23.199> is.<00:06:23.520> This<00:06:23.759> is<00:06:23.919> really<00:06:24.160> good<00:06:24.479> for 00:06:24.950 --> 00:06:24.960 align:start position:0% what it is. This is really good for 00:06:24.960 --> 00:06:27.670 align:start position:0% what it is. This is really good for severity<00:06:25.600> rankings.<00:06:26.639> So<00:06:26.880> say<00:06:27.120> the<00:06:27.360> example 00:06:27.670 --> 00:06:27.680 align:start position:0% severity rankings. So say the example 00:06:27.680 --> 00:06:29.029 align:start position:0% severity rankings. So say the example here<00:06:27.840> is<00:06:27.919> a<00:06:28.080> great<00:06:28.240> one<00:06:28.400> which<00:06:28.560> is<00:06:28.639> like<00:06:28.800> if<00:06:28.960> you 00:06:29.029 --> 00:06:29.039 align:start position:0% here is a great one which is like if you 00:06:29.039 --> 00:06:31.590 align:start position:0% here is a great one which is like if you get<00:06:29.199> a<00:06:29.360> bug,<00:06:30.080> you<00:06:30.319> want<00:06:30.400> to<00:06:30.479> rank<00:06:30.720> it<00:06:31.360> like 00:06:31.590 --> 00:06:31.600 align:start position:0% get a bug, you want to rank it like 00:06:31.600 --> 00:06:35.110 align:start position:0% get a bug, you want to rank it like cosmetic,<00:06:32.479> broken<00:06:32.960> or<00:06:33.199> blocking,<00:06:34.319> Jev<00:06:34.720> will 00:06:35.110 --> 00:06:35.120 align:start position:0% cosmetic, broken or blocking, Jev will 00:06:35.120 --> 00:06:38.469 align:start position:0% cosmetic, broken or blocking, Jev will triage<00:06:35.600> that<00:06:35.840> bug<00:06:36.080> and<00:06:36.319> give<00:06:36.479> it<00:06:36.639> a<00:06:37.199> score.<00:06:38.319> And 00:06:38.469 --> 00:06:38.479 align:start position:0% triage that bug and give it a score. And 00:06:38.479 --> 00:06:40.790 align:start position:0% triage that bug and give it a score. And then<00:06:38.639> finally,<00:06:39.520> there's<00:06:39.919> a<00:06:40.080> new.<00:06:40.479> It's<00:06:40.639> a 00:06:40.790 --> 00:06:40.800 align:start position:0% then finally, there's a new. It's a 00:06:40.800 --> 00:06:43.189 align:start position:0% then finally, there's a new. It's a version<00:06:41.039> of<00:06:41.199> a<00:06:41.440> boolean.<00:06:42.400> It<00:06:42.639> basically<00:06:42.960> tells 00:06:43.189 --> 00:06:43.199 align:start position:0% version of a boolean. It basically tells 00:06:43.199 --> 00:06:45.909 align:start position:0% version of a boolean. It basically tells you<00:06:43.680> what<00:06:44.080> the<00:06:44.720> likelihood<00:06:45.280> that<00:06:45.520> the<00:06:45.680> answer 00:06:45.909 --> 00:06:45.919 align:start position:0% you what the likelihood that the answer 00:06:45.919 --> 00:06:49.029 align:start position:0% you what the likelihood that the answer to<00:06:46.160> a<00:06:46.319> question<00:06:46.800> is<00:06:47.680> yes.<00:06:48.400> So<00:06:48.560> if<00:06:48.720> the<00:06:48.880> answer 00:06:49.029 --> 00:06:49.039 align:start position:0% to a question is yes. So if the answer 00:06:49.039 --> 00:06:51.510 align:start position:0% to a question is yes. So if the answer to<00:06:49.199> a<00:06:49.440> question<00:06:49.600> is<00:06:49.759> yes<00:06:50.000> or<00:06:50.160> no,<00:06:50.800> is<00:06:51.039> Claire<00:06:51.280> a 00:06:51.510 --> 00:06:51.520 align:start position:0% to a question is yes or no, is Claire a 00:06:51.520 --> 00:06:53.270 align:start position:0% to a question is yes or no, is Claire a podcaster?<00:06:52.160> it's<00:06:52.479> going<00:06:52.560> to<00:06:52.639> give<00:06:52.720> you<00:06:52.880> like<00:06:53.039> a 00:06:53.270 --> 00:06:53.280 align:start position:0% podcaster? it's going to give you like a 00:06:53.280 --> 00:06:57.350 align:start position:0% podcaster? it's going to give you like a 99%<00:06:54.560> nule<00:06:55.039> because<00:06:55.360> there's<00:06:55.680> a<00:06:55.840> 99%<00:06:56.560> chance 00:06:57.350 --> 00:06:57.360 align:start position:0% 99% nule because there's a 99% chance 00:06:57.360 --> 00:07:01.350 align:start position:0% 99% nule because there's a 99% chance that<00:06:57.680> I<00:06:57.919> am<00:06:58.240> a<00:06:58.560> podcaster.<00:06:59.440> Okay,<00:06:59.919> so<00:07:00.319> this<00:07:00.639> is 00:07:01.350 --> 00:07:01.360 align:start position:0% that I am a podcaster. Okay, so this is 00:07:01.360 --> 00:07:03.510 align:start position:0% that I am a podcaster. Okay, so this is how<00:07:02.080> you<00:07:02.240> know<00:07:02.319> you<00:07:02.560> would<00:07:02.800> think<00:07:02.960> about<00:07:03.280> the 00:07:03.510 --> 00:07:03.520 align:start position:0% how you know you would think about the 00:07:03.520 --> 00:07:05.430 align:start position:0% how you know you would think about the three<00:07:03.759> things<00:07:04.000> it<00:07:04.240> can<00:07:04.319> return.<00:07:04.720> And<00:07:04.960> again, 00:07:05.430 --> 00:07:05.440 align:start position:0% three things it can return. And again, 00:07:05.440 --> 00:07:06.870 align:start position:0% three things it can return. And again, very<00:07:05.840> simple,<00:07:06.080> but<00:07:06.319> if<00:07:06.479> you've<00:07:06.639> been<00:07:06.720> a 00:07:06.870 --> 00:07:06.880 align:start position:0% very simple, but if you've been a 00:07:06.880 --> 00:07:09.670 align:start position:0% very simple, but if you've been a software<00:07:07.280> engineer,<00:07:08.080> this<00:07:08.319> is<00:07:08.479> like<00:07:08.720> 90%<00:07:09.440> of 00:07:09.670 --> 00:07:09.680 align:start position:0% software engineer, this is like 90% of 00:07:09.680 --> 00:07:11.749 align:start position:0% software engineer, this is like 90% of software<00:07:10.080> engineering<00:07:10.479> is<00:07:10.720> like<00:07:11.120> doing<00:07:11.440> these 00:07:11.749 --> 00:07:11.759 align:start position:0% software engineering is like doing these 00:07:11.759 --> 00:07:14.469 align:start position:0% software engineering is like doing these things,<00:07:12.160> returning<00:07:12.720> a<00:07:12.960> choice,<00:07:13.919> scoring 00:07:14.469 --> 00:07:14.479 align:start position:0% things, returning a choice, scoring 00:07:14.479 --> 00:07:17.510 align:start position:0% things, returning a choice, scoring something,<00:07:15.039> routing,<00:07:16.479> saying<00:07:16.800> yes<00:07:16.960> or<00:07:17.199> no. 00:07:17.510 --> 00:07:17.520 align:start position:0% something, routing, saying yes or no. 00:07:17.520 --> 00:07:21.909 align:start position:0% something, routing, saying yes or no. And<00:07:17.680> so<00:07:17.919> it<00:07:18.160> is<00:07:18.400> just<00:07:18.800> so<00:07:19.440> so<00:07:19.520> so<00:07:20.319> powerful.<00:07:21.599> And 00:07:21.909 --> 00:07:21.919 align:start position:0% And so it is just so so so powerful. And 00:07:21.919 --> 00:07:23.909 align:start position:0% And so it is just so so so powerful. And the<00:07:22.240> number<00:07:22.479> one<00:07:22.720> thing<00:07:23.039> I<00:07:23.360> have<00:07:23.520> been<00:07:23.680> using 00:07:23.909 --> 00:07:23.919 align:start position:0% the number one thing I have been using 00:07:23.919 --> 00:07:27.990 align:start position:0% the number one thing I have been using it<00:07:24.080> for<00:07:24.479> is<00:07:25.039> classification<00:07:26.319> of<00:07:26.560> a<00:07:26.800> vast<00:07:27.199> sets 00:07:27.990 --> 00:07:28.000 align:start position:0% it for is classification of a vast sets 00:07:28.000 --> 00:07:30.550 align:start position:0% it for is classification of a vast sets of<00:07:28.639> unstructured<00:07:29.360> data<00:07:29.919> that<00:07:30.240> would<00:07:30.400> have 00:07:30.550 --> 00:07:30.560 align:start position:0% of unstructured data that would have 00:07:30.560 --> 00:07:33.430 align:start position:0% of unstructured data that would have been<00:07:30.880> annoying<00:07:31.680> to<00:07:32.080> classify<00:07:32.800> but<00:07:32.960> is<00:07:33.199> very 00:07:33.430 --> 00:07:33.440 align:start position:0% been annoying to classify but is very 00:07:33.440 --> 00:07:34.710 align:start position:0% been annoying to classify but is very high<00:07:33.680> value.<00:07:34.000> So<00:07:34.160> I'm<00:07:34.319> going<00:07:34.400> to<00:07:34.479> show<00:07:34.560> you 00:07:34.710 --> 00:07:34.720 align:start position:0% high value. So I'm going to show you 00:07:34.720 --> 00:07:36.309 align:start position:0% high value. So I'm going to show you those<00:07:34.960> use<00:07:35.120> cases<00:07:35.440> and<00:07:35.680> hopefully<00:07:35.919> this<00:07:36.160> will 00:07:36.309 --> 00:07:36.319 align:start position:0% those use cases and hopefully this will 00:07:36.319 --> 00:07:39.589 align:start position:0% those use cases and hopefully this will inspire<00:07:36.880> you<00:07:37.520> about<00:07:37.840> how<00:07:38.080> you<00:07:38.240> can<00:07:38.479> use<00:07:38.960> Jev. 00:07:39.589 --> 00:07:39.599 align:start position:0% inspire you about how you can use Jev. 00:07:39.599 --> 00:07:41.189 align:start position:0% inspire you about how you can use Jev. Okay.<00:07:39.840> So<00:07:40.000> I'm<00:07:40.160> going<00:07:40.240> to<00:07:40.319> pull<00:07:40.479> up<00:07:40.560> Codeex<00:07:41.039> and 00:07:41.189 --> 00:07:41.199 align:start position:0% Okay. So I'm going to pull up Codeex and 00:07:41.199 --> 00:07:44.150 align:start position:0% Okay. So I'm going to pull up Codeex and show<00:07:41.360> you<00:07:41.840> like<00:07:42.160> two<00:07:42.400> or<00:07:42.639> three<00:07:43.039> examples<00:07:43.840> that 00:07:44.150 --> 00:07:44.160 align:start position:0% show you like two or three examples that 00:07:44.160 --> 00:07:46.629 align:start position:0% show you like two or three examples that are<00:07:44.479> super<00:07:44.880> simple<00:07:45.120> to<00:07:45.360> run,<00:07:46.080> incredibly 00:07:46.629 --> 00:07:46.639 align:start position:0% are super simple to run, incredibly 00:07:46.639 --> 00:07:49.430 align:start position:0% are super simple to run, incredibly cheap,<00:07:46.880> and<00:07:47.120> incredibly<00:07:47.599> powerful.<00:07:48.720> This<00:07:49.199> is 00:07:49.430 --> 00:07:49.440 align:start position:0% cheap, and incredibly powerful. This is 00:07:49.440 --> 00:07:52.950 align:start position:0% cheap, and incredibly powerful. This is one<00:07:50.400> CTO's,<00:07:51.120> VPs<00:07:51.520> of<00:07:51.680> product,<00:07:52.319> V,<00:07:52.639> you<00:07:52.800> know, 00:07:52.950 --> 00:07:52.960 align:start position:0% one CTO's, VPs of product, V, you know, 00:07:52.960 --> 00:07:55.110 align:start position:0% one CTO's, VPs of product, V, you know, chief<00:07:53.199> product<00:07:53.520> officers,<00:07:54.000> listen<00:07:54.240> up.<00:07:54.879> This 00:07:55.110 --> 00:07:55.120 align:start position:0% chief product officers, listen up. This 00:07:55.120 --> 00:07:56.710 align:start position:0% chief product officers, listen up. This is<00:07:55.199> the<00:07:55.360> one<00:07:55.520> that<00:07:55.759> three<00:07:56.000> years<00:07:56.160> ago<00:07:56.400> I<00:07:56.560> would 00:07:56.710 --> 00:07:56.720 align:start position:0% is the one that three years ago I would 00:07:56.720 --> 00:08:00.309 align:start position:0% is the one that three years ago I would have<00:07:56.800> paid<00:07:57.199> truly<00:07:57.759> $100,000<00:07:58.479> for.<00:07:59.280> So<00:07:59.599> what<00:07:59.919> I 00:08:00.309 --> 00:08:00.319 align:start position:0% have paid truly $100,000 for. So what I 00:08:00.319 --> 00:08:05.430 align:start position:0% have paid truly $100,000 for. So what I had<00:08:01.039> Jev<00:08:01.520> do<00:08:02.479> is<00:08:02.800> look<00:08:02.960> at<00:08:03.520> thousands<00:08:04.000> of<00:08:04.160> PRs. 00:08:05.430 --> 00:08:05.440 align:start position:0% had Jev do is look at thousands of PRs. 00:08:05.440 --> 00:08:08.070 align:start position:0% had Jev do is look at thousands of PRs. I<00:08:05.680> got<00:08:05.919> PRs.<00:08:06.879> I<00:08:07.120> have<00:08:07.280> connection<00:08:07.599> to<00:08:07.919> to 00:08:08.070 --> 00:08:08.080 align:start position:0% I got PRs. I have connection to to 00:08:08.080 --> 00:08:11.110 align:start position:0% I got PRs. I have connection to to GitHub.<00:08:09.039> Pull<00:08:09.360> every<00:08:09.599> single<00:08:09.840> PR.<00:08:10.800> And<00:08:10.960> then 00:08:11.110 --> 00:08:11.120 align:start position:0% GitHub. Pull every single PR. And then 00:08:11.120 --> 00:08:12.790 align:start position:0% GitHub. Pull every single PR. And then what<00:08:11.360> I<00:08:11.520> had<00:08:11.680> it<00:08:11.840> do,<00:08:12.000> which<00:08:12.240> would<00:08:12.400> have<00:08:12.560> been 00:08:12.790 --> 00:08:12.800 align:start position:0% what I had it do, which would have been 00:08:12.800 --> 00:08:17.189 align:start position:0% what I had it do, which would have been so<00:08:13.199> impractical<00:08:13.919> in<00:08:14.240> the<00:08:14.400> past,<00:08:15.680> is<00:08:15.919> I<00:08:16.160> said 00:08:17.189 --> 00:08:17.199 align:start position:0% so impractical in the past, is I said 00:08:17.199 --> 00:08:21.510 align:start position:0% so impractical in the past, is I said categorize<00:08:18.319> all<00:08:18.479> the<00:08:18.720> PRs.<00:08:19.759> And<00:08:20.000> so<00:08:20.560> use<00:08:20.879> Jev 00:08:21.510 --> 00:08:21.520 align:start position:0% categorize all the PRs. And so use Jev 00:08:21.520 --> 00:08:24.629 align:start position:0% categorize all the PRs. And so use Jev to<00:08:22.479> do<00:08:22.720> pair-wise<00:08:23.520> relations.<00:08:24.160> And<00:08:24.319> so<00:08:24.479> this 00:08:24.629 --> 00:08:24.639 align:start position:0% to do pair-wise relations. And so this 00:08:24.639 --> 00:08:26.070 align:start position:0% to do pair-wise relations. And so this is<00:08:24.720> something<00:08:24.879> that<00:08:25.039> I<00:08:25.199> found<00:08:25.360> Jev<00:08:25.680> is<00:08:25.919> really 00:08:26.070 --> 00:08:26.080 align:start position:0% is something that I found Jev is really 00:08:26.080 --> 00:08:29.270 align:start position:0% is something that I found Jev is really good<00:08:26.240> at<00:08:26.560> is<00:08:26.960> compare<00:08:27.199> like<00:08:27.440> P<00:08:28.000> to<00:08:28.160> PRB<00:08:29.039> and 00:08:29.270 --> 00:08:29.280 align:start position:0% good at is compare like P to PRB and 00:08:29.280 --> 00:08:31.110 align:start position:0% good at is compare like P to PRB and say,<00:08:29.520> are<00:08:29.759> you<00:08:29.919> the<00:08:30.160> same?<00:08:30.639> Are<00:08:30.800> you<00:08:30.960> working 00:08:31.110 --> 00:08:31.120 align:start position:0% say, are you the same? Are you working 00:08:31.120 --> 00:08:33.350 align:start position:0% say, are you the same? Are you working on<00:08:31.280> the<00:08:31.440> same<00:08:31.680> thematic<00:08:32.159> area<00:08:32.479> or<00:08:32.800> not?<00:08:33.039> Again, 00:08:33.350 --> 00:08:33.360 align:start position:0% on the same thematic area or not? Again, 00:08:33.360 --> 00:08:34.630 align:start position:0% on the same thematic area or not? Again, Jev's<00:08:33.760> not<00:08:33.839> going<00:08:33.919> to<00:08:34.000> tell<00:08:34.080> you<00:08:34.240> what<00:08:34.399> the 00:08:34.630 --> 00:08:34.640 align:start position:0% Jev's not going to tell you what the 00:08:34.640 --> 00:08:36.630 align:start position:0% Jev's not going to tell you what the thematic<00:08:35.039> area<00:08:35.360> is<00:08:35.680> unless<00:08:36.000> you<00:08:36.159> give<00:08:36.320> it 00:08:36.630 --> 00:08:36.640 align:start position:0% thematic area is unless you give it 00:08:36.640 --> 00:08:38.709 align:start position:0% thematic area is unless you give it choices.<00:08:37.360> is<00:08:37.760> it's<00:08:37.839> going<00:08:37.919> to<00:08:38.000> say<00:08:38.159> like<00:08:38.479> yes 00:08:38.709 --> 00:08:38.719 align:start position:0% choices. is it's going to say like yes 00:08:38.719 --> 00:08:41.029 align:start position:0% choices. is it's going to say like yes these<00:08:38.959> two<00:08:39.200> are<00:08:39.360> related<00:08:39.680> or<00:08:40.000> no<00:08:40.159> they're<00:08:40.399> not 00:08:41.029 --> 00:08:41.039 align:start position:0% these two are related or no they're not 00:08:41.039 --> 00:08:42.389 align:start position:0% these two are related or no they're not and<00:08:41.200> I've<00:08:41.440> been<00:08:41.519> doing<00:08:41.680> this<00:08:41.839> a<00:08:42.000> lot<00:08:42.080> where<00:08:42.240> I'm 00:08:42.389 --> 00:08:42.399 align:start position:0% and I've been doing this a lot where I'm 00:08:42.399 --> 00:08:43.990 align:start position:0% and I've been doing this a lot where I'm taking<00:08:42.640> vast<00:08:42.959> amounts<00:08:43.279> of<00:08:43.360> data<00:08:43.599> and<00:08:43.839> I'm 00:08:43.990 --> 00:08:44.000 align:start position:0% taking vast amounts of data and I'm 00:08:44.000 --> 00:08:45.910 align:start position:0% taking vast amounts of data and I'm saying<00:08:44.159> like<00:08:44.399> yes<00:08:44.640> related<00:08:45.040> not<00:08:45.279> related<00:08:45.680> yes 00:08:45.910 --> 00:08:45.920 align:start position:0% saying like yes related not related yes 00:08:45.920 --> 00:08:48.230 align:start position:0% saying like yes related not related yes related<00:08:46.480> not<00:08:46.640> related<00:08:47.200> and<00:08:47.440> it's<00:08:47.760> doing 00:08:48.230 --> 00:08:48.240 align:start position:0% related not related and it's doing 00:08:48.240 --> 00:08:50.710 align:start position:0% related not related and it's doing clustering<00:08:49.040> which<00:08:49.360> I<00:08:49.600> find<00:08:49.839> very<00:08:50.160> very<00:08:50.480> useful 00:08:50.710 --> 00:08:50.720 align:start position:0% clustering which I find very very useful 00:08:50.720 --> 00:08:54.389 align:start position:0% clustering which I find very very useful so<00:08:51.120> I<00:08:51.360> create<00:08:51.680> these<00:08:52.000> clusters<00:08:52.720> of<00:08:53.279> data<00:08:53.600> sets 00:08:54.389 --> 00:08:54.399 align:start position:0% so I create these clusters of data sets 00:08:54.399 --> 00:08:57.110 align:start position:0% so I create these clusters of data sets and<00:08:54.640> that's<00:08:54.959> what<00:08:55.600> Jev<00:08:56.000> did<00:08:56.480> and<00:08:56.640> then<00:08:56.800> I<00:08:56.959> used 00:08:57.110 --> 00:08:57.120 align:start position:0% and that's what Jev did and then I used 00:08:57.120 --> 00:08:59.670 align:start position:0% and that's what Jev did and then I used a<00:08:57.440> really<00:08:57.839> cheap<00:08:58.160> model<00:08:58.480> I<00:08:58.640> use<00:08:58.800> Gemini<00:08:59.279> flash 00:08:59.670 --> 00:08:59.680 align:start position:0% a really cheap model I use Gemini flash 00:08:59.680 --> 00:09:02.150 align:start position:0% a really cheap model I use Gemini flash light<00:09:00.399> to<00:09:00.640> then<00:09:00.880> take<00:09:01.040> those<00:09:01.279> clusters<00:09:01.839> and 00:09:02.150 --> 00:09:02.160 align:start position:0% light to then take those clusters and 00:09:02.160 --> 00:09:06.070 align:start position:0% light to then take those clusters and categorize<00:09:02.800> them<00:09:04.160> and<00:09:05.040> I<00:09:05.279> first<00:09:05.519> ran<00:09:05.760> it<00:09:05.920> on 00:09:06.070 --> 00:09:06.080 align:start position:0% categorize them and I first ran it on 00:09:06.080 --> 00:09:07.750 align:start position:0% categorize them and I first ran it on our<00:09:06.240> marketing<00:09:06.560> site<00:09:07.120> where<00:09:07.360> we<00:09:07.519> only<00:09:07.680> have 00:09:07.750 --> 00:09:07.760 align:start position:0% our marketing site where we only have 00:09:07.760 --> 00:09:11.590 align:start position:0% our marketing site where we only have like<00:09:08.000> 112<00:09:08.560> PRs.<00:09:09.279> It<00:09:09.519> cost<00:09:09.760> me<00:09:10.080> 1.1<00:09:10.959> cent.<00:09:11.440> I 00:09:11.590 --> 00:09:11.600 align:start position:0% like 112 PRs. It cost me 1.1 cent. I 00:09:11.600 --> 00:09:13.590 align:start position:0% like 112 PRs. It cost me 1.1 cent. I guess<00:09:11.760> they<00:09:12.000> wouldn't<00:09:12.160> round<00:09:12.399> down<00:09:12.640> that.1 00:09:13.590 --> 00:09:13.600 align:start position:0% guess they wouldn't round down that.1 00:09:13.600 --> 00:09:16.470 align:start position:0% guess they wouldn't round down that.1 penny.<00:09:14.480> And<00:09:14.720> you<00:09:14.959> can<00:09:15.120> see<00:09:15.360> here,<00:09:15.760> it<00:09:16.000> lets<00:09:16.240> me 00:09:16.470 --> 00:09:16.480 align:start position:0% penny. And you can see here, it lets me 00:09:16.480 --> 00:09:18.389 align:start position:0% penny. And you can see here, it lets me see<00:09:16.800> how<00:09:17.040> much<00:09:17.200> my<00:09:17.440> work<00:09:17.600> is<00:09:17.920> related<00:09:18.160> to 00:09:18.389 --> 00:09:18.399 align:start position:0% see how much my work is related to 00:09:18.399 --> 00:09:20.790 align:start position:0% see how much my work is related to maintenance,<00:09:19.040> content,<00:09:19.760> tools,<00:09:20.399> site,<00:09:20.640> and 00:09:20.790 --> 00:09:20.800 align:start position:0% maintenance, content, tools, site, and 00:09:20.800 --> 00:09:23.590 align:start position:0% maintenance, content, tools, site, and conversion<00:09:21.279> services<00:09:21.839> or<00:09:22.080> docs.<00:09:23.279> Super 00:09:23.590 --> 00:09:23.600 align:start position:0% conversion services or docs. Super 00:09:23.600 --> 00:09:26.470 align:start position:0% conversion services or docs. Super useful.<00:09:24.320> Again,<00:09:24.640> it<00:09:24.800> ran<00:09:25.200> very,<00:09:25.600> very,<00:09:26.080> very 00:09:26.470 --> 00:09:26.480 align:start position:0% useful. Again, it ran very, very, very 00:09:26.480 --> 00:09:28.550 align:start position:0% useful. Again, it ran very, very, very fast<00:09:26.880> and<00:09:27.120> very<00:09:27.440> cheap.<00:09:27.839> But<00:09:28.000> then<00:09:28.160> I<00:09:28.320> ran<00:09:28.480> it 00:09:28.550 --> 00:09:28.560 align:start position:0% fast and very cheap. But then I ran it 00:09:28.560 --> 00:09:30.470 align:start position:0% fast and very cheap. But then I ran it on<00:09:28.720> my<00:09:28.800> chat<00:09:29.040> PRD<00:09:29.440> app,<00:09:29.600> which<00:09:29.760> has<00:09:29.920> about 00:09:30.470 --> 00:09:30.480 align:start position:0% on my chat PRD app, which has about 00:09:30.480 --> 00:09:33.190 align:start position:0% on my chat PRD app, which has about 2,000<00:09:31.120> PRs<00:09:31.519> on<00:09:31.680> it<00:09:31.839> to<00:09:32.080> date<00:09:32.320> in<00:09:32.560> this<00:09:32.800> calendar 00:09:33.190 --> 00:09:33.200 align:start position:0% 2,000 PRs on it to date in this calendar 00:09:33.200 --> 00:09:35.990 align:start position:0% 2,000 PRs on it to date in this calendar year.<00:09:33.920> because<00:09:34.320> it<00:09:34.560> has<00:09:34.800> a<00:09:35.040> lot<00:09:35.120> more<00:09:35.360> PRs.<00:09:35.839> It 00:09:35.990 --> 00:09:36.000 align:start position:0% year. because it has a lot more PRs. It 00:09:36.000 --> 00:09:37.910 align:start position:0% year. because it has a lot more PRs. It cost<00:09:36.160> me<00:09:36.320> a<00:09:36.480> lot<00:09:36.640> more<00:09:36.800> money.<00:09:37.120> And<00:09:37.279> by<00:09:37.519> a<00:09:37.760> lot 00:09:37.910 --> 00:09:37.920 align:start position:0% cost me a lot more money. And by a lot 00:09:37.920 --> 00:09:41.430 align:start position:0% cost me a lot more money. And by a lot more<00:09:38.080> money,<00:09:38.399> I<00:09:38.640> mean<00:09:39.600> nine<00:09:40.560> whole<00:09:40.880> cents.<00:09:41.279> It 00:09:41.430 --> 00:09:41.440 align:start position:0% more money, I mean nine whole cents. It 00:09:41.440 --> 00:09:43.509 align:start position:0% more money, I mean nine whole cents. It cost<00:09:41.600> me<00:09:41.839> 9<00:09:42.080> cents<00:09:42.399> to<00:09:42.640> do<00:09:42.800> this.<00:09:43.040> It<00:09:43.279> took 00:09:43.509 --> 00:09:43.519 align:start position:0% cost me 9 cents to do this. It took 00:09:43.519 --> 00:09:46.310 align:start position:0% cost me 9 cents to do this. It took probably<00:09:43.920> about<00:09:44.640> 2<00:09:44.880> minutes.<00:09:45.680> What<00:09:45.920> it<00:09:46.080> did<00:09:46.160> is 00:09:46.310 --> 00:09:46.320 align:start position:0% probably about 2 minutes. What it did is 00:09:46.320 --> 00:09:51.269 align:start position:0% probably about 2 minutes. What it did is it<00:09:46.560> analyzed<00:09:47.200> 1,700<00:09:48.240> PRs.<00:09:49.360> It<00:09:49.600> did<00:09:50.399> 17<00:09:50.800> found 00:09:51.269 --> 00:09:51.279 align:start position:0% it analyzed 1,700 PRs. It did 17 found 00:09:51.279 --> 00:09:52.949 align:start position:0% it analyzed 1,700 PRs. It did 17 found 17,000 00:09:52.949 --> 00:09:52.959 align:start position:0% 17,000 00:09:52.959 --> 00:09:55.269 align:start position:0% 17,000 pairs<00:09:53.519> in<00:09:53.760> those<00:09:53.920> PRs<00:09:54.399> of<00:09:54.560> things<00:09:54.800> that<00:09:55.040> could 00:09:55.269 --> 00:09:55.279 align:start position:0% pairs in those PRs of things that could 00:09:55.279 --> 00:09:58.070 align:start position:0% pairs in those PRs of things that could be<00:09:56.000> matched.<00:09:56.560> And<00:09:56.720> then<00:09:56.959> the<00:09:57.200> themes<00:09:57.760> were 00:09:58.070 --> 00:09:58.080 align:start position:0% be matched. And then the themes were 00:09:58.080 --> 00:10:01.829 align:start position:0% be matched. And then the themes were labeled<00:09:58.640> by<00:09:58.800> Gemini<00:09:59.360> Flash<00:09:59.920> Light.<00:10:01.120> And<00:10:01.440> it 00:10:01.829 --> 00:10:01.839 align:start position:0% labeled by Gemini Flash Light. And it 00:10:01.839 --> 00:10:04.949 align:start position:0% labeled by Gemini Flash Light. And it pulled<00:10:02.959> all<00:10:03.440> of<00:10:03.839> the<00:10:04.080> data<00:10:04.320> out.<00:10:04.640> I<00:10:04.800> mean, 00:10:04.949 --> 00:10:04.959 align:start position:0% pulled all of the data out. I mean, 00:10:04.959 --> 00:10:06.630 align:start position:0% pulled all of the data out. I mean, again, 00:10:06.630 --> 00:10:06.640 align:start position:0% again, 00:10:06.640 --> 00:10:10.070 align:start position:0% again, CTO's,<00:10:07.519> CEOs,<00:10:08.480> like<00:10:09.200> I<00:10:09.440> know<00:10:09.600> you're<00:10:09.839> asked 00:10:10.070 --> 00:10:10.080 align:start position:0% CTO's, CEOs, like I know you're asked 00:10:10.080 --> 00:10:11.990 align:start position:0% CTO's, CEOs, like I know you're asked this<00:10:10.320> by<00:10:10.480> the<00:10:10.720> board<00:10:10.959> and<00:10:11.200> by<00:10:11.360> your<00:10:11.600> team<00:10:11.760> and 00:10:11.990 --> 00:10:12.000 align:start position:0% this by the board and by your team and 00:10:12.000 --> 00:10:13.750 align:start position:0% this by the board and by your team and by<00:10:12.160> your<00:10:12.320> boss<00:10:12.640> all<00:10:12.880> the<00:10:13.040> time,<00:10:13.279> like<00:10:13.519> what 00:10:13.750 --> 00:10:13.760 align:start position:0% by your boss all the time, like what 00:10:13.760 --> 00:10:16.470 align:start position:0% by your boss all the time, like what percentage<00:10:14.160> of<00:10:14.399> work<00:10:14.640> is<00:10:14.880> going<00:10:15.839> to<00:10:16.160> what 00:10:16.470 --> 00:10:16.480 align:start position:0% percentage of work is going to what 00:10:16.480 --> 00:10:17.750 align:start position:0% percentage of work is going to what initiatives?<00:10:17.040> Like,<00:10:17.279> tell<00:10:17.440> me<00:10:17.519> the 00:10:17.750 --> 00:10:17.760 align:start position:0% initiatives? Like, tell me the 00:10:17.760 --> 00:10:19.350 align:start position:0% initiatives? Like, tell me the percentage<00:10:18.079> to<00:10:18.320> tech<00:10:18.480> debt.<00:10:18.800> Tell<00:10:18.880> me<00:10:19.040> the 00:10:19.350 --> 00:10:19.360 align:start position:0% percentage to tech debt. Tell me the 00:10:19.360 --> 00:10:20.710 align:start position:0% percentage to tech debt. Tell me the percentage<00:10:19.680> to<00:10:19.920> this<00:10:20.079> product<00:10:20.240> or<00:10:20.480> that 00:10:20.710 --> 00:10:20.720 align:start position:0% percentage to this product or that 00:10:20.720 --> 00:10:23.110 align:start position:0% percentage to this product or that product.<00:10:21.360> And<00:10:21.600> you<00:10:21.839> can<00:10:22.000> see<00:10:22.160> here<00:10:22.720> it<00:10:22.880> got 00:10:23.110 --> 00:10:23.120 align:start position:0% product. And you can see here it got 00:10:23.120 --> 00:10:25.269 align:start position:0% product. And you can see here it got down.<00:10:23.360> It<00:10:23.519> excluded<00:10:23.839> our<00:10:24.079> docs<00:10:24.560> PRs<00:10:25.040> because 00:10:25.269 --> 00:10:25.279 align:start position:0% down. It excluded our docs PRs because 00:10:25.279 --> 00:10:27.829 align:start position:0% down. It excluded our docs PRs because those<00:10:25.600> are<00:10:25.760> completely<00:10:26.079> separate.<00:10:27.440> almost 00:10:27.829 --> 00:10:27.839 align:start position:0% those are completely separate. almost 00:10:27.839 --> 00:10:30.389 align:start position:0% those are completely separate. almost 30%<00:10:28.720> of<00:10:29.040> the<00:10:29.200> effort<00:10:29.519> the<00:10:29.680> PRs<00:10:30.000> that<00:10:30.160> we<00:10:30.240> do<00:10:30.320> at 00:10:30.389 --> 00:10:30.399 align:start position:0% 30% of the effort the PRs that we do at 00:10:30.399 --> 00:10:32.949 align:start position:0% 30% of the effort the PRs that we do at Chat<00:10:30.720> Pured<00:10:31.440> are<00:10:31.519> around<00:10:31.839> platform<00:10:32.640> security 00:10:32.949 --> 00:10:32.959 align:start position:0% Chat Pured are around platform security 00:10:32.959 --> 00:10:34.630 align:start position:0% Chat Pured are around platform security and<00:10:33.200> infrastructure.<00:10:33.920> on<00:10:34.079> being<00:10:34.240> a<00:10:34.399> good 00:10:34.630 --> 00:10:34.640 align:start position:0% and infrastructure. on being a good 00:10:34.640 --> 00:10:36.389 align:start position:0% and infrastructure. on being a good citizen<00:10:34.959> and<00:10:35.279> investing<00:10:35.680> in<00:10:35.920> security 00:10:36.389 --> 00:10:36.399 align:start position:0% citizen and investing in security 00:10:36.399 --> 00:10:38.790 align:start position:0% citizen and investing in security performance<00:10:37.040> and<00:10:37.279> infrastructure<00:10:38.320> and<00:10:38.560> then 00:10:38.790 --> 00:10:38.800 align:start position:0% performance and infrastructure and then 00:10:38.800 --> 00:10:40.710 align:start position:0% performance and infrastructure and then of<00:10:38.959> course<00:10:39.120> because<00:10:39.360> we're<00:10:39.680> a<00:10:39.839> chatbot<00:10:40.480> a 00:10:40.710 --> 00:10:40.720 align:start position:0% of course because we're a chatbot a 00:10:40.720 --> 00:10:43.670 align:start position:0% of course because we're a chatbot a conversational<00:10:41.360> AI<00:10:42.240> reliability<00:10:43.120> and<00:10:43.360> then 00:10:43.670 --> 00:10:43.680 align:start position:0% conversational AI reliability and then 00:10:43.680 --> 00:10:45.590 align:start position:0% conversational AI reliability and then some<00:10:43.920> product<00:10:44.240> areas<00:10:44.560> that<00:10:44.720> we<00:10:44.880> invest<00:10:45.120> in<00:10:45.360> are 00:10:45.590 --> 00:10:45.600 align:start position:0% some product areas that we invest in are 00:10:45.600 --> 00:10:47.509 align:start position:0% some product areas that we invest in are like<00:10:45.839> data<00:10:46.160> and<00:10:46.399> integrations<00:10:47.120> document 00:10:47.509 --> 00:10:47.519 align:start position:0% like data and integrations document 00:10:47.519 --> 00:10:50.150 align:start position:0% like data and integrations document editing<00:10:47.839> and<00:10:48.079> prototyping<00:10:48.800> which<00:10:49.040> is<00:10:49.120> new<00:10:49.920> and 00:10:50.150 --> 00:10:50.160 align:start position:0% editing and prototyping which is new and 00:10:50.160 --> 00:10:54.710 align:start position:0% editing and prototyping which is new and so<00:10:51.040> this<00:10:51.360> was<00:10:51.760> so<00:10:52.079> cheap<00:10:52.560> so<00:10:52.880> fast<00:10:53.760> it<00:10:54.000> is 00:10:54.710 --> 00:10:54.720 align:start position:0% so this was so cheap so fast it is 00:10:54.720 --> 00:10:56.790 align:start position:0% so this was so cheap so fast it is accurate<00:10:55.200> like<00:10:55.440> I<00:10:55.600> can<00:10:55.760> just<00:10:56.000> tell<00:10:56.160> you<00:10:56.480> yes 00:10:56.790 --> 00:10:56.800 align:start position:0% accurate like I can just tell you yes 00:10:56.800 --> 00:10:58.310 align:start position:0% accurate like I can just tell you yes this<00:10:56.959> is<00:10:57.120> where<00:10:57.279> we're<00:10:57.519> investing<00:10:57.839> our<00:10:58.160> time 00:10:58.310 --> 00:10:58.320 align:start position:0% this is where we're investing our time 00:10:58.320 --> 00:11:00.710 align:start position:0% this is where we're investing our time and<00:10:58.560> you<00:10:58.720> can<00:10:58.800> even<00:10:59.040> see<00:10:59.600> as<00:10:59.839> we<00:11:00.079> invest<00:11:00.480> more 00:11:00.710 --> 00:11:00.720 align:start position:0% and you can even see as we invest more 00:11:00.720 --> 00:11:03.590 align:start position:0% and you can even see as we invest more in<00:11:01.040> different<00:11:01.440> things<00:11:02.800> over<00:11:03.040> the<00:11:03.200> last<00:11:03.360> couple 00:11:03.590 --> 00:11:03.600 align:start position:0% in different things over the last couple 00:11:03.600 --> 00:11:05.990 align:start position:0% in different things over the last couple months<00:11:03.839> it<00:11:04.079> goes<00:11:04.320> up.<00:11:04.720> And<00:11:04.880> so<00:11:05.120> this<00:11:05.360> is<00:11:05.600> just 00:11:05.990 --> 00:11:06.000 align:start position:0% months it goes up. And so this is just 00:11:06.000 --> 00:11:08.630 align:start position:0% months it goes up. And so this is just an<00:11:06.240> example<00:11:06.560> of<00:11:06.800> how<00:11:07.040> powerful,<00:11:07.519> cheap,<00:11:08.399> and 00:11:08.630 --> 00:11:08.640 align:start position:0% an example of how powerful, cheap, and 00:11:08.640 --> 00:11:13.030 align:start position:0% an example of how powerful, cheap, and good<00:11:09.279> Jev<00:11:09.680> can<00:11:09.839> be<00:11:10.240> on<00:11:10.959> large<00:11:11.760> data<00:11:12.079> sets.<00:11:12.880> And 00:11:13.030 --> 00:11:13.040 align:start position:0% good Jev can be on large data sets. And 00:11:13.040 --> 00:11:15.110 align:start position:0% good Jev can be on large data sets. And then<00:11:13.200> I<00:11:13.360> want<00:11:13.440> to<00:11:13.600> give<00:11:13.839> you<00:11:14.079> all<00:11:14.480> one<00:11:14.800> that 00:11:15.110 --> 00:11:15.120 align:start position:0% then I want to give you all one that 00:11:15.120 --> 00:11:17.750 align:start position:0% then I want to give you all one that even<00:11:15.360> if<00:11:15.519> you<00:11:15.680> don't<00:11:15.920> have<00:11:16.079> like<00:11:16.320> a<00:11:16.560> big<00:11:16.800> repo 00:11:17.750 --> 00:11:17.760 align:start position:0% even if you don't have like a big repo 00:11:17.760 --> 00:11:20.310 align:start position:0% even if you don't have like a big repo with<00:11:18.079> PRs<00:11:18.640> everywhere<00:11:19.279> that<00:11:19.519> you<00:11:19.760> can<00:11:19.920> run, 00:11:20.310 --> 00:11:20.320 align:start position:0% with PRs everywhere that you can run, 00:11:20.320 --> 00:11:23.590 align:start position:0% with PRs everywhere that you can run, which<00:11:20.560> is<00:11:20.720> you<00:11:20.959> can<00:11:21.120> run<00:11:21.360> this<00:11:22.240> on<00:11:22.880> your<00:11:23.120> local 00:11:23.590 --> 00:11:23.600 align:start position:0% which is you can run this on your local 00:11:23.600 --> 00:11:27.190 align:start position:0% which is you can run this on your local cloud<00:11:24.000> code<00:11:24.800> and<00:11:25.120> codec<00:11:25.600> sessions.<00:11:26.560> So<00:11:26.880> all<00:11:27.120> of 00:11:27.190 --> 00:11:27.200 align:start position:0% cloud code and codec sessions. So all of 00:11:27.200 --> 00:11:29.110 align:start position:0% cloud code and codec sessions. So all of your<00:11:27.440> cloud<00:11:27.680> code<00:11:27.839> and<00:11:28.000> codec<00:11:28.399> sessions<00:11:28.880> are 00:11:29.110 --> 00:11:29.120 align:start position:0% your cloud code and codec sessions are 00:11:29.120 --> 00:11:31.910 align:start position:0% your cloud code and codec sessions are stored<00:11:29.680> locally.<00:11:30.640> And<00:11:30.880> so<00:11:31.120> you<00:11:31.360> can<00:11:31.519> actually 00:11:31.910 --> 00:11:31.920 align:start position:0% stored locally. And so you can actually 00:11:31.920 --> 00:11:35.670 align:start position:0% stored locally. And so you can actually run<00:11:32.480> this<00:11:32.880> analysis<00:11:33.760> on<00:11:34.800> everything<00:11:35.279> stored 00:11:35.670 --> 00:11:35.680 align:start position:0% run this analysis on everything stored 00:11:35.680 --> 00:11:38.310 align:start position:0% run this analysis on everything stored on<00:11:36.000> your<00:11:36.320> local<00:11:36.800> machine.<00:11:37.519> So<00:11:37.680> I<00:11:37.920> did<00:11:38.079> that 00:11:38.310 --> 00:11:38.320 align:start position:0% on your local machine. So I did that 00:11:38.320 --> 00:11:40.470 align:start position:0% on your local machine. So I did that while<00:11:38.640> Codex<00:11:39.120> kicked<00:11:39.440> off<00:11:39.519> a<00:11:39.760> thread<00:11:40.079> to<00:11:40.320> do 00:11:40.470 --> 00:11:40.480 align:start position:0% while Codex kicked off a thread to do 00:11:40.480 --> 00:11:44.550 align:start position:0% while Codex kicked off a thread to do that.<00:11:41.040> And<00:11:41.519> you<00:11:41.920> can<00:11:42.160> see<00:11:42.880> depending<00:11:43.440> on<00:11:44.320> what 00:11:44.550 --> 00:11:44.560 align:start position:0% that. And you can see depending on what 00:11:44.560 --> 00:11:47.670 align:start position:0% that. And you can see depending on what you<00:11:44.800> count<00:11:45.120> as<00:11:45.519> like<00:11:45.920> effort<00:11:46.959> how<00:11:47.200> much<00:11:47.360> I'm 00:11:47.670 --> 00:11:47.680 align:start position:0% you count as like effort how much I'm 00:11:47.680 --> 00:11:49.750 align:start position:0% you count as like effort how much I'm spending<00:11:48.079> on<00:11:48.399> different<00:11:48.640> things.<00:11:48.959> So<00:11:49.120> I<00:11:49.360> do<00:11:49.519> a 00:11:49.750 --> 00:11:49.760 align:start position:0% spending on different things. So I do a 00:11:49.760 --> 00:11:51.590 align:start position:0% spending on different things. So I do a lot<00:11:49.839> of<00:11:50.160> product<00:11:50.480> engineering.<00:11:50.959> And<00:11:51.120> so<00:11:51.279> for 00:11:51.590 --> 00:11:51.600 align:start position:0% lot of product engineering. And so for 00:11:51.600 --> 00:11:55.110 align:start position:0% lot of product engineering. And so for grouping<00:11:52.000> by<00:11:52.720> user<00:11:53.200> turns<00:11:54.000> in<00:11:54.240> January<00:11:54.720> I<00:11:54.959> was 00:11:55.110 --> 00:11:55.120 align:start position:0% grouping by user turns in January I was 00:11:55.120 --> 00:11:58.389 align:start position:0% grouping by user turns in January I was almost<00:11:55.600> exclusively<00:11:56.640> doing<00:11:57.839> engineering 00:11:58.389 --> 00:11:58.399 align:start position:0% almost exclusively doing engineering 00:11:58.399 --> 00:12:00.870 align:start position:0% almost exclusively doing engineering tasks<00:11:58.720> in<00:11:58.959> cloud<00:11:59.279> code<00:11:59.440> and<00:11:59.600> codecs.<00:12:00.480> And<00:12:00.640> then 00:12:00.870 --> 00:12:00.880 align:start position:0% tasks in cloud code and codecs. And then 00:12:00.880 --> 00:12:03.110 align:start position:0% tasks in cloud code and codecs. And then as<00:12:01.120> you<00:12:01.440> kind<00:12:01.680> of<00:12:01.760> like<00:12:02.079> come<00:12:02.320> into<00:12:02.640> this<00:12:02.880> new 00:12:03.110 --> 00:12:03.120 align:start position:0% as you kind of like come into this new 00:12:03.120 --> 00:12:07.269 align:start position:0% as you kind of like come into this new world<00:12:03.839> now<00:12:04.079> in<00:12:04.320> September<00:12:05.040> less<00:12:05.440> than<00:12:06.320> 40%<00:12:07.120> it 00:12:07.269 --> 00:12:07.279 align:start position:0% world now in September less than 40% it 00:12:07.279 --> 00:12:08.870 align:start position:0% world now in September less than 40% it looks<00:12:07.519> like<00:12:07.680> of<00:12:07.920> my<00:12:08.079> tasks<00:12:08.399> are<00:12:08.639> actually 00:12:08.870 --> 00:12:08.880 align:start position:0% looks like of my tasks are actually 00:12:08.880 --> 00:12:11.430 align:start position:0% looks like of my tasks are actually engineering<00:12:09.440> tasks.<00:12:10.160> I'm<00:12:10.480> doing<00:12:10.639> a<00:12:10.959> lot<00:12:11.120> more 00:12:11.430 --> 00:12:11.440 align:start position:0% engineering tasks. I'm doing a lot more 00:12:11.440 --> 00:12:13.670 align:start position:0% engineering tasks. I'm doing a lot more work<00:12:11.760> with<00:12:12.240> agents<00:12:12.800> which<00:12:13.120> makes<00:12:13.279> a<00:12:13.519> lot<00:12:13.600> of 00:12:13.670 --> 00:12:13.680 align:start position:0% work with agents which makes a lot of 00:12:13.680 --> 00:12:15.590 align:start position:0% work with agents which makes a lot of sense.<00:12:14.320> And<00:12:14.480> then<00:12:14.639> I'm<00:12:14.880> doing<00:12:15.040> a<00:12:15.200> lot<00:12:15.360> more 00:12:15.590 --> 00:12:15.600 align:start position:0% sense. And then I'm doing a lot more 00:12:15.600 --> 00:12:17.269 align:start position:0% sense. And then I'm doing a lot more like<00:12:15.920> publishing<00:12:16.399> media.<00:12:16.800> I'm<00:12:16.959> doing<00:12:17.040> a<00:12:17.200> lot 00:12:17.269 --> 00:12:17.279 align:start position:0% like publishing media. I'm doing a lot 00:12:17.279 --> 00:12:19.829 align:start position:0% like publishing media. I'm doing a lot of<00:12:17.360> our<00:12:17.600> videos<00:12:18.079> through.<00:12:19.200> And<00:12:19.360> then<00:12:19.519> you<00:12:19.680> can 00:12:19.829 --> 00:12:19.839 align:start position:0% of our videos through. And then you can 00:12:19.839 --> 00:12:21.590 align:start position:0% of our videos through. And then you can see<00:12:20.160> I<00:12:20.320> have<00:12:20.399> a<00:12:20.560> new<00:12:20.720> business.<00:12:21.040> So<00:12:21.279> client 00:12:21.590 --> 00:12:21.600 align:start position:0% see I have a new business. So client 00:12:21.600 --> 00:12:23.990 align:start position:0% see I have a new business. So client delivery,<00:12:22.399> family<00:12:22.720> and<00:12:22.959> personal<00:12:23.360> stuff.<00:12:23.839> And 00:12:23.990 --> 00:12:24.000 align:start position:0% delivery, family and personal stuff. And 00:12:24.000 --> 00:12:26.230 align:start position:0% delivery, family and personal stuff. And then<00:12:24.320> where<00:12:24.560> it<00:12:24.800> couldn't<00:12:25.200> categorize<00:12:25.760> or<00:12:26.000> it 00:12:26.230 --> 00:12:26.240 align:start position:0% then where it couldn't categorize or it 00:12:26.240 --> 00:12:28.470 align:start position:0% then where it couldn't categorize or it was<00:12:26.399> unclear.<00:12:27.360> If<00:12:27.519> I<00:12:27.680> take<00:12:27.760> it<00:12:27.920> to<00:12:28.160> session 00:12:28.470 --> 00:12:28.480 align:start position:0% was unclear. If I take it to session 00:12:28.480 --> 00:12:30.389 align:start position:0% was unclear. If I take it to session days,<00:12:29.040> you<00:12:29.200> can<00:12:29.279> see<00:12:29.519> again<00:12:29.839> most<00:12:30.079> of<00:12:30.160> my 00:12:30.389 --> 00:12:30.399 align:start position:0% days, you can see again most of my 00:12:30.399 --> 00:12:33.190 align:start position:0% days, you can see again most of my sessions<00:12:30.880> were<00:12:31.680> coding.<00:12:32.160> And<00:12:32.320> now<00:12:32.560> it's<00:12:32.880> like 00:12:33.190 --> 00:12:33.200 align:start position:0% sessions were coding. And now it's like 00:12:33.200 --> 00:12:36.389 align:start position:0% sessions were coding. And now it's like more<00:12:33.839> equally<00:12:34.320> split<00:12:34.720> across<00:12:35.200> different<00:12:36.160> use 00:12:36.389 --> 00:12:36.399 align:start position:0% more equally split across different use 00:12:36.399 --> 00:12:39.190 align:start position:0% more equally split across different use cases.<00:12:36.959> And<00:12:37.200> so<00:12:37.440> if<00:12:37.680> you<00:12:38.079> think<00:12:38.399> about<00:12:38.720> this, 00:12:39.190 --> 00:12:39.200 align:start position:0% cases. And so if you think about this, 00:12:39.200 --> 00:12:41.430 align:start position:0% cases. And so if you think about this, it<00:12:39.440> is<00:12:39.600> just<00:12:40.000> super<00:12:40.399> useful<00:12:40.720> to<00:12:40.880> do<00:12:41.040> meta 00:12:41.430 --> 00:12:41.440 align:start position:0% it is just super useful to do meta 00:12:41.440 --> 00:12:44.230 align:start position:0% it is just super useful to do meta analysis<00:12:42.000> on<00:12:42.800> all<00:12:42.959> this<00:12:43.279> data<00:12:43.680> that's<00:12:44.000> sitting 00:12:44.230 --> 00:12:44.240 align:start position:0% analysis on all this data that's sitting 00:12:44.240 --> 00:12:47.030 align:start position:0% analysis on all this data that's sitting on<00:12:44.399> your<00:12:44.560> desktop<00:12:45.200> that<00:12:45.519> LMS<00:12:46.160> can<00:12:46.399> totally 00:12:47.030 --> 00:12:47.040 align:start position:0% on your desktop that LMS can totally 00:12:47.040 --> 00:12:49.269 align:start position:0% on your desktop that LMS can totally parse.<00:12:47.519> that<00:12:47.680> will<00:12:47.839> cost<00:12:48.079> you<00:12:48.399> basically<00:12:49.040> no 00:12:49.269 --> 00:12:49.279 align:start position:0% parse. that will cost you basically no 00:12:49.279 --> 00:12:51.670 align:start position:0% parse. that will cost you basically no money<00:12:49.760> and<00:12:50.079> give<00:12:50.240> you<00:12:50.399> a<00:12:50.639> lot<00:12:50.800> of<00:12:51.040> insight<00:12:51.440> that 00:12:51.670 --> 00:12:51.680 align:start position:0% money and give you a lot of insight that 00:12:51.680 --> 00:12:54.230 align:start position:0% money and give you a lot of insight that I<00:12:51.920> think<00:12:52.079> previously<00:12:52.720> would<00:12:53.040> have<00:12:53.200> been<00:12:53.440> hard 00:12:54.230 --> 00:12:54.240 align:start position:0% I think previously would have been hard 00:12:54.240 --> 00:12:57.910 align:start position:0% I think previously would have been hard to<00:12:54.639> get.<00:12:55.519> So<00:12:55.920> these<00:12:56.320> are<00:12:56.639> two<00:12:57.120> use<00:12:57.360> cases<00:12:57.680> I 00:12:57.910 --> 00:12:57.920 align:start position:0% to get. So these are two use cases I 00:12:57.920 --> 00:13:00.069 align:start position:0% to get. So these are two use cases I think<00:12:58.079> everybody<00:12:58.399> who<00:12:58.639> is<00:12:58.880> coding<00:12:59.279> should<00:12:59.440> do. 00:13:00.069 --> 00:13:00.079 align:start position:0% think everybody who is coding should do. 00:13:00.079 --> 00:13:01.430 align:start position:0% think everybody who is coding should do. The<00:13:00.320> third<00:13:00.480> one<00:13:00.639> and<00:13:00.800> I<00:13:01.040> won't<00:13:01.120> show<00:13:01.279> it 00:13:01.430 --> 00:13:01.440 align:start position:0% The third one and I won't show it 00:13:01.440 --> 00:13:02.470 align:start position:0% The third one and I won't show it because<00:13:01.600> it's<00:13:01.760> a<00:13:01.839> lot<00:13:01.920> of<00:13:02.000> my<00:13:02.160> private 00:13:02.470 --> 00:13:02.480 align:start position:0% because it's a lot of my private 00:13:02.480 --> 00:13:04.870 align:start position:0% because it's a lot of my private information<00:13:03.040> is<00:13:03.600> I<00:13:03.760> did<00:13:03.920> run<00:13:04.160> this<00:13:04.320> on<00:13:04.480> my 00:13:04.870 --> 00:13:04.880 align:start position:0% information is I did run this on my 00:13:04.880 --> 00:13:07.509 align:start position:0% information is I did run this on my personal<00:13:05.839> Gmail.<00:13:06.320> So<00:13:06.399> I<00:13:06.639> basically<00:13:06.880> said<00:13:07.120> like 00:13:07.509 --> 00:13:07.519 align:start position:0% personal Gmail. So I basically said like 00:13:07.519 --> 00:13:09.430 align:start position:0% personal Gmail. So I basically said like given<00:13:07.839> a<00:13:08.079> subject<00:13:08.399> line<00:13:08.560> and<00:13:08.800> a<00:13:08.959> snippet 00:13:09.430 --> 00:13:09.440 align:start position:0% given a subject line and a snippet 00:13:09.440 --> 00:13:10.949 align:start position:0% given a subject line and a snippet categorize<00:13:10.000> whether<00:13:10.160> or<00:13:10.320> not<00:13:10.480> I<00:13:10.639> can<00:13:10.720> like 00:13:10.949 --> 00:13:10.959 align:start position:0% categorize whether or not I can like 00:13:10.959 --> 00:13:12.790 align:start position:0% categorize whether or not I can like delete<00:13:11.279> this<00:13:11.519> email<00:13:12.000> like<00:13:12.160> score<00:13:12.480> whether<00:13:12.639> or 00:13:12.790 --> 00:13:12.800 align:start position:0% delete this email like score whether or 00:13:12.800 --> 00:13:14.710 align:start position:0% delete this email like score whether or not<00:13:12.880> I<00:13:13.040> can<00:13:13.200> delete<00:13:13.360> this<00:13:13.600> email.<00:13:14.160> It<00:13:14.399> did<00:13:14.480> it 00:13:14.710 --> 00:13:14.720 align:start position:0% not I can delete this email. It did it 00:13:14.720 --> 00:13:16.710 align:start position:0% not I can delete this email. It did it very<00:13:15.040> fast<00:13:15.360> and<00:13:15.519> then<00:13:15.680> it<00:13:15.839> gave<00:13:16.000> me<00:13:16.160> very<00:13:16.399> clean 00:13:16.710 --> 00:13:16.720 align:start position:0% very fast and then it gave me very clean 00:13:16.720 --> 00:13:19.509 align:start position:0% very fast and then it gave me very clean tags<00:13:17.120> that<00:13:17.440> I<00:13:17.600> could<00:13:17.760> go<00:13:17.920> through<00:13:18.480> and<00:13:19.279> then 00:13:19.509 --> 00:13:19.519 align:start position:0% tags that I could go through and then 00:13:19.519 --> 00:13:21.590 align:start position:0% tags that I could go through and then have<00:13:19.760> another<00:13:20.240> model<00:13:20.720> work<00:13:21.040> through 00:13:21.590 --> 00:13:21.600 align:start position:0% have another model work through 00:13:21.600 --> 00:13:24.069 align:start position:0% have another model work through categorized<00:13:22.399> emails.<00:13:22.880> And<00:13:23.040> so<00:13:23.600> this<00:13:23.760> is<00:13:23.920> where 00:13:24.069 --> 00:13:24.079 align:start position:0% categorized emails. And so this is where 00:13:24.079 --> 00:13:27.670 align:start position:0% categorized emails. And so this is where I<00:13:24.320> would<00:13:24.480> say<00:13:24.639> like<00:13:24.959> Jev<00:13:25.279> alone<00:13:26.399> is<00:13:26.720> okay.<00:13:27.279> Jev 00:13:27.670 --> 00:13:27.680 align:start position:0% I would say like Jev alone is okay. Jev 00:13:27.680 --> 00:13:31.190 align:start position:0% I would say like Jev alone is okay. Jev with<00:13:27.839> an<00:13:28.000> LLM<00:13:28.560> buddy<00:13:28.880> is<00:13:29.200> super<00:13:29.920> powerful.<00:13:30.959> So 00:13:31.190 --> 00:13:31.200 align:start position:0% with an LLM buddy is super powerful. So 00:13:31.200 --> 00:13:32.949 align:start position:0% with an LLM buddy is super powerful. So what<00:13:31.360> I<00:13:31.600> like<00:13:31.680> to<00:13:31.839> do<00:13:32.000> with<00:13:32.160> Jab<00:13:32.480> is<00:13:32.560> I<00:13:32.720> like<00:13:32.800> to 00:13:32.949 --> 00:13:32.959 align:start position:0% what I like to do with Jab is I like to 00:13:32.959 --> 00:13:35.750 align:start position:0% what I like to do with Jab is I like to take<00:13:33.120> a<00:13:33.279> big<00:13:33.440> corpus<00:13:33.839> of<00:13:34.079> information,<00:13:35.440> tag 00:13:35.750 --> 00:13:35.760 align:start position:0% take a big corpus of information, tag 00:13:35.760 --> 00:13:39.110 align:start position:0% take a big corpus of information, tag it,<00:13:36.160> categorize<00:13:36.880> it,<00:13:37.839> cluster<00:13:38.240> it,<00:13:38.720> filter 00:13:39.110 --> 00:13:39.120 align:start position:0% it, categorize it, cluster it, filter 00:13:39.120 --> 00:13:43.030 align:start position:0% it, categorize it, cluster it, filter it,<00:13:40.079> and<00:13:40.320> then<00:13:41.120> apply<00:13:41.600> really<00:13:42.000> precise<00:13:42.560> AI 00:13:43.030 --> 00:13:43.040 align:start position:0% it, and then apply really precise AI 00:13:43.040 --> 00:13:46.230 align:start position:0% it, and then apply really precise AI actions<00:13:43.440> to<00:13:43.760> the<00:13:44.000> right<00:13:44.320> clusters.<00:13:44.959> And<00:13:45.200> so 00:13:46.230 --> 00:13:46.240 align:start position:0% actions to the right clusters. And so 00:13:46.240 --> 00:13:48.629 align:start position:0% actions to the right clusters. And so that<00:13:46.560> could<00:13:46.720> be<00:13:47.279> take<00:13:47.440> your<00:13:47.680> bugs,<00:13:48.320> take<00:13:48.480> your 00:13:48.629 --> 00:13:48.639 align:start position:0% that could be take your bugs, take your 00:13:48.639 --> 00:13:50.629 align:start position:0% that could be take your bugs, take your high<00:13:48.880> severity<00:13:49.360> ones<00:13:49.680> and<00:13:49.920> really<00:13:50.160> triage 00:13:50.629 --> 00:13:50.639 align:start position:0% high severity ones and really triage 00:13:50.639 --> 00:13:52.550 align:start position:0% high severity ones and really triage them<00:13:50.800> deeply.<00:13:51.680> It<00:13:51.839> could<00:13:52.000> be<00:13:52.160> take<00:13:52.320> your 00:13:52.550 --> 00:13:52.560 align:start position:0% them deeply. It could be take your 00:13:52.560 --> 00:13:54.550 align:start position:0% them deeply. It could be take your emails,<00:13:53.200> group<00:13:53.440> them<00:13:53.600> into<00:13:53.920> like<00:13:54.160> you<00:13:54.399> can 00:13:54.550 --> 00:13:54.560 align:start position:0% emails, group them into like you can 00:13:54.560 --> 00:13:56.069 align:start position:0% emails, group them into like you can definitely<00:13:54.880> delete<00:13:55.200> them<00:13:55.279> and<00:13:55.600> ignore<00:13:55.839> them, 00:13:56.069 --> 00:13:56.079 align:start position:0% definitely delete them and ignore them, 00:13:56.079 --> 00:13:57.670 align:start position:0% definitely delete them and ignore them, delete<00:13:56.399> them,<00:13:56.560> and<00:13:56.800> then<00:13:56.959> work<00:13:57.199> your<00:13:57.440> other 00:13:57.670 --> 00:13:57.680 align:start position:0% delete them, and then work your other 00:13:57.680 --> 00:13:59.990 align:start position:0% delete them, and then work your other emails<00:13:58.000> with<00:13:58.160> an<00:13:58.399> agent.<00:13:59.199> It's<00:13:59.519> just<00:13:59.760> all 00:13:59.990 --> 00:14:00.000 align:start position:0% emails with an agent. It's just all 00:14:00.000 --> 00:14:01.829 align:start position:0% emails with an agent. It's just all those<00:14:00.240> things<00:14:00.399> that<00:14:00.560> you<00:14:00.720> can<00:14:00.880> do<00:14:01.199> where<00:14:01.519> a 00:14:01.829 --> 00:14:01.839 align:start position:0% those things that you can do where a 00:14:01.839 --> 00:14:05.189 align:start position:0% those things that you can do where a very<00:14:02.160> fast<00:14:02.639> but<00:14:02.959> accurate<00:14:03.440> filter<00:14:04.240> can<00:14:04.560> be 00:14:05.189 --> 00:14:05.199 align:start position:0% very fast but accurate filter can be 00:14:05.199 --> 00:14:08.150 align:start position:0% very fast but accurate filter can be helpful.<00:14:06.399> So,<00:14:06.720> I<00:14:06.959> think<00:14:07.120> this<00:14:07.360> is<00:14:07.839> so 00:14:08.150 --> 00:14:08.160 align:start position:0% helpful. So, I think this is so 00:14:08.160 --> 00:14:11.430 align:start position:0% helpful. So, I think this is so powerful.<00:14:08.639> I<00:14:08.880> hope<00:14:09.040> it<00:14:09.279> unlocks<00:14:09.920> your<00:14:10.399> minds 00:14:11.430 --> 00:14:11.440 align:start position:0% powerful. I hope it unlocks your minds 00:14:11.440 --> 00:14:13.829 align:start position:0% powerful. I hope it unlocks your minds on<00:14:12.000> what<00:14:12.320> Jev<00:14:12.720> can<00:14:12.880> do.<00:14:13.040> I<00:14:13.279> want<00:14:13.360> to<00:14:13.519> show<00:14:13.680> you 00:14:13.829 --> 00:14:13.839 align:start position:0% on what Jev can do. I want to show you 00:14:13.839 --> 00:14:16.230 align:start position:0% on what Jev can do. I want to show you like<00:14:14.160> the<00:14:14.639> biggest<00:14:15.199> version<00:14:15.519> of<00:14:15.760> this<00:14:16.000> that 00:14:16.230 --> 00:14:16.240 align:start position:0% like the biggest version of this that 00:14:16.240 --> 00:14:18.470 align:start position:0% like the biggest version of this that I've<00:14:16.480> done<00:14:16.720> just<00:14:16.959> to<00:14:17.120> like<00:14:17.279> kind<00:14:17.440> of<00:14:17.519> give<00:14:17.680> you 00:14:18.470 --> 00:14:18.480 align:start position:0% I've done just to like kind of give you 00:14:18.480 --> 00:14:21.110 align:start position:0% I've done just to like kind of give you numbers<00:14:18.800> and<00:14:19.040> ideas<00:14:19.440> of<00:14:19.680> what<00:14:19.839> I'm<00:14:20.079> working<00:14:20.240> on 00:14:21.110 --> 00:14:21.120 align:start position:0% numbers and ideas of what I'm working on 00:14:21.120 --> 00:14:23.030 align:start position:0% numbers and ideas of what I'm working on and<00:14:21.360> then<00:14:21.519> I'll<00:14:21.760> show<00:14:21.920> a<00:14:22.240> couple<00:14:22.399> like<00:14:22.720> fun 00:14:23.030 --> 00:14:23.040 align:start position:0% and then I'll show a couple like fun 00:14:23.040 --> 00:14:26.230 align:start position:0% and then I'll show a couple like fun little<00:14:23.440> apps<00:14:24.240> that<00:14:24.480> you<00:14:24.720> can<00:14:24.880> build<00:14:25.360> with<00:14:25.839> Jev 00:14:26.230 --> 00:14:26.240 align:start position:0% little apps that you can build with Jev 00:14:26.240 --> 00:14:27.910 align:start position:0% little apps that you can build with Jev that<00:14:26.480> I<00:14:26.560> think<00:14:26.720> would<00:14:26.880> have<00:14:27.040> been<00:14:27.199> hard<00:14:27.680> to 00:14:27.910 --> 00:14:27.920 align:start position:0% that I think would have been hard to 00:14:27.920 --> 00:14:32.069 align:start position:0% that I think would have been hard to build<00:14:28.880> before.<00:14:29.760> So<00:14:30.240> the<00:14:30.720> example<00:14:31.360> I<00:14:31.680> want<00:14:31.839> to 00:14:32.069 --> 00:14:32.079 align:start position:0% build before. So the example I want to 00:14:32.079 --> 00:14:34.310 align:start position:0% build before. So the example I want to give<00:14:32.800> is<00:14:33.199> you<00:14:33.360> all<00:14:33.519> have<00:14:33.680> heard<00:14:33.839> me<00:14:34.000> talk<00:14:34.160> about 00:14:34.310 --> 00:14:34.320 align:start position:0% give is you all have heard me talk about 00:14:34.320 --> 00:14:36.710 align:start position:0% give is you all have heard me talk about this<00:14:34.560> product.<00:14:34.959> So<00:14:35.519> chat<00:14:35.839> PD<00:14:36.320> I'm<00:14:36.480> trying<00:14:36.560> to 00:14:36.710 --> 00:14:36.720 align:start position:0% this product. So chat PD I'm trying to 00:14:36.720 --> 00:14:39.910 align:start position:0% this product. So chat PD I'm trying to build<00:14:36.880> like<00:14:37.040> a<00:14:37.279> product<00:14:37.760> insights<00:14:39.120> graph. 00:14:39.910 --> 00:14:39.920 align:start position:0% build like a product insights graph. 00:14:39.920 --> 00:14:41.509 align:start position:0% build like a product insights graph. Basically,<00:14:40.399> I'm<00:14:40.560> like<00:14:40.720> trying<00:14:40.959> to<00:14:41.120> suck<00:14:41.360> in 00:14:41.509 --> 00:14:41.519 align:start position:0% Basically, I'm like trying to suck in 00:14:41.519 --> 00:14:44.069 align:start position:0% Basically, I'm like trying to suck in everybody's<00:14:42.000> data<00:14:42.720> and<00:14:42.959> tell<00:14:43.120> you<00:14:43.600> really 00:14:44.069 --> 00:14:44.079 align:start position:0% everybody's data and tell you really 00:14:44.079 --> 00:14:47.350 align:start position:0% everybody's data and tell you really interesting<00:14:45.120> insights<00:14:45.839> about<00:14:46.079> it.<00:14:46.800> And<00:14:47.040> I 00:14:47.350 --> 00:14:47.360 align:start position:0% interesting insights about it. And I 00:14:47.360 --> 00:14:49.430 align:start position:0% interesting insights about it. And I have<00:14:47.519> used<00:14:47.920> every<00:14:48.240> frontier<00:14:48.800> model<00:14:49.120> there<00:14:49.279> is 00:14:49.430 --> 00:14:49.440 align:start position:0% have used every frontier model there is 00:14:49.440 --> 00:14:50.870 align:start position:0% have used every frontier model there is to<00:14:49.680> try<00:14:49.760> to<00:14:49.920> figure<00:14:50.079> out.<00:14:50.320> And<00:14:50.480> it's<00:14:50.720> just 00:14:50.870 --> 00:14:50.880 align:start position:0% to try to figure out. And it's just 00:14:50.880 --> 00:14:52.150 align:start position:0% to try to figure out. And it's just really<00:14:51.040> hard.<00:14:51.279> There's<00:14:51.519> just<00:14:51.680> too<00:14:51.920> much 00:14:52.150 --> 00:14:52.160 align:start position:0% really hard. There's just too much 00:14:52.160 --> 00:14:56.310 align:start position:0% really hard. There's just too much nuance<00:14:52.800> in<00:14:53.839> all<00:14:54.079> the<00:14:54.320> data<00:14:54.720> to<00:14:54.959> kind<00:14:55.120> of<00:14:55.279> like 00:14:56.310 --> 00:14:56.320 align:start position:0% nuance in all the data to kind of like 00:14:56.320 --> 00:14:57.990 align:start position:0% nuance in all the data to kind of like gro<00:14:56.639> all<00:14:56.880> this,<00:14:57.120> get<00:14:57.360> it<00:14:57.440> in<00:14:57.600> structured 00:14:57.990 --> 00:14:58.000 align:start position:0% gro all this, get it in structured 00:14:58.000 --> 00:14:59.670 align:start position:0% gro all this, get it in structured format,<00:14:58.480> do<00:14:58.639> the<00:14:58.800> right<00:14:58.959> like<00:14:59.199> structured, 00:14:59.670 --> 00:14:59.680 align:start position:0% format, do the right like structured, 00:14:59.680 --> 00:15:01.910 align:start position:0% format, do the right like structured, unstructured.<00:15:00.399> It's<00:15:00.800> super<00:15:01.199> expensive.<00:15:01.680> I've 00:15:01.910 --> 00:15:01.920 align:start position:0% unstructured. It's super expensive. I've 00:15:01.920 --> 00:15:04.389 align:start position:0% unstructured. It's super expensive. I've spent<00:15:02.880> thousands<00:15:03.360> of<00:15:03.519> dollars<00:15:03.760> if<00:15:04.000> not<00:15:04.160> tens 00:15:04.389 --> 00:15:04.399 align:start position:0% spent thousands of dollars if not tens 00:15:04.399 --> 00:15:06.150 align:start position:0% spent thousands of dollars if not tens of<00:15:04.560> thousands<00:15:04.880> of<00:15:05.040> dollars<00:15:05.519> trying<00:15:05.920> to 00:15:06.150 --> 00:15:06.160 align:start position:0% of thousands of dollars trying to 00:15:06.160 --> 00:15:10.069 align:start position:0% of thousands of dollars trying to prototype<00:15:06.800> this.<00:15:07.600> It's<00:15:07.920> just<00:15:08.560> hard.<00:15:09.600> And<00:15:09.839> I 00:15:10.069 --> 00:15:10.079 align:start position:0% prototype this. It's just hard. And I 00:15:10.079 --> 00:15:13.590 align:start position:0% prototype this. It's just hard. And I think<00:15:10.399> I<00:15:10.720> cracked<00:15:11.120> this<00:15:11.360> baby<00:15:12.320> with<00:15:12.639> Jev.<00:15:13.360> I 00:15:13.590 --> 00:15:13.600 align:start position:0% think I cracked this baby with Jev. I 00:15:13.600 --> 00:15:15.189 align:start position:0% think I cracked this baby with Jev. I kind<00:15:13.680> of<00:15:13.760> want<00:15:13.839> to<00:15:14.000> show<00:15:14.240> you<00:15:14.399> what<00:15:14.639> that 00:15:15.189 --> 00:15:15.199 align:start position:0% kind of want to show you what that 00:15:15.199 --> 00:15:16.710 align:start position:0% kind of want to show you what that means, 00:15:16.710 --> 00:15:16.720 align:start position:0% means, 00:15:16.720 --> 00:15:20.310 align:start position:0% means, which<00:15:17.120> is<00:15:18.000> it's<00:15:18.320> not<00:15:18.560> that<00:15:18.800> I<00:15:19.199> like<00:15:19.440> Jev<00:15:20.079> has 00:15:20.310 --> 00:15:20.320 align:start position:0% which is it's not that I like Jev has 00:15:20.320 --> 00:15:23.990 align:start position:0% which is it's not that I like Jev has done<00:15:20.560> it<00:15:20.800> all<00:15:21.760> at<00:15:22.000> all.<00:15:22.800> It<00:15:23.040> is<00:15:23.279> actually<00:15:23.680> I 00:15:23.990 --> 00:15:24.000 align:start position:0% done it all at all. It is actually I 00:15:24.000 --> 00:15:26.470 align:start position:0% done it all at all. It is actually I have<00:15:24.160> figured<00:15:24.399> out<00:15:24.560> where<00:15:25.199> classification, 00:15:26.470 --> 00:15:26.480 align:start position:0% have figured out where classification, 00:15:26.480 --> 00:15:30.069 align:start position:0% have figured out where classification, clustering,<00:15:27.440> and<00:15:27.760> mapping<00:15:29.040> are<00:15:29.360> important 00:15:30.069 --> 00:15:30.079 align:start position:0% clustering, and mapping are important 00:15:30.079 --> 00:15:32.470 align:start position:0% clustering, and mapping are important and<00:15:30.320> I<00:15:30.480> put<00:15:30.720> Jeff<00:15:31.120> there.<00:15:31.839> And<00:15:32.000> then<00:15:32.160> I<00:15:32.320> figure 00:15:32.470 --> 00:15:32.480 align:start position:0% and I put Jeff there. And then I figure 00:15:32.480 --> 00:15:35.110 align:start position:0% and I put Jeff there. And then I figure out<00:15:32.639> where<00:15:32.880> like<00:15:33.040> the<00:15:33.279> big<00:15:33.600> brains<00:15:34.160> like 00:15:35.110 --> 00:15:35.120 align:start position:0% out where like the big brains like 00:15:35.120 --> 00:15:36.629 align:start position:0% out where like the big brains like analysis, 00:15:36.629 --> 00:15:36.639 align:start position:0% analysis, 00:15:36.639 --> 00:15:39.590 align:start position:0% analysis, strategy,<00:15:37.519> insights,<00:15:38.079> extraction,<00:15:39.199> and<00:15:39.360> I 00:15:39.590 --> 00:15:39.600 align:start position:0% strategy, insights, extraction, and I 00:15:39.600 --> 00:15:42.310 align:start position:0% strategy, insights, extraction, and I put<00:15:39.760> like<00:15:40.000> Astra<00:15:41.040> there.<00:15:41.839> And<00:15:42.000> then<00:15:42.160> like 00:15:42.310 --> 00:15:42.320 align:start position:0% put like Astra there. And then like 00:15:42.320 --> 00:15:45.110 align:start position:0% put like Astra there. And then like where<00:15:42.720> generation<00:15:44.000> is<00:15:44.320> important,<00:15:44.720> I<00:15:44.959> use 00:15:45.110 --> 00:15:45.120 align:start position:0% where generation is important, I use 00:15:45.120 --> 00:15:47.990 align:start position:0% where generation is important, I use like<00:15:45.279> a<00:15:45.519> soul<00:15:46.079> or<00:15:46.240> a<00:15:46.399> Luna.<00:15:47.279> And<00:15:47.519> so<00:15:47.680> if<00:15:47.920> you 00:15:47.990 --> 00:15:48.000 align:start position:0% like a soul or a Luna. And so if you 00:15:48.000 --> 00:15:49.350 align:start position:0% like a soul or a Luna. And so if you look<00:15:48.160> at<00:15:48.240> this<00:15:48.399> map<00:15:48.560> and<00:15:48.800> it's<00:15:48.959> like<00:15:49.120> probably 00:15:49.350 --> 00:15:49.360 align:start position:0% look at this map and it's like probably 00:15:49.360 --> 00:15:51.030 align:start position:0% look at this map and it's like probably not<00:15:49.519> that<00:15:49.759> interesting<00:15:50.079> to<00:15:50.240> you<00:15:50.399> all<00:15:50.800> because 00:15:51.030 --> 00:15:51.040 align:start position:0% not that interesting to you all because 00:15:51.040 --> 00:15:54.870 align:start position:0% not that interesting to you all because it's<00:15:51.440> very<00:15:51.839> internal<00:15:52.320> to<00:15:52.800> chat<00:15:53.120> pd<00:15:53.759> but<00:15:54.639> you 00:15:54.870 --> 00:15:54.880 align:start position:0% it's very internal to chat pd but you 00:15:54.880 --> 00:15:58.629 align:start position:0% it's very internal to chat pd but you can<00:15:55.040> see<00:15:55.199> like<00:15:55.519> I<00:15:55.839> extract<00:15:56.399> things,<00:15:57.680> I<00:15:58.079> extract 00:15:58.629 --> 00:15:58.639 align:start position:0% can see like I extract things, I extract 00:15:58.639 --> 00:16:01.110 align:start position:0% can see like I extract things, I extract labels,<00:15:59.440> I<00:15:59.680> then<00:16:00.079> quickly<00:16:00.560> assign<00:16:00.880> everything 00:16:01.110 --> 00:16:01.120 align:start position:0% labels, I then quickly assign everything 00:16:01.120 --> 00:16:04.230 align:start position:0% labels, I then quickly assign everything to<00:16:01.360> those<00:16:01.519> labels<00:16:01.839> with<00:16:02.079> Jev,<00:16:03.199> then<00:16:03.519> I<00:16:03.759> pair 00:16:04.230 --> 00:16:04.240 align:start position:0% to those labels with Jev, then I pair 00:16:04.240 --> 00:16:06.150 align:start position:0% to those labels with Jev, then I pair those<00:16:04.720> clusters<00:16:05.199> in<00:16:05.440> those<00:16:05.600> groups<00:16:05.920> with 00:16:06.150 --> 00:16:06.160 align:start position:0% those clusters in those groups with 00:16:06.160 --> 00:16:07.749 align:start position:0% those clusters in those groups with Astra<00:16:06.560> and<00:16:06.720> I<00:16:06.880> say<00:16:06.959> like<00:16:07.199> what<00:16:07.360> the<00:16:07.440> heck's 00:16:07.749 --> 00:16:07.759 align:start position:0% Astra and I say like what the heck's 00:16:07.759 --> 00:16:10.069 align:start position:0% Astra and I say like what the heck's going<00:16:07.920> on<00:16:08.160> across<00:16:08.560> all<00:16:08.800> of<00:16:08.959> this.<00:16:09.600> And<00:16:09.759> then<00:16:09.920> it 00:16:10.069 --> 00:16:10.079 align:start position:0% going on across all of this. And then it 00:16:10.079 --> 00:16:12.629 align:start position:0% going on across all of this. And then it extracts<00:16:10.639> more<00:16:10.959> insights<00:16:11.600> and<00:16:12.240> all<00:16:12.399> of<00:16:12.480> a 00:16:12.629 --> 00:16:12.639 align:start position:0% extracts more insights and all of a 00:16:12.639 --> 00:16:15.110 align:start position:0% extracts more insights and all of a sudden<00:16:12.800> I<00:16:13.040> have<00:16:13.199> this<00:16:13.440> really<00:16:13.759> cool<00:16:14.639> product. 00:16:15.110 --> 00:16:15.120 align:start position:0% sudden I have this really cool product. 00:16:15.120 --> 00:16:17.030 align:start position:0% sudden I have this really cool product. And<00:16:15.360> just<00:16:15.600> to<00:16:15.759> give<00:16:15.839> you<00:16:16.000> a<00:16:16.160> sense<00:16:16.399> of<00:16:16.560> like<00:16:16.800> the 00:16:17.030 --> 00:16:17.040 align:start position:0% And just to give you a sense of like the 00:16:17.040 --> 00:16:20.069 align:start position:0% And just to give you a sense of like the scope<00:16:17.360> of<00:16:17.600> data<00:16:17.839> here,<00:16:19.040> I'm<00:16:19.360> probably<00:16:19.680> pulling 00:16:20.069 --> 00:16:20.079 align:start position:0% scope of data here, I'm probably pulling 00:16:20.079 --> 00:16:23.990 align:start position:0% scope of data here, I'm probably pulling about<00:16:21.279> a,00and<00:16:22.320> um,<00:16:22.800> 1100<00:16:23.360> individual 00:16:23.990 --> 00:16:24.000 align:start position:0% about a,00and um, 1100 individual 00:16:24.000 --> 00:16:26.629 align:start position:0% about a,00and um, 1100 individual signals<00:16:24.399> into<00:16:24.639> this.<00:16:24.880> So<00:16:25.040> these<00:16:25.279> are<00:16:25.440> PRs, 00:16:26.629 --> 00:16:26.639 align:start position:0% signals into this. So these are PRs, 00:16:26.639 --> 00:16:29.430 align:start position:0% signals into this. So these are PRs, these<00:16:26.959> are<00:16:27.680> support<00:16:28.079> tickets,<00:16:28.880> these<00:16:29.199> are 00:16:29.430 --> 00:16:29.440 align:start position:0% these are support tickets, these are 00:16:29.440 --> 00:16:31.670 align:start position:0% these are support tickets, these are granola<00:16:30.000> conversations, 00:16:31.670 --> 00:16:31.680 align:start position:0% granola conversations, 00:16:31.680 --> 00:16:34.150 align:start position:0% granola conversations, these<00:16:32.079> are<00:16:32.639> um,<00:16:32.800> linear<00:16:33.279> tickets.<00:16:34.000> They're 00:16:34.150 --> 00:16:34.160 align:start position:0% these are um, linear tickets. They're 00:16:34.160 --> 00:16:35.990 align:start position:0% these are um, linear tickets. They're like<00:16:34.399> kind<00:16:34.480> of<00:16:34.639> like<00:16:34.800> all<00:16:34.959> the<00:16:35.199> signals<00:16:35.600> in<00:16:35.839> our 00:16:35.990 --> 00:16:36.000 align:start position:0% like kind of like all the signals in our 00:16:36.000 --> 00:16:37.990 align:start position:0% like kind of like all the signals in our business<00:16:36.399> about<00:16:37.120> what<00:16:37.360> people<00:16:37.519> are<00:16:37.759> worried 00:16:37.990 --> 00:16:38.000 align:start position:0% business about what people are worried 00:16:38.000 --> 00:16:41.829 align:start position:0% business about what people are worried about<00:16:38.240> and<00:16:38.880> what<00:16:39.279> is<00:16:39.519> going<00:16:39.680> on.<00:16:40.639> And<00:16:40.959> then<00:16:41.440> I'm 00:16:41.829 --> 00:16:41.839 align:start position:0% about and what is going on. And then I'm 00:16:41.839 --> 00:16:45.030 align:start position:0% about and what is going on. And then I'm getting<00:16:42.320> now<00:16:42.639> like<00:16:42.880> this<00:16:43.199> gap<00:16:43.680> between<00:16:44.880> what 00:16:45.030 --> 00:16:45.040 align:start position:0% getting now like this gap between what 00:16:45.040 --> 00:16:47.509 align:start position:0% getting now like this gap between what are<00:16:45.279> customers<00:16:45.600> telling<00:16:45.839> us<00:16:46.000> they<00:16:46.240> want<00:16:47.120> and 00:16:47.509 --> 00:16:47.519 align:start position:0% are customers telling us they want and 00:16:47.519 --> 00:16:49.829 align:start position:0% are customers telling us they want and what<00:16:47.759> are<00:16:47.920> we<00:16:48.240> actually<00:16:48.880> working<00:16:49.120> on<00:16:49.440> and<00:16:49.600> I 00:16:49.829 --> 00:16:49.839 align:start position:0% what are we actually working on and I 00:16:49.839 --> 00:16:51.910 align:start position:0% what are we actually working on and I can<00:16:49.920> get<00:16:50.079> those<00:16:50.320> trends<00:16:50.720> over<00:16:51.040> time<00:16:51.440> I<00:16:51.600> can<00:16:51.759> get 00:16:51.910 --> 00:16:51.920 align:start position:0% can get those trends over time I can get 00:16:51.920 --> 00:16:53.749 align:start position:0% can get those trends over time I can get them<00:16:52.240> categorized 00:16:53.749 --> 00:16:53.759 align:start position:0% them categorized 00:16:53.759 --> 00:16:56.069 align:start position:0% them categorized I<00:16:54.000> can<00:16:54.160> get<00:16:54.399> details<00:16:54.959> about<00:16:55.279> them<00:16:55.519> so<00:16:55.839> it's 00:16:56.069 --> 00:16:56.079 align:start position:0% I can get details about them so it's 00:16:56.079 --> 00:17:01.269 align:start position:0% I can get details about them so it's just<00:16:56.399> really<00:16:57.839> super<00:16:59.040> fascinating<00:17:00.079> very 00:17:01.269 --> 00:17:01.279 align:start position:0% just really super fascinating very 00:17:01.279 --> 00:17:04.630 align:start position:0% just really super fascinating very helpful<00:17:01.920> has<00:17:02.240> made<00:17:02.639> this<00:17:03.040> feature<00:17:04.240> I<00:17:04.480> would 00:17:04.630 --> 00:17:04.640 align:start position:0% helpful has made this feature I would 00:17:04.640 --> 00:17:08.549 align:start position:0% helpful has made this feature I would say<00:17:05.679> probably<00:17:06.240> more<00:17:07.199> margin<00:17:07.679> accretive<00:17:08.160> to<00:17:08.400> my 00:17:08.549 --> 00:17:08.559 align:start position:0% say probably more margin accretive to my 00:17:08.559 --> 00:17:10.630 align:start position:0% say probably more margin accretive to my business<00:17:08.880> if<00:17:09.039> you<00:17:09.199> all<00:17:09.360> know<00:17:09.439> what<00:17:09.679> that<00:17:09.839> means 00:17:10.630 --> 00:17:10.640 align:start position:0% business if you all know what that means 00:17:10.640 --> 00:17:12.630 align:start position:0% business if you all know what that means because<00:17:11.199> before<00:17:11.679> I<00:17:11.919> was<00:17:12.079> really<00:17:12.240> like<00:17:12.480> trying 00:17:12.630 --> 00:17:12.640 align:start position:0% because before I was really like trying 00:17:12.640 --> 00:17:15.029 align:start position:0% because before I was really like trying to<00:17:12.799> brute<00:17:13.199> force<00:17:13.520> with<00:17:13.760> these<00:17:14.079> like<00:17:14.319> brainy 00:17:15.029 --> 00:17:15.039 align:start position:0% to brute force with these like brainy 00:17:15.039 --> 00:17:18.150 align:start position:0% to brute force with these like brainy models,<00:17:16.319> what<00:17:16.959> I<00:17:17.199> needed<00:17:17.439> to<00:17:17.600> work<00:17:17.679> on<00:17:17.839> and<00:17:18.079> how 00:17:18.150 --> 00:17:18.160 align:start position:0% models, what I needed to work on and how 00:17:18.160 --> 00:17:19.750 align:start position:0% models, what I needed to work on and how I<00:17:18.319> could<00:17:18.400> do<00:17:18.559> this<00:17:18.720> data.<00:17:18.959> And<00:17:19.120> now<00:17:19.280> I<00:17:19.439> can<00:17:19.600> like 00:17:19.750 --> 00:17:19.760 align:start position:0% I could do this data. And now I can like 00:17:19.760 --> 00:17:21.990 align:start position:0% I could do this data. And now I can like combine<00:17:20.160> these<00:17:20.480> like<00:17:20.720> very<00:17:21.120> cheap<00:17:21.520> decision 00:17:21.990 --> 00:17:22.000 align:start position:0% combine these like very cheap decision 00:17:22.000 --> 00:17:24.309 align:start position:0% combine these like very cheap decision models<00:17:22.319> like<00:17:22.559> Jev<00:17:23.280> with<00:17:23.520> a<00:17:23.679> really<00:17:23.919> brainy 00:17:24.309 --> 00:17:24.319 align:start position:0% models like Jev with a really brainy 00:17:24.319 --> 00:17:27.510 align:start position:0% models like Jev with a really brainy model<00:17:24.640> and<00:17:24.959> get<00:17:25.199> this<00:17:25.520> like<00:17:26.079> interesting 00:17:27.510 --> 00:17:27.520 align:start position:0% model and get this like interesting 00:17:27.520 --> 00:17:30.870 align:start position:0% model and get this like interesting completely<00:17:28.319> hard<00:17:28.720> to<00:17:29.039> generate<00:17:29.919> set<00:17:30.160> of<00:17:30.320> data 00:17:30.870 --> 00:17:30.880 align:start position:0% completely hard to generate set of data 00:17:30.880 --> 00:17:35.669 align:start position:0% completely hard to generate set of data context<00:17:32.080> like<00:17:33.280> auto<00:17:33.600> wiki.<00:17:34.480> It's<00:17:34.720> like<00:17:35.039> really 00:17:35.669 --> 00:17:35.679 align:start position:0% context like auto wiki. It's like really 00:17:35.679 --> 00:17:38.390 align:start position:0% context like auto wiki. It's like really unlocked<00:17:36.240> this<00:17:36.480> product<00:17:37.280> and<00:17:37.679> it<00:17:37.919> has<00:17:38.080> taken 00:17:38.390 --> 00:17:38.400 align:start position:0% unlocked this product and it has taken 00:17:38.400 --> 00:17:40.710 align:start position:0% unlocked this product and it has taken about,00 00:17:40.710 --> 00:17:40.720 align:start position:0% about,00 00:17:40.720 --> 00:17:43.669 align:start position:0% about,00 raw<00:17:41.039> sources<00:17:41.440> of<00:17:41.600> data<00:17:42.400> and<00:17:42.640> done<00:17:42.960> over<00:17:43.200> like 00:17:43.669 --> 00:17:43.679 align:start position:0% raw sources of data and done over like 00:17:43.679 --> 00:17:45.190 align:start position:0% raw sources of data and done over like 200,000 00:17:45.190 --> 00:17:45.200 align:start position:0% 200,000 00:17:45.200 --> 00:17:47.669 align:start position:0% 200,000 classification<00:17:46.000> and<00:17:46.160> pair-wise<00:17:46.720> groupings 00:17:47.669 --> 00:17:47.679 align:start position:0% classification and pair-wise groupings 00:17:47.679 --> 00:17:50.150 align:start position:0% classification and pair-wise groupings and<00:17:48.160> it<00:17:48.400> probably<00:17:48.720> cost<00:17:48.960> me<00:17:49.200> four<00:17:49.440> bucks<00:17:49.919> on 00:17:50.150 --> 00:17:50.160 align:start position:0% and it probably cost me four bucks on 00:17:50.160 --> 00:17:51.510 align:start position:0% and it probably cost me four bucks on the<00:17:50.240> Jeff<00:17:50.559> side.<00:17:50.799> It's<00:17:50.960> cost<00:17:51.120> me<00:17:51.200> a<00:17:51.280> lot<00:17:51.440> more 00:17:51.510 --> 00:17:51.520 align:start position:0% the Jeff side. It's cost me a lot more 00:17:51.520 --> 00:17:54.470 align:start position:0% the Jeff side. It's cost me a lot more on<00:17:51.679> the<00:17:51.760> Astra<00:17:52.160> side.<00:17:53.120> But<00:17:53.360> I<00:17:53.600> just<00:17:53.760> think<00:17:53.919> like 00:17:54.470 --> 00:17:54.480 align:start position:0% on the Astra side. But I just think like 00:17:54.480 --> 00:17:57.830 align:start position:0% on the Astra side. But I just think like thinking<00:17:55.039> through<00:17:55.840> where<00:17:57.120> classification 00:17:57.830 --> 00:17:57.840 align:start position:0% thinking through where classification 00:17:57.840 --> 00:17:59.270 align:start position:0% thinking through where classification like<00:17:58.080> super<00:17:58.320> smart<00:17:58.559> classification 00:17:59.270 --> 00:17:59.280 align:start position:0% like super smart classification 00:17:59.280 --> 00:18:02.630 align:start position:0% like super smart classification clustering<00:18:00.240> decisions<00:18:00.960> could<00:18:01.600> unlock<00:18:02.240> really 00:18:02.630 --> 00:18:02.640 align:start position:0% clustering decisions could unlock really 00:18:02.640 --> 00:18:05.590 align:start position:0% clustering decisions could unlock really complex<00:18:03.760> products<00:18:04.240> and<00:18:04.559> how<00:18:04.880> you<00:18:05.120> might<00:18:05.360> use 00:18:05.590 --> 00:18:05.600 align:start position:0% complex products and how you might use 00:18:05.600 --> 00:18:08.549 align:start position:0% complex products and how you might use as<00:18:05.840> I'm<00:18:06.000> showing<00:18:06.240> here<00:18:06.960> Jev<00:18:07.520> alongside<00:18:08.160> some 00:18:08.549 --> 00:18:08.559 align:start position:0% as I'm showing here Jev alongside some 00:18:08.559 --> 00:18:11.430 align:start position:0% as I'm showing here Jev alongside some smarter<00:18:09.039> models.<00:18:10.480> It's<00:18:10.720> like<00:18:10.960> really<00:18:11.200> blowing 00:18:11.430 --> 00:18:11.440 align:start position:0% smarter models. It's like really blowing 00:18:11.440 --> 00:18:13.350 align:start position:0% smarter models. It's like really blowing my<00:18:11.679> mind<00:18:11.840> right<00:18:12.000> now<00:18:12.160> and<00:18:12.320> I<00:18:12.480> think<00:18:12.559> is<00:18:13.039> it 00:18:13.350 --> 00:18:13.360 align:start position:0% my mind right now and I think is it 00:18:13.360 --> 00:18:14.710 align:start position:0% my mind right now and I think is it should<00:18:13.600> be<00:18:13.760> interesting<00:18:14.080> for<00:18:14.320> those<00:18:14.559> out 00:18:14.710 --> 00:18:14.720 align:start position:0% should be interesting for those out 00:18:14.720 --> 00:18:17.110 align:start position:0% should be interesting for those out there<00:18:15.039> building<00:18:15.600> interesting<00:18:16.240> data 00:18:17.110 --> 00:18:17.120 align:start position:0% there building interesting data 00:18:17.120 --> 00:18:19.350 align:start position:0% there building interesting data products.<00:18:18.000> So,<00:18:18.320> so<00:18:18.480> far<00:18:18.640> I've<00:18:18.880> told<00:18:19.039> you<00:18:19.200> like 00:18:19.350 --> 00:18:19.360 align:start position:0% products. So, so far I've told you like 00:18:19.360 --> 00:18:22.470 align:start position:0% products. So, so far I've told you like what<00:18:19.600> Jeb<00:18:19.919> is,<00:18:20.720> how<00:18:20.960> you<00:18:21.120> can<00:18:21.280> use<00:18:21.440> it<00:18:21.679> on<00:18:22.000> PR 00:18:22.470 --> 00:18:22.480 align:start position:0% what Jeb is, how you can use it on PR 00:18:22.480 --> 00:18:24.549 align:start position:0% what Jeb is, how you can use it on PR review<00:18:22.799> or<00:18:23.120> data<00:18:23.440> analysis,<00:18:24.080> how<00:18:24.240> you<00:18:24.320> can<00:18:24.400> use 00:18:24.549 --> 00:18:24.559 align:start position:0% review or data analysis, how you can use 00:18:24.559 --> 00:18:26.310 align:start position:0% review or data analysis, how you can use it<00:18:24.640> on<00:18:24.880> your<00:18:25.039> local<00:18:25.440> sessions,<00:18:25.919> how<00:18:26.080> you<00:18:26.240> could 00:18:26.310 --> 00:18:26.320 align:start position:0% it on your local sessions, how you could 00:18:26.320 --> 00:18:28.549 align:start position:0% it on your local sessions, how you could even<00:18:26.559> use<00:18:26.720> it<00:18:27.280> on<00:18:27.520> your<00:18:27.760> email,<00:18:28.160> but<00:18:28.320> I'm<00:18:28.480> going 00:18:28.549 --> 00:18:28.559 align:start position:0% even use it on your email, but I'm going 00:18:28.559 --> 00:18:31.750 align:start position:0% even use it on your email, but I'm going to<00:18:28.799> show<00:18:28.960> you<00:18:30.240> two<00:18:30.480> things<00:18:30.720> that<00:18:30.960> I<00:18:31.200> built<00:18:31.520> with 00:18:31.750 --> 00:18:31.760 align:start position:0% to show you two things that I built with 00:18:31.760 --> 00:18:34.630 align:start position:0% to show you two things that I built with it<00:18:32.480> in<00:18:33.200> an<00:18:33.520> afternoon<00:18:34.000> that<00:18:34.240> I<00:18:34.400> think<00:18:34.480> are 00:18:34.630 --> 00:18:34.640 align:start position:0% it in an afternoon that I think are 00:18:34.640 --> 00:18:36.710 align:start position:0% it in an afternoon that I think are really<00:18:34.799> cool.<00:18:35.039> And<00:18:35.280> this<00:18:35.440> is<00:18:35.600> my<00:18:35.840> attempt<00:18:36.480> to 00:18:36.710 --> 00:18:36.720 align:start position:0% really cool. And this is my attempt to 00:18:36.720 --> 00:18:40.150 align:start position:0% really cool. And this is my attempt to like<00:18:37.120> go<00:18:37.440> against<00:18:37.919> the<00:18:39.039> like<00:18:39.360> eyepopping 00:18:40.150 --> 00:18:40.160 align:start position:0% like go against the like eyepopping 00:18:40.160 --> 00:18:43.669 align:start position:0% like go against the like eyepopping demos<00:18:40.559> that<00:18:40.799> you're<00:18:41.039> seeing<00:18:41.440> on<00:18:42.320> X.<00:18:43.280> I<00:18:43.520> think 00:18:43.669 --> 00:18:43.679 align:start position:0% demos that you're seeing on X. I think 00:18:43.679 --> 00:18:45.270 align:start position:0% demos that you're seeing on X. I think people<00:18:43.840> have<00:18:44.160> shown<00:18:44.640> interesting<00:18:45.039> things, 00:18:45.270 --> 00:18:45.280 align:start position:0% people have shown interesting things, 00:18:45.280 --> 00:18:47.990 align:start position:0% people have shown interesting things, but<00:18:45.520> they<00:18:45.760> actually<00:18:46.080> haven't<00:18:46.400> shown<00:18:47.520> how<00:18:47.760> you 00:18:47.990 --> 00:18:48.000 align:start position:0% but they actually haven't shown how you 00:18:48.000 --> 00:18:49.590 align:start position:0% but they actually haven't shown how you have<00:18:48.080> to<00:18:48.240> build<00:18:48.400> it<00:18:48.559> and<00:18:48.799> how<00:18:48.960> it<00:18:49.120> works<00:18:49.280> to<00:18:49.520> get 00:18:49.590 --> 00:18:49.600 align:start position:0% have to build it and how it works to get 00:18:49.600 --> 00:18:51.190 align:start position:0% have to build it and how it works to get that<00:18:49.840> real-time<00:18:50.240> effect.<00:18:50.559> And<00:18:50.720> so,<00:18:50.880> I'm<00:18:51.039> going 00:18:51.190 --> 00:18:51.200 align:start position:0% that real-time effect. And so, I'm going 00:18:51.200 --> 00:18:55.110 align:start position:0% that real-time effect. And so, I'm going to<00:18:51.360> show<00:18:51.520> you<00:18:51.679> these<00:18:52.000> apps<00:18:53.200> live<00:18:54.320> because<00:18:54.799> I 00:18:55.110 --> 00:18:55.120 align:start position:0% to show you these apps live because I 00:18:55.120 --> 00:18:56.390 align:start position:0% to show you these apps live because I think<00:18:55.200> it's<00:18:55.520> important<00:18:55.760> to<00:18:56.000> kind<00:18:56.080> of<00:18:56.160> like 00:18:56.390 --> 00:18:56.400 align:start position:0% think it's important to kind of like 00:18:56.400 --> 00:18:57.750 align:start position:0% think it's important to kind of like understand<00:18:56.720> where<00:18:56.880> the<00:18:57.039> latency<00:18:57.440> comes<00:18:57.600> from 00:18:57.750 --> 00:18:57.760 align:start position:0% understand where the latency comes from 00:18:57.760 --> 00:18:59.350 align:start position:0% understand where the latency comes from and<00:18:57.919> what<00:18:58.080> the<00:18:58.240> real<00:18:58.480> experience<00:18:58.880> is<00:18:59.120> as 00:18:59.350 --> 00:18:59.360 align:start position:0% and what the real experience is as 00:18:59.360 --> 00:19:01.750 align:start position:0% and what the real experience is as opposed<00:18:59.600> to<00:18:59.840> like<00:19:00.080> kind<00:19:00.320> of<00:19:00.400> a<00:19:01.440> 30-se 00:19:01.750 --> 00:19:01.760 align:start position:0% opposed to like kind of a 30-se 00:19:01.760 --> 00:19:04.630 align:start position:0% opposed to like kind of a 30-se secondond<00:19:02.080> demo<00:19:02.480> that<00:19:02.720> goes<00:19:03.039> goes<00:19:03.360> viral.<00:19:04.480> But 00:19:04.630 --> 00:19:04.640 align:start position:0% secondond demo that goes goes viral. But 00:19:04.640 --> 00:19:06.150 align:start position:0% secondond demo that goes goes viral. But I<00:19:04.880> do<00:19:05.039> think<00:19:05.120> it<00:19:05.360> shows<00:19:05.600> some<00:19:05.760> like<00:19:06.000> pretty 00:19:06.150 --> 00:19:06.160 align:start position:0% I do think it shows some like pretty 00:19:06.160 --> 00:19:08.310 align:start position:0% I do think it shows some like pretty cool<00:19:06.320> stuff.<00:19:06.640> So<00:19:06.880> the<00:19:07.200> first<00:19:07.360> one<00:19:07.679> I<00:19:08.000> want<00:19:08.080> to 00:19:08.310 --> 00:19:08.320 align:start position:0% cool stuff. So the first one I want to 00:19:08.320 --> 00:19:10.870 align:start position:0% cool stuff. So the first one I want to do<00:19:09.360> is 00:19:10.870 --> 00:19:10.880 align:start position:0% do is 00:19:10.880 --> 00:19:14.630 align:start position:0% do is how<00:19:11.200> I<00:19:11.520> AI<00:19:12.080> audience<00:19:12.799> signals.<00:19:13.520> So<00:19:14.320> you 00:19:14.630 --> 00:19:14.640 align:start position:0% how I AI audience signals. So you 00:19:14.640 --> 00:19:17.350 align:start position:0% how I AI audience signals. So you wonderful<00:19:15.200> people<00:19:15.919> give<00:19:16.160> us<00:19:16.400> comments<00:19:16.880> on<00:19:17.200> the 00:19:17.350 --> 00:19:17.360 align:start position:0% wonderful people give us comments on the 00:19:17.360 --> 00:19:21.510 align:start position:0% wonderful people give us comments on the how<00:19:17.520> I<00:19:17.760> AI<00:19:18.160> podcast<00:19:19.360> and<00:19:19.919> I<00:19:20.960> go<00:19:21.120> through<00:19:21.280> them. 00:19:21.510 --> 00:19:21.520 align:start position:0% how I AI podcast and I go through them. 00:19:21.520 --> 00:19:23.029 align:start position:0% how I AI podcast and I go through them. I<00:19:21.679> read<00:19:21.840> them<00:19:22.000> every<00:19:22.160> day<00:19:22.320> and<00:19:22.480> I<00:19:22.640> reply<00:19:22.880> to 00:19:23.029 --> 00:19:23.039 align:start position:0% I read them every day and I reply to 00:19:23.039 --> 00:19:25.110 align:start position:0% I read them every day and I reply to them<00:19:23.200> when<00:19:23.360> I<00:19:23.520> can,<00:19:23.919> but<00:19:24.160> I've<00:19:24.400> never<00:19:24.559> done 00:19:25.110 --> 00:19:25.120 align:start position:0% them when I can, but I've never done 00:19:25.120 --> 00:19:28.390 align:start position:0% them when I can, but I've never done analysis<00:19:25.840> on<00:19:26.080> them.<00:19:26.960> And<00:19:27.280> there's<00:19:27.600> about 00:19:28.390 --> 00:19:28.400 align:start position:0% analysis on them. And there's about 00:19:28.400 --> 00:19:31.110 align:start position:0% analysis on them. And there's about 4,500<00:19:29.280> comments<00:19:30.160> and<00:19:30.400> I<00:19:30.559> just<00:19:30.720> wanted<00:19:30.880> to<00:19:30.960> know 00:19:31.110 --> 00:19:31.120 align:start position:0% 4,500 comments and I just wanted to know 00:19:31.120 --> 00:19:32.549 align:start position:0% 4,500 comments and I just wanted to know like<00:19:31.280> are<00:19:31.440> they<00:19:31.600> good,<00:19:31.840> are<00:19:32.000> they<00:19:32.160> bad,<00:19:32.400> are 00:19:32.549 --> 00:19:32.559 align:start position:0% like are they good, are they bad, are 00:19:32.559 --> 00:19:34.310 align:start position:0% like are they good, are they bad, are they<00:19:32.720> happy,<00:19:33.039> are<00:19:33.120> they<00:19:33.280> sad?<00:19:33.600> And<00:19:33.760> I<00:19:34.000> also 00:19:34.310 --> 00:19:34.320 align:start position:0% they happy, are they sad? And I also 00:19:34.320 --> 00:19:36.070 align:start position:0% they happy, are they sad? And I also wanted<00:19:34.559> to<00:19:34.720> know<00:19:34.880> if<00:19:35.120> you<00:19:35.280> all<00:19:35.440> had<00:19:35.679> any 00:19:36.070 --> 00:19:36.080 align:start position:0% wanted to know if you all had any 00:19:36.080 --> 00:19:39.110 align:start position:0% wanted to know if you all had any episode<00:19:36.559> ideas<00:19:37.200> for<00:19:37.520> me<00:19:38.320> where<00:19:38.640> I<00:19:38.960> could 00:19:39.110 --> 00:19:39.120 align:start position:0% episode ideas for me where I could 00:19:39.120 --> 00:19:40.630 align:start position:0% episode ideas for me where I could extract<00:19:39.440> them<00:19:39.600> and<00:19:39.840> come<00:19:39.919> up<00:19:40.080> with<00:19:40.320> episodes 00:19:40.630 --> 00:19:40.640 align:start position:0% extract them and come up with episodes 00:19:40.640 --> 00:19:43.110 align:start position:0% extract them and come up with episodes that<00:19:40.799> I<00:19:40.960> could<00:19:41.120> do<00:19:41.360> like<00:19:41.679> this<00:19:41.919> Jeff<00:19:42.240> one.<00:19:42.880> And 00:19:43.110 --> 00:19:43.120 align:start position:0% that I could do like this Jeff one. And 00:19:43.120 --> 00:19:46.630 align:start position:0% that I could do like this Jeff one. And so<00:19:43.360> I<00:19:43.600> hooked<00:19:43.840> up<00:19:44.080> the<00:19:44.640> YouTube<00:19:45.280> V3<00:19:45.840> API.<00:19:46.480> You 00:19:46.630 --> 00:19:46.640 align:start position:0% so I hooked up the YouTube V3 API. You 00:19:46.640 --> 00:19:48.230 align:start position:0% so I hooked up the YouTube V3 API. You just<00:19:46.799> have<00:19:46.880> to<00:19:46.960> enable<00:19:47.280> it<00:19:47.360> in<00:19:47.600> Google 00:19:48.230 --> 00:19:48.240 align:start position:0% just have to enable it in Google 00:19:48.240 --> 00:19:51.990 align:start position:0% just have to enable it in Google console.<00:19:49.679> And<00:19:49.919> then<00:19:50.240> I<00:19:50.720> said<00:19:51.440> pull<00:19:51.679> all<00:19:51.840> the 00:19:51.990 --> 00:19:52.000 align:start position:0% console. And then I said pull all the 00:19:52.000 --> 00:19:54.310 align:start position:0% console. And then I said pull all the comments<00:19:52.400> and<00:19:52.640> categorize<00:19:53.280> them<00:19:53.840> into 00:19:54.310 --> 00:19:54.320 align:start position:0% comments and categorize them into 00:19:54.320 --> 00:19:57.110 align:start position:0% comments and categorize them into positive,<00:19:54.799> negative<00:19:55.120> or<00:19:55.360> neutral.<00:19:56.720> So<00:19:56.880> that 00:19:57.110 --> 00:19:57.120 align:start position:0% positive, negative or neutral. So that 00:19:57.120 --> 00:19:58.789 align:start position:0% positive, negative or neutral. So that would<00:19:57.280> be<00:19:57.360> a<00:19:57.520> choice,<00:19:57.840> right?<00:19:58.080> Or<00:19:58.240> a<00:19:58.400> score 00:19:58.789 --> 00:19:58.799 align:start position:0% would be a choice, right? Or a score 00:19:58.799 --> 00:20:00.870 align:start position:0% would be a choice, right? Or a score probably.<00:19:59.360> And<00:19:59.520> then<00:19:59.679> I<00:19:59.840> said<00:20:00.000> also<00:20:00.320> use<00:20:00.480> Jev 00:20:00.870 --> 00:20:00.880 align:start position:0% probably. And then I said also use Jev 00:20:00.880 --> 00:20:03.029 align:start position:0% probably. And then I said also use Jev to<00:20:01.200> identify<00:20:01.600> whether<00:20:01.840> or<00:20:01.919> not<00:20:02.160> includes<00:20:02.720> a 00:20:03.029 --> 00:20:03.039 align:start position:0% to identify whether or not includes a 00:20:03.039 --> 00:20:06.230 align:start position:0% to identify whether or not includes a idea<00:20:03.360> for<00:20:03.679> a<00:20:03.919> future<00:20:04.240> episode<00:20:05.120> and<00:20:05.360> then 00:20:06.230 --> 00:20:06.240 align:start position:0% idea for a future episode and then 00:20:06.240 --> 00:20:08.870 align:start position:0% idea for a future episode and then analyze<00:20:07.440> all<00:20:07.679> the<00:20:07.840> data<00:20:08.080> and<00:20:08.400> give<00:20:08.559> me<00:20:08.640> a 00:20:08.870 --> 00:20:08.880 align:start position:0% analyze all the data and give me a 00:20:08.880 --> 00:20:10.950 align:start position:0% analyze all the data and give me a dashboard<00:20:09.280> to<00:20:09.520> look<00:20:09.679> at<00:20:09.760> the<00:20:09.919> data.<00:20:10.640> And<00:20:10.799> so 00:20:10.950 --> 00:20:10.960 align:start position:0% dashboard to look at the data. And so 00:20:10.960 --> 00:20:13.430 align:start position:0% dashboard to look at the data. And so you<00:20:11.200> can<00:20:11.360> see<00:20:11.520> here<00:20:12.240> about<00:20:12.559> half<00:20:12.960> are 00:20:13.430 --> 00:20:13.440 align:start position:0% you can see here about half are 00:20:13.440 --> 00:20:16.710 align:start position:0% you can see here about half are positive.<00:20:14.559> There<00:20:14.720> are<00:20:15.039> 58<00:20:15.840> comments<00:20:16.240> in<00:20:16.480> here 00:20:16.710 --> 00:20:16.720 align:start position:0% positive. There are 58 comments in here 00:20:16.720 --> 00:20:19.510 align:start position:0% positive. There are 58 comments in here with<00:20:17.200> episode<00:20:17.760> ideas<00:20:18.400> and<00:20:18.640> then<00:20:18.799> there's<00:20:19.120> like 00:20:19.510 --> 00:20:19.520 align:start position:0% with episode ideas and then there's like 00:20:19.520 --> 00:20:22.390 align:start position:0% with episode ideas and then there's like quality<00:20:20.400> praise<00:20:20.880> which<00:20:21.120> is<00:20:21.600> praise<00:20:22.000> for<00:20:22.240> our 00:20:22.390 --> 00:20:22.400 align:start position:0% quality praise which is praise for our 00:20:22.400 --> 00:20:24.470 align:start position:0% quality praise which is praise for our production<00:20:22.799> team<00:20:23.360> which<00:20:23.600> is<00:20:23.760> like<00:20:23.919> how<00:20:24.160> nice 00:20:24.470 --> 00:20:24.480 align:start position:0% production team which is like how nice 00:20:24.480 --> 00:20:28.070 align:start position:0% production team which is like how nice the<00:20:24.799> podcast<00:20:25.919> looks.<00:20:26.880> And<00:20:27.200> so<00:20:27.520> then<00:20:27.760> it<00:20:27.919> made 00:20:28.070 --> 00:20:28.080 align:start position:0% the podcast looks. And so then it made 00:20:28.080 --> 00:20:31.110 align:start position:0% the podcast looks. And so then it made me<00:20:28.240> this<00:20:28.480> dashboard<00:20:29.200> which<00:20:29.520> is<00:20:29.840> telling<00:20:30.159> me<00:20:30.960> is 00:20:31.110 --> 00:20:31.120 align:start position:0% me this dashboard which is telling me is 00:20:31.120 --> 00:20:33.669 align:start position:0% me this dashboard which is telling me is it<00:20:31.280> positive,<00:20:31.760> neutral,<00:20:32.240> negative<00:20:32.559> or<00:20:32.880> mixed. 00:20:33.669 --> 00:20:33.679 align:start position:0% it positive, neutral, negative or mixed. 00:20:33.679 --> 00:20:35.669 align:start position:0% it positive, neutral, negative or mixed. And<00:20:33.840> then<00:20:34.000> it<00:20:34.240> gave<00:20:34.400> me<00:20:34.559> an<00:20:34.720> audience<00:20:35.200> request 00:20:35.669 --> 00:20:35.679 align:start position:0% And then it gave me an audience request 00:20:35.679 --> 00:20:38.070 align:start position:0% And then it gave me an audience request board.<00:20:36.080> So<00:20:36.320> you<00:20:36.480> all<00:20:36.720> want<00:20:36.880> like<00:20:37.520> openw<00:20:37.840> weight 00:20:38.070 --> 00:20:38.080 align:start position:0% board. So you all want like openw weight 00:20:38.080 --> 00:20:39.909 align:start position:0% board. So you all want like openw weight models,<00:20:38.640> you<00:20:38.720> want<00:20:38.960> instinct,<00:20:39.600> you<00:20:39.760> really 00:20:39.909 --> 00:20:39.919 align:start position:0% models, you want instinct, you really 00:20:39.919 --> 00:20:41.669 align:start position:0% models, you want instinct, you really want<00:20:40.080> a<00:20:40.240> comparison<00:20:40.480> of<00:20:40.640> Grock<00:20:40.960> and<00:20:41.120> Muse<00:20:41.440> for 00:20:41.669 --> 00:20:41.679 align:start position:0% want a comparison of Grock and Muse for 00:20:41.679 --> 00:20:43.669 align:start position:0% want a comparison of Grock and Muse for personal<00:20:42.000> use.<00:20:42.320> That's<00:20:42.559> coming<00:20:42.799> soon.<00:20:43.520> And 00:20:43.669 --> 00:20:43.679 align:start position:0% personal use. That's coming soon. And 00:20:43.679 --> 00:20:45.990 align:start position:0% personal use. That's coming soon. And then<00:20:43.919> do<00:20:44.080> I<00:20:44.240> use<00:20:44.480> Grock<00:20:44.799> or<00:20:45.039> Brockbot<00:20:45.600> or<00:20:45.840> like 00:20:45.990 --> 00:20:46.000 align:start position:0% then do I use Grock or Brockbot or like 00:20:46.000 --> 00:20:49.110 align:start position:0% then do I use Grock or Brockbot or like what<00:20:46.240> am<00:20:46.320> I<00:20:46.559> using?<00:20:47.760> And<00:20:48.000> then<00:20:48.320> you<00:20:48.640> can<00:20:48.799> also 00:20:49.110 --> 00:20:49.120 align:start position:0% what am I using? And then you can also 00:20:49.120 --> 00:20:53.830 align:start position:0% what am I using? And then you can also see<00:20:50.080> by<00:20:50.799> episode<00:20:51.760> the<00:20:52.080> sentiment<00:20:53.120> which<00:20:53.440> is 00:20:53.830 --> 00:20:53.840 align:start position:0% see by episode the sentiment which is 00:20:53.840 --> 00:20:56.549 align:start position:0% see by episode the sentiment which is Ryan's<00:20:54.400> very<00:20:54.720> popular<00:20:55.440> three-step<00:20:55.919> AI<00:20:56.240> coding 00:20:56.549 --> 00:20:56.559 align:start position:0% Ryan's very popular three-step AI coding 00:20:56.559 --> 00:20:58.950 align:start position:0% Ryan's very popular three-step AI coding workflow.<00:20:57.120> 61% 00:20:58.950 --> 00:20:58.960 align:start position:0% workflow. 61% 00:20:58.960 --> 00:21:00.789 align:start position:0% workflow. 61% positive.<00:20:59.600> We<00:20:59.840> had<00:20:59.919> an<00:21:00.080> awesome<00:21:00.320> cloud<00:21:00.559> code 00:21:00.789 --> 00:21:00.799 align:start position:0% positive. We had an awesome cloud code 00:21:00.799 --> 00:21:03.830 align:start position:0% positive. We had an awesome cloud code for<00:21:00.960> product<00:21:01.280> managers<00:21:02.240> episode.<00:21:02.799> 80% 00:21:03.830 --> 00:21:03.840 align:start position:0% for product managers episode. 80% 00:21:03.840 --> 00:21:05.909 align:start position:0% for product managers episode. 80% positive<00:21:04.880> comments.<00:21:05.360> And<00:21:05.440> then<00:21:05.600> we<00:21:05.760> can 00:21:05.909 --> 00:21:05.919 align:start position:0% positive comments. And then we can 00:21:05.919 --> 00:21:08.070 align:start position:0% positive comments. And then we can actually<00:21:06.240> go<00:21:06.640> through<00:21:07.200> the<00:21:07.600> comments 00:21:08.070 --> 00:21:08.080 align:start position:0% actually go through the comments 00:21:08.080 --> 00:21:13.510 align:start position:0% actually go through the comments themselves.<00:21:09.360> And<00:21:10.480> I<00:21:11.120> using<00:21:11.600> Jev<00:21:12.400> built<00:21:13.039> live 00:21:13.510 --> 00:21:13.520 align:start position:0% themselves. And I using Jev built live 00:21:13.520 --> 00:21:16.149 align:start position:0% themselves. And I using Jev built live search<00:21:14.000> against<00:21:14.320> these<00:21:14.640> comments.<00:21:15.280> So,<00:21:15.600> if<00:21:15.840> I 00:21:16.149 --> 00:21:16.159 align:start position:0% search against these comments. So, if I 00:21:16.159 --> 00:21:19.430 align:start position:0% search against these comments. So, if I wanted<00:21:16.400> to<00:21:16.640> find<00:21:18.000> comments<00:21:18.559> about<00:21:19.120> screen 00:21:19.430 --> 00:21:19.440 align:start position:0% wanted to find comments about screen 00:21:19.440 --> 00:21:23.430 align:start position:0% wanted to find comments about screen share,<00:21:20.720> it<00:21:21.039> would<00:21:21.919> search<00:21:22.320> and<00:21:22.640> find<00:21:23.039> very 00:21:23.430 --> 00:21:23.440 align:start position:0% share, it would search and find very 00:21:23.440 --> 00:21:25.510 align:start position:0% share, it would search and find very quickly<00:21:24.240> something<00:21:24.480> that<00:21:24.799> says<00:21:25.200> screen 00:21:25.510 --> 00:21:25.520 align:start position:0% quickly something that says screen 00:21:25.520 --> 00:21:28.149 align:start position:0% quickly something that says screen share.<00:21:25.919> If<00:21:26.080> I<00:21:26.240> wanted<00:21:26.480> to<00:21:26.720> say,<00:21:27.600> "What<00:21:27.919> are<00:21:28.000> the 00:21:28.149 --> 00:21:28.159 align:start position:0% share. If I wanted to say, "What are the 00:21:28.159 --> 00:21:30.149 align:start position:0% share. If I wanted to say, "What are the comments<00:21:28.400> about<00:21:28.640> slop?"<00:21:29.200> I<00:21:29.440> could<00:21:29.520> do<00:21:29.679> slop 00:21:30.149 --> 00:21:30.159 align:start position:0% comments about slop?" I could do slop 00:21:30.159 --> 00:21:33.029 align:start position:0% comments about slop?" I could do slop and<00:21:30.320> then<00:21:30.480> very<00:21:30.799> quickly<00:21:31.679> it<00:21:31.919> scanned<00:21:32.400> all 00:21:33.029 --> 00:21:33.039 align:start position:0% and then very quickly it scanned all 00:21:33.039 --> 00:21:37.510 align:start position:0% and then very quickly it scanned all 4,400<00:21:34.320> and<00:21:35.679> found<00:21:36.000> all<00:21:36.240> the<00:21:36.400> comments<00:21:37.200> that 00:21:37.510 --> 00:21:37.520 align:start position:0% 4,400 and found all the comments that 00:21:37.520 --> 00:21:41.190 align:start position:0% 4,400 and found all the comments that are<00:21:38.000> related<00:21:38.640> to<00:21:39.280> slop.<00:21:39.760> So,<00:21:40.000> again,<00:21:40.799> this<00:21:40.960> is 00:21:41.190 --> 00:21:41.200 align:start position:0% are related to slop. So, again, this is 00:21:41.200 --> 00:21:43.669 align:start position:0% are related to slop. So, again, this is very<00:21:41.520> performant,<00:21:42.240> very<00:21:42.720> fast.<00:21:43.280> just<00:21:43.520> for 00:21:43.669 --> 00:21:43.679 align:start position:0% very performant, very fast. just for 00:21:43.679 --> 00:21:45.350 align:start position:0% very performant, very fast. just for like<00:21:43.919> behind<00:21:44.080> the<00:21:44.320> scenes,<00:21:44.559> you<00:21:44.799> have<00:21:44.880> to<00:21:45.039> like 00:21:45.350 --> 00:21:45.360 align:start position:0% like behind the scenes, you have to like 00:21:45.360 --> 00:21:47.270 align:start position:0% like behind the scenes, you have to like batch<00:21:45.760> the<00:21:46.000> results<00:21:46.240> and<00:21:46.480> then<00:21:46.799> score<00:21:47.039> them 00:21:47.270 --> 00:21:47.280 align:start position:0% batch the results and then score them 00:21:47.280 --> 00:21:49.430 align:start position:0% batch the results and then score them and<00:21:47.520> then<00:21:47.679> push<00:21:48.000> the<00:21:48.159> high<00:21:48.480> scores<00:21:48.799> up<00:21:49.039> to<00:21:49.360> get 00:21:49.430 --> 00:21:49.440 align:start position:0% and then push the high scores up to get 00:21:49.440 --> 00:21:51.430 align:start position:0% and then push the high scores up to get that<00:21:49.679> kind<00:21:49.840> of<00:21:50.000> performance.<00:21:50.880> So,<00:21:51.039> there<00:21:51.280> is 00:21:51.430 --> 00:21:51.440 align:start position:0% that kind of performance. So, there is 00:21:51.440 --> 00:21:53.029 align:start position:0% that kind of performance. So, there is some<00:21:51.600> architecture<00:21:52.080> here.<00:21:52.400> I<00:21:52.640> don't<00:21:52.799> want<00:21:52.880> to 00:21:53.029 --> 00:21:53.039 align:start position:0% some architecture here. I don't want to 00:21:53.039 --> 00:21:54.870 align:start position:0% some architecture here. I don't want to pretend<00:21:53.280> like<00:21:53.520> Jev<00:21:53.919> you<00:21:54.080> just<00:21:54.159> like<00:21:54.320> slap<00:21:54.640> Jev 00:21:54.870 --> 00:21:54.880 align:start position:0% pretend like Jev you just like slap Jev 00:21:54.880 --> 00:21:57.110 align:start position:0% pretend like Jev you just like slap Jev in<00:21:55.039> the<00:21:55.120> middle<00:21:55.200> and<00:21:55.440> evaluate<00:21:56.000> all<00:21:56.240> 4,400 00:21:57.110 --> 00:21:57.120 align:start position:0% in the middle and evaluate all 4,400 00:21:57.120 --> 00:21:59.830 align:start position:0% in the middle and evaluate all 4,400 that<00:21:57.440> quickly,<00:21:58.400> but<00:21:58.720> you<00:21:58.960> can<00:21:59.039> imagine<00:21:59.600> this 00:21:59.830 --> 00:21:59.840 align:start position:0% that quickly, but you can imagine this 00:21:59.840 --> 00:22:03.590 align:start position:0% that quickly, but you can imagine this is<00:22:00.400> very<00:22:01.760> useful.<00:22:02.480> And<00:22:02.720> so,<00:22:02.960> one,<00:22:03.280> thanks<00:22:03.440> for 00:22:03.590 --> 00:22:03.600 align:start position:0% is very useful. And so, one, thanks for 00:22:03.600 --> 00:22:05.590 align:start position:0% is very useful. And so, one, thanks for all<00:22:03.679> the<00:22:03.840> comments.<00:22:04.159> And<00:22:04.400> two,<00:22:05.200> this<00:22:05.440> was 00:22:05.590 --> 00:22:05.600 align:start position:0% all the comments. And two, this was 00:22:05.600 --> 00:22:07.110 align:start position:0% all the comments. And two, this was really,<00:22:06.000> really<00:22:06.240> cool<00:22:06.400> to<00:22:06.559> build.<00:22:06.799> And<00:22:06.960> then 00:22:07.110 --> 00:22:07.120 align:start position:0% really, really cool to build. And then 00:22:07.120 --> 00:22:09.350 align:start position:0% really, really cool to build. And then finally,<00:22:07.440> I<00:22:07.679> have<00:22:07.760> to<00:22:07.919> give<00:22:08.159> Astra<00:22:08.799> props. 00:22:09.350 --> 00:22:09.360 align:start position:0% finally, I have to give Astra props. 00:22:09.360 --> 00:22:11.750 align:start position:0% finally, I have to give Astra props. Really<00:22:09.600> nailed<00:22:09.840> the<00:22:10.000> Howa<00:22:10.320> AI<00:22:11.200> podcast 00:22:11.750 --> 00:22:11.760 align:start position:0% Really nailed the Howa AI podcast 00:22:11.760 --> 00:22:14.149 align:start position:0% Really nailed the Howa AI podcast styling.<00:22:12.400> So,<00:22:12.720> good<00:22:12.960> job<00:22:13.120> on<00:22:13.360> the<00:22:13.520> front<00:22:13.679> end, 00:22:14.149 --> 00:22:14.159 align:start position:0% styling. So, good job on the front end, 00:22:14.159 --> 00:22:16.470 align:start position:0% styling. So, good job on the front end, but<00:22:14.320> I<00:22:14.480> want<00:22:14.559> to<00:22:14.640> show<00:22:14.880> one<00:22:15.120> last<00:22:15.360> one<00:22:15.600> before<00:22:16.080> I 00:22:16.470 --> 00:22:16.480 align:start position:0% but I want to show one last one before I 00:22:16.480 --> 00:22:18.789 align:start position:0% but I want to show one last one before I get<00:22:16.720> us<00:22:16.880> out<00:22:17.039> of<00:22:17.200> here.<00:22:17.520> And<00:22:17.679> then<00:22:18.159> I<00:22:18.400> said<00:22:18.640> this 00:22:18.789 --> 00:22:18.799 align:start position:0% get us out of here. And then I said this 00:22:18.799 --> 00:22:21.909 align:start position:0% get us out of here. And then I said this was<00:22:18.960> Jev<00:22:19.280> week.<00:22:19.600> So,<00:22:20.320> like<00:22:20.559> and<00:22:20.880> subscribe<00:22:21.520> for 00:22:21.909 --> 00:22:21.919 align:start position:0% was Jev week. So, like and subscribe for 00:22:21.919 --> 00:22:24.470 align:start position:0% was Jev week. So, like and subscribe for a<00:22:22.240> second<00:22:22.640> follow-up<00:22:23.280> Jev<00:22:23.760> episode<00:22:24.080> with<00:22:24.320> one 00:22:24.470 --> 00:22:24.480 align:start position:0% a second follow-up Jev episode with one 00:22:24.480 --> 00:22:25.990 align:start position:0% a second follow-up Jev episode with one of<00:22:24.559> our<00:22:24.640> How<00:22:25.039> Ia<00:22:25.360> guests<00:22:25.679> that's<00:22:25.840> going<00:22:25.919> to 00:22:25.990 --> 00:22:26.000 align:start position:0% of our How Ia guests that's going to 00:22:26.000 --> 00:22:27.830 align:start position:0% of our How Ia guests that's going to come<00:22:26.240> later<00:22:26.480> this<00:22:26.720> week.<00:22:27.280> But<00:22:27.440> I<00:22:27.600> wanted<00:22:27.679> to 00:22:27.830 --> 00:22:27.840 align:start position:0% come later this week. But I wanted to 00:22:27.840 --> 00:22:30.870 align:start position:0% come later this week. But I wanted to show<00:22:28.000> like<00:22:28.240> kind<00:22:28.400> of<00:22:28.400> a<00:22:28.640> fun<00:22:29.120> realtime 00:22:30.870 --> 00:22:30.880 align:start position:0% show like kind of a fun realtime 00:22:30.880 --> 00:22:34.470 align:start position:0% show like kind of a fun realtime use<00:22:31.120> case<00:22:31.520> for<00:22:32.000> Jev.<00:22:32.559> So<00:22:32.799> if<00:22:33.039> you<00:22:33.360> have<00:22:33.600> been 00:22:34.470 --> 00:22:34.480 align:start position:0% use case for Jev. So if you have been 00:22:34.480 --> 00:22:36.710 align:start position:0% use case for Jev. So if you have been seeing<00:22:34.799> any<00:22:35.039> of<00:22:35.120> these<00:22:35.360> like<00:22:35.600> real<00:22:35.919> time<00:22:36.320> app 00:22:36.710 --> 00:22:36.720 align:start position:0% seeing any of these like real time app 00:22:36.720 --> 00:22:39.350 align:start position:0% seeing any of these like real time app applications<00:22:37.520> of<00:22:37.760> Jev<00:22:38.240> like<00:22:38.640> playing<00:22:38.880> a<00:22:39.120> video 00:22:39.350 --> 00:22:39.360 align:start position:0% applications of Jev like playing a video 00:22:39.360 --> 00:22:42.470 align:start position:0% applications of Jev like playing a video game<00:22:40.080> or<00:22:40.400> you<00:22:40.559> know<00:22:40.720> playing<00:22:41.039> playing<00:22:41.440> Tetris 00:22:42.470 --> 00:22:42.480 align:start position:0% game or you know playing playing Tetris 00:22:42.480 --> 00:22:44.230 align:start position:0% game or you know playing playing Tetris doing<00:22:42.799> live<00:22:43.120> search<00:22:43.520> all<00:22:43.679> these<00:22:43.919> things<00:22:44.080> you 00:22:44.230 --> 00:22:44.240 align:start position:0% doing live search all these things you 00:22:44.240 --> 00:22:46.549 align:start position:0% doing live search all these things you can<00:22:44.320> do<00:22:44.480> a<00:22:44.640> lot<00:22:44.720> of<00:22:44.880> real<00:22:45.120> time<00:22:45.440> stuff<00:22:46.240> where 00:22:46.549 --> 00:22:46.559 align:start position:0% can do a lot of real time stuff where 00:22:46.559 --> 00:22:48.310 align:start position:0% can do a lot of real time stuff where making<00:22:46.799> a<00:22:47.039> very<00:22:47.200> quick<00:22:47.520> decision<00:22:48.000> or 00:22:48.310 --> 00:22:48.320 align:start position:0% making a very quick decision or 00:22:48.320 --> 00:22:51.190 align:start position:0% making a very quick decision or returning<00:22:48.799> a<00:22:48.960> set<00:22:49.120> of<00:22:49.280> choices<00:22:50.559> can<00:22:50.799> be<00:22:50.960> very 00:22:51.190 --> 00:22:51.200 align:start position:0% returning a set of choices can be very 00:22:51.200 --> 00:22:54.149 align:start position:0% returning a set of choices can be very powerful.<00:22:51.840> Okay,<00:22:52.240> so<00:22:52.480> I<00:22:52.799> built<00:22:53.120> a<00:22:53.440> real<00:22:53.840> time 00:22:54.149 --> 00:22:54.159 align:start position:0% powerful. Okay, so I built a real time 00:22:54.159 --> 00:22:57.350 align:start position:0% powerful. Okay, so I built a real time app<00:22:54.480> that<00:22:54.799> takes<00:22:55.039> in<00:22:55.360> voice<00:22:56.320> and<00:22:56.640> then<00:22:56.880> uses 00:22:57.350 --> 00:22:57.360 align:start position:0% app that takes in voice and then uses 00:22:57.360 --> 00:23:01.190 align:start position:0% app that takes in voice and then uses Jev<00:22:57.760> to<00:22:58.000> determine<00:22:58.880> what<00:22:59.360> color<00:23:00.480> is<00:23:00.720> like<00:23:00.960> my 00:23:01.190 --> 00:23:01.200 align:start position:0% Jev to determine what color is like my 00:23:01.200 --> 00:23:04.710 align:start position:0% Jev to determine what color is like my emotion<00:23:02.080> and<00:23:02.400> then<00:23:02.640> returns<00:23:03.039> a<00:23:03.280> quote<00:23:04.000> in 00:23:04.710 --> 00:23:04.720 align:start position:0% emotion and then returns a quote in 00:23:04.720 --> 00:23:08.149 align:start position:0% emotion and then returns a quote in reflection<00:23:05.280> of<00:23:05.520> my<00:23:05.760> emotion.<00:23:06.799> It<00:23:07.120> uses 00:23:08.149 --> 00:23:08.159 align:start position:0% reflection of my emotion. It uses 00:23:08.159 --> 00:23:10.950 align:start position:0% reflection of my emotion. It uses OpenAI's<00:23:08.880> real<00:23:09.120> time<00:23:09.360> voice<00:23:09.760> API.<00:23:10.400> It<00:23:10.640> uses 00:23:10.950 --> 00:23:10.960 align:start position:0% OpenAI's real time voice API. It uses 00:23:10.960 --> 00:23:13.270 align:start position:0% OpenAI's real time voice API. It uses Jev<00:23:11.360> and<00:23:11.520> then<00:23:11.600> it<00:23:11.760> uses<00:23:12.080> like<00:23:12.400> API<00:23:12.880> ninja 00:23:13.270 --> 00:23:13.280 align:start position:0% Jev and then it uses like API ninja 00:23:13.280 --> 00:23:15.110 align:start position:0% Jev and then it uses like API ninja quote<00:23:13.679> API.<00:23:14.080> There's<00:23:14.320> apparently<00:23:14.559> an<00:23:14.720> API<00:23:15.039> for 00:23:15.110 --> 00:23:15.120 align:start position:0% quote API. There's apparently an API for 00:23:15.120 --> 00:23:17.190 align:start position:0% quote API. There's apparently an API for quotes.<00:23:15.760> And<00:23:15.919> so<00:23:16.159> we're<00:23:16.320> going<00:23:16.400> to<00:23:16.640> see<00:23:16.960> if 00:23:17.190 --> 00:23:17.200 align:start position:0% quotes. And so we're going to see if 00:23:17.200 --> 00:23:19.909 align:start position:0% quotes. And so we're going to see if this<00:23:17.440> works<00:23:17.760> and<00:23:18.159> how<00:23:18.480> fast<00:23:18.720> it<00:23:18.960> is.<00:23:19.520> I'm 00:23:19.909 --> 00:23:19.919 align:start position:0% this works and how fast it is. I'm 00:23:19.919 --> 00:23:28.149 align:start position:0% this works and how fast it is. I'm feeling<00:23:20.320> so<00:23:20.720> tired<00:23:21.200> today. 00:23:28.149 --> 00:23:28.159 align:start position:0% 00:23:28.159 --> 00:23:32.789 align:start position:0% I'm<00:23:28.480> feeling<00:23:28.720> very<00:23:28.960> happy<00:23:29.280> today. 00:23:32.789 --> 00:23:32.799 align:start position:0% 00:23:32.799 --> 00:23:36.310 align:start position:0% Okay,<00:23:33.039> the<00:23:33.280> quotes.<00:23:33.679> Oh,<00:23:34.000> there<00:23:34.159> we 00:23:36.310 --> 00:23:36.320 align:start position:0% Okay, the quotes. Oh, there we 00:23:36.320 --> 00:23:39.669 align:start position:0% Okay, the quotes. Oh, there we see<00:23:36.640> the<00:23:36.799> quote<00:23:37.120> worked.<00:23:37.760> Okay,<00:23:38.000> hold<00:23:38.240> on.<00:23:39.440> Oh, 00:23:39.669 --> 00:23:39.679 align:start position:0% see the quote worked. Okay, hold on. Oh, 00:23:39.679 --> 00:23:45.510 align:start position:0% see the quote worked. Okay, hold on. Oh, it's<00:23:39.919> excited. 00:23:45.510 --> 00:23:45.520 align:start position:0% 00:23:45.520 --> 00:23:54.310 align:start position:0% I'm<00:23:46.000> in<00:23:46.400> love<00:23:47.760> today. 00:23:54.310 --> 00:23:54.320 align:start position:0% 00:23:54.320 --> 00:24:01.990 align:start position:0% I<00:23:54.799> can't<00:23:55.200> wait<00:23:55.679> for<00:23:56.000> the<00:23:56.159> weekend. 00:24:01.990 --> 00:24:02.000 align:start position:0% 00:24:02.000 --> 00:24:08.310 align:start position:0% Doing<00:24:02.320> this<00:24:02.640> podcast<00:24:03.360> is<00:24:04.000> the<00:24:04.320> best<00:24:04.799> job<00:24:05.200> ever. 00:24:08.310 --> 00:24:08.320 align:start position:0% 00:24:08.320 --> 00:24:10.149 align:start position:0% Look<00:24:08.480> at<00:24:08.640> that.<00:24:08.880> So,<00:24:09.120> we<00:24:09.280> got<00:24:09.520> all<00:24:09.679> these<00:24:10.000> Okay, 00:24:10.149 --> 00:24:10.159 align:start position:0% Look at that. So, we got all these Okay, 00:24:10.159 --> 00:24:11.269 align:start position:0% Look at that. So, we got all these Okay, I'm<00:24:10.320> going<00:24:10.400> to<00:24:10.480> turn<00:24:10.640> it<00:24:10.799> off<00:24:10.880> because<00:24:11.120> it's 00:24:11.269 --> 00:24:11.279 align:start position:0% I'm going to turn it off because it's 00:24:11.279 --> 00:24:13.190 align:start position:0% I'm going to turn it off because it's going<00:24:11.360> to<00:24:11.520> like<00:24:11.679> keep<00:24:11.919> listening<00:24:12.159> to<00:24:12.320> me.<00:24:13.039> Look 00:24:13.190 --> 00:24:13.200 align:start position:0% going to like keep listening to me. Look 00:24:13.200 --> 00:24:14.630 align:start position:0% going to like keep listening to me. Look at<00:24:13.360> all<00:24:13.520> these<00:24:13.840> quotes<00:24:14.159> where<00:24:14.480> like 00:24:14.630 --> 00:24:14.640 align:start position:0% at all these quotes where like 00:24:14.640 --> 00:24:16.230 align:start position:0% at all these quotes where like immediately<00:24:15.120> it<00:24:15.360> picked<00:24:15.600> the<00:24:15.760> right<00:24:15.919> color. 00:24:16.230 --> 00:24:16.240 align:start position:0% immediately it picked the right color. 00:24:16.240 --> 00:24:17.909 align:start position:0% immediately it picked the right color. It<00:24:16.400> picked<00:24:16.640> the<00:24:16.799> right<00:24:16.960> quote.<00:24:17.520> You<00:24:17.760> can<00:24:17.840> tell 00:24:17.909 --> 00:24:17.919 align:start position:0% It picked the right quote. You can tell 00:24:17.919 --> 00:24:19.830 align:start position:0% It picked the right quote. You can tell the<00:24:18.080> quote<00:24:18.400> API<00:24:18.799> has<00:24:18.960> a<00:24:19.120> little<00:24:19.279> latency<00:24:19.679> in 00:24:19.830 --> 00:24:19.840 align:start position:0% the quote API has a little latency in 00:24:19.840 --> 00:24:23.269 align:start position:0% the quote API has a little latency in it,<00:24:20.159> but<00:24:21.360> you<00:24:21.600> can<00:24:21.760> imagine<00:24:22.159> how<00:24:22.400> fun<00:24:22.799> it<00:24:23.120> would 00:24:23.269 --> 00:24:23.279 align:start position:0% it, but you can imagine how fun it would 00:24:23.279 --> 00:24:25.990 align:start position:0% it, but you can imagine how fun it would be<00:24:23.760> to<00:24:24.080> be<00:24:24.240> able<00:24:24.400> to<00:24:24.640> build<00:24:24.880> these<00:24:25.200> real<00:24:25.520> time 00:24:25.990 --> 00:24:26.000 align:start position:0% be to be able to build these real time 00:24:26.000 --> 00:24:28.070 align:start position:0% be to be able to build these real time experiences.<00:24:26.799> And<00:24:26.960> again,<00:24:27.279> when<00:24:27.440> it's<00:24:27.679> like 00:24:28.070 --> 00:24:28.080 align:start position:0% experiences. And again, when it's like 00:24:28.080 --> 00:24:29.669 align:start position:0% experiences. And again, when it's like pick<00:24:28.400> the<00:24:28.559> right<00:24:28.720> color<00:24:28.960> to<00:24:29.200> match<00:24:29.440> the 00:24:29.669 --> 00:24:29.679 align:start position:0% pick the right color to match the 00:24:29.679 --> 00:24:31.990 align:start position:0% pick the right color to match the sentence,<00:24:30.559> it<00:24:30.880> can<00:24:31.039> do<00:24:31.200> that<00:24:31.360> really<00:24:31.679> well. 00:24:31.990 --> 00:24:32.000 align:start position:0% sentence, it can do that really well. 00:24:32.000 --> 00:24:33.669 align:start position:0% sentence, it can do that really well. Just<00:24:32.240> for<00:24:32.400> you<00:24:32.559> all<00:24:32.720> to<00:24:32.960> know<00:24:33.120> kind<00:24:33.279> of<00:24:33.360> how<00:24:33.520> it 00:24:33.669 --> 00:24:33.679 align:start position:0% Just for you all to know kind of how it 00:24:33.679 --> 00:24:36.390 align:start position:0% Just for you all to know kind of how it works,<00:24:34.240> I<00:24:34.480> gave<00:24:34.640> it<00:24:34.799> a<00:24:35.039> list<00:24:35.200> of<00:24:35.520> hex<00:24:35.919> values. 00:24:36.390 --> 00:24:36.400 align:start position:0% works, I gave it a list of hex values. 00:24:36.400 --> 00:24:39.029 align:start position:0% works, I gave it a list of hex values. So,<00:24:36.559> a<00:24:36.720> list<00:24:36.880> of<00:24:37.120> colors.<00:24:37.840> Every<00:24:38.240> sentence<00:24:38.720> or 00:24:39.029 --> 00:24:39.039 align:start position:0% So, a list of colors. Every sentence or 00:24:39.039 --> 00:24:40.549 align:start position:0% So, a list of colors. Every sentence or like<00:24:39.279> phrase<00:24:39.760> it<00:24:40.000> ingests<00:24:40.320> from<00:24:40.480> the 00:24:40.549 --> 00:24:40.559 align:start position:0% like phrase it ingests from the 00:24:40.559 --> 00:24:43.510 align:start position:0% like phrase it ingests from the real-time<00:24:40.960> API,<00:24:41.760> it<00:24:42.000> asks<00:24:42.240> what<00:24:42.480> color<00:24:43.120> or<00:24:43.360> it 00:24:43.510 --> 00:24:43.520 align:start position:0% real-time API, it asks what color or it 00:24:43.520 --> 00:24:45.029 align:start position:0% real-time API, it asks what color or it scores<00:24:43.840> the<00:24:44.000> colors.<00:24:44.400> It<00:24:44.559> gives<00:24:44.720> the<00:24:44.880> top 00:24:45.029 --> 00:24:45.039 align:start position:0% scores the colors. It gives the top 00:24:45.039 --> 00:24:47.510 align:start position:0% scores the colors. It gives the top ranking<00:24:45.360> score<00:24:45.679> color<00:24:46.000> and<00:24:46.320> then<00:24:46.880> it<00:24:47.200> also 00:24:47.510 --> 00:24:47.520 align:start position:0% ranking score color and then it also 00:24:47.520 --> 00:24:50.149 align:start position:0% ranking score color and then it also picks<00:24:47.840> from<00:24:48.159> a<00:24:48.400> set<00:24:48.640> list<00:24:48.880> of<00:24:49.200> filters<00:24:49.760> for<00:24:50.000> the 00:24:50.149 --> 00:24:50.159 align:start position:0% picks from a set list of filters for the 00:24:50.159 --> 00:24:53.029 align:start position:0% picks from a set list of filters for the quote<00:24:50.480> API.<00:24:51.039> So<00:24:51.200> it<00:24:51.440> filters<00:24:51.919> the<00:24:52.159> quotes<00:24:52.799> and 00:24:53.029 --> 00:24:53.039 align:start position:0% quote API. So it filters the quotes and 00:24:53.039 --> 00:24:56.870 align:start position:0% quote API. So it filters the quotes and then<00:24:53.200> it<00:24:53.520> scores<00:24:54.000> them<00:24:54.400> against<00:24:55.039> my<00:24:55.919> sentiment 00:24:56.870 --> 00:24:56.880 align:start position:0% then it scores them against my sentiment 00:24:56.880 --> 00:24:58.630 align:start position:0% then it scores them against my sentiment and<00:24:57.120> then<00:24:57.279> it<00:24:57.440> shows<00:24:57.679> it<00:24:57.840> on<00:24:58.000> the<00:24:58.159> screen.<00:24:58.480> So 00:24:58.630 --> 00:24:58.640 align:start position:0% and then it shows it on the screen. So 00:24:58.640 --> 00:25:01.430 align:start position:0% and then it shows it on the screen. So again<00:24:58.960> like<00:24:59.679> running<00:25:00.080> locally<00:25:00.960> not<00:25:01.200> the 00:25:01.430 --> 00:25:01.440 align:start position:0% again like running locally not the 00:25:01.440 --> 00:25:03.510 align:start position:0% again like running locally not the fastest.<00:25:01.840> I'm<00:25:02.080> sure<00:25:02.320> I<00:25:02.480> could<00:25:02.640> optimize<00:25:03.039> it<00:25:03.279> by 00:25:03.510 --> 00:25:03.520 align:start position:0% fastest. I'm sure I could optimize it by 00:25:03.520 --> 00:25:05.590 align:start position:0% fastest. I'm sure I could optimize it by caching<00:25:03.919> a<00:25:04.080> bunch<00:25:04.240> of<00:25:04.320> this<00:25:04.559> stuff<00:25:04.880> and<00:25:05.360> you 00:25:05.590 --> 00:25:05.600 align:start position:0% caching a bunch of this stuff and you 00:25:05.600 --> 00:25:07.830 align:start position:0% caching a bunch of this stuff and you know<00:25:06.000> doing<00:25:06.240> all<00:25:06.480> sorts<00:25:06.640> of<00:25:06.799> things<00:25:07.279> but<00:25:07.520> again 00:25:07.830 --> 00:25:07.840 align:start position:0% know doing all sorts of things but again 00:25:07.840 --> 00:25:10.950 align:start position:0% know doing all sorts of things but again like<00:25:08.000> a<00:25:08.240> little<00:25:08.480> like<00:25:08.880> magic<00:25:09.679> use<00:25:09.919> case<00:25:10.400> that<00:25:10.720> I 00:25:10.950 --> 00:25:10.960 align:start position:0% like a little like magic use case that I 00:25:10.960 --> 00:25:13.909 align:start position:0% like a little like magic use case that I think<00:25:11.200> is<00:25:12.240> really<00:25:12.559> indicative<00:25:13.120> of<00:25:13.360> the<00:25:13.600> kinds 00:25:13.909 --> 00:25:13.919 align:start position:0% think is really indicative of the kinds 00:25:13.919 --> 00:25:18.310 align:start position:0% think is really indicative of the kinds of<00:25:14.240> things<00:25:14.640> you<00:25:15.039> can<00:25:15.279> build<00:25:15.679> with<00:25:16.159> Jeb.<00:25:17.440> So 00:25:18.310 --> 00:25:18.320 align:start position:0% of things you can build with Jeb. So 00:25:18.320 --> 00:25:21.669 align:start position:0% of things you can build with Jeb. So that<00:25:18.640> is<00:25:18.880> my<00:25:19.440> Jev<00:25:19.919> 101.<00:25:20.799> How<00:25:20.960> to<00:25:21.120> use<00:25:21.279> it<00:25:21.440> on 00:25:21.669 --> 00:25:21.679 align:start position:0% that is my Jev 101. How to use it on 00:25:21.679 --> 00:25:24.149 align:start position:0% that is my Jev 101. How to use it on your<00:25:21.840> own<00:25:22.000> data<00:25:22.880> how<00:25:23.120> to<00:25:23.200> use<00:25:23.360> it<00:25:23.520> with<00:25:23.840> other 00:25:24.149 --> 00:25:24.159 align:start position:0% your own data how to use it with other 00:25:24.159 --> 00:25:26.789 align:start position:0% your own data how to use it with other models<00:25:24.640> and<00:25:24.880> how<00:25:25.039> to<00:25:25.200> build<00:25:25.520> some<00:25:25.840> fun 00:25:26.789 --> 00:25:26.799 align:start position:0% models and how to build some fun 00:25:26.799 --> 00:25:30.070 align:start position:0% models and how to build some fun realtime<00:25:27.600> experiences<00:25:28.480> in<00:25:28.799> your<00:25:29.039> app<00:25:29.520> intro. 00:25:30.070 --> 00:25:30.080 align:start position:0% realtime experiences in your app intro. 00:25:30.080 --> 00:25:33.669 align:start position:0% realtime experiences in your app intro. Again,<00:25:30.960> as<00:25:31.200> I<00:25:31.440> said,<00:25:31.919> this<00:25:32.080> is<00:25:32.240> Jev<00:25:32.720> episode 00:25:33.669 --> 00:25:33.679 align:start position:0% Again, as I said, this is Jev episode 00:25:33.679 --> 00:25:35.510 align:start position:0% Again, as I said, this is Jev episode number<00:25:34.159> one<00:25:34.480> this<00:25:34.799> week.<00:25:35.039> So,<00:25:35.200> we're<00:25:35.360> going<00:25:35.440> to 00:25:35.510 --> 00:25:35.520 align:start position:0% number one this week. So, we're going to 00:25:35.520 --> 00:25:38.630 align:start position:0% number one this week. So, we're going to have<00:25:35.679> another<00:25:36.080> one<00:25:36.960> midweek<00:25:37.840> with<00:25:38.080> one<00:25:38.320> of<00:25:38.400> our 00:25:38.630 --> 00:25:38.640 align:start position:0% have another one midweek with one of our 00:25:38.640 --> 00:25:40.710 align:start position:0% have another one midweek with one of our most<00:25:39.039> popular<00:25:39.520> guests.<00:25:40.000> So,<00:25:40.159> if<00:25:40.320> you<00:25:40.480> are 00:25:40.710 --> 00:25:40.720 align:start position:0% most popular guests. So, if you are 00:25:40.720 --> 00:25:43.669 align:start position:0% most popular guests. So, if you are excited<00:25:41.120> about<00:25:41.279> that<00:25:41.600> episode,<00:25:42.720> subscribe, 00:25:43.669 --> 00:25:43.679 align:start position:0% excited about that episode, subscribe, 00:25:43.679 --> 00:25:45.430 align:start position:0% excited about that episode, subscribe, comment,<00:25:44.240> let<00:25:44.400> me<00:25:44.559> know<00:25:44.640> what<00:25:44.799> you<00:25:44.960> want<00:25:45.120> us<00:25:45.279> to 00:25:45.430 --> 00:25:45.440 align:start position:0% comment, let me know what you want us to 00:25:45.440 --> 00:25:47.269 align:start position:0% comment, let me know what you want us to talk<00:25:45.600> about,<00:25:46.000> what<00:25:46.240> questions<00:25:46.559> I<00:25:46.799> can<00:25:46.960> answer 00:25:47.269 --> 00:25:47.279 align:start position:0% talk about, what questions I can answer 00:25:47.279 --> 00:25:49.990 align:start position:0% talk about, what questions I can answer about<00:25:47.600> Jeb.<00:25:48.240> And<00:25:48.480> until<00:25:48.799> then,<00:25:49.440> it<00:25:49.600> has<00:25:49.840> been 00:25:49.990 --> 00:25:50.000 align:start position:0% about Jeb. And until then, it has been 00:25:50.000 --> 00:25:52.230 align:start position:0% about Jeb. And until then, it has been so<00:25:50.320> nice<00:25:50.720> showing<00:25:51.039> you<00:25:51.360> my<00:25:51.679> favorite<00:25:52.000> new 00:25:52.230 --> 00:25:52.240 align:start position:0% so nice showing you my favorite new 00:25:52.240 --> 00:25:56.789 align:start position:0% so nice showing you my favorite new model.<00:25:53.200> Thanks<00:25:53.440> for<00:25:53.679> joining<00:25:54.159> How<00:25:54.480> I<00:25:54.640> AI. 00:25:56.789 --> 00:25:56.799 align:start position:0% model. Thanks for joining How I AI. 00:25:56.799 --> 00:25:58.630 align:start position:0% model. Thanks for joining How I AI. Thanks<00:25:57.039> so<00:25:57.200> much<00:25:57.360> for<00:25:57.600> watching.<00:25:58.080> If<00:25:58.400> you 00:25:58.630 --> 00:25:58.640 align:start position:0% Thanks so much for watching. If you 00:25:58.640 --> 00:26:00.390 align:start position:0% Thanks so much for watching. If you enjoyed<00:25:59.120> this<00:25:59.360> show,<00:25:59.760> please<00:26:00.000> like<00:26:00.159> and 00:26:00.390 --> 00:26:00.400 align:start position:0% enjoyed this show, please like and 00:26:00.400 --> 00:26:02.070 align:start position:0% enjoyed this show, please like and subscribe<00:26:00.720> here<00:26:00.960> on<00:26:01.120> YouTube,<00:26:01.600> or<00:26:01.840> even 00:26:02.070 --> 00:26:02.080 align:start position:0% subscribe here on YouTube, or even 00:26:02.080 --> 00:26:03.510 align:start position:0% subscribe here on YouTube, or even better,<00:26:02.400> leave<00:26:02.559> us<00:26:02.720> a<00:26:02.960> comment<00:26:03.120> with<00:26:03.360> your 00:26:03.510 --> 00:26:03.520 align:start position:0% better, leave us a comment with your 00:26:03.520 --> 00:26:05.909 align:start position:0% better, leave us a comment with your thoughts.<00:26:04.400> You<00:26:04.559> can<00:26:04.720> also<00:26:04.960> find<00:26:05.200> this<00:26:05.360> podcast 00:26:05.909 --> 00:26:05.919 align:start position:0% thoughts. You can also find this podcast 00:26:05.919 --> 00:26:08.870 align:start position:0% thoughts. You can also find this podcast on<00:26:06.240> Apple<00:26:06.559> Podcasts,<00:26:07.520> Spotify,<00:26:08.320> or<00:26:08.640> your 00:26:08.870 --> 00:26:08.880 align:start position:0% on Apple Podcasts, Spotify, or your 00:26:08.880 --> 00:26:11.190 align:start position:0% on Apple Podcasts, Spotify, or your favorite<00:26:09.200> podcast<00:26:09.760> app.<00:26:10.559> Please<00:26:10.799> consider 00:26:11.190 --> 00:26:11.200 align:start position:0% favorite podcast app. Please consider 00:26:11.200 --> 00:26:13.029 align:start position:0% favorite podcast app. Please consider leaving<00:26:11.520> us<00:26:11.679> a<00:26:11.840> rating<00:26:12.159> and<00:26:12.400> review,<00:26:12.799> which 00:26:13.029 --> 00:26:13.039 align:start position:0% leaving us a rating and review, which 00:26:13.039 --> 00:26:15.669 align:start position:0% leaving us a rating and review, which will<00:26:13.279> help<00:26:13.520> others<00:26:14.000> find<00:26:14.240> the<00:26:14.480> show.<00:26:15.279> You<00:26:15.520> can 00:26:15.669 --> 00:26:15.679 align:start position:0% will help others find the show. You can 00:26:15.679 --> 00:26:17.909 align:start position:0% will help others find the show. You can see<00:26:15.919> all<00:26:16.159> our<00:26:16.480> episodes<00:26:17.120> and<00:26:17.440> learn<00:26:17.760> more 00:26:17.909 --> 00:26:17.919 align:start position:0% see all our episodes and learn more 00:26:17.919 --> 00:26:21.590 align:start position:0% see all our episodes and learn more about<00:26:18.080> the<00:26:18.320> show<00:26:18.559> at<00:26:18.880> howiaipod.com. 00:26:21.590 --> 00:26:21.600 align:start position:0% about the show at howiaipod.com. 00:26:21.600 --> 00:26:25.159 align:start position:0% about the show at howiaipod.com. See<00:26:21.760> you<00:26:21.919> next<00:26:22.159> time.