I'm bl4ckmeow — building ground-segment software at GISTDA by day, running an infra-network studio after hours, and shipping product with friends on weekends.
Different stakes, different runtimes — same engineer. If your project sits between any two of these worlds, that's usually where I'm most useful.
I write code that runs from kernel-adjacent network rules to the labels on a Leaflet map. The thread is the same: build the boring layers well so the interesting parts can move fast.
I've been doing this for ~6 years across government, agency, and independent work. Heavy on PostgreSQL, Go, and TypeScript — but the stack follows the problem, not the other way around.
Currently engineering across three different surfaces — government, infra studio, and product work. Different timelines, different stakes, same craft.
Building ground-segment software for Earth-observation missions: geospatial pipelines (PostGIS, GDAL), internal analyst tools, and public-facing portals. Lead web platform initiatives end-to-end — API contract, UI, deployment.
Co-running an infra-network engineering studio. Network design, firewall & routing (pfSense, MikroTik, Fortigate), site-to-site VPN, observability stacks (Prometheus, Grafana, Zabbix). Also build the studio web & client portals.
Small team taking custom software projects for SMEs — web, mobile, integrations. Mostly TypeScript / Next.js / NestJS / Postgres. We act as the engineering team for clients who don't have one.
Built web platforms across e-commerce, content, and internal tools. Picked up the habit of owning the whole stack — design implementation, API, infra, runbook.
Mix of government, studio, and personal projects. Some are internal — ask if you'd like a walkthrough.
End-to-end web for tasking & tracking Earth-observation missions. PostGIS-backed scheduling, near-real-time tiles, role-based ops UI.
Self-hosted control plane for managing site-to-site VPNs across SMB clients. pfSense data plane, custom Go controller, web admin.
All-in-one POS for a small TH chain — table mgmt, kitchen display, payments, inventory. Designed for the night shift, not the demo reel.
Small Go CLI for batch geospatial ops — reproject, tile, COG-convert. Replaced a 200-line bash script no one wanted to touch.
Tooling I reach for daily. Heavy on Postgres & Go, but I'll pick whatever fits the problem — including plain HTML and a cron job.
Occasional posts on infra, geospatial, and small-team engineering. Slow to publish, but each piece is something I'd actually want to read.
All postsOpen to consulting on geospatial systems, infra-network projects, and full-stack product work. The weirder the requirements, the better.