{"podcast":{"title":"Programming Tech Brief By HackerNoon","slug":"programming-tech-brief-by-hackernoon-6364125","podcast_index_feed_id":6364125,"rss_url":"https://feeds.transistor.fm/programming-tech-brief-by-hackernoon","website_url":"https://hackernoon.com/c/programming","image_url":"https://img.transistorcdn.com/AKbQjnYbCNDgF_frZ_Hpi8tkLS7aZezqecpWn6o-Rh8/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.jpg","author":"HackerNoon","episode_count":100,"summary":"Learn the latest programming updates in the tech world.","last_synced_at":"2026-07-29T06:19:42.842448+00:00","page_url":"https://stenobird.com/podcast/programming-tech-brief-by-hackernoon-6364125"},"episode":{"title":"Rethinking the Single Responsibility Principle for Modern Software Teams","slug":"rethinking-the-single-responsibility-principle-for-modern-software-teams","published_at":"2026-06-11T16:01:00+00:00","page_url":"https://stenobird.com/podcast/programming-tech-brief-by-hackernoon-6364125/rethinking-the-single-responsibility-principle-for-modern-software-teams","show_page_url":"https://stenobird.com/podcast/programming-tech-brief-by-hackernoon-6364125","url":"https://share.transistor.fm/s/266e442f","audio_url":"https://media.transistor.fm/266e442f/42711133.mp3","summary":"This story was originally published on HackerNoon at: https://hackernoon.com/rethinking-the-single-responsibility-principle-for-modern-software-teams . The Single Responsibility Principle is useful, but misusing it can create fragmented code, bloated interfaces, and technical debt. Check more stories related to programming at: https://hackernoon.com/c/programming . You can also check exclusive content about #software-engineering , #software-development , #agile , #refactoring , #solid-principles , #clean-code , #code-fragmentation , #software-architecture , and more. This story was written by: @kornilovconstru . Learn more about this writer by checking @kornilovconstru's about page, and for more stories, please visit hackernoon.com . The Single Responsibility Principle is useful, but misusing it can create fragmented code, bloated interfaces, and technical debt.","meta_description":"This story was originally published on HackerNoon at: https://hackernoon.com/rethinking-the-single-responsibility-principle-for-modern-software-teams . Th…","key_points":[],"chapters":[],"topics":[],"duration_seconds":1120,"processing_state":"not_requested","actions":[{"name":"request_transcript","method":"POST","url":"https://stenobird.com/v1/public/podcasts/programming-tech-brief-by-hackernoon-6364125/episodes/rethinking-the-single-responsibility-principle-for-modern-software-teams/transcription-requests","description":"Idempotently request low-priority transcript generation for this episode."},{"name":"read_markdown","method":"GET","url":"https://stenobird.com/podcast/programming-tech-brief-by-hackernoon-6364125/rethinking-the-single-responsibility-principle-for-modern-software-teams.md","description":"Read the agent-friendly Markdown representation of this episode resource."}]}}