About Me

It started in the dial-up days — back when connecting to the internet meant tying up the phone line and hoping nobody picked up. I got curious about how things worked under the hood, started writing tools that interacted with the software everyone was using, and eventually that curiosity led somewhere it probably shouldn't have for a middle schooler. Nothing I'm proud of, but it built a foundation that a computer science degree couldn't replicate: a genuine understanding of how systems can be abused, which is the best way to learn how to defend them.

Being the local "computer guy" meant I was also fixing everyone's machines — diagnosing bad RAM, corrupted installs, networking headaches. By the time I finished a Bachelor of Applied Science in Network Security & Computer Forensics, I'd already been doing the work for years.

My first real IT job was junior sysadmin work for a local municipality. From there I moved through several sysadmin roles, always leaning on scripting and programming to automate things faster than the next person. That eventually landed me at a large MSP — which got acquired. After a year under new management I jumped to an MSSP as a Solutions Engineer: top-tier escalation for AlienVault and several other SIEM platforms, while managing the SOC's internal AD environment. I rewrote their core customer monitoring tool in Python and Flask while I was there.

That company merged too. The acquiring company had a real dev team and offered me a choice: stay in solutions engineering or move to development. I moved to dev and built integration tooling for Splunk and LogRhythm — first in Python, later ported to Node.js.

When I saw the writing on the wall there, I landed at my current role: Systems Engineer at a large national homebuilder and Berkshire Hathaway company, where I'm part of a team managing a five-figure endpoint environment across the enterprise.

As a Systems Engineer III, my day-to-day is Microsoft Intune, SCCM/ConfigMgr, Azure, and the PowerShell that holds it all together. Currently working toward my Azure Foundations certification as we continue expanding our Azure footprint.

"I was usually the last escalation before a vendor call. I hate vendor calls. So I started writing things down."

This site is a documentation habit turned public. The posts here cover the tricky, specific, hard-to-Google problems — the ones where the answer exists somewhere on the internet but takes three hours to find. SCCM, Intune, PowerShell, Active Directory, and whatever crossed my desk recently.