Let’s think of an imaginary company that has a product, built as a software monolith. This is not hard to imagine, right?

So, now let’s imagine a situation where the time comes for the company to slice the product technically, into a set of independent services.

The reason may be that codebase becomes hard to manage due to too big complexity, technical debts, or different scalability required for some parts of the application.

State pattern is a pretty nice solution for solving problems related to changing behavior of some component(class) at runtime, which varies depending on current state of that object.

In this article my goal is to help you become a very pragmatic software developer.

Someone may find this article way too opinionated. I'm fine with that, since it is.

Although this article is not strictly deeply technical, by reading it and sticking to the advices I'm giving you, you will benefit on your productivity side in the long run.

I thought it would be nice to use advantages of Kotlin language to showcase strategy pattern implementation. In order to get the example running – we need to install kotlin binaries (installation). I’m running simple Kotlin script in this example.

Ladies and gents, here’s one fairly short hint for anyone wondering how to query documents in Mongodb using regular expressions. Let’s get straight to the point:

For all of you that are just new to the topic, I'll try to make a concise introduction to the idea of unit testing.

Unit testing allows us to test our functions (This is most often the case, but we can also unit test other things as well - e.g class instance state, etc) in isolation, so that we can verify implementation correctness.

In this, relatively short post, I’ll try to cover some aspects of programming in Kotlin programming language that may give you a better context when deciding upon whether you may like to use it for your next project.

Let’s get started.