How I got here.

Sysadmin, then cybersecurity, then frontend, then backend, now agentic engineer.

The compression of that sentence is dishonest about ten years of work. The expansion takes more space than this post will. What follows is the shape.

Compounding

Each chapter compounded into the next, and the compounding is the point.

The sysadmin years. Treating production like production. Backups that are not backups until restored. Logs that mean nothing if no one is reading them. The infrastructure habits that nobody teaches in school.

The cybersecurity years. Thinking adversarially about every system I touch. Not as a posture for an audit; as the default frame. Every API, every form input, every trust boundary, every assumption. Outputs from these years: bug-bounty research, vulnerability-discovery tooling.

The frontend years. Learning what users actually see and click. The discipline of accessibility. The realisation that backend correctness without frontend coherence ships nothing.

The backend years. Database modelling, API design, the operational properties of long-running services. Payment gateway prototypes. The years where infrastructure intuition met code.

Now: agentic engineer. Driving Claude Code and Codex as primary collaborators on a production hosting business. The bet is that the prior four chapters fortify me against the failure modes of the fifth.

The through-line

Ship something real. Operate it under load. Learn from where it breaks.

I am not done.

— Hisham