How would you QA something like this across all possible sports? Or test it? How was the feature even developed or requested though if the specification isn't written to explain what it is? Are the frontend designers developing the specification? The developers? What about the backend engineers who need to implement APIs?
What if there's a couple of different factions in a fandom for some particular sport that disagree on the ordering?
Imagine doing this for any other industry and expecting coherent results. An effective developer given a vague tasking will do a bit of quick research and come up with an idea, but they could also be entirely wrong compared to the business objectives. Or the task could relate solely to internal business processes, in which case there is no consensus it's whatever the internal culture of the business does.
What if there's a couple of different factions in a fandom for some particular sport that disagree on the ordering?
Imagine doing this for any other industry and expecting coherent results. An effective developer given a vague tasking will do a bit of quick research and come up with an idea, but they could also be entirely wrong compared to the business objectives. Or the task could relate solely to internal business processes, in which case there is no consensus it's whatever the internal culture of the business does.