Which one of us doesn’t like to give commands? It’s the natural way to ask (in a polite way) for a specific task that needs to be completed. Therefore, it shouldn’t be surprising that the command pattern can be also easily implemented within our software, which might provide some serious benefits in terms of loose coupling the existing code.
Within the last few weeks, a lot of things have happened in terms of the Warden project.
It has gained already quite some popularity and became a whole stack of different applications and technologies with a single, ultimate goal which is providing the unified interface and set of tools to help you monitor and automatically resolve the issues with the maintenance of your system, infrastructure and resources.
If you take a look at the title of this post and instantly think it’s a trap or bait – let me prove you wrong. This is not going to be one of these catchy titles, so “what kind of bs am I going to read here” has little use in this place. Actually, this is 100% true that contributing to the open source community might greatly affect your life – and it goes far beyond daily activities related to the coding. Therefore, let me tell you a short story about a guy, typical .NET developer, who not so long ago also thought that being an open source developer literally means wasting your time.
Do you ever feel like (well, you should) these huge switch + case statements or too many ifs seem to be wrong? What if I told you, there’s one simple trick that will change your life, by getting rid of them? Ok, seriously – I have nothing against switch or if as the way of controlling the flow (I use them quite often) however, there are certain occasions at which the things could be done better. And let me show you another way to achieve the same goal which is much cleaner in terms of code readability and maintenance.