Where it started
I was interested in systems because I wanted to know how they broke.
As a kid, I took apart the family computer, learned Windows when the internet was off, wrote small batch scripts, and tried to understand how admin controls actually worked. I was not just interested in using computers. I was interested in making them do things, finding limits, bypassing restrictions, and figuring out why something failed.
One early lesson came from a screen-time control device connected to our TV. My stepdad kept changing the PIN because I kept figuring it out. What I was really doing was listening to the keypad tones, memorizing the pattern, and mapping the sounds back to numbers. At the time, I just wanted more video game time. Looking back, it was the same mindset that pulled me toward penetration testing later: observe the system, find the weak point, test the assumption, and understand the failure.
Cybersecurity gave that curiosity a responsible direction.
Full story on the about page →
Age 6–10
Took apart computers. Learned Windows, hardware, and software. Broke things, fixed them, tried again.
Early lesson
Controls fail when the surrounding process is predictable. The weakness was never the device. It was the behavior around it.
Age 12
Knew technology was the direction. Penetration testing gave structure to the curiosity about how things fail.
Today
Security engineering, public-safe tools, engineering patterns, and practical fixes.
