Description: The Single Responsibility Principle states that a class should have one (and only one) reason to change. Classes that don't adhere to this principle can result in tightly coupled spaghetti code that leads to more bugs and higher maintenance. We'll look at how to identify these classes by using some heuristics and looking for "code smells", and we'll clean them up using refactoring tools, design patterns, dependency injection and even aspect-oriented programming. Examples will be in C#, but the concepts can be applied to a variety of languages.
Bio: Matthew D. Groves is a guy who loves to code. It doesn't matter if it's "enterprisey" C# apps, cool jQuery stuff, contributing to OSS, or rolling up his sleeves to dig into some PHP. He has been coding professionally ever since he wrote a QuickBASIC point-of-sale app for his parent's pizza shop back in the 90s. He currently works from home on the Telligent product team, and loves spending time with his wife and 2 kids, watching the Cincinnati Reds, and getting involved in the developer community. He is currently writing a book for Manning about aspect-oriented programming in .NET, and also teaches a class on web development at Capital University in Columbus, Ohio.
http://twitter.com/mgroves https://plus.google.com/107286805132042335159 http://www.linkedin.com/in/mgroves
Comments