My first challenge when I decided to adopt Node.js to develop web applications was to find out how to write end-to-end/acceptance tests. My workflow to develop something new usually starts with a high-level feature test, so finding something like capybara for Ruby/Rack and RSpec was the logical first step.

When working on a project, committing and pushing to master is a no-brainer. Using feature branches is a logical step forward in a development process, but merging a branch back to master isn’t always a piece of cake, right? In that case, pull requests to the rescue!

Until less than two months ago, working with feature branches and pull requests were, for me, “the only way”. Then I started working at Barsoom/Auctionet, and there we usually work direct on master.

I’m writing this post to publicize the material I’ve wrote to help organizers to setup a coding dojo in Elixir to a group of non-Elixir programmers. The material below (and in this repo) exposes the basics of the language – just enough to starting coding. I hope this can help people to begin programming with this great language.

In my last post I wrote about a “bad part” of Ruby: how easily can it be to “leaky” memory with Ruby. Although that’s true, Ruby is a GREAT language and because of that, I decided to write a series of posts about topics that I like the most in it. Today I’m starting with how to extend classes and types.