RailsClubMoscow

    On April 19, a tasting of horseradish took place in Moscow under the guise of RailsConf. The scope of the conference is not comparable with the ones in the USA that I described on this blog, but the fact of its holding makes me very happy.

    The reports will be interesting exclusively to rubists and rails.

    All reports were in Russian. The average reports lasted 15-20 minutes. Unfortunately, the questions did not include speakers and answers to them.

    One of the distinguishing features of this conference is the presence of many (all?) Speakers at the hub Therefore, you can ask questions on the topic in the comments and I think you will get the answers.


    Name: Database Caching
    Tags: databases, postgresql, memcached
    Duration: 16 minutes
    Description: In some applications, you need to show data, the calculation of which can be a time-consuming process. For example, it may be some kind of statistics: the number of page views, the number of objects with which the object of interest to us is connected, etc. This can be done using memcached, but in some cases this approach does not work. The speaker talks about how this can be done by caching data in the database.
    URL: vimeo.com/4306281

    Name: Internationalization and localization of Rails. gem russian
    Tags: i18n, russian
    Duration: 18 minutes
    Description: A man talks about how you can create multilingual applications on rails using the russian gem. The report discusses the history of this problem, the attitude to the Russian language in the Rails core team and the possibilities of extreme developments in this direction. In general, the case of Tarkhanov lives and wins. Details on the link on the next line.
    URL: vimeo.com/4306404

    Name: How to make an attribute in Ruby on Rails
    Tags: tips, bugs, features, documentation
    Duration: 24 minutes
    Description: If you found a bug in the rails, wrote a patch and want to share it with the whole community, then you should not think that you have already done the main work. It is much more difficult than writing a patch to get it accepted. This report talks about ways to speed up the process of making your changes. In addition, different types of attributes are described. Despite the Rails core team's policy of shared responsibility for the entire project, different people focus on different parts of the framework. Who aims at what and can somehow speed up the process of adopting the patch is also described in the report.
    URL: vimeo.com/4306459

    Name: Productivity flirtim.ru
    Tags: database, caching, chat, web server
    Duration: 15 minutes
    Description: A person working on a loaded rail project talks about performance problems and methods for solving them. Despite the fact that the project was described very specific (browser game) and the requirements will be different in most rail projects, ideas and ideas are quite applicable for most rail projects.
    URL: vimeo.com/4317313

    Name: How to cross github and pivotal tracker
    Tags: ticket, github, pivital
    Duration: 11 minutes
    Description: First of all, this performance can be heard because nothing is visible on the slides. The man tells how the team in which he works wrote a wrapper on pivotal which allows you to use the git logs of commits in pivotal. The report is not very interesting because little specificity.
    URL: vimeo.com/4323263

    Personally for me the report on caching in the database was very interesting. This is due to the fact that literally on Monday I will implement the same thing in my project.

    Also popular now: