ABSTRACT OF THE TOPIC
We have been running Blazor in production since 2019. Everyone on our team is a C# developer, so when we went into our latest project, Blazor was a natural choice, even though Blazor was only a week old. Looking at my peers working in the same space, I am convinced that it saved our project by switching to Blazor.
Even though it has been mostly smooth sailing, we have learned a lot during the years.
In this session, I will give you some tips, tricks, and learnings we have collected over the years, when to choose what, and how to avoid pitfalls in converting your existing project to Blazor.
--------------------------------------------------
SPEAKER'S BIO
Jimmy Engström has been developing ever since he was 7 years old and got his first computer. He loves to be on the cutting edge of technology, trying new things. When he got wind of Blazor, he immediately realized the potential and adopted it already when it was in beta. He has been running Blazor in production since it was launched by Microsoft.
He is the author of 'Web Development with Blazor' and the co-host of Coding After Work (podcast and stream).
His passion for the .NET industry and community has taken him around the world, speaking about development. Microsoft has recognized this passion by awarding him the Microsoft Most Valuable Professional award 9 years in a row.
He occasionally blogs at engstromjimmy.com.
www.codingafterwork.com
