This is the second post of the series on our blog, in which I'll present to you the part of our infrastructure that is visible to the users. Here you can find links to past and, when we publish them, future posts:

Ruby 2.0 came with some pretty useful features like lazy enumerators, keyword arguments, convention for converting to hash. There is also `Module#prepend`, which is not that commonly used, but there are some cases where it really shines. Let's see what we can get from that feature then.

One of the most important things for applications is stability. There are various hosting platforms that give you virtual servers, where you can run multiple services.

I have recently changed payment service provider to Braintree on Shelly Cloud and would love to share the experience with you. This post will show a fast and easy way of adding credit card payments to a Rails application.

I would like to share with you the details of how we built Shelly Cloud, our platform for hosting Ruby applications, and how it works. This is the first post of the series on our blog, in which I'll present you with an introduction to the company and an overview of our stack.

Chef is a framework written in Ruby, and partially in Erlang. It provides an API for numerous system services.

Ever run into the situation where you had to perform some operation based on the value from select field? How did you handle it? Maybe multiple case / switch statements?

Maybe the right question would be: why was it nil in the first place? Could it be avoided? Was the possibility of nil a desired behavior? And why at all is nil even a problem? Let's find out and investigate some usecases.