Skip to content
Revoech
··/··

all work

Each entry below is a long-form technical write-up of a real project. The emphasis is on what I would do differently, not on presenting the outcome as a success story. Names of third-party systems and libraries are accurate; internal tooling names have been generalised.

  1. 01
    Fixing a race condition in the grant approval workflow

    Q4 2024 · 10 minutes

    Two admins approving the same grant within milliseconds of each other triggered two divestment flows. The ticket was about to be closed as unreproducible. A concurrency script changed that.

  2. 02
    Batching GraphQL resolvers with DataLoader

    Q1 2025 · 9 minutes

    A portfolio holdings endpoint was making one database query per position. On a realistic dataset that was over 200 sequential round-trips per request. The fix was a DataLoader and a lesson about where N+1 hides.

  3. 03
    Zero-downtime index on a high-write transactions table

    Q2 2025 · 7 minutes

    An admin report endpoint was taking three seconds on large accounts. EXPLAIN ANALYZE pointed to a missing composite index. The fix took an afternoon. The lesson about column ordering took longer.

  4. 04
    Cutting replication lag on a Postgres read fleet

    Q2–Q3 2025 · 14 minutes

    A multi-week investigation turned a recurring multi-second tail into a steady sub-second one. The fix that mattered was not the one I had planned to ship.

  5. 05
    Multi-tenant data isolation in a shared PostgreSQL schema

    2024 · 8 minutes

    FlowBoard is a project management SaaS where multiple organizations share one database. The hard problem was not the Kanban boards or the real-time updates. It was making sure a query for one organization could never accidentally return data from another.

  6. 06
    Designing a university community platform

    2024–2025 · 6 minutes

    UniPal is a full-stack platform built as a final year project. The engineering challenge was designing a MongoDB schema for three distinct features that share users but have different data shapes, and making them feel like one coherent product.

  7. 07
    Weather-risk routing for long-haul freight

    2025 · 9 minutes

    An internal routing tool for a logistics client. The hard part was not finding routes -- it was sampling weather at the right time. A checkpoint 400 miles out needs tomorrow's forecast, not today's.