cognitive psychology. PhD 
Just noticed while pair debugging: lack of live visibility in a programming env becomes more obvious when pairing. “Hey, can you check what type X is?” Live Vis takes better advantage of two pairs of eyes
Show this thread
-
Wow awesome find! The second part especially is so key. Abstracting over time is a weirdly powerful and underused idea
I think the challenge is knowing what to show. Value of printf is you only see exactly the points (you think) you should care about. A full dump of program output is obviously too much. You probably want: 1) Smart defaults 2) Lightweight interactivity 3) Zoomable UI
-
-
Digital maps are a relevant case study. Older tools focused on physical/geographic accuracy. However, people's mental model of space is different. They care about landmarks, intersections, their current location. See: "Distortions in Memory for Maps", Tversky 1981pic.twitter.com/Szc3fgB1BG
-
And we can use this research to make better digital maps. Maps that emphasize the cognitively-relevant features of geography help people more effectively navigate using the map. See: "Cognitive Design Principles for Automated Generation of Visualizations", Tversky et al. 2007pic.twitter.com/I6i0fuIz5o
- Show replies
New conversation -
-
-
yeah, i'm lately thinking of this as: 1) built-in viz tooling at _framework_ / DSL level 2) programmer can specify vis in some lightweight way 3) authors leave behind visualizations as docs; also remix / build new vis on the fly
-
eg, little sketch of that: tool where programmers can dynamically visualize various projections of Redux state (i'm cheating, these are actually hardcoded now, but seems easy to make dynamic because of the common structure of Redux apps)https://twitter.com/geoffreylitt/status/1260641012415946754 …
0:16 - 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.