> I'm strongly against creating interfaces for non-library (not shared) code, that will only ever have one concrete implementation. I agree with this, but the

> I'm strongly against creating interfaces for non-library (not shared) code, that will only ever have one concrete implementation. I agree with this, but the problem I see is that people have bad judgement when thinking about if something will only be implemented once or not. Personally, I don't think the boiler plate / interface bloat is as cumbersome as others do. I'm currently working in a code base where things were decided to "never change", and now we need to change those things. In a perfect world, I'd rather have less abstract code that never changes. But if it's a choice between poorly written highly coupled code or poorly written code that relies on interfaces, I'll take the interfaces and their bloats.