<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Emirhan Kavgacı on Medium]]></title>
        <description><![CDATA[Stories by Emirhan Kavgacı on Medium]]></description>
        <link>https://medium.com/@emirhankavgaci127?source=rss-a37e82bf8543------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*VGs24AaxZzRpZOGb</url>
            <title>Stories by Emirhan Kavgacı on Medium</title>
            <link>https://medium.com/@emirhankavgaci127?source=rss-a37e82bf8543------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 07:19:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@emirhankavgaci127/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A short overview of coding world’s SOLID Principles — What are they ?]]></title>
            <link>https://medium.com/@emirhankavgaci127/a-short-overview-of-coding-worlds-solid-principles-what-are-they-4f6ae2b82d6e?source=rss-a37e82bf8543------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f6ae2b82d6e</guid>
            <category><![CDATA[solid]]></category>
            <category><![CDATA[short-read]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Emirhan Kavgacı]]></dc:creator>
            <pubDate>Thu, 25 Jul 2024 18:45:14 GMT</pubDate>
            <atom:updated>2024-07-25T18:45:14.515Z</atom:updated>
            <content:encoded><![CDATA[<h3>A short overview of coding world’s SOLID Principles — What are they ?</h3><p>SOLID principles , in the world of coding , you can say they are what holds a good piece of code together , like they might be the diferentiation between a code who is written by someone who just started object oriented programming and someone professional. So what does SOLID stand for ?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/1*7_6X_S94JbvZqoaGIus6Jw.png" /><figcaption><strong>SINGLE RESPONSIBILITY PRINCIPLE</strong></figcaption></figure><p><strong>Single Responsibility Principle : </strong>An object can only have one reason to change and it is called the responsibility of the class , it means that a class can only have one singular objective to complete. You can’t have one class to do more than one job. It must have one single focus like we can’t have one class do the operations for database and also have the codes for the customer manager class as it might lead to a conflict between the objectives of the classes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/1*ite_eEihV5heYrzqDR7E9Q.png" /><figcaption><strong>OPEN-CLOSED PRINCIPLE</strong></figcaption></figure><p><strong>Open-Closed Principle:</strong> A class or function should protect the attributes it already has. However, it should also be able to be improved without needing to change its core functionalities in any way. In short, the code should not be open to any changes, but it should be open to improvements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/1*sbpt97HVManf1KW99tSeGg.png" /><figcaption><strong>LISKOV SUBSTITUTION PRINCIPLE</strong></figcaption></figure><p><strong>Liskov Substitution Principle : </strong>Classes derived from a parent class should be able to replace their parent class in any given piece of code without needing to change the code itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/1*4RwjUfkuc3m0S_aznVE2Nw.png" /><figcaption><strong>INTERFACE SEGREGATION PRINCIPLE</strong></figcaption></figure><p><strong>Interface Segregation Principle: </strong>Instead of relying on one interface for all tasks, we should separate the tasks and have a different interface for each, specialized in its task. We shouldn’t add new functions to an interface to make it handle many tasks; we should create a new one without hesitation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/1*eJWIYoALCYQUkFxGL1c4JA.png" /><figcaption><strong>DEPENDENCY INVERSION PRINCIPLE</strong></figcaption></figure><p>Dependency Inversion Principle: Classes should be as independent of each other as possible. Higher-level classes shouldn’t depend on lower-level classes; instead, we can use abstractions or interfaces when needed.</p><p>And this is the end. Thank you for reading this brief overview of the famous SOLID principles in software development. I believe everyone interested in coding should know these principles and implement them in their code. Have a good day!</p><p>Now, I’ll provide the links to the icons I used, attributing them to their author:</p><ul><li>&lt;a href=”https://www.flaticon.com/free-icons/s&quot; title=”s icons”&gt;S icons created by Freepik — Flaticon&lt;/a&gt;</li><li>&lt;a href=”https://www.flaticon.com/free-icons/o&quot; title=”o icons”&gt;O icons created by Freepik — Flaticon&lt;/a&gt;</li><li>&lt;a href=”https://www.flaticon.com/free-icons/l&quot; title=”l icons”&gt;L icons created by Freepik — Flaticon&lt;/a&gt;</li><li>&lt;a href=”https://www.flaticon.com/free-icons/alphabet&quot; title=”alphabet icons”&gt;Alphabet icons created by Freepik — Flaticon&lt;/a&gt;</li><li>&lt;a href=”https://www.flaticon.com/free-icons/d&quot; title=”d icons”&gt;D icons created by Freepik — Flaticon&lt;/a&gt;</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f6ae2b82d6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>