.jpeg)
Unresolved Dependencies
Welcome to the Unresolved Dependencies Podcast. A bi-weekly, unfiltered, not so serious catch up between two Microsoft Most Valuable Professionals, colleagues, community speakers, and - most importantly - good friends.
Join us on our fiscal year-based journey within the Microsoft ecosystem, AI, Events, Training, and Customer delivery
Unresolved Dependencies
#12 Can GitHub Copilot Save Copilot Studio? 👩🏼⚕️
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
HARNESSSSS - your new favourite buzzword in the agentic world we are trying to survive. But what is a harness? And what can GitHub Copilot do to save Copilot Studio?
Learn everything about the new Copilot Studio experience and what's different from the Standard Harnessssss. Do these changes make our licensing talk obsolete? What are the costs involved? And what is actually inside a Harnesssssss?
Find out in the new Episode of Unresolved Dependencies!
YouTube: https://www.youtube.com/@unresolveddependencies
Instagram: https://www.instagram.com/unresolveddependencies
Website: https://unresolveddependencies.buzzsprout.com/
Email us your Joe's Travel Guess: hello@unresolveddependencies.com
Connect with us on LinkedIn!
Joe: https://www.linkedin.com/in/joejgriffin/
Sebastian: https://www.linkedin.com/in/siebersebastian/
Podcast: https://www.linkedin.com/company/unresolved-dependencies
Links / Shout-Outs
LinkedIn Announcement / Video from Ryan Cunningham on the new harness experience
Microsoft Agentic Transformation Resources
Copilot Studio Licensing Guide
Overview of Microsoft Copilot Studio extension for Microsoft Visual Studio Code
God fuck you.
SPEAKER_00Joe, good morning. Joseph. Good morning, Joe. It's a new episode of Unresolved Dependencies. Wakey Wakey.
SPEAKER_01Okay.
SPEAKER_00No, it's it's it's better than a dream. It's Unresolved Dependencies.
SPEAKER_01Yeah, I'm sorry. I'm a bit I'm a bit tired today. Do you want to know why I'm tired?
SPEAKER_00Tell me, of course, why are you tired?
SPEAKER_01It is uh 7 a.m. UK time here, and I stupidly agreed to do training for a client in Australia time zone, which means I've had to be up at midnight and between 1 and 5 am in the morning. So I'm a little bit behind on my sleep. I need my sleep to function.
SPEAKER_00Um literally, you you you already have your working day behind you now. But you have a new UK working day in front of you.
SPEAKER_01This is the dilemma. Do I do I do I power on through or do I go straight back to bed after this? This is the this is the dilemma.
SPEAKER_00So it's my personal opinion as not as not as your help coach. I would say go to sleep.
SPEAKER_01I think I might do, but you know, the pop but the podcast has to continue. This is this is kind of mandatory, we have to do it.
SPEAKER_00So well, honestly, how are you doing?
SPEAKER_01How are you doing today anyway?
SPEAKER_00We're recording that early because you can't do it tomorrow, so so it's me.
SPEAKER_01Again, it's a me problem. It's always a me problem, you know.
SPEAKER_00So what are you doing tomorrow?
SPEAKER_01Ah, well, we'll find out in a few moments when we do a feature of Joe's travel.
SPEAKER_00You're traveling, right? I'm traveling.
SPEAKER_01I mean, it's a stupid question, of course. You just assume that I'm gonna be traveling, and you're probably gonna be correct, yeah.
SPEAKER_00So yes, right, so it's somewhat your fault.
SPEAKER_01Exactly, exactly. But yeah, speaking of Joe's travels, let's kick that off. Um, so yeah, last time we did um uh I guess again, we the inbox has been absolutely smashful with responses. Um, you know, people find this feature so popular. So if you were playing and you just you know didn't have the time to email in, you know, why not? You know, just email in. Um, the answer was uh Lubeck. I was in the lovely city of Lubeck. Um and uh it was for work, of course. Uh but a good but a shout out to Bjorn who gave me a great tip. He saw I was there, he said, okay, you need to go and check out the Marzipan. Lubeck is actually famous for Marzipan. So I stocked up on quite a bit of very tasty, lovely marzipan.
SPEAKER_00Are you a marzipan fan?
SPEAKER_01I like anything that's got you know chocolate, sugar in, you know. Maybe, maybe if I had some sugar now, I'd be I'd be like that would be a good start in the day, right?
SPEAKER_00Very looks healthy. But yeah, why why I'm surprised a British guy likes marzipan. So yeah.
SPEAKER_01Exactly. If it's got sugar in, I'm there probably. So yeah. So that was the answer from last time. So if you are interested in taking it getting involved, then you let us know on the email. Hello at Unresolved Dependencies.com. Let us know on the socials, we'll give you a nice little shout out. And there's also some vague promises eventually of some kind of uh merch. Uh so yeah, so as mentioned I'm traveling again, so where am I going to be next? The clue this time is I'm going to a city that is famous for a tea-related celebration, uh, and where a famous radio psychiatrist used to go to a bar where everyone knew his name. Where am I talking about?
SPEAKER_00So you didn't say pop, therefore, so a bar and tea and England does not go well together.
SPEAKER_01Yeah, you but you kind of get him beyond the right thought, beyond the on the right thought pattern, though. So, but yeah, but yeah, have a think yourself. Let us know uh in via email hello ohmsoredpenses.com. Uh, we'll be glad to hear from you, and yeah, we'll give you a nice little shout out. Why not?
SPEAKER_00Awesome. Yeah, I'm very curious where you're going.
SPEAKER_01Yeah, so it should be good. But you know what goes really well with um uh beverages at parties, food, particularly Sebastian's food, Sebastian's eats. So tell me Sebastian. What have you been eating? I I need to know what you're eating, it's essential information for me.
SPEAKER_00It's especially essential if you start your day and you want to just figure out what happens today and what do you want to eat.
SPEAKER_01Um, I'm on my last low needs of hierarchy. I'm sort of like sleep, food thing. Tell me what you're eating now. I need to know. Yes.
SPEAKER_00I'm paralyzed of decisions at this point. Exactly. Yeah, basically, so this time, um, basically it was curry. Uh, it was sorry, rice, chicken, curry, vegetables, and uh, it was made by my girlfriend, very, very nice of her. So the the only yeah, it was the only issue was that I didn't snap a picture for Instagram. So my my food blocking style or my fluke blocking skills kind of vanishing since uh it is uh much more summertime here. But yeah. I I I directly stuck my hat into it. No, but it was very nice. The the fun part is because I'm I'm um how to say it is nicely privileged asshole. I I had a chance as well to go to travel to India sometimes in the past, so I the curry was made with Indian curry, which was super spicy, and I'm not that spicy eater, but uh luckily my my late run to the nearest supermarket um saved us a little bit here because then we could as well um put on different spices because all the curry-related spices I had at home were like straight out of India. So instead of like um still burning and um uh getting flamed by the by the meat, it was very, very delicious, so very nice curry.
SPEAKER_01My best tip if you for spicy food, get some yogurt, some sort of normal plain white yogurt here, and that'll be that would sort it out in no time.
SPEAKER_00Quark. Speaking of quark, shootout to the best breakfast on the earth, which is quark, berries, and some oat oats and some milk. Best best breakfast on earth. Yeah, I don't argue about this. I'm eating this since 10 years every day.
SPEAKER_01Is that is that good food for like weight training? Would you say?
SPEAKER_00Yeah, so quark quark, so especially like the fat-free mark, uh fat-free quark, um, has some proteins, but also with the berries and so on, it's it's quite nice. Oats, anyways, is there small protein source and as well. Um, I don't know what the word is, it's ballaststoffer. So I um it it's good for your your diet in general, and um yeah, then you can just add whatever you like to. For example, I add some um whey protein powder just for the taste, so just a scoop of it, maybe one and a half, and for yourself, why not? You know, yeah. Well, well, well, actually, it just helps me to get to the proteins which I need to consume a day much more quicker and more free of choice during the day in terms of what I eat. Um, therefore, I I tend to have a very heavy protein meal in the morning, and then as well as well, like it's nice because it just saturates you for like half of the day, so you don't get any hunger randomly at 10:30 at a day. So super nice.
SPEAKER_01That's my problem. I think I eat it's my own, but it's again, it's my own fault. I eat too much carbs, and carbs then make you growly hungry. So, and my my stomach is very, very audible. I'll literally be sat there and it'll just be like making that growling. I mean, literally, literally, and I'm just I haven't say sorry, it's it's not my fault, it's my stomach. It is my stomach making that noise, just make that clear, first of all. So, yeah, it's it's definitely it's good to have something. I think porridge can be quite good in the morning just to give you that base. You need a base to make you last until like lunch or whatever.
SPEAKER_00So what is surprisingly not that good in the morning is sugar.
SPEAKER_01Yeah, that I ate too much, I ate too much sugar, you know. I need to, I need to, I I slightly I did quite well with a diet last year. I need to get back into more of a uh a nicer thing, but yeah, summer is always quite tricky with what's happening and things like that.
SPEAKER_00I find yeah, especially also with traveling, to be honest. Travel it traveling is for me like the the hardest part because on it so a lot of countries don't have quark at their hotel breakfast, for example, and I also don't want to rely on these like 50 grams of protein milkshake drinks you can buy in in supermarkets, for example, in the US. So it's not a big fan of that. But I also don't want to bring like my I don't know, my supplements to every place I go. So I that's always traveling is always a bit tough, so you need to be very keep attention on it, and then you often go for for dinner or something like that, and it destroys your whole diet very often. So that's like the hardest part for me because I'm I'm a I'm not a picky idiot. I I could eat like the same things like whole day, whole week, whole month. It's for me, this is like not a big problem. I literally eat the same breakfast since 10 years, and and I have not an issue with that.
SPEAKER_01I had a great tip from and yeah, well worth a follow on YouTube uh Damien Bird, just lots of really amazing content. So yeah, his trick is like the Huel Meal packs, you can sort of just you spoil it with some hot water, and then you get like a nice little curry thing. Um, and yeah, if you particularly if you're managing your diet and you know, um set off by things like you know, gluten or other things, which are you because you don't if you don't want to be that awkward person, like you know, around the dinner table, just like, yeah, can I is it is it gluten-free? Is it have you got the C that action? Have you got uh have you got have you got have you got a pesca pescatarian option?
SPEAKER_00You know, you don't want to be you know you you feel like you don't want to be that person sometimes, particularly just be the awkward person that brings us chicken and rice to like every occasion and just eat it from your tub box.
SPEAKER_01Yeah, I mean that's a it's everyone knows you're like oh it's a chicken and rice guy, chicken rice, chicken rice. Yep, there we go.
SPEAKER_00That's the dream, and then just eating from your bowl. Yeah, that's a dream. Also, what was a dream was our last episode and was a little bit awkward because on the day I think on the day, right, when we released the episode, or like just a few days later, Microsoft changed a little bit like how we think about Copolit Studio, right?
SPEAKER_01There was a nice um announcement, you know. It's actually it was pretty good to see the announcement because it was a nice video announcement. I think um Ryan did the whole uh video demo stuff like that. It felt like that there was quite a bit of good, although we'll get into maybe some of the annoying aspects of it, perhaps um annoying inverted comments, but uh the the the way it was announced, the energy, I think it was I think it's also quite interesting. There's gotta be, I think, the feature fastest to GA from public preview that I've seen ever. And of course, we're talking about the a month, literally a month, and of course, we're talking about the what we can now call the GitHub Copilot Harness experience in Copilot Studio, you know, it just rolls off the tongue, doesn't it? It's uh yeah, so beautiful. So so basically is so everything from our previous episode is out of date, then pretty much.
SPEAKER_00Oh no, so because so most of it um is still true. So everything in terms of the license consumption, how core work works, how GitHub Copilot itself works. The only little thing that changes is that you now have two different experiences in Copilot Studio, and potentially the billing is a bit different. So maybe we start with that reconciliation part of our last episode, and then you may can explain to the folks um what the actual new experience is, and I can explain the hard part right now. Um, so what we told last week is essentially true. Um, with Copolit Studio, you still have the classic interface, which is more of like your conversational agent, so a conversational structure. So this is as well still in the same consumption rate as before, it consumes Copolit credits, unless your user um the end user is an M365 Copilot licensed user, then this is within the license. So advise at this point if you do need to create an agent that is a very chatty experience, potentially about some documents, some internal rules, or something where um people need to reach out, and then there is an um agent uh or multiple agents that sits there and provide information, you still want to go with the classic experience because that chat experience definitely sits good there, and as well, it still supports the uh topics feature, which is um one of the features that didn't make the cut to uh the new GitHub Copilot Harness experience. On the new experience, the licensing looks a little bit different, so there um because it is built on the GitHub Copilot Harness, um the general execution of agents will be consumption-based. So it's pretty similar to covert, or more similar to covork, let's say it's like this. Not like just every action you take, every step you make um will consume uh credits at the point. The the system, like what consumes credits, is a bit easier, so it's a bit easier to follow like how much the consumption is now. So, in terms of, for example, estimation, I think it's a bit easier. Um, while there is a bit more control over that. Still, the important thing is um all the agents you have built so far, um, and the agents you built since the announcement of GA, which is like the 7th August or something, um everything that was built till the 6th August will now be consumption free till I think 1st of September. Um, and then this will be as well charged. Um, everything which you built right now today in the new experience will be charged right away. This also includes um the creation of an agent. So before in the classic experience, and this is maybe the biggest lapdown at the at the point of being right now, that when I create a new agent in the new Copilot Studio experience, which is GitHub Copilot Harness. Harness is by the way, the already word of harness harness harness.
SPEAKER_01Um put some emphasis in it, harness. Yeah, you can have some fun with it.
SPEAKER_00I really hate that word. Um, but this new build agent this will consume credits from the very first execution, so not from published, no, not after publishing, how it was before. So that you build your agent, you test the agent, and you make adjustments, which is totally natural. No one of us builds just agent right away that works in the first try. You do not test it.
SPEAKER_01I usually I usually I usually do. I mean, it's uh maybe a bit hard, so yeah.
SPEAKER_00Okay, you you you may be very gifted in this uh agentic world. We can say, yeah. So before it was that, like after um pressing publish, that will then consume credits if the situation appears that the end user is not M55 co-pilot license. Right now it is the moment you click on create and you test your agent, this will consume credits. And and this is like the the biggest caveat of that, or like the biggest like laturn of the of the new experience that like there is uh like a consumption cost for the makers, for the deaths, for people just trying out what the new experience can do. Um so this is already like the the most important point. And I I have not seen in the license guide any exclusion for developer environments as well. So um it is just in general, the moment this agent um goes into testing, um, it doesn't need to have to be published, it will consume credits, it will cost, and you need to be aware of that before you um build that or make this hardness decision.
SPEAKER_01Okay, so that's a huge box you've just dumped there. There's uh loads of stuff there to unpack. Let's just focus on a few little bits there. So you mentioned the word classic. Now, classic, we usually we use to talk about anything that's kind of old. What I think is kind of interesting when we're looking at the learn articles, we're talking about it being uh the standard harness. And in fact, there's three harnesses that it mentions it's the GitHub Copilot Harness, the standard harness, which is what we sort of are used to there, and then we now got this concept of GitHub copilot chat harness, uh specifically for extending M365 copilot. But I think it's interesting that they haven't used formally the words classic harness because usually, well, in our world, classic, what does that usually mean when it's being used? It means it's old, it's old, and probably is going to be eventually for like you know the chop type thing. So I mean, is it safe to build standard harness agents? Do you think should we be telling people to do that?
SPEAKER_00No, so there is no official information or as well. Honestly, there's also no NDA information about that. So at the moment it's still safe, and there is also no immigration between your standard harness, as I just learned, to uh GitHub compiled harness experience. So everything would you need to uh what you already have built in the in the standard experience, let's not call it classic anymore. Um, and you need to gather to the new experience, you need to rebuild that. But there is a we can potentially put this in the in the show notes, there is a um a skill for that. Um basically that can do it with with GitHub Copilot. So you can use that skill and then just connect to Copilot Studio via the GitHub or the Visual Studio connector, and and then just pull it from there and redeploy it with the skill.
SPEAKER_01So these new agents are also stored as YAML definitions similar to the old style agents. Yeah, yeah.
SPEAKER_00So you can just interpret that interpret it and migrate to basically a new experience. So but there is no button in Copolis 2G to click on and then oh yeah, do this to the you can type Copolit harness, please. So yeah, this is not there, yeah. But yeah, for right now, it is not going away.
SPEAKER_01Yeah, it feels like it's gonna, and it's because it still feels to me, there's still gonna need to be those scenarios where okay, I need to have you know determinism. Deterministic is what I need in my life, I need to have full control over what my agent can sort of do. Um, so that option is gonna be there. So I you know, I would say I'm still maybe saying to people, okay, try and have a look at the GitHub copilot harness over the standard harness, but yeah, I think we're still going to be probably talking about well, both, if not all three of them, for quite some time now and into the future as well, perhaps.
SPEAKER_00Um I mean, definitely there, as I mentioned, there are use cases to use the um the standard harness over the GitHub copilot harness, which is very simple in terms of I want to have a conversational driven agent and I want to have the lifters in M55 Copilot or in Teams, and I have a bunch of licensed M55 Copilot users. So if this is your use case, I would 100% go with the standard harness. If I have something that, anyways, runs autonomously in the background, or is something that is as part of a um more complex model um of multi-agent or in terms of um needs to do some some action in the background in terms of updating the system or something, I would may think to go with the GitHub Copilot harness because it supports skills and memory and has some recent new features. And as you know, skills is maybe something that is all over the um all over the bubble in the past months and weeks. So meanwhile, I think with skills, everyone everyone had some touch points so far, and you can just use those skills now in in custom agents, which is great, and you can uh build a lot of automation based on your business processes, and you don't need to um you do don't need to know coding in terms of um having everything tracked, you can just um define it in skills perhaps and um give this to the agent.
SPEAKER_01It's what I think is also interesting in the article they do like. of a table. We'll link to this in the show notes and stuff like that. But you know, it talks about like as you say skills and memory. Okay, yeah, GitHub Copilot Harness uh supports that. But then for the standard harness and copilot chat harness, it's kind of like this almost like you know, come hither sort of teasing sort of language like uh oh not a focus not a focus as if to sort of say like okay maybe maybe if you're good in the future. So I'm just I'm just wondering this is this perhaps maybe the the biggest example of like testing in production that we've ever seen with this Google Copilot harness? Is this going to be still a thing in six months or a year time?
SPEAKER_00It's I don't I don't think that is like something testing in production because the um what we have seen on GitHub Copilot in the past is already quite good and it's um uh follows a good adoption not only in in our organization but as well across multiple organizations and GitHub Copilot actually works very very well it works very well with agents with skills with different models so I there there is definitely they have done something right in the GitHub slash max of third quarters here um and there is already a success story with GitHub Copilot so so why not learning from what they have done or how they have implemented and why not have feature parry with um or for example what happens on foundry and what happens on GitHub so I so there is definitely definitely a need to to at least try that but the the past success of GitHub Copilot um gives them a huge favor and I I I don't think it's like something like testing production it's more like oh yeah from all the things we have done in the past 12 months or 25 or 24 months this architecture um has proven that works very good. So we know adapting this for other scenarios as well and we need to change that and it's better sooner than later to do this change before the whole world just runs on agents and the internet is just full of agents and we're um very very close to to Terminator movies.
SPEAKER_01So making this change right now is perhaps enjoying the summer break yeah because no no piece working we're all just asleep aren't we so yeah yeah they they could have just announced it during the World Cup and no one would have noticed that exactly we would be still here on the same day talking about an Indian could it be could it be GitHub Copilot saves Copilot Studio could we be saying that in 12 months time you know this you know now we can we the meteoric rise of Copilot Studio above and beyond where it is now of course you know we we we can we can basically think GitHub you can definitely make the case because um if we if we think back like six months or so my impression of Copilot Studio was like yeah it's a nice tool to play around but um as soon as we we received like real business cases and um more complex scenarios and um different kinds of user inputs where it's just not streamlined always the same prompt or always the same situation.
SPEAKER_00We faced a lot of difficulties not only in publishing but also in like maintaining the agent and we had like very weird setups that we changed the whole architecture of like all the agents we build which is now again obsolete of course but never mind uh but like well and then I was like I I was saying and uh I think you can you may hear it like in one of the first episodes or something or at one of the the conference um sessions I I did in the earlier this year that like okay Copoly Studio is fine for like a certain case of of situations but if you think about more complex scenarios you definitely want to go with foundry today I would may revise this and say okay you you you have a case of Copol Studio now again where you have a um yeah like your low code first approach when you can write skills when you do have an idea how this works uh with all of the MCPs and so connected uh you would be able to to create your more complex agent as well in Codepoly Studio Microsoft Foundry of course with the Microsoft Agent Framework or any kind of other kind of frameworks still sits there and is still getting like this super super complex cases or code first approaches where we for example connect the agent call to to a website or something like that.
SPEAKER_01So basically what you you what you basically said is you you you friend zone copilot studio you're like oh you know you're really nice you're really great but I'm sorry it's it's it's it's not you it's not me you friend zoned it fast forward six months you sort of see copilot again you're coming to Copilot Studio view again and you're sort of going oh hello hello that's you basically the glow up is real I'm with the music box in the backyard of Copilot Studio and backing for my pardon so yeah the glow up is real okay well I hope that you succeed in that in in all of your endeavors there is all I was saying but let's let's talk about the final thing but build to create it seems it seems controversial but I don't see given the way the consumption costs are I don't see how there could have been any other option at the moment for that so it's kind of like we were it was a nice ride while it lasted is what I'm saying basically well yes but also no so on on the one side so far so from a from a economical point of view absolutely right decision it's just like okay there are so many people running this on on their def environments there they they potentially have all those numbers um on like a very fancy dashboard and and then they say okay we need to bring this we have so many costs and we have so many thousands of agents running in context of a deaf environment or they're not published and they just consume um messages during the creation phase and this is a high cost for us.
SPEAKER_00So from from that point of view it definitely um makes sense from now from my personal perspective and from like your maker perspective or for someone for example very different breed but doing workshops and trainings this is a challenge now because um suddenly everything what we do in our session or we do at a workshop of course this is just a very slow tier on the list of uh people consuming messages on on the power platform but this also now costs us money so um we will double down on like um what are the scenarios and how complex they are potentially um as well if you want to just explore co-poly studio and this was already my critique on covork you you need to find your use case on covork but to find that use case and to find that use case for the new co-poly studio experience you need to have enhanced on and try out there is no no simulation to get there and say oh yeah this is my perfect agent this is not existing so you need to have enhanced on you need to try you need to um to excuse pardon my friend you need to fuck around and until you figure out yes yes of course exactly yes it's a classic thing yeah yes and and this is how it works with like new technology and new stuff that happens and you can't do this without generating costs now and how how do you how do you argue for this cost?
SPEAKER_01We had like the this this month we had like one agent that consumed within four days a hundred thousand credits if you're not aware of that if you don't check the telemetrics on PowerPlatform admin center which is um bit lacking right now in terms of availability or for example the Microsoft admin center with agent 365 which is again a paid license uh you potentially generate an invoice at the end of the month if you don't set up your limits um that you don't want to see but Sebastian you know how badly Microsoft is shocking you saw the earnings report last year you know how can you morally be expected to take such a free ride moving forward you know you have to pay for this stuff you know Satya's children haven't eaten for many many months now I've been reliably told so you know you you have to pay now that that is just the way of the game we have to pay speaking a bit more seriously though um I just wonder whether there will be and we have we've spoken about this kind of uh not on the podcast specifically but whether there will be more of a push towards going local because everything always feels kind of cyclical in everything to do with IT you know we you know we there's we you know there was a whole demand you know back in the 80s okay let's go to have these remote machines that we connect to have these dummy terminals oh let's all go back local again oh let's all go back to the cloud and stuff like that you know yeah with these rising costs and these large language modeling could it be a point when we start to get to see this run on our local machines you know are we just building and developing locally do we just build and test and develop our agents locally and then just get them onto these cloud platforms after the fact so that that's a part of your character because I was just exploring last week's a lot of around um using local models and and deploying and what are differences and what we can do and um how for example things um do you run?
SPEAKER_00I would say not yet maybe for personal productivity maybe in terms of like you have a local agent um or you have a local setup where you can just quickly chat with it or something that runs locally on your machine that just um considers things which are on your machine um something like open claw in that direction and you kind of hook it up to messaging um and different mcps but still the the model needs to run as well locally so it does not only have the need to have your agent locally deployed but also in the model and this is I think where it falls short still a little bit the there is um I think you shared this there is a as well a model from from Germany that is quite good for a local model um there is well Gwen models which are quite good um Google has a own breed of local models I would as well for example um yeah I would like to see some local models for Microsoft Nvidia has them so there's a wide uh wide variety of local models but I think still like for that organizational wide rollout or for this organizational wide use case I think it's maybe still still too early and that whole hardware and infrastructure still costs that much so that's also why we have that high cost prices because all of these light energy water consuming data centers do consume so much energy and do cost that much to run. So it's not just that the costs of AI are that high that everyone earns a ton of money and um builds up generational wealth but also because of the infrastructure costs are that high and you would need to carry out this um costs by yourself now internally and you need as well to be um you are responsible for the uptime you're responsible that everything is up to date you're responsible that everything is maintained over the the sake of time so these are all factors you shouldn't ignore when we're talking about local for personal productivity uh I I totally agree that this is definitely something to explore um in terms of um the the own if you like to do it because there's definitely some some barrier with the with the setup but with Olama for example it's quite easy um and you still can for example there's there's something called like something called there's called like uh the Hermes agent which you can spin up to like a telegram or something and then you can chat with it and I can response it you don't need to go for the console or the terminal. So there's definitely options and I and I think this is the the models are good enough to do that for personal productivity.
SPEAKER_01Yeah I'll link to the one that I sent you um um uh made in Germany Sufi S you know a a true uh Wunderwaffen the best thing that Germany has done for quite some time I'm sure but yeah it looks it's receiving well let's see who knows maybe Germany saves the whole AI race you know in terms of making it affordable making it better you know all this sort of good stuff but yeah this is I think where we're increasingly going now um I think in terms of you know because I think there's gonna we're gonna reach a point where um you know things are just gonna break you know in terms of consumption to cost in terms of costs being too high all this sort of stuff I just feel like that we're gonna hit a point where people just go right I'm not paying that I still want to use it so I'm just gonna go local instead I get I get maybe 50% maybe of the of the same sort of benefit but I'm still able to manage my costs better. So yeah definitely definitely worth exploring indeed so quite a week what what a what a week or what a day between publishing episodes you know happens. Usually this is the this is the time of the year where we can just sit back and relax and just not worry about anything sort of um you know production breaking hitting our sort of news feed. So I have to say props to Microsoft in terms of just the the way they approach the whole announcement the way it was announced uh the energy behind it as I say it's it's just it's just crazy that you know the the time from it being just public preview to GA is just phenomenal.
SPEAKER_00I've never seen anything come come go through that sort of life cycle as fast before it's uh astounding you have to say just nothing like project operations no you're we get you're gonna be you got you're gonna be waiting two years for things uh I'm sorry but I may but what one more thing maybe at the end to ask maybe you should kindly explain the word harness because this is not an AI word harness just harness harness it is it is basically uh it is basically just a connection of different things that that make it up together to like one thing so um if you think of agents a harness is basically like all of the tools triggers um skills all of that all of that combined is the harness with the agent together um there you can also apply this this word to for example um qa so a test case a test suite or um the scripts you run on your automation testing this all is a harness so I really don't get intimidated but as like a p it's like a picnic basket you know an inside picnic basket I've got my my agent my tools my knowledge sources maybe a nice little nice little dessert for afterwards you know so it's all just yes so it's a nice presented and lovely so yeah so so please please don't get intimidated because everyone knows harness and you need to understand what a little and you have no idea so harness you have to get the face right when you say it harness harness yeah it is it basically in old terms we just call it a solution I think yeah exactly exactly so yeah it's it's nothing new it's it's it's been there for a long time and since I think the 80s or something so it was just not used and someone just thought oh yeah this is like a non-used word we we didn't use a lot in the in the past decades so let's call it now and and make it very important in the age of AI. Retro is the new vibe you know so I'm all for this let's let's bring let's bring back all the great stuff from the from the 80s all the great stuff from the 90s yeah yeah so because retro is the vibe also being offline is the new vibe and therefore um thank you for listening but no please go back and touch some grass and go enjoy enjoy the summer um you're still here till we resolve this thing here um so thank you yeah i'm gonna i'm I'm gonna go back to bed and see if that helps go back to bed how this goes I will head down for breakfast um and therefore thank you so much um new episode of unresolved dependencies every second Monday and uh yeah last words to Joe uh keep on vibing enjoy it and uh I hope you uh really really enjoy your newness goodbye
People on this episode
Podcasts we love
Check out these other fine podcasts recommended by us, not an algorithm.
