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.
I recently contributed an article entitled A Facade for Tooling with NPM Scripts to the Bocoup blog. Package.json script aliases… Read more Blog post on Bocoup.com: Using NPM script aliases as a tooling facade
I had the pleasure of speaking in New York this month at EmpireJS, and the video of my talk has… Read more Side Projects, Front & Center! from EmpireJS
In my JS Unit Testing presentation today for WPSessions (slides for the talk are available here), I showed a WordPress… Read more Enhanced Twenty Fourteen Image Navigation
Yesterday we formally kicked off the work to fix JSHint errors in WordPress Core, after a week of preparation, decisions,… Read more JSHint patches are landing in WordPress Core
Recently a friend suggested I check out a font called Blokk. Blokk is aptly named, as it’s just a typeface… Read more Blokking In Your Designs
Towards the end of August, Underscore.js and Backbone.js were added into WordPress core in preparation for release 3.5 (trac changeset… Read more I’m Speaking at WordCamp Providence!