Let’s be honest. Up until now, my learning process has been… optimistic. I spent a good chunk of my time as a 3rd-year Computer Engineering student at PICT assuming my brain was a perfectly indexed database.
Spoiler Alert!!!: it’s not.
It’s more like a neglected /tmp directory that’s been collecting garbage since Semester 1.
This blog exists because I’m done with delusional learning. I’m entering my Proof of Competence era. If I can’t explain a concept, a failure, or a research idea in a way that’s both accurate and engaging, then I probably don’t understand it as well as I think I do.
The Mission: Learning in Public
A GitHub repo full of commits looks impressive until you realize it hides the chaos. The failed experiments. The lab sessions where nothing works. The 2 AM research rabbit holes that start with “just one paper” and end with an existential crisis.
This space is my public logbook. Here, I’ll document:
Cybersecurity Experiences
The reality of working on behavioral trust frameworks, network defense, and why “secure by design” often isn’t.The Project Grind
The evolution of ideas and implementations like B-ARP (Blockchain Secured ARP) including what broke, why it broke, and how I fixed (or abandoned) it.The Human Side of Tech
The frustration, breakthroughs, and hard-earned lessons that come with surviving the SPPU curriculum while trying to actually learn something meaningful.
Why the Sarcasm?
Because most technical writing is soul-crushing.
If a protocol is flawed, I’ll roast it.
If a project fails, I’ll document the autopsy.
If something works, I’ll explain why not just that it does.
The goal is consistency, honesty, and usefulness. Think of this as a roadmap for students and early researchers who are navigating the same mess minus the illusion that everyone else has it figured out.
I’m building my cybersecurity career in public one experiment, one failure, and one lesson at a time.
Stick around if you want to watch a PICT student try to break into cybersecurity without losing his mind (or at least while documenting the process).
If you’re also tired of dry documentation, leave a like. It’s better for my ego than a 404 error.
Top comments (0)