The First World

A grey box. A cartridge slotted in with both hands. The screen filled with Yoshi's Island — floating platforms, pastel sky, a small green creature that moved when I moved.

The machine conjured a world from a shell of plastic and silicon. I did not know how. That question would wait years to find its answer.

What I knew: pressing a button made something happen. Learning the rules let you go further. The world rewarded attention. I stayed until the television went dark.

The spell was cast then. The forest would come later — this was the first glimpse of what lay on the other side of a screen.

First Incantations

It started with a game — one seen online, and the question of how became the only question. Looked at the source. Found PHP. Found MySQL. Found that the forest had an entrance.

Spent the years that followed building for communities: clan sites, match records, member pages, gatherings that existed mostly online. The browser game never shipped. The craft grew without ceremony. The internet was already a forest then — I just didn't have a name for it yet.

Developer & Sysadmin

The client: a photography company that sent crews into nightclubs and needed somewhere to hold the pictures. Built the platform from scratch — community layer, upload pipeline, the servers underneath. No team. No runbook. No one to hand it off to when something broke.

Things broke. Servers went dark, ran out of resources, came back slowly. No escalation path — just the logs and whatever could be figured out from them. Each failure answered a question the coursework had never asked. The craft grew fastest where the theory ran out.

Computer Science Student

Studied networks, security, and economics. Between lectures, held the lantern for others — programming courses, databases, the first rites of writing code and shaping data.

One practicum stood apart from the coursework: cables first, protocols next, routing tables last. Every layer opened and studied from the inside — from the question a switch asks the room to the treaties that hold the internet's paths together. Built it all by hand. The kind of work that leaves a mark.

The thesis came last: what can the browser seal before the wire carries it? Written inside a sentinel institute that builds its own defences.

Incident Responder

Stood watch while the forest burned. When the signal came — attacker in the network, lateral movement confirmed, kill chain mid-flight — the work began: trace the intrusion path, contain the breach, cut the next stage before it landed. The fire usually started with a letter.

The network was shared — the CISOs were not. When incidents ran, a dozen of them needed briefing: fast, clear, translated from technical to consequential. Learned to hold both conversations at once: the logs and the briefing room.

Read packet captures like scripture, correlated logs across a dozen systems, checked what the sentinels on every endpoint had witnessed. Wrote post-mortems that asked the uncomfortable questions. Learned the adversary's grammar. Moved faster for it.

DevOps Engineer · Security Tooling

It started with automation. Small incantations to speed up incident handling. Nobody assigns what comes next — it accretes. The scripts became tools, the tools became platforms, and the platforms needed someone to hold them together.

Ended up steering development across incident response, threat intelligence, and forensics teams. Three disciplines, one platform layer beneath them all. Kept the pipelines honest, the integrations wired, the automations from quietly unravelling.

A different kind of on-call — the kind where teams depend on what you built. No attacker in the network this time. Just a broken deploy and a dozen analysts waiting.

Engineering Manager

The ward was new — assembled from scattered parts of the order, gathered under one root for the first time.

Two missions ran in parallel: web applications that other teams depend on for internal workflows, and platforms the whole organisation uses for cybersecurity processes.

First we rebuilt the ground beneath it all — infrastructure raised from scratch, segmented, sealed with proper authentication, and kept clean by the same automation it was built to serve.

Alongside it, we tended the chronicle — a SIEM of considerable weight: a hall of iron at a single centre, listeners at every edge of the forest, a petabyte of logs that never forgets — a platform we had taken from the order's general keepers to run ourselves, for tighter control and changes that didn't wait.

Then we turned to the SOAR stack — automations written before the craft arrived — and rewrote them: freed from a single vendor's hold, better structured, closer to something that lasts.