AI Is No Code
2026-06-24
AI is No Code for one specific architectural pattern. The one I call “function-based”, which is synchronous and sequential.
You can build other architectural patterns on top of that one architectural pattern, but the substrate function-based pattern restricts your architectural thinking (“Design”). For example, you cannot build Forth on top of that substrate. Forth doesn’t use the function-based “calling convention”. The best you can do is to build a fake Forth that adheres to a prematurely-supplied calling convention. Nor, can you build something that is asynchronous and fully parallel on top of that substrate, since the substrate has already eliminated asynchrony from any design you put on top of it. The best you can do is to define synchronous “reactors” and then plumb them together by hand in a manner analogous to writing assembler.
I’ve built many Designs using a different substrate architectural pattern - asynchronous, electronic IC based. From that experience, I conclude that the function-based pattern is too restrictive and bloatful and that we need to break free of it. AI won’t help with that.
See Also
Email: ptcomputingsimplicity@gmail.com
Substack: paultarvydas.s. bstack.com
Videos: https://www. youtube.com/@programmingsimplicity2980
Discord: https://discord.gg/65YZUh6J. q
Leanpub: https:. /leanpub.com/u/paul-tarvydas
Twitter: @paul_tarvydas
Bluesky: @paultarvydas.bsky.social
Mastodon: @paultarvydas
(earlier) Blog: guitarvydas.github.io
References: https://guitarvydas.github.io/2024/01/06/References.html
Paid subscriptions are a voluntary way to support this work.