I make pixels
move at the speed
of the market.
12+ years turning high-frequency chaos into sub-100ms calm — across trading floors, digital banks, and design systems.
A “20–25× faster” claim
you can actually run.
On a CPU-heavy charting workload at Grasshopper, I cut render time by 20–25× — Web Worker offloading, OnPush change detection, lazy module boundaries, all locked in as CI performance budgets. Here’s what that feels like. Hit the button.
Same data, same device. The only thing that changed is the engineering. Click below to feel the difference.
A career, shipped
as releases.
Every role was a deploy to production. Reverse-chronological, like a good changelog — newest on top.
The instrument panel.
Deep where it counts — frameworks, rendering internals, and the performance toolchain that makes the needle move.
I don’t just list frameworks.
I write them.
The price tape below is live — a random-walk ticker running in this page, hand-written in vanilla JS. The tabs show the same widget the way each framework actually wants it written: state, lifecycle, cleanup. Same logic, five dialects.
Proof, not promises.
problem? Let’s talk.