If your team is anything like the one I work with, everyone has their own preferred IDE that they use (Sublime Text, Atom, WebStorm, Vim, Visual Studio Code, etc…) and although most of them have integrated linting support that doesn’t guarantee all issues have been addressed before a Pull Request is made.
Read More »
I’ve been working on the EveryDollar.com Single Page Application (SPA) budgeting tool for the past year or so.
I recently gave a talk about Facebook’s React library at AngleBrackets in Scottsdale, AZ. The talk, React to the Future, is an introduction to React and then I start to touch on some larger concepts like Flux and Isomorphic JavaScript.
Wait, what!?! CSS for Developers? Aren’t developers supposed to know CSS? Yes, the title of this blog post and associated talk may seem odd at first, but I feel it reaches out to several audiences that need it… and one of those used to be me.
In the past I’ve given presentations, recorded videos, and written blog posts about fixing common JavaScript and jQuery bugs. This is a good skill to have, but what about working code? Fixing broken code is important, but have you ever gotten into the situation where your code works, but it doesn’t feel quite right… maybe even smells?
