5.5+ years of it, mostly on the half nobody photographs — the APIs, queues and schemas that decide whether a product survives its first real spike.
make the rail crop the second card
Done — 24px, and it holds at 960 too.
Editing WorkRail.tsx
The work keeps coming back to the same three. Each one makes the other two easier.
Whole features, not slices. A ticket through to a reviewable PR, then owned through the bug reports.
Eight products live, three teams, six sectors. Small numbers, but every one of them shipped and still standing.
Read the full profileNot a wishlist. This is what is running on my machine most days, and what I would reach for on a new project tomorrow.
Contest engines under broadcast load, wellness apps, onboarding flows, a solar calculator. Different domains, same problem shapes.
Decoupled architecture for enterprise reliability
A2Handled high concurrency at scale
A3Shipped full MVP with AI integrations
A4Streamlined document approval cycles
A5Reduced manual ops for sales teams
A6Low-latency real-time messaging
A7End-to-end booking and event workflow
A8Dynamic pricing logic for installers