1 01:00:00,708 --> 01:00:01,625 Welcome back to the 2 01:00:01,625 --> 01:00:03,833 Laravel Community Creator Series. 3 01:00:04,791 --> 01:00:07,041 Today we are joined by Alfred Nutile, 4 01:00:07,833 --> 01:00:10,666 and he has, you know, he's been a pillar 5 01:00:10,666 --> 01:00:11,541 of the community forever. 6 01:00:11,791 --> 01:00:15,125 I think I've known about him for, man, 10 7 01:00:15,125 --> 01:00:16,958 years now? Does that sound about right? 8 01:00:17,500 --> 01:00:19,000 But, you know, Alfred, welcome to the 9 01:00:19,000 --> 01:00:20,375 show, and if you don't mind, sort of 10 01:00:20,375 --> 01:00:21,250 introduce yourself to 11 01:00:21,250 --> 01:00:22,583 those that might not know you. 12 01:00:23,041 --> 01:00:25,375 Right, no, thank you. Yeah, it's been a 13 01:00:25,375 --> 01:00:26,666 while. I kind of realize I'm 14 01:00:26,666 --> 01:00:28,000 not in the background a lot, 15 01:00:28,000 --> 01:00:30,083 especially I was hidden away at Pfizer 16 01:00:30,083 --> 01:00:32,000 for a while. I introduced Laravel 17 01:00:32,000 --> 01:00:34,000 there eons ago, 10 or 18 01:00:34,000 --> 01:00:35,333 more years ago, 4.2. 19 01:00:36,166 --> 01:00:38,416 And I worked there for like 11 years as a 20 01:00:38,416 --> 01:00:40,041 contractor, kind of hiding away. 21 01:00:40,791 --> 01:00:42,291 But for the past three years, I've been 22 01:00:42,291 --> 01:00:44,458 on my own and just producing more content 23 01:00:44,458 --> 01:00:45,125 for the public 24 01:00:45,125 --> 01:00:46,916 because of being on my own. 25 01:00:46,916 --> 01:00:47,583 It's a lot easier just 26 01:00:47,583 --> 01:00:49,166 to share things. So, yeah. 27 01:00:50,250 --> 01:00:53,833 That's awesome. Yes, yes. I've, man, it's 28 01:00:53,833 --> 01:00:55,500 funny how like, you know, 29 01:00:55,500 --> 01:00:57,000 the community's been, you know, 30 01:00:57,000 --> 01:00:59,083 it's just so big from all these years and 31 01:00:59,083 --> 01:01:00,541 like you don't get to meet everybody just 32 01:01:00,541 --> 01:01:01,958 because it's, you know, now it's so 33 01:01:01,958 --> 01:01:02,875 global and worldwide. 34 01:01:03,166 --> 01:01:05,250 So it's awesome, you know, for you to 35 01:01:05,250 --> 01:01:07,666 come on board and do this with us. 36 01:01:08,416 --> 01:01:11,041 That's awesome. Yeah. Thanks. So you have 37 01:01:11,041 --> 01:01:13,083 a project which is pretty interesting. 38 01:01:13,416 --> 01:01:16,166 It's called Lara Llama. 39 01:01:16,708 --> 01:01:18,541 Did I pronounce that right? Kind of like 40 01:01:18,541 --> 01:01:21,583 the animal? Yeah, yeah. 41 01:01:22,166 --> 01:01:25,166 It was called Lain Chain before that or 42 01:01:25,166 --> 01:01:27,625 Lara Chain, sorry. But people got to 43 01:01:27,625 --> 01:01:28,541 confuse with like 44 01:01:28,541 --> 01:01:31,375 Bitcoin and that type of stuff. 45 01:01:32,333 --> 01:01:34,833 So and I made it after Lain Chain, the 46 01:01:34,833 --> 01:01:36,458 Python version, but now it's just called 47 01:01:36,458 --> 01:01:38,500 Lara Llama just because again, naming's 48 01:01:38,500 --> 01:01:40,166 hard and I just tried to rename it. 49 01:01:41,416 --> 01:01:43,000 That's good, though. I mean, that seems 50 01:01:43,000 --> 01:01:44,041 memorable, you know. It's 51 01:01:44,041 --> 01:01:44,875 like, oh, that's simple. 52 01:01:45,125 --> 01:01:47,000 And, you know, it stands out because it's 53 01:01:47,000 --> 01:01:49,250 not something you hear very often. So 54 01:01:49,250 --> 01:01:51,000 what exactly is the project? 55 01:01:51,000 --> 01:01:54,666 So and that's the thing. So two years 56 01:01:54,666 --> 01:01:56,750 ago, Lain, so basically it all started 57 01:01:56,750 --> 01:01:58,625 out of being scared out of my socks one 58 01:01:58,625 --> 01:02:00,416 night learning about Lain Chain. 59 01:02:01,250 --> 01:02:03,541 Lain Chain is the Python project that 60 01:02:03,541 --> 01:02:05,458 builds automations and workflows and 61 01:02:05,458 --> 01:02:07,208 makes it really easy for developers to 62 01:02:07,208 --> 01:02:09,125 say, hey, I want to connect all these 63 01:02:09,125 --> 01:02:12,166 things together with LLMs and workflows 64 01:02:12,166 --> 01:02:14,208 and all this stuff to then make things 65 01:02:14,208 --> 01:02:17,291 happen, projects and, you know, agents 66 01:02:17,291 --> 01:02:19,000 and stuff that can really automate stuff. 67 01:02:19,000 --> 01:02:20,708 And I'll talk about that later because 68 01:02:20,708 --> 01:02:22,541 with your workflows, we could talk about 69 01:02:22,541 --> 01:02:24,708 that. And I was like, wow, what's going 70 01:02:24,708 --> 01:02:26,625 to happen to me, a PHP Laravel developer? 71 01:02:26,625 --> 01:02:27,666 Do I have to start learning Python? 72 01:02:28,125 --> 01:02:31,000 Where do we fit into this next era of web 73 01:02:31,000 --> 01:02:34,041 technology? So then like around that 74 01:02:34,041 --> 01:02:38,083 time, I started making Lara Chain to just 75 01:02:38,083 --> 01:02:39,000 prove to myself we still have a place. 76 01:02:39,000 --> 01:02:42,666 And when you come down to it, one of the 77 01:02:42,666 --> 01:02:44,166 biggest things with open AI is they made 78 01:02:44,166 --> 01:02:46,375 an API that was really easy to use. And 79 01:02:46,375 --> 01:02:49,041 we, Laravel is really, 80 01:02:49,041 --> 01:02:50,125 really good with APIs. 81 01:02:50,875 --> 01:02:52,291 And so when it comes to building web 82 01:02:52,291 --> 01:02:54,625 stacks that can have scheduling, 83 01:02:54,916 --> 01:02:57,666 batching, automations, we still have a 84 01:02:57,666 --> 01:02:59,250 foot in the game or whatever they say, 85 01:02:59,250 --> 01:03:01,708 because we can do all that and use these 86 01:03:01,708 --> 01:03:04,333 APIs and get all the benefits of this AI 87 01:03:04,333 --> 01:03:06,416 or more importantly, or more 88 01:03:06,416 --> 01:03:08,000 specifically LLM integrations. 89 01:03:08,791 --> 01:03:13,291 So that's where Lara Llama is at now at its 90 01:03:13,291 --> 01:03:17,750 core, it is a rag system, but where it 91 01:03:17,750 --> 01:03:19,583 helps to retrieve data from a vector 92 01:03:19,583 --> 01:03:22,208 database augmented with the LLM and 93 01:03:22,208 --> 01:03:23,291 generate more data 94 01:03:23,291 --> 01:03:24,000 from that or more output. 95 01:03:24,000 --> 01:03:27,666 But it's more than that, the goal was 96 01:03:27,666 --> 01:03:29,625 actually to go beyond making it for 97 01:03:29,625 --> 01:03:31,000 developers, but making it for business 98 01:03:31,000 --> 01:03:32,958 owners or not no code level people as 99 01:03:32,958 --> 01:03:35,291 well who can log in, click, click, click, 100 01:03:35,375 --> 01:03:37,416 and do things to automate like checking 101 01:03:37,416 --> 01:03:40,000 your email boxes or scraping websites to 102 01:03:40,000 --> 01:03:41,541 gather data about their clients and then 103 01:03:41,541 --> 01:03:42,000 generate more content. 104 01:03:43,000 --> 01:03:45,208 So it really started to grow into more 105 01:03:45,208 --> 01:03:46,791 than a rag system because I'm seeing 106 01:03:46,791 --> 01:03:50,000 workflows and automations around that. 107 01:03:50,000 --> 01:03:51,416 And one of the most recent ones I'll talk 108 01:03:51,416 --> 01:03:54,416 about after is how it can be a personal 109 01:03:54,416 --> 01:03:55,625 assistant around projects 110 01:03:55,625 --> 01:03:56,916 and planning around that. 111 01:03:57,833 --> 01:04:00,583 So that's the gist of where it came from 112 01:04:00,583 --> 01:04:01,291 and what it's about. 113 01:04:02,500 --> 01:04:04,541 That's awesome. Yeah, it's the whole 114 01:04:04,541 --> 01:04:08,416 like, you know, for me sort of very new 115 01:04:08,416 --> 01:04:11,333 to that side of the tech stack, you know, 116 01:04:11,333 --> 01:04:12,500 tell this the future 117 01:04:12,500 --> 01:04:14,583 of LLMs and everything. 118 01:04:16,250 --> 01:04:19,125 Like, say you had to explain LLM to 119 01:04:19,125 --> 01:04:21,625 somebody that's not even big into coding. 120 01:04:21,916 --> 01:04:22,750 How would you even 121 01:04:22,750 --> 01:04:24,250 describe that, I guess? 122 01:04:25,000 --> 01:04:26,958 I know a lot of people are saying it's 123 01:04:26,958 --> 01:04:30,333 auto correct on steroids. I think I think 124 01:04:30,333 --> 01:04:33,583 a good way to look at it is, you know, 125 01:04:33,916 --> 01:04:37,541 it's just a way for us to feed a prompt 126 01:04:37,541 --> 01:04:39,416 to or a question with some information 127 01:04:39,416 --> 01:04:44,041 and get results and it basically, you 128 01:04:44,041 --> 01:04:46,083 know, people are fearful about 129 01:04:46,083 --> 01:04:48,875 hallucinations, but it doesn't have to be 130 01:04:48,875 --> 01:04:49,583 a problem once you get 131 01:04:49,583 --> 01:04:51,000 better at these tools. 132 01:04:51,000 --> 01:04:54,958 So an LLM is just an API or system or we 133 01:04:54,958 --> 01:04:56,916 can use to basically hand it a question 134 01:04:56,916 --> 01:05:00,208 and get results. So, for example, I have 135 01:05:00,208 --> 01:05:03,125 a lot of I'll use it. Here's a nice one. 136 01:05:03,125 --> 01:05:05,708 We send recipes to Lera Lama via the 137 01:05:05,708 --> 01:05:07,041 email address it makes for you. 138 01:05:07,458 --> 01:05:08,875 It takes all those recipes and at the end 139 01:05:08,875 --> 01:05:10,833 of the week, it sends a summary of the 140 01:05:10,833 --> 01:05:13,291 recipes and what we like, you know, it 141 01:05:13,291 --> 01:05:15,666 then summarizes them by title, by cook 142 01:05:15,666 --> 01:05:17,958 time or whatever we want, because we tell 143 01:05:17,958 --> 01:05:20,000 the LLM in the prompt, you know, at the end of the week, send us an email. 144 01:05:20,000 --> 01:05:24,000 Summarize all the new recipes this way 145 01:05:24,000 --> 01:05:25,875 and then it produces that output that 146 01:05:25,875 --> 01:05:28,000 way. So does that 147 01:05:28,000 --> 01:05:28,875 answer your question there? 148 01:05:29,125 --> 01:05:30,875 It does. It does. That's pretty good. 149 01:05:30,875 --> 01:05:34,500 That was a good explanation, I think. So 150 01:05:34,500 --> 01:05:36,125 I think my next question just about the 151 01:05:36,125 --> 01:05:39,833 project is you can actually use sort of 152 01:05:39,833 --> 01:05:42,833 any back end, right? 153 01:05:42,833 --> 01:05:45,458 As far as like, yeah, or called or. Yeah, 154 01:05:46,125 --> 01:05:46,958 that's a good question. 155 01:05:47,666 --> 01:05:49,000 There's so more, right? 156 01:05:49,000 --> 01:05:51,083 Oh, yeah, yeah. And it's endless because 157 01:05:51,083 --> 01:05:53,666 again, we're like once this became an API 158 01:05:53,666 --> 01:05:55,541 thing, it's endless and we shouldn't lock 159 01:05:55,541 --> 01:05:57,166 ourselves down to a API 160 01:05:57,166 --> 01:05:58,500 like open AI, especially. 161 01:05:59,333 --> 01:06:01,875 So the goal here is two things. One is by 162 01:06:01,875 --> 01:06:04,083 being agnostic to the LM where we can 163 01:06:04,083 --> 01:06:05,791 talk to any API and get the results, just 164 01:06:05,791 --> 01:06:07,875 like we do with storage or cash or 165 01:06:07,875 --> 01:06:08,958 anything in Laravel. 166 01:06:09,500 --> 01:06:13,125 We talked to an LM. We get the results in 167 01:06:13,125 --> 01:06:15,250 we format them like the same for any LM 168 01:06:15,250 --> 01:06:16,541 you're talking to any API. 169 01:06:18,000 --> 01:06:19,541 And so at that point, it doesn't matter. 170 01:06:19,541 --> 01:06:21,041 You can just keep spitting out these HTTP 171 01:06:21,041 --> 01:06:26,708 driven drivers in Grok, Claude, Olama, 172 01:06:26,708 --> 01:06:27,750 which that's why I really want to talk 173 01:06:27,750 --> 01:06:28,791 about an open AI are the ones 174 01:06:28,791 --> 01:06:30,458 that I have working right now. 175 01:06:31,750 --> 01:06:33,541 But then you get into the more important 176 01:06:33,541 --> 01:06:35,000 thing coming up down the road is like 177 01:06:35,000 --> 01:06:38,583 within two years, like recently, PCs have 178 01:06:38,583 --> 01:06:43,000 released chips that are good with AI. 179 01:06:43,000 --> 01:06:45,083 So you can run Olama. Have you heard of 180 01:06:45,083 --> 01:06:48,208 Olama at all? I have not known so Olama. 181 01:06:48,208 --> 01:06:50,541 Olama. Yeah, Olama is like the engine X 182 01:06:50,541 --> 01:06:53,416 of LLMs. Okay, you run a llama on your 183 01:06:53,416 --> 01:06:54,333 machine, just like engine 184 01:06:54,333 --> 01:06:55,625 X download, click running. 185 01:06:56,125 --> 01:06:57,583 But then you pull in a model. So I'm 186 01:06:57,583 --> 01:07:01,541 going to pull in the model, llama 3.1. So 187 01:07:01,541 --> 01:07:04,416 now you can then run that model on your 188 01:07:04,416 --> 01:07:05,708 machine and ask it questions. 189 01:07:06,000 --> 01:07:09,041 It makes an API. So just like engine X, 190 01:07:09,041 --> 01:07:11,750 it's a proxy. That proxy has an API, you 191 01:07:11,750 --> 01:07:13,000 talk to that API, it happens 192 01:07:13,000 --> 01:07:14,458 to match opening AI exactly. 193 01:07:15,083 --> 01:07:16,583 So now you could just point your driver 194 01:07:16,583 --> 01:07:20,541 there. Right. So now you have a local LLM 195 01:07:20,541 --> 01:07:23,083 that you can talk to, more importantly, 196 01:07:23,083 --> 01:07:25,000 for a lot of people, a, it costs nothing 197 01:07:25,000 --> 01:07:28,000 besides your machine and B, you don't 198 01:07:28,000 --> 01:07:30,083 have fear of like your data leaking out, 199 01:07:30,458 --> 01:07:32,500 because you're running a local LLM. 200 01:07:33,000 --> 01:07:35,041 So that's another win here is that when 201 01:07:35,041 --> 01:07:37,000 you're working as a developer locally, or 202 01:07:37,000 --> 01:07:39,041 if even for privacy reasons, you can use 203 01:07:39,041 --> 01:07:41,750 that local API. So it's another key thing 204 01:07:41,750 --> 01:07:44,333 there. So that's awesome. Yeah. Yeah, it 205 01:07:44,333 --> 01:07:46,000 is amazing. Yeah. Yeah. 206 01:07:46,333 --> 01:07:49,708 I was gonna say, yeah, it's, well, let's 207 01:07:49,708 --> 01:07:51,458 just, while we're talking about this, 208 01:07:51,458 --> 01:07:52,041 let's talk about some 209 01:07:52,041 --> 01:07:53,833 use cases. Yeah. Right. 210 01:07:54,000 --> 01:07:57,041 You know, for me as a sort of a content 211 01:07:57,041 --> 01:07:59,000 creator, the first thing that comes to 212 01:07:59,000 --> 01:08:01,750 mind is like, article summaries for 213 01:08:01,750 --> 01:08:05,333 sharing on socials. Yeah. That's sort of 214 01:08:05,333 --> 01:08:06,791 the first one I think about, but there's 215 01:08:06,791 --> 01:08:08,916 like so many use cases you can use this 216 01:08:08,916 --> 01:08:10,541 for. Right. I mean, it's, it's sort of 217 01:08:10,541 --> 01:08:11,833 endless, whatever you, you 218 01:08:11,833 --> 01:08:13,000 can dream up, you can do. 219 01:08:14,000 --> 01:08:16,583 It's good. It's yeah. And it's so let's 220 01:08:16,583 --> 01:08:18,250 talk about use cases. And then along the 221 01:08:18,250 --> 01:08:20,750 line, let's keep in our minds that, hey, 222 01:08:20,750 --> 01:08:22,333 chat, you can do that. I can go to their 223 01:08:22,333 --> 01:08:24,583 website, paste this in, and it can do it. 224 01:08:24,583 --> 01:08:25,541 So we'll always keep 225 01:08:25,541 --> 01:08:26,458 that in mind as we talk. 226 01:08:27,041 --> 01:08:28,583 And then another thing to keep in mind is 227 01:08:28,583 --> 01:08:30,208 like, no matter what it can do today, 228 01:08:30,750 --> 01:08:32,250 we're always going to be ahead of it, 229 01:08:32,250 --> 01:08:33,833 because we're developers, we're creating, 230 01:08:34,041 --> 01:08:36,500 we're thinking ahead of things. So we'll 231 01:08:36,500 --> 01:08:38,083 always be able to offer our customers and 232 01:08:38,083 --> 01:08:39,458 ourselves an edge because 233 01:08:39,458 --> 01:08:40,000 we're always ahead of the case. 234 01:08:40,000 --> 01:08:42,041 And I've proven this with myself for 235 01:08:42,041 --> 01:08:43,791 years, at least two years now with 236 01:08:43,791 --> 01:08:45,291 opening AI, I'm always way ahead of them 237 01:08:45,291 --> 01:08:47,541 on some ideas and abilities. So back to 238 01:08:47,541 --> 01:08:52,291 your point. You could use like, like, let 239 01:08:52,291 --> 01:08:53,750 me specifically talk about mine. And then 240 01:08:53,750 --> 01:08:54,666 you'll see your overlap. 241 01:08:55,333 --> 01:08:57,291 I made a project in Leralama. That 242 01:08:57,291 --> 01:09:00,958 project is basically me with a prompt 243 01:09:00,958 --> 01:09:02,833 saying, hey, help me market this book. 244 01:09:03,375 --> 01:09:04,958 What are some key things I can do? Build 245 01:09:04,958 --> 01:09:07,875 me a plan. And then the project says, 246 01:09:08,208 --> 01:09:09,000 okay, here's your plan. 247 01:09:09,000 --> 01:09:11,416 Here's all the tasks you have to do. And 248 01:09:11,416 --> 01:09:13,583 when they're due, I'll remind you every 249 01:09:13,583 --> 01:09:15,708 morning what's going on this week. Right. 250 01:09:16,333 --> 01:09:18,833 And then in the background, I can have a 251 01:09:18,833 --> 01:09:20,125 bunch of other stuff happen because 252 01:09:20,125 --> 01:09:22,333 Leralama has these plugins or these ways 253 01:09:22,333 --> 01:09:24,958 to send data to the system, which is 254 01:09:24,958 --> 01:09:28,125 another thing to keep in mind is all day 255 01:09:28,125 --> 01:09:28,916 long, we're collecting 256 01:09:28,916 --> 01:09:30,000 data or we like things. 257 01:09:30,000 --> 01:09:31,583 And if you can send them somewhere 258 01:09:31,583 --> 01:09:34,583 consistently and then have that be your 259 01:09:34,583 --> 01:09:37,000 repository, then that's a big win. Where 260 01:09:37,000 --> 01:09:38,416 it's opening AI or chat, GPT and all 261 01:09:38,416 --> 01:09:40,000 these web interfaces, it's kind of hard 262 01:09:40,000 --> 01:09:41,458 to just keep it up to date and keep your 263 01:09:41,458 --> 01:09:42,041 data in there. So 264 01:09:42,041 --> 01:09:44,000 another short term win there. 265 01:09:44,416 --> 01:09:46,375 So now all week long, I can send it via 266 01:09:46,375 --> 01:09:48,541 email, a link to a news article I like. 267 01:09:48,541 --> 01:09:51,666 So 10 articles later, it's collecting all 268 01:09:51,666 --> 01:09:53,916 this stuff when it gets the email, it 269 01:09:53,916 --> 01:09:55,666 goes, oh, there's a link in here. I'm 270 01:09:55,666 --> 01:09:57,208 going to go his prompt says go get the 271 01:09:57,208 --> 01:09:58,000 website from that link. 272 01:09:58,041 --> 01:10:00,083 And I'll go get it goes, it gets the 273 01:10:00,083 --> 01:10:02,166 website downloads it and puts it into the 274 01:10:02,166 --> 01:10:05,166 system, right? So now by the end of the 275 01:10:05,166 --> 01:10:08,458 week, I have a collection of emails that 276 01:10:08,458 --> 01:10:10,083 are now websites I wanted 277 01:10:10,083 --> 01:10:11,708 to talk about or think about. 278 01:10:12,166 --> 01:10:13,750 I have a system that could help summarize 279 01:10:13,750 --> 01:10:16,541 them for me. I could potentially have the 280 01:10:16,541 --> 01:10:18,000 system plugged in the LinkedIn or Twitter 281 01:10:18,000 --> 01:10:19,791 to help post for me consistently, 282 01:10:21,125 --> 01:10:23,500 especially once I build trust with it. 283 01:10:23,500 --> 01:10:24,666 And that's another thing I talked about 284 01:10:24,666 --> 01:10:27,000 in another article of like, you can automate a lot of things, but we can't do that. 285 01:10:27,000 --> 01:10:28,041 We can automate a lot of things, but we 286 01:10:28,041 --> 01:10:30,000 have to build that trust meter in the 287 01:10:30,000 --> 01:10:32,791 specific task. So for you, it's it kind 288 01:10:32,791 --> 01:10:35,000 of overlaps what you're doing, right? You 289 01:10:35,000 --> 01:10:36,500 can start collecting information in one 290 01:10:36,500 --> 01:10:38,166 place, you could start helping it, it can 291 01:10:38,166 --> 01:10:39,791 even know your voice and your tone. 292 01:10:40,708 --> 01:10:42,125 So there's an area in Laryllama where you 293 01:10:42,125 --> 01:10:44,375 can say, this is how I speak, this is how 294 01:10:44,375 --> 01:10:46,375 I write, I mean, right? So then when it's 295 01:10:46,375 --> 01:10:48,041 repeating things or building things for 296 01:10:48,041 --> 01:10:48,791 you, you can say use 297 01:10:48,791 --> 01:10:50,416 my voice or use my tone. 298 01:10:51,000 --> 01:10:52,833 And when the LM is building that response 299 01:10:52,833 --> 01:10:55,416 or building that summary, it can then use 300 01:10:55,416 --> 01:10:56,666 your tone to help do that. 301 01:10:57,375 --> 01:10:59,208 So that's that's pretty sweet. Because 302 01:10:59,208 --> 01:11:04,583 one thing just using like chat GPT is the 303 01:11:04,583 --> 01:11:07,666 when I write prompts, I try to be really 304 01:11:07,666 --> 01:11:09,666 specific, but it's like it will still 305 01:11:09,666 --> 01:11:11,625 come out weird a lot of times. 306 01:11:13,000 --> 01:11:15,541 Yeah, so as an example, so like when we 307 01:11:15,541 --> 01:11:17,416 publish a new post on the on the Laryll 308 01:11:17,416 --> 01:11:20,583 news website, I'm just using Zapier right 309 01:11:20,583 --> 01:11:22,500 now and it pulls down the article tags. 310 01:11:23,083 --> 01:11:25,250 Yeah, it runs it through chat GPT and 311 01:11:25,250 --> 01:11:27,000 supposed to summarize it into a tweet. 312 01:11:27,708 --> 01:11:29,916 And then it pushes out to like threads 313 01:11:29,916 --> 01:11:31,000 and LinkedIn or whatever. 314 01:11:31,000 --> 01:11:34,000 But a lot of times it'll come out like, 315 01:11:35,250 --> 01:11:37,166 like in a first person, you know, like 316 01:11:37,166 --> 01:11:38,833 I'm writing about something Larylla 317 01:11:38,833 --> 01:11:40,625 Incorporated did. And it'll be like, look 318 01:11:40,625 --> 01:11:42,250 what we did. And it's like, but that's 319 01:11:42,250 --> 01:11:43,958 not that's not even how I wrote the 320 01:11:43,958 --> 01:11:45,833 prompt. Like it should never do that. But 321 01:11:45,833 --> 01:11:47,291 you know, look what we made in this 322 01:11:47,291 --> 01:11:49,375 package. But I've still been struggling 323 01:11:49,375 --> 01:11:50,666 with the trust issue on 324 01:11:50,666 --> 01:11:53,000 the way I've been doing it. 325 01:11:53,000 --> 01:11:56,416 Yeah, in in one thing to mention there is 326 01:11:56,416 --> 01:11:58,458 prompt engineering seems like a silly 327 01:11:58,458 --> 01:12:02,125 concept. But I think you'll see you have 328 01:12:02,125 --> 01:12:05,000 to get better at it. Right. So just sit 329 01:12:05,000 --> 01:12:08,000 there and hammer away in the in the chat 330 01:12:08,000 --> 01:12:10,541 GPT UI or Claude, I like Claude better. 331 01:12:11,541 --> 01:12:12,875 Throw your prompt at it, get your 332 01:12:12,875 --> 01:12:14,583 responses, get them right, keep messing 333 01:12:14,583 --> 01:12:16,791 with the prompt, ask it to help you fix 334 01:12:16,791 --> 01:12:19,000 the prompt to get the right answer 335 01:12:19,000 --> 01:12:21,041 because you're what you're asking isn't 336 01:12:21,041 --> 01:12:24,208 hard, impossible. I mean, it's just, you 337 01:12:24,208 --> 01:12:25,291 need to keep refining your 338 01:12:25,291 --> 01:12:26,000 prompt to help with that. 339 01:12:26,000 --> 01:12:29,041 And you know, the concept of multi shot 340 01:12:29,041 --> 01:12:31,416 versus one shot, like you can give it 341 01:12:31,416 --> 01:12:33,000 multiple examples of what you want 342 01:12:33,000 --> 01:12:34,708 multiple examples of what you don't want 343 01:12:34,708 --> 01:12:37,500 so that it can keep learning and not 344 01:12:37,500 --> 01:12:39,416 learning is a bad word. It can keep using 345 01:12:39,416 --> 01:12:40,958 the context of your prompt to 346 01:12:40,958 --> 01:12:42,291 not do the wrong thing again. 347 01:12:43,000 --> 01:12:45,583 So yeah, awesome. Yeah, yeah. 348 01:12:47,000 --> 01:12:49,125 Not to sort of derail too much. But as 349 01:12:49,125 --> 01:12:51,375 far as like deploying like say I want to 350 01:12:51,375 --> 01:12:54,083 run this on my own on my side, I can just 351 01:12:54,083 --> 01:12:56,666 deploy it as a normal level app or is 352 01:12:56,666 --> 01:12:58,291 there like a lot of stuff involved like 353 01:12:58,291 --> 01:12:59,375 I'm thinking like a 354 01:12:59,375 --> 01:13:00,708 forge or something like that. 355 01:13:00,708 --> 01:13:01,750 Yeah, yeah, forge. 356 01:13:03,000 --> 01:13:06,000 It's really that easy. So, you know, 357 01:13:06,166 --> 01:13:07,750 ideally it would be a bunch of easy like 358 01:13:07,750 --> 01:13:09,041 filament ideally it would be like 359 01:13:09,041 --> 01:13:12,541 filament but it's not like, listen, my 360 01:13:12,541 --> 01:13:16,083 goal is to inspire 361 01:13:16,083 --> 01:13:17,500 people to think about this. 362 01:13:18,375 --> 01:13:20,333 Right, we have it, we have, look at I was 363 01:13:20,333 --> 01:13:22,083 pulling up some numbers about lane chain 364 01:13:22,083 --> 01:13:23,958 there's 72,000 stars and 365 01:13:23,958 --> 01:13:26,166 GitHub versus level 78,000. 366 01:13:27,000 --> 01:13:29,708 This is a popular thing that no one's 367 01:13:29,708 --> 01:13:31,458 talking about in our community very few 368 01:13:31,458 --> 01:13:32,625 people that I meet even know what lane 369 01:13:32,625 --> 01:13:34,666 chain is. Okay, yeah, I've never heard of 370 01:13:34,666 --> 01:13:37,875 it. Right. So my point is, there's 371 01:13:37,875 --> 01:13:39,375 something going on here it's more than 372 01:13:39,375 --> 01:13:41,000 hype, it's a new way of thinking about 373 01:13:41,000 --> 01:13:43,041 tools just like WordPress was a CMS. 374 01:13:44,000 --> 01:13:45,958 We have a new era of like I call it a CRS 375 01:13:45,958 --> 01:13:47,750 a content retrieval system but it's more 376 01:13:47,750 --> 01:13:49,625 than that it's automation it's workflows. 377 01:13:50,583 --> 01:13:52,833 And so, ideally, it would be like 378 01:13:52,833 --> 01:13:54,125 filament where you can plug it in your 379 01:13:54,125 --> 01:13:56,416 level package and go right right now it's 380 01:13:56,416 --> 01:13:58,250 a, it is like WordPress where it's like 381 01:13:58,250 --> 01:14:00,208 the whole thing or nothing, and that's 382 01:14:00,208 --> 01:14:01,208 not ideal, whatever. 383 01:14:02,000 --> 01:14:05,541 But honestly forage deploy use a Postgres 384 01:14:05,541 --> 01:14:08,291 database on forage in everything should 385 01:14:08,291 --> 01:14:10,291 just work because it's that simple just 386 01:14:10,291 --> 01:14:13,083 Laravel Postgres with its vector ability 387 01:14:13,083 --> 01:14:15,750 which is awesome horizon to run q jobs 388 01:14:15,750 --> 01:14:17,750 in, and that's pretty much 389 01:14:17,750 --> 01:14:19,500 it in web sockets reverb or 390 01:14:21,000 --> 01:14:23,125 to get a little bit of the dynamic UI. 391 01:14:23,750 --> 01:14:25,041 But then what you get after that is you 392 01:14:25,041 --> 01:14:27,000 get the the awesomeness of Laravel with 393 01:14:27,000 --> 01:14:28,000 the scheduling where you 394 01:14:28,000 --> 01:14:29,333 can have tasks waiting to run. 395 01:14:30,416 --> 01:14:32,416 You can tell it to go check an email box 396 01:14:32,416 --> 01:14:33,333 so that's another thing. 397 01:14:35,000 --> 01:14:38,000 I have an email box so you can make a, 398 01:14:38,541 --> 01:14:40,291 you know, like an info at your email 399 01:14:40,291 --> 01:14:41,458 domain and then you can say 400 01:14:41,458 --> 01:14:42,791 okay go get emails from there. 401 01:14:43,416 --> 01:14:45,041 And so every time you make a new email 402 01:14:45,041 --> 01:14:48,625 box it will just put the email plus 12345 403 01:14:48,625 --> 01:14:50,500 at that domain so you can just keep 404 01:14:50,500 --> 01:14:53,250 creating on the fly more and more places 405 01:14:53,250 --> 01:14:54,875 to send different types of emails. 406 01:14:55,375 --> 01:14:56,958 These are my emails about news articles 407 01:14:56,958 --> 01:14:58,458 these are my emails about things I want 408 01:14:58,458 --> 01:15:00,833 to look into, blah blah blah so before 409 01:15:00,833 --> 01:15:02,000 long you can use these 410 01:15:02,000 --> 01:15:02,666 different techniques. 411 01:15:03,000 --> 01:15:04,333 Or how about this one you have five 412 01:15:04,333 --> 01:15:06,291 projects and they're all in GitHub and 413 01:15:06,291 --> 01:15:08,166 every time you commit the webhook sends 414 01:15:08,166 --> 01:15:11,125 back to Lara llama the results so now at 415 01:15:11,125 --> 01:15:12,833 the end of the week, you can sum up your 416 01:15:12,833 --> 01:15:14,500 change log for five projects 417 01:15:14,500 --> 01:15:15,958 because it's all right there. 418 01:15:16,458 --> 01:15:19,000 So you got webhooks you get web scraping 419 01:15:19,000 --> 01:15:20,208 with browser shots you 420 01:15:20,208 --> 01:15:21,291 can set up browser shot. 421 01:15:22,000 --> 01:15:23,916 And you have web search with a brave API 422 01:15:23,916 --> 01:15:25,458 right now so you get all these things 423 01:15:25,458 --> 01:15:27,666 like you said by just forge deploy 424 01:15:27,666 --> 01:15:30,625 postgres which forge will do for you and 425 01:15:30,625 --> 01:15:32,500 it should be that easy honestly. 426 01:15:33,166 --> 01:15:34,708 Yeah, that's that's really good. That's 427 01:15:34,708 --> 01:15:36,291 what I like to hear is the easy side of 428 01:15:36,291 --> 01:15:39,416 it. That's the goal in it hasn't so 429 01:15:39,416 --> 01:15:42,416 there's the concept of output is there as 430 01:15:42,416 --> 01:15:44,791 well where you can say hey make an API 431 01:15:44,791 --> 01:15:47,750 API around this collection of data so now 432 01:15:47,750 --> 01:15:49,125 you have a collection of news articles, 433 01:15:49,125 --> 01:15:50,416 or more importantly. 434 01:15:51,041 --> 01:15:54,083 I was talking to someone like, well, I'll 435 01:15:54,083 --> 01:15:55,583 just say like there's a company I know 436 01:15:55,583 --> 01:15:58,708 that has articles online. And they're 437 01:15:58,708 --> 01:16:00,500 like, how do we make this whatever like 438 01:16:00,500 --> 01:16:02,916 like so it's using this modern technology 439 01:16:02,916 --> 01:16:03,458 but you could be 440 01:16:03,458 --> 01:16:04,750 sending all that stuff here. 441 01:16:05,625 --> 01:16:08,125 And then you could say, make this an API 442 01:16:08,125 --> 01:16:10,041 click a button, and now you have an API. 443 01:16:10,500 --> 01:16:13,041 So now on your website somewhere else you 444 01:16:13,041 --> 01:16:15,291 have a chat widget that talks when the 445 01:16:15,291 --> 01:16:16,750 user asked a question that actually is 446 01:16:16,750 --> 01:16:18,416 asking it from your API and layer llama 447 01:16:18,416 --> 01:16:20,000 and gets the results so you can actually write away. 448 01:16:20,000 --> 01:16:24,458 Plug in this LLM API to any website you 449 01:16:24,458 --> 01:16:27,791 want, but using your data that makes it 450 01:16:27,791 --> 01:16:30,333 chattable. So yeah, you can go in a lot 451 01:16:30,333 --> 01:16:31,166 of directions there 452 01:16:31,166 --> 01:16:32,708 with with layer llama. 453 01:16:33,291 --> 01:16:35,041 And again, this is all to inspire ideas 454 01:16:35,041 --> 01:16:37,208 if layer llama has gone in five years. I 455 01:16:37,208 --> 01:16:39,416 don't care. It's to get us thinking as a 456 01:16:39,416 --> 01:16:42,541 community. What can we be doing in I 457 01:16:42,541 --> 01:16:44,291 think what we need to be doing this state 458 01:16:44,291 --> 01:16:46,541 may be relevant relevant relevant to 459 01:16:46,541 --> 01:16:47,000 relative in this next era, you know. 460 01:16:47,000 --> 01:16:50,666 Yeah, for sure. I mean, that's, I mean, 461 01:16:50,666 --> 01:16:51,750 that's all you keep hearing about 462 01:16:51,750 --> 01:16:53,583 probably the last what five years is, you 463 01:16:53,583 --> 01:16:57,250 know, is open AI and lms and everything. 464 01:16:57,500 --> 01:16:59,541 Yeah, I'm engineering so it's I feel like 465 01:16:59,541 --> 01:17:00,875 it's going to be it's one of those things 466 01:17:00,875 --> 01:17:01,916 that that's definitely 467 01:17:01,916 --> 01:17:02,791 going to be here to stay. 468 01:17:03,833 --> 01:17:06,833 Yeah, yeah, yeah, I have a question. This 469 01:17:06,833 --> 01:17:08,416 is totally off the wall but you know, as 470 01:17:08,416 --> 01:17:10,750 you're describing all this so one feature 471 01:17:10,750 --> 01:17:13,000 of the Louisville news site is we have a community link section. 472 01:17:14,000 --> 01:17:18,500 And it's, it's sort of hard to keep up 473 01:17:18,500 --> 01:17:19,875 with because you know I'm only one person 474 01:17:19,875 --> 01:17:21,916 and then what I normally do is every 475 01:17:21,916 --> 01:17:23,791 Sunday is when I go in and 476 01:17:23,791 --> 01:17:25,208 approve them, it would be nice. 477 01:17:26,291 --> 01:17:27,583 I don't even know if this possible but it 478 01:17:27,583 --> 01:17:31,166 could could it's good. Yeah, I am or not 479 01:17:31,166 --> 01:17:33,833 spam. No, that's beautiful. Like, 100% 480 01:17:34,250 --> 01:17:38,125 like you could say hey, go look at these 481 01:17:38,125 --> 01:17:42,000 URLs go parse them so layer llama and again, you can grab the code. 482 01:17:43,000 --> 01:17:45,666 Just use it so layer llama will take your 483 01:17:45,666 --> 01:17:48,666 URL if you use so so lms have a tool 484 01:17:48,666 --> 01:17:51,458 ability and the tool says the LM says oh 485 01:17:51,458 --> 01:17:53,708 he wants a URL turned into a website so 486 01:17:53,708 --> 01:17:56,041 sometimes I'm going to use my tool, you 487 01:17:56,041 --> 01:17:57,666 know, URL to website and 488 01:17:57,666 --> 01:17:58,625 it just knows it right. 489 01:17:59,250 --> 01:18:00,708 So then it would get that data and your 490 01:18:00,708 --> 01:18:02,541 prompt will say then verify if this is 491 01:18:02,541 --> 01:18:03,000 spam or not and then the prompt. 492 01:18:03,000 --> 01:18:06,875 The results would be like yes or no like 493 01:18:06,875 --> 01:18:09,750 whatever you want. Right. So you could in 494 01:18:09,750 --> 01:18:14,208 one prompt. Say, check these URLs for me. 495 01:18:15,125 --> 01:18:16,583 If it's spam return false 496 01:18:16,583 --> 01:18:18,333 if it's not spam return true. 497 01:18:19,083 --> 01:18:21,125 And then even you know do the next thing 498 01:18:21,125 --> 01:18:23,875 if it's okay then your next tool would be 499 01:18:23,875 --> 01:18:26,083 then go set it to approved in my database 500 01:18:26,083 --> 01:18:29,000 because it could query your database but not magically. 501 01:18:30,000 --> 01:18:34,791 Think about tools dependency injection. 502 01:18:35,500 --> 01:18:36,750 Right. So when it says 503 01:18:36,750 --> 01:18:39,083 use the get URL tool. 504 01:18:40,041 --> 01:18:41,750 There else dependency injection system 505 01:18:41,750 --> 01:18:43,750 gets past that line that then renders 506 01:18:43,750 --> 01:18:46,958 that class and it's past the arguments or 507 01:18:46,958 --> 01:18:48,416 the information and then do what it needs 508 01:18:48,416 --> 01:18:50,000 to do and then return whatever it needs to return. So there's no magic here. It's just it knowing what tools you have what steps to take and what to what what to do with the results of that tool. Right. So yeah, I think that's awesome. 509 01:18:58,375 --> 01:19:00,958 You could do that and that's a brilliant. 510 01:19:01,333 --> 01:19:02,375 These are the things I want people 511 01:19:02,375 --> 01:19:04,833 thinking about though you just like it's 512 01:19:04,833 --> 01:19:08,083 not to take away your job or many jobs 513 01:19:08,083 --> 01:19:09,583 but it's to assist us in getting this 514 01:19:09,583 --> 01:19:11,000 stuff done that we don't want to do or grunt worker. You know we can be doing something else. Yeah, we mean the way you describe it could even you know it could see if it's spam. 515 01:19:20,083 --> 01:19:22,958 But then secondly it could be like can 516 01:19:22,958 --> 01:19:24,583 you make sure this article is actually 517 01:19:24,583 --> 01:19:29,000 about Laravel? Yeah, 100% by that. Yes, I got I got to have to research this more because that would be awesome to have that more automated. And I think what you saw there hopefully one thing I am writing the book in in will talk about in a moment, but basically we're empowering you to do that. 518 01:19:29,000 --> 01:19:30,875 I got to have to research this more 519 01:19:30,875 --> 01:19:32,000 because that would be awesome to have 520 01:19:32,000 --> 01:19:34,375 that more automated. And I think what you 521 01:19:34,375 --> 01:19:36,583 saw there hopefully I one thing I am 522 01:19:36,583 --> 01:19:38,291 writing the book in in will talk about 523 01:19:38,291 --> 01:19:40,166 that in a moment, but basically we're 524 01:19:40,166 --> 01:19:43,916 empowering users to like like not only is 525 01:19:43,916 --> 01:19:45,916 business owners like yourself, but when 526 01:19:45,916 --> 01:19:47,416 you build an application and you could 527 01:19:47,416 --> 01:19:49,250 say to a user number all those things you 528 01:19:49,250 --> 01:19:50,833 had to do to query the database or to 529 01:19:50,833 --> 01:19:51,750 filter or do this. No, 530 01:19:51,750 --> 01:19:52,625 just type in that prompt. 531 01:19:53,000 --> 01:19:54,791 Find me people who live in California who 532 01:19:54,791 --> 01:19:56,875 went to the school and it does it all for 533 01:19:56,875 --> 01:19:59,000 you. You're empowering users to get their 534 01:19:59,000 --> 01:20:00,916 jobs done without horrible interfaces or 535 01:20:00,916 --> 01:20:04,208 tons of steps. You know, so it's that 536 01:20:04,208 --> 01:20:05,375 prompting ability is a 537 01:20:05,375 --> 01:20:06,875 key thing here. Yeah, yeah. 538 01:20:08,583 --> 01:20:11,416 Yeah, well, actually, this might lead 539 01:20:11,416 --> 01:20:14,583 into your book, but as far as tips for 540 01:20:14,583 --> 01:20:17,583 good prompt writing the best is it best 541 01:20:17,583 --> 01:20:19,666 just to sort of just trial and error and 542 01:20:19,666 --> 01:20:21,208 ask it. Like you said, 543 01:20:21,208 --> 01:20:22,666 just ask it to help you. 544 01:20:22,916 --> 01:20:26,750 Um, yeah, I mean, I would. What I there's 545 01:20:26,750 --> 01:20:29,000 a lot of bad information out there where 546 01:20:29,000 --> 01:20:30,625 everything gets more complicated than it 547 01:20:30,625 --> 01:20:33,208 needs to be. If you stick to a particular 548 01:20:33,208 --> 01:20:34,666 structure, you'll do pretty well. 549 01:20:35,208 --> 01:20:38,833 And then there's the deep learning dot AI 550 01:20:38,833 --> 01:20:41,333 site where it's written by or run by 551 01:20:41,333 --> 01:20:42,833 Andrew and G. I think I 552 01:20:42,833 --> 01:20:43,833 forgot to say his last name. 553 01:20:44,791 --> 01:20:46,000 And there's a lot of good trainings 554 01:20:46,000 --> 01:20:47,625 there. Even one of the ladies who works 555 01:20:47,625 --> 01:20:49,500 at open AI had a good prompting training, 556 01:20:49,500 --> 01:20:52,291 but in the end, basically start off with 557 01:20:52,291 --> 01:20:55,125 the role in brackets and say, hey, you're 558 01:20:55,125 --> 01:20:56,958 my assistant who's helping me parse this 559 01:20:56,958 --> 01:20:59,750 information to find good or bad links. 560 01:21:00,000 --> 01:21:03,416 And this is, you know, these links are in 561 01:21:03,416 --> 01:21:06,166 explain what it's about. Right. And then 562 01:21:06,166 --> 01:21:08,916 your task is the next bracketed area. 563 01:21:08,916 --> 01:21:10,833 Your task is to find the links that are 564 01:21:10,833 --> 01:21:14,000 good and ignore the ones that are not in 565 01:21:14,000 --> 01:21:15,625 at the end, you're going to return to me 566 01:21:15,625 --> 01:21:17,250 an array of results. 567 01:21:17,875 --> 01:21:19,916 And then the format is the last bracket 568 01:21:19,916 --> 01:21:21,875 second to last where you're like, do this 569 01:21:21,875 --> 01:21:23,375 format. Like we just said, it's an array 570 01:21:23,375 --> 01:21:25,791 in the object with the URL, the title, 571 01:21:26,125 --> 01:21:28,000 and maybe a TL DR or all the content. 572 01:21:29,000 --> 01:21:31,833 So it's role task format. And then the 573 01:21:31,833 --> 01:21:33,083 last one is just context 574 01:21:33,083 --> 01:21:34,166 where you're handing it. 575 01:21:34,750 --> 01:21:38,000 If you're in your case, you'd be handing 576 01:21:38,000 --> 01:21:39,666 it the links, right? Where you're like, 577 01:21:39,666 --> 01:21:40,791 here's all the links I want you to look 578 01:21:40,791 --> 01:21:43,041 at. So it's that particular format that 579 01:21:43,041 --> 01:21:45,083 is a good starting point to then just 580 01:21:45,083 --> 01:21:46,000 start cranking away. 581 01:21:46,000 --> 01:21:47,708 And then, you know, you have examples 582 01:21:47,708 --> 01:21:49,708 like don't do this, do this, you know, I 583 01:21:49,708 --> 01:21:51,083 didn't like this. And then you can learn 584 01:21:51,083 --> 01:21:54,166 from those. Like one thing I, that's kind 585 01:21:54,166 --> 01:21:55,208 of interesting is when you 586 01:21:55,208 --> 01:21:56,500 use chat activity or cloud. 587 01:21:57,416 --> 01:21:59,750 And you're typing in that prompt. And you 588 01:21:59,750 --> 01:22:02,000 say check if you go do this, there's a 589 01:22:02,000 --> 01:22:04,083 system level prompt that's probably this 590 01:22:04,083 --> 01:22:05,708 big that's telling chat activity what not 591 01:22:05,708 --> 01:22:07,208 to do what to do how to answer you how to 592 01:22:07,208 --> 01:22:09,500 treat you how to think like, it's not 593 01:22:09,500 --> 01:22:11,166 just an LLM getting your question. 594 01:22:11,166 --> 01:22:14,041 It's an LLM who has a prompt around your 595 01:22:14,041 --> 01:22:16,958 prompt. Okay, so, so you got to remember, 596 01:22:16,958 --> 01:22:19,916 you know, it is a big deal prompting and 597 01:22:19,916 --> 01:22:21,458 you can give it a lot of information. 598 01:22:22,250 --> 01:22:24,416 So it can be helpful to give it a sense 599 01:22:24,416 --> 01:22:26,333 of what it's doing, why it's doing it and 600 01:22:26,333 --> 01:22:28,375 the task to be done. Does that make 601 01:22:28,375 --> 01:22:32,041 sense? It does. It does. It's, it's, it's 602 01:22:32,041 --> 01:22:34,208 funny. It almost reminds me of a back 603 01:22:34,208 --> 01:22:35,666 when I was in school, one of our 604 01:22:35,666 --> 01:22:37,625 projects, this was like middle school was 605 01:22:37,625 --> 01:22:41,125 like we had to write down how to tell 606 01:22:41,125 --> 01:22:42,208 somebody to make a peanut butter jelly 607 01:22:42,208 --> 01:22:44,125 sandwich if they, oh, yeah, and they can 608 01:22:44,125 --> 01:22:45,041 only follow the steps 609 01:22:45,041 --> 01:22:46,333 that you tell them to take. 610 01:22:47,000 --> 01:22:48,750 Just I just remember how hard that was. 611 01:22:48,750 --> 01:22:51,250 And then like, yeah, so specific, like 612 01:22:51,250 --> 01:22:54,166 you pick up the knife, you dip it in the 613 01:22:54,166 --> 01:22:57,875 jar. So it has a lot of, to me, it has a 614 01:22:57,875 --> 01:23:00,041 lot of feel of that to this, you know, 615 01:23:00,250 --> 01:23:02,500 yeah, don't give up. No, it's a good way 616 01:23:02,500 --> 01:23:04,000 to put it. So don't give up because you 617 01:23:04,000 --> 01:23:06,791 told it to do something you thought was 618 01:23:06,791 --> 01:23:09,208 obvious. But keep going and keep it 619 01:23:09,208 --> 01:23:10,000 giving it more details. 620 01:23:10,000 --> 01:23:11,666 There was a funny video on what you just 621 01:23:11,666 --> 01:23:13,500 said. And the guy had his kids doing just 622 01:23:13,500 --> 01:23:15,541 that. And he followed the directions. And 623 01:23:15,541 --> 01:23:16,833 it was just silly. Like, you're like, 624 01:23:16,833 --> 01:23:18,625 yeah, okay, I see. You know, it was a 625 01:23:18,625 --> 01:23:22,416 good one. You know, that's awesome. So 626 01:23:22,416 --> 01:23:23,791 you mentioned, you mentioned the book. So 627 01:23:23,791 --> 01:23:26,416 you're writing a book on PHP and LLMs. 628 01:23:27,500 --> 01:23:28,958 Yeah, tell us a little bit about that. 629 01:23:28,958 --> 01:23:29,791 And like, you know, how 630 01:23:29,791 --> 01:23:31,000 that came about, like, right. 631 01:23:31,375 --> 01:23:35,708 Right. So basically, it's been a couple 632 01:23:35,708 --> 01:23:37,916 years now. And I use it every day, not 633 01:23:37,916 --> 01:23:39,375 just to help get my work done, but with 634 01:23:39,375 --> 01:23:43,666 clients. I have a lot of moments where it 635 01:23:43,666 --> 01:23:45,416 just it's a tool that solves a lot of 636 01:23:45,416 --> 01:23:47,875 problems for me or gets me, you know, to 637 01:23:47,875 --> 01:23:49,166 solve a problem, because I didn't 638 01:23:49,166 --> 01:23:50,750 understand like how to do GIS in a 639 01:23:50,750 --> 01:23:51,916 database and actually know it has me 640 01:23:51,916 --> 01:23:53,500 doing everything I need to do. And I was 641 01:23:53,500 --> 01:23:56,041 able to pull it off or format emails, 642 01:23:56,375 --> 01:23:57,708 data from emails that were coming from 643 01:23:57,708 --> 01:23:59,625 random people to then generate JSON 644 01:23:59,625 --> 01:24:00,000 consistently without having to do that. 645 01:24:00,000 --> 01:24:00,458 And I was able to do that consistently 646 01:24:00,458 --> 01:24:02,166 without having to write all the text 647 01:24:02,166 --> 01:24:05,500 parsing I was trying to write. So I just 648 01:24:05,500 --> 01:24:06,791 wanted to start sharing those as 649 01:24:06,791 --> 01:24:08,458 practical solutions in this book, almost 650 01:24:08,458 --> 01:24:11,583 like a recipe book. But at the same time, 651 01:24:12,500 --> 01:24:14,666 help the developer understand how this 652 01:24:14,666 --> 01:24:16,500 works with prompts, how this works with 653 01:24:16,500 --> 01:24:20,291 drivers and APIs and how we can build or 654 01:24:20,291 --> 01:24:23,458 work in this way that we don't it doesn't 655 01:24:23,458 --> 01:24:26,416 matter what API reason because it's, you 656 01:24:26,416 --> 01:24:27,750 know, and it will continue to do that 657 01:24:27,750 --> 01:24:28,500 where it shows all these 658 01:24:28,500 --> 01:24:29,958 examples, explains it in 659 01:24:30,000 --> 01:24:32,208 hopefully at the end, the person can just 660 01:24:32,208 --> 01:24:34,000 start to see real like day to day 661 01:24:34,000 --> 01:24:36,916 examples, I can use it in for work. And 662 01:24:36,916 --> 01:24:40,000 it just it's, it's really interesting 663 01:24:40,000 --> 01:24:43,833 stuff because, you know, it's a lot of 664 01:24:43,833 --> 01:24:45,750 stuff is changing. And so I want to it's 665 01:24:45,750 --> 01:24:47,125 kind of the foundation. So you can keep 666 01:24:47,125 --> 01:24:48,916 ahead of things and not wait for things. 667 01:24:49,250 --> 01:24:51,708 Like, if you're waiting for open AI to do 668 01:24:51,708 --> 01:24:53,583 something or our PHP, open AI driver, 669 01:24:53,583 --> 01:24:55,083 you're gonna be waiting. And you 670 01:24:55,083 --> 01:24:56,791 shouldn't be because these are just API's 671 01:24:56,791 --> 01:24:58,958 and code just make stuff happen. So 672 01:24:58,958 --> 01:25:00,000 hopefully, we'll help people get 673 01:25:00,000 --> 01:25:02,625 ahead and just understand the root of 674 01:25:02,625 --> 01:25:06,000 things. So that's awesome. So, so the 675 01:25:06,000 --> 01:25:09,916 book, it's, it's still in in development, 676 01:25:09,916 --> 01:25:12,166 right? Yeah, it's still working. Not not 677 01:25:12,166 --> 01:25:14,666 officially launched yet. Yeah, it's about 678 01:25:14,666 --> 01:25:17,750 five chapters in, it's there to buy. It's 679 01:25:17,750 --> 01:25:20,250 there to see some sample chapters. And 680 01:25:20,250 --> 01:25:21,750 there's a newsletter that you can then 681 01:25:21,750 --> 01:25:23,166 keep up to date with the articles and 682 01:25:23,166 --> 01:25:26,416 stuff going on. And I will I continue to 683 01:25:26,416 --> 01:25:27,916 release some of the chapters or articles 684 01:25:27,916 --> 01:25:30,000 about the chapter to just show 685 01:25:30,000 --> 01:25:32,875 you some information while I go. So 686 01:25:32,875 --> 01:25:36,083 that's awesome. Yes. And, and so where 687 01:25:36,083 --> 01:25:38,000 are you? Where are you publishing the 688 01:25:38,000 --> 01:25:41,458 book? Are you using right? Yeah, I went 689 01:25:41,458 --> 01:25:43,166 with lean pub for no good reason. I'm old 690 01:25:43,166 --> 01:25:45,583 school. Yeah, I saw I could think of. So 691 01:25:45,583 --> 01:25:47,375 yeah, I don't know if anyone uses them 692 01:25:47,375 --> 01:25:51,500 anymore. So yeah, lean pub, PHP, LLMs 693 01:25:51,500 --> 01:25:53,833 should be able to find the book pretty 694 01:25:53,833 --> 01:25:55,541 easily. Or we can share a link after. 695 01:25:55,541 --> 01:25:57,291 Yeah, yeah, it will definitely have links 696 01:25:57,291 --> 01:25:58,416 of all this in the 697 01:25:58,416 --> 01:25:59,875 show notes when we when we 698 01:26:00,000 --> 01:26:03,000 push it up. And then I guess, you know, 699 01:26:03,000 --> 01:26:06,791 as far as the the book, the PHP, LLMs, is 700 01:26:06,791 --> 01:26:08,750 it? Yeah. I mean, if you know, Laravel, 701 01:26:08,750 --> 01:26:11,041 you know, PHP. So it doesn't it just 702 01:26:11,041 --> 01:26:13,458 raising the title PHP gives your 703 01:26:13,458 --> 01:26:15,750 audience, right? Then yeah, this is it. 704 01:26:15,750 --> 01:26:17,208 And I didn't want to deal with any legal 705 01:26:17,208 --> 01:26:19,500 stuff. But it's so Laravel. It's insane. 706 01:26:20,041 --> 01:26:23,000 I'm a Laravel. It's what I know. You 707 01:26:23,000 --> 01:26:26,250 know, so but it is, you know, at the end, 708 01:26:26,250 --> 01:26:28,000 I want all PHP developers to 709 01:26:28,000 --> 01:26:30,000 kind of be aware of, like, the 710 01:26:30,000 --> 01:26:30,791 Python community. Let's embrace this like 711 01:26:30,791 --> 01:26:32,500 the Python community did, let's make 712 01:26:32,500 --> 01:26:35,000 tools around these APIs and, and so 713 01:26:35,000 --> 01:26:36,458 forth. But yeah, it's a good point. It is 714 01:26:36,458 --> 01:26:40,416 very Laravel centric. That's awesome. Are 715 01:26:40,416 --> 01:26:43,541 you thinking of sort of like creating 716 01:26:43,541 --> 01:26:47,291 like a community around all this as and 717 01:26:47,291 --> 01:26:50,750 being like the the thought leader of the 718 01:26:50,750 --> 01:26:55,958 LLM PHP LLM? I don't know if I have the 719 01:26:55,958 --> 01:26:57,833 control to do all that. Like, I think 720 01:26:57,833 --> 01:26:58,708 this stuff just happens 721 01:26:58,708 --> 01:27:00,000 organically who you know, 722 01:27:00,000 --> 01:27:01,333 who you know, where you are in the 723 01:27:01,333 --> 01:27:03,583 community. For me, I'm just going to keep 724 01:27:03,583 --> 01:27:06,416 I have clients, I'm working on things for 725 01:27:06,416 --> 01:27:08,750 people, things come up like, you know, 726 01:27:09,583 --> 01:27:11,208 it's just amazing the stuff I've been 727 01:27:11,208 --> 01:27:13,166 solving for people lately that I couldn't 728 01:27:13,166 --> 01:27:15,291 have done before. And it's just fun. 729 01:27:15,291 --> 01:27:17,083 Because when you were like, Oh, crap, we 730 01:27:17,083 --> 01:27:18,458 can do this, you're like, this is 731 01:27:18,458 --> 01:27:20,791 awesome. Like, even one client, like they 732 01:27:20,791 --> 01:27:22,833 have this list of data, they have to get 733 01:27:22,833 --> 01:27:24,125 in the client in the customer with them 734 01:27:24,125 --> 01:27:26,041 export it because it's, they're hoarding 735 01:27:26,041 --> 01:27:28,458 your data. You know, she can take 736 01:27:28,458 --> 01:27:30,000 screenshots and it gets translated 737 01:27:30,000 --> 01:27:32,791 into the system. Right? Just from a 738 01:27:32,791 --> 01:27:34,291 screenshot. And it's like, yeah, this 739 01:27:34,291 --> 01:27:37,416 saved our butts. You don't have to hand 740 01:27:37,416 --> 01:27:38,875 enter this. This was awesome. So there's 741 01:27:38,875 --> 01:27:40,875 all these little moments that come along 742 01:27:40,875 --> 01:27:42,166 where problems are getting solved that I 743 01:27:42,166 --> 01:27:44,458 couldn't solve before. So I'll keep doing 744 01:27:44,458 --> 01:27:46,250 that. I'll keep blogging. I'll keep 745 01:27:46,250 --> 01:27:47,750 putting stuff on YouTube. And I'll have a 746 01:27:47,750 --> 01:27:49,375 video course eventually after the book to 747 01:27:49,375 --> 01:27:52,125 just help people go deeper, hopefully, or 748 01:27:52,125 --> 01:27:54,000 just continue to hopefully learn this if 749 01:27:54,000 --> 01:27:55,333 they don't like reading, they rather 750 01:27:55,333 --> 01:27:56,708 learn through videos, some people like 751 01:27:56,708 --> 01:27:58,541 that better. So yeah, 752 01:27:58,541 --> 01:27:59,375 the community thing. 753 01:28:00,000 --> 01:28:02,916 I hope, but it's a tricky one, right? 754 01:28:03,250 --> 01:28:05,416 Like, it's there for the open sources 755 01:28:05,416 --> 01:28:07,500 there to be a community. And hopefully 756 01:28:07,500 --> 01:28:10,083 people can drive it to that next level. I 757 01:28:10,083 --> 01:28:11,125 don't know how they did it with filament. 758 01:28:11,458 --> 01:28:12,708 I don't know if it was just good stuff at 759 01:28:12,708 --> 01:28:14,791 the start, or like, but that's a great 760 01:28:14,791 --> 01:28:17,833 example of a success in my book, that I 761 01:28:17,833 --> 01:28:19,416 would like to strive for with it. Yeah. 762 01:28:20,041 --> 01:28:23,125 Yeah, yeah, actually, I don't know. I'm 763 01:28:23,125 --> 01:28:26,000 feeling that, you know, I know, Laervel 764 01:28:26,000 --> 01:28:27,416 itself, you know, I was there in the 765 01:28:27,416 --> 01:28:28,958 very, very early days, and it was 766 01:28:28,958 --> 01:28:31,333 basically, you know, our C, and it was 767 01:28:31,333 --> 01:28:33,000 just like, that's how we communicate and 768 01:28:33,000 --> 01:28:36,416 talk to everybody. And then sort of. And 769 01:28:36,416 --> 01:28:38,750 then, then we then they switched to 770 01:28:38,750 --> 01:28:39,958 something else. I can't 771 01:28:39,958 --> 01:28:42,166 maybe it was so like, or not. 772 01:28:42,583 --> 01:28:43,083 Telegram. 773 01:28:44,958 --> 01:28:47,000 Telegram, yes, Telegram. And then from 774 01:28:47,000 --> 01:28:49,750 there, it went to Discord, I guess. But 775 01:28:49,750 --> 01:28:52,875 yeah, it's, it's sort of, you know, I 776 01:28:52,875 --> 01:28:55,375 think just, you know, as a project owner, 777 01:28:55,375 --> 01:28:57,625 just having some place to go and be like, 778 01:28:57,875 --> 01:28:59,583 where can I go ask a question when I 779 01:28:59,583 --> 01:29:00,166 don't understand what 780 01:29:00,166 --> 01:29:02,500 is really beneficial. But 781 01:29:02,916 --> 01:29:04,416 now it's a good point. I'll keep that in 782 01:29:04,416 --> 01:29:07,125 mind. I was using GitHub's discussion 783 01:29:07,125 --> 01:29:09,458 area, but it's not I don't think it's the 784 01:29:09,458 --> 01:29:10,708 same because it's not real 785 01:29:10,708 --> 01:29:12,833 time. So it's a good point. Yeah. 786 01:29:13,250 --> 01:29:13,333 So, 787 01:29:13,958 --> 01:29:17,666 you know, speaking of on that, this is 788 01:29:17,666 --> 01:29:21,125 totally on a tangent. Now, the one thing 789 01:29:21,125 --> 01:29:22,500 I hate about discord and all these other 790 01:29:22,500 --> 01:29:24,583 things is you can never search like the 791 01:29:24,583 --> 01:29:26,291 search is never good. Like, you know, in 792 01:29:26,291 --> 01:29:27,791 the old days when everybody used like old 793 01:29:27,791 --> 01:29:29,500 style forums, you could just go to Google 794 01:29:29,500 --> 01:29:30,250 and type in like 795 01:29:30,250 --> 01:29:31,708 whatever and it was there. 796 01:29:32,333 --> 01:29:33,791 Because it was all, you know, indexable 797 01:29:33,791 --> 01:29:35,125 and searchable. And it was like, ah, 798 01:29:35,125 --> 01:29:38,708 well, this is the answer. But I guess, in 799 01:29:38,708 --> 01:29:40,666 theory, we're actually in this 800 01:29:40,666 --> 01:29:44,500 transitionary phase of searching right 801 01:29:44,500 --> 01:29:46,041 now, you know, because you can still use 802 01:29:46,041 --> 01:29:47,291 the Google and you still get the, you 803 01:29:47,291 --> 01:29:48,916 know, whatever. But now it's like, 804 01:29:48,916 --> 01:29:51,541 everybody's going to chat GPT or going to 805 01:29:51,541 --> 01:29:53,833 all these things and searching instead of 806 01:29:53,833 --> 01:29:55,250 actually going to Google, you know, if 807 01:29:55,250 --> 01:29:57,375 it's something that they can explain, and 808 01:29:57,375 --> 01:29:58,333 you're getting better results. 809 01:29:59,291 --> 01:30:00,625 Yeah, I mean, they're going to release 810 01:30:00,625 --> 01:30:04,125 something soon about that. Yeah, I talk 811 01:30:04,125 --> 01:30:06,791 about tangent. Yeah, I just discourse and 812 01:30:06,791 --> 01:30:08,833 I always get the mix up as a discord or 813 01:30:08,833 --> 01:30:10,708 discourse because there's that one where 814 01:30:10,708 --> 01:30:12,666 the stack overflow guys were released, 815 01:30:12,666 --> 01:30:14,375 which was a great forum software. But 816 01:30:14,375 --> 01:30:14,875 then there's the one 817 01:30:14,875 --> 01:30:16,291 everybody uses for everything else. 818 01:30:16,916 --> 01:30:19,000 And I always click the video button. So 819 01:30:19,000 --> 01:30:20,750 in the moment, I'm like, panicking 820 01:30:20,750 --> 01:30:22,208 because I'm like, I just started to call 821 01:30:22,208 --> 01:30:23,416 with this person. I don't know. 822 01:30:25,166 --> 01:30:28,458 Yes, yes, I think yes, discord, C O R D 823 01:30:28,458 --> 01:30:31,416 is the one with the call button and then 824 01:30:31,416 --> 01:30:33,166 discourse like the form. 825 01:30:33,625 --> 01:30:36,375 But I'm going to follow up later, because 826 01:30:36,375 --> 01:30:38,208 I think you're spot on. I need a more 827 01:30:38,208 --> 01:30:39,750 dynamic place if I want to build 828 01:30:39,750 --> 01:30:41,083 community where people can come in and 829 01:30:41,083 --> 01:30:43,083 ask any question. Yeah, that's a good 830 01:30:43,083 --> 01:30:45,375 point. Like with native PHP, I joined 831 01:30:45,375 --> 01:30:46,708 that one. So I get to do one, 832 01:30:46,708 --> 01:30:47,416 too. Yeah, it's a great idea. 833 01:30:47,458 --> 01:30:52,666 I love that. And now the book when when 834 01:30:52,666 --> 01:30:54,500 you're expecting, I guess it's for sale 835 01:30:54,500 --> 01:30:56,750 now, and then you just release new 836 01:30:56,750 --> 01:30:58,583 chapters, you just if you purchase the 837 01:30:58,583 --> 01:31:00,000 book, you get the chapters as you write 838 01:31:00,000 --> 01:31:01,208 them. And as they come out, 839 01:31:01,833 --> 01:31:04,291 yeah, they come out every week, one or 840 01:31:04,291 --> 01:31:07,875 two on Monday. And then if at the rate 841 01:31:07,875 --> 01:31:09,416 I'm going, it will be done by early 842 01:31:09,416 --> 01:31:13,958 November. And if I remember, right, and 843 01:31:13,958 --> 01:31:16,125 but along the way, I've been adding 844 01:31:16,125 --> 01:31:17,875 chapters, I think you asked it recently, 845 01:31:17,875 --> 01:31:20,291 you said, Well, why why LMS? I'm like, I 846 01:31:20,291 --> 01:31:21,583 don't even have a chapter on that. I just 847 01:31:21,583 --> 01:31:25,083 assumed people know why. So I built out 848 01:31:25,083 --> 01:31:26,833 that chapter. And so that's a good 849 01:31:26,833 --> 01:31:28,666 example. Sometimes I think things are 850 01:31:28,666 --> 01:31:30,458 kind of come in as I as I do this stuff. 851 01:31:31,458 --> 01:31:34,833 You know, so but by early November, it 852 01:31:34,833 --> 01:31:36,750 all should be done. Yeah. 853 01:31:37,041 --> 01:31:42,833 Awesome. And, and then this, I don't know 854 01:31:42,833 --> 01:31:44,000 if your website says this or not. But 855 01:31:44,000 --> 01:31:47,500 let's just say I want to hire you to be 856 01:31:47,500 --> 01:31:50,250 an LAM for something is that is that is 857 01:31:50,250 --> 01:31:52,166 that a possibility? Are you? Yeah, of 858 01:31:52,166 --> 01:31:53,416 course, of course, you do custom stuff. 859 01:31:53,458 --> 01:31:57,583 I always do. That's all I do. So I full 860 01:31:57,583 --> 01:31:59,291 time, I'm a freelancer who just does 861 01:31:59,291 --> 01:32:02,666 custom stuff for for customers. I'll give 862 01:32:02,666 --> 01:32:04,375 you my bit.ly link at the end, because it 863 01:32:04,375 --> 01:32:06,250 goes to all these, these things, 864 01:32:06,250 --> 01:32:07,750 including how to get me a calendar 865 01:32:07,750 --> 01:32:09,041 invite. So you can just talk to me 866 01:32:09,041 --> 01:32:11,333 sometime. But yeah, if you ever need 867 01:32:11,333 --> 01:32:13,208 consulting, or more importantly, build 868 01:32:13,208 --> 01:32:15,916 something fun, I can help out. I mean, 869 01:32:15,916 --> 01:32:16,833 some of the stuff I don't want to talk 870 01:32:16,833 --> 01:32:18,291 about, because it's kind of NDA, but just 871 01:32:18,291 --> 01:32:19,875 the stuff you can do, it's just, it's 872 01:32:19,875 --> 01:32:21,166 just like with you and you're automating 873 01:32:21,166 --> 01:32:21,416 your workflows, like, 874 01:32:21,458 --> 01:32:24,833 you'll be amazed at what you do. It's 875 01:32:24,833 --> 01:32:26,458 cool you're using Zapier, I never think 876 01:32:26,458 --> 01:32:27,916 about them, because I'm too busy trying 877 01:32:27,916 --> 01:32:30,583 to make that thing. But I forget how easy 878 01:32:30,583 --> 01:32:32,041 it can be if I would just stop being so 879 01:32:32,041 --> 01:32:34,875 stubborn, you know, well, I mean, it has 880 01:32:34,875 --> 01:32:36,791 its benefits. But it's also very 881 01:32:36,791 --> 01:32:38,291 expensive to run. It's it's 882 01:32:38,291 --> 01:32:38,416 not good. Good point. Yeah. 883 01:32:38,458 --> 01:32:39,458 Because now they charge you by the like, you get so many tasks, tasks run by month or something in the way it works is every link we approve goes out to, you know, for social services or, you know, five, it goes out everywhere. And then, and then we publish posts that goes out everywhere. So it's like, we're running tons of tasks. And it's all like, yeah, probably 1000s of months, I guess, is pushing all that stuff out. But well, we should look at 884 01:33:08,458 --> 01:33:10,000 we'll look at lara llama together, I'll 885 01:33:10,000 --> 01:33:11,666 show you my hosted versions, my training 886 01:33:11,666 --> 01:33:13,916 version, and then we can just see what 887 01:33:13,916 --> 01:33:16,000 can I do? What could it do? And then 888 01:33:16,000 --> 01:33:17,500 maybe we can play around. Because in the 889 01:33:17,500 --> 01:33:19,916 end, I love these real use cases, right? 890 01:33:19,916 --> 01:33:22,541 This is how products succeed is they have 891 01:33:22,541 --> 01:33:23,958 real use. I think that's why Laravel 892 01:33:23,958 --> 01:33:25,500 succeeded. It wasn't trying to solve 893 01:33:25,500 --> 01:33:28,583 imaginary problems. It was a SAS focused, 894 01:33:28,583 --> 01:33:31,458 like product from the start, you know, it 895 01:33:31,458 --> 01:33:33,750 was solving real problems that, you know, 896 01:33:33,750 --> 01:33:35,375 paid off. So like with you, if you want 897 01:33:35,375 --> 01:33:37,708 to talk about it, we can just, you know, 898 01:33:37,708 --> 01:33:38,416 I'll show you around. 899 01:33:38,458 --> 01:33:40,125 And show you it hosted and show you all 900 01:33:40,125 --> 01:33:41,458 that. And then you can see what can you 901 01:33:41,458 --> 01:33:43,208 do now? And what could it do easily? If 902 01:33:43,208 --> 01:33:43,916 you just think about 903 01:33:43,916 --> 01:33:45,000 it? Yeah, so it'd be fun. 904 01:33:45,625 --> 01:33:46,875 I love that. Yeah, that's a that's a 905 01:33:46,875 --> 01:33:49,666 wonderful idea. Yeah, yeah. Yeah, we'll 906 01:33:49,666 --> 01:33:51,000 definitely have to get that scheduled. 907 01:33:51,333 --> 01:33:54,916 Um, so sort of to wrap up the call. 908 01:33:55,666 --> 01:33:57,541 Anything else I missed that you know, 909 01:33:57,541 --> 01:33:59,791 might be you'd like the 910 01:33:59,791 --> 01:34:01,083 community to know or anything? 911 01:34:01,125 --> 01:34:04,791 Right. I mean, I will start a place to 912 01:34:04,791 --> 01:34:07,625 talk more about this. But I guess the 913 01:34:07,625 --> 01:34:09,291 only thing I just keep saying or 914 01:34:09,291 --> 01:34:11,625 hopefully showed in this or explain this 915 01:34:11,625 --> 01:34:14,041 like it like it, there is hype and the 916 01:34:14,041 --> 01:34:15,666 hypes gonna fade because hype fades, I 917 01:34:15,666 --> 01:34:16,791 think it's what it has to be hyped to 918 01:34:16,791 --> 01:34:19,416 fade. So, but I think in the end, this is 919 01:34:19,416 --> 01:34:21,458 a real this is a new tool that we can use 920 01:34:21,458 --> 01:34:23,666 today to do some cool stuff for our 921 01:34:23,666 --> 01:34:24,666 clients and for ourselves. 922 01:34:25,416 --> 01:34:28,458 Like, like a total home project I can do 923 01:34:28,458 --> 01:34:31,250 now. There's so many of them. But like, 924 01:34:31,250 --> 01:34:33,041 like, just a side note, like just how 925 01:34:33,041 --> 01:34:34,208 cool this is, like now you're a 926 01:34:34,208 --> 01:34:35,208 developer, you're thinking you're 927 01:34:35,208 --> 01:34:37,125 tinkering, you want to do things. Like no 928 01:34:37,125 --> 01:34:40,416 one ever in my household says, hey, we 929 01:34:40,416 --> 01:34:43,000 ran out of oatmeal order some more empty 930 01:34:43,000 --> 01:34:44,708 box, they don't even take the box down. 931 01:34:44,708 --> 01:34:45,875 It's empty. But just say they took the 932 01:34:45,875 --> 01:34:47,708 box down, threw it away. And then 933 01:34:47,708 --> 01:34:49,041 tomorrow, they're like, hey, there's no 934 01:34:49,041 --> 01:34:51,000 more. I'm like, yeah, you ate it all. No 935 01:34:51,000 --> 01:34:53,375 one told me to buy more. Right. So, so 936 01:34:53,375 --> 01:34:55,000 like, what I did was I put on a 937 01:34:55,041 --> 01:34:56,541 I haven't finished this yet. This is just 938 01:34:56,541 --> 01:34:58,791 an idea. I have this top row of all the 939 01:34:58,791 --> 01:35:00,875 backup food. This is our when this is 940 01:35:00,875 --> 01:35:02,666 gone, I have to order more. And now you 941 01:35:02,666 --> 01:35:04,625 take a stupid little camera on a 942 01:35:04,625 --> 01:35:06,208 Raspberry Pi, and you point to that and 943 01:35:06,208 --> 01:35:08,958 take a photo. Or every time motion 944 01:35:08,958 --> 01:35:10,750 happens, and the LM could say, Oh, 945 01:35:11,208 --> 01:35:13,083 oatmeal is missing. I'm going to now 946 01:35:13,083 --> 01:35:15,083 order more. Because it happens to be 947 01:35:15,083 --> 01:35:16,666 right next to Alexa. And it can say, 948 01:35:16,666 --> 01:35:18,958 Alexa, order more oatmeal, like, you 949 01:35:18,958 --> 01:35:21,666 know, the fun stuff we can do at this 950 01:35:21,666 --> 01:35:23,291 next level for for just 951 01:35:23,291 --> 01:35:25,000 messing around. It just it's kind 952 01:35:25,000 --> 01:35:26,958 of cool. So I would just say, like, just 953 01:35:26,958 --> 01:35:29,083 see this stuff is like, it can help do 954 01:35:29,083 --> 01:35:30,125 some really cool stuff we couldn't 955 01:35:30,125 --> 01:35:33,500 imagine before. You know, yeah, that's 956 01:35:33,500 --> 01:35:35,166 such an awesome use case. Because every, 957 01:35:35,416 --> 01:35:37,291 every week when we go to order groceries, 958 01:35:37,583 --> 01:35:38,916 always like, what do you want? I'm like, 959 01:35:38,916 --> 01:35:41,125 I don't know, just normal stuff. And then 960 01:35:41,125 --> 01:35:42,333 she's like, Well, what is that? Like, I 961 01:35:42,333 --> 01:35:46,666 don't know. Like, look, I now made this 962 01:35:46,666 --> 01:35:48,750 project, one of mine's a meal assistant. 963 01:35:48,750 --> 01:35:50,583 So it's a meal planner, we send our 964 01:35:50,583 --> 01:35:52,458 recipes, we tell it we like, and every 965 01:35:52,458 --> 01:35:53,416 week, it can build up a 966 01:35:53,416 --> 01:35:55,000 plan. It can send us a memo, 967 01:35:55,000 --> 01:35:56,333 email saying this is your shopping list 968 01:35:56,333 --> 01:35:58,833 for this week. And then every week, it 969 01:35:58,833 --> 01:36:00,958 does another plan, hopefully not 970 01:36:00,958 --> 01:36:02,166 repeating everything. Because that's what 971 01:36:02,166 --> 01:36:03,625 I always do. I'm like, let's have this we 972 01:36:03,625 --> 01:36:06,625 had that last week. Okay, like, so it's 973 01:36:06,625 --> 01:36:08,000 just fun stuff. I know there's so many 974 01:36:08,000 --> 01:36:09,291 other ways to solve these problems. But 975 01:36:09,291 --> 01:36:12,041 to me, it's just kind of fun to use these 976 01:36:12,041 --> 01:36:14,666 tools like that. So I love that. Yeah. 977 01:36:15,125 --> 01:36:16,625 But my family's the same way. It's like, 978 01:36:16,625 --> 01:36:20,250 we have four staple dinners. That's every 979 01:36:20,250 --> 01:36:21,791 week. It's like what day do you want? 980 01:36:22,166 --> 01:36:23,791 Yeah, what day do you want tacos? What 981 01:36:23,791 --> 01:36:24,416 day do you want spaghetti? 982 01:36:25,000 --> 01:36:29,208 That's funny. It's funny how we we all 983 01:36:29,208 --> 01:36:31,166 have sort of the same shared problems 984 01:36:31,166 --> 01:36:34,958 across. Yeah. Yeah. Yeah. And so they're 985 01:36:34,958 --> 01:36:37,416 fun to solve and do this creative stuff 986 01:36:37,416 --> 01:36:39,833 to just kind of add a whatever a twist to 987 01:36:39,833 --> 01:36:42,041 it. So, so yeah, that's the that's the 988 01:36:42,041 --> 01:36:43,666 point I want to get across is it really 989 01:36:43,666 --> 01:36:45,333 is here, I think, for good and it can do 990 01:36:45,333 --> 01:36:47,375 some things now that are, are fun and 991 01:36:47,375 --> 01:36:50,791 practical. So yeah, that's amazing. I 992 01:36:50,791 --> 01:36:52,333 love this. Yeah, yeah, yeah, you're gonna 993 01:36:52,333 --> 01:36:53,750 have to Yeah, you have to do more videos 994 01:36:53,750 --> 01:36:55,000 on on you making all this 995 01:36:55,000 --> 01:36:58,250 stuff, you know. Yeah, I know. I know. I 996 01:36:58,250 --> 01:37:00,458 try. I got lighting and everything. I 997 01:37:00,458 --> 01:37:01,833 just got to do it. I don't know what 998 01:37:01,833 --> 01:37:05,458 happens. But then we'll talk. We'll talk 999 01:37:05,458 --> 01:37:06,916 soon as well, because it'd be fun to 1000 01:37:06,916 --> 01:37:08,958 watch your process and see what can be 1001 01:37:08,958 --> 01:37:12,833 done there. So for sure. Yes. And, and 1002 01:37:12,833 --> 01:37:15,583 yeah, that's, but yeah, I want to, I 1003 01:37:15,583 --> 01:37:16,916 think we'll wrap it up here because I 1004 01:37:16,916 --> 01:37:18,125 feel like I can talk to you all day about 1005 01:37:18,125 --> 01:37:20,250 this stuff. And I know the listeners want 1006 01:37:20,250 --> 01:37:23,375 to keep it tight. So, but, you know, I 1007 01:37:23,375 --> 01:37:23,916 want to, I want to thank 1008 01:37:23,916 --> 01:37:24,958 Alfred for coming on the show. 1009 01:37:25,000 --> 01:37:27,750 You know, I've learned so much today and 1010 01:37:27,750 --> 01:37:30,250 really enjoy like finding these new 1011 01:37:30,250 --> 01:37:32,083 packages and these new things within the, 1012 01:37:32,083 --> 01:37:33,666 within the literal community and PHP 1013 01:37:33,666 --> 01:37:36,750 community. It's awesome. You know, all 1014 01:37:36,750 --> 01:37:38,125 these links will be in the show notes. 1015 01:37:38,416 --> 01:37:41,166 Alfred will, he does consulting and he's 1016 01:37:41,166 --> 01:37:42,541 got a book for sale. So you need to go 1017 01:37:42,541 --> 01:37:45,000 and check out all of that too. If you, 1018 01:37:45,000 --> 01:37:46,000 you know, if you're having ideas on this 1019 01:37:46,000 --> 01:37:47,750 stuff that your company needs that, you 1020 01:37:47,750 --> 01:37:49,375 know, maybe you're, you don't want or 1021 01:37:49,375 --> 01:37:50,833 don't have the time to implement yourself 1022 01:37:50,833 --> 01:37:53,041 and would prefer a professional to do it. 1023 01:37:55,000 --> 01:37:57,833 Thanks for joining us. Until next time. 1024 01:37:58,500 --> 01:37:59,250 Cool. Cool. Thank you.