What are your thoughts on a future where code is represented as a structured model, rather than text? Do you think that AI-powered coding assistants benefit from that?

Last Updated: 03.07.2025 00:50

What are your thoughts on a future where code is represented as a structured model, rather than text? Do you think that AI-powered coding assistants benefit from that?

First, it’s worth noting that the “syntax recognition” phase of most compilers already does build a “structured model”, often in what used to be called a “canonical form” (an example of this might be a “pseudo-function tree” where every elementary process description is put into the same form — so both “a + b” and “for i := 1 to x do […]” are rendered as

plus(a, b) for(i, 1, x, […])

+ for

Trump is at a moment of choosing as Israel looks for more US help crushing Iran's nuclear program - AP News

i.e. “operator like things” at the nodes …

a b i 1 x []

Most coding assistants — with or without “modern “AI” — also do reasoning and manipulation of structures.

Eagles star Saquon Barkley stunningly hints he could retire ‘out of nowhere’ - New York Post

NOT DATA … BUT MEANING!

in structures, such as:

A slogan that might help you get past the current fads is:

Why do some people admire Latin American cultures but not want to be from or live in those countries?

Long ago in the 50s this was even thought of as a kind of “AI” and this association persisted into the 60s. Several Turing Awards were given for progress on this kind of “machine reasoning”.

Another canonical form could be Lisp S-expressions, etc.

It’s important to realize that “modern “AI” doesn’t understand human level meanings any better today (in many cases: worse!). So it is not going to be able to serve as much of a helper in a general coding assistant.

Apple drops a spot on 2025 Fortune 500 list - 9to5Mac

These structures are made precisely to allow programs to “reason” about some parts of lower level meaning, and in many cases to rearrange the structure to preserve meaning but to make the eventual code that is generated more efficient.

/ \ and ⁄ / | \