I already did in response to @singham's rather standoff-ish reply (inconsistent typing rules in the data store across APIs, oftentimes with no way to override).
That is very much a "Big Company" problem though. At Google, you have one team doing the web UI, one team doing the data store backend, one team doing the Python API, one team doing the GoLang API.
These teams may (and probably will) disagree about the best way to handle types, and they won't collaborate (due to politics and differences of opinions) about making sure they are consistent. Given that cross-team communication is often poor, there won't even be any "forcing function" to make sure that they are consistent, and so, by Murphy's Law, they won't be.
That is very much a "Big Company" problem though. At Google, you have one team doing the web UI, one team doing the data store backend, one team doing the Python API, one team doing the GoLang API.
These teams may (and probably will) disagree about the best way to handle types, and they won't collaborate (due to politics and differences of opinions) about making sure they are consistent. Given that cross-team communication is often poor, there won't even be any "forcing function" to make sure that they are consistent, and so, by Murphy's Law, they won't be.