Main Content

The class that knew too much: refactoring spaghetti code

About the Talk

October 13, 2012 12:05 PM

1275 Kinnear Rd, Columbus, OH 43212

1275 Kinnear Rd, Columbus, OH 43212

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, and how to clean them up using refactoring tools, design patterns, and even aspect-oriented programming.

Ratings and Recommendations

This Talk hasn't been rated yet. Sign In to rate Talks.

comments powered by Disqus