Is there any point to an interface if only one class implements it?
class-design, interface, refactoring
Solution
No way! Its has zero harmful effects and one day somebody can swap an implementation without having to refactor tons of code.
Problem
Looking at the (mature) codebase at my new job, there is an interface, and only one class implements it (as far as I can tell). Can/should I get rid of the interface?