Lodash & Folktale Partial Function Differences


At work I was trying to practice doing more composing of functions, and to do so you create a lot of partial functions, often through currying. Sometimes, the functions aren’t built for partial/currying, or the parameters are in an awkward order. Lodash offers partialRight instead.

However, I was trying to use all of Folktale’s functions instead of my normal use of Lodash in an effort to force myself to learn the differences. I came to like the Folktale’s v2 version of partial called partialize and wanted to briefly talk about why.

Below, I’ll go over parsing a time & weather web service JSON response. We’ll show parsing the data using both Lodash and Folktale functional partials. This should teach you the difference between the 2 libraries approaches to function partials.

Continue reading “Lodash & Folktale Partial Function Differences”

Node.js Crash Course


I’ve been doing Node full-time at work and noticed a lot of other people lacking a centralized resource to get up and running quickly. There are a lot of wonderful resources out there for Node, a Google search away, but hopefully this document should get you coding quickly as well as able to communicate effectively with other Node developers.

I’ve tried to write this list in order of most important things you need to know. Feel free to skip around.
Continue reading “Node.js Crash Course”

Error Handling Strategies


There are various ways of handling errors in programming. This includes not handling it. Many languages have created more modern ways of error handling. An error is when the program, intentionally, but mostly not, breaks. Below, I’ll cover the 4 main ones I know: try/catch, explicit returns, either, and supervising crashes. We’ll compare various languages on how they approach errors: Python, JavaScript, Lua, Go, Scala, Akka, and Elixir. Once you understand how the newer ways work, hopefully this will encourage you to abandon using potentially program crashing errors via the dated throw/raise in your programs.
Continue reading “Error Handling Strategies”

AWS Adventures: Part 2 – Infrastructure As Code, Deploying a Microservice



In the old days, you’d write code and allow another team called Operations (or OPs for short) to deploy it to various servers for testing, and eventually production. Quality Assurance teams would be testing your code from a few days to a few weeks ago on another server.

Developer tooling, infrastructure as a service, and shorter development cycles have changed all that. The Amazon practice of “you build it, you own it” has started to filter out to other companies as an adopted practice. Teams are now expected to build, deploy, and maintain their own software.

Today, I wanted to cover what I’ve learned about automated deployments around AWS. You’ll learn why you don’t need Ansible, Chef, or even Serverless, and instead can use AWS API’s to do everything you need.

Continue reading “AWS Adventures: Part 2 – Infrastructure As Code, Deploying a Microservice”