There are times that I get into the flow while coding and end up solving a few future problems in addition to right now problems. I know that the code is over-e

There are times that I get into the flow while coding and end up solving a few future problems in addition to right now problems. I know that the code is over-engineered, but if it passes all of the tests and there's nothing obviously wrong with it I would probably check it in anyway. Over engineering never comes up in our code reviews but I think it would be a productive conversation if it did - even if the decision was still to accept the code as-is. The programmers I work with can be defensive of their architecture, but they also love to talk about architecture generally. I think there's a "yes and" [0] way to bring this up that engages the whole team. [0] https://en.m.wikipedia.org/wiki/Yes,_and.. https://en.m.wikipedia.org/wiki/Yes,_and...