Welcome to Practical AI, the podcast that makes artificial intelligence practical, productive and accessible to all. If you like this show, you will love the changelog, it's news on Mondays, deep technical interviews on Wednesdays, and on Fridays, an awesome talk show where you're a weekend enjoyment. Find us by searching for the changelog wherever you get your podcasts. Thanks to our partners at fly.io, launch your AI apps in five minutes or less, learn how at fly.io.
Welcome to another fully connected episode of the Practical AI podcast. In these fully connected episodes, Chris and I keep you updated with everything that's happening in the AI world, if we can. There's a lot, and we try to give you some learning resources to level up your machine learning and AI game. I'm Daniel Whitenack, I'm CEO at Prediction Guard, and I'm joined as always by my co-host, Chris Benson, who is a principal AI research engineer at Lockheed Martin.
How are you doing, Chris? I'm doing great. I just don't know what we're going to talk about because there's nothing ever happening. There's nothing happening.
There's never anything going on has done nothing. Oh my gosh, Elon is throwing spit wads at people again. He's been suing open AI and now he's put his bid out in the last few days. For open AI, the article that I saw was, we are not for sale chat, GPT bosses.
I know, good old Sam, Sam said we're not for sale because the two of them really love each other. Oh yeah, definitely. Elon Musk and Sam Altman, they are best friends. Best friends.
That's how we'll report it here. That's how we're reporting here because we always look for the upside of the AI world here. Yeah, who knows the motivations behind billionaires? It's an interesting thing to watch.
It certainly spices up conversations in the work day and is a nice point of discussion with friends. That's about how I'm taking it. Yes, I would agree with that. The spats between billionaires just doesn't quite make it to my, not being a billionaire myself, it doesn't quite make it onto my list of concerns.
Yeah, what do you think is the trajectory with players like OpenAI? Someone was, well, the other thing that happened in the US was this fits into maybe the other thing I was going to ask as well, although I got sidetracked in my mind because I remember that there was a Super Bowl and there was a Super Bowl commercial that OpenAI had, which it was a cool commercial. I didn't know what it was going to be at first because it's just the artistic dots around forming scenes. And then I think I gradually realized that this is those little dots on the OpenAI chat GPT app that expand and cool ad.
Someone commented to me, they spent like $14 million or whatever a Super Bowl ad cost. I forget how much it was. But I was like, that's really nothing compared to what OpenAI is losing generally on hosting models and infrastructure. So yeah, that's what circles back to my other question, which was, yeah, what are your thoughts on, I mean, if Elon doesn't buy OpenAI, what's the future?
I honestly don't know. And I got to be honest with you. I'm not sure that I care a whole lot. I was thinking about that as we were leading into this, is that, you know, I mean, there's not a protagonist here from my standpoint.
There's not a side, there's not a side that I'm for or against so much. You know, you have Elon with all the, you know, the adventure around Elon Musk. And I say that word kind of tongue in cheek. And then OpenAI and, you know, there is a kernel of truth to what Elon says when he talks about it being, you know, going from being the nonprofit with the grand vision that it started out with in the early days, and then it has increasingly gone commercial and become for profit.
You know, so it's another big, it's another big giant AI company, you know, like the others and stuff. So I'm watching it with half an eye, like everybody else in the world, but not sure. I just don't know. And I'm not terribly sure I care.
Yeah. Is there somebody out there in our audience that is deeply concerned about this? I would love to I would love to hear somebody who is not Elon or Sam Altman. Tell me why this is a big deal.
Yeah, maybe we'll leave it at that. It's a good point. I am interested in, you know, some of the dynamics like OpenAI released their deep research product. So if you kind of look at the trajectory of what they're releasing, what they're doing, there's this deep research product, which is really geared towards this, you know, multi step online information research type of task.
Yeah. So, you know, going and looking at various, you know, trends across various sites with various data, reasoning, certain information, consolidating that, you know, contributing to some sort of research project. And I find it interesting that, you know, OpenAI introduces one of the dynamics I love watching is OpenAI releases the application level products are like deep research. And then so I see the blog post by hugging face.
It was it was like the day after. So they say yesterday, opening I released deep research. So this is a blog post that I'll link in the in the show notes from hugging face. And basically, they they just decided to make sure that they could reproduce the functionality with open source code.
Maybe some recently released models like deep seek models or others in 24 hours. And then they wrote the blog post and released it. I don't know how long of a 24 hours it was, but you know, you see that dynamic happening. So you see that with deep research.
And then you have, you know, the open deep research thing, you see kind of the operator stuff where it's operating your, your screen, your browser window. Now earlier today, I was running hugging face small agents. They have a web agent, which is essentially that spins up a browser window. It does certain tasks for you in the browser window.
Like it, you can type a prompt like, hey, find the most recent episode of practical AI, summarize the topic, and then find, you know, seven other articles of a related topic, list them out in markdown format and, you know, output that, you know, something like that, where it requires this sort of agent operating over the internet, super slick, super fun. I would definitely recommend people if they, if they want to try that sort of thing, try the, try the small agents web agent. But yeah, you see this kind of trend where at the application level, some of this is just, you know, it seems like you can't develop a moat generally there. Now you might be able to develop a kind of moat as a company in a specific domain or a vertical or with certain knowledge or proprietary data, right?
But it's very hard at that kind of general, general application level, I would say. I think, you know, I keep wondering, as, you know, OpenAI had had a substantial lead, and it was taking quite a period of time for a while for open source options and application, you know, level of things to come about. And we've seen that, the, you know, that time interval shrink tremendously here. So, you know, and ironically, at the same time that Elon makes his $97 billion effort to buy open AI, but you can't help but wonder a little bit about what the future business model looks like, you know, to your point there about, you know, if it takes so, you never have time to create a moat, you know, if you're one of the main players.
Now, you can, you know, there's, there's certainly business models for other players to come in their industry, as you just mentioned, and create capability because that's their thing, and it's not something that the big boys are going to go after. But as we've seen this interval between the commercial players and open source shrink, almost nothing. How does that, what do you think that means for the business models going forward for the Googles and the open AIs and the end bropics of the world? I mean, I think part of part of it is maybe this sort of integration in the kind of enterprise stack into, and what I mean by that is, is the kind of bundle effect that you get from something like offerings from Microsoft.
So, you know, absolutely known in the world wants to use teams because it's absolutely terrible. And I will go on record as saying that. Sorry for those that work on it. I have to use it.
I have no choice. I guess, you know, you have a podcast, you have an opinion, but that's my opinion. But, you know, I'm also not going to pay hundreds of thousands of dollars to Slack if I can just flip on teams in, you know, in my Microsoft tenant and they already have all my data and all this stuff. So, the fact that they're tying in, you know, co-pilot and those licenses around co-pilot in an ecosystem that's already so embedded in the enterprise world, there is a very strong bundle effect there.
And yeah, it's very real, right? And it doesn't mean that it's necessarily the best solution, but it is a solution depending on what you're looking for, right? At that kind of generic co-pilot level, in a case where you have, you need kind of single tenant meaning in theory, the terms and service are, my data is not being used in certain ways. That kind of gets that generic case.
But again, like the real business value that a company has, the way I see it is, you've kind of got these generic cases where someone random going to want to find a word document or paste in an email, then you've got like the core business value, right? So, a pharma company that has their most sensitive tiers of data that are the, you know, lifeblood of their company or a healthcare company or a finance company that has certain classifications or regulatory burdens around certain tiers of data. It's a whole other thing to think about integration of those tiers of data into a generic system like that, because they're not, you know, they're a generic co-pilot system for those kind of less sensitive tiers of data. There's still something that needs to be solved at those other layers, which is where I think, you know, vertical AI players, but also, you know, tooling and infrastructure players can still make, you know, a lot of progress.
Do you think that the bundling that you're describing that's, you know, occurring between the vertical capabilities where they're producing these and, you know, an open AI going and doing deep research or Google integrating Gemini into, you know, the Google suite, which they've been doing and trying to drive a premium, you know, from users for that, is that bundling going to be critical to them going forward? Or do you think that the open AI's of the world and, you know, and we've seen this historically with Google, maybe not in an AI context always, but driving into specialties where they, you know, they open up a new vertical underneath the umbrella and stuff. You know, it's open AI going to have to do that to survive, since it's going to have open source chomping and it seals down the general path? Yeah, I don't know.
It could be by vertical. It could be, I mean, you look at Palantir, for example, you know, stock price soaring. Most regular people aren't using a Palantir co-pilot, right, in their day to day, but they have that a certain market, particularly around, you know, DoD or defense or other areas. They have really put a lot into serving that well with the less generic, but still fairly generic across different use cases set of functionalities and that, you know, has served them well, at least from an outsider's perspective, if I'm, if I'm looking at that.
So it may be a specialization in terms of tools or vertical. It might also just be a segment of the market that you choose to, to focus on and is kind of the bread and butter. It's interesting because you've got all of these really end users direct to consumer traffic on open AI and these things now where a lot of what we had talked about before with data science and AI and machine learning was really enterprise focused, not direct to consumer. So let me throw one other layer onto this conversation.
As we circle back around AGI ideas with, you know, kind of have an artificial generalized intelligence being bantured about Sam Altman was just saying that he was expecting GPT-5 to be smarter than he was. And so as we look at that, you know, I think GPT-3 is smarter than I am. Me too, I agree with you. But, but with that, you know, with us, with that, the AGI chase continuing at this point.
And, you know, we've heard, you know, with DeepSeek and all these others going in and talking about business models and bundling and such and exploring new verticals, how do you think that the AGI race fits into that? Yeah. Maybe that's the piece that in my mind, I'm not, isn't really entering into my mind much in the same way that you don't think about Elon so much, which is probably good. Yeah.
I think it's an interesting question. And there's implications, the questions that come into my mind at a more general level, which is what you could talk about it as AGI or not, I don't know. But the questions that come into my mind are more the downstream effects of some of these things. Are we building systems that enhance human agency rather than replace it?
Are we building systems that allow us to trust more in human institutions or fear and distrust them more? Are we, you know, are we building systems that actually drive us more into isolation as individuals or into community together? I think those are interesting kind of directions that are on my mind as I think about the more general side of this. Well, there's no shortage of AI tools out there, but I'm loving Notion and I'm loving Notion AI.
I use Notion every day. I love Notion. It helps me organize so much for myself and for others. I can make my own operating systems, my own, you know, processes and flows and things like that to just make it easy to do, checklists, flows, etc that are very complex and share those with my team and others externally from our organization.
And Notion AI on top of it is just, wow, it's so cool. I can search all of my stuff in Notion, all of my docs, all of my things, all of my workflows, my projects, my workspaces. It's really astounding what they've done with Notion AI. And if you're new to Notion, Notion is your one place to connect your teams, your tools, your knowledge, so that you're all empowered to do your most meaningful work.
And unlike other specialized tools or legacy suites that have you bouncing from six different apps, Notion seamlessly integrates it's infinitely flexible. And it's also very beautiful and easy to use mobile, desktop, web, shareable. It's just all there. And the fully integrated Notion AI helps me and will help you to work faster, write better, think bigger, and do task that normally take you hours to do it in minutes or even seconds.
You can see a time by writing faster, by letting Notion AI hang left first draft and give you some ideas to jumpstart a brainstorm or to turn your messy notes. I know my notes are sometimes messy. And if something polished, you can even automate TS tasks like summarizing me notes or finding your next steps to do, Notion AI does all this and more, and it frees you up to do the deep work you want to do. The work that really matters, the work that is really profitable for you and your company.
And of course, Notion is used by over half of Fortune 500 companies and teams that use Notion send less email, they cancel more meetings, they save time searching for their work and reduce spending on tools, which kind of helps everyone be on the same page. Try Notion today for free when you go to Notion.com slash Practical AI, that's all our case letters, Notion.com slash Practical AI, that try the powerful, easy to use Notion AI today. And when you use our link, of course, you are supporting the show and we love that Notion.com slash Practical AI. Well, Chris, we talked a little bit about tools and agents, well, agents generally, the web agents, the deep research things.
And we've kind of talked about tool calling and the connection to agents at certain points on the show. But I don't think we've really dug into the detail in a way that maybe will make things clear for people. I still see a lot of confusion around this. Even in my day to day, as I'm talking to customers, the question of, well, how do I make an LLM talk to this system?
Or how do I, that deep research tool? How do I make an LLM, go and do a thing? That's often how the question comes. And what I think I realize when I'm hearing those questions is there's kind of a fundamental misunderstanding of what the LLM does and how it's tied into a framework, which you might call tool calling, you might call agent, the names kind of get mushed around a lot these days, unfortunately, they do.
I was thinking that as you were saying all that, and then you got that's literally what was in my head in terms of the misuse of different names of the technologies and what's what's doing what. So yeah, yeah, exactly. So in my mind, so this is, I'm feeling very opinionated today. I don't know why for it.
Excellent. In my mind, how I kind of draw the lines here, there's, you know, of course models, large language models, they predict probable text, they generate, they generate text or images or whatever you want them to generate, then there's other systems kind of over on the other side. So you could think of, you know, your email or your bank account or an external system, like an Airbnb where I might want to make a reservation or my company's database, right, which contains transactional data or another system that I use like HubSpot or all of these types of things or all of these other things. And to ask a question, well, how could I, how could an LLM go and create a new deal for me in HubSpot, right?
That hurts me when, when you phrase it like that, it causes pain in my head. Okay. But that's how, that's how people phrase it to be clear. Like, you know, these questions are the questions that come up every day, right?
So how the question is often phrased, how do I make the LLM create a new deal for me in HubSpot? So right in that phrasing, to your point, I don't know what makes you cringe about that. It's just, that's a fingernails on the chalkboard kind of moment for me is, you know, to answer that question in the six and a half years that we've been doing the show. And we have evolved through a number of technologies, you know, that at each point in time, we're the hot thing.
And inevitably, people focus in on just that for a while. But right now, we're at a point where generative and LLM, the last few years have been the hot thing. And we forget that they don't necessarily do everything out there. It's not, you know, people will say LLM.
In fact, they only do one thing. That's exactly right. And not only that, but there might be an AI architecture that does, they could do the thing that they want to talk about, but it's not necessarily the thing that they're talking about. And they're mislabeling.
It's not the model. It's not the model. And so that's the fingers on the chalkboard of, wait, there's, we've kind of talked about this over the last year, the tunnel vision of the generative AI era, you know, in terms of everyone focusing on that. But it's to the point that there are other technologies in the mix, and there is a technology that will do the thing they want to do.
They're just not picking the right one in the way that they're verbalizing it. So yeah, yeah. So let's, let's maybe break this down into components. So let's say there's the LLM, you know, we'll just talk about text now.
Certainly, there's multimodal and all that stuff. But just think about text. There's the LLM, which all it does is complete probable text. So I could, you know, ask it to auto complete, I could ask it to write something for me, I could ask it to generate something for me.
That's what it does, right? Then there's the system, let's say, we'll take the HubSpot example, since I use that HubSpot for those that aren't familiar, it's a popular CRM solution for those that maybe aren't, you know, don't want to mess with Salesforce and all of that world. So HubSpot, I can create a deal associated with maybe a sales lead I have, right? That is its own software system that's hosted by HubSpot, right?
And I actually, I don't know this, but I assume HubSpot has an API, a REST API, meaning you could programmatically interact with HubSpot. This is how apps on HubSpot work, right? An app on HubSpot is regular good old fashioned code that maybe allows you to add a field, add these fields to these records or retrieve this data or report on this data that's just good old fashioned code. It uses the API.
So this is a separate system. And so there's really no connection between, there can be no connection directly between the LLM, which generates text and this other system out there that's a CRM that does certain things, there's no connection between the two. Except in the middle of that, there can be this process which I would generally say, I would categorize as tool calling, generally, or function calling, which let's say that you wrote a good old fashioned software function that creates a deal in HubSpot via the REST API of HubSpot, right? That has nothing to do with AI.
It's just a software function where you tell me the email of the person, the name, the company, I'm going to go in and create the deal in HubSpot via the API. So there's a function, you give me these arguments, I'm going to create the deal in HubSpot. Okay, still no connection to the LLM, but if I then ask the LLM to say, hey, I have this customer information, email name, et cetera, generate the arguments for me to call this function, which takes these specific arguments, then the LLM could generate the necessary arguments to call that function. And if you create a link between the function and the output of the LLM, so the LLM is still not really doing anything other than generating text, but in your code, you literally take the output of the LLM and you put it into the input of that function.
Now, you could put something on the front end into the LLM and have the result be a flow of data out of the LLM into the function and then into the HubSpot API. So that's sort of how this tool calling function calling thing works, which makes perfect sense. And that's standard software development, you know, that's the only thing that is different there is the fact that the function parameters that you're using have been generated by the LLM, which is a generative model, perfect, that's what it does. And there are some special things related to this in the sense that, you know, if you look back in time at LLMs, first we had kind of really good auto complete models because that was a meta task for people, you know, training language models.
Then people figured out, oh, I kind of want to use these as general instruction following models, right? And so they develop specific prompt formats and prompt data sets to fine tune LLMs for specifically instruction following, right? So here's your system message, here's the message I'm providing you give me the assistant response, and they trained it on a bunch of general instruction following things. Well, they've done the same thing now because they've realized, oh, a lot of people want to do this tool or function calling mechanism.
So certain people, including open AI in a closed sense, but others in an open sense, like new research we had on the show, they have a data set called Hermes. This includes a set of prompts that is that are related to function calling specifically. So they've given a huge number of examples of function calling prompts to a model that they would train like a llama model. And now you have Hermes llama 3170b.
It's been fine tuned to follow that Hermes style prompt format for function calling, which means it kind of has an advantage if you like, or certain models that have been trained with these examples have an advantage specifically for that function calling task, right? So there is an AI element in the sense that some models are better at this than others because of the way that they've been trained. And there's certain prompt formats that are special, and you'll get better performance if you use those prompt formats, or if you use a model server like the LLM that supports or has the inbuilt translation to those prompt formats, etc. So there is an AI element of it, but it's only in the sense that you're preparing the model for this type of use case, rather than connecting, there's some inbuilt connection of the model to something external.
So I'm curious, can you tie in the tool calling into what might be considered a full, you know, agentic implementation? What's the leap there of any? Yeah, interesting question, because people use the term agent very loosely. So some people would say what I just described, even just that chain of processing, so I put something in the front end of the LLM, deal is created in HubSpot that might be considered an agent, my HubSpot deal creation agent.
I would say that's really just a tool calling example of how to use an LLM. In my mind, what separates out the agentic side of things is where you have some sort of orchestration performed by the LLM. So what I mean by that is you have a set of tools. So let's say I have access to Airbnb's API and Kayaks API and United Airlines API or whatever other travel things I need to do, maybe my Gmail for various things.
And I say, hey, I need to book a car next week for my trip to wherever, right? That input could then be processed through the LLM, not to call a single tool, but first as an objective to determine what tools to call and in what sequence, with what dependencies. Try to do a first step of that and then reevaluate and then do the next step until you reach the objective. So first in order to book my thing, I need to know what my flight is.
So I go to my Gmail and I look for the confirmation. Or second, I use that date in the Kayak API to look for choices. And then I evaluate those choices and then I use it to book the reservation. So there's a series of steps that might call different tools or systems.
It could be data sources, unstructured or structured data sources like a database or a RAG system. And so that thing that I talked about like that HubSpot deal creation tool might be one of those tools in an agent system where an agent could choose to use it at certain points. And I'm being anthropomorphizing here. It's not choosing anything, right?
But it's useful to talk about it sometimes in that way. So forgive me. It's choosing to use that tool in one case and maybe other tools in other sequences in other cases. In my mind, that's what really distinguishes the agent side from just the tool calling side.
Well, Chris, it's fun to talk about some of the agents thing. Normally we wait till the end of the episode to share some learning resources. But since we've been talking about tool calling and agents, I just wanted to mention this new course by hugging face. So they now have an agents course, which I think was just released and is coming out live on YouTube, if I understand correctly.
And so in the course, they talk about studying AI agents and theory design and practice using established libraries like small agents, link chain, lama index, sharing your agents, evaluating your agents. And then at the end, you earn a nice certificate. So plug for the hugging face agents course. If those of you out there intrigued by some of the tool calling and agent stuff, it seems like a good one.
Yeah, as we record this, they're actually doing it in about an hour and 20 minutes from right now as we record the ship. It'll be passed by the time you're listening. If you're listening, you missed it. You missed it.
Sorry, you're going to play replay. Yeah, but you can do the replay. And it's interesting. One of the packages there that they mentioned is called small agents, which is really great.
I love using that package. It's a lot of fun. And I've even used it in a couple of really interesting internal use cases at Prediction Guard. So do me a favor here, depending on if so long as there's no secret sauce, moments there for Prediction Guard, can you can you plan a couple of seeds on things that you've done, that people could explore in terms of what you found useful and hey, I did this thing and just kind of let people get a sense of how you're looking at it and what things they might be able to do so that they can ID you on their own.
Yeah, definitely. So I'll speak somewhat generically here. So I don't reveal certain things, but customer things. But one of the cases that we actually experience fairly often with customers is they want to build, you know, maybe it's they want to build a chatbot that has access to some or has access to some special knowledge or can access special knowledge in one way.
So on the one hand, if you have a bunch of unstructured text, right, that's a typical case where you would use a rag workflow and you would put that into a vector database, you can retrieve it on the fly. That's a rag chatbot. On the other side, there are text to SQL methods, for example, or, you know, API calling methods that could allow you to interact with your database, right? So there's those methods.
Sometimes though you have a source of data and there's been a couple of times where it's maybe a web app that doesn't have a really convenient API, but has a really complicated and annoying user interface. And the company has this web app that has a bunch of knowledge in it, right? But there's really no good way to extract all of that content from the web app. It has an annoying interface, so no one wants to use it, right?
And so something like the small agent's web agent, like a system like that. And what the web agent does is it executes a series of tool calls that leverage helium under the hood, which is a package that allows you to automate interactions with a browser. And so if it's a web app, it can basically spin up the application in the browser and then interact with certain elements, like search for a certain thing or find a certain component or an object, summarize that output and output it from the web agent. So one of the interesting cases where we're thinking about that is, is these cases where a company has invested a lot of money in some system or application that's maybe a legacy system that they have to keep on using, right?
But no one really wants to engage it with it because the UI sucks, but it also doesn't have a really nice API or way to access the data in there. So actually using an agent as a kind of extra user that you can control programmatically to interact with the application is really, really an intriguing kind of prospect to tie in that knowledge and extract things from the app. The other one that I think comes up a lot for us because we work, you know, we work in a lot of regulated security privacy context, that's kind of what we do is prediction guard and deploying secure infrastructure for AI and people's companies. Often people will want to once they now have a private secure system tie in their transactional databases to to their queries, right?
And that's often a text to SQL type of operation where you're querying a database, you're generating a SQL query that can be error prone, right? Like you can generate SQL queries that don't execute or potentially problematic SQL queries or ones that are very computationally expensive. And so you can tie in other elements, agent elements into that where you kind of try to answer the question iteratively with different SQL queries until you reach an objective having the agent that's this is kind of an agent take way to go about the text to SQL, or you could tie in other tools like SQL query optimizers and that sort of thing to help in that process as well. So on more on the enterprise kind of business side, those are a couple things that have come up for us.
No, that sounds interesting. It's, I'm just kind of curious what you're thinking is, as how does this change the human side of the workflow as you've seen, you know, in recognizing these are some small use cases and everything. But you know, this is the beginning of the agentic wave as we go forward. And I guess, especially prompted with the kinds of things that we're seeing in the news these days, you know, about evaluation of, of government departments and just that general, that general notion of reassessment for better or for worse.
How do you think that that's going to, you know, be taken into, into commercial spaces in terms of deploying these agents will it change jobs significantly? Do you think or do you think it will just be adding in without that kind of, I'm kind of curious what your landscape is? Yeah, I mean, I think there will be a shifting of jobs. I think some of the things that we've talked about specifically in those examples are actually good examples of expanded human agency because a lot of times people don't do certain tasks or can't do certain tasks that they would like to do as a part of their job because of limitations of, you know, really complicated UIs or that this, you know, doing this and then this and then that will take me a ton of time.
And I've got to jump to this meeting, right? And so I think there's a lot of those things where that is expanded human agency of that. And so it's amplifying the effect of that worker and helping them feel like they have superpowers because they really didn't want to log into that application and use it one more time, right? So I think there's an element of that.
Now you could make the argument, well, maybe they've hired three people under them because of those inefficiencies to do some of those tasks, which in some ways is a shame because if they're really just grunts, you know, cranking through extraction of data from horrible API or horrible user interfaces, like you could, I mean, maybe there's people that enjoy that all day. I think generally that's not a very dignified sort of way to go about it. Now, I'm realizing that I'm kind of making generalities here and there's the reality of people's work. Not everyone kind of gets to do the work that they, you know, they might desire to do or would give them most dignity.
So I want to recognize that. And I think there will be a, there will be a negative impact for portions. But I'm hopeful that there's also this positive impact. And even for people that are maybe in less skilled professions, if there's more of a natural language way to access skilled knowledge and kind of these amplifying effects of AI, it could hopefully open up new types of opportunities within the market as well.
So I would hope so. I mean, I think that's certainly, I think I suspect that we'll see all just as we do in life in every other aspect, we will see people enhancing human agency on that kind of to the use cases that you're talking about. And we'll probably see people with, you know, that would rather take alternative paths to that as well. I think it will be a mixture of the whole thing.
So yeah, yeah, as we kind of close out here, and I guess we're talking already about about new trends and other things. One thing I wanted to note is Deloitte just put out there in January, they put out the state of JNI in the enterprise quarter for report, which I've been going through for so for those maybe business leaders or managers or other people that are wanting to get a sense of some of the things that are being tracked across different industries in the enterprise. There's a great report there. I see, you know, for example, they are tracking barriers to developing and deploying JNI worries about complying with regulations, difficulty managing risks, they're tracking certain use cases, volume of experiments and POCs or proof of concepts, benefit, sought versus benefit achieved, which is an interesting one.
And also, JNI initiatives where they're most active within certain job functions, all these sorts of things and many more. So if you're interested in those sorts of insights, which I do think are interesting to track, then that's a great learning resource that we'll link in the show notes and hopefully people can find and prove if they're interested. Definitely. Well, Chris, it's been a great time.
I felt like I functioned well in my tooling as a podcast agent. So you did good. You did so good that who knows Elon Musk may be coming out of a prediction guard any day now. Or maybe what I'm saying is just being generated by Notebook LM.
That could be true. Okay. Good conversation today. All right.
Yeah. Thanks, Chris. Have a good one. You too.
All right. That is our show for this week. If you haven't checked out our changelog newsletter, head to changelog.com slash news. There you'll find 29 reasons.
Yes, 29 reasons why you should subscribe. I'll tell you reason number 17, you might actually start looking forward to Mondays. Sounds like somebody's got a case of the moondos. 28 more reasons are waiting for you at changelog.com slash news.
Thanks again to our partners at fly.io to breakmaster cylinder for the beats and to you for listening. That is all for now, but we'll talk to you again next time.