Magnus Gether Sørensen's Tech Journey and the Role of Generative AI

Transcript

WEBVTT

00:00:06.692 --> 00:00:07.974
Welcome to the MVP show.

00:00:07.974 --> 00:00:17.289
My intention is that you listen to the stories of these MVP guests and are inspired to become an MVP and bring value to the world through your skills.

00:00:17.289 --> 00:00:23.211
If you have not checked it out already, I do a YouTube series called how to Become an MVP.

00:00:23.211 --> 00:00:24.946
The link is in the show notes.

00:00:24.946 --> 00:00:31.210
With that, let's get on with the show.

00:00:31.210 --> 00:00:37.124
Today's guest is from Denmark.

00:00:37.124 --> 00:00:40.551
He works at Delegate as a Managing Specialist.

00:00:40.551 --> 00:00:42.924
He was the first award as MVP in 2022.

00:00:42.924 --> 00:00:47.523
He has got the nickname of XRM tooling wizard for creating developer tools.

00:00:47.523 --> 00:00:55.164
His goal is to bring best practice from both the academic and the real world into the world of business applications.

00:00:55.164 --> 00:01:02.006
You can find links to his bio and social media, et cetera, in the show notes for this episode.

00:01:02.006 --> 00:01:03.210
Welcome to the show, Magnus.

00:01:03.939 --> 00:01:04.983
Thank you, thank you.

00:01:06.989 --> 00:01:08.820
I'm pleased to have you on Like.

00:01:08.820 --> 00:01:11.129
I remember observing you at MVP Summit.

00:01:11.129 --> 00:01:14.870
I call you the flashiest dressed MVP in the game.

00:01:14.870 --> 00:01:18.430
You always look smart, put together on point.

00:01:19.180 --> 00:01:21.308
I always feel comfortable in a suit.

00:01:21.308 --> 00:01:33.772
You know I come from a consultancy background and it's sort of part of the uniform and of course if you have off the rack suits it's not as comfortable.

00:01:33.772 --> 00:01:38.165
But I have tailored suits so it's comfortable in any weather at all.

00:01:39.028 --> 00:01:47.703
So yeah, very very classy, Very very classy Tell me about food, family and fun.

00:01:47.724 --> 00:01:51.010
Oh, food, I love food, just any food at all.

00:01:51.010 --> 00:01:52.793
My favorite food is just buffet.

00:01:52.793 --> 00:01:59.626
You know, if you ask anyone, they'll tell you how much I slaughter food.

00:01:59.626 --> 00:02:00.870
I've had a lot of issues with that.

00:02:00.870 --> 00:02:05.634
When I was pretty inactive I gained some weight.

00:02:05.634 --> 00:02:10.831
But during my paternity leave I walked a lot with my daughter and I think I lost 10 kilos or something like that.

00:02:10.831 --> 00:02:12.939
Yeah, yeah, just walking.

00:02:12.939 --> 00:02:15.127
I walked 600 kilometers in.

00:02:15.127 --> 00:02:17.453
You're American, what is a kilometer?

00:02:17.453 --> 00:02:21.424
But 600 kilometers in like two months or something.

00:02:22.044 --> 00:02:22.806
Kilometers works.

00:02:22.806 --> 00:02:25.689
I'm not American, I'm Kiwi, so we are in kilometers.

00:02:25.689 --> 00:02:28.754
Perfect, that's perfect, nice nice.

00:02:31.846 --> 00:02:34.157
Wow, that's a lot of walking.

00:02:34.157 --> 00:02:36.449
And yeah, I have my wife.

00:02:36.449 --> 00:02:39.961
We met in high school, so stuck with her ever since.

00:02:39.961 --> 00:02:41.343
Still love each other for some reason.

00:02:41.343 --> 00:02:49.612
We're insane like that and our daughter just turned one year just a week ago.

00:02:50.574 --> 00:02:53.580
Very cool, very cool, I love.

00:02:55.044 --> 00:02:56.669
Denmark yeah, I love it as well.

00:03:00.552 --> 00:03:01.638
I don't want to leave.

00:03:01.638 --> 00:03:11.979
So my wife and I were in Denmark and we had an Airbnb and we did a design thinking exercise on the wall to set out where we wanted to be in the future and we put up all our dreams, aspirations, desires.

