From Snowflake Servers to GitOps Nirvana: A beginner-friendly tour of the declarative stack that actually runs itself

You’ve probably heard the buzzwords: GitOps, NoOps, immutable infrastructure.

Today I’d like to walk you — step by step — through why these concepts exist and how a small constellation of tools (Git, NixOS, Docker, Terraform, Kubernetes, ArgoCD, DSPy, and a pinch of OPA policy-as-code) fit together to create a platform that deploys itself every time you hit merge.

1. The Problem We’re Solving

In the old world, a server was a pet: lovingly hand-fed config files, patched on Sundays, and inevitably different from every other server. The result?

• “It works on my machine!”
• Snow-flake drift and 3 a.m. pages.
• Scaling = more pets.

2. The North Star: Everything as Code

Instead of pets, we want cattle — identical, replaceable, and defined in text files that live in Git. If Git is the single source of truth, the rest of the stack becomes a conveyor belt that turns that truth into running software.

3. The Cast of Characters and Their Jobs

Table: A Declarative Software Stack

4. How the Characters relate to Each Other

5. A Day in the Life of a Change

Let’s add a new feature: “Show real-time in-game leader boards”.

Code

• Write the leader board service in Go.
• Add a DSPy pipeline to pre-aggregate stats.
• Commit everything to git.

CI Gate

• Nix builds the Docker image (bit-for-bit reproducible).
• Terraform dry-run shows a new Redis cache.
• Tests pass → image is signed & pushed.

GitOps Sync

• Argo CD detects the new commit hash.
• Kubernetes manifests are applied; pods roll out blue-green.
• OPA policy ensures the service can’t talk to the payments DB.

Observe

• Prometheus sees p95 latency drop.
• Grafana dashboard auto-updates.
• No humans touched a server.

6. Beginner Take-aways

• Start small: Put one service in Docker, store its manifest in Git, and let Argo CD sync it.
• Lean on NixOS for dev laptops — nix develop gives the exact same tools as prod.
• Policies early: A 15-line OPA rule today prevents a 3 a.m. breach tomorrow.
• Celebrate merges: Every green PR is a fully tested, policy-compliant, zero-downtime release.

7. The Bigger Picture

Declarative, Git-driven stacks aren’t tools; they’re a culture. When everything is code, knowledge lives in the repo, not in someone’s head. That means faster onboarding, fearless refactors, and — best of all — Friday deploys that don’t ruin weekends.

Welcome to the Declared World: where the robots do the toil, and we get back to building great games.