$ whoami
Lead Developer · platform engineering × AI-native architecture · real-time UIs · calisthenics as the lens
This is a knowledge garden, not a blog. Notes start as seeds 🌱, grow 🌿 and, with enough tending, become evergreen 🌳 — all linked, the way I actually think.
Case study — raising coverage with network-level mocks instead of brittle ones, shipping features test-first, speeding up quality checks, and getting Playwright adopted across several teams.
The simplest form of "real-time" — ask the server every N seconds. Wasteful at scale, perfectly fine more often than people admit, and the baseline every other technique is compared against.
Put a layer between external APIs and your UI that parses raw responses into your own domain models, so a backend change touches one adapter instead of forty components.
A one-page, version-controlled record of a significant decision. Context, decision, consequences. Never edited after acceptance, only superseded, so the history of "why" survives.
The friendliest of the big statics — tuck to full back lever, with the shoulder extension prep that makes it safe. Full back lever unlocked in 2026; pullouts are next.
A handstand is a feedback loop with a sensor, a delay and an actuator. So are autoscalers, rate limiters and a real-time UI under load — and they fail the same way.
Golden paths, internal developer platforms, delivery metrics, and what changes when AI agents become users of the platform too.
32 notes🌳 1🌿 27🌱 4
Interfaces that stay smooth under a firehose. Streaming transports, 60fps rendering, state that doesn't thrash, and connections that heal themselves.
13 notes🌳 2🌿 10🌱 1
Component architecture, React patterns, security and testing strategies that give teams confidence rather than ceremony.
28 notes🌳 7🌿 20🌱 1
Failure, consistency, consensus and delivery guarantees. The fundamentals underneath every platform and real-time system, written down so I actually understand them.
22 notes🌳 5🌿 13🌱 4
Second brains, spaced repetition and the daily loop that turns scattered notes into knowledge I can actually use. This site is its visible end.
17 notes🌳 2🌿 12🌱 3
A calisthenics skills library, training principles, and the engineering lessons hiding inside them.
28 notes🌿 19🌱 9
Leading UI teams, running communities of practice, communicating with stakeholders, and the habits that make a team better at its craft over time.
24 notes🌳 2🌿 20🌱 2
Case study — raising coverage with network-level mocks instead of brittle ones, shipping features test-first, speeding up quality checks, and getting Playwright adopted across several teams.
Case study — designing and shipping a React network-graph library for several teams, and why rendering tech, API shape and Storybook mattered most.
Case study — leading the UI of a low-code network automation platform where workflows are drawn as BPMN diagrams. Model-driven editing, server-side permissions and a catalogue of reusable building blocks.
$ nowOct 2026
Life. I became a dad this year, and it has changed what I learn and how. Time comes in smaller, less predictable blocks, so I'm ruthless about fewer, sharper priorities, short focused sessions over long ones, and systems that let me pick a thread back up after a broken night.
Work. Leading front-end development at a fintech building real-time crypto trading interfaces. Most of my thinking goes into keeping fast-moving UIs smooth and predictable: decoupling rendering from the data feed, holding 60fps under a firehose of updates, and making click-to-trade flows feel instant without cutting corners on quality.
Thinking about. Platform engineering for an AI-native world. What a golden path looks like when coding agents walk it alongside people; how evals, tracing and sandboxes become platform capabilities rather than afterthoughts; and how to design platforms that both people and agents can trust.
$ radar
24 items · 11 adopt · 3 trial · 7 assess · 3 hold
My tech radar →$ ./lab --train
A library of 42 calisthenics skill families: 131 progressions unlocked, 18 current goals — and the engineering lessons hiding in progressive overload, deloads and balance.
Open the skills library →