Becoming Something
Why this blog exists, and the one rule I'm holding myself to: write up the dead ends, not just the wins.
This is the first entry. I want to set the one rule I care about: document the failures.
Most security write-ups present a clean path from question to exploit, as if the author never took a wrong turn, which confused me at first. I came to realize That’s not how any of it actually happens, and pretending otherwise makes the field feel more gatekept than it is. So the deal here is that the confusion stays in. Now, some of the rabbit trails can lead to a fruit, but for the reader’s sake they can be distracting. So, I’ll keep tabs of success/failure in a format that’s reproducible and readable.. hopefully.
What this looks like in practice
A post here should have a shape or purpose. It could be:
- A specific, concrete thing I didn’t understand.
- Research that I’m conducting or tools I’m building.
- CTF findings, write-ups, or experiences as a wannabe red-teamer.
Only allowed write-ups for platforms will be posted. Write-ups may consist of older CTFs such as older challenges on platforms like HackTheBox, VulnLab, pwncollege, or Pwned Labs
Frequency of Posts
My goal is to keep myself honest and push to post weekly, if not more. Why? Because I work on CTFs, build vulnerable infrastructure, make tools daily. I should always have material to work on or go through. I don’t know it all so I can easily take some concept here or there to study more and share here.
Overall
This blog is for me. I want to grow. I want to learn. I want to do everything in excellence. I want to be the best I can be. I don’t want to grow stagnant. Cheers to my future self.. Let’s hope I stay disciplined and humble!