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: 27.06.2025 01:16
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.
Another canonical form could be Lisp S-expressions, etc.
in structures, such as:
Sega's leaked sales figures show Sonic's new frontier is heading in the right direction - Eurogamer
i.e. “operator like things” at the nodes …
/ \ and ⁄ / | \
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”.
A slogan that might help you get past the current fads is:
plus(a, b) for(i, 1, x, […])
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.
Are cold plunges good for you? Here’s what the science says. - The Washington Post
Most coding assistants — with or without “modern “AI” — also do reasoning and manipulation of structures.
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
a b i 1 x []
Atque sapiente quis aspernatur.
+ for
NOT DATA … BUT MEANING!