Stack · Web
React.js — how I build web interfaces
Core toolReact.js
React is where most of my web work happens, and has been since 2017. Everything from marketing pages to dashboards dense enough that render cost stops being an abstract concern.
Why I use it
The thing React got right is that a UI is a function of state, and the hard part of front-end work is deciding what the state actually is. Most of the bugs I've chased in other people's React code weren't render bugs — they were the same piece of truth stored in three places, drifting apart. So the work is mostly drawing component boundaries where the data already has seams, and keeping state as close to where it's used as it will go.
What I've built with it
- Client dashboards with tables and filters large enough that memoisation and list virtualisation were load-bearing, not premature
- Design-system components with accessibility built in from the start — roles, labels and keyboard behaviour, rather than bolted on after a review
- A carousel library contribution (react-multi-carousel) where SSR correctness and a 2kb budget shaped every decision
- Server Components in Next.js, which changed where I put data fetching more than any React release since hooks
Alongside
Rest of the stack
Got a project that needs React.js?
Get in touch →