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 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
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