What is the Principle of Mutual Oblivion (POMO) and why is it important?
It's a software engineering principle that states that components or routines at the same level of abstraction should be unaware and independent of each other.
#90DaysOfProse
It's a software engineering principle that states that components or routines at the same level of abstraction should be unaware and independent of each other.
#90DaysOfProse
... with this pattern, functional units are designed with no knowledge of the outside world. The inputs and outputs are without any bias to the sender or receiver. They also shouldn't know the responsibilities of one another. #90DaysOfProse
Talk is cheap, show me the code...
... an example of co-routines that know too much.
buildSchema knows more than it should, thereby causing to change for more than one reason. Any changes to the schema deployment logic will mean that buildSchema has to be changed too.
... an example of co-routines that know too much.
buildSchema knows more than it should, thereby causing to change for more than one reason. Any changes to the schema deployment logic will mean that buildSchema has to be changed too.
one way to fix this will be to abstract the schema (the piece of work) away from the deployment strategy (worker)
#90DaysOfProse
#90DaysOfProse
Why is this important?
When software units are designed with a focus on a single responsibility, they become:
- very easy to test
- easier to refactor and extend
- reuse in a dissimilar context is easy peasy
#cleancode
#90DaysOfProse
When software units are designed with a focus on a single responsibility, they become:
- very easy to test
- easier to refactor and extend
- reuse in a dissimilar context is easy peasy
#cleancode
#90DaysOfProse
@threadreaderapp unroll
• • •
Missing some Tweet in this thread? You can try to
force a refresh
