Master The L in SOLID скачать в хорошем качестве

Master The L in SOLID

Download source code ►   / zoranhorvat   Join the C# Discord server ► https://codinghelmet.com/go/discord Enroll course Beginning Object-Oriented Programming with C# ► https://codinghelmet.com/go/beginning... Subscribe ►    / @zoran-horvat   Have you noticed how everyone has an opinion about LSP - usually the strong one - yet hardly anyone can explain it clearly? It would sound even stranger if I told you that you can automate the verification of the Liskov Substitution Principle. That is how clear it is! Let me change that unfavorable situation by drawing you back to the fundamental principles of OOP. I will teach you how to formalize the definition of a type, either a class or an interface, to define the rules every subtype must satisfy. That will be the Liskov principle at work. With the abstract properties defined, every implementation of an interface and every subclass will always produce objects that are substitutable for objects of their parent type - just as the LSP would define them. ⌚ 00:00 Intro ⌚ 01:05 Defining Class Attributes ⌚ 06:43 Detecting LSP Violations ⌚ 08:54 Designing Interfaces with LSP ⌚ 12:29 Implementing Concrete Classes ⌚ 15:03 Outro ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ ⚡️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. #csharp #dotnet #objectorientedprogramming