I&#x27;ve gotten many code review comments to the effect of &quot;can you break this out into an interface?&quot; so I 100% understand what you&#x27;re saying.<p>Many of the instances were things that we were only likely to make one example of either. I could see that argument being valid if there was a clear second implementation in mind, but an interface with only one implementing class is often just wasted time.