Skip to content

Services

Make the React frontend easier to change

I build first versions, fix brittle UI, and finish the product work already sitting on the roadmap. Some teams bring me in at the start, others halfway through. I work mainly with React and TypeScript. I also audit and repair Vue frontends.

  • There is nothing built yet and the first version has to be right
  • The backend exists, but the frontend and key product flows are still incomplete
  • Screens keep re-rendering because state, effects, and context are doing too much
  • Tables, filters, and modals keep getting rebuilt because the shared UI is difficult to use
  • The team is discussing a rewrite because nobody trusts what the current frontend will break next

Frontend audit

1 to 2 weeks

The product works. Every change just costs too much context, caution, or repeated work. I trace the real code and the critical flows, then separate measured problems from preferences.

What it covers

  • Architecture and ownership
  • State and data flow
  • Shared UI and design system
  • Critical-flow performance
  • Migration risk
See what the audit coversThe LockeBio router migration

AI coding standards

1 to 2 weeks, then sessions

Your team ships more code than it can review, and the codebase starts holding several answers to the same question. I document review rules, code boundaries, and checks the team can use.

What it covers

  • What gets reviewed, and how
  • Conventions the tools can follow
  • Boundaries and blast radius
  • Verification that means something
  • Shared review and coding rules
See what the standards work covers

Frontend architecture

Ongoing

Shared code that stopped being shared, or a product about to become two products. I draw the boundaries so repeated mechanics live in one place and product rules stay where they belong.

What it covers

  • Shared component libraries
  • Monorepo and workspace boundaries
  • Forms, tables, and repeated screens
  • Staged migrations
  • Conventions the team can use in daily work
See how I approach architectureShared React components need migration boundaries

Where I have the most context

Healthcare

EMR product UI, clinical forms, patient intake, provider dashboards, and privacy-aware interfaces at LockeBio and St. Michael’s Hospital.

See the healthcare work

Fintech

Investor dashboards, investment forms, transaction states, and tax filing screens at Reitium and Intuit / TurboTax.

See the fintech work

How we can start

Start with a focused frontend project. If ongoing support makes sense after that, we can continue.

What has become harder to change?

Send me the context and I will tell you if I can help, and if I cannot, who or what would.