Logo

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: 29.06.2025 00:25

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?

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

in structures, such as:

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

Users Are Leaving Google Drive for This 2TB Cloud Plan - PCMag

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

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.

NOT DATA … BUT MEANING!

How do fictional characters like Peter Pan from Once Upon a Time shape adolescents' perceptions of relationships and personal growth?

+ for

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”.

/ \ and ⁄ / | \

What real evidence is there to believe in legends such as the story of Atlandida or the lost continent of Lemuria?

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

a b i 1 x []

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

Apple’s struggles to update Siri lead to investor concerns over AI strategy - Financial Times

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.

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