> Do you think any engineers on the team are aware of this situation? Yes, there probably are. If you haven't been working there for long enough to know who t

> Do you think any engineers on the team are aware of this situation? Yes, there probably are. If you haven't been working there for long enough to know who they are, then you shouldn't be YOLO'ing it. The fact that it hasn't all been cleaned up yet is due to that being an order of magnitude harder than greenfielding your own standard. That doesn't mean that nobody is aware of it, or working on it. I've absolutely worked for a decade on a codebase which had at least 5 different standards, and I was the one responsible for cleaning it all up, and we were understaffed so I could never finish it, but I could absolutely point you at the standard that I wanted you to follow. It also probably was somewhat deficient, but it was better than the other 4. It evolved over time, but we tried to clean it all up as we went along. Trying to ram another standard into the codebase without talking it over with me, was guaranteed to piss me off.