Sparks of our daily work and broad point of view on the industry we live in.
For about a year now, the support team of one of our high-loaded instruments has been using an ML-system of our own development, the Problem Detection Platform (PDP). This service can analyze logs and automatically classify errors. As a result, the support team does not get a bunch of raw data from the logs, but rather information that can be handled quickly and conveniently.
We keep explaining how True Engineering builds its support processes. In this paper, we’ll go over the main tools that provide our teams with monitoring and alerting functions.
When we started building the True Engineering platform, there were no uniform rules for architecture design. Different teams used different tools, different designations and levels of abstraction. In such a way you can’t even compare similar solutions with each other, and someone looking at the architecture of a project for the first time usually needs a guide to tell you what exactly it presents. We decided to unify approaches using the C4 model, which provides a comprehensive description of software architectures.
Today we’re going to take a closer look at how we’re transforming our testing processes by means of implementing automation standards and embedding automated test plans into the development process.
Some time ago we decided to analyze the experience we have accumulated over the past years of projects in DevOps methodology. We have evolved along with the market and now it’s time to capture the best practices to plan further development. In this article, we will share our vision, in which directions we will move and which particular tools and skills we will develop.
Some time ago, we had to modernize the frontend monolith of a large high-loaded system running 24/7 transferring it from the outdated Knockout framework to modern React. We want to share our experience on how to facilitate such a project.
On the corporate portal of one of our customers, some users’ birthdays were not displayed correctly in their profiles – the page showed the date before the correct one. Our developers found out that the reason for this error was hidden deep in history.
