Solo developer

What I build.

Alongside client work I build products around automation — taking the kinds of work that used to require a meeting, a ticket, and three handoffs, and collapsing them into something an AI agent can do end to end with a human in the loop only where it matters. Typhon — my AI agent — produces plans, opens pull requests, and ships features without leaving the dashboard.

I build my own tooling because the off-the-shelf pieces aren't shaped right yet. Orchestration, planning, approval flows — the things that turn a raw model into a teammate — are mostly still being invented. I'd rather invent them than wait.

How I got here.

I'm self-taught. In 2015 I built a practice app for the Slovak driving-theory exam and published it on Google Play. People used it, it earned money, and in 2016 it got me my first developer job — building a banking app from scratch alongside one senior developer.

Since then I've built mobile banking and telecom apps for Erste Group's George platform, ČSOB and T-Mobile, been the only Android developer on a tenant-experience app, and spent the last few years as one of two developers on a large consumer social platform: around 245 screens and hundreds of thousands of users. There I moved a legacy Java codebase to Kotlin and MVVM, built peer-to-peer video calling over WebRTC, and built a Rails pipeline that used Claude and ElevenLabs to voice each character in a written story.

Before any of that I trained as a mechatronics technician — mechanics, electronics and automation in one program. I still think about software the way that taught me to: as a machine whose parts should each do one thing, and be easy to take out.