Agentic AI researcher, software architect and experienced developer

For the Dream World, an immersive art experience built in soon to be
demolished abandoned gas station near Ostkreuz in Berlin, I delivered
an installation called "I see you in my dreams", in the form of interactive
synaesthetic projection located in front of the dance floor. Fluid visuals helped
to sustain the oniric vibes after the whole experience. I also delivered a smaller
installation using old CRT screen and generative analog video synthesis +
magnets for bending cathode rays.

I prepared generative visuals for the Angels In America opera staged at UNI.T
* the theater of Universität der Künste Berlin (Berlin University of the Arts).
The scenography included circular screen of 7 meters in diameter, where my
prerecorded video was displayed in the key moments of the play. According to
the libretto I prepared the following visuals: "The ghost of Ethel Rosenberg",
"Angelic Appearance", "Angelic Ejaculate". In terms of technique they are
using motion capture with kinect depth camera and fluid, interpolated, pixel
feedback loops generating illusion of space, where human arms generate
"feather" of wings, and the wings interpolate to light dispersed clouds.

At audibene I refactored the configuration system in order to prepare the
backend system for deployment in different environments on top of different
cloud providers. The new configuration system helped audibene enter the
Chinese market and to migrate from AWS to Azure cloud. I reduced the
backend build time from 20 to 7 minutes, boosting the productivity of a growing
backend team. I also introduced guidelines for contract-based API tests.

When I joined Bonial, the whole code base was a Grails monolith which had
accumulated technical debt from its startup days. The app was deployed
on expensive hardware, in a heavy release cycle involving almost half of IT
once every 2 weeks. By the end of my time there, we were deploying in the
cloud several times per day, with 0 manual testing policy, and providing our
APIs as a product to 3rd parties. I was responsible for the first microservice
deployed in AWS. Also, I laid the foundation for the future content delivery
infrastructure and established frameworks and shared libraries for our
microservice architecture on top of spring boot stack.
As Lead Developer, I dealt with the daily issues which arose from the
company's legacy code base. Eventually, I was able to address the very
root cause of our problems. The main added value that Bonial delivers
is geolocalized advertisement. However, this feature was also one of the
weakest areas of our system. The caching techniques we were using
were completely inefficient. I decided to reverse the architecture and move
geo-spatial indexes of published data from the database to edge servers
which we could scale horizontally on reduced AWS EC2 instances. I built a
specialized in-memory database populated by content publishing events, with
a reactive API which represented Bonial's content geo-distribution model. It
is convenient to build any geo-spatial services on top of it, like geolocation
queries, background geofencing queries (points of interest), geolocated
content queries, etc. Our team eliminated all the bottlenecks in the stack, and
now requests are served in milliseconds and daily traffic volume no longer
affects API response time.
While working at Bonial, I had the pleasure of participating in the evolution
of corporate culture which started from strongly coupled scrum teams and
developed into well-choreographed team of teams. Thanks to this experience I
can help scale up the agile process in IT.

Joining Bonial gave me a new opportunity to work in an international team
with people from all over the world. I joined the team in a critical moment:
when Bonial's user base was growing to the level of millions. The exponential
increase of traffic volume presented me with new challenges in adapting the
infrastructure for scalability. Databases could no longer cope with the amount
of queries and there were limited possibilities of scaling them horizontally.
Additionally, NoSQL databases started to expose unprecedented locking
impact on write operations. I joined Bonial's legendary backend team called
"42", which was responsible for all the mobile APIs and push notifications.
As mobile devices generated most of the traffic volume on the platform, most
of the performance problems were left to my team. In order to solve many of
these problems, I had to use all my professional experience with the whole
software stack including JVM tuning, memory management, transaction
management, connection pooling, and Linux kernel optimizations. Thanks to
my time at Bonial, I am capable of responding to the challenges of scaling
complex systems and finding bottlenecks with monitoring tools.

In the early 2010, NCDC was supporting insurance companies in the transition
from call center-based models to an online sales approach. By utilizing
modeling techniques based on UML, we significantly reduced the time to
market for insurance products. I was responsible for providing core software
components. These components were used by other teams to deliver web
solutions for the specific needs of different customers. The solution was
based on code generators exposing Oracle PL/SQL as native Java services
and web services (SOA). I chose lightweight Google Guice with support for
Aspect Oriented Programming as the container. Our solution was an order of
magnitude more efficient and resilient than available alternatives at the time.
The process was greatly simplified for developers since complete API clients
were autogenerated on demand according to each specific TIA system. Our
online sales solutions were based on Rich Internet Application utilizing Google
Web Toolkit and acting as an interpreter of insurance product metadata.
Our consultants were able to model insurance product in UML, generate
spreadsheets to be filled with tariff factors with the customer, upload these
documents and have this product available for online sales immediately.

Thanks to the financial success of the PCM system I designed for NCDC,
the company was able to compete on the market of software consulting for
insurance companies internationally. The NCDC team grew rapidly in this
phase, during which I was responsible for deployment architectures, promotion
of company solutions, mentoring of developers and building new integration
solutions which subsequently added value to our platform (e.g. support for
manual workflows).

I was able to help build NCDC from its very beginning. The idea behind the
company was to develop an innovative Business Process Management
system called PCM (Process Control & Management). I was responsible
for designing its architecture and the implementation of the PCM Engine
component, a virtual machine that interprets NCDC's proprietary programming
language with visual notation. The design was inspired by Petri net simulation
techniques and workflow system theory. The goals for the project were
to visualize business processes as automated work units. The system I
designed and implemented is capable of handling a virtually unlimited number
of business cases simultaneously which are generating millions of atomic
transactions. Additionally, PCM Engine provides per-case resilience, audit trail,
and overall performance analytics. Its advantages play an important role as a
component supporting integration with 3rd party systems. While PCM's design
was conceived as a solution towards the insurance industry and TIA system,
its foundation is flexible enough to support a variety of business purposes.

Panoramix started as a small internet service provider. It became a popular
free hosting platform for hundreds of websites and custom web applications.
I was responsible for system and network administration as well as web
development. Towards the end of my role at Panoramix, I also served as a
Java consultant for financial industry projects specializing in money laundering
detection.