Not a generalist who dabbles. A specialist who won't stop.
I started in network closets and ended up teaching SOC analysts how to defend production environments. The throughline: I find systems I don't understand, I take them apart, and I build them back better. Then I write down what I learned so the next person doesn't have to relearn it.
Today I run a small studio that pairs security engineering with product engineering. Same operator hardens your stack, ships your site, and trains your team. No handoffs, no diluted accountability.
From wiring closets to SOC dashboards to shipping curriculum.
The arc, year by year. No filler. Each step taught me something I still use.
Train operators, not certificate-collectors.
Most cyber courses teach you to pass exams. Mine train you to walk into a SOC at 03:00 and triage an alert. Lab-heavy. Scenario-driven. Honest about how messy real production is.
- Security without product context is theatre.
- You learn faster by writing it up than by watching it.
- Every "hacker" is mostly a careful reader.
- Ship under pressure. Reflect with a calm mind.
Where I'm sharp.
Self-rated. Calibrated by shipped projects, not certificate count.
Certs & training.
Selective. I take certs that change how I work, not ones that decorate a LinkedIn.
The cybersecurity path I'd retake if I started today.
If you're starting out, this is the order I'd march in. It's also how my curriculum is structured.
Foundations
- Networking, TCP/IP
- Linux & shell scripting
- Python for sec
- OWASP Top 10
Defensive
- SIEM (Splunk, Wazuh)
- EDR (CrowdStrike)
- Detection engineering
- Threat hunting
Offensive
- Recon & enumeration
- Web app pentesting
- Privilege escalation
- Active Directory
Specialist
- Cloud security (AWS/GCP)
- Malware analysis
- Incident response
- Threat intelligence
Ready to level up your security & brand?
30-minute free strategy session. We'll audit your stack, identify the biggest leverage points, and map a 90-day roadmap.