> abstract unless there's a reason not to Is the _exact_ behavior I have seen in 100% of the Java and C# codebases I've used. > But where it becomes a big pro

> abstract unless there's a reason not to Is the _exact_ behavior I have seen in 100% of the Java and C# codebases I've used. > But where it becomes a big problem is when it's used in a one, two, five-person project, and all those walls just become massive speedbumps, not only slowing you down but making it hard to drive straight. I think that most patterns exist to prevent bad things from happening, or to make things easier to understand. I think that in a team of 1-5, there just isn't enough output happening to make either of those things huge concerns. If you're very small, there's not a ton of reason to try to protect yourself from future-scaries that don't exist in your company yet. And then, if the response is "But what about when we grow", that's literally the exact right time to abstract behavior. _As needed_.