Comment by IggleSniggle

I feel as though many problem spaces are already expressible in human language, but that “code” is just a more concise expression of the same thing.

The main issue with common language encoding is dialect (this happens in code, too, especially “common” languages like C++, Java, or JavaScript). That is to say, the assumptions you bring with you about what for example a “schedule” is affects all subsequent decisions based on it, but there are many possible interpretations for the semantics of such a thing.

It seems to me that most programming languages of today are better than “human language.” They more concisely AND precisely express the decision space.

I assumed “better tooling” meant some deeper heuristic wherein you might expect an AI to interpret your meaning based on your own enculturation, accepting the high subjectivity of any request/definition and producing an output formed by these assumptions.

I would still call this “source code” however, in much the same way that legal precedent is the source code for the next legal decision.