Archive for March 2015

Week 14, year 2015

  • How to Send Emails the Right Way in a CQRS System - Where do you put code for sending emails? Sounds simple right? The funny thing is that if you’re adding it to a CQRS system it can be a little tricky. Why? It all depends on when you send them. Too early and other processes may fail and you end up sending your email half cocked. […] [Learn CQRS and Event Sourcing]
  • How we think - Did you think about how we think? How do we come up with a solution and how we decide whether it’s good or bad? It seems like a very interesting topic, so let’s dive in! [Enterprise Craftsmanship]
Permalink | From 30 March 2015 to 05 April 2015 | Last updated on: Mon, 7 Jun 2021 09:11:15 GMT

Week 13, year 2015

  • 8 Resharper shortcuts everyone should know - If you use Resharper, you must have been using some (or maybe most) of its features already. But what I see a lot is that some really useful features are left unattended. I want to describe those lesser known yet very useful features that can help you in your day-to-day work. [Enterprise Craftsmanship]
Permalink | From 23 March 2015 to 29 March 2015 | Last updated on: Mon, 7 Jun 2021 09:11:15 GMT

Week 12, year 2015

  • Functional C#: Handling failures, input errors - The topic described in this article is a part of my Applying Functional Principles in C# Pluralsight course. In this article, I’m going to write about how to deal with failures and invalid input in a functional way. Functional C#: Immutability Functional C#: Primitive obsession Functional C#: Non-nullable reference types Functional C#: Handling failures and input errors Handling errors in C#: the common approach The concept of validation and error processing is well known, but the code required to handle it may become really annoying in languages like C#. [Enterprise Craftsmanship]
Permalink | From 16 March 2015 to 22 March 2015 | Last updated on: Mon, 7 Jun 2021 09:11:15 GMT

Week 11, year 2015

  • Functional C#: Non-nullable reference types - The topic described in this article is a part of my Applying Functional Principles in C# Pluralsight course. This is the third article in my Functional C# series. Functional C#: Immutability Functional C#: Primitive obsession Functional C#: Non-nullable reference types Functional C#: Handling failures and input errors C# non-nullable reference types: state of affairs Look at the code example below: [Enterprise Craftsmanship]
  • Event Storming, Storytelling, Visualisations - Visual storytelling through Event Storming Last week, my client’s Chief Product Owner announced to the team they would introduce a set of new requirements using Event Storming, “as Mathias has taught us”. (I’ve visited there regularly for the past half year or so). The session took about ten minutes, and included no brainstorming or collaboration of any kind. The only thing it had in common with Event Storming, was that the PO used colorful stickies. I was of course sceptical at first, but it turned out to be quite interesting in its own right, as a presentation technique. The Chief PO and his team were well prepared. [Mathias Verraes]
Permalink | From 09 March 2015 to 15 March 2015 | Last updated on: Mon, 7 Jun 2021 09:18:52 GMT

Week 10, year 2015

  • Functional C#: Primitive obsession - The topic described in this article is a part of my Applying Functional Principles in C# Pluralsight course. This is the second article in my Functional C# blog post series. Functional C#: Immutability Functional C#: Primitive obsession Functional C#: Non-nullable reference types Functional C#: Handling failures and input errors What is primitive obsession? Primitive obsession stands for using primitive types to model domain. [Enterprise Craftsmanship]
  • Functional C#: Immutability - The topic described in this article is a part of my Applying Functional Principles in C# Pluralsight course. I’m starting a series of articles in which I want to show how to program in C# in a more functional way. Functional C#: Immutability Functional C#: Primitive obsession Functional C#: Non-nullable reference types Functional C#: Handling failures and input errors Why immutability? [Enterprise Craftsmanship]
Permalink | From 02 March 2015 to 08 March 2015 | Last updated on: Mon, 7 Jun 2021 09:11:15 GMT