// Cloud & Security Engineer
I translate betweensystems and people.
Cloud & security infrastructure — made clear to everyone who has to trust it.
// The Difference
“Before I read logs, I read literature.”
I came to engineering through English Literature — and found a field full of brilliant systems almost nobody could explain.
I came to engineering through English Literature — years spent on how meaning travels, and how the right framing makes a hard idea suddenly obvious. Then I found cloud and security, and saw a quiet problem: brilliant systems almost nobody could explain.
That gap is where I live.
Turned away for the wrong background, I built a community and taught what I was learning. Now I architect and secure cloud systems — and translate between the people who build and the people who decide.
The transition wasn’t easy — rooms full of computer-science degrees and a head start I didn’t have. So while I was getting turned away for the wrong background, I built a community and taught what I was learning. We grew together, and I learned more than any classroom could teach.
Today I architect and secure cloud systems, document them so they outlast me, and translate between the people who build and the people who decide.
This site is the record of that, written as it happens.
// The road so far — swipe
// Field Notes
My first production system was not a tutorial.
Real infrastructure, real teams depending on it, real consequences. The lesson wasn’t any single service — it was that a system only survives if the people around it understand why it exists.
It was real infrastructure, with real teams depending on it and real consequences when something broke. For the first time, the stakes weren’t a grade — they were people trusting that what I built would hold.
What I took from it had little to do with any single service.
I learned that an architecture decision is also a communication decision — that the cleanest design fails if the team can’t understand why it exists. I learned that documentation is not paperwork; it’s whether a system survives the person who built it.
Maturity isn’t avoiding failure. It’s how fast and how honestly you recover from it.
// A system I worked in production
Build for the engineer who comes after you.
Document the reasoning, not just the commands.
An architecture decision is a communication decision.
// Projects
What I've Built
// swipe each row to explore
// AWS
2 projects
// Serverless
2 projects// Full Stack
1 project// Community
1 project// Challenge
2 projects// CREDENTIALS
AWS Certifications
// Speaking & Education
I teach what I had to learn the hard way.
Cloud, security, systems thinking, and the strange advantage of coming to tech from the humanities.
// In the room
// The Longer Game
I’m not building a career.
I’m building an ecosystem.
A job is something you have. An ecosystem is something you tend — so alongside the engineering, I’m building two things for the long run.
A job is something you have. An ecosystem is something you tend. I’m drawn to the second kind of work — the kind that compounds, that outlasts any single role, that leaves the people around me better at what they do.
So alongside the engineering, I’m building two things I intend to keep building for a long time.
Community
TribeSec
A cybersecurity community where people finding their way into security get mentorship, challenges, and somewhere to belong. It started because I needed that room and couldn't find it — so I built it.
The longer bet
Afriture
A space for African tech futures — technology, talent, and ideas grown on the continent and built to last. Quietly underway; more in time.
The infrastructure I care about most isn’t only in the cloud. It’s in people.
Let’s talk about the long game →// Tech Stack
Skills & Tools
// Proficiency
☁ Cloud
🏗 IaC & DevOps
💻 Frontend
🖥 Backend
🛠 Tools
Currently deepening: Kubernetes · AWS CDK · Python for Lambda