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 was asked about what exactly is on that short list of iPhone applications I use. In no particular order:… Read more iPhone Apps
When I finally caved in and got a Mac last year, one of the unexpected killer apps was a little… Read more Handbrake
Energy Modeling in SketchUp
I don’t personally use Google SketchUp a whole lot, having more than enough on my mind just trying to figure… Read more Energy Modeling in SketchUp