Talks

Our employees actively participate in industrial conferences on high technologies. This section contains some of our presentations. While abstracts are in English, the presentations themselves are mostly in Russian.

  • Flying robots

    Who: Anatol Filin, Denis Eldandi

    Where: RIT 2013

    When: 22 апреля 2013 г.

    What is copter - flying robot with several propellers?

    1. Main components. Sensors.
    2. Architecture of app on examle og: Arduino, PX4.
    3. Controlled and autonomous flight.
    4. Photo and video shooting.
    5. External equipment. Communications.
    6. Field of usage

  • API plus fat client – a new paradigm in web development?

    Who: Andrey Lebedev

    Where: RIT 2013

    When: 22 апреля 2012 г.

    Any given major web service has its own API (Facebook, Flickr, Amazon, Vkontakte, etc.). But do smaller projects need one? What are the advantages of separating the front-end from the back-end through an API? Technology is quickly advancing, as is Javascript— not the language used for animating webpage elements, but the powerful development tool. Few people are surprised by the need to use frameworks and libraries like AngularJS or Backbon e. Single-page web applications are more actively competing with mobile applications due to how light they are and their simplicity. In this presentation, the advantages and features of developing using an API are covered: 1. The basic features and business and end-user advantages of single-page applications. 2. How to change development speed. After interfacing with an API, all system modules can process in parallel and independent of one another. This approach allows you to better concentrate on each part of the system without disrupting major development components. 3. Automated API testing methods. 4. Non-obvious advantages of single-page application search engine optimization.

    Slides

    Video

    Text

  • Usage of Agile in non-Agile projects

    Who: Artem Volftrub, Gleb Ilyinikh

    Where: РИТ 2012

    When: 3 апреля 2012 г.

    It's not a secret, that Agile is one of the most popular metodologies in the sphere of web-development. Indeed, majority of Internet projects are characterised with speediness and dynamics, shich makes it impossible to develop detailed specifications on the stage of prepararion or getting borders of project before the start of it. At the glance, this conditions perfectly fit for work with Agile.Unfortunately, starting to use Agile frequently brings different aspects, which makes usage of Agile less effefcrive or even unusable. In this speech, we will try to take a look at most frequently occuring problems and give practical tips on the solution. Main problems, which are discussed in this speech:

    1. What makes project non-Agile. Where is the border between desire to use Agile and practical use.
    2. Using Agile in projects with fixed cost.
    3. How to sell Agile to client, if he uses different metodology.
    4. Main features of using Agile in case of distributed team.
    5. Factors, which have an effect on Agile processes and solution methods
      - Distributed team
      - Correlation between iterrations
      - Unequal task load of team members
      - Pragmatic approach to testings
    6. On what projects it is better not to use Agile

  • Anatomy of banner system

    Who: Artem Volftrub

    Where: Highload++ 2011

    When: 3 октября 2011 г.

    This talk deals with a banner platform and its components and based on our experience of developing at least three high-performance banner systems. The major topics include principles of efficient display of banners, banner view limits and architectural structure and limitations of banner platform. Much attention is paid to synchronization of data between various system components. We also consider some issues related to banner platform statistical component: statistics that banner system can collect; dealing with large amount of data especially on unique clicks; methods of analysis of advertising campaigns efficiency. We also touch upon the issue of false clicks and police tools, system monitoring, as well as support and maintenance of typical banner system.

    Slides

    Video

    Text

  • Ways of protecting media content. Is DRM possible in Web?

    Who: Denis Eldandi, Aleksandr Kistanov

    Where: RIT 2011

    When: 25 апреля 2011 г.

    Large part of our projects are related to storing and publishing of video content on the Internet. One of the frequently asked questions of our customers is the issue of protection of content from illegal reproduction and distribution. There is a wide-spread belief that there exist software products and technologies that guarantee that reproduction and distribution of licensed content is impossible. This presentation deals with current technologies, their vulnerabilities. It also talks about open-source software having the same level of protection to that of proprietary and very expensive products.

    Video

    Text

  • Let us draw requirements

    Who: Artem Volftrub

    Where: RIT 2011

    When: 24 апреля 2011 г.

    Every project starts with collecting and understanding it’s requirements. Depending on development methodology (RUP, Agile etc) used by a team, they look differently, but they are always present. The main idea of this presentation is to use as much visual information as possible while preparing system requirements. Web systems which we mostly develop are characterized by large volume of web interfaces and rapidly changing requirements. The key to a project success is efficient communication between customer and development team. Since usually most of such communication with a customer takes place at requirements stage, it’s important to involve customer in the process as much as possible, to understand expectations and lower the chance of different interpretations of such requirements by project members. This presentation deals with modern methods of gathering requirements, describes specifics of web projects and their influence on requirements, and also analyses such problems as communication with customer, organization of the process of producing requirements for long-term projects and specifies major tools for requirements gathering. Presentation also deals with tools and methods of requirements visualization and interfaces design.

    Slides

  • What to consider when starting development on a high-load system. The Top-10 mistakes made even before development starts.

    Who: Artem Volftrub

    Where: HighLoad++ 2010

    When: 25 октября 2010 г.

    According to statistics, at the beginning of 2010, there were around 43 million Internet-users in Russia--about 37% of the country’s population. The great potential of this market, as well as its rapid growth, has led many companies to hurriedly try to fill this niche by making web-projects that will “change the world”. For a long time, the deterring factor for entering the web-app market was the difficulty of attracting an audience. After major social networks unveiled APIs for developing applications, the threshold for entering the market reduced to a minimum. Often, the efforts of only one developer are enough for an application to attract a million users. Farm Frenzy (Весёлый фермер), for example, has demonstrated that you can earn a fair amount of money in this market, which is why people have started investing in the creation of social network applications. A similar situation has been observed in other web-projects, which have nothing to do with social networks, but which are also meant for a wide audience. The development of Internet systems has its own quirks. If projects are managed following the old tried-and-true methods, the results will most likely be unfavorable. Additionally, many mistakes are made because project managers are poorly oriented with the technology and try to control the developers in every possible way. In this presentation, we will examine some of the most common mistakes, the majority of which are made before development begins, with real-world examples.

    Slides

    Video

    Text

  • From startup to public corporation

    Who: Anatol Filin

    Where: Whale Rider 2010

    When: 20 сентября 2010 г.

    In "From startup to public corporation" speech, Anatol Filin presented a development story of japanese company - ValueCommerce, which he took part in from the startup to one of the biggest corporations of it's period. Moscow office of ValueCommerce "gave birth" to Gramant company. 1. Main purpose of startup was tracking of sales with paying commission to the partner site, which made readress and payment. Part of commission was given ro company, which provided the platform. 2. An international team, specialising in development and ifrastructure, was gathered for startup. Sales were operated by japanese workers. 3. Motivation for team members were options mechanism - contract which gives an employee right to buy determined ammount of company stocks for lower price, in case of completing some cnditions. 4. Startup team released a version of system in 2001. Development took a year. System was expected to work on extremely high loads (nearly a billion of microtransactions a day) and gigantic ammounts of data. However, a small part of functional was demanded by market and during immigration time from previous version of system, which took a week, company lost a third part of clients. 5. After the release of new version, growth and employment of new members took place. This led to neccesity of changing managment processes. In result, 4 departments were created: Analytics, Development, Testing, Application Support. Moreover, every product got it's Product Manager - a person, who got understanding of market's needs, and uses it to help optimising system. Process of creating technical documentation was elaborated. 6. In result of organisation changes, chance to scale team geographically appeared, in order to outsource and divide work task. This led to oppening moscow office in 2003. 7. In 2005, half of ValueCommerce company was bought by Yahoo!Japan, because of successful buisness results and creation of new features. In 2006, IPO was released in Tokyo Mothers. Estimated value was $600 million. 8. However, after IPO growth stopeed and recession happened. After 4 years companies' value were estimated 8 times lesser than on IPO. Lots of employees founded their own companies. Gramant is one of them. 9. Looking back, companies' lost positions could be concluded: absence of espansion stratigies, devided buisness and IT, and absence of "great" idea.

    Slides

    Video

  • About Scrum

    Who: Artem Volftrub

    Where: Whale Rider 2010

    When: 20 сентября 2010 г.

    Scrum is a remarkable methodology for developing software; this conclusion is based on our practical experience using a variety of methodologies. Additionally, Scrum perfectly fits the unique features of our company (small teams, projects with vague requirements, fast-changing conditions). In order to better understand the essence of the problems covered in this report, we will need to present some features of our “habitat”. We’re certain that many people work under similar conditions, which are characteristic of most small teams:

    1. All team members are all-round specialists who can fulfill various roles on various projects.
    2. . A large number of projects. Several projects are actively in development, but the number of “potentially active” projects exceeds the number of developers.
    3. A large stream of internal requests. Potential projects must constantly be evaluated and preliminary research and analyses must constantly be conducted.
    4. . Remote team members are present.
    5. The absolute majority of projects are done on a fixed budget.
    When introducing Scrum, we found that we didn’t receive optimal results even when we followed described practices. We had obvious problems with quality, iteration periods, priorities and communication. Over the course of several projects, we saw similar problems, but we also thought up and implemented procedures which would allow us to satisfy the vital conditions for staying within an Agile framework. In this presentation, we will observe the most interesting problems we came across, as well as their solutions:
    1. Iteration planning without guaranteed resources.
    2. How to minimize the gap between iterations and how to handle bugs.
    3. How to minimize testing expenditures and economize resources.
    4. Documenting Agile projects. The eternal question, “Do we need documentation?”
    5. Projects with fixed budgets. How to satisfy the client and not come out empty handed.

    Slides

  • Java as the language of Web: evolution or rebranding

    Who: Anatol Filin

    Where: RIF+IBC 2010

    When: 21 апреля 2010 г.

    New life of Java: from corporate to Web application. JVM as the platform for languages of the future. Web evolution towards complication. Java evolution towards Web and simplification. Modern image of Java: simple development on powerful platform.

    Slides

    Video

    Text

  • Anatomy of the Internet-bank

    Who: Artem Volftrub

    Where: Russian Internet technologies (RIT-2010)

    When: 12 апреля 2010 г.

    Internet banks for individuals exist for quite a while, however recently they became considerably more popular. Some time ago personal Internet bank was more like a marketing tool, but today it is the real business tool that can generate revenues. Despite the fact that there are several companies on the Russian market that offer wrap-box solutions, most of banks consider building their own product as an alternative to current systems. The presentation deals with major technology issues that arise during development of an Internet bank. It also provides several recommendations based on the experience of development of a similar system for a bank holding.

    Slides

  • Grails. Search is over

    Who: Sergey Nekoval

    Where: RIT-2010

    When: 12 апреля 2010 г.

    Grails — new framework for web-development, based on Groovy language for JVM and combining the best and newest features from Ruby on Rails and Java tchnologies.
    Success of Grails is caused by fast education and development, based on using DSL (domain-specific languages) and serious support from Java community.
    This review presentation is aimed to create an interest and attract specialists from Java and Ruby spheres.
    We acquired some expirience on using this technology in Gramant and we shared it with audience.

    Slides

  • Pragmatic approach to documenting Web projects

    Who: Anatol Filin

    Where: Russian Internet technologies (RIT-2010)

    When: 12 апреля 2010 г.

    The presentation deals with documenting of the process of web systems development. Typical project is participated by a team consisting of specialists in various spheres: investors, business founders, business managers, analysts, developers, users, designers, testers, system administrators. All of them have different experience, different goals and speak different languages (sometimes even literally). Some roles may be not presented, some may be merged.
    There is a relatively developed culture of project documentation that includes traditional artifacts: the Vision, Business requirements document (BRD), Functional requirements (FRD), Interface requirements, Technical and architectural requirements (TAD), Testing requirements, Infrastructure requirements, as well as Agile artifacts such as user stories, visual stories etc.
    Web projects can vary greatly, there can be interface projects and projects with complex logics (financial, scientific), average sized and large sized, written from scratch and inherited from other developers. Besides that, customers may have different ideas regarding documentation, as some are satisfied with the simple list of features, some need detailed functional requirements, and some prefer Agile style. Teams can also vary: complete (analytics, designers etc), local and distributed.
    This presentation does not offer the ultimate remedy. Its main goal is to assist in choosing of the optimal set of documents required for successful development of a project considering project specifics and project team.

    Slides

  • How to build budget video-hosting system

    Who: Sergey Nekoval, Denis Eldandi

    Where: Highload++ 2009

    When: 12 октября 2009 г.

    This presentation describes architecture and specifics of major Japanese video-hosting (over 10 million hits every day) system. It shall be interesting to developers and system administrators of high load systems.

    1. Specifics of free hosting systems: free soft, cheap hardware, minimal labor expenses.
    2. Everything shall work and recover on its own: system administrator time is expensive. Monitoring, post-boot checks and auto patching.
    3. Memory is cheap, let’s buy more. Caching systems on PgQ – cheap and good
    4. SPoF – is it always bad? How to survive with only one central DB.
    5. How to make file storage. Cheap and expensive files.
    6. How to squeeze 100% out of hardware. Server is large, it will survive!
    This presentation is “anti-crisis” to a certain extent. Budgets reduction is the gloomy reality of many Internet projects.

    Slides

  • Mobile wars: Services vs applications in mobile world

    Who: Anatol Filin

    Where: Joint conference RIF+IBC

    When: 23 апреля 2009 г.

    This presentation is dedicated to mobile application world. Browser applications wherever possible push desktop applications out of business, however, in mobile world these trends are not that obvious.
    Sometimes mobile applications win (App Store), sometimes services (i-mode in Japan). Mobile application context includes several dimensions: network operators – mobile manufacturers – mobile devices OS manufacturers – application developers – service providers. All those players exercise considerable influence on mobile development. Besides that important role is also played by geographic factor (America – Europe – Asia) and, however strange it may seem, cultural factor.
    One of the problems we face is the compatibility and mobile standards problems. Porting of mobile application to a set of mobile devices sometimes can be more difficult than development itself. This is one of the reasons of existence of mobile platforms (analogy of virtual machine or semi-browser) that are the intermediate approach between mobile services and applications. Another intermediate approach includes browser services that use specific features of a phone: GPS, contact list, mobile purse, etc. Problems related to porting can make development of mobile applications unprofitable.
    The report provides an attempt to understand whether the key success factor is the right technology or the right business model.

    Slides

  • Three-tier architecture

    Who: Anatol Filin, Artem Volftrub

    Where: RIW-2009

    When: 18 апреля 2009 г.

    A review dedicated to evolution of information systems architecture. Advantages and disadvantages of each architecture. Different modifications of three-tier architecture are described. Main focus is on architecture of Web application. Variations of three-tier architecture are illustrated on the examples of reat corporative systems. Modern trends are described, and some hyporhesis on evolution of Web applications architectures in future are made.

    Slides

  • Scaling of banner advertising system with centralized database

    Who: Sergey Nekoval

    Where: RIT: Highload

    When: 22 сентября 2008 г.

    This presentation states that relational DB are scalable despite a wide-spread trend to create custom-build DBs (that trend is often spoken about at technical conferences). However, rumors on relational DB death are highly exaggerated. When data are highly connected (such as in affiliate marketing case) relational DB not only provides advantage in speed of applications development, but also allows to reduce risks.

    1. Presentation describes architecture of existing banner advertising system with over 500 million hits a day that successfully works on Japanese market
    2. Some problems related to system evolution and centralization of DB are discussed.
    Presentation highlights business benefits of investments into Enterprise-level DB (Oracle) at the early-stage and on possible scaling risks associated.

    Slides

  • Internet-advertising based on CPA model

    Who: Anatol Filin

    Where: Internet and Business Conference 2008

    When: 16 апреля 2008 г.

    This survey describes online advertising system with commission based on results that the speaker headed during his work at Japanese company ValueCommerce. The system was launched in 1999, in 2005 the part of the company was acquired by Yahoo!, and in 2006 the company went to IPO. Presentation provides concise description of the business model with major revenue sources. Company CTR and CPA performance for last few years is analyzed and major trends are provided. It also gives review of the market on the basis of information taken from available sources.

    Slides