The Script Kiddie Era

Here's something I haven't told many people, and it's time to put it in the record: before I was a programmer, I was a script kiddie.

Not in the criminal sense, let me be clear about that. I wasn't out here trying to bring down banks or steal credit cards. But after I learned Python, after I started understanding how systems communicated, I became fascinated by cybersecurity. Not the theory. The practice. The actual, hands-on, what- happens-if-I-try-this kind of practice. I was that kid downloading tools I didn't fully understand, running scripts I found on forums, poking at systems just to see what would happen. Script kiddie energy. Curious, reckless, hungry to understand how things broke and what happened when they did. The difference is, most script kiddies stay script kiddies. They run other people's tools and never learn what's underneath. I couldn't do that, you know this about me by now. The surface was never enough.

So I started learning. What makes an exploit work? What is a buffer overflow actually doing to memory? How does a SQL injection manipulate a database? How does a packet look when it's been crafted for reconnaissance versus normal traffic? I went from running tools to understanding them to wanting to build my own. The script kiddie phase wasn't a destination. It was a doorway. And I walked through it.

Then I built something that still makes me laugh: a penetration testing bot controllable through Telegram and WhatsApp. Let me say that again because it sounds absurd and it was: I built a bot that could perform security testing tasks, and you could control it by sending commands through messaging apps. Just type a command into Telegram, and somewhere a system would execute it. Type another command into WhatsApp, and the bot would respond with results.

It was ridiculous. It was powerful. It was the kind of thing you build when you're too young to know you're not supposed to be able to build it, and too stubborn to stop once you've started. I don't think anyone outside my immediate circle ever saw it or used it. But I knew it worked. I knew what it meant. I knew that I had built something that crossed boundaries, between messaging and systems, between casual interfaces and serious security tools, between what people thought a teenager could do and what I had actually done.

The gap again. Always the gap.