The recent Tensorflow Sucks post not a new sentiment, but struck a nerve with me and this is my reaction.
Knowing what sucks is cheap. Knowing what’s hard, on the other hand, is valuable.
Knowing what’s hard keeps you from buying snakeoil sold as solving all things for all people. It focuses the mind on choosing the right problems and saying no to others. Finally, it has the benefit of providing actual insight, and opportunity for genuine progress.
Machine Learning has a unique design challenge, because the domain of ML itself is trending towards universal computation as a subject, not…
The Reconciler is the heart of Om/Next. If you want to understand how Om/Next works, how its pieces come together, understanding the reconciler is a great place to start.
Note: This post is about architecture, not API. For details on how to use Om/Next, see the official or unofficial wikis, or the sample application. However, I hope this will be useful to help people get oriented to the API.
The reconciler manages or “reconciles” data between React, your local client application, and the server. …
Lately I’ve been itching to return one of my favorite activities: visualizing communities. In particular, I want to look at a community that I myself have been a member for the last four years: the Clojure community.
Today we are gonna look at data from the GitHub Archive, which is a scrape of the GitHub public events feed going back to 2012. (It actually goes back a bit further, but those early events don’t carry the all-important language tag, among other things)
Session lets you explore ideas and execute computations, with minimal incidental complexity. It stores your interactions so you can come back to your work later, or share it with others. And its architecture allows tight integration with production environments, so you can easily move between exploration and production.
Ushering in the computational civilization.