Erik Heemskerk

htmx

htmx: Simplicity in an Age of Complicated Solutions

Almost four decades ago, Fred Brooks, software engineer and writer of The Mythical Man-Month, wrote:

NUKE

Reporting NUKE build failures on Slack

Let’s make our NUKE builds report failures by themselves, using a little reflection magic.

NUKE

Creating reusable build scripts with NUKE components

How can we take advantage of the latest C# features to create highly reusable build scripts with NUKE?

Event Feeds

Event Feeds: Simple and reliable messaging infrastructure

Event feeds are a simple mechanism to enable applications to react to things happening in other applications, reliably, consistently, and quickly.

Benchmarking

Revisited: Is WCF faster than ASP.NET Core? Of course not! Or is it?

Revisiting an article about how I got triggered after somebody exclaimed that WCF had lower response times than ASP.NET Web API and ASP.NET Core MVC.

Benchmarking

Is WCF faster than ASP.NET? Of course not! Or is it?

How does WCF, a 13-year-old mega-abstraction framework hold up against the modern, lean, ASP.NET Core? You’d be surprised.

.NET Core

PSA: Don’t change the assembly name for published NuGet packages

Somebody published a new version of a NuGet package with a different assembly name. You’ll never guess what happens next.

DDD

DDD Persistence: Recorded Event-Driven Persistence

When you decide to implement your business logic by applying DDD, one of the things you’ll run into is ‘how do I save my changes?’ The internet is full of blogs and a

C#

Transitive NuGet dependencies: .NET Core’s got your back

The other day, a colleague and I were looking into an issue with one of our solutions’ build pipeline. The main project was a ‘classic’ MSBuild project with a transitive NuGet dependency through another classic MSBuild project. The transitive dependency wasn’t being copied into the main project’s output …

Logging

Meaningful Logging and Metrics

Pretty much any application needs logging. Except maybe the simplest of applications that do not require user interaction and only do one incredibly specific thing. Or applications that only interact via the console. Pretty much any other application needs logging, though. When things are on fire, you need to be …

C#

C# 7.x and 8.0: Uncertainty and Awesomeness

Last week I wrote about the new features that Microsoft have planned for the next version of C#, version 7.1. Let’s also take a look at the things they have planned for a bit further out. Strap yourselves in, because this will be a rather long read.

C#

C# 7.1 and Beyond: Polishing Usability

Last year I talked about the new features of C# 7.0. Visual Studio 2017 has been released a few months ago, so you can now enjoy using these features in your day-to-day work. But Microsoft has, of course, not been idle in the meantime. They’ve detailed what …

Event Sourcing

Event Sourcing: Eventual Consistency and Responding to Events

In my last post, about CQRS and how to keep your read model synchronized, I mentioned how you could ‘broadcast’ your events to other parts of the system in order to keep read-optimized representations of your application’s state in sync with the actual state. You use an ‘event …

Event Sourcing

Event Sourcing: CQRS and querying using read models

In my previous post I introduced the concept of Event Sourcing, which is a radically different way of storing application state: instead of storing the current state, we only store the events that lead up to that state. More than one person asked the following question in response: how do …

Event Sourcing

Event Sourcing: Awesome, powerful & different

I was introduced to Event Sourcing by the CQRS Journey series of articles from Microsoft’s Patterns and Practices team. It’s an excellent read about a pattern that offers great flexibility, at a cost. Event Sourcing was mentioned as more of a side note, but I was immediately drawn …

Dependency Injection

Inspecting aspects and interception in .NET, part 3

Previously in this series, I looked at ways we can instrument our code with two of the most basic metrics; how often does our code run and how long does it take to execute? After settling on interception, we took a small detour and looked at how hard it is …

Benchmarking

Inspecting aspects and interception in .NET, part 2

Last time we evaluated a number of ways to add instrumentation to your code while keeping your code maintainable and legible. We landed on using interception and the cliffhanger question from last time was: what’s the overhead? Is it fast enough? In this post, we will start looking at …

C#

C# 7.0: Small but welcome improvements

I know I said the next post would be about benchmarking, and it was fully my intention, but then the real world happens. Recently, Microsoft announced the tentative feature-set of C# 7.0. Glancing over it, it looks like a similar improvement to what C

Benchmarking

Inspecting aspects and interception in .NET, part 1

Recently I was tasked with adding instrumentation to a project: measuring how often methods were being called and how long each execution took. I had a couple of options.