00:03:11.979 --> 00:03:14.747
We'd been traveling the world for some time at this point.

00:03:14.747 --> 00:03:20.382
We recently went and looked at the photos that we'd taken in that Airbnb.

00:03:20.382 --> 00:03:22.384
Every one of our dreams have come true.

00:03:22.384 --> 00:03:33.949
Every one of the things we you know we didn't own any house, property, land, we didn't have children All the things that we desired in our careers, and everything.

00:03:33.949 --> 00:03:43.372
Everything came to pass that we put in our like our five, 10 year vision, that we put up in that Airbnb in Denmark, in Copenhagen.

00:03:44.061 --> 00:03:45.165
Crazy, crazy.

00:03:45.165 --> 00:03:49.692
So just the atmosphere, it's the atmosphere man, it's a great city.

00:03:49.740 --> 00:03:51.105
I've got two nephews that are Danish.

00:03:51.105 --> 00:03:57.131
My brother married multiple Danish women over his life.

00:03:57.131 --> 00:04:03.569
He seemed to have a taste for them, and so, yeah, I've got two Danish nephews.

00:04:03.569 --> 00:04:05.447
They'd be in their late 20s now.

00:04:05.447 --> 00:04:10.712
One's in the military there and the other one's into, uh, audio production.

00:04:10.712 --> 00:04:14.782
Um, but, yeah, yeah, yeah, yeah, so I do.

00:04:14.782 --> 00:04:17.269
I do have a, uh, a connection to denmark.

00:04:17.269 --> 00:04:21.425
Tell me about how you got into tech uh.

00:04:21.504 --> 00:04:27.019
So I originally thought, you know, when I was in what was that 9th grade?

00:04:27.019 --> 00:04:30.466
Or something that I was going to do a lot with money and finance and so on.

00:04:30.466 --> 00:04:51.632
But then there was this high school teacher in the first year of high school that showed me I could do websites and build them on my own, and I was gaming a lot back then 12-14 hours a day in world of warcraft so having a job that you can do on your computer sounded perfect for me.

00:04:51.632 --> 00:04:55.701
So began building websites for small businesses.

00:04:55.701 --> 00:05:02.394
Uh, began building apps and so on and uh, yeah, things just rolled from there.

00:05:02.394 --> 00:05:04.798
Yeah, things just rolled from there.

00:05:04.798 --> 00:05:11.199
Became a dynamics developer during my university studies and began building tools from there.

00:05:11.199 --> 00:05:14.149
Yeah, just stuck with it ever since.

00:05:15.000 --> 00:05:17.629
So when you say dynamics, are you on the F&O or CE side?

00:05:18.161 --> 00:05:18.744
CE side.

00:05:18.744 --> 00:05:20.846
Yeah, funny thing about that, though.

00:05:20.846 --> 00:05:23.146
I've never touched a first-party product in my life.

00:05:24.230 --> 00:05:24.959
Wow, so you just do model-driven apps, so you use a clean dataverse.

00:05:24.959 --> 00:05:25.704
Perfect thing about that though I've never touched the first party product in my life.

00:05:25.704 --> 00:05:30.634
Wow, so just you do, you just do model driven apps so you use clean dataverse perfect, perfect.

00:05:30.634 --> 00:05:33.317
Um, it's uh, I love that.

00:05:33.317 --> 00:05:33.841
I love that.

00:05:33.920 --> 00:05:54.314
Tell me about xrm tooling wizard yeah, the idea was just, you know, I saw everyone who had some fancy name and then I thought, the people that I saw who built tools, they built you know one or two, but at that point as a student I I had built one and I was maintaining three others.

00:05:54.314 --> 00:06:03.206
So I mean I I thought I could grab that and then later on I just dropped the tooling part of it because I mean I knew a lot about the platform anyway.

00:06:03.206 --> 00:06:07.983
So I mean I loved Harry Potter and XM Wizard seemed fine.

00:06:08.245 --> 00:06:09.206
So I love it.

00:06:09.848 --> 00:06:10.329
I love it.

00:06:10.329 --> 00:06:15.975
I also didn't use LinkedIn for anything at that point, so my LinkedIn tag is also XM Wizard.

