Deny First.
Verify Always.
Every engineer eventually reaches the point where the right answer is no.
Not because you can’t do it — you probably can. But because saying yes to everything is how complexity compounds, how scope creeps, and how good infrastructure quietly becomes someone else’s problem at 2am. Implicit deny isn’t just a firewall rule. It’s a discipline. Start with no. Build toward yes only when it’s earned.
That’s the philosophy this blog runs on.
I’ve spent 20 years across the infrastructure stack — a decade as a network engineer, a decade as a systems engineer and architect. These days I’m focused on large-scale virtualization, cybersecurity, and building AI-capable infrastructure in constrained and air-gapped environments.
Institutional Knowledge Doesn’t Transfer Itself
Something’s happening in enterprise IT that nobody’s saying loudly enough. The engineers who built their careers on deep, hard-won infrastructure knowledge — the ones who’ve sat through three generations of hypervisors, who learned BGP from a Cisco press book and a lab full of routers because that’s just what you did back then — are aging out of the workforce. And nobody’s systematically handing that knowledge down to whoever’s coming up behind them.
AI is speeding that up, for what it’s worth. Junior engineers reach for a chat interface before they reach for actually understanding why something works the way it does. That’s not me knocking them — it’s just the structural shift happening right now. But it means the gap between looking capable and actually being capable is widening fast, and somebody should probably say that out loud.
So that’s what this exists to push back on. Not with textbook rehashes or vendor doc rewrites — there’s plenty of that already. With the kind of perspective you only get from actually making the mistakes, actually seeing the edge cases, actually spending enough time in production to know what matters and what’s just noise. Two decades across networking and systems gives you opinions whether you asked for them or not. This blog is where mine go.
The Human Behind the Terminal
I’ve spent over seven years living in Korea across different stretches of my life — enough time to develop a genuine love for the culture, the food, and the particular brand of organized chaos that makes Seoul one of the most interesting cities on earth. Budae jjigae at midnight is a perfectly valid life choice.
When I’m not working, I’m usually in the home lab. My current obsession is self-hosting everything — the goal being to progressively replace every cloud service I pay for with something I run and control myself. It’s part principle, part curiosity, and part the kind of project that never quite finishes, which is honestly the appeal.
What Gets Published Here
Infrastructure deep dives. Security takes that don’t pull punches. Honest assessments of the vendor landscape — including when the answer is to walk away. Home lab builds and self-hosting guides for people who want to actually understand what they’re running. And occasionally, an opinion piece when something in the industry needs saying plainly.
If you’re a junior engineer trying to build real depth: this is written for you. If you’re a seasoned practitioner who’s tired of surface-level content: also for you. If you’re a vendor hoping for favorable coverage in exchange for nothing: implicit deny.