In a previous instalment, we identified the Config file as being a promising tool to map data reusable code to project-specific code. In this third article, we'll examine what our Settings page example looks like if we do indeed make use of such a Config file.
While the first part of this series identified the need to separate business-specific logic from reusable code, we haven't yet discussed how to best achieve this. Let's try to think it through...
How do you sell benefits when your potential customers haven't faced the problems yet? Sometimes, concepts that are useful and necessary in a given context are rendered meaningless when applied to a different context, making it difficult to explain these concepts in a handful of slides.
OOP lures you with the promise of making code reusable, but OOP syntax alone does not make your code reusable. Let's find out why that is, and how to really write reusable code.