> teaching the model what a human wants from a language Yes, I think this kind of requirement would lead us to a very interesting specification exercise which

> teaching the model what a human wants from a language Yes, I think this kind of requirement would lead us to a very interesting specification exercise which would address questions like: (1) what are the different use cases relevant to identifying 'as yet unaddressed' programming language design issues? (2) what are the 'success metrics' of a new language design? (3) what are the 'unresolved shortcomings' of existing languages? (4) What are the issues related to 'non-human language design'? This last question is kind of about the opposite to 'readability as we know it', where you could anticipate a language suited to creating non-human-intelligible code, which might require tools to translate it into human intelligible form, kind of like the assembly-language to higher-level language issue but kind of in reverse.