## Twitter research

* TOC
{: toc }

### Inviting people to the podcast

I looked at [this list](#18) of potential guests, invited my friend Nicolae Russan as well as his friend Simon last to the podcast, and reached out to Brent Yorgey as well.

I really enjoyed reading [Brent's slides](http://ozark.hendrix.edu/~yorgey/pub/explaining-errors-slides.pdf) on Explaining Type Errors through an interactive interface where you click on a series of questions. However, it did make me recall Bret Victor's "interaction considered harmful" point, and I wonder if there are ways to build a context-sensitive graphic for explaining type errors without any interaction nor a block of text. Maybe with colors? Maybe with shapes? Definitely in the context of where the error is occuring, and not in the console.

### xstate

I then took to [my Twitter list](https://twitter.com/stevekrouse/lists/future-of-coding) for more inspiration, where I stumbled upon [xstate](https://github.com/davidkpiano/xstate), which seems quite similar to CycleJS, particularly now that they can generate state diagrams from your code. I'm quite excited to read:

* https://rauchg.com/2015/pure-ui
* https://medium.com/@asolove/pure-ui-control-ac8d1be97a8d
* https://statecharts.github.io/use-case-statecharts-in-user-interfaces.html

I also stumbled across this neat tool. "Dynamic layout meets direct manipulation.": https://subformapp.com/

Goodness! There are so many people building cool things in this space. It's difficult to find a balance between research and novel work.

Author: Steve Krouse