Telegram, Facebook Messenger, Skype, Kik, Microsoft Bot Framework, Slack, Twilio, WeChat, Whatsapp, Viber, Twitter, SMS

I'm passionate about Ruby. I like it's focus on simplicity and productivity. It was really created for programmers' happiness. Apart of a programming language advantages I value it's vibrant community, RubyGems and Rails.

This is my strongest skill. I learn something new about Rails every week and even every day. I enjoy reading blog articles, improving my Rails internals understanding and sharing my experience about Rails development. Sometimes I contribute to the Rails source code.

I tried Javascript first before learning Rails. It's an easy to start language every web developer should be familiar with nowadays. However Javascript becomes a powerful tool for those who know and use it a lot. During my working experience I tried different JS frameworks. As a full-stack web developer I use it a lot.

As a full-stack web developer I work with HTML every day. I tried HTML first when I was in school. I use ERb, Slim and Haml combining with Rails for a long time.

As a full-stack web developer I work with CSS almost every day. I tried CSS first when I was in school. I use Sass/Scss combining with Rails for a long time.

I'm an experienced Git user. I work with git daily, I know many different features of git and completed a couple courses related to git.

I started using SQL earlier then I used Rails. I read a book first and then I learnt it in the university. My first university thesis was related to Rails and SQL database design. 

During my development work I deploy frequently. I deployed many times with Capistrano setting up a deployment processed from scratch. I have a decent Docker understanding and used it for more than a year now. Also I can do a simple and very fast deploy to pre-installed Digital Ocean server as I wrote down steps for it after doing it many times.

I was doing testing from my early days as a Rails developer. After years of development I have a better understanding what I should really test and when. I always aim to a reasonable test coverage.

On one of projects I worked on we used Elasticsearch and then we switched to Algolia. It was a great move and our search UX was improved drastically. I'd recommend to use Algolia instead of Elasticsearch if you are looking into column (not documents) search.

I understand what's SEO and what it means for the business. I have a decent SEO experience working with Rails: using moz.com, generating sitemaps, working with links, renaming images on upload, optimizing titles, using slugs, etc.

I completed 10gen courses on MongoDB and used it in my startup a while ago. I worked a lot with Redis inside Rails apps. I have a good understanding of different NoSQL concepts.

Personal details

Sergey A.

Summary

Technical skills