I read that you learn more from a poor example than from a correct one. I don't believe this but that means my site will be a success.
Figuring out JS quirks
Was looking at some decompiled code from ES6 the other day, when I saw a line that looked like this:
Replaying changes from one git branch onto another
Where I work, we use git (like everyone else), and we follow this common pattern for development:
Code coverage for CoffeeScript and JavaScript using gulp and istanbul without pre-compiling
If you’re not aware of your code coverage when building a serious application, you’re not building a serious app.
jasmine-node, beforeAll & afterAll
On Feb 9, 2011, Fat (Jacob Thornton, one of the creators on Bootstrap) opened a pull request to add beforeAll and afterAll statements to the jasmine library.
Express View Engine for Rendering JSX Components written in CoffeeScript
This is an Express view engine which renders React components written in CoffeeScript on the server. It renders static markup and does not support mounting those views on the client.
React and JSX. class vs className, for vs htmlFor
Ember.Data Model Issues
I was working with some older Ember.Data code, and I came across a model like this:
Ember.Data Promise-Aware Properties (Cheaters Edition)
I have models like this:
Stuff to mind when writing ES6 code
These are some good tips I picked up browsing the ember and ember.data commits. Nice if you’re looking for best practices in writing ES6 code.
Post about Songbird on npmawesome
The folks at npmawesome wrote a blog post about the Songbird library I wrote.