Day 58 SOLID Methodology
Whats up coding fam today I came across a new methodology that I’m hype about. The reason I’m hyped about this methodology because of the first book I read this year was the Agile Architecture Revolution, which was too advanced for me. However, I got the general concept of it, but Solid was mentioned in the book and definitely seems like a methodology you’d need to know before learning about Agile. Learning about solid is definitely the next book on my book list. I just bought a copy of Clean Code written by Robert Martin who was also the co-author of the Agile
So, lets get right into what the letters in SOLID means.
S — Single Responsibility Principle(S.R.P)
A class should have one, and only one, reason to change.
O — Open-Closed Principle
You should be able to extend a classes behavior, without modifying it.
L — Liskov Substitution Principle
Derived classes must be substitutable for their base classes.
I — Interface Segregation Principle
Make fine grained interfaces that are client specific.
D — Dependency Inversion Principle
<div class='sharedaddy sd-block sd-like jetpack-likes-widget-wrapper jetpack-likes-widget-unloaded' id='like-post-wrapper-155635758-320-5ce3d79f5260f' data-src='https://widgets.wp.com/likes/#blog_id=155635758&post_id=320&origin=trilamanila.com&obj_id=155635758-320-5ce3d79f5260f' data-name='like-post-frame-155635758-320-5ce3d79f5260f'><h3 class="sd-title">Like this:</h3><div class='likes-widget-placeholder post-likes-widget-placeholder' style='height: 55px;'><span class='button'><span>Like</span></span> <span class="loading">Loading...</span></div><span class='sd-text-color'></span><a class='sd-link-color'></a></div>Depend on abstractions, not on concretions.