Over my development life I've worked with many, many teams developing Elixir, Phoenix, Ruby, Rails, Go and React applications. (Thankfully, not all of those languages/frameworks at the same time.)
Here's where I've worked and what I've done.
August '16 → Current — Culture Amp
I love working at Culture Amp because I get to do what I love: mentor and grow junior developers. I also get lots of opportunities to help out other developers by working with them on difficult issues.
December '08 → Current — Programming Author
I have contributed extensively to documentation for Ruby and Rails. I started writing documentation for Rails in December 2008. The two guides I am best known for are the Getting Started guide and Active Record Querying guide. I also wrote the Engines guide and the Asset Pipeline guide.
After the success of Rails 3 and Rails 4 in Action I decided to strike out on my own and become a self-published author. I do this through Leanpub and have published two books (Multitenancy with Rails and Toy Robot) and I'm currently writing a third (Joy of Elixir).
You can read more about these books over on my books page.
As a part of this writing process, I developed a review tool called "Twist" which allows reviewers to leave notes on my books as they read them. It has been extremely useful.
January '15 → August '16 — Marketplacer
I worked at Marketplacer as a Senior Developer. Marketplacer is an application which powers sites such as BikeExchange (also in the US and a few countries in Europe), TiniTrader and BikeExchange. The overall goal of the application is to make it easier for stores and private sellers to sell their goods online.
My day-to-day work involved working on new features for the Marketplacer application, and leading the Core development team. It was here that I was first introduced to Angular and React and where I learned I had a strong preference for React over Angular.
July '14 → Jan '15 — LIFX
At LIFX I worked on a small team of 3 developers building their Cloud architecture using a mixture of Ruby and Go. This architecture allows users of LIFX lights to control their lights wherever they are in the world; and also provides integration with Nest. For example, if there's smoke detected in the house by a Nest smoke dectector, the LIFX lights will flash red.
November '11 → July '14 — Spree Commerce
I was hired as the Community Manager for Spree after showing a very keen interest in the framework. I posted a lot to the user group and then one day Sean Schofield (the CEO of Spree) asked if I wanted a job which was essentially being paid to maintain open source. I said yes.
At Spree I was _the_ Community Manager. This is a fancy title which means my primary responsibility was keeping the community happy. I did this by leading the development of the Spree ecommerce framework, answering posts on our user group, writing documentation and giving talks all over the world about Spree. In one instance, I was flown to London to consult with a large surf clothing distributor.
February '11 → November '11 — Reinteractive
At Reinteractive I worked as a consultant, doing Rails projects (which included Rails rescue projects; reviving legacy code bases) and code analysis of applications. The biggest project we shipped in my time there was the conversion of The ABC Shop to a Rails app.
April '10 → 2016 — Manning
I was contacted by Manning and asked if I would like to write a book. Around this time I was keeping my blog up-to-date with the latest Rails happenings, and they thought I would make a good author. It turns out they were right.
I wrote Rails 3 in Action, which was the first Rails book to show how to develop a Rails application using industry-best-practices when it came to Behaviour-Driven-Development (BDD) and Test-Driven-Development (TDD).
A few years later I got some help from Rebecca Skinner and Steve Klabnik and together we wrote the sequel: Rails 4 in Action.
Manning and I parted ways (more than once), and so there will not be a Rails 5 in Action.
2010 - GetUp
In 2010, I introduced a small team of PHP developers at GetUp in Sydney to Ruby on Rails and the best practices (such as BDD and Agile) associated with it. Our task was to rebuild the getup.org.au site from the ground up, using Ruby on Rails.
2005 → 2010 — Various
My formative years. Spent this time working for various companies and freelancing, doing whatever PHP or Ruby on Rails work came my way.