Skip to content
heaps goodstudio
Start something

The record

A few worked examples.

Representative, not name-dropped: the kind of problem the studio is built for, written up plainly. Drawn from the systems we build, not one client's engagement.

  1. Rebuilding a payments ledger no one wants to touch

    Payments

    How we take a brittle, mutate-in-place ledger and turn it into an append-only event log behind a type-safe Go service, migrated against live traffic, with no big-bang cutover.

    • Every balance derived from an immutable event log
    • A type-safe contract no other service can write a bad entry through
    • A live migration with no big-bang cutover

  2. One typed API contract, two teams that stop breaking each other

    API & Backend

    How we make a Protobuf + buf contract the single source of truth between a Go backend and a TypeScript frontend, so API drift becomes a compile error instead of a production incident.

    • End-to-end type safety from the Go server to the browser
    • API drift caught at compile time, not in production
    • Front and back end shipping on independent cadences