At ModCloth, I’ve been working on an internal application that uses Ember.js as its front end framework. In learning Ember I’ve noticed some interesting architectural decisions they’ve made.

I’ve just ended a very long relationship that was hideously overdue for some closure. That’s right - I’ve left wordpress.

Are you looking for an A/B framework? Something you can use in the browser to toggle a user experience - do they see marketing promotion #1, or a picture of a cat?

At work we’ve been having some issues tracking down some nasty client side bugs. We know they’re happening in our Backbone views, but we’ve been unable to locate them with any accuracy due to the errors bubbling all the way to the window.onerror handler.

One of the projects I’m working on deals with source maps.

CoffeeScript, what can I tell ya - I didn’t want to love it.

EDIT: My fork is no longer needed. The folks at docco saw the same thing and recently ported over the library to use highlight.js.

I spent a good bit of time working on the Esvalidate code that comes with Esprima, trying to get it to work smoothly with my sublime plugin. After submitting a massive pull request to the author of Esprima and our reviewing my code we came to a conclusion - the new code was better served in its own library.

A friend and I were working on some code together when we found an interesting edge case in .Net that neither of us knew about. This is what we knew: if you have a class with a protected field in it, if you declare a private class inside of that class, the private class can access the protected variable. The example below shows what this looks like.

I’ve recently created a portfolio on Pathbrite. If you haven’t heard of Pathbrite, they are a company aiming to: