So here I am—on a noble quest to become a network and cybersecurity engineer. A digital knight, if you will, except instead of a sword, I wield Wireshark and Python scripts, and instead of dragons, I fight NAT issues and firewall configs that mysteriously delete themselves. And you know what makes this whole journey survivable (and kinda fun)? Two unlikely
Tag: cybersecurity
This fall, while most people are buying pumpkin spice everything and pretending they like the cold, I’ll be doing something actually bold: going online full-time to Southeastern Louisiana University to kick off my Master’s in Computer Networking and Administration. That’s right. I’m going back to school. On purpose. “Why?” — People Who Know Me Because I like pain. Just kidding
Because textbooks speak fluent Martian and I prefer human. Here’s the deal: every time I take on a new topic—networking, cybersecurity, Python, how to survive a data analysis without summoning demons—I do something that feels almost rebellious. I buy a For Dummies book.Yes, on purpose. Not because I think I’m dumb. Not because I collect yellow covers like Pokémon cards.
Hey there. I’m your IT department.No, not part of a team. Not “one of the tech guys.”Just me. One human. One coffee-fueled, semi-burnt-out digital janitor holding this entire circus together with duct tape, Google searches, and sheer panic. And let me tell you: being a solo IT admin? It’s the most gloriously underappreciated, stress-inducing, caffeine-powered, thankless job on the planet.
Let me get this out of the way: yes, I know we’re living in the Age of AI. Machines are writing essays, generating art, chatting like therapists, and possibly plotting to take over your job while pretending to be helpful productivity tools. Meanwhile, “the cloud” isn’t just where your embarrassing high school photos live—it’s where your entire business infrastructure has
Let’s take it back. There I was—bright-eyed, highly caffeinated, and absolutely convinced that becoming a software developer was the move. Why? Because in my mind, devs were the tech world’s version of rockstars. They had it all—cool job titles, slick GitHub profiles, an endless supply of dark-mode editors, and a paycheck that whispered, “Go ahead, buy that mechanical keyboard with
Let me just say it loud and awkward:I want to be a network and cybersecurity engineer. I want to design resilient systems, stop intrusions, debug failed packets like Sherlock Holmes in a hoodie, and make sense of chaos.But right now? I’m just trying to make sense of my own voice on video. You see, I don’t do videos.Not because I’m
Let’s be honest. In IT, professional development often gets treated like that ancient printer in the breakroom — essential, ignored, and only noticed when it breaks down. But here’s the punchline: we’re the people keeping your Wi-Fi running, your files safe, and your bosses from emailing their passwords to “[email protected].” So, if you’re in management and you’re not investing in
When a few government websites got defaced, it wasn’t just a prank—it was a wake-up call that the Philippines is already caught in the crosshairs of a silent cyber war. I didn’t get hacked. No virus took down my PC. No ransomware locked up my files. But when I saw a few Philippine government websites defaced—replaced with foreign symbols, strange
Every journey begins with a single step—but not every step is documented. I’ve decided to write about my journey into network and cybersecurity engineering to share not just what I’m learning, but why I’m learning it. This is more than just a technical pursuit—it’s a commitment to growth, resilience, and the evolving role of technology in our lives. As someone