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
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!
I delivered a talk this morning at WordCamp Boston 2012 on how to find ways to fit web development tools… Read more How we can have Nice Things: my slides from WordCamp Boston 2012
The msys shell that comes with a Windows install of Git has curl, which is an awesome little utility, but… Read more wget in Git Bash
To be honest, I really like working in Windows 7. It’s fast, it’s stable (for me at least), I love… Read more The best of both worlds: A lightweight, awesome Bash shell on Windows
My slides for today’s presentation have been uploaded to Slideshare! I will post a link to the video when it… Read more Stepping Into Custom Post Types
Mouse over the landscape to see the effect I’m spending the bulk of this weekend at the HTML5 Tools Jam… Read more Parallax & CSS3
At the Boston WordPress Meetup this evening, I saw a presentation by Chris Brogan on “The Power of Content.” While… Read more This talk is about Content