Michaël Hompus

ARM-wrestling? Use (your) bicep! EN

With the introduction of the Azure Resource Manager in 2014, Microsoft offered a way to describe our desired state of resources in Azure using ARM Templates.

For years, people have struggled with ARM templates: they are too verbose, too hard to write, too hard to read, too hard to learn, a lack of tooling support, etc. Some have switched to writing scripts using PowerShell, Azure CLI or now use third party software like Terraform.

With the introduction of Bicep, Microsoft has delivered a new DSL that should fix our issues with ARM templates, pump up our DevOps experience and slim down our code.

In this session I will show you why bicep might muscle its way into our hearts.

Use your source code to document your application EN NL

As a development team, writing documentation is often not our favorite activity. And keeping it up to date after every code change is a bigger challenge. Developers claim that the source code is the documentation itself, but do your stakeholders agree, do they actually read the code? And does it show how the parts are working together?

What if our source code would be the source of our documentation, for the team and our stakeholders?

In this session we will see how we can utilize Roslyn to generate documentation. Like creating diagrams that display the structure and relationships within an aggregate, or a sequence diagram that displays the flow throughout the application. We will render this using file formats such as PlantUML, Markdown and AsciiDoc.

After this session you will be able to let your source code speak in forms that your team and your stakeholders explain to the operation of your application.

Length: preferable 45-70 mins
Audience: dotnet, c# background helps, not required
Keywords: Documentation, Roslyn, dotnet, C#, DDD

Postponing architectural choices and start developing first with Dapr EN

When starting a new project, we tend to make a lot of architectural choices when it comes to components like (relational) databases, service busses, and deployment models like cloud and/or on premises. Most of the choices will be based on past experiences and upfront assumptions. But are they part of the right solution to your current challenge?
When you discover it is not the right fit, are you still able to change your code to use the better tool? Or is it now too expensive to change?

What if we could postpone our choices and just can start developing the right solution first and pick the right dependencies when we know which those are, or even keep it open until it is time to launch.

Dapr is a distributed application runtime which promises us we can postpone our decisions until we know what the right decision is. In this session we will discover how that is possible.

Achievement unlocked: use .NET to unlock Xbox achievements EN NL

While playing the movie trivia game "Scene It?" [https://en.wikipedia.org/wiki/Scene_It%3F] on my Xbox 360 back in 2007, I had the feeling that with a camera, computer, and some software, it should be much easier to get the correct answers to the questions in the game. But where to start?
Fast forward to today: Now I have lots of tools and frameworks at my disposal so I can use all my programming skills to build that application. To finish those achievements that eluded me for so long.

In this session I will go through the techniques that can be applied. You will see how we can use .NET Core with OpenCV, Azure Custom Vision, ML.NET, Tesseract OCR, and more, to answer every question the game will throw at us.