00:06:15.975 --> 00:06:19.944
I don't know when that's going to bite my ass at some point in 40 years or something.

00:06:19.964 --> 00:06:23.271
But I think it's very cool.

00:06:23.271 --> 00:06:31.233
I mean you can change it at any time and so you know when you look at what you do in the community, kind of what are you known for.

00:06:33.161 --> 00:06:33.983
What do people come to you for?

00:06:33.983 --> 00:06:35.045
Deep technical knowledge?

00:06:35.045 --> 00:06:36.850
I would say so.

00:06:36.850 --> 00:06:41.992
So my, the tool that I've built is just a copy of a dataverse basically.

00:06:41.992 --> 00:06:43.826
So it like fake XMEC.

00:06:43.826 --> 00:07:02.627
It knows how to run business logic from Dataverse locally so developers can test stuff without contacting a real environment, and in that I have had to experiment a lot with what Dataverse can do and all the quirks and so on.

00:07:02.627 --> 00:07:04.654
So of course that gains you some knowledge.

00:07:04.654 --> 00:07:09.125
I have built an interpreter for the old classical workflows so on, so of course that gains you some knowledge, like I've built an interpreter for the old classical workflows so they can run locally.

00:07:09.125 --> 00:07:15.569
That was a lot of fun, you know, pulling out the definitions of the workflow and looking at how it works and so on.

00:07:17.802 --> 00:07:24.391
So when you did that, did you kind of because that was built on Windows Workflow Foundation, right.

00:07:24.391 --> 00:07:28.230
So do you have a local instance of that running?

00:07:28.230 --> 00:07:31.129
Are you using that or did you create a full new version?

00:07:31.759 --> 00:07:35.170
Just create my own custom interpreter in C Sharp.

00:07:35.170 --> 00:07:49.649
So taking that SAML definition, compiling it over to some classes In academia, you would call it an abstract syntax tree and then you run an interpreter on that and then, yeah, then you have an interpreter.

00:07:49.649 --> 00:07:50.541
It took two months to build.

00:07:50.541 --> 00:07:54.011
You know as my part-time stuff doing as a study.

00:07:55.274 --> 00:07:55.735
That's epic.

00:07:55.735 --> 00:08:09.098
So what are your thoughts between Power Automate and what was provided in that workflow tool that was part of the original Dynamics product.

00:08:11.151 --> 00:08:14.382
The most sad part is that Power Automate is asynchronous.

00:08:14.382 --> 00:08:26.937
So if you want to Google my name, you can probably find some super old article where, when Power Automate came out, I said that it would suck, it wouldn't scale and so on.

00:08:26.937 --> 00:08:37.941
And the whole point is that if all of your business logic is running asynchronously, your data quality is going to go bad, and that was the great part about the classical workflows was that they can run synchronously.

00:08:38.509 --> 00:08:40.556
You know they only could run synchronously.

00:08:40.556 --> 00:08:41.899
I thought towards the end.

00:08:41.899 --> 00:08:51.211
I don't remember the OG product having the synchronous functionality, like back in 20 crm4 days and things like that.

00:08:51.331 --> 00:09:03.307
Now it could be wrong, but I thought, but at least the 2011, they had it so yeah, yeah power debate is pretty old by that standard, so they haven't followed suit so, so.

00:09:03.687 --> 00:09:06.413
So let's unpack this because it was interesting.

00:09:06.413 --> 00:09:28.692
Ryan cunningham coined this term in the fullness of time that it would achieve that, and Steven Siciliano, who then was the Power Automate owner for some time, coined that some years ago when it first came out, because our biggest complaint was when are you going to give us parity with what we had with Windows Workflow Foundation in Power Automate?

00:09:28.692 --> 00:09:30.523
Was, when are you going to give us parity with what we had with windows workflow foundation in power automate?

00:09:30.523 --> 00:09:31.484
And of course, we're now.

00:09:31.484 --> 00:09:31.964
What?

00:09:31.964 --> 00:09:32.644
Uh?

00:09:32.644 --> 00:09:35.187
2017, 2016?

00:09:35.187 --> 00:09:37.370
That's a long time ago, right where?

00:09:37.370 --> 00:09:39.572
And it still hasn't come about.

