Skip to content

Writing

Notes from the work

What broke, what it cost to find, and what we changed so it could not happen the same way twice.

31 documents · press / to search

  1. 6 min read

    Why we build modular monoliths first, and when we actually split

    Microservices solve an organisational problem and charge you a distributed-systems bill for it. Here is how to get the modularity without the network, and the four specific signals that mean it is genuinely time to split.

    ArchitectureBackendNode.js

  2. 6 min read

    Interaction to Next Paint: what actually moves it, and what only looks like it does

    INP measures three things and most advice only addresses one of them. A breakdown of input delay, processing and presentation delay — with the fixes that move each, and the popular optimisations that move none.

    PerformanceCore Web VitalsINPFrontend

  3. 6 min read

    From commit to production: a CI/CD blueprint that stays fast as it grows

    The pipeline shape that keeps deploys boring — one build artefact promoted rather than rebuilt, gates ordered by how fast they fail, and a rollback that is a routing change rather than a redeploy.

    CI/CDDevOpsGitHub ActionsTesting

  4. 6 min read

    Hardening the deployment pipeline: supply chain, secrets, containers and the edge

    Where a pipeline is actually attacked, in order of likelihood — and the specific GitHub Actions and AWS controls that close each one, including the permission default almost every repository gets wrong.

    DevSecOpsSecurityGitHub ActionsAWS

  5. 6 min read

    Infrastructure as code in practice: structuring Terraform for a team that is growing

    The layout that survives a second environment and a third engineer — what belongs in a module and what does not, why state boundaries matter more than folder structure, and the review discipline that stops a plan being rubber-stamped.

    TerraformIaCAWSDevOps

  6. 5 min read

    React Native or Flutter: a decision framework, not a benchmark

    Both are fast enough for almost every product. The decision is made on hiring, native integration depth, UI fidelity and long-term maintenance — with a checklist for testing your own case in a week rather than trusting somebody else's numbers.

    MobileReact NativeFlutterArchitecture

Start here

Tell us what you are building

Or what is breaking, or what has to go faster. You will get a straight answer from an engineer who would do the work.