A few weeks ago, there was a post on Reddit, when the author asked a very interesting question, which I’m paraphrasing as “Are there any concrete examples where mutability has introduced a software bug?”. We all (hopefully) know mutable state is bad, unfortunately it’s the standard set by decades of programming. However, as hyped as functional programming is at the current era, it’s still not at large, and some principles are not well understood.

Almost one year ago, Node 8 was released. It was a major release and brought quite a bit of ESnext to the masses. Even then, back in June I recognized that one of the major pitfalls when working with Node are the callback-based APIs that (IMHO) pollute your code. Somewhat hidden in that release, was util.promisify, a native way of converting an errback (or Node-style callback) into a Promise. A Promise-based fs As Node 10 just landed a few days ago, I was excited to see the most common case for such an util (dealing with filesystem APIs) was being addressed in some fashion.

Glamorous is my favorite CSS-in-JS library for React and React Native. Coupled with styled-system, polished and prop-styles, it brings you the most complete and flexible approach to component styling. Among the many reasons to prefer Glamorous, is the ability to use JSX props for styling and not having to… Let’s take a look at an example of what I mean: <Box flex={1} justify="center" align="center"> {/*...*/} </Box> See? I didn’t have to name this particular instance of Box, and there’s only a couple of style overrides I was interested in, I didn’t have to create a new component for it.

If you’ve been around my site lately, you would not only have noticed a big redesign and a move to Gatsby, but something more subtle, hiding under the covers, almost unnoticed… That is, of course, links. As a visual cue for the readers, which will now know instantly which site they’re about to be brought to there’s an icon attached to them. This applies to only the ones I thought to be relevant to the content and audience of this site.

A lot … has … been … written about good commit messages and how it’s a very important part of team communication, specially in an open-source setting, and the benefits that such an approach would bring. But, as most things in programming life, unless there’s a clear blueprint and tools that aid with enforcing good patterns, these tend to be ignored, leaving us unable to reap their benefits. In this post, we’ll discuss not only what makes a good commit message, but we will focus on the benefits of following conventions, how to enforce them, and tools that will aid us along the way.

Improving your development environment with the help of Docker, Nginx and other tools

How to dynamically configure Single Page Applications through environment variables in a 12-factor app fashion

A bit of backstory I’ve been pretty invested in the Docker ecosystem for quite a while now, evangelizing about the greatest of its advantages, dealing with the quirks in production, and closely following every release and discussion. One of the main benefits Docker has brought to my workflow is that I seldom install software directly in my computer anymore. Not only that, uninstallation and cleanup have become something that’s a breeze, allowing my host OS (OS X if you’re interested) by extension to function even better, be less polluted, and use less storage.

If you’re doing software development these days, more often than not you would be working on a social application of some kind. Engaging user interaction, communication and sharing of content is pretty much what made the Internet become what we’re seeing now. In this quick post I’ll share with you some tips, snippets, pointers or links on how to add some of the most common social features to your web application.

This had been bugging for a long time, as has to many users before: OSX doesn’t seem to register simultaneous keypresses the way that Windows works, having many users wondering about N-key Rollover and whatnot. I decided to dig into it, cave around the forums, Google Groups and every available documentation, and the solution finally came with the aid of a software I was already using: Karabiner. I don’t remember exactly where I saw a discussion that led to this (re)discovery (which proves how hidden it was), I thought sharing is caring 😂.