Michael A. White

What My Editor Means For AI

October 9, 2026

I’ll be adding AI to my editor whitepaper soon. (Sorry, President Trump, I plan on continuing to use the term AI instead of SI for at least a little while.) Any expression node, from the whole program to one component to one expression, will be able to be edited as a natural language description of the functionality that is converted to code written by an algorithm. Any edits made directly to the code using the editor will be used to automatically update the natural language description of the closest relevant node. We can do this because there is a straightforward algorithm that is less difficult than general intelligence, which programmers have to learn, for translating between natural language and programming language once you have a grammar and lexicon for the natural language and the semantics of the programming language. Concurrent programs could be a little more difficult, but can still be accomplished.

I believe this will make AI models unnecessary for GUI-DB application development, because the algorithm can be implemented without the need for an AI. AIs will still be useful for other kinds of applications. I believe every GUI-DB application can be abstracted to use a modular package ecosystem of plugins and components according to the plugin system in my whitepaper. An advanced civilization should have a fully properly abstracted definition of GUI-DB applications that can have any part edited by a qualified human, rather than AI slop. The algorithm for translating between natural language and programming language can be required learning for computer science and AI Bachelor’s degrees.

If implementing the algorithm proves too difficult or we want to charge a lot for it, an alternative is to still call a traditional AI model to do the translation.