Profile

By the numbers

• 6

  public projects

• 11

  languages across repos

• 3

  years on GitHub

• 2

  stars received

readme · in the developer's own words

• Backend & systems engineer. I build services that keep running long after everyone has gone home.
• Currently building: APIs, tooling and automation, written to be read, not just run.
• Levelling up: distributed systems, security and performance.
• Ask me about: Linux, Git, Docker, Python, TypeScript, Rust.
• Creed: clean architecture, small diffs, no undefined behaviour.

Interests

• Backend systems

  Services with clear boundaries that stay up and stay readable.

• APIs and services

  REST endpoints with typed contracts, documented and versioned.

• Automation

  Scheduled workflows and bots that remove toil and report when they fail.

• Linux and infrastructure

  Shells, containers, reverse proxies and the manifests that hold them.

• Reliability and performance

  Timeouts, retries, idempotency, and measuring before optimising.

• Security-minded engineering

  Credentials out of code, least privilege, scanning for leaks.

• Clean architecture

  Small diffs, boring solutions, decisions written down next to the code.

Method · how the work gets done

1. 01

   Read first

   Understand the system end to end before touching it. Most bugs are a misunderstanding wearing a stack trace.

2. 02

   Small diffs

   Change one thing, make it reviewable, ship it. Big rewrites hide big regressions.

3. 03

   Boring over clever

   Standard library before dependency, platform before framework. Clever is what someone decodes at 3am.

4. 04

   Keep it running

   Timeouts, retries, logs that say what happened, and an error channel that reaches a human.