I build frontends that work for everyone.

How I work

• Accessibility is tested with the people it’s for.

  Twelve Disabled drivers and passengers tested Close to the Door over two rounds, and most of the best decisions in that codebase came from them.

• I give every page a performance budget.

  Slow pages cost the people on old phones and poor connections first. The budget covers size and speed, it is checked on every change, and a miss is fixed in the page rather than by raising the budget.

• Security is part of frontend work.

  I completed an MSc in Cyber Security with distinction in 2024. On the frontend that means a content security policy, dependencies checked for known vulnerabilities, and untrusted input cleaned before it reaches the page. When a penetration test of Close to the Door showed row-level security leaking data, I closed the database to clients, and every write now goes through an edge function that checks the token, rate-limits and validates.

• A change is mine until it is running in production.

  At Fruugo I deploy and monitor my own changes to production weekly. I introduced Vitest and Playwright there and put axe and IBM Equal Access checks into the pipeline, so a change is tested before it goes out and watched after it does.

• Leading a team means review, tests and teaching.

  At Aspect Digital I led a team of four and brought in code review standards, automated testing pipelines and mentoring for the junior developers. At Fruugo I started the company’s accessibility group and built its internal training tools.