DevOps¶

Git Workflow for Release Management: Branches vs Tags

Most teams invent their Git strategy as they go. One developer starts tagging releases. Another uses branches. A third creates a hotfix branch and never deletes it. By the time you need to patch a six-month-old release, nobody remembers what release-final-v2 means or where hotfixes actually landed.

A clear branching strategy prevents this. This post covers a battle-tested Git workflow built around two parallel approaches — version control with branches and version control with tags — and tells you exactly when to use each.

DevOps Project Example: From Code Push to Production with GitOps, FluxCD, and Kubernetes

Most DevOps tutorials show you a pipeline diagram. This one shows you a real pipeline, built on a real application, running on real Kubernetes clusters — with every tool, every workflow, and every design decision explained.

This post walks through the complete CI/CD system behind Slotmachine — a real-time multiplayer tournament app — from the moment a developer pushes code to GitHub, through six security and quality gates, all the way to automated deployment on both Nutanix on-premise clusters and AWS EKS. No hand-waving. No "and then magic happens."

The full source code is available in two repositories:

• Application repo: github.com/pkhamdee/slotmachine
• Deployment repo: github.com/pkhamdee/slotmachine-deployment

Cloud Engineer vs DevOps vs SRE vs Platform Engineer: Who Does What?

You're browsing job boards and you see four different titles: Cloud Engineer, DevOps Engineer, Site Reliability Engineer, Platform Engineer. The salaries are similar. The required skills overlap. Some listings seem interchangeable.

Are these the same job? Is one better than the others? Which should you aim for?

They are not the same job — but they are deeply related, and the confusion is completely understandable. Each role grew from a different pain point in how software gets built and run, and in 2026, all four exist inside most engineering organizations at the same time.

The DevOps Delivery Pipeline: End-to-End Framework

A DevOps framework is not a single tool or process — it is an end-to-end system that connects your product idea to production software, with quality and security built in at every step.

Engineering Standards for DevOps: The Complete Guide

A team without standards is a team that reinvents everything — every time, in every project. Standards are not bureaucracy. They are the codified answers to questions your team has already solved, so you can spend your energy solving new ones.

This guide covers thirteen engineering standards that separate high-performing DevOps teams from the rest. For each standard, we go beyond the "what" to explain the "why" and the "how" — with concrete tooling, configuration examples, and the decision frameworks you need to implement them in your organisation.

What Is DevOps? The Complete Guide

Ask ten engineers what DevOps is and you'll get ten different answers.

"It's CI/CD." "It's automation." "It's when developers do operations." "It's a culture." "It's a job title." "It's a toolchain." "It's a movement."

They're all partially right. And because DevOps touches culture, process, and technology simultaneously, it resists simple definition.