00:09:39.572 --> 00:09:51.667
Why do you think it's one not being a desire from the product team to get the synchronous functionality in there?

00:09:51.667 --> 00:09:56.923
Is it just too big a challenge for them to solve in the architecture they've created with Power Automate?

00:09:57.210 --> 00:09:59.193
I mean we've also created we.

00:09:59.193 --> 00:10:05.063
I say I have a colleague who created an interpreter and I gave him comments on it for CloudFlows.

00:10:05.063 --> 00:10:09.240
So there's a pretty big difference in how they're written.

00:10:09.240 --> 00:10:20.436
They are much more abstract, so it's easier for them to add more connections and so on, but it also means that it's harder for you to run an interpreter that doesn't spin up stuff.

00:10:20.436 --> 00:10:27.149
So, inherently, power Automate interpreting is slower than classic workflows.

00:10:27.149 --> 00:10:31.988
Currently, power Automate interpreting is slower than classic workflows.

00:10:31.988 --> 00:10:40.009
So I think a much more fast and easy transition would be the low-code plugins or whatever they might be called in the future.

00:10:40.009 --> 00:10:40.190
Right?

00:10:42.092 --> 00:10:45.240
Okay, so is that the future way to do things you're thinking?

00:10:45.761 --> 00:10:46.322
Yeah, I think so.

00:10:46.912 --> 00:11:04.057
Low-code plugins addresses the scenario and the problem, though, I suppose, with the low-code plugins, which you didn't have with Workload Foundation, was a GUI that allowed a quote citizen developer to build them.

00:11:04.970 --> 00:11:18.529
But I think with natural language, helping writing formulas and so on, I think having a GUI is more of a hindrance than just having something helping out writing formulas.

00:11:18.529 --> 00:11:25.779
I think the actual media that we interact with will change in the next five to 10 years anyway.

00:11:25.779 --> 00:11:36.317
I think everything will be more abstract, right, but the Power Fx will have the same strength in that it can use all the connections, but it's inherently more lightweight.

00:11:36.317 --> 00:12:03.278
So if you think that you can still have named formulas and so on so you can break down your big complex logic, but you can still do the same stuff that you can call the environment, so you can call custom APIs or actions that you can patch and retrieve and so on, the real big gap right now is that the triggers are not as sophisticated as plugins.

00:12:03.278 --> 00:12:21.419
If there was full parity for these local plugins as plugins, that they can have access to the same plugin execution context, then I don't see a reason why a lot of the simple stuff wouldn't be written in that Interesting, and why do you think that is not there?

00:12:22.951 --> 00:12:25.259
I just think it hasn't been a focus.

00:12:25.259 --> 00:12:32.197
I mean, you must also have realized that as long as as well as everyone who's listening that AI has been a great focus.

00:12:32.197 --> 00:12:37.716
I think everything that was on the board two years ago has been pushed.

00:12:37.716 --> 00:12:49.558
But looking at the release wave that we've seen now, it seems like they're picking up steam again and actually fixing stuff on the platform, but there's been a one and a half year gap.

00:12:50.812 --> 00:13:00.206
So I made a prediction last week that Power Automate will disappear into the background in the next five years.

00:13:00.206 --> 00:13:12.711
Developer or configurer.

00:13:12.711 --> 00:13:55.150
Because I believe that, as speech becomes ubiquitous in how we interact with AI, that although AI will build out the automations for us, there will be no need for us to go in and build out an automation as such as that we would, you know, maybe hit a record button on our screen and show kind of what's already been proposed, or literally just talk to it and say I need an automation that does this and it might, you know, schematic that up on screen for you and you might yeah, I need this to happen at this point and basically verbally go through and then behind the scenes, it'll go okay, I need these connectors to do that, and then, if they're not, don't exist, it'll build them and, and you know, you'll provide access to data sets etc.

00:13:55.150 --> 00:13:58.376
Um, it'll have a full formula engine in it.

00:13:58.697 --> 00:13:59.278
Blah, blah, blah.

00:13:59.278 --> 00:14:00.942
Do you see that?

00:14:00.942 --> 00:14:03.432
That's, you know, the, the demand.

00:14:03.432 --> 00:14:13.586
For you know, in the last five, ten years I've seen a lot of people put you know their power automate guru on their profiles and stuff and really built a brand around that.

