Yeah, this drives me crazy. I've had people in the past suggest supporting legacy apis on our project that has exactly one consumer (whose code we can directly

Yeah, this drives me crazy. I've had people in the past suggest supporting legacy apis on our project that has exactly one consumer (whose code we can directly update in the same repo), or adding wrapper functions all over the place for "layers" in an app that's like maybe 10,000 lines of code. These things are perfectly fine in the context they're designed for, but people love their shiny new hammers.