Design Patterns: Don't Repeat Yourself in C#

IAmTimCorey October 22, 2018
Video Thumbnail
IAmTimCorey Logo

IAmTimCorey

@iamtimcorey

About

My goal is to make your life easier, specifically when it comes to learning software development. I remember what it was like to not know even what questions to ask. In every video I do, I try to answer those questions. You will notice that I don't usually do quick videos. That's because I would rather help you understand rather than just padding my watch percentages. If you want more in-depth training, feel free to head over to my website (https://www.iamtimcorey.com) where I have courses dedicated to C#, SQL, and more.

Video Description

Video Sponsor: PVS-Studio: https://bit.ly/2PeCS2v Newsletter signup (with exclusive discounts): https://signup.iamtimcorey.com/ (your email will be kept safe and you will not be spammed). Source Code: https://www.iamtimcorey.com/downloads/?code=DRY Have you ever heard the term DRY, as in "Keep your code DRY"? DRY refers to one of the foundational design principles in programming. It stands for Don't Repeat Yourself. On the surface, that sounds so easy to do. However, as you will see in this video, there is a lot to think through when trying to get this right. From thinking through where to put code to ensuring that you don't repeat yourself in testing and bug fixing, there is a lot beneath the surface of simply keeping code DRY. 0:00 - Intro 0:53 - recognize and anticipate repetition in your code 4:44 - create a discrete method and make it independent 7:40 - class library - why and how to 16:05 - bringing the class library into other projects 21:55 - briefly on updating dll files - NuGet packages 22:28 - DRY in development work - unit tests (crash course) 41:51 - how to make the class library more versatile - consider .NET Standard 44:47 - video summary 46:32 - how far to take DRY: general tips