About

Security-first operator who builds faster, cleaner ways to work.

My background spans IT, cybersecurity, systems implementation, networking, and workflow design. I believe time is as valuable as money, and I hate wasting it on work that can be automated, simplified, or done better. If a process can be automated or done smarter, it probably should be.

🛡️ Cyber health first 🛡️ ⚙️ AI-assisted workflows ⚙️ 🧠 Security operations 🧠 🤝 Executive support 🤝 ⚡ Fast delivery time ⚡
Focus
Cyber + IT

Practical security and infrastructure work built around real support, implementation, and operational needs.

How I build
Fast loops

Build it, test it, break it, fix it. I’ll create processes, systems, and automations to keep things organized and efficient.

Tool preference
Useful automation

Automations, dashboards, API integrations, and assistants that save time instead of feeling like an unpaid intern.

How I think
Security first

Convenience is useful. Exposure is expensive. Security is like vegetables: most of us hate it, but it’s good for you.

I got into technology young.

At 10, I was coding and running my own Minecraft servers, which turned into an early obsession with how technology works, breaks, and how to make our lives better. I became the person people leaned on whenever something technical needed to be figured out.

That turned into real work early. In high school, I worked as an IT intern and later moved into system administration for small businesses, where I learned the foundations of real-world IT: networking, user support, infrastructure, access control, troubleshooting, and the operational chaos that no textbook fully prepares you for.

From there, I pursued cybersecurity and built experience across internal IT and MSP environments. I worked hands-on with Azure, Active Directory, Nerdio, network systems, endpoint environments, incident response, and infrastructure support, all while learning how cyber risks show up in the real world, not just on an exam.

My experiences shape who I am and how I think today. I do not look at security as a checklist. You have to look at the full system: users, devices, infrastructure, access points, weak defaults, workflows, and the risk hiding between everything.

My strength is turning messy technical environments into something cleaner, safer, and easier to run. I can troubleshoot the problem in front of me, but I also know when to step back, understand the larger risk, and build a better way to respond.

If it involves technology, there are very few problems I cannot learn, break down, understand, and solve.

Clickable skills, condensed into the lanes that actually matter.

Tap any skill to see a short description.

Core skills

Built for secure systems, real-world pressure, and getting technical work across the line.

OpenClaw

Built, configured, and secured my own OpenClaw environment on a dedicated server. I used it to create dashboards, host tools on custom ports, build this website, and prototype workflows like a sports analytics bot that analyzes previous games, season trends, player performance, and live variables to support prediction logic.

Cybersecurity

I’ve worked across the parts of cybersecurity that actually affect people. Accounts, devices, inboxes, networks, public exposure, identity controls, and bad defaults quietly waiting to ruin someone’s week. My focus is to proactively prevent risks through password manager rollouts, MFA hardening, mobile security, endpoint configuration, phishing workflows, OSINT exposure reviews, data broker removals, home network hardening, and executive-level support.

IT and delivery

I built my foundation through internal IT and MSP work. Serving as a lead specialist, escalation point, and core contact during technical emergencies. That meant supporting infrastructure, rolling out systems, solving urgent issues, and dealing directly with executives when things were already on fire or not exactly bringing their best customer-service energy.

This is where I learned how technology actually fails in the real world. It taught me not to crack under pressure, how to communicate with difficult users, how to spot risk before it becomes a bigger problem, and how front-line IT experience builds the instincts behind a true cybersecurity mindset.

I spent the last few months turning ideas into working systems fast.

I did not realize there was a name for it at first, but a lot of what I have been doing lately fits what people now call vibe coding. For me, it is not just prompting for code and hoping for the best. It is fast iteration, product instinct, technical judgment, and using AI to move from rough concept to usable tool without getting stuck in over-planning.

Since spinning up OpenClaw, I have been building in loops. Sketch the shape, get something working, see where it breaks, tighten the logic, improve the UX, and keep going until it actually earns its place. That process has driven Alfred-style assistant workflows, Mission Control as a personal operating surface, Sports Bagwaan as a private app, and even this site, which has gradually become more reflective of how I actually work instead of reading like a placeholder.

A lot of that work has lived across PHP, HTML, CSS, JavaScript, Node.js, Python, SQLite, JSON-based state, lightweight APIs, and careful prompt-guided iteration with models like Claude. The AI helps with speed, but the real value comes from knowing what to keep, what to throw out, how to debug weird behavior, and how to shape something into a cleaner system instead of a pile of generated parts.

I have also used Claude to help build Python tooling that reads structured Excel inputs and assembles polished PowerPoint outputs, cutting a process that used to eat most of a workday down to a much smaller window. That kind of work matters to me because good automation should reduce friction, standardize output, and give people more time for judgment instead of repetitive assembly.

I also work with OSINT researchers on background reporting, and that has pushed me to think carefully about verification, workflow quality, and being deliberate about what should stay private. The result is a style of building that is fast, hands-on, and creative, but still grounded in real constraints, real users, and real consequences.