Hey — I'm Kieran. I design and harden pragmatic systems.

Edge agents, safe upgrade paths, sub-second payment flows, and release toolchains that make shipping calm. Clear constraints in; verifiable results out.

How I work

• Start with constraints and outcomes: agree the target, budget, and latency/error budgets up front.
• Design explicit data flows and boundaries; favor boring tech and narrow surfaces.
• Ship thin slices to production, observe, then harden based on real usage.
• Make constrained runtimes work (Workers/ESM); solve crypto primitives pragmatically with compatibility.
• Fast-fail: bounded timeouts, latency-ranked selection, retries that users don't pay for.
• Reproducible environments: local forks, wallet stubs, deterministic CI; logs and coverage in PRs.

Origin

Left home at 16. Finished a four-year skilled trade apprenticeship in three. Pivoted into software after seven years with daily ships, ruthless focus, and a notebook full of experiments. That stretch felt like a “lonely chapter” — outgrowing old circles before finding new peers. The habit that stuck: earn results first, narrate later.

The trade mindset carried over: respect constraints, reduce waste, ship increments, observe reality, then harden. It still anchors how I approach uncertain domains (AI context shaping, cryptographic infra, upgrade safety).

Highlights

• Maintainer of a flagship Web3 payment portal.
• Built and maintained RPC infrastructure (RPC Handler NPM pkg) used across apps.
• Developer relations: onboarding (100+ devs), documentation, and tooling leadership.
• Progression: ~12 months contributing in OSS → joined the team → reached skilled-trade salary parity within three months.

I stepped back from grind-mode to rebuild curiosity. The work is better when it starts from play and lands as calm reliability.