I design while I build
Figma is useful when we need to look at the same thing. After that I'm in the code. Spacing, error states, loading, how a form feels between steps.
Available for frontend work
I build fast, considered interfaces for the web.
I'm Luke Webster-Khan, a frontend developer with five years shipping production React, Next.js and TypeScript — most recently a storefront for Pearce's Hardware.
Intro
About
Currently @ Citation Group·Bristol, UK
I'm Luke, a frontend developer. I started out on custom WordPress sites and moved into React. Five years of e-commerce, customer portals, data visualisation and marketing sites.
Day to day I use Next.js, Tailwind and SCSS modules. I like GraphQL, and anything that gets a page out of the way faster. I write tests before I merge, and review is part of the job.
- 5 years
- Shipping production React
- 4 teams
- WordPress agency → React dev
- AWS CP
- Cloud Practitioner, Jun 2024
- Bristol, UK
- Remote-first
Work
I'm leading the frontend on a multi-step form for sensitive data. React and TypeScript, SCSS modules and Tailwind, from Figma through to review and tests.
- React
- TypeScript
- Tailwind
- SCSS
Day to day
How I work
Small pull requests
Big PRs are a pain to review. I keep changes small, write tests before I merge, and try to explain what I was thinking so the next person isn't guessing.
Quick, and usable
Images, bundle size, how fast a page feels. Keyboard use and screen readers too. Easy to leave for later, and obvious when you have.
Not just the frontend
A lot of bugs aren't in the component. I look at the console and the network tab: CORS, CSP, a request that didn't come back. Images in S3, something stuck in a CloudFront cache, that kind of thing too.
Selected work