That surprised me, too. I'd have thought they'd have an API for all this kind of stuff, so the front end page rendering part simply couldn't make these mistakes.

Maybe it was too limiting (slow dev) to have change two things anytime they needed different data? Or perhaps at one point there were performance concerns?