Platform Engineering
Notes on building internal developer platforms: golden paths, self-service infrastructure, platform APIs, and the org design that makes platform teams effective rather than another bottleneck.
22 articles
Day 50: Fifty Days Later — the Whole Arc, in One Place
From 'what is DevOps, actually' to 'who can be a platform engineer' — a full recap of the five phases this series walked through, and the one question every day of it was really answering.
September 4, 2026 6 min read
Day 47: Every Platform Team Is on a Journey. Where Are You?
From ad-hoc scripts to an AI-native platform — a six-level maturity model for judging honestly where a platform actually stands, not where its roadmap slide claims it stands.
September 1, 2026 4 min read
Day 45: Good Intentions. Bad Patterns. Big Impact.
Every platform failure this series has warned about individually — building in secret, over-engineering, ignoring developer experience — shows up together as five recurring anti-patterns. None of them come from bad intentions.
August 30, 2026 5 min read
Day 41: Secure by Design. Enforce by Default.
Manual security review doesn't scale, and policies drift the moment humans have to remember to check them. Policy as code writes the rule once and enforces it everywhere, automatically, forever.
August 26, 2026 4 min read
Day 39: Build What Differentiates. Buy What Accelerates.
There's no universal right answer to building versus buying platform tooling — only the right answer for your team's goals, resources, timeline, and what actually differentiates you.
August 24, 2026 4 min read
Day 38: Adoption Is the True North. It's What Proves a Platform Delivers Value.
A platform with excellent DORA metrics for the ten teams still using it and zero adoption everywhere else isn't succeeding. Adoption is the one metric that can't be faked by looking only at your happy users.
August 23, 2026 4 min read
Day 36: Build Platforms Developers Love, Not Platforms They Tolerate.
Opening the Advanced Platform Engineering phase with the discipline that decides whether everything built so far actually gets used: platform product management.
August 21, 2026 4 min read
Day 31: Platform APIs Turn Infrastructure Into Self-Service at Scale.
A platform API is the contract between developers and everything running underneath — Kubernetes, CI/CD, observability, secrets. Get the contract right and self-service scales to hundreds of teams without chaos.
August 16, 2026 4 min read
Day 30: Kubernetes Isn't Just a Tool. It's Your Platform's Foundation.
Running Kubernetes and building a platform on Kubernetes are different jobs. The gap between them is exactly the three layers this series spent Day 28 mapping out — all built on top of what K8s already gives you for free.
August 15, 2026 4 min read
Day 29: GitOps — Declare It in Git, Let Automation Do It
GitOps isn't 'CI/CD but for Kubernetes.' It's a specific claim about where truth lives — and once you take that claim seriously, drift, rollbacks, and audits stop being separate problems.
August 14, 2026 5 min read
Day 27: One Platform. Limitless Impact.
Self-service, golden paths, and guardrails aren't three separate initiatives — they're facets of one thing: the Internal Developer Platform. Pulling this phase of the series together into the artifact it's all been building toward.
August 12, 2026 4 min read
Day 26: Don't Build Gates. Build Guardrails.
A gate asks permission and waits for a human. A guardrail lets you move at full speed and only intervenes when you're about to leave the road. Platform engineering has to pick one, and the wrong choice recreates the ticket queue.
August 11, 2026 5 min read
Day 25: We Don't Remove Choice. We Remove Bad Choices.
A golden path is the opinionated, production-ready way to accomplish a common task — not a restriction on what's possible, but a fast lane that makes the right way also the easy way.
August 10, 2026 4 min read
Day 24: Self-Service Isn't the Absence of Control. It's Governance That Scales.
A ticket queue for infrastructure requests feels like control. It's actually just latency with extra steps. Self-service platforms replace waiting with automated, guardrail-enforced approval — without giving up governance.
August 9, 2026 5 min read
Day 21: A Platform Isn't a Project. It's a Product.
Ship v1.0, declare victory, move on — and six months later nobody's using it. Treating an internal developer platform like a product instead of a project is the difference between adoption and a very expensive shelf-ware.
August 6, 2026 5 min read
Day 20: Platform Teams Exist to Remove Friction, Not to Add Layers.
The fastest way to make a platform team fail is to let it become another approval gate. The reason platform teams exist at all is the opposite instinct: fewer people should have to think about infrastructure, not more.
August 5, 2026 4 min read
Day 19: DevOps Is How We Build. Platform Engineering Is What We Build On.
Two disciplines keep getting flattened into one because they're both about shipping software faster. They're not the same thing — one is a practice everyone follows, the other is a product with actual users.
August 4, 2026 4 min read
Day 18: Platform Engineering Builds the Highway. Developers Drive.
Platform engineering isn't DevOps with a new name. It's the discipline of building the internal developer platform that makes DevOps practices achievable without every team reinventing them.
August 3, 2026 4 min read
Day 9: Manage Everything Like Code. Not Like Chaos.
Terraform gets infrastructure into Git. That's one system out of six that can still drift silently. Everything-as-code is what happens when the same discipline applies everywhere else too.
July 25, 2026 5 min read
Day 3: Silos Don't Build Software. Teams Do.
Silos aren't a personality problem — they're a rational response to how each team gets measured. Fixing them means changing the incentive, not asking people to talk more.
July 19, 2026 4 min read
Day 2: The Three Ways — the Actual Theory Behind DevOps
Flow, feedback, and continuous learning aren't a checklist. They're a sequence — and most teams stop after the first one, then wonder why 'doing DevOps' didn't fix much.
July 18, 2026 4 min read
Day 1: What DevOps Actually Is (Not the Job Title)
DevOps isn't a role you hire for — it's a set of practices for closing the gap between writing code and running it. Here's what that means in a system that has to ship.
July 17, 2026 5 min read