At this point, we have seen how you can achieve a more robust variant of a composition by delegation rather than inheritance.
You can also use this if you are confronted with legacy source codes with this anti-pattern.
It’s not always possible to clean up everything or change it to the last detail.
But I hope this has given an incentive to approach this situation.S. Ruppert
Even as a software developer, you will often hear this phrase during meetings with the company’s management and sales part. The phrase is called “Make or Buy”. Typically, we have to decide if we want to do something ourselves or spend money to buy the requested functionality. It could be less or more functionality or different so that we have to adjust ourself to use it in our context.
But as a software developer, we have to deal with the same question every day. I am talking about dependencies. Should we write the source code by ourselves or just adding the next dependencies? Who will be responsible for removing bugs, and what is the total cost of this decision? But first, let’s take a look at the make-or-buy association inside the full tech-stack.S. Ruppert