I've been building for the web for 20+ years — real estate platforms, nightlife apps, media-heavy galleries, databases with millions of rows. Different industries, same throughline: figuring out how the tech actually serves the business.
These days I work as a fullstack engineer — React, Next.js, and Laravel on top, PostgreSQL and MySQL underneath. I've written my share of pixel-perfect UIs and designed plenty of REST APIs, but the work I enjoy most sits where the front end meets a query that needs to come back in under 50ms.
Code is only half the job. The other half is thinking clearly — modeling data before you write the migration, profiling before you optimize, weighing trade-offs honestly instead of reaching for the shiny option. Good software comes from clear thinking and honest collaboration as much as from the right framework.
On paper: MS in Computer Science and BS in IT Security, both from Kharkov National University of Radio Electronics (KhNURE). In practice: it means I architect with both performance and a security-first mindset baked in from day one.
Fullstack isn't a label for me — it's how I think. Most of the interesting problems sit on the boundary between the front end and the back end: a form that has to validate the same way in two places, an optimistic UI update that has to roll itself back gracefully when the server disagrees, a permission model that has to make sense to both the API and the UI. Working across the whole stack means I don't have to throw the problem over a wall to solve it.
The database is where I spend a disproportionate amount of my time — and I like it that way. Most of the apps I've worked on lived or died by how well the data layer was designed: real-time analytics dashboards, property search with geospatial filters, platforms with thousands of concurrent users. Indexing, query plans, replication, migrations at scale — the unglamorous stuff that keeps software feeling fast when the data stops being a toy.
Outside the heavy machinery, I've built plenty of the surface stuff people actually see and touch: scroll-driven landing pages, media-heavy galleries that don't choke on a slow connection, dashboards that turn a wall of numbers into something an operator can act on without scheduling a meeting about it.
Platforms have gotten good enough that "preview URL for every PR" or "auth in an afternoon" stopped being aspirational years ago. I lean toward boring, well-supported infrastructure — the kind where the interesting decisions happen in the application code, not in arguing with the deploy. When editors need to own content, I bias toward CMSes that give them a real studio without locking the developers out.
AI is part of how I work now — not a novelty bolted on, not something I'm cautious about. I use it the way I'd use a sharp pair of collaborators: to draft, to refactor, to argue against my own assumptions before I commit to a design. The judgment still has to come from a human who's done the work for years — but the gap between "I have an idea" and "I have a working prototype" is smaller than it's ever been, and I'd rather use that than pretend otherwise.
Two decades of shipping production code have shaped a broad, battle-tested toolkit. Here's the technology I reach for — from frontend frameworks and backend systems to databases, e-commerce platforms, and AI-powered workflows.
A corner for my personal, hobby projects — the ones I build for myself on nights and weekends, not for a client or a deadline. Sometimes I'd rather build the tool than go hunt for one: open-source, small on purpose, sharpened on my own daily workflow, and shipped only once they're genuinely useful.
Built sharp. Stays sharp.
A publishing engine you run yourself — the classic CMS model rebuilt server-first on Next.js 16 & React 19. No PHP, no tracking, with SEO and security baked into core, a typed plugin system, and a visual theme builder. One repo, one deploy, your data.
$ fs serve → https://<name>.test
A tiny, brew-based CLI that turns any folder into a real local site with browser-trusted HTTPS. Pick PHP, Node, or a zero-runtime static server per project, add MySQL on demand, and drive it all from a live terminal dashboard.
Calibre → static, encrypted, yours
A static-site generator that turns a Calibre e-book library into a private, password-protected reading room — AES-256 encrypted at rest, hostable on any static server, with an in-browser EPUB reader and a book-themed design that works down to mobile.
Have a project in mind or just want to say hello?
Drop me an email and I'll get back to you as soon as I can.
Best viewed in portrait mode