Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* TOC {: toc } ### Prisma yesterday I spent yesterday researching GraphQL for Dark. I combined a few pictures on their website to explain Prisma. It's a little complicated, because it's solving a GraphQL problem with more GraphQL, but I think this photo explains it pretty well: <blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">One graphic to explain <a href="https://twitter.com/prisma?ref_src=twsrc%5Etfw">@prisma</a>, the <a href="https://twitter.com/hashtag/GraphQL?src=hash&ref_src=twsrc%5Etfw">#GraphQL</a> ORM-like layer <a href="https://t.co/8jaq2ayUGK">pic.twitter.com/8jaq2ayUGK</a></p>— Steven Krouse (@stevekrouse) <a href="https://twitter.com/stevekrouse/status/1011296632221110279?ref_src=twsrc%5Etfw">June 25, 2018</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> ### The Software Elephant I was inspired by a wonderful conversation this morning with [James Somers](http://jsomers.net/) (of [The Coming Software Apocalypse](https://www.theatlantic.com/technology/archive/2017/09/saving-the-world-from-code/540393/) and many others) to write up my thoughts on how visualizations will save programming. I somewhat-recently read [Fred Brook's No Silver Bullet](http://worrydream.com/refs/Brooks-NoSilverBullet.pdf) where he very eloquently argues that software is "inherently unvisualizable." What makes Brooks so great is that he gives you such a wonderful structure for your arguments, including great metaphors. I actually can't believe my metaphorical luck: in a relevant quote he refers to software as an "elephant," which is perfect because it allows me to reference the story of the blind men and the elephant. I 'm pretty pumped about the rough draft / outline I've come up with in the last 2 hours. I'm not sure how this essay relates to [Casual Programming](./essays/casual). Maybe it's a replacement? Maybe they're somehow complimentary? ### Next steps 06/26/18 I'm pumped to get this essay polished and published before continuing trying to understand Reflex, etc, etc. I think it's useful to take a break to explain the *why* of what I'm doing before spending more time doing. This post might be similar to [my first (and favorite) Andre Staltz post](https://web.archive.org/web/20180530055638/https://futurice.com/blog/reactive-mvc-and-the-virtual-dom), which is similar in that its a mile-marker on his way to creating CycleJS.
- Loading branch information