While working, I came across someone who would rather not centralize abstractions needed throughout the code, meaning that there can be duplicates and that the call sites now need to know the specifics of abstracting things like stage or what query to use for dynamic thing groups.
While there are arguments to be made for over-abstraction (which I'm against, I also worked with an overengineer) - this helps reduce code complexity elsewhere and guides developers to use the API in a way that makes sense for our application. Not having it written down in code somewhere means "The abstraction is in my head, and it doesn't need to be written down for other people to understand."
While working, I came across someone who would rather not centralize abstractions needed throughout the code, meaning that there can be duplicates and that the call sites now need to know the specifics of abstracting things like stage or what query to use for dynamic thing groups.
While there are arguments to be made for over-abstraction (which I'm against, I also worked with an overengineer) - this helps reduce code complexity elsewhere and guides developers to use the API in a way that makes sense for our application. Not having it written down in code somewhere means "The abstraction is in my head, and it doesn't need to be written down for other people to understand."