Case studies and personal projects
Every case has a "why this way" section: out of several workable options one was chosen, with the reason and the price named.
Websites · SystemsThree websites, a client area and a freight accounting systemA storefront, a shipping calculator, a client area and the system that carries a shipment from order to invoice. Usually different teams build these. Here I worked on every part.SystemsA client area: purchases, shipments, payments and documents in one placeOne client area instead of emailing managers: see where the parcel is, pay, download a document. The same code serves two different services — the differences live in configuration.SystemsA freight accounting system: from the order to the client invoiceThe whole shipment passes through the system — orders, air and sea delivery, consolidation, tariffs, invoices, credit limits, agent commissions. Processes are described in configuration, so they change without a release.SystemsAn application for a new industry is assembled from configuration, not written againScreens, data, access rights and processes are described in configuration files. Launching a product for another industry does not mean copying and rewriting code.SystemsA lending platform at a large bankA large estate of thirty-odd repositories with strict security requirements and a rule that every change to data must be traceable — who made it and when.Websites · SystemsThis websiteBuilt by the rules I offer clients: it opens instantly, depends on no third-party services, and its copy and case studies are edited without a programmer.
Personal projects
Not case studies — things built for myself
kopim
A Telegram app for household budgets. Shared groups, split expenses, budgets by category, multiple currencies, fingerprint login, AI hints, a bot, history import. Designed, built, deployed and maintained alone. 16k lines of C# and 25k of TypeScript.
- .NET 10
- EF Core
- PostgreSQL with pgcrypto
- React 19
- Zustand
- Docker
- Sentry
My own infrastructure
The cluster my projects live on: applications are described as packages, deployed automatically from the repository, and secrets are stored encrypted next to the code. The value is direct: infrastructure I hand over can be maintained without me.
- Helm umbrella charts
- ArgoCD
- SOPS + age