00:14:13.586 --> 00:14:17.697
Do you see it all kind of just disappearing into the background.

00:14:17.697 --> 00:14:20.062
As in that, ai will be our interface.

00:14:21.071 --> 00:14:30.279
It depends on how slow we as consultancies and so on are changing, but I definitely think that the future is that direction.

00:14:30.279 --> 00:14:40.937
The future will be that systems describe how data should be understood in their domain, and so that would be kind of closed source.

00:14:40.937 --> 00:14:46.614
So let's say you have a warehouse system In your system.

00:14:46.614 --> 00:14:51.878
You know what an item is in a warehouse, but how an item gets in there.

00:14:51.878 --> 00:14:55.394
You might have a single interface for adding items.

00:14:55.394 --> 00:15:00.255
But from the rest of the business perspective, you don't really care.

00:15:01.691 --> 00:15:19.236
Your solution that you've built still on Dataverse, still on so on, you have all your business logic that runs, hopefully, synchronously, so your data remains intact, is is full of your domain knowledge, and then you have these points in.

00:15:19.236 --> 00:15:30.457
And that's where your point is right that right now we would put your Power Automate guru in there and have them describe exactly how these different systems should connect.

00:15:30.457 --> 00:15:33.238
I definitely think that layer will be blurred out.

00:15:33.238 --> 00:15:44.777
As long as your warehouse system can describe how to interact with it well enough, such that an AI can interact with it, there's no reason why you need the logic.

00:15:45.629 --> 00:15:47.356
Have you looked at semantic kernel?

00:15:49.552 --> 00:15:50.416
No, I don't think so.

00:15:51.912 --> 00:16:16.857
So Microsoft announced it in July this year and it's pretty mind-blowing because I watched last week a demonstration of a shopping cart scenario where somebody says you know, the shopping cart metaphor, right, based on kind of a supermarket checkout, is cumbersome and particularly if you're elderly, right as a necessary, understand that, and so I noticed this example.

00:16:16.857 --> 00:16:24.432
So, using voice interaction, it said you know, somebody goes to the websites that has a catalog of products and just said I need some boots.

00:16:24.432 --> 00:16:26.758
And they showed that in semantic kernel.

00:16:26.758 --> 00:16:28.341
Well, what's a boot?

00:16:28.341 --> 00:16:29.283
Right?

00:16:29.283 --> 00:16:33.919
So, using generative AI, then it can say a boot is this type of thing.

00:16:34.019 --> 00:16:41.741
Oh, we, and you hand that to the API, the product API, and says okay, do you have a product that has a dimension called boot?

00:16:41.741 --> 00:16:42.803
Yeah, I do.

00:16:42.803 --> 00:16:45.174
Well, can you display those on screen?

00:16:45.174 --> 00:16:46.419
Great, there they are.

00:16:46.419 --> 00:16:48.155
I want a black boot?

00:16:48.155 --> 00:16:54.601
Well, it has no concept of black, yellow, green, but we can go, hang on a second.

00:16:54.601 --> 00:16:55.943
What is black?

00:16:55.943 --> 00:17:00.365
And your generative AI goes well, black is a color, is a color.

00:17:00.365 --> 00:17:02.111
And so, okay, do we have a dimension called black?

00:17:02.152 --> 00:17:07.996
Yeah, here's a, you know, and all of a sudden, the way you're going to interact becomes pretty compelling, right?

00:17:07.996 --> 00:17:16.026
Well, I'll have two of those and, by the way, just use my credit card to to complete the, the purchase, rather than you know.

00:17:16.026 --> 00:17:18.720
And you might have a validator saying put your cv, cvc or whatever it is, you know code in what.

00:17:18.720 --> 00:17:22.375
Might have a validator saying put your CVC or whatever it is, you know code in what is it and it just give it to you.

00:17:22.375 --> 00:17:32.592
It might give it to you auditory and all of a sudden the way we can create experiences for people massively changes by using this kind of.

00:17:32.592 --> 00:17:34.757
So check out Semantic Kernel.

00:17:34.757 --> 00:17:41.871
Anyhow, I'm a big fan because it's kernel.

00:17:41.871 --> 00:17:44.576
Anyhow, I'm a big fan because it's very human, readable code and what it gets, what's generated.

