Solution Architecture
One infrastructure plan for 14 departments
Designed a comprehensive infrastructure framework for a research institute impacting 14 departments, featuring flexible modules, unified data pipelines, and structured support strategies for long‑term adoption.
Designed a comprehensive infrastructure framework for a research institute across 14 departments — modular, with unified data pipelines and support strategies.
Led a GIS map application to 10x revenue growth
Led the software development of a GIS map application, driving revenue growth by 10x and positioning the product as a primary data asset.
Led development of a GIS map application that became a platform cornerstone, driving a 10x revenue increase via upsells and data licensing.
Overhauled internal processes, saving 8,000 hours
Overhauled internal processes, saving 8,000 hours by improving software architecture, systems, and scheduling efficiency.
Overhauled internal processes to save ~8,000 hours, improving software architecture, systems and scheduling efficiency.
Infrastructure simplified beyond AWS
Reworked an international client’s infrastructure by removing unused services, adjusting capacity and moving workloads away from AWS. The founder reports a 10x reduction in cloud costs with no loss of productivity.
Reviewed an international client’s infrastructure, removed unused services, adjusted capacity and moved workloads away from AWS.
A maritime platform with clear system boundaries
Architected a layered maritime platform separating a Next.js PWA frontend, a Go (Huma/Fiber) API, and a PostgreSQL function layer, keeping all business logic in the database.
Architected a layered maritime platform — Next.js PWA, a Go (Huma/Fiber) API and a PostgreSQL function layer holding all business logic.
Set the platform's founding technical decisions
Set the platform's founding decisions in the weeks after the repository opened in November 2025 — the layering, database‑first data access and the zero‑warnings bar — and they still hold nine months on.
Set the platform's founding decisions in November 2025 — the layering, database-first data access and the zero-warnings bar — and they still hold.
Built infrastructure that still runs years later
Planned and implemented new infrastructure functionality for internal and external systems, building solutions durable enough to still run years later with minimal change.
Planned and built infrastructure for internal and external systems durable enough to still run years later with minimal change.
Built the entire core infrastructure from scratch
As one of the first hires, designed and built the entire core infrastructure and supporting processes from scratch for a green‑energy SaaS startup, laying the foundation for rapid growth.
As one of the first hires, designed and built a green-energy SaaS startup's entire core infrastructure from scratch, enabling rapid growth.
Public services on a small server
Hosted the company’s public services on a single‑core 512 MB host — a git forge, a web server for seven domains, Tor, two alternative‑protocol servers and intrusion banning — treating 464 MB of usable memory as the design constraint; backup automation is a separate implementation.
The recorded public-service setup ran on a machine that cost less per month than a lunch, and the design is better for the discipline rather than merely…
Split every operational secret per host
Split the four per‑host operational secrets after establishing that two hosts sharing one dead‑man's switch alert less than two switches, not more, and that a shared backup passphrase can expose both hosts' backups, even in separate repositories, if someone obtains it and can read both repositories' encrypted data and key files.
Secrets are per host by construction, and the two failure modes that would have followed from sharing them are written down where the next person edits the…
Built a database‑driven CV generator
Built a database‑driven CV, references, portfolio and cover‑letter generator in Python — 41 modules, 10,580 lines — rendering six output formats from one 23‑table SQLite source assembled by a 19‑step idempotent pipeline.
Six formats, three languages and five themes come out of one database, and a corrected sentence is corrected once.
Built a native macOS client in Swift 6
Built a native macOS messaging client in Swift 6 and SwiftUI — 11,141 lines across 53 files — over the C interface of a Rust core linked as a static archive from a pinned revision.
A native client that starts as a Mac application, uses the platform's own materials and controls, and carries no embedded browser.
A bounded event pipeline for a macOS app
Bounded event buffers and logging after a recorded macOS incident with 41 MB per second growth and 111 GB of compressed pages on a 36 GB machine; a recorded full test run reduced core log lines from 610,996 to 1,411.
The incident record documents a full test-run comparison: core log lines fell from 610,996 to 1,411, and captured log size from 63 MB to 388 KB.
Adopted Swift 6 strict concurrency over C
Adopted Swift 6 complete strict concurrency with no actors, bridging a blocking C event loop to the main actor through one producer, one consumer and one ordering — after establishing that a task per event loses the ordering the interface depends on.
The application compiles under complete strict concurrency with no suppressions, and event ordering is a structural property rather than a hope.