Which coding approach helps maintain ADP in evolving codebases?

Which coding approach helps maintain ADP in evolving codebases?

• A. Use global variables for services.
• B. Hard-code all dependencies to simplify builds.
• C. Avoid interfaces to reduce indirection.
• D. Use dependency injection to supply implementations at runtime.

Answer: (D)

Dependency management through dependency injection is the approach that helps maintain adaptability in evolving codebases. When concrete implementations are supplied from outside the consuming code, components depend on abstractions rather than on specific classes. This keeps the consumer’s interface stable while letting you swap implementations, replace them with mocks for testing, or reconfigure behavior at runtime without touching the dependent code. It also reduces ripple effects when a dependency changes, since only the wiring or configuration needs updating, not the consumer itself. This aligns with keeping high-level logic decoupled from low-level details. Global variables for services introduce hidden dependencies and tangled state that are hard to test and replace. Hard-coding dependencies ties code to specific implementations, forcing widespread changes if one part evolves. Avoiding interfaces removes a crucial indirection that enables easy substitution of alternatives. For example, a component that relies on a repository interface can receive any concrete repository at runtime, making it straightforward to test with a mock or swap data sources without modifying the component.

Dependency management through dependency injection is the approach that helps maintain adaptability in evolving codebases. When concrete implementations are supplied from outside the consuming code, components depend on abstractions rather than on specific classes. This keeps the consumer’s interface stable while letting you swap implementations, replace them with mocks for testing, or reconfigure behavior at runtime without touching the dependent code. It also reduces ripple effects when a dependency changes, since only the wiring or configuration needs updating, not the consumer itself. This aligns with keeping high-level logic decoupled from low-level details. Global variables for services introduce hidden dependencies and tangled state that are hard to test and replace. Hard-coding dependencies ties code to specific implementations, forcing widespread changes if one part evolves. Avoiding interfaces removes a crucial indirection that enables easy substitution of alternatives. For example, a component that relies on a repository interface can receive any concrete repository at runtime, making it straightforward to test with a mock or swap data sources without modifying the component.