<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Single-Responsibility-Principle on DATATWEETS</title><link>https://datatweets.com/tags/single-responsibility-principle/</link><description>Recent content in Single-Responsibility-Principle on DATATWEETS</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2025 Datatweets</copyright><lastBuildDate>Sun, 28 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://datatweets.com/tags/single-responsibility-principle/index.xml" rel="self" type="application/rss+xml"/><item><title>The Single Responsibility Principle: One Class, One Reason to Change</title><link>https://datatweets.com/blog/single-responsibility-principle/</link><pubDate>Sun, 28 Jun 2026 00:00:00 +0000</pubDate><guid>https://datatweets.com/blog/single-responsibility-principle/</guid><description>The Single Responsibility Principle says a class should have only one reason to change. See it in action: take a Python AuthService that also owns its logging, find why that&amp;rsquo;s a problem, and refactor it into clean, focused classes.</description></item></channel></rss>