{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Rethinking the Single Responsibility Principle for Modern Software Teams","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/266e442f\"></iframe>","width":"100%","height":180,"duration":1120,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/rethinking-the-single-responsibility-principle-for-modern-software-teams.\nThe Single Responsibility Principle is useful, but misusing it can create fragmented code, bloated interfaces, and technical debt.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #software-engineering, #software-development, #agile, #refactoring, #solid-principles, #clean-code, #code-fragmentation, #software-architecture,  and more.\nThis story was written by: @kornilovconstru. Learn more about this writer by checking @kornilovconstru's about page,\n            and for more stories, please visit hackernoon.com.\nThe Single Responsibility Principle is useful, but misusing it can create fragmented code, bloated interfaces, and technical debt.\n        \n        ","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}