Power Platform Boost Podcast

Travelling Circus (#82)

• Ulrikke Akerbæk and Nick Doelman • Season 1 • Episode 82

Share episode

Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.

0:00 | 32:43
Nick

So I'm here, you're here, your voice is not here. I think you left it some you did you leave it in Vancouver?

Ulrikke

I left it in Vancouver.

Nick

Okay.

Ulrikke

So I woke up this morning and my voice was like this. So I'm gonna try to keep it low like this, sensual and low for you guys. And I'm gonna try to get through this, but it's rough. Yes, it's okay. Okay. So it's gonna do most of the talking today.

Nick

Hello everyone, and welcome to the Power Platform Boost Podcast, your timely source of Power Platform news and updates with your hosts, Nick Dolman and Ulrike Ackerback. Hey, Ulrikke

Ulrikke

Hey Nick.

Nick

How's it going?

Ulrikke

Um, not so good.

Nick

It's funny because we we we're recording live here at the Microsoft campus at the developer DevRel Studios. The DevRel Studios. I took this opportunity to for us to be able to record in person. So I'm here, you're here, your voice is not here. I think you left it some. Did you leave it in Vancouver?

Ulrikke

I left it in Vancouver.

Nick

Okay.

Ulrikke

So I woke up this morning and my voice was like this. So I'm gonna try to keep it low, like this, sensual and low for you guys. And I'm gonna try to get through this, but it's rough. Yes, it's okay. Okay. Nick's gonna do most of the talking today.

Nick

Yeah, well, my voice is already beginning to go too, but I think mine will I it's okay.

Ulrikke

So maybe we'll just go until we all both full silence.

Nick

Right. So, of course, we did our episode last week. Uh, we did a bonus episode, we did the release wave uh 2026 wave one. Haven't had a chance to check that out, please do because we talked about all the new things or well, quite a few of the our favorite new things that are coming in the release wave of this year. Um, but yeah, we there's been a few news items as well coming up. Um, a lot of things have been happening. Like you, like we said, we are here for MVP Summit. Uh, we're hoping to learn a lot of interesting things about where Microsoft is going, what their plans are. Uh, of course, I we really can't say too much because a lot of it is uh redacted or under NDA because sometimes plans change, sometimes this information can compact, you know, impact competitive things and all this other stuff. Whatever. We just got to keep our mouth shut. But I think we can safely say it might have something to do with co-pilot and agents and AI. I think maybe, or maybe they're maybe they're doing something different.

Ulrikke

Maybe they're just turning it completely around and just going down a different route. Who knows?

Nick

Maybe exactly.

Ulrikke

Yeah. And I think we can say for sure that next time we will know a bit more about the direction Microsoft's going with. Right. Um, and of course, like you said, we can't say anything, but we can always it will always influence what we talk about. Yeah. Right. Because so that's kind of also a reason to follow MEPs in the community. Yeah. Is that you will get a sense of if something is going away or um Microsoft moving in a different direction, that influences the things that we are focusing on.

Nick

Yeah.

Ulrikke

So it's a good way to kind of keep on track and making sure that you are on top of things.

Nick

Right. And so let's like speaking of community content, we have a few things. Uh speaking of community events, uh, we also we we just came back from the Canadian Power Platform Summit. That was what came back from that was part of the journey here. Stopped in Vancouver, came down here. Uh, it's uh it was basically a two-day event, or maybe kind of three, if you consider the dynamics user group, the folks that do dynamics con also had an event on the Friday. We did workshops on Friday, um, covering different things we've had uh on ALM, on co-pilots, on you know, career planning. Um, and uh oh, what was the fourth workshop on? Um, I planned it, I was there. Oh, apps, uh creating beautiful apps, uh power apps and things like that. That went really well. And then, of course, we had the general sessions on the Saturday, and uh just a big shout out to Keegan Chambers, um, her keynote, uh, really a lot of these technical conferences. We talk about all the new technology, and of course, sometimes there's Microsoft keynotes talking about the latest and greatest and what's coming up. Keegan really hit on something about something that I think affects a lot of people in the IT community is the being different, neurodig neurodivergent. Um, Keegan has uh, you know, in her family, she she deals with this. Uh, she has some of she talked about her own experiences. And I think if you looked in that whole crowd um and you kind of looked around, a lot of people would have been nodding or identifying or realizing that for us in the IT industry specifically, we we we are a little different sometimes. Uh, but it's our superpower. It's how we think about things, how we can interpret things, how we can work through that logic and problems. And I think these superpowers in this new world that we're going into are going to be even more prevalent and more important as we move forward. So Keegan's uh keynote was great. Of course, a lot of the other speakers, a lot of the other sessions were on top, amazing. Um, and then April Dunham did the closing one. Again, that was much more the Microsoft technology, but really pointed. It was a nice mix of hey, if you know the power platform, it's still good. That knowledge you have, it's not going away. But she gave some very concrete ways of how to kind of transfer this and take your knowledge and enhance it so you can be very successful moving forward. So um, as an organizer, I'm happy it's done because it was it was very tiring. But most people, overall sentiment people were very happy. Um, we're really hoping to do it again next year. Uh, probably the venue might change a little bit, a few other things. So we'll figure that out. We have uh we have all sorts of time to sort that out. And I'm not gonna, yeah. So that was really cool. Um I was a really good vibe.

Ulrikke

Yeah, it really was. And I think the the the keynotes that touch on personal themes, it feels a bit out of place at a technology conference because, like you said, it creates a very intimate vibe. A lot of us can relate, and so it brings people together in a very special way. And we saw that the last few years at EPP, no, sorry, CPBS especially. Yeah, you've done that kind of consistently, and it creates a very it feels like a safe space. Yeah, that's what it creates, and it kind of makes everyone breathe deeper a little bit in the morning, so it's uh it feels a bit invasive sometimes, but it is a really good way to start a technology conference, yeah. I think so, really well done for putting on a good conference. It was a very good vibe when I arrived, and it was uh yeah, it was great.

Nick

Cool. Well, thank you. So, and then moving on, uh, so of course, uh, we had a different travel adventures coming down here. Uh, coming here wasn't too too much of a problem. Um, and now we're here today at the the the devreel studios, devrel studios, not not not at home. No, uh I'll get back home eventually, I think.

Ulrikke

Maybe if you can find your way, find my way. We're gonna spend the week here with our very good friends in the M MEP community. Yep, and we're gonna learn so much. And I looked at the schedule and it's completely backed. Yeah, my plan is just day, morning till evening, jam packed. Yeah, and I know from Beaver's experiences here that I'm gonna be poop by the end of this week. It's like I underestimate because we we go to conferences, we speak, we're engaged, we have a job to do. So our focus is on delivering and to host and to be there for the attendees. But then being here for a full week and consuming content for a week makes me appreciate how tiring it can be to learn all this stuff and how intense it is.

Nick

And to take it all in and you're making notes and you're just trying to absorb all that. And it's it's nice to not have that um that the fact that we're not presenting anything, um, besides from this. Uh, but overall, it's uh it's just it's good, but it is very tiring. And I think uh for all the other MVPs that might be watching this, and I'm giving you this advice as well, is try to take a break sometimes. Like, yeah, there's the sessions uh for us, they they are recorded, it's not public, unfortunately. Um, but you could catch up later on the plane ride home, maybe download a couple videos and just to give your yourself. I'm probably gonna do that. I'm gonna try to sneak off to the gym a couple times this week, um, just to kind of you know clear my head, you know, exhaust the body, clear the mind. That's true. But we we also, but of the past week, we've had a couple of our community friends come up with some really neat content or Microsoft themselves. We made the big announcement. We did want to, well, big announcement, um, talking about co-pilot co-work.

Ulrikke

Yeah. So haven't you used um claude co-work at all?

Nick

Yes, I've used claude co-work. I've been experimenting with that. So this is my understanding. This is Microsoft taking that technology, but putting the proper, I'd say, governance and security wrappers around it, or not even wrappers, but also taking that technology, but making it in a way that you can work within your Microsoft 365 environment. You could use your content, and it's just going to make it a little bit uh more secure and a little bit more enterprise ready and more collaborative under underneath all that. Part of a new um SKU, we always talk about the E3 SKU or the E5 SKU. This is the you know, E7 SKU right now.

Ulrikke

A new licensing model, $99 per user per month. You get access to all the frontier, um, new frontier capabilities, features, call it what you want. And co-work's part of that. And I've been using cloud co-work a lot lately, yeah. But I have to limit myself and what I give it access to because I don't trust it with customer information, for instance. So to have this co-work experience in Co-Pilot and to be able to trust it within the ecosystem of my Microsoft 365 tenant is really something I'm looking forward to. It's gonna open up the box for what I can use it for more. So if you haven't used co-work before, it's a way for you to collaborate with AI on a much bigger scale. Yeah. That's how I find it. I'll give it access to um different documents. You can look at it as a workspace or a project. Um, it is very it's great for PowerPoint presentations, document creation, um, and also kind of um aligning work. So I use it to create a framework, for instance. It's worked really well.

Nick

Yeah, what I like about these tools is like when you work with agents before, like the thing is the co-pilot or chat GPT were always good, like, build me a PowerPoint about this, and it'd be like, got it. And it would come back with a heaping pile of crap. What I like about this is it's and this is going to be this is what I have to you know talk about working on skills. I'm not the best delegator in the world, probably like so. I'm like, okay, let me do it myself. So part of working with these tools, essentially you're delegating a bunch of work to the agents. What I like about it is it sometimes what I think my my my issues with delegating is here, go do it. Okay, like you don't have any questions. No, no, we're good. But now, if you use these cowork tools, um, I assume co-pilot co-work from what we've seen will do the same as how cloud co-work does. It's like, okay, you want it kind of goes back to you, okay. You want me to do this, you want me to create a PowerPoint, you want me to look at the meetings this week, you want to pull in these emails, this documentation. Okay, I this is this. I've here's my task, here's my plan. I'm gonna do this, I'm gonna do this. Here's step one, two, three, four, five. Does that sound good to you? Yeah, and you got to read through it, and then you could say the thing is it's not like it won't be offended either if you say, No, no, no, no, no. Okay, step one, actually, because a lot of it's just how I explained it. No, actually, what I meant was, and let me re-explain it, I want you to do it like this, like this. And again, it's you know, giving you that opportunity, and it's like, oh, okay, instead of this, we're gonna do this instead. Like instead of oh, going to your Outlook calendar, or I want you, you want me to look in the these emails, or I want you to do you know this with a Word document, maybe not a PDF document, you know, stuff like that. And then it will come back, okay. Here's the plan one, two, three, four, five, six, seven steps, good, go. And then it's gonna go off and you see it thinking and you see it kind of going through the motions. So this helps you when you're giving it tasks again down the line, you're sort of seeing how it works and how it understands. It's like it like working with a colleague. Once you understand their working habits, you can collaborate a lot better. And not only that, you can give it the skills and give it the information. It's like, oh, you're okay, I need to give you a little bit more information on this. So I'm really excited, I'm excited. I'm also like, okay, am I gonna be a little bit nervous handing stuff off? But I've been using some of these tools uh for other things, and I'm already finding that it is giving me a lot of that productivity, um, but realizing again, I it's my part in it, it's still integral. The human in the loop. I'm still orchestrating it, I'm actually giving it the feedback, but a lot of that tedious work um is gone. It is bringing in a lot of that creative work as well, but also because I'm giving it system prompts or giving that information of how I work, what my voice is, it's taking that. So it's almost like, okay, yeah, I would have written it the same way, or written it would have been very similar, but I can still go through and do some final edits and make it my own. So yeah, very excited to see how this evolves and it coming up and just waiting to get my fingers on the actual Microsoft version of this. And then that way, again, that kind of takes a little bit of those, those wall or builds gives me that that security blanket that I need for this.

Ulrikke

And also there's the the storage, the memory part of cowork is different than a chat. Yeah, so you have a chat with a and with an agent, and it will fatigue and it will forget, and you have to refresh because it will go off on a tangent somewhere, and you have to kind of bring it back. But with co-work, it's different because you'll have a fresh loop every time. So it's more designed to um save its knowledge in the files. So it saves memory in the physical MD files. Yes. And then it will be more, it will be able to kind of refresh your TAT experience more often.

Nick

And you can edit these markdown files. Yeah, we say MD markdown, markdown is a formatting. Um we use it a lot when I was here working on the docs team. Uh, so um, yeah, that gives you the ability to kind of again guide or give it like give a playbook to your agents, right?

Ulrikke

And it learns how you do things and how you work. You can share those files within your team and you know, among colleagues to give it specific skills, which is a big enhancement to what we had in the past. So it's gonna be more like a coworker.

Nick

Yeah, very cool. So, speaking of getting work done in cool ways, uh, there's a video this week from our friend Sean Astrakhan. I don't know if you've seen that.

Ulrikke

I have, but you tell the people so that this is your voice.

Nick

So you're oh okay, the truck the trucker voice.

Ulrikke

I'm outsourcing talking to you.

Nick

It's just getting worse and worse. So you need a talking agent now.

Ulrikke

Yes, I do, and I have one.

Nick

There we go. Okay, so here's my plan. I'm okay. I'm gonna tell I'm gonna, you know, we're gonna look at Sean's video, we're gonna discuss the points, and then I'm gonna reiterate the points, and I'm gonna follow this, I'm gonna talk, you're gonna nod, you're gonna smile, and then you're gonna interrupt me and say, no, no, this is how I understand it, and everything like that. So, okay, good. Got the instructions, gonna go with it. Yep. All right, so Sean Astercan did a video. You really have to check this out if you haven't seen that yet. He basically talks about a very simple process that if you're working in the Power Platform and model-driven apps, we've all been there. Like we have uh a task in DevOps, client wants to add a couple new fields to a model-driven app. We've done this a hundred times. Of course, we'd probably see that task. We would go into our dev environment and click ity clack, add the fields, then go update the view, update the form, uh, save, publish, uh, do some testing, deploy it to our test server, have uh QA people maybe look at it, uh, or maybe our client look at it, depending on the size of the project, make sure it all works good, done in production. Not a hard task, but of course, our task become a lot more complex over time. So, what Sean did is kind of went through the motions and did this completely 100% from Visual Studio Code.

Ulrikke

Wow.

Nick

He went in uh using the Dataverse MCP server, the Azure uh DevOps MCP server, and Playwright. So those are the cool main tools. Uh uh used a, I think maybe a bit of GitHub Copilot or a bit of Claude code or a mix of both. I think he used Claude to verify some of what the GitHub Cloud did or something like that. But basically had it read the task from Azure DevOps and very much like we were talking about before, read that read the task and said, ooh, okay, here's what I need to do. Here are the steps, and basically broke down the steps and then used the Dataverse MCP server to kind of find the schema names and everything like this. Uh, use the command line utilities to update the views and the forms. Um, of course, there is a bit of back and forth, you know, again, orchestrating human in the loop, and went through and then finally, when that was all done, did through playwright and tested the process and did the clicking on the screen, opened up the browser. Is this new field here? Is the view look right? Is there values in there? And then coming back saying all tests passed, good to deploy, and then update the Azure DevOps task in the end that it's now complete, putting in the notes of all what it did.

Ulrikke

Awesome. So document as well.

Nick

Yes. Well, that well, document that was part of the process in Azure DevOps, right? So there's no reason why it couldn't have like updated a wiki page or or update that. The other cool thing, too, with the playwright steps. Uh, Sean was funny too. If you maybe did some other work later, or one of your colleagues are going and manipulating those forms. Well, let's run those playwright scripts again. Oh, it failed this time because your colleague removed the field from the form. So you know how it is, right? We we build something, we deploy it, client's happy. Three or four months later, or a year later, or two years later, oh, we want to change this, we want to add this, we want to change things around. Good, we fix all that, we deploy it, but what we did two years ago is broken, or six months ago is broken. If we can now run that through the those original playwright scripts again, that it can go through and like, yeah, wait a minute, yeah, you fixed this, but this has been broken. So before we deploy to prod, we catch that and then we can make those adjustments, or the agent, or we can work with the agents to make those adjustments. So, Sean, amazing video. It's like it's 10 minutes, um, but he refers to some of his other videos as well. But just to take in what is possible, and also I think again, enhancing your power platform skills. Um, even if you're not a developer, if you consider yourself just a functional consultant or a maker, download Visual Studio code, look at the command line, look what it's doing. It's not that scary. And you also have a co-pilot that can help you throughout the way and explain it to you because you can even ask your code, I do this a lot, explain this code. If I'm looking at code someone else wrote, what is this doing? And what is it wrong? And I've had, I've had um, I've had both co-pilot, GitHub co-pilot, and Cloud Code come back saying there's a whole function that's never been called in this script because there's no entry point. And the developer that worked on that years ago might not have even noticed it and that kind of thing. So these are the tools, and it's that all that is, I think Visual Studio Code is basically the primary thing that I'm into these days.

Ulrikke

Yeah, for me as well. Yeah. And I also know you have to kind of check its work a little bit as well. Okay, very some stories this at CPBS was someone telling me that it confidently asked it to run a CLI command that doesn't exist. It's like, and then this person knows CLI very well and just came back and said, Are you sure that this exists? It's like, oh yeah, I'm sure. Just try it and you will see. It's like, no, it won't, it doesn't exist. But I've used Copilot uh or um um Cloud code a lot now to help me set up these things, right? To collaborate with it to help me set up what do I need? Do I need Node.js for this? Right. Do I need to install any libraries for this? And it helps me set up my development workspace. And as much as we like the term maker, the new term is builder. Yeah, a lot of us are builders, and a lot of makers are now transitioning into code through these tools because you can have someone hold your hand as you're doing it. So it's yeah, it's scary, but give it a go. I think you're gonna be surprised of how easy it is when someone holds your hand.

Nick

Yep. Yep, a lot of cool content.

Ulrikke

Right. This is timing out. Let's see if I can get back in. So you want to talk about um the thing that uh Frederick Right.

Nick

So there was another really cool article I saw this week from uh Frederick uh sorry, Frederick Engeset. Engeset? Engeset Cool, yeah, all right, good. Norwegian Norwegian of mine, previous colleague of Litika um did a really cool thing with uh Power Automate. And of course, people are like, Oh, like there's you know, Power Automate. Well, that's oh what's what about all the new cool tools and stuff like that? Guess what? Probably of the 10 automations you're doing, eight of them still need power automate.

Speaker

Yep.

Nick

So what he did though, uh you know, trying to change a few things and power automate, power automate does have its own built-in copilot. Yes, it is getting better, but he he looked at it and he goes, Power automate, you can export to JSON. Claude code works really well with JSON. Yes, so it's almost like hmm, chocolate, peanut butter, let's put this together. See what happens. So, what he did was and he explains it in his blog, and of course, we have the link in the show notes. He exported the JSON from Power Automate, put it into Cloud Code, gave it some instructions to make a few changes. It went through and gave it told it you're working on a Power Automate JSON configuration here. Cloud Code knows about Power Automate and went through. And again, these are not only he could kind of find that information, but again, we can start building agent skills, and that's a whole other conversation. But basically went through, made the changes to the JSON file. He took it, pasted it back into Power Automate, and it's another one of these. Wow, it it actually worked. So it was a very simple example, but again, it's really showing how there's we can use these tools in very creative ways to get our work done. And we're not just limited to one set of tools. So it's not like, well, we're creating Power Automate, we have to use the built-in co-pilot. We can use the other tools. And like we said previously about, you know, you work with Visual Studio, we can actually use the different models to check each other's work as well. So if GitHub Copilot comes up with something, we can take, you know, comes up with a plan, we could give that plan to uh Cloud Code and say, what do you think of this plan? And it could come back and say, Oh, this is great. I think going back to Sean's example in our previous segment there, he actually had that in Cloud Code found an error with one of the formulas. So, like what you were saying, with that's who you ran into, someone said they were very confident about the CLI command. You could ask another, does a CLI command work or exist? And it could come back and say, no, you know. So again, this gives us good information. But again, shows the huge we need the human in the loop.

Ulrikke

Yeah, yeah. And also you can have different agents with different skill sets in Cobile Studio, for instance, and you can have the critique.

Nick

Yes.

Ulrikke

Right. And you have someone who always yeah, the critique skill that always goes in and is very kind of judgmental and will always uh source check all the things that are in there and check it against documentation. Yeah, which is a good thing to have, right? Quality assurance.

Nick

Right. Stuff that sometimes we as developers we like, no, if it if it works, ship it.

Ulrikke

Yeah, exactly. Right.

Nick

So uh very good, Frederick. That was a yeah, an awesome was my one of my uh one of my uh one of these like these little things, very kind of a simple uh process that shows some experimentation, which I always love doing. Like kind of like, well, let's try this and see what happens. What's the worst that could happen? It could work, and you have a really cool blog post about it.

Ulrikke

Yeah, exactly. Um, and I also wanted to touch on the IQ series. So um Microsoft has launched an a series of learning content and videos on fabric or sorry, um, foundry IQ. Uh so three videos up on Foundry. Yeah, I think they're gonna cover the rest of the IQ stack as well. Um, I haven't had time to go through it, but I see that there's a lot of very good learning content around the IQ series, which is part of the Frontier framework.

Nick

Yep.

Ulrikke

And you can get access to that through the Frontier program.

Nick

Awesome. Yeah, definitely. I saw that I saw that you showed me that this morning. I'm gonna check that out. Probably not this week. But we'll probably get a lot of that, a lot of very similar info potentially. Uh, but yeah, just again, so if these are things on your learning plan, um, you should be, and this is interesting. We talk about learning plans and absorbing when do we find the time and all this? Uh, I saw a blog, uh, a link, and I have I don't have it in the show notes. I do have to find it, but it'd be reflected on sort of what I do as well. Um, how much time should we be spending learning new things in our job? How much time do we allocate for that? If I go to my power lifting career, I spend six to eight hours per week in the gym.

unknown

Okay.

Nick

Go early in the morning before I work, whatever. Um, I I'm gonna I'm in a fortunate place where I can actually, not this week, but generally if I'm home, I can get the I can schedule that in. For when I compete, I may be on the platform from anywhere from like six to nine minutes. And you think about that ratio of time, time to results. Now, I'm not saying that you have to spend um that same ratio in terms of learning, but if we actually look at our our daily work and how much time we actually spend learning new things, it's like we maybe spend 15 minutes to watch a video and yet we're doing 40, 50 hours of work that week. So just something to consider. And it's not really, we don't have a solution per se, but just food for thought when people say, Okay, how much like I don't have the time to learn all this new stuff. There was a very uh saying that I've heard before, I'm too busy cutting down trees, I don't have time to sharpen my saw. Yeah, and then you become more less efficient, and of course, people start you know doing these new things, like what Sean was showing and all of this stuff. So I guess I'm sort of uh reminding myself, probably reminding you as well, and everybody that watches us, do try to carve out some time per week, a few hours at least, if not more, if you can, and just to spend time at least, you don't have to be a pro or an expert, but have some um indications of where this is going. Of course, listening to us, we can kind of check. We put the show notes, we put the links. Um, and I know some of you will go down and check that all out. That's great. Continue to do that, but also take the time and actually fire up Visual Studio Code and fire up Co-Pilot Studio and try, just experiment. Like you're not going to launch nuclear missiles, hopefully. Um probably not if you make sure you're using the right governance in place, anyways. We anyway, uh so, anyways, it was just sort of something that I thought about too. It's like, you know, all of these things, like where do we find the time? And I think it's just something we have to schedule like a meeting, like anything else.

Ulrikke

Yeah, and I think that goes for a lot of the I saw a quote, you know, it's the the most important asset we have is time, and that's the thing that we squander the the most.

Nick

Right.

Ulrikke

So your priorities and where you prioritize your time shows yourself what it is that is most important. And I think so. When I started uh my career, we had 20% allocated to learning. So we had one, I could take one out of five days at my job to learn new things. And that came, and that was with the foundation for me being able to become an MEP essentially, because I could spend that time learning and then document what I learned in the blog post, right? And then kind of get the word out there.

Nick

Yeah.

Ulrikke

But to be able to set aside that, and there's learning when you're on the job. So when you learn something new, show a colleague, show someone, yeah, and don't be afraid to make mistakes.

Nick

And and the thing about showing something you've done, like if you're like doing an experiment, like grabbing a JSON file out of a Power Automate, you show somebody, even if it's just a colleague or something, they might say, Ooh, what if we tried this and what if we did that? And then it kind of explodes from there. You might learn, and you could learn something new, or they could say, Yeah, but watch out for this kind of thing. So, anyways, I'm all about the uh yeah, and this uh this week we're gonna be taking in a lot of learning. Um, but I just sort of say it's just part of in terms of career, I think overall, and this goes back to April's closing keynote at CPPS. A lot of things I've been hearing lately about this new way of working and things like that, is the value it is important for your careers to to actually invest the time to learn some of these new tools, but enhance the knowledge you have, and that's gonna make you successful going forward. And uh we're still gonna need people.

Ulrikke

Um yeah, 100%.

Nick

Uh and it's the people that are gonna be um kind of being able to embrace a lot of these tools, are gonna be sort of the ones kind of leading the pack. And so yeah.

Ulrikke

Yeah, but it's like I said a few episodes ago, we're in the chaos part of this. And don't be an expert. Play, experiment, explore, explore, yeah, and then it will quiet down. You know, not long from now, we will see the standards, we'll see a clearer path forwards, we'll kind of know our way around it and where to invest. Then that's the time to double down to find your niche thing, yeah, to find your kind of your axis that you're good at, and then you run and you capitalize. Right. But right now, don't be an expert. Play with everything.

Nick

Yeah, and you can't be.

Ulrikke

No, there's no way. If anyone tells you they're an expert in anything, for me, it's like, sorry, dude, too soon.

Nick

Yeah, yeah, yeah. Cool. Anyways, this has been a great episode. I think we need to give your voice a rest. Uh, we did cover a lot of cool community content. We talked about the uh the the conferences, of course. There's conferences coming up again, or you know, check us out. We're going to be at Color Cloud. Yep. Uh, I will be at Dynamics Minds at the end of May. Uh, we'll both be at the European Power Platform uh conference.

Ulrikke

Yep.

Nick

And and then we'll see what the fall brings. Um, still a little bit up in the air. Anyplace else you're gonna be in the next uh month or two?

Ulrikke

So I'm dialing down, so I'm keeping it local.

Nick

Good for you. Cool. All right, thanks everybody, and I think we'll be back to our regular episode uh in two weeks. In two weeks. Uh, and uh and probably in our regular recording setups. Yeah, maybe but this is cool. I maybe I should be so cool. Maybe I should build one in my house.

Ulrikke

Yes, can you? And then you can invite me to come every two weeks. Yeah, we'll do that. Yeah, yeah. Thank you so much for that.

Nick

So, like, yeah, please please buy us a beer or biotica airline points.

Ulrikke

Yeah, that's right. Thank you so much to the very professional people here at Devon Studios. Thank you for the opportunity to have us here for us to record. It's so cool.

Nick

Yeah, yeah. Big shout out to Matt and Sarah that helped getting everything set up. Uh we love you guys. Thank you for doing this. And of course, uh see you all soon.

Ulrikke

Yep. All right, bye-bye, everyone.

Nick

Thank you for listening. If you like this episode, please make sure you share it with your friends and colleagues in the community. And be sure to leave a rating and or a review on your favorite streaming service. That makes it easier for others to find us. Follow us on social platforms, and make sure you don't miss a single episode. Thank you for listening to the Power Platform Boost Podcast with your hosts Lurik Akovek and Nick Dolman. See you next time for your timely boost of Power Platform news and updates.

Head Shot

Nick Doelman

Host
Head Shot

Ulrikke Akerbæk

Host