> I’m still defining the term. I want my software to *grow organically*! My current workflow still feels fairly sequential: brainstorm, make some decisions, spec, let a model do some work, wait, review, make more decisions, iterate. Whatever project I work on, I always enjoy it more if the feedback loop is tight. I want to see my changes show up fast! **The process of creation is also a process of learning about the problem.** I’m old enough to remember [Inventing on Principle](https://youtu.be/PUv66718DII), excellent talk by [Bret Victor](https://en.wikipedia.org/wiki/Bret_Victor). I want to blend the role of developer and user, to sketch and then add detail. To [create software within the software itself](https://diogosnows.substack.com/p/good-software-a-little-more-my-way). I want to start from a simple prompt, let the AI (compiler) make decisions and assumptions but then see a Canvas with decisions and open questions. I want to change any of them and see it play out in real-time. I want to build a shared understanding with the AI, not argue in a linear [[A multiplayer canvas|wall of text]], alone. The [[Harnesses are compilers|AI Compiler]] should generate proofs that match my decisions and “compile” the code into the application as it changes. ![[39FD2657-4DD9-469F-A89E-6A12539C61A4.png]] ### Open questions I'm exploring [[Formal spec for natural language]] ### Worth reading next [[Systems of creation]]