$ whoami
Software Engineer · 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: a Node.js tool I built at Elanco in 2020 to move whole sites from Contentful to Kentico Kontent: export to disk, a work queue, batched streaming, adapter layers and resumable runs. It became open-source tooling and a guest post on Kontent's blog.
Twenty-odd books across code, platforms, teams, trading and science fiction turn out to make the same five arguments. Here's the thread that connects them.
Case study: on my industrial placement at Elanco, and then remotely through my final year, I set web standards, built a self-service web accelerator, shared components across 80 sites, consolidated them into 3, then led the CMS migration through delivery.
A cloud platform translates what developers declare into what the cloud provides, by composition, lookup or model transformation, and keeps it true through an observe → analyse → act loop.
Four years and 168 commits of dotfiles: GNU Stow mirroring $HOME, a Linux-to-macOS migration, a graveyard of Neovim configs, scripts that encode my workflow, and keyboard firmware as config too.
Kent Beck's 3X model for how products grow (cheap experiments, then removing obstacles to growth, then harvesting what worked) and why platforms fail when they rush or skip a phase.
Golden paths, internal developer platforms, delivery metrics, and what changes when AI agents become users of the platform too.
46 notes🌳 1🌿 36🌱 9
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.
33 notes🌳 7🌿 24🌱 2
Failure, consistency, consensus and delivery guarantees. The fundamentals underneath every platform and real-time system, written down so I actually understand them.
26 notes🌳 5🌿 15🌱 6
Second brains, spaced repetition and the daily loop that turns scattered notes into knowledge I can actually use. This site is its visible end.
21 notes🌳 2🌿 16🌱 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.
31 notes🌳 2🌿 25🌱 4
Case study: a Node.js tool I built at Elanco in 2020 to move whole sites from Contentful to Kentico Kontent: export to disk, a work queue, batched streaming, adapter layers and resumable runs. It became open-source tooling and a guest post on Kontent's blog.
Case study: on my industrial placement at Elanco, and then remotely through my final year, I set web standards, built a self-service web accelerator, shared components across 80 sites, consolidated them into 3, then led the CMS migration through delivery.
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.
$ nowOct 2026
Life. I became a dad this year, and it has changed how I spend my time. With an office five days a week, close to two hours' commute each way and longer hours, time comes in smaller blocks. So I get up early, keep the priority goals few and get things done effectively. I still train six days a week, and weekends are for my family.
Work. Owning front-end development as a software engineer 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 →