From Curiosity to Certification: My Cybersecurity Journey
How a Fascination with How Things Work Led Me into Cybersecurity - The Challenges, the Late Nights, and the Lessons Learned Along the Way.
The Spark
It started with a question that would not leave me alone: "How do hackers actually hack?" I was 16, building my first PC, when I first heard about cybersecurity. The idea that there were people who found vulnerabilities in systems, who could think like attackers - that fascinated me.
I did not want to break things. I wanted to understand how they could be broken, so I could help build stronger systems.
The Learning Curve
My first attempts at learning cybersecurity were overwhelming. There was so much to know - networking, operating systems, programming, cryptography. I did not know where to start, so I started everywhere at once.
I spent evenings watching ethical hacking videos. I spent weekends setting up virtual labs. I failed more times than I can count. But each failure taught me something new.
Building My Toolkit
Instead of just consuming tutorials, I decided to build. I created my own security tools - not to use maliciously, but to understand how attackers think. A port scanner helped me understand networks. A password strength checker taught me about cryptography.
Every tool I built became a learning opportunity. I documented everything. I asked questions in forums. I made mistakes and learned from them.
The University Years
When I started my BSc in Cybersecurity, I realized how much I had already taught myself. The formal education complemented my practical skills perfectly. Theory explained why the techniques I had discovered actually worked.
The Road Ahead
I am still early in this journey. There is so much more to learn. But that is what makes cybersecurity exciting - the endless learning curve, the constant evolution, the need to stay ahead of attackers.
To anyone starting: your curiosity is your greatest asset. Nurture it. Ask questions. Break things (in your own lab). That is how we grow.
Feel free to reach out with questions: haynesluke96@gmail.com
Luke Dodge
DevSec Engineer & Full-Stack Developer