<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>single-responsability on Washington Botelho</title><link>http://www.wbotelhos.com/tags/single-responsability/</link><description>Recent content in single-responsability on Washington Botelho</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 18 Jul 2023 00:00:00 -0300</lastBuildDate><atom:link href="http://www.wbotelhos.com/tags/single-responsability/index.xml" rel="self" type="application/rss+xml"/><item><title>SOLID Principles</title><link>http://www.wbotelhos.com/solid-principles/</link><pubDate>Tue, 18 Jul 2023 00:00:00 -0300</pubDate><guid>http://www.wbotelhos.com/solid-principles/</guid><description>The SOLID Principles are five ways to make Object Oriented programming better to deal with.
Goal Explain each of the five principles:
(S)ingle Responsibility (O)pen Closed (L)iskov Substitution (I)nterface Segregation (D)ependency Inversion Single Responsability (SRP) &amp;ldquo;A class should have one, and only one reason to change.&amp;rdquo;
The point here is to make sure that one specific method should do only one thing, not two or more.
Imagine a method to display an account balance:</description></item></channel></rss>