Skip to content
BUILD FOUNDRY

Notes

Method, written down in enough detail to be checked.

We have one public case study, which is the honest position for a team this new. What we can publish instead is how we work and what we have got wrong — including a bug from this website’s own contact form, with the code.

What is in here

Checklists we actually run, methods described step by step, and defects from this repository with the before and after. No case studies dressed up as advice, and no claims about results we cannot show you.

  1. Engineering

    11 min read

    Signing S3 requests without the SDK

    Two operations did not justify the AWS SDK in a serverless bundle, so we signed them by hand. How SigV4 works, the four traps that cost the most time, and when the SDK is still the right answer.

    Read the note
  2. Engineering

    11 min read

    The contact form that quietly threw away every enquiry

    A bug from this codebase: a stub transport returned a failure value instead of throwing it, Promise.allSettled read the returned value as success, and the visitor got a reference number for an enquiry nobody received.

    Read the note
  3. Operations

    9 min read

    Taking over a codebase somebody else wrote

    What we read first and in what order, how to tell an understaffed system from a broken one, the severity-by-effort risk report, why stabilising comes before any change, and the four things that are almost always wrong.

    Read the note
  4. Audits

    11 min read

    What we actually check in a technical audit

    The full checklist behind the free audit: Core Web Vitals and what each one means when it is bad, security headers, which dependency advisories matter, accessibility with legal weight, deployment risk, and what breaks first under load.

    Read the note

Posted when there is something worth writing down rather than to a schedule. If one of these raises a question about your own system, the fastest way to get it answered is a free technical audit.

The audit checklist above is exactly what we work through when you send us a URL. It costs nothing, the assessment is written rather than exported from a tool, and there is no obligation to continue afterwards.