Spend less than 2 minutes to discover three simple tricks that will help you to be in the coding flow! Write the code in the more effective way. Code with better quality. Be more satisfied with the time spent on programming.
You’ve probably read or heard a lot that the two most difficult concepts in computer science are naming things and cache invalidation. The quote has appeared numerous times in books, blogs, and other programming sources in one form or another. While the only remedies for coming up with names are practicing a lot, being clear in our intentions or having a sudden epiphany (none of which are quick and simple), Rails tries to help us with the caching part as much as possible. Caching can significantly improve web application performance. This requires little additional code, especially if we have a large number of complex partial rendering.
On the latest Euruko Ruby Conference (Bulgaria, Sofia, 2016) I had a lightning talk about a different approach to data verification. Today, I want to share and explain more of the good stuff in validation.
In a Ruby on Rails application, we use validation...
There have been a lot of buzz around service objects in Ruby community. It started some time ago and new articles about them popped up like mushrooms. I still think about myself as a “developer in progress” and I think it’s a good approach for all of us. 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?
This article is the next episode in our Flow series. You can find the first episode here. In this part, we will talk about daily routines that can help you go into the flow state
How you start is how productive you are
The most effective ways to enter the flow state are focus and involvement. This is why it is so important to start in a good way. It has a critical impact on your productivity and state during the entire day.
Hey there traveller, I want to share a story with you. Some time ago I set off for a programming journey. This has been a fun and rewarding adventure. It was also filled with unexpected frustrations, roadblocks and dangers. I have been on the learning...
There comes a time in your life when you apply for a job. Sometimes, your potential employer gives you a recruitment task to check your skills and qualifications. When applying to Ragnarson, one of my tasks was to redesign the existing logo. In this...
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.
In 2010, EuRuKo was organized in Kraków, Poland. It was my first time at this conference.
I still remember two things from the conference:
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 previous post
we saw how to install Elasticsearch and import data needed for searching. We also set up basic
searching for the
House models. 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.