Is almost never the right answer when developing systems, at least the sort that I build. The easy path is almost always best and that feeling of “something being easy” is often a sure sign of being on the right track. So last week when I found myself “grinding” on…

The takeaway from the last post is that if you can compose your code you should. Consider it an extension of other, less controversial maxims like: use map when transforming a collection into another and reduce to convert a collection into a “single” value. To be frank, I’d be pleased…

More and more I see javascript that makes use of async/await: async function imperativeWay(color) { try { let resultsString = await fetch(color) let jsonResults = JSON.parse(resultsString); let transformedResults = transformFirst(jsonResults) let sendResults = await sendToClient(transformedResults) await remotelog('log', sendResults) } catch (e) { remotelog('error', e) } }

We’d spoken before about my coming on board in a leadership role. The chemistry hadn’t been right, but some additional elbow grease was needed to get the next iteration to market… My task was to alter a portion of the data model and related code to prepare for the large…