I think Ember.js has the potential of becoming the go-to JavaScript MVC framework. The architectural decisions made, boilerplate added, auto-updating templates, a class system and property bindings make it stand above the crowd. But, speaking for me personally, it’s a tricky project to get your hands on. This part will be introductory trying to build some foundation for the upcoming parts. A Quick JavaScript MVC Refresher If you’re familiar with other JavaScript MVC frameworks (such as Backbone, which I’m a big fan of) feel free to skip to the next section.

Cucumber is a very vibrant eco-system on it’s own. It became the defacto-standard tool for high-level testing and a great addition to the Behavior Driven Development set of tools. I’m sharing with you a list of tips related to it. The Tips 1. Write Declarative Step Definitions I thank this has become so common-practice, and I totally advocate the decision of removing web_steps.rb. As you go to the roots of the process itself, it’s all meant to be described in a language that’s both familiar to your end users and yourself, but also uses dead simple domain terms, as in a token for a conversation.

Tmux is a multi-platform terminal multiplexer similar (and for me, better) than GNU screen. I’m describing a new and simpler way to share you terminal interactively. It’ll be a read-only of course, that’s why it’s a showcase.

Always wanted to bend the Markdown markup language to do things it wasn’t designed to do. I love the language’s simplicity, and that’s precisely what gets in your way if you’re thinking about What if it were just a little more dynamic?. Basically, what we’ll do it’s to tweak the parser/renderer a little to allow this dynamic processing of our input, and to get in the middle of the rendering process to achieve our results.