Optimizing Your Time and Separating Responsibilities
It’s time for a little practice after all that theory! We’ve already seen a lot together: advanced principles on clean code, how to choose the right external libraries for your applications, and how to take advantage of the latest patches of these libraries while not risking making your project explode in mid-air. But we should not forget that there is the word “code” in “clean code” (obviously). In this chapter, we will therefore concentrate a little more on the source code of your application and see the following points:
- Naming conventions and organization of files and folders
- Why is it important to separate responsibilities to respect the “S” of the SOLID principles? What does it bring to you?
- We’ll discover an elegant way to manage responsibility separation with an event system
- And we’ll finish with some polymorphism—namely, abstract...