A hypothesis: for live programming to scale beyond toy programs, generic low-level visualizations aren't enough. Instead, we need Live Literate Programming: better tools for creating *program-specific* views, which communicate our higher-level understanding.
-
-
For example, instead of Processing, imagine a Rails dev making a CRUD website. I have an asset pipeline, a database, so on. How do I visualize a database? A transaction? A server connection? A thread pool?
-
Now I've come up with a proper visualization for all those things. How do I package the vis with the data types? How does my IDE access the vis? How does it know which vis to render, and at what granularity? How does it have access to my runtime state?
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
cognitive psychology. PhD