I'm Boris — a founder and engineer. When I was fourteen, I got a book on HTML and wrote my first lines of code in Notepad. Seeing my own creation appear on the page from just a few keystrokes fascinated me, and that feeling never wore off.

The first real things I made were two hackathon wins at university: an IPv6 messenger and a tool for sysadmins. Both are lost to time, as hackathon projects tend to be, but they led to my first contract: an industrial platform for Vertro that is still in production, and still growing, eight years later. In the years since, I've gone from frontend engineer to staff engineer, tech lead, and founder, building systems that thousands of companies rely on daily.

Most of my work starts in the same uncomfortable place: the problem is real, the business needs it solved, but the shape of the software is still unclear. Scattered requirements, old systems, hidden rules, and people who understandably just want the thing to work. That's the part I enjoy: taking a half-understood problem and turning it into a live product. And when the system is old, the goal is never to keep it on life support — it's to bring it forward.

If I hold one conviction about this craft, it's that understanding beats brilliance. A team that truly understands its users and their world can ship a beloved product on ordinary engineering; without that understanding, even an engineering miracle goes unappreciated. It's probably why I like arriving in a field I know nothing about. Every domain turns out to be deeper than it looks, and learning it well enough to build the right thing is as satisfying as the building.

Outside of work, I'm interested in architecture, old cities, medieval and ancient history, perfumes, jewelry-making — objects that feel like someone cared while making them. Lately I've been learning game design and creating small games: my own little worlds with their own hidden rules.