Skip to content

Work with me

The handbook is what a good default looks like on paper. Applying it to a real team, with its own history and constraints, is a separate piece of work — and one I take on. Background on why the handbook exists and who wrote it: About.

  • Practice reviews. A read of how a development team currently works — branching, review, testing, release, on-call — against the defaults in this handbook. Written up as a short report with the two or three changes worth making first.
  • Advisory engagements. Ongoing input on a specific bet: a platform migration, a rewrite, standing up a new team, tightening a release process. Usually a few hours a week.
  • Workshops. A working session with a team or engineering leadership on one topic from the handbook — code review, branching, testing strategy, cloud choices — tailored to where the team actually is.

Software teams and engineering leaders who want a second opinion from someone outside the org, and are willing to change something once they have one. Best fit is teams between five and fifty engineers.

  1. Send a short note describing the team, the problem, and what “better” would look like.
  2. A short call to confirm scope and check fit.
  3. A written proposal with deliverables, timeline, and cost.

Email: [email protected]. Issues on the repository also reach me.