Is this overengineering attitude coming from those few longstanding members? Because if so, I don't see how You can convince them of the value of simplicity (an

Is this overengineering attitude coming from those few longstanding members? Because if so, I don't see how You can convince them of the value of simplicity (and that any kind of abstraction have a cost) if they themselves does not see value in it. This intuition can only come from long exposition to consequences of adding to much of accidental complexity. And what is more by openly contradicting their intuitions You directly threaten their status in company (because Your solutions will be directly opposing their way of solving things). There is of course second possibility - are You sure that the problem is not You ? Are there other team members that also complain? OOP style of programming takes a lot of time to get used to, but sometimes it can work if programmers are familiar enough with it. The use of strategy pattern can be good if there is enough variability in parts of algorithm that is being implemented. Personally I hate this style but its because I lack imagination (which is necessary to select proper patterns and create proper abstractions). I can only create them as an afterthought (by extracting them from existing codebase). But I know that there are people that can do it up front and hit the right spot enough times (and refactor if not).