Experience

eyeo

• Germany
• Technology, Information and Internet
• 100 - 200 Employee

• Chromium Developer

  • Dec 2019 - Present

  One day I found myself thinking that every opportunity to write in C++ again is perceived as a cause for celebration. Now it's like a holiday for me every day. Plus the opportunity to work with the guts of browsers again. It's been a long time since I swore at Mozilla code and now I'm swearing at Chromium code. I have to admit that I do it less often. The challenges are inspiring. One day I found myself thinking that every opportunity to write in C++ again is perceived as a cause for celebration. Now it's like a holiday for me every day. Plus the opportunity to work with the guts of browsers again. It's been a long time since I swore at Mozilla code and now I'm swearing at Chromium code. I have to admit that I do it less often. The challenges are inspiring.



OnTarget Inc.

• 1 - 100 Employee

• Team Lead

  • Feb 2013 - Dec 2019

  Have you ever really been ready for anything? No, really, no matter what happens, you are ready and you cope. I can tell you that I have been and it's fun. I didn't expect myself to be able to do so much and in so many different areas. After that experience, sometimes it's easier to say what I *didn't* do than to list what I did. Computational biology, cybersecurity, fintech, blockchain, social apps, just the first 5 topics I can remember. Yes, and this is the first time I've put off C++ development for a long time in favor of Java, Kotlin, and Node.JS. Show less



FotoStrana

• Saint Petersburg, Russian Federation

• Software architect, desktop solutions

  • Mar 2012 - Dec 2012

  It was a challenge for me to return to the everyday realities of a Russian company and to be limited by a modest budget. It required using a bit of magic with personnel to assemble the team, adjusting the production process by hook or by crook, and wielding a heavy blunt object to get the needed resources. Weekdays... It was a challenge for me to return to the everyday realities of a Russian company and to be limited by a modest budget. It required using a bit of magic with personnel to assemble the team, adjusting the production process by hook or by crook, and wielding a heavy blunt object to get the needed resources. Weekdays...



Unison

• Armenia
• Software Development
• 1 - 100 Employee

• Development Manager

  • Jun 2009 - Sep 2011

  Oversaw the development issues of cross-platform client for Unison Server. Planning iterations of development, access arrangement of the necessary resources and production processes organization. Support for communication between units.The major release SaaS-oriented product was delivered in time. Unison was named "Cool Vendor of the year in Unified Communication 2009" (Gartner)***Some IT people in Russia believe that after 35 you should change your occupation. Leave software development, and became, say, a manager. But most of them have never thought about what it means. We (developers) are not accustomed to convince, to persuade, to argue, to maneuver. In the best case, we suspect the existence of these tools, but... there is no fun to use them. Show less

• Team Lead

  • Aug 2007 - May 2009

  Supervised department of JS / XUL developers. Carried out work planning, assessment deadlines, writing specifications, goal setting, monitoring, interaction with QA, designers and other departments of the developers. Took part in the selection of technologies, discussing style, code review. Also, was involved in the search for new employees and personal training.As a result, created a modern interface for cross-platform product that interacts with the multithreaded libraries. The separation between JavaScript and C++ served as a natural delineator for an interface and business logic. ***World is crazy for an open source. Somehow, all believe that if open source product (somehow) works, there is no trouble to adapt it for similar purposes. In fact, the last thing developers thought on is your needs. Show less

• Developer

  • Sep 2005 - Jul 2007

  Developed interfaces for different products. The first project was a SIP-client, slightly stripped-down analog of Skype. Fully developed product interface using the designers' specifications, MFC, and a small amount of magic.In the future, was doing research on the adaptation of developments the company for Mozilla Gecko Engine. This work formed the technology development company for several years in advance. I developed the basic tools for working with XPCOM, the process of introducing third-party components into Gecko, JavaScript-trained developers working with XUL. ***It happens so, that many experienced developers not fond of GUI development. "It's too simple" said one. "Our skills are not in demand, if we start to paint a pictures" consider others. Do not believe them. In fact, they are frightened. Core level (almost) always well-defined, or at least can be understand how and what needs to be done. The GUI is more prone to chaos. To make a truly comfortable and attractive interface you will need to take into account the huge number of things. Create a simple table (from scratch) in fact is a nontrivial task. And do not forget that non-developers, for whom the system things are too complex, will pay the utmost attention to your work. Show less



SmartBear

• United States
• Software Development
• 700 & Above Employee

• Developer

  • Aug 2004 - Sep 2005

  Was responsible for testing profiler AQTime. In my line had been planning and testing process, the distribution of roles among the testers, the creation of automated regression testing, reporting on the status of the product.A year later, in addition to the responsibilities of a tester, began to develop components for more than one product company, IDE for testing TestComplete. Create a library for working with Windows Common Controls and several other modules. ***To work at the top of your bent is the best way to find out the boundary of your abilities. But... it is not worth while. Show less

• SQA

  • Jul 2003 - Jul 2004

  If you believe that the QA is boring, try to answer the following questions. You have a profiler, which seems to be working. How is satisfied that this is so? How sophisticated code will you have to write for the tests? And how many tests should you create in general? And finally, what actions will you perform, if deadline is approaching, but you'd like to be sure that everything is ok?