Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When I’m doing TDD, it forces me to employ Dependency Injection principle and I end up with loosely coupled code.
I was told that it’s harder to understand application that has loosely coupled code.
Can you tell me what pros and cons of loosely coupled code?
Dependency Injection does not automatically lead to low coupling. I agree with the answers above about the pros of low coupling. The main benefits of Dependency Injection is that it improves testability and that it helps you follow the GoF principle of Program to Interfaces, not Implementations. But you can have high coupling to injected dependencies too.