Showing Post From DevOps
Container engines in 2026: revisit Docker Engine, Podman and containerd before you install another container daemon
On most teams, installing a container engine is the first thing done on a new machine and the last thing anybody thinks about.
Read moreConfiguration management in 2026: revisit Ansible, Salt and Puppet before you write another server setup script
Almost every team has one: a setup.sh or bootstrap.sh written for the first production server and grown every year since. It installs packages, edits configuration files with sed, creates users and starts services.
Read morePython dependency tooling in 2026: revisit pip, Poetry and uv before you rebuild another virtualenv
Every Python team has the same conversation at least once a year. One developer has started using uv on a side project and wants to move every service to it, because installs that took a minute now take a few seconds.
Read moreKubernetes packaging in 2026: revisit Helm, Kustomize and Timoni before you template another YAML file
Sooner or later every team on Kubernetes has the same argument. One person says Helm charts have become unreadable and the team should move to plain YAML with Kustomize overlays.
Read moreSelf-hosted CI in 2026: revisit Jenkins, Woodpecker CI and Tekton before you add another build agent
Most teams that keep builds on their own servers did not choose their CI engine recently. It was chosen years ago, by someone who may have left, on a machine that has been upgraded “when there was time”.
Read moreDependency updates in 2026: revisit Renovate, Dependabot and Updatecli before another library falls three majors behind
A dependency rarely breaks your system on the day it goes out of date. It breaks it eighteen months later, when a security fix lands only on a major version you skipped, and the upgrade that should have been a ten minute review becomes a two week project.
Read more