Skip to content

How I Work

Transparent scope, safe change, and a named engineer. The process is the product.

Diagnosis before theatre

I will not quote a rewrite from a sales call. I will look at the repo, the lockfile, and how production actually runs. A code audit is the written version of that.

Engagement models

  • Fixed-scope when the edge is knowable.
  • Day or project blocks when it is not — typical at the start of a takeover.
  • Retainers once the app is supportable.
  • Audits when you need a decision artefact.

Safe change

Staging where it exists, backups that are real, and a rollback story. Production heroics are for incidents, not for “while I’m in there”.

You work with me

See the profile. If the work needs a team I do not have, I will say so rather than staff it with fiction.

Remote, UK hours, written record

Default is remote, UK working hours, pull requests you can still read if I am hit by a bus. Calls when they unblock something. Response expectations for retainers are written per engagement — not as a website SLA badge.