René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Refactor User.java","articleBody":"I've selected [**User.java**](https://github.com/tejada7/Java_IAM_Project/blob/b82dd4ae57617cf6bb51057df0908b778b3dedd5/EPITASpecialization_IAMCore/src/main/java/com/ftm/iamcore/datamodel/User.java#L1-L45) for refactoring, which is a module of **22** lines of code that couples the top-level components tightly. Addressing this will make our codebase more maintainable and improve [Better Code Hub](https://bettercodehub.com)'s **Couple Architecture Components Loosely** guideline rating! 👍 \r\n\r\nHere's the gist of this guideline:\r\n- **Definition** 📖 \r\nMinimize 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\").\r\n- **Why**❓ \r\nHaving loose coupling between top-level components makes it easier to maintain them in isolation.\r\n- **How** 🔧 \r\nYou can hide a component's implementation details through various means, e.g. using the \"abstract factory\" design pattern.\r\n\r\nYou can find more info about this guideline in [Building Maintainable Software](http://shop.oreilly.com/product/0636920049159.do). 📖 \r\n \r\n---- \r\nℹ️ 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! 🏁 \r\n\r\n\r\n----\r\nGood luck and happy coding! :shipit: :sparkles: :100:","author":{"url":"https://github.com/tejada7","@type":"Person","name":"tejada7"},"datePublished":"2020-03-27T22:53:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1/Java_IAM_Project/issues/1"}