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.
In January I had the pleasure of speaking at the inaugural Day of REST event in London, where I presented… Read more Pay No Attention to That WordPress Behind Your Application
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
My work at Bocoup has taught me to fear the term “deeply nested” above everything else – Mike Pennisi
The hell with being a rockstar; I didn’t have the hair for it anyway. I make websites. ~ Mat Marquis