I'll complete this section someday ;)

A project for a telecommunications operator providing services for several countries in Europe. As a team, we mainly created IMS based Value-Added-Services in Java. The project was very extensive and I had the chance to work on things in many areas (frontend, backend, devops).

The things I dealt with:

• development of a Java application for conducting functional tests using the SIP and Diameter protocols (something like Taurus/Postman). It is used internally by all teams as the main tool for testing,
• development of a provisioning system consisting of multiple microservices. Gateway, Eureka registry, Authorization, REST API services...
• development of a Java framework for IMS-based Value-Added-Services and creation of multiple services based on it,
• implementation of CI/CD workflows on GitHub/Bamboo/Jenkins,
• implementation of a dashboard React application, collecting data from multiple sources in one place.
• creation of automatically generated documentation,
• preparation of automated virtual machines for developers,
• creation of custom Gradle plugins and Docker containers,
• configuration of project build.

We used the SAFe framework in the organization and I am a Certified SAFe 5 Practitioner.

The aim of the project was to port a part of the ERP-like system from ancient technology (Panther, good luck finding what it is) to Java.

I was a team leader in the project. The difficulty of this work was the lack of documentation for the existing application. I remember this project as a lesson. It taught me, above all, how dangerous is technological debt and showed me live that when deadlines are chasing, adding new programmers to the project is the last nail in the coffin.

I was working on a vehicle simulator to test a platform that collects real-time information from vehicle sensors.

The application was supposed to allow the user to manually draw the route of the simulated vehicle and to mark events (such as: detection of sign/pedestrian/slippery surface, or connection problems) on the map. The drawn scenario was saved to a file and then it could be used for a real-time simulation using the protobuf protocol.

I created a website that displays the weather forecast. The scope of work included design, implementation and tests (unit and functional).

The backend was an REST API based on the existing service - Wunderground. This site's API was not entirely consistent and had some design flaws. My job was to improve this API by making an adapter.

As part of the exercises backend was written in both Jersey and Vert.x. Due to the limited number of queries to Wunderground API, the cache mechanism has also been implemented.