It's a very interesting (and to some very frustrating) time to be a front end developer. Libraries and tooling have exploded in every direction, providing an overwhelming myriad of choices. Angular, Ember, React, Elm, Om, PureScript and so many more compete for your attention every day, driving peop…Brandon Konkle
GraphQL/Node/React engineer, TypeScript nerd, Postgres fan, Linux enthusiast, supporter of social justice, loving husband and father, avid comic reader.
In recent weeks a fascinating new library has been getting attention in the React community - redux-saga. It's billed as an "alternative side-effect model" for Redux that uses ES'15 generators and competes with the fundamental redux-thunk middleware. As part of my in-progress quest for a n…Brandon Konkle
As I make my transition from working in the office back to working remotely I've been thinking a lot about what makes remote teams successful and what challenges they face, especially in blended teams where some are still in the office. I took some time and wrote down my thoughts on how to overcome…Brandon Konkle
If you follow React developers on Twitter, you've probably been hearing the name Redux come up a lot lately. There's a good reason for this - Redux solves one of the biggest and most frustrating pain points for most React developers - state management. In this article I'll describe the problem of st…Brandon Konkle
Prior to Node v0.12, writing a command line tool in Node was a rather difficult proposition. There was no way to execute a command synchronously, so tools like ShellJS worked around this by blocking the event loop until a 'done' file was created on the filesystem signifying that the command was comp…Brandon Konkle