Lots of teams write software in a nonuniform, disjoined, messy way. Whatever the last engineer thought is what gets merged. Sometimes it can be different ideas being welcomed, sometimes it is unhealthy disagreements in the team, but usually it is likely to be that the team never talked about it before.
One of the best tools to bring unambiguity to what kind of code and architecture your team writes is an “RFC” process. The the real purpose is to drive a conversation until consensus is formed. Then it becomes a tool to make quick decisions about how to build software.
Here’s an easy git-controlled RFC template that lets you get started in one minute with sensible defaults.
