I build products that keep working when the internet doesn't.

Small grocery shops lose sales every time the internet drops — and in their neighbourhoods, it drops often.

An offline-first desktop app in Electron.js and React that keeps checkout running with no connection and syncs automatically when it returns — plus the NestJS/PostgreSQL backend behind it and the Linux server it runs on. I built the product on my own, end to end.

Reached 8+ paying businesses, 19,000+ transactions a month and a 30,000+ product catalog.

Teams needed to edit thousands of ERP records without ever leaving the table — and every department wanted different columns.

A fully dynamic editable grid: row virtualization for thousands of rows, inline editing with rich field types (select, datepicker, rating, emoji), columns added, hidden or removed at runtime, and auto-save. Plus the modular architecture of the ERP frontend around it.

Adopted as a core building block across the ERP. Led a 5-person frontend team.

The hours-of-service log is the main screen of an ELD system — a US truck driver’s 24-hour day drawn as a connected step line across four duty statuses, with violations, breaks and running totals on top. It carries legal weight, so it has to be exact. Recharts and Chart.js could not support the interaction the design called for: hovering a segment had to highlight that exact time range, place tooltips on both of its edges, and update the duty-hour total below.

A framework-agnostic TypeScript class that generates the entire SVG itself. It takes the API data, a timezone and a hover callback, then does the rest: mapping time to coordinates, connecting status segments, placing labels so they never collide, and rendering. Building it in React would have cost performance and control, so it deliberately depends on nothing. I also built the admin and superadmin panels, fleet-monitoring dashboards fed by in-truck IOSiX devices, a Gemini-powered assistant that explains engine error codes to dispatchers, and a maintenance scheduler.

The Flutter mobile team tried to draw the same chart natively, could not implement the full design, and ended up loading mine in a WebView — it is still running in production, on the screen every driver and dispatcher opens daily.

I learned English words in a notebook and forgot them — I could recite a list in order, but shuffle it and I was lost. Paper flashcards fixed the order problem and let me study anywhere, but created a worse one: the words I already knew kept coming back as often as the ones I did not, and once the stack grew, scheduling them by hand became impossible.

A scheduler that measures a word’s position in repetitions, not in calendar days. Each finished batch raises the learner’s counter by one; answering “I know this” pushes a word three repetitions further out, “I don’t” pulls it three closer, and every word whose counter falls behind the learner’s comes back. Because nothing is tied to a date, the whole timezone problem disappears — a person studying at 3 a.m. across a date boundary gets exactly the right words. Around it: US pronunciation audio cached on the server and fetched only when missing, a curated 4,000+ word dataset with images and example sentences, shared decks so learners never re-type words someone has already added, and a leaderboard with progress nudges to keep people coming back. It runs as a Telegram bot and a web app.

It is public and running, with no marketing behind it — I built it for my own problem and left it open in case someone else had the same one. The first scheduler is deliberately simple, and I now know where it falls short, so I am rebuilding it on NestJS and PostgreSQL with a stronger model and a Telegram Mini App sharing a single frontend codebase with the web version.

Tickets sell out, then quietly reappear — someone cancels, or the railway adds a wagon. Almost nobody is watching at that moment. This bot watches, and tells you instantly. 1,700+ people use it, and the number keeps growing on its own.