У нас вы можете посмотреть бесплатно Keep an Eye on SRP - That Might Just Save Your Broken Code Base или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
Become a patron and download the source code: / zoranhorvat Ever felt overwhelmed looking at a Swiss Army knife of a class in your code? We've all seen them - those classes that juggle functionalities, often coming that way without an up-front plan. They just happen! At first glance, they might appear efficient. The allure of a one-stop shop can be tempting. However, they often lead to unforeseen challenges down the line. Picture this: Classes that cover multiple responsibilities do not combine well - soon enough, we won't be able to implement a larger feature because there is no combination of existing classes that does what is asked for! The inability to implement new features without pulling apart the existing structure can lead to lost opportunities and frustrated clients. There is hope in the form of the Single Responsibility Principle (SRP). Instead of that all-in-one chaos, envision an orchestra: Each musician is a master of their instrument, coming together to produce a harmonious symphony. With SRP, each class focuses on one small responsibility and does it exceptionally well. It brings clarity, making it easier to identify and resolve issues. Moreover, it offers flexibility - each piece can be adjusted or replaced without disturbing the entire ensemble. The final touch comes in the form of object composition. It is through composing objects into larger wholes that we can effectively implement features of great complexity, especially those governed by multiple interconnected business rules. This video is meant to teach you the virtue of the Single Responsibility Principle applied to domain classes, combined with object composition in addressing and resolving the issues we see when original classes are implementing multiple responsibilities each. Thank you so much for watching! Please like, comment & share this video as it helps me a ton!! Don't forget to subscribe to my channel for more amazing videos and make sure to hit the bell icon to never miss any updates.🔥❤️ ✅🔔 Become a patron ► / zoranhorvat ✅🔔 Subscribe ► / @zoran-horvat ⭐ Learn more from video courses: Beginning Object-oriented Programming with C# ► https://codinghelmet.com/go/beginning... ⭐ Collections and Generics in C# ► https://codinghelmet.com/go/collectio... ⭐ Making Your C# Code More Object-oriented ► https://codinghelmet.com/go/making-yo... ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ ⭐ CONNECT WITH ME 📱👨 🌐Become a patron ► / zoranhorvat 🌐Buy me a Coffee ► https://ko-fi.com/zoranhorvat 🗳 Pluralsight Courses ► https://codinghelmet.com/go/pluralsight 📸 Udemy Courses ► https://codinghelmet.com/go/udemy 📸 Join me on Twitter ► / zoranh75 🌐 Read my Articles ► https://codinghelmet.com/articles 📸 Join me on LinkedIn ► / zoran-horvat ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 👨 About Me 👨 Hi, I’m Zoran, I have more than 20 years of experience as a software developer, architect, team lead, and more. I have been programming in C# since its inception in the early 2000s. Since 2017 I have started publishing professional video courses at Pluralsight and Udemy and by this point, there are over 100 hours of the highest-quality videos you can watch on those platforms. On my YouTube channel, you can find shorter video forms focused on clarifying practical issues in coding, design, and architecture of .NET applications.❤️ ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ ⚡️RIGHT NOTICE: The Copyright Laws of the United States recognize a “fair use” of copyrighted content. Section 107 of the U.S. Copyright Act states: “Notwithstanding the provisions of sections 106 and 106A, the fair use of a copyrighted work, including such use by reproduction in copies or phono records or by any other means specified by that section, for purposes such as criticism, comment, news reporting, teaching (including multiple copies for classroom use), scholarship, or research, is not an infringement of copyright." This video and our youtube channel, in general, may contain certain copyrighted works that were not specifically authorized to be used by the copyright holder(s), but which we believe in good faith are protected by federal law and the Fair use doctrine for one or more of the reasons noted above. ⭐For copyright or any inquiries, please contact us at [email protected] #csharp #dotnet #objectorientedprogramming