Skip to content

How we work

The habits behind everything we build. None of it is clever. All of it is on purpose.

What we hold to

Eight things that decide how the work gets done, whatever the work is.

  • Build new, replace old

    We would rather build the right thing than keep patching the wrong one. When something you inherited is holding you back, we replace it, and keep it talking to what you already run until the switch is made.

  • More is less

    Every extra part is one more thing that breaks while you sleep. We do the boring work up front, the checks, the tests, the previews, so there's less of everything later. Fewer surprises, fewer fixes, fewer late nights.

  • Boring on purpose

    Ordinary tools, few moving parts, nothing clever that only we understand. Clever is what the next developer refuses to touch.

  • Names, not documents

    Code should explain itself. If something needs a paragraph to say what it does, it gets a better name instead. Documents rot on their own schedule. A good name doesn't.

  • Every change carries its reason

    Anyone can follow what changed and why, years later. That includes you, and it includes whoever comes after us.

  • Yours from day one

    Repositories, servers and accounts are created in your name, not moved over at the end. If we stop tomorrow, nothing stops with you.

  • Slower than the fastest

    Somebody will always quote you three days. We'd rather take the week than be the reason you hire a second developer to redo it.

  • Honest about fit

    If a job is wrong for us, that's the first thing you hear, not the last. We'd rather lose the work than disappoint you with it.

How we work with you

The six habits that keep a job moving, on your side and ours.

  • One person decides

    We'll talk anything through, and we're happy to be overruled. Somebody just has to make the call.

  • Access on day one

    Waiting for a login is the most common way a week disappears.

  • Changes go through the same door

    If somebody edits the running system by hand, the next release overwrites it and an evening goes with it.

  • Fix the cause, not the symptom

    When something breaks twice, we fix why it breaks, rather than cleaning up after it a third time.

  • Tell us early

    A surprise in week one is a conversation. The same surprise in week six is a rebuild.

  • You see it before your players do

    A link you can click whenever there's something to look at. No guessing what happened this week.

That's the method

If it sounds like how you'd want it done, tell us what you run and what you need.