About
Crew operations by trade, software by practice.
This page holds what a CV cannot: the projects themselves, what they looked like, and how they went.
Heston Airlines: automating crew operations
Crew ground transfers at Heston were arranged by hand: an Excel file, updated every day. I pitched an Automatic Transfer Tool to management, with a prototype I designed in Figma.
I wrote the full specification: a step-by-step plan of how the tool should work, what values it takes in, what it calculates and when, and what it sends out. Everything except the code. The project was approved, then cancelled in a round of cost cuts before anything was built.
There was more automation work besides the Transfer Tool.
The rostering system, NAVBLUE N-Ops & Crew, could not produce combined season-long reports on its own. Someone had to compile them by hand, every day.
I built Excel pipelines that pulled the N-OC data together automatically. They replaced that daily compilation and ran for the whole season.
I built a shift-based salary checker that reproduced the payslip calculation line by line.
I also wrote a technical specification for a second tool, the Automatic Shiftlog, and handed it to IT.
Everything else ran on the airline's internal systems, so you will have to take my word for that part. Airline data is not mine to share.
Crewcast: crew-demand estimation for charter operators
A B2B tool for ACMI and charter operators. It works out how much crew a flight schedule needs under EASA FTL rules, so a question that currently takes crew planning several days can be answered quickly enough to inform a bid.
Crewcast is still on paper: the engine design and the V1 scope are defined. Writing the code is the next step.
Self-hosted infrastructure
Proxmox on Hetzner, Docker, GitLab CI/CD, Tailscale, Caddy. Everything I ship runs on machines I administer myself, which means I am also the one who keeps them running.
Arinstata: a marketing site for a roofing company
A paying client in Lithuania. The site is bilingual, Lithuanian and English. It works, but the public domain still points at the old site.
I built the site, frontend and backend, and wired up the integrations with Meta Ads and Google Analytics. I handled part of the deployment. The design came from someone else.
Next.js, Payload CMS, PostgreSQL, Tailwind CSS, LT/EN internationalization.
How I build
Self-taught since 2020. PHP, C++, TypeScript and Vue, writing game servers, web apps and payment integrations by hand. Since 2025 I work AI-first: I direct the coding tools, and the spec, the architecture and the review stay mine. I read everything before it ships. The tools write most of the code. The decisions are mine.