THE PURPOSE OF CODE
April 16, 2016
Any employee who works on an IT project should be able to explain what it is and why they are doing it. This helps to define a single goal and a single purpose both for an individual employee and the whole team. A short answer not only helps to focus the effort on a single goal, but also provides an opportunity to measure success.
Co-organizers of IT NonStop Voronezh:
Voronezh State University and the Faculty of Applied Mathematics and Mechanics.
Technology Evangelist, Microsoft, Russia
Alex Belotserkovskiy helps partners and users of Microsoft’s technologies design and build high-quality solutions. He is engaged in technological IoT evangelism in Russia and other countries in Central and Eastern Europe. Before joining Microsoft, he received the Microsoft Azure Most Valuable Specialist Russia award and advised Microsoft Azure clients in Russia and CIS countries, from startups and developers to corporate users. Alex is a constant speaker at Russian and international events.
Senior Developer, DataArt
I began my career at DataArt in 2011 as a Web master for internal projects. Today I engage in such activities as selling, developing and testing large international internet applications. I’m also currently developing the client side of a product for a financial company. In addition, I am a regular participant in various IT events held in Voronezh.
Senior Developer, Technical Evangelist, DataArt
I’ve been working in this industry for over 15 years, and have 12 years of experience developing mobile applications and applications for embedded systems. My interests: iOS and Android development in all its forms and manifestations (Android Wear and Apple Watch, Apple tvOS, Andorid TV, Auto and Apple Car).
Senior Android Developer at DataArt and GDG Dnipro Organizer
The main interests of Constantine are development for Wearables, especially for Android Wear, Google Fit, Reactive Functional Programming with RxJava, and cross-platform mobile development with Xamarin.
Senior Ruby Developer, Dataart
I graduated from Voronezh State University. I used to work as a system administrator and develop sites using Bitrix, but then I had an epiphany.
Solutions Architect, DataArt, Saint-Petersburg
Vyacheslav is a Solutions Architect in DataArt. He’s been working with software development for 18 years. He’s worked with various industries: finance, information security, travel. Vyacheslav is a wizard, who started working with .Net in 2000, when first Beta-versions only came out and he is still on top of modern technologies.
I’m a Senior Project Manager. The technologies I work with are PHP, MySQL and a bit of node.js. I try to develop my management abilities without abandoning the technical side. Before joining DataArt, I was the team leader in shopotam.ru and the Director of IT in Doctornet.pro.
Google Developer Expert. Tech Lead Android at Mobile 2 Business. Host of Android Dev podcasts.
I am madly passionate about the Android ecosystem. “Quality, performance and stability describe my approach to development.
11:00 – 11:35
“Android. Let the manual testers rest. WebDev. Why do we need automated testing of applications?”
Why does every developer (experienced or not) need to test the automation of their applications? How do we do this and maintain it today? What changes to the architecture of an application are you required to make in order to make launching tests on the local JVM more convenient? How do we transition to MVP without trouble? In addition to these questions, we’re going to talk about the tools for mockups in Android, advanced usage of Espresso 2 and integration of tests in the CI process.
11:40 – 12:15
“Why do we need an automated testing of applications?”
Is the quality of software connected to automated tests? And in what cases is testing required? We will consider the value of writing unit and integration tests for web applications. This is of great interest for mid-level and large projects. Novice programmers will learn about testing applications and how it works, while professionals will have the opportunity to view examples of implementation. I will explain this in a simple way and with examples. Furthermore, I will leave the source code on github.
12:30 – 13:05
“The Internet of Things for developers - Microsoft's vision of the problems and their solutions”
“The very concept of Internet of things has been around for many years, but only in the last few years has it become quite popular. What does it mean? What problems face anyone who starts building their own IoT solution and how do we solve these problems? What aspects should any developer consider at the beginning of a project? Let’s talk about how Microsoft sees the Internet of Things from the developer’s point of view.
13:10 – 13:45
“Android TV Development”
“Operating Systems for TV” is a relatively new field of work. Just like in every research and development area, the main goal of this presentation is to figure out what can we do with Android TV, how we can do it, what opportunities it provides for programmers, and what restrictions it imposes on the code. We will talk about the features and potential of Android TV, focus on the specifics of control and UI, discuss every new feature of Android N preview for Android TV, and answer some questions like “Why do we need it”, “What will happen in the future?” and “What new features of Android N will help us create more interesting applications.
13:50 – 14:25
“What is a “good” API and why does your product require it?”
No modern product can live without an API. APIs can be external, public or internal. However, the requirements for creating extensible, versioned, tested and documented software interfaces are similar. In my report, I will talk about how and why we need to create such APIs, what best practices are available right now, what to avoid and what to pay attention to during the design process.
15:25 – 16:00
“Dagger2.0: Dealing with dependences the Google way”
If you are an Android developer, why do you have to wait while the backend team finish their work with the server so you can start working on the project? Skillful use of the dependency injection framework allows you to begin a mobile project at any time, replacing the logic of the server side work (and not only) with mock data and it’s then easily switched over at the right time from the mock module to the module with real logic. One of the best dependency injection frameworks today is Dagger 2 from Google. We will become acquainted with it and will consider its advantages, risks, and use cases.
16:05 – 16:40
“Augean stables: supporting someone else's code”
Why should we rewrite everything and spend time on restoring the logic of business processes when we can solve problems in a different way? Are you familiar with a desire to rewrite whole modules or even projects? Is it necessary to suppress this desire? For many programmers, including very experienced ones, working with other people’s code can be a serious obstacle. We will try to figure out what risks are involved and how to minimize them.
16:45 – 17:20
“A major Rails5 release is right around the corner”
The 5th version of the Ruby on Rails web framework is coming soon. Every major Rails release brings not only many cool features, but also a major headache caused by the need to upgrade existing applications and gems. However, if you want your application to live a long time and grow, you need to know about every update, understand the reasons behind them and be ready to adapt your code. We will look through the new functions of the framework and evaluate the significance of innovations based on small web applications. We will also look at and try out the new components of the framework, figure out how to update the existing applications to Rails 5, predict when it’s best to switch to the new version and discuss situations when your favorite gem does not work with the new version of the framework.
Voronezh State University
University sq. 1
Registration is closed
We suggest for presenters to focus on the tasks and impact of their projects along with their roles and technologies, which were used during the work. Aims may vary, e.g. some projects required elegant solutions while others required swift ones.
Every report is viewed by the expert board of IT NonStop. This board includes senior specialists and project managers from DataArt. The experts are ready to provide support with the preparation of speeches and presentations.
The main principle of IT NonStop is “case after case”. We expect the reports to be based on specific solutions and cases, and request one slide of each presentation to be dedicated to the following question: “Why did you do it?”
- Duration of report (30 minutes)
- Short description of the report (300-400 symbols)
- Full name
- Position held
- Current place of employment
- A brief text about yourself (300-400 characters)
- Photo in .PNG format
Abstract Deadline: 2016-03-25
Deadline of Full Paper: 2016-04-08
- Reimbursement for travel and accommodation
- Lunch and coffee breaks
- IT Nonstop conference souvenirs