Unattended automation, built for the failure cases.
| gui-report-automation | Borrows a human-owned Chrome session on a Linux VM to produce a daily report |
| drive-whisper-transcriber | Batch transcription of Google Drive media with Whisper on a Compute Engine VM |
| durable-webhook | A webhook relay on Cloudflare Workers that accepts fast and delivers stubbornly |
| publish-guard | Finds what you forgot to remove before publishing a repository — git history included |
| flex-guard | Catches the LINE Flex messages that fail to send, and the ones that fail quietly |
The first two are sanitised editions of systems still running in production, published with the client's permission. The rest are my own work, unconnected to any client.
Most of my work is under contract and cannot be published — around 900 commits, 165 database migrations, a permission system, analytics, and multi-account isolation. The repositories above are what I can show.
Production — TypeScript · JavaScript · Python · Node.js · Cloudflare Workers (D1 / KV) · Google Workspace API
Ops — systemd · Google Compute Engine · Railway · Playwright · GitHub Actions
I design around how things fail — idempotency in state files, quarantine instead of delete, stop when the outcome is unknown, never automate authentication. The repositories above show what that looks like in practice.
Native Japanese speaker, based in Macau (UTC+8) — one hour behind JST, so working hours overlap almost entirely with Japan. Comfortable working in Japanese or English.
日本出身、マカオ在住。日本との時差は1時間で、日本時間での対応が可能です。