As part of my consulting work at Human Made I contribute code to a number of different client GitHub organizations.… Read more Juggling SSH keys when using multiple GitHub accounts
I normally try to avoid parades, but there’s no way we were going to miss today’s ticker tape parade (right… Read more US Women’s National Team in the Canyon of Heroes
Gutenberg is the project name for the new WordPress block editor, a multi-year effort that launched to the world last… Read more Finding Things in Gutenberg Globals
At Human Made my local development environment is usually a Chassis virtual machine running in Vagrant. Chassis helpfully includes WP-CLI, so whenever… Read more A Few Fewer Keystrokes for Vagrant SSH
This post documents the process I followed to be able to run Torch and NVIDIA CUDA on my development machine after upgrading to Ubuntu 18.04 LTS
Since switching from Apple to a Dell XPS13 and Ubuntu Linux about a year ago I’ve been on the hunt… Read more Using Plexamp on Ubuntu Linux
In the midst of two days of dense, technical talks at LoopConf last month, the moment when I knew that my… Read more The Best Talk from LoopConf 2018
Last month I had the pleasure of attending this year’s edition of LoopConf, a developer conference that distinguishes itself from… Read more Loop Me ‘Round
In June I departed Bocoup, the open-source software engineering consultancy where I’ve worked since 2013. Since then I’ve been traveling, doing some contracting work and planning my next move, but I’ve also been reflecting on the extraordinary experiences I shared as a part of a very unusual company.
Attempting to apply a new code style to a large existing codebase with tools like ESLint can be a daunting prospect; when your linter shows thousands of errors, it’s hard to know where to start without derailing more important work. By using Git to determine which files we have recently changed, however, we can break this Sisyphean task down into manageable chunks that align with our existing sprint feature work. Progressive linting makes your whole codebase more consistent, one patch at a time.