Systems is the broadest technical part of my work. It brings together the software, digital infrastructure, interfaces, tools and experiments I build across very different areas of business and personal interest.
Some of these systems are large and operational. In agriculture, I work on ERP platforms and tools for grain traders and brokers, market monitoring, commodity and logistics data, freight brokerage, and infrastructure that connects different participants in the trading process. Together with industry partners, we also created some of the first Ukrainian grain market indices based on data from the Ukrainian Grain Association and brokerage companies. Other projects explore how agricultural transactions and market infrastructure can work with blockchain and new forms of digital settlement.
But Systems is not limited to agriculture. It also includes the infrastructure behind my publishing projects, book series and editorial experiments: websites, landing pages, discovery tools, publishing workflows and language-related systems. Some of them exist to support a specific book or project; others gradually become independent products of their own.
Another large part of this section comes from software development itself. I build tools for web development and AI-assisted coding, agent workflows, generators, reusable skills, internal development utilities, analytics systems and interfaces. Some are practical tools I use every day, while others begin as experiments designed to answer a simple question: could this process work differently?
The same applies to design and commercial projects. Systems includes websites and digital experiences for my apartments in Menton, tools and interfaces created around branding projects, and work connected to Blue J Vodka and other consulting projects. I still work in brand and business consulting, both in Ukraine and internationally, so technical development often becomes part of a much broader brand, product or business problem.
And sometimes a system exists simply because I wanted it to exist. A good example is a player that turns YouTube Music into something closer to the old Winamp experience. It does not need to belong to a larger business strategy to be worth building.
So this section is deliberately eclectic. Systems can overlap with Focus, Books, publishing, branding, consulting or something completely unrelated to the rest of the site. What connects everything here is not the industry. It is the method: identifying a problem, designing a structure around it, and turning that structure into something usable.
This is essentially my technical toolbox: the things I build as a programmer, product designer, systems designer and someone who prefers turning ideas into working infrastructure.