My main proficiency is with Ruby and Rails. I use it day-to-day, and have been doing so for the last 10 years. I'm familiar with the latest versions of Ruby. I've also used JRuby and Rubinius on some projects.

I started using Ruby on Rails before 1.0 was released and have used it for numerous projects ever since.

Except for a couple years I always worked as a full-stack developer. Before 4-5 years ago that only meant I also worked with HTML/CSS and a little JavaScript. However, in the last years that changed into having my time split almost 50-50 between Ruby and JavaScript. I'm up-to-date with latest ES6 developments and use them in my Ember.js projects and some also in Node.js projects.

I built the Fit Predictor API with Node.js using Express. It involved using a bunch of npm packages (some listed as tags) and a solid understanding of non-blocking IO. I also played with state-of-the-art frameworks like Meteor and Derby.js for side projects.

Along with Ruby, and JavaScript, this is the bread and butter of my professional life. I wouldn't say I'm the best expert with some of the latest developments, but I am always a fast learner for new things and given the necessity I wouldn't shy away from difficult front-end issues and experiments.

I started using git just a little bit before joining GitHub in Feb 2008. I've used it almost exclusively ever since. At SSP we used a branching model inspired by git-flow[1], but nowadays I mostly use the simpler github-flow[2].

I'm familiar with the inner workings of git and some of the less used commands.

[1]: http://nvie.com/posts/a-successful-git-branching-model/
[2]: http://scottchacon.com/2011/08/31/github-flow.html

Architected configuration management for our servers with Chef when we started to having more than a couple of them in 2010. Since then I had worked with a bunch of AWS services, Rackspace, SoftLayer. We used Capistrano first, but later moved to a custom Chef based delpoyment solution. Lately I've been playing with docker, but I wouldn't say I have much experience with it.

I've been using relational databases since I started doing web development. I'm experienced with database normalization and with its tradeoffs. I used Postgres extensively at SSP for our in-house analytics processes which involved some very complex SQL queries with stored procedures.

We started using MongoDB for Fit Predictor at SSP as the main database 3 years ago. I set up the cluster, planned the schema, orchestrated backup procedures. I also created a ruby tool mongo_delta[1] which helped us create a separate replica database with only a few collections for the purpose of processing our daily map–reduce jobs.

[1]: https://github.com/sspinc/mongo_delta

I use jQuery in most of my front-end projects. I'm pretty proficient with it, although I have to look at the API documentation from time to time.

I used CoffeeScript to build the Fit Predictor API at SSP. Nowadays I'm only using it occasionally, mostly when dealing with packages for the Atom editor. I prefer vanilla JavaScript with an ES6 transpiler.

Personal details

László B.

Summary

Technical skills