## Plan for July 2018

* TOC
{: toc }

Yesterday I had a wonderful conversation with Jonathan Edwards, which helped me figure out my focus for the next month, and possible beyond. I feel very lucky to get his advice. 

I updated him on my progress, that I was able to solve [DOM Recursion Problem with Reflex](http://futureofcoding.org/log#dom-recursion-problem-solved-by-reflex), but haven't made much progress on the UI part of visualizing the stream operators yet.

He was able to give me really great advice here, because he's potentially the original guy who's been insisting that we need to work both on the model and the UI at the same time - as opposed to PL people who only work on the model and Bret Victor people who only work on the UI. It's called co-design, desigining two different pieces towards each other.

He suggested that before I work on the UI, I should write a blog comparing Reflex to Elm, why I like the Reflex semantics as a model better, why the UI of Haskell is hard to use and why we need a better UI, and only vaugely hand-wave about how I think the UI will look.

This essay will be a great foundation to build off of. I'll share it on social media, HN, etc.

I started the [essay today here](/drafts/frp).

Then, I should pick a few very specific and small examples, and draw out by hand and Figma what they should look like from a storyboarded perspective, not worrying too much about the general case. I can then publish this as a follow up essay. However, Jonathan warned me (and I agree) that this will likely be difficult, possible where this research thread comes to an end, so we'll see...

However, if I am able to get something that looks promising, I should, in effect, concatenate the two essays into a single narrative and submit to either LIVE or REBLS at SLASH on Aug 17th. In particular, Jonathan noted that I should explain in my submission the "technical challenges for building this for real."

If I don't make it in time for SPLASH, the next relevant workshop would be PX at <Programming> in the Spring of 2019, which is very far away, so I hope I make it in time!

Author: Steve Krouse