The Open-Closed Principle Explained: How More Code Reduces Complexity
Many systems we build find their end of life due to excess complexity, bloat, and risk involved with making changes. The open-closed principle, when applied properly, can help make sure the cost of change in a system remains relatively flat over time. Join Dustin Williams to discover context setting of the SOLID principles and the general use of the open-closed principle, with some manufactured examples of violation shown with guidelines about how to "fix" the code. We'll explore complex examples taken from actual systems and discuss various ways in which the violations can be resolved. You'll leave with real-world examples of how to address violations of the principle, but perhaps more importantly, you'll gain an understanding of the difference between perceived code complexity and actual measured complexity.
Dustin Williams is currently an architect working on commercial technologies with Cardinal Health. Over the past 20 years he has had a variety of roles across many different types of organizations. His first job was with a startup—learning to balance idealistic code with impossible deadlines. Since then, he has had the opportunity to teach software development as an adjunct instructor and lead software development teams. Dustin finds the greatest satisfaction in IT to be creating software that can live beyond the life of the problem it was meant to solve. Outside of work Dustin likes to make sure the lines left by the lawn mower are perfectly straight and watching motorcycle racing.