Short introduction

My name is Mikhail Emelchenkov. By education I am computer scientist and economist. More than 17 years I am doing computer research, software development (application, system, network, mobile, web), administration of network environments, project management, usability, design.

In sections Portfolio and Resume you can see my extensive experience and scope of technologies used.

My offer - a solution to your complex, custom, research problems using information technology and engineering ingenuity. Personalized approach. Privacy Guaranteed.

Mobile platforms

Research and development in the field of mobile platforms and software. Android internals, adaptation to hardware, reverse-engineering applications and system software. Creating new applications.

Android iOS

Business software

Selection and development of software for the execution of business processes. CRM-system, computer telephony, VPN-network virtualization. Modules integration with CRM and billing systems, e-commerce solutions. Work on the server infrastructure.


Web solutions

Projects working right in a browser. Development and support of HTML5 websites, e-commerce systems. Optimization for high loads. Writing modules for CMS. Domains registration, web hosting.

HTML5 CSS3 JavaScript PHP

Project management

Managing projects on combining the principles of the system approach and Agile philosophy. An explanation why Scrum is good only on paper, and Kanban—a supply management system on Toyota plant, and nothing more.

Legacy software

Challenges connected with legacy systems. Modification of existing software by immersing in an outdated technology stack. Data conversion. Migration to a new hardware, moving to a virtual environment.

Apple hardware

Individual examination of problems, advice on choosing software. Solving technical problems. Repair and maintenance of Apple hardware. Assistance with collectible items.

Apple Apple Classic

First meeting

In the first place, try to describe in details your problem and your expectations for its solution. For example, a description of the problem, technical requirements, technology stack as well as other relevant data. Definitely need to specify the planned budget. This will give the minimum initial information to identify choices of promising solutions, possibilities of hiring external experts and determining start date of work.

If you need to perform a small one-time job, to solve a typical problem, get rid of the routine, get results fast and cheap—it is not my profile. Try searching for professionals on freelance exchanges, previously find in your company someone who can clearly define the requirements and will monitor the results. I can help you with this and act both roles of systems analyst and a project manager—this is my profile.

My contact info is at the bottom of the page.

Work process

Solving the problem of a customer is a process relies on combination principles of systematic approach and Agile philosophy, key steps includes:

  1. Application domain research, clarification of the problem.
  2. Elaborating user stories, forming product requirements.
  3. Conducting research to select appropriate engineering solutions.
  4. Continuous integration (development - deployment - feedback).

Continuous Integration process—a replacement for the traditional production, which has the beginning and the end. In today's world there are usually already exist some previous business processes, legacy systems, which should be organized into something new, meet the changing needs, to ensure the integrity of the self-developing systems .

This is a complex job that requires extensive practical experience and knowledge of related disciplines, synergistic component. The simpler and clearer result looks, the more difficult the underlying process. God is in the details.


In-house is a term signifying close cooperation of external experts with customer’s staff while working on customer's internal projects on its territory. For many projects that do not have detailed technical specification it is the only appropriate way of development. For example, one of our projects had been altered more than 10 times (see “Integration module of 1C:Enterprise 8.3 and Billing” in the Portfolio). In-house helped us successfully complete this project. With a fully remote working this would not have happened.

Of course, many projects can and should be conducted from a remote location, by distributed team. However, for tasks that are closely integrated into the infrastructure of the company and its business processes in-house is the only effective approach. Here are few examples.