I have worked with and against different forms of code analysis tooling during my coding work. What I am usually very surprised about, is the importance that code analysis gets in software development. There is a place for code analysis, but it's not the independent ruler that will improve your system quality automatically when you follow its rules and that some companies would like it to be. In this article I will try to explain some of the issues that arise when applying these kinds of tools difficulties of these kinds of tools and why they are sometimes the sole anchor point in quality assessment.
With Blazor .Net, developers have been given a new way to create a web front-end with C# and HTML. Every application of considerable size needs some kind of design philisophy of how the different parts should work together. This article describes a Mvvm pattern, nicknamed "The Butterfly Pattern", and a sample prototype for Blazor.
As I was asked to organise one of the retrospectives for our team I had a look at several retrospective types. I found the sailboat retrospective to be most suitable to be adapted for our team. This small article shows how I applied the sailboat retrospective.