00:17:44.576 --> 00:17:55.833
And I just see a lot of runway in the area of the power, platform dynamics, that type of thing of where this is going to be incredibly powerful tool to create new experiences yeah, and of course it's.

00:17:55.992 --> 00:17:57.195
it's easy to get hyped right.

00:17:57.195 --> 00:18:01.624
My big worry is that I can see the vision.

00:18:01.624 --> 00:18:05.019
I can see that there will no longer be a Canvas app, a model-driven app.

00:18:05.019 --> 00:18:08.240
You just have a blank screen and it auto-generates whatever UI you want.

00:18:08.240 --> 00:18:13.000
But I am much more interested in how close are we now?

00:18:13.000 --> 00:18:22.065
How close is Code Interpreter in ChatGPT to be able to generate a React app for me that can interact with an API?

00:18:22.065 --> 00:18:34.961
It's not there yet, but I would love for these examples to be what we study, because it's super easy to talk about five to ten years.

00:18:34.961 --> 00:18:36.655
Who the fuck is going to check up?

00:18:37.990 --> 00:18:39.096
Yeah, exactly right.

00:18:39.550 --> 00:18:40.855
It's much easier to figure out.

00:18:40.855 --> 00:18:41.638
What can you do now?

00:18:41.638 --> 00:18:47.136
You can point Copilot to your Dataverse database and it can answer some stuff.

00:18:47.136 --> 00:18:52.338
It can probably not answer stuff if you have a complex table structure.

00:18:52.338 --> 00:18:55.676
So it's not there yet.

00:18:55.676 --> 00:19:07.142
It can probably get there, but there are a lot of scenarios, like user guidance, where you can point it to some documentation you have and so on.

00:19:07.142 --> 00:19:09.215
That might be a good idea.

00:19:09.215 --> 00:19:11.295
How do I do stuff?

00:19:11.295 --> 00:19:16.338
Well, if you have written pretty good documentation, why not just give it to Copilot and then it can figure it out?

00:19:17.371 --> 00:19:18.453
So a lot of these.

00:19:18.453 --> 00:19:23.858
I need to read a lot of documents in order to understand something.

00:19:23.858 --> 00:19:38.202
It can do that now, and I'm guessing you must have read a lot of the examples of different businesses that are using generative AI now in success A lot of them.

00:19:38.202 --> 00:19:41.038
We've also built a bunch of these systems.

00:19:43.954 --> 00:20:10.143
They have a lot of cases and usually there are a lot of documents tied to it, and it makes it a lot easier for them to read a summary from generative AI and then they can dig into the documents if they need to, rather than they have to figure it out, and a lot of these cases also have pretty short SLAs, which allows them to actually read through stuff and maybe win more cases and so on.

00:20:10.143 --> 00:20:18.695
Maybe, yeah, solve them faster or at least you know, do them thoroughly enough, follow company policy and so on, a lot of these different companies.

00:20:18.695 --> 00:20:24.136
They aren't following their own compliance internally because there's not enough time, right?

00:20:24.136 --> 00:20:33.896
So that is what we can do now, and I'm much more interested in what is the next six months in the year, because I don't think anyone knows any more than that anyway.

00:20:34.538 --> 00:20:34.700
Yeah.

00:20:34.700 --> 00:20:43.333
So with that in mind, final question for you is what are you learning, what are you studying?

00:20:43.333 --> 00:20:44.356
What is your focus?

00:20:44.356 --> 00:20:46.196
That is only six months out.

00:20:47.990 --> 00:20:52.373
Right now it is a lot on how we can do so.

00:20:52.373 --> 00:20:53.705
It's not AI focused at all.

00:20:53.705 --> 00:21:03.625
Actually, it's how we can get to the actual treat your environments as cattle and not kittens story.

00:21:03.625 --> 00:21:12.183
So Microsoft has been pushing this narrative a lot, that they want you to spin up environments whenever you create a new feature and then merge it in and then deploy it.

00:21:12.183 --> 00:21:14.257
But the story hasn't really been there.

00:21:15.891 --> 00:21:28.857
But I do believe that in the next six months to a year we will get to that point and I can do my part from community tooling that a lot of community tooling right now needs an environment to run.

