Some time ago we mentioned on our blog that according to Clutch, Monterail was ranked as a market leader in Polish development companies, Ruby on Rails developers, and software companies in general. With more testimonials published on our profile, we’ve climbed even higher and managed to become #1 in Ruby on Rails category.
In February, Clutch - a Washington-based business analytics company, released 2017 edition of updated research of top development companies. We’re very excited to announce, that Monterail, competing with 100+ companies, was recognized as a Market Leader in Polish Development Companies and Ruby on Rails Developers categories, currently ranking on 2nd place in both.
If you've ever found yourself adding another boolean flag to mark your object's state, chances are you would greatly benefit from introducing the workflow or aasm gems. Those two are best-known and most well-proven state-machine solutions in the Ruby world. I had the chance to work with both of them and found the experience pleasing. Today I'm going to concentrate only on the latter. I encourage you to check both and decide what best suits your needs.
A recent confession by Piotr Solnica started another bit of drama in the Ruby world. I started writing this post just after reading Fabio Akita's response to Piotr's post - for me it shows all the problems with Rails' defensive mindset, but it also reminded me that Rails is still a pretty cool framework. Feel confused? Let's solve that.
At Monterail we like to try new stuff. We try new languages and new (maybe not so new) frameworks.
Have you ever wondered how many simultaneous queries your application sends to the database? A hundred, a thousand, or perhaps a million? Whatever your answer, we should be aware of the influence that this number has on the performance of our programme. I would like to introduce to you the rspec-query-limit gem (you can find the source code on our github in the monterail/rspec-query-limit repository): this gem is a rspec matcher that measures the numbers of queries being sent to the database in Ruby on Rails applications. The main goal of this gem is to prevent the so-called
N+1 problem from occurring, and to make us realize how many different queries are subsequently being sent to the database. Rspec query limit measures queries using Active Support Instrumentation which allows us to measure certain actions in Rails.
This summer, I spent a wonderful 2 months at Monterail. I’ve been asked to share my overall impression about my time spent there working on an open source project. It was an experience that changed how I view my skills. It helped me believe that I can, so I would like to share with you about how I felt and how I benefited from this experience more than what I did.
This year, EuRuKo was hosted in Salzburg, Austria. We haven’t been to a Rails or Ruby conference since wroc_love.rb and we were pumped to go there! I’ll just remind you, that the previous EuRuKo was canceled for political reasons and to secure the safety of attendees.
I suppose everyone can recall blog posts about building your own blog in 15 minutes with Ruby on Rails. Building a simple blog post page with Rails was as easy as writing
hello world in any other language. Nowadays, however, there are more and more articles about Elixir and it looks like the Ruby world has started to fall in love with Elixir. Because of that, I took the challenge and decided to check out how easy (or difficult ;-)) it is to write a blog using Elixir's web framework - Phoenix.