Practical articles on AI, DevOps, Cloud, Linux, and infrastructure engineering.
A container is a process with extra kernel features applied. Walking through namespaces, cgroups, and the actual mechanics — the level of detail that makes "container weirdness" debuggable.
We have a few hundred shell scripts in production. The patterns that make them survive contact with reality, and the ones we've stopped writing.
Filesystem choice, mount options, IO schedulers — the per-host tweaks that actually moved disk performance for our database and storage workloads.
How processes actually live and die on Linux, the tools that show what's happening, and the patterns we use for monitoring service health.
A practical Linux hardening checklist for production hosts. The settings that earn their place via real production reasons, not the cargo-cult version.
A condensed checklist of the systemd unit-file patterns we now use everywhere, with the production reasons each one matters.
A systematic approach to debugging Linux network issues. The tools that earn their place and the order I use them in.
A practical Linux performance tuning playbook for production servers. The kernel parameters, disk and network tweaks that earn their place, and the ones that turned out to be folklore.
A practical guide to writing and managing systemd services for production. The unit file features that earn their place, plus the operational workflows.
We had four different patch cadences across our fleet and routinely missed CVEs by weeks. The unified workflow that finally caught up.
A team of 30 engineers all editing the same monolithic Ansible repo doesn't work. Here's the role taxonomy and review process that did.
Concrete systemd unit patterns that reduced flakiness: restart policies, resource limits, and structured logs.
