Practical, tested guides for developers and DevOps engineers: Git and GitHub Actions, AI tools, Kubernetes and Docker, and cloud services across AWS, Azure and GCP.
Written by Amaresh Pelleti. I run the commands in new guides before I publish them, and show the real output.
Browse by topic
GitBranching, workflows, recovery and team conventions
GitHub ActionsWorkflow YAML, CI/CD pipelines, testing and security
AI toolsOllama, Claude Code, local models and coding assistants
CloudAWS, Azure and GCP: service comparisons and identity setup
KubernetesCluster concepts, networking, troubleshooting and certifications
DockerImages, volumes, Compose and Docker vs Podman
Start here
One guide from each topic that readers use most.
GitGit Flow vs GitHub Flow vs Trunk-Based DevelopmentHow each workflow works, the commands, and how to pick one for your team.
GitHub ActionsGitHub Actions Workflow Files: YAML ExplainedTriggers, jobs, steps, permissions, matrix builds and reusable workflows.
AI toolsTrain Your Own Local AI ModelFine-tune an open model on your own machine and run it offline in Ollama.
CloudAWS Secrets Manager vs Azure Key Vault vs GCP Secret ManagerThe three secret stores compared side by side.
KubernetesKubernetes in 2026: The Complete Guide for DevOps TeamsCore concepts, security and where to go next.
DockerDocker vs Podman: Which Container Tool Should You Use?Rootless, daemonless, and which one fits your setup.
Latest guides
- Git Rebase vs Merge: What Changes, Tested on Git 2.56Git merge joins two histories and adds a merge commit, leaving every existing commit untouched. Git rebase replays your commits on top of another branch, so they get new SHAs and the history becomes a straight line. The git-rebase docs… Read moreGit Rebase vs Merge: What Changes, Tested on Git 2.56
- Git Commit Message Conventions: Format, Hook and CI CheckThe git commit message conventions I would use are type(scope): description on the first line, a blank line, then an optional body. That is the Conventional Commits format. Git itself requires none of it, so a convention only helps if… Read moreGit Commit Message Conventions: Format, Hook and CI Check
- Git Branch Naming Conventions: Patterns and a CI CheckThe git branch naming conventions I would use are a lowercase type/short-name pattern, such as fix/empty-password-crash, with an optional ticket number. Git enforces only a short list of hard rules. Everything else is a team agreement, so the useful part… Read moreGit Branch Naming Conventions: Patterns and a CI Check
- GitHub Flow: 6 Steps, Tested With the gh CLI and RulesetsGitHub flow is a branch-per-change workflow: you branch off main, push commits, open a pull request, get a review, merge, and delete the branch. GitHub’s docs list exactly those six steps and no others. I ran all six in a… Read moreGitHub Flow: 6 Steps, Tested With the gh CLI and Rulesets
- Git Recover Lost Commits: 12 Fixes for Common MistakesTo git recover lost commits, run git reflog, find the hash from before the mistake, and point a branch at it with git branch rescue <hash>. Almost every local Git mistake can be undone this way, but only if you… Read moreGit Recover Lost Commits: 12 Fixes for Common Mistakes
- CLAUDE.md vs AGENTS.md: Which Claude Code ReadsClaude Code reads CLAUDE.md first and falls back to AGENTS.md only when no CLAUDE.md exists. That one rule settles most claude.md vs agents.md questions. If you also use Codex, Cursor or Copilot, put the shared rules in AGENTS.md and add… Read moreCLAUDE.md vs AGENTS.md: Which Claude Code Reads
- Terraform vs Pulumi: Which to UseChoose Terraform when your team wants one declarative language that every cloud engineer already reads. Choose Pulumi when you want loops, tests and secrets handled in a real programming language. The terraform vs pulumi decision matters less for what each… Read moreTerraform vs Pulumi: Which to Use
- Cloud Run vs Cloud Functions: What Changed and Which to UseCloud Functions is now Cloud Run functions, and that changes the cloud run vs cloud functions question. A function you deploy today runs as a Cloud Run service. So the real choice is between handing Google your source code or… Read moreCloud Run vs Cloud Functions: What Changed and Which to Use







