throwaway365x2

8 ms·

1. 1.▲
   by throwaway365x2 2y ago

   In that case you have more than one implementation, or at least a reasonable expectation that it will be used. I don't have a problem with that. My comment was regarding interfaces used internally within the code, with no expectation
2. 2.▲
   by throwaway365x2 2y ago

   That's very true. When a customer has a problem, you create a solution to it. Often the problem is part of a much larger space, so you tend to have discussions of all the possible features you could implement. This is a necessary step
3. 3.▲
   by throwaway365x2 2y ago

   I think you have good approach. I also tend to go with the flow and follow the common practice. If I tried to do "Java in C#", it would make it more difficult to follow my code and decrease maintainability. I sometimes work on leg
4. 4.▲
   by throwaway365x2 2y ago

   I don't follow .Net closely, but it seems like there should be a better alternative. Java has a library called "Mockito" that can mock classes directly without requiring an interface. I assume something similar exists for .Ne