Explorations

The foundation everything else runs on.

From first login to production confidence — not sysadmin training, practical Linux competence for developers and platform engineers who need to get work done.

Your app has to become a container. This is where you actually learn how.

What a container actually is — not a lightweight VM — plus the Dockerfile, the build, and the registry push most tutorials skip past. Day One splits by situation: containerize a single app for the first time, or break a monolith out of VMs one deliberate seam at a time.

Your company adopted it. This gets you functional — then fluent.

Start by getting your app deployed and debugging when it breaks. Then go past copy-pasted YAML: what each core object actually is — Pods, Services, config, namespaces, labels — why it's built that way, and its blast radius on a cluster you share. Then the workloads you'll actually create day to day: Deployments, ReplicaSets, Jobs and CronJobs, and the two fields every real container spec needs — resource requests/limits and health probes.

The layer between "works on my machine" and "it's down in prod."

Practical networking for SREs and platform engineers, taught through real incidents instead of OSI-model theory. How an API gets exposed and secured on the wire, DNS resolution, load balancer health checks, and TLS certificate automation.

Your platform team adopted Flux. This explains what changed.

GitOps with FluxCD — your desired state lives in Git and the cluster reconciles toward it. Day One gets developers working confidently on a Flux-enabled cluster: what changed, why you commit instead of kubectl apply, and how to read what Flux is doing.

For platform engineers who already know bash.

Task-first, not syntax-first. You don't need to understand decorators before you can write a health-check poller. This site starts with the task. The Python comes with it.

You know how to code. This teaches you why it works.

The formal theory that makes you a stronger engineer — Big-O, data structures, FSMs, parsers, compilers. Not academic exercises; the stuff that makes you able to explain your own PR.

The tools that make working with everything else bearable.

Git workflows, editors, terminal multiplexers, and the other tools that separate engineers who fight their environment from ones who work in flow.