To some extent that reflects that in programming we encounter a mixture of naming origins between computer science (where naming follows an academic tradition t

To some extent that reflects that in programming we encounter a mixture of naming origins between computer science (where naming follows an academic tradition that shares its heritage with Mathematics) and software engineering (where naming follows a tradition closer to that of other engineering tooling, where naming is more like branding - think 'Duck tape' or 'Allen wrench'). Often the closest thing we do to the whole 'Thurston maps are Thurston-equivalent to polynomials, unless they have Thurston obstructions' thing is that we qualify our statements about programming entities by the programming language or platform to which the statement applies. So you might reasonably have a statement like 'A JSON value consists of an array of JSON values, a map of string keys to JSON values, or a primitive value', which sounds just as self-referential as the Thurston example, but because it's called a JSON value, not a Crockford value, it sounds less conceited.