162. SOLID - Single Responsibility Principle
from Kutad Gubilik's Listen Later Hosted by Stride NYC
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?) Episode: 162. SOLID - Single Responsibility Principle Pub date: 2020-06-30 Get Podcast Transcript → powered by Listen411 - fast audio-to-text and summarization Do you know how you can feel overwhelmed when you have too much on your plate? Well, your code can feel the same way. This is why it’s important to follow the Single Responsibility Principle, SRP, which is what the ‘s’ in SOLID stands for. Today we do a deep dive into the SRP and how you can ensure that your class or object only does one thing at a time. We take a look at some of the benefits of following the SRP, such as ease of testing and greater flexibility with making changes. When there is more than one responsibility designated to a class, it can quickly become confusing when you need to alter a piece of code. We also look into why you should try to keep classes as small as you can, how to know if a class or object has more than one responsibility, and why you should always be ready to refactor. The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Embed this episode
What this episode covers
Podcast: The Rabbit Hole: The Definitive Developer's Podcast Episode: 162. SOLID - Single Responsibility Principle Pub date: 2020-06-30 Details: https://www.listennotes.com/e/5107b5f7a6f04fad9399e12126d63ffd/ The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
No transcript yet.