Team lead at LogicNow, at backup-solution MAXBackup project. Specializes in low-level development, developing architecture, performance, debugging. Automation community COMAQA.BY activist.
Senior Software Developer in Low Level Programming Department at EPAM Systems. Right now he is a part of a development team of hierarchical storage management system. Has 15 years of development experience using C++ in various IT-companies in Minsk. Used to be a programming teacher at FAMI at BSU.
Lead developer/architect at LogicNow at MAXBackup solution. Specializes in design and development of high-load failover systems in C++
COMAQA.BY automation community activist, COREHard.BY hardcore development community activist, co-founder of DPI.Solutions company. More than 13 years of experience in IT. Main specializations: automated testing, C++ low-level development and lower. Management, sales.
OJSC "Banking Technologies Center" management deputy head. BSU FAMI assistant professor. Physics-Mathematics PhD. He is in lead of application development for banking.
Typical and unexpected errors of money and time calculations are going to be presented and discussed. The roots of all the problems are coming from 1985 and linked to imperfection of storing numbers with floating point in coprocessor and virtual machines (ANSI/IEEE Std 754-1985)/ Most of those errors are not connected to programming language which is going to be shown on real-life examples from different spheres.
In programming frequently occurs a situation when routine tasks appear, which can be solved once by effectively using code generating. Classification of such problems is going to be presented in the report in C++ context and solution is going to be advised based on clang tools family. Solution examples of real projects are going to be shown at the presentation.
We hear about mocks in Java, C# and multiple other programming languages, and what’s about C++? It appears to be very interesting: dozens of libraries which are completely different as to talk about functionality and programming style. How to choose an appropriate one for your project, what criteria to use? How to “make it friends” with chosen Unit-testing library? We’re going to try to answer all those questions.