I admire what you&#x27;re doing, but I can&#x27;t help but see gaping holes in your card wiki idea.<p>1. Your examples all seem to suffer from the same problem all of Bret Victors ideas do too; they don&#x27;t scale. Sure I would like interactivity, no I don&#x27;t want to re-eval my entire codebase on every keystroke, and no I don&#x27;t want to recreate my vertex data every frame in the Draw method just so I can scrub a tree&#x27;s bendiness.<p>2. The card wiki is too reliant on perfect structure. What if I need to change the structure at some point (refactor), then all my queries break. They&#x27;ll break even worse too if my queries just says &#x27;get the salaries per department&#x27;, but then I modify the structure to have two sets of employees per dept (perhaps current and ex-employees), which changes the meaning of the query, yet the computer would plod along and now wrongly sum both groups I presume, if working in this automated way.<p>3. Performance. Sure it&#x27;s easy to re-calculate an equation based on dependencies. Want to do &#x27;a = b + c&#x27;? Then obviously re-calc &#x27;b&#x27; and &#x27;c&#x27; dependencies before performing the equation. But the hard part is when to do the re-calculation? Perhaps store an &#x27;isDirty&#x27; bool? Or cache the value? Or just re-calc everytime it&#x27;s needed? Human programmers make this decision based on how the result is used, how many times it is used, framerate, memory consumption and performance heuristics. There isn&#x27;t a one size fits all, it&#x27;s highly contextual.<p>4. You say &#x27;we know Wikipedia works&#x27;. But have you tried scraping data from Wikipedia? Computers get stuck on all sorts of dumb stuff. Wikipedia is obviously meant for human consumption, where visual data and the English language rule, and the only structure we need is a &#x27;top to bottom&#x27; layout. Programming is way more specific that this, so I can&#x27;t see how combining the two ideas is any good.<p>5. Organisation. Perhaps you&#x27;re still working on this, but you switched back and forth between a single card at a time, but given 20+ cards I&#x27;m not going to remember where stuff is. Code editors throw a bunch of stuff into one document, have tabs, and an explorer, and intellisense and search etc - and I still lose stuff all the time!<p>Hopefully when you do this release you&#x27;ll include some complex samples, like you said you could build a compiler with these cards? So perhaps I&#x27;ll be proved wrong.