00:21:28.857 --> 00:21:38.857
But if the stuff that is stored inside of your version control is good enough, in a good enough format, then we can also point to that instead.

00:21:38.857 --> 00:21:42.832
Stuff that is stored inside of your version control is good enough in a good enough format, then we can also point to that instead.

00:21:42.832 --> 00:22:02.579
And if the act of spinning up new environments becomes faster, if we can configure them correctly, then it becomes much faster and safer to be a lot of developers on the same team.

00:22:02.579 --> 00:22:11.800
So right now I'm on a project where I think we are 15, 17 developers on the same environment, right, and we are stomping on each other's toes.

00:22:11.800 --> 00:22:23.862
We have reduced the stomping a lot because we can do local testing and so on, but we're still creating these fields on the same entities.

00:22:23.862 --> 00:22:27.140
That will just cause problems.

00:22:27.140 --> 00:22:31.276
So that is my focus I want environments to be cattle.

00:22:31.817 --> 00:22:32.420
How do you solve that?

00:22:32.420 --> 00:22:38.901
Because what you just described there, I can remember in CRM four days that being a problem.

00:22:38.901 --> 00:22:58.815
In this case it would be three different Microsoft partners working with the same customer and you would get this overwriting happen of solutions or customizations built in the system, being the last person in wins type thing, and it would create problems.

00:22:58.815 --> 00:23:01.759
How far down the solved path are we?

00:23:02.580 --> 00:23:05.285
wins type thing and it would create problems.

00:23:05.285 --> 00:23:07.328
How far down the solved path are we?

00:23:07.328 --> 00:23:08.049
We will be far down soon.

00:23:08.049 --> 00:23:15.922
So the reason I can't say specifics is that it's a private preview running right now, but it should have been announced last week, I think so.

00:23:15.922 --> 00:23:17.535
So it's out soon.

00:23:17.535 --> 00:23:22.692
It's the new uh git solution structure, right, it's.

00:23:22.692 --> 00:23:28.020
It's in the release wave, so we can say that much um.

00:23:28.541 --> 00:23:30.371
But that story will become much better.

00:23:30.371 --> 00:23:38.561
And previously it's only been a demand from a developer point of view, because we know better I mean, get off my high horse and so on.

00:23:38.561 --> 00:23:44.479
But we know how software development can be done in parallel because we have version control and stuff like that.

00:23:44.479 --> 00:23:59.420
And if that story gets better from a platform point of view and it becomes easy for people who just sit inside Make, then the storytelling gets better at least.

00:23:59.420 --> 00:24:11.696
And it's also something I will talk about in the new year at different conferences, because it is such a pain that you can't be many developers on the same project, right.

00:24:11.696 --> 00:24:21.760
And yeah, just the last part that I don't expect Microsoft to fix is just the community tooling part.

00:24:21.760 --> 00:24:26.662
If we have a good enough story that matches what Microsoft is doing, then we'll also keep investing in it.

00:24:26.662 --> 00:24:28.234
That's how it's always been.

00:24:33.271 --> 00:24:34.296
Hey, thanks for listening.

00:24:34.296 --> 00:24:40.423
I'm your host business application MVP Mark Smith, otherwise known as the NZ365 guy.

00:24:40.423 --> 00:24:46.702
If you like the show and want to be a supporter, check out buymeacoffeecom forward slash NZ365 guy.

00:24:46.702 --> 00:24:49.151
Thanks again and see you next time.

00:24:49.151 --> 00:25:29.490
Thank you.

Magnus Gether Sørensen's Tech Journey and the Role of Generative AI

Listen On

Recent Episodes

Power Platform Show Episodes

MVP Show Episodes

Power 365 Show Episodes

Ecosystem Show Episodes

Copilot Show Episodes

Browse episodes by category

Magnus Gether Sørensen's Tech Journey and the Role of Generative AI

Join over 1500 Power Platform & Dynamics 365 pros for a quick, fun, and insightful 4-minute read each week!

Subscribe to Tech Trailblazer newsletter

Listen On

Recent Episodes

Power Platform Show Episodes

MVP Show Episodes

Power 365 Show Episodes

Ecosystem Show Episodes

Copilot Show Episodes

Browse episodes by category