Blog Posts

How do you convince management to invest time and money into refactoring your legacy monolith?

Where do you even begin when considering “fixing” or refactoring legacy monoliths? I’ve been thinking about this lately - as I’ve been doing it for the last month or so.

Let’s look at some different ways you could implement the strategy pattern in C#. First, I’d like to briefly mention why we care about design patterns and where the strategy pattern fits in. (Skip ahead if you want 😉)

In Martin Fowler’s “famous” article about fluent interfaces, he talks about how it’s beneficial (when using strongly typed languages) to have the return type of your fluent method be flexible. We’ll be looking at this advanced fluent interface technique today.

In my previous post I looked at a few reasons that I’ve seen given for thinking that fluent interfaces are “not all that.” I personally think that fluent interfaces can add some serious benefits to developers.

Are fluent interfaces evil? (As some might suggest)… I don’t think so. In fact, I think they are great.

I plan on doing a few posts around this topic in the coming days/weeks (I’m pretty busy…). I wanted to start by addressing some common arguments I’ve come across.

Update: I created a YouTube video based on this post, if you are interested.

During the past year and a half I have been making a point to learn about and develop my skills in functional programming. For the majority of this experience, I have been using JavaScript and TypeScript. After moving onto another project at work, I was brought back to “C# and SQL world.” Long story short, I noticed the way I was thinking about software problems in C# were totally different than before.