2015 is behind us and the market is flooded with new languages and frameworks. A lot of them seem promising, and in the same time a lot of developers are talking about the death of Ruby and Rails.

After building libraries for multiple teams and consuming libraries from others Enrico Teotti came up with a list of best practices to handle errors, deprecations and releasing.

How do you make a deep copy of an object? Is it really impossible to unfreeze an object? Find these an other tricks on this post.

Rails server does all kinds of wonderful things. One of those things is taking JSON, parsing it and storing it somewhere. But how do you parse the JSON and where?

It's important to produce a clear, standards-compliant API. We're going to look at how to build an API which conforms to the json:api spec.

This is a list of Aleks favorite Vim plugins. You can find his dotfiles over at GitHub.

When you start your journey with DDD, it's quite easy to apply DDD in a fresh app. It's a bit more complicated for existing, legacy apps. This blog post shows how you can start applying DDD by publishing events.

Integration and unit tests ensure that changing code maintains expected functionality. What is not guaranteed is the code changes impact on library performance. It is easy to refactor your way out of fast to slow code.