Tuesday 10 July 2018

Reasoning with SOLID Principles: Open Closed

Open Closed Principle

This principle is really great, basically setup your code so that new features are extensions to the existing code and not changes. Although I find it to be really useful I would recommend exercising caution when using it. It is very easy to overuse this principle and end up with a lot of unnecessary code ready to handle perceived future changes.

Identify the areas that are susceptible to change and the refactor them to the open closed principle. As a rule of thumb I would say the first time just write the code in the simplest way possible, then when a new feature is required add an if statement to incorporate the change. By the third or fourth time you should really be thinking about changing the code to accommodate future changes.

There are also times when it can be applied straight away, it seems to me a lot of good architecture is identifying which parts of the system are likely to change and planning this into your design. This does not mean you need to spend loads of time identifying which parts of the system these will be before hand and design them in. Refactor your design as they naturally appear in the course of development.

So this principle is yet another great thinking tool that should be applied with balance but when in doubt Keep It Simple Stupid.

1 comment:

  1. Instead, you pay a flat wager which gives you the possibility to win each attainable left-to-right symbol combination, regardless of the place the symbols land. 1024 ways to win slots have a 5-reels and 4-rows, with payouts made for getting matching symbol combos on adjoining reels in any 룰렛 place. There isn't any limit to the imagination in terms of|in relation to} slot themes.