<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>SOLID principle - Category - KLog</title><link>https://deploy-preview-3--cocky-keller-ea3c87.netlify.app/categories/solid-principle/</link><description>SOLID principle - Category - KLog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>lgx9587@gmail.com (Kevin)</managingEditor><webMaster>lgx9587@gmail.com (Kevin)</webMaster><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Sat, 27 Feb 2021 15:52:24 +1300</lastBuildDate><atom:link href="https://deploy-preview-3--cocky-keller-ea3c87.netlify.app/categories/solid-principle/" rel="self" type="application/rss+xml"/><item><title>SOLID principle in C#</title><link>https://deploy-preview-3--cocky-keller-ea3c87.netlify.app/posts/coding/solid_principle/</link><pubDate>Sat, 27 Feb 2021 15:52:24 +1300</pubDate><author>Author</author><guid>https://deploy-preview-3--cocky-keller-ea3c87.netlify.app/posts/coding/solid_principle/</guid><description>Youtube Origin Youtube channel link here
Udemy Full course on design patterns on .Net here
Single Responsibility Principle A class should have one, and only one, reason to change A class should only be responsible for one thing. There&amp;rsquo;s a place for everything and everything is in its place Find one reason to change and take everything else out of the class Very precise names for small classes &amp;gt; generic names for large classes namespace DotNetDesignPatternDemos.</description></item></channel></rss>