As developers we constantly try to improve our knowledge. We are trying to implement features where the code will be easy to maintain in the future. But should it be a priority when we work for a client with limited budget or tight deadline?
It’s our annual tradition that we go to the biggest Ruby conference in Poland - wroc_love.rb. This year it took place from 17th to 19th March. It’s a really good thing to attend programming conferences for couple of reasons and here are my thoughts about it.
Testing your application is a crucial thing to ensure that everything is working as expected. It gives you a quick feedback if the new feature can be shipped and you didn’t introduce any regression. It’s pretty much an integral part of development.
We should always keep learning new stuff. For me, the so-called service objects were like a milestone. A lot of things started to look simpler with them. So how does the perfect implementation of service objects looks to me?
EuRuKo is the annual European Ruby conference, launched for the first time in Karlsruhe (Germany) in 2003. The first four editions were organized in Germany. Since 2007 it's moved from city to city across Europe. At the end of each event, people vote for the next edition's host city.
This is a final part of the series about Elasticsearch. We already covered installing and multi model searching. Now it’s time to talk about some of the more complicated stuff and try to improve the searching intelligence. Let’s dive in.
In the next post we will see how to improve searching intelligence, but right now let’s take care of the main part of our functionality - multi model searching.
For one of our projects I had to do some complex searching. After considering the complexity of searching by every possible column, and the importance of speed, I decided to use Elasticsearch.
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.
When I finally became one of the "Perfect Programmers", I considered myself a guy who knew enough stuff to take another step forward. But it quickly turned out that there was one important skill I was missing which was not related to any technical knowledge.