[engineering · life · the sky]
I write about building dependable systems, working alongside AI, protecting privacy, and the life beyond the screen that sharpens how I see and build.
[start here · then newest first]
Production systems sit beside the observations that sharpen how I think: family, travel, photography, reflection, and the night sky.
Three pieces that show the range: mobile architecture, working with agents, and life away from the editor.
How a Rust facade, UniFFI bindings, and platform packaging can give Android and iOS one domain core without duplicating behavior.
A practical reflection on local agents, memory, verification, and the handoffs that let the next run trust what happened.
We have become fluent in naming what hurts. But awareness can become another form of avoidance when it never turns into care, accountability, or action.
I’m not a web developer, but with Codex I turned a static portfolio into a working orbital interface—and spent more time shaping the product than wrestling with syntax.
We have become fluent in naming what hurts. But awareness can become another form of avoidance when it never turns into care, accountability, or action.
A reflection on the defenses we build from old wounds, pride, and habit—and why real change begins when we stop guarding what keeps us trapped.
Lessons from a compact backend: explicit API contracts, append-only location history, PostGIS semantics, guarded AI prose, and evidence-based verification.
A practical reflection on local agents, memory, verification, and the handoffs that let the next run trust what happened.
How I set up MemPalace as a practical tool for local agents: small taxonomy, verify-first retrieval, agent diaries, AAAK wake-up context, and why protocol matters more than storage.
How a Rust facade, UniFFI bindings, and platform packaging can give Android and iOS one domain core without duplicating behavior.
A practical framework for reading engineering growth through scope, decision quality, operational responsibility, and durable outcomes.
How I use two assessment profiles as prompts for better decisions and communication—without treating their scores as identity or proof of ability.
A practical quality loop for static personal sites: verify the publication boundary, exercise critical routes, and review desktop and mobile rendering.
How SQLite authoring, deterministic static generation, and a public-only build artifact create an editable blog without shipping a runtime database.
How agentic tools widened my engineering workflow without replacing mobile depth, explicit ownership, or evidence-based delivery.
A practical prompt structure for coding agents: live context, real constraints, side-effect boundaries, observable acceptance evidence, and reproducible handoffs.
Lessons from multi-agent engineering work: define output contracts, instrument repeated effort, match verification to risk, and preserve trustworthy handoffs.
Family holidays in Auckland, a compressed South Island road trip, and the surprise of catching the Aurora Australis.
A personal essay about designing focus blocks, protecting rest, and keeping philosophy close to the shipping calendar.
Three frames from one trip, one ongoing experiment: motion, moon detail, and mountain light across different gear and shooting constraints.
A practical way to divide shared domain behavior, state, packaging, and native UI responsibilities across Kotlin and Swift.
Short delivery records from client and product work. The same projects, with screenshots, are in the portfolio.
A public-safe account of my Android work across multichain rewards, transaction replacement, wallet migration, swaps, shared Rust, startup performance, and release reliability.
How I delivered ITVX Android player features at Candyspace across recommendations, timeline previews, phone and tablet motion, reliability, security, and XML parsing.
I led five senior Android engineers on MySTC, working in Kotlin and Java across account, ordering, support, and multilingual flows.
I worked on OCBC Business for Android in Kotlin and XML, covering chart UI, identity-verification integration, network behavior, and focused unit tests.
I worked on openpay's Android purchase flow, including spend-limit cards, merchant content, checkout state, and partner-dependent payment paths.
I worked in Solo's shared Kotlin and XML codebase, shipping Android features and production fixes used by multiple restaurant-branded apps.
I led delivery across OWTO's Android, iOS, and backend work and stayed hands-on with booking, GPS, payments, and the APIs connecting them.
I built and evaluated Android experiment variants for Popslide and worked on lockscreen behavior, notifications, caching, and production state handling.
I worked on WebSafety features across Java and Objective-C code, including GPS, synchronization, permissions, and platform behavior that wasn't always documented.
I contributed Kotlin feature and maintenance work to ProjectBASS, an open-source Android app for collecting volunteer network measurements.
No writing matches that subject yet.
[28 published entries · engineering, systems, and life]