<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>SOLID on Abhishek Shukla</title><link>https://abhishekshukla.dev/tags/solid/</link><description>Recent content in SOLID on Abhishek Shukla</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 22 Jun 2026 14:52:03 +0530</lastBuildDate><atom:link href="https://abhishekshukla.dev/tags/solid/index.xml" rel="self" type="application/rss+xml"/><item><title>Understanding SOLID Principles in Swift: Violations, Fixes, and Real-World Examples</title><link>https://abhishekshukla.dev/blog/solid-priciples/</link><pubDate>Mon, 22 Jun 2026 14:52:03 +0530</pubDate><guid>https://abhishekshukla.dev/blog/solid-priciples/</guid><description>&lt;p&gt;The &lt;strong&gt;SOLID&lt;/strong&gt; principles are five fundamental design guidelines in object-oriented programming intended to make software designs more understandable, flexible, and maintainable. These principles help developers avoid code smells, refactor easily, and build robust architectures.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s break down each principle with a real-world scenario, showing how it is commonly violated and how to properly fix it using Swift.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="1-single-responsibility-principle-srp"&gt;1. Single Responsibility Principle (SRP)&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Definition:&lt;/strong&gt; A class should have one, and only one, reason to change. Meaning it should only have one job or responsibility.&lt;/p&gt;</description></item></channel></rss>