{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Finding the Stinky Parts of Your Code: Code Smell 256 - Mutable Getters","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/817a51ec\"></iframe>","width":"100%","height":180,"duration":176,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/finding-the-stinky-parts-of-your-code-code-smell-256-mutable-getters.\nAvoid mutable getters to protect your code's integrity and encapsulation. Learn how to return immutable copies in Java for safer and more predictable coding\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #clean-code, #code-quality, #code-refactoring, #refactor-legacy-code, #mutable-getters, #immutable-objects-java, #java-collections, #immutable-data-structures,  and more.\nThis story was written by: @mcsee. Learn more about this writer by checking @mcsee's about page,\n            and for more stories, please visit hackernoon.com.\nAvoid exposing mutable getters in your code to maintain object integrity and encapsulation. Use immutable copies or data structures to prevent unintended modifications and ensure thread safety.","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}