I was recently working on learning more about using Dataframes and Polyglot Notebooks with C# and needed some sample data to work with. At first I started by looking for some examples online, but I wanted to write a blog about my experience and wanted my own sample of data.

Assuming you are skilled in C# and the .NET ecosystem, you may be wondering if you need to learn Python to do data analysis or AI/ML. The short answer is you can do everything that Python does with C# and it will likely perform better and take less time to build in C#.

I was recently working through some automation challenges and looked up c# scripting options. I wasn't really expecting to find any compelling solutions, but the world of .NET is evolving at a rapid rate in the last few years and thought I'd try my luck. I was pleasantly surprised when the dotnet tool dotnet-script came up in my search. I had not seen this tool before and it started me on a path of evaluation.

The results of my recent experiment where I evaluated the new Blazor Server Side Rendering (SSR) to see how well it works for migrating from older MVC or Razor Page project incrementally.

I recently converted one of my example projects that used MVC controller based API, Marten Event Sourcing and Rebus to use Wolverine. This article contains some of my initial impressions of Wolverine in that experience and focuses on Wolverine.http API endpoints.

I have been digging into MartenDb and found a sample of the Event Sourcing features included in MartenDb. In this article I walk through this simple Event Sourcing example and describe what is happening.

In today's rapidly evolving business landscape, traditional linear business models are being disrupted by the emergence of platforms. Platform thinking offers a new paradigm for businesses to unlock their potential, create scalable ecosystems, and drive innovation. In this article, we will delve into the world of platform thinking, exploring its benefits and highlighting why businesses should consider adopting this strategic approach.

Goldratt provides 6 thinking processes as part of TOC and two of them are systematic approaches for resolving conflict. These thinking processes are Evaporating Cloud (Conflict Resolution Diagram) and Current Reality Tree (CRT). The evaporating cloud process is the simpler approach that can be used to solve most conflicts and is a frequently used tool in my toolbelt.

The Theory of Constraints (TOC) is a management philosophy and methodology developed by Eliyahu M. Goldratt. It focuses on improving organizational performance by identifying and addressing constraints, which are bottlenecks or limiting factors that impede the system's ability to achieve its goals.

I recently stumbled upon a Library called FastEndpoints while doing research and it immediately struck me as something I wanted to learn more about. I had started experimenting with Minimal APIs at the time. While I liked that Minimal APIs lower the entry point for simple API creation and are significantly more performant than MVC Controllers, they quickly turn your program.cs file into a jumbled mess with anything beyond trivial. The desire for code organization quickly pushes towards finding a sensible way to orient the code.