Skip to content

Writing. How we think about the work.

Short pieces on the parts of a build that go wrong most often, and what we do about them.

Articles

  • Why we write the spec before the code

    Misunderstandings are cheapest to find on paper. Why every engagement starts with a written technical spec, and why it stays yours either way.

  • What you get every Friday

    A link you can open, not a status report. What arrives at the end of every week of a build, what stands behind it, and what we do when one slips.

  • Leaving us is part of the plan

    Every engagement ends. How we plan for that from the first day, so the code, the accounts and the knowledge are already yours when it does.