At first sight it works out this new Unmarried Responsibility Principle (SRP), and particular interpretations out-of SRP you will find certain convergence. However, “carrying out something better” try another-during the angle; it’s the possessions of getting a particular, well-laid out, and complete mission.
Brand new SRP, regarding the terms from Robert C. Martin, exactly who coined the word, is that [code] “need to have you to definitely, and simply that, need to alter.” This new analogy on the Wikipedia article was a module that produces a study, in which you must look into the message and you can format of your own declaration just like the independent concerns that ought to live in independent groups, if not separate segments. When i told you in other places, for me, it brings phony seams, therefore the most commonly known case is the place the message and you will style of your study changes with her; a new profession, including, or a change to the reason of some investigation one to has an effect on one another its articles and in what way you want to display they.
Some other common condition is actually a good “UI role” in which SRP mandates that you independent the newest leaving and organization reasoning of your own component. Because a designer, having these staying in different places leads to an administrative task of chaining similar fields together. The greater number of risk is the fact this may be an early optimisation blocking an even more sheer breakup from questions growing because codebase grows, and as section arise you to definitely “carry out anything really” hence are more effective ideal for the domain brand of brand new state space. Once the any codebase develops, the amount of time will come to split up they with the sensible subcomponents, nevertheless the properties off Composability and Website name-dependent structure would-be a much better indicator off whenever as well as how and then make such structural alter.