Refactor DAO.java #4
Description
I've selected DAO.java for refactoring, which is a module of 10 lines of code that couples the top-level components tightly. Addressing this will make our codebase more maintainable and improve Better Code Hub's Couple Architecture Components Loosely guideline rating! 👍
Here's the gist of this guideline:
- Definition 📖
Minimize the amount of interface code; that is, code in modules that are both called from and call modules of other components ("throughput"), and code in modules that are called from modules of other components ("incoming"). - Why❓
Having loose coupling between top-level components makes it easier to maintain them in isolation. - How 🔧
You can hide a component's implementation details through various means, e.g. using the "abstract factory" design pattern.
You can find more info about this guideline in Building Maintainable Software. 📖
ℹ️ To know how many other refactoring candidates need addressing to get a guideline compliant, select some by clicking on the 🔲 next to them. The risk profile below the candidates signals (✅) when it's enough! 🏁
Good luck and happy coding! 
✨ 💯