In pursuit of code quality: Beware the tight couple!
Use the Dependency Inversion Principle to untangle tightly coupled code
You know tight coupling is bad news and you really want
to avoid it in your designs -- but the question is how. One thing developers have come to agree on is that well-written code is maintainable, and the Dependency Inversion Principle is a sure way to design for maintainability.
In the latest installment, Beware the tight couple!, in his "In pursuit of code quality series" , Stelligent President Andrew Glover
shows you how to recognize a tightly coupled system and then disentangle it using the Dependency Inversion Principle. Applying this technique ensures that not only will you be able to modify your code base when you need to, but so will other developers.
Don’t miss the accompanying code quality discussion forum where you can learn first-hand about code metrics, test frameworks, and writing quality-focused code.
|
