#clean-code #solid-principles

idea

Components should do only one thing, and they should do the thing entirely.

“A module should have one, and only one, reason to change.”

Another way uncle Bob puts it, is that there should be a 1-1 mapping of a component and a business owner^[1].

links

Clean code

separation-of-concerns

references

[1]: Clean Architecture, Robert C. Martin, page 65:

“A module should be responsible to one, and only one, actor.”