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, […])

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

What is one small habit that has transformed your life in unexpected ways?

NOT DATA … BUT MEANING!

/ \ and ⁄ / | \

in structures, such as:

Novo's Ozempic linked to rare cases of serious eye disorder, EU regulator says - KSL News

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

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.

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

What are some good Caribbean islands to travel to with friends or family? Why?

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

+ for

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

The biggest binoculars we've ever tested: Celestron SkyMaster 25x100 hands-on review - Live Science

a b 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.