🚨 Quite often, to make our code simpler, we're trying to make our code more reusable and generic. I wrote an article with a warning that "generic" does not mean "simple". I did that on the example of #CQRS code evolution. Beware and have a read!

SourceGear.Llama.Swift.Sdk, now available on NuGet, is an MSBuild project SDK for .NET 5 that allows compiling Swift, with support for calling .NET class libraries. This blog entry is a closer look at those features. Reminder: Llama is at the "proof of concept" stage, and is not production ready. In my previous Llama blog entry, I walked through a simplistic implementation of "grep" in both C# and Rust. Let's revisit that sample now in Swift.The .swiftproj file Recall that the project file for the C#...

Today I want to invert the classical pro-agile drawing. Let’s talk about the devaluation of functionality that occurs in Agile projects and the cases when Agile is not enough.

This is next post in my little series on streaming JSON objects (NDJSON) in .NET. This one discusses how to send an async stream with HttpClient.

Snapshots in Event Sourcing are a controversial topic. It's tempting to use them, but in my opinion, they should be used only when you had to, as a technical optimisation technique. Read more in my latest article!

Today I'm sharing a sneak peek of our dev/docs process at Event Store. I'm doing that on the practical example of the custom Github Action that cherry-picks pull request commits to the different (e.g. release) branches to keep them in sync.

Pragmatic about programmingStartCategoriesAboutContact🇵🇱 oskar dudyczEvent Sourcing Autonomy is the Holy Grail for teams management. At least that’s how it’s perceived. It’s not easy to get the right balance. In this post, I'm talking about inverted Conway's law in a good sense. I’m explaining how doing event-based systems can help in running autonomous teams.

Events should be as small as possible, right? It's not so simple as it may sound. If you take this principle literally, then it may get you in serious troubles. Why? Read more in my latest post.

As you may know, I’m an active Open Source contributor. I decided to write a set of thoughts and suggestions based on my experience on starting your journey with Open Source.

It’s intriguing how our perspective on software development changed in the last few years. We transformed from the on-premise age to the cloud era. Cloud is no longer a “buzz word”. I wrote my (not) obvious observations on how money in Cloud impacts Architectural decisions.