Adding simple, easy to customize and reliable autocomplete functionality has always been one of the topics that I thought wasn't very clear for Rails applications. During my last project, I finally decided that I would do some serious research and find one solution that I could use later without hesitation. And here it is: my choice is to use Twitter typeahead.js library.
My favourite definition of the term digital nomad is 'Someone who flies across half the globe to look for good wifi in Starbucks'.
Working remotely comes with a lot of perks. Deploying to production in your pyjamas or fixing a critical bug while sipping coffee in your favourite bar may sound appealing, however, having worked more than a year remotely, I still had the feeling that I wasn't making the most of it. Recently I decided to give something more extreme a try. Continue working while travelling in Thailand? Why not?
Last weekend I watched a really enjoyable talk about the Readline editor by George Brocklehurst. It interested me enough to do some extra investigation. This article shares the results of my little research.
Before working for Ragnarson I was a Rails developer for nearly 2 years. When I finally became one of the "Perfect Programmers", I considered myself a guy who knew enough stuff to take another step forward. I felt ready for new challenges. But it quickly turned out that there was one important skill I was missing which was not related to any technical knowledge. In simple terms, I can say now that I wasn't 100% professional about my work. But what exactly does that mean?
One of the most common practices when writing controllers in Rails is using
before_actions to keep them DRY. Sure, repeating code is a bad practice and leads to maintenance nightmare, but what happens when the readability drastically deteriorates after making the code DRY to the max? Is it still worth it? Let's see how it applies to controllers, what are the consequences and possible solutions.
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.
Gems are great...
Gems are a superb tool for every Rubyist. They can help you rapidly implement complex solutions in your applications without having to reinvent the wheel.
The second edition of Rails Girls Łódź took place a few weeks ago and I cannot be more proud to have been a part of that – again. The recipe for a great workshop boils down to just a few good quality ingredients. Come along, I'll show you.
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. There is no limit to the number of processes so it is up to you how much of their...