Author & lifelong learner
One More Patch — practical notes from the IT/security trenches
I’m the writer behind One More Patch—an IT professional who treats security as a habit, not a finish line. Here you’ll find practical observations, lessons learned, and the occasional “well, that was avoidable” moment from real-world operations.
I’m not here to sell services or play elite-expert bingo. I write to document what I’m studying, what worked (and what didn’t), and the small improvements that add up—patch by patch—across identity, operations, and risk.
Security, One More Patch at a Time
I write about security as a practice, not a finish line: patching, hardening, IAM basics, and the small controls that actually move risk. Expect practical notes, what I’d do differently next time, and links worth bookmarking—without the doom, hype, or “just run this script” energy.
IT Operations & Lessons Learned
Most security work lives in the messy middle of operations—inventory, logs, identity, backups, change windows, and vendor quirks. I share real-world lessons from the admin side: what broke, what worked, and how to make systems a little more resilient (and a little less surprising).
Curiosity, Research & Continuing Ed
This blog is my learning trail: reading notes, lab experiments, conference takeaways, and “wait, how does that really work?” deep dives. I aim for clear, humble explanations that help other IT folks level up—because there’s always one more patch.
ABOUT THIS BLOG
One More Patch is a personal field journal for IT and security work—where learning never ships finished.
One More Patch started as a place to write down the things I kept re-learning on the job: why the “quick fix” becomes technical debt, how small configuration choices ripple into risk, and why the best security improvements are usually the boring, repeatable ones.
The goal is practical clarity. I share observations, lessons learned, and research notes that I’d want in my own backlog—grounded in real-world constraints, sourced when possible, and written to be useful to other working admins and security learners, not to impress anyone.
This site is independent, not sponsored by vendors, and not a consulting pitch in disguise. If you read along, share feedback, or point out a mistake, that’s what keeps it honest—and keeps me accountable to the work instead of the hype.
STAY IN TOUCH
Get new posts when there’s one more patch
Have a question, a correction, or a topic you’d like to see covered? Drop a note—or just say hi. I read every message, and the best ones often turn into future posts (with credit when it’s due).