Skip to main content
← /writing

topic · 33 essays

Platform Engineering

Platform engineering is the work of taking decisions every team would otherwise make differently and turning them into shared defaults, templates, and guardrails. Done well, the right way is also the easy way. I've built two greenfield cloud platforms in financial services. Most of what I believe about this work comes from the choices that aged well and the ones I'd redo.

A few positions run through these essays. Platforms only work when defaults are inherited, not chosen. Removing direct production access is a culture change before it's a tooling change. Complexity is unavoidable in a large organization, and the drag it creates is something you can design out.

The newer essays ask what changes when the platform gets a second user. Developers now arrive with an AI agent beside them, and the agent can't work around the ambiguity people absorb every day. That makes agent readiness a useful test of platform maturity. It also moves work onto the platform: trusted context, an interface that accepts intent, an identity for the agent, and a way to stop it.

Abundant generation makes constraints more valuable. An agent can produce hundreds of technically valid solutions, and none of them tells it which one fits your security model, cost expectations, or support model. So the paved road matters more once agents arrive. It's the boundary between what an agent can create and what the organization is prepared to operate. Every default, error message, and exception also teaches engineers and agents how work gets done, whether or not anyone chose the lesson.

Start with the essays below. The Agent-Ready Platform series takes the second half of this argument in order.

start here · 9 essays

The essays to read first

  1. 01
    Complexity Is Inevitable. Drag Is Optional.
    13 min read

    The pre-agent thesis: good platforms convert unavoidable complexity into defaults and automation.

  2. 02
    Building Cloud From Zero: Five Decisions That Compounded and Three I’d Redo
    16 min read

    Two greenfield cloud builds in financial services: the decisions that aged well, and the ones I'd redo.

  3. 03
    Pipeline-First Is Not a DevOps Initiative - It's a Culture Shift.
    7 min read

    Removing production access is a culture problem, and culture problems do not yield to Terraform.

  4. 04
    Your Platform Has a New User: The Agent
    11 min read

    Names the new user: the platform now serves the developer and the developer's agent.

  5. 05
    Context Is a Platform Capability Now
    9 min read

    The first capability: trusted context, provided by the platform instead of gathered by hand.

  6. 06
    The Golden Path Needs an Intent Interface
    7 min read

    The interface moves up: developers state intent, and the golden path becomes the compiler target.

  7. 07
    Your Platform Is Teaching Your Engineers
    9 min read

    Defaults, errors, and exceptions show engineers and agents what normal work looks like.

  8. 08
    The Agent Is Wearing Your Badge
    14 min read

    An agent acting on your authority needs its own identity and a stop the platform can prove.

  9. 09
    The Developer Experience Ledger
    10 min read

    Follows a saved hour across the delivery journey, so platform teams can see what they remove.

go deeper

the full list · 33 essays

Every essay on this topic

Agentic SDLC

Architecture Is What Agents Can't Refactor

Agents made code structure cheap to change. What's left of architecture is what a revert can't undo and what needs someone else's agreement, so that's where platform teams should spend their design time.

13 min read · 2.5k words
★
Engineering Leadership

What the Rollup Leaves Out

Writing my transition plan showed me what our metrics could not establish: what people had learned, how their judgment had developed, and what my leadership had contributed.

7 min read · 1.4k words
★
AI Economics

Your Agent Is Bad for Their Business

An agent that saves you money threatens somebody else's revenue. Amazon, Walmart, the banks, and the card networks are deciding who gets to influence the customer's decision, and better authentication settles only part of that argument.

16 min read · 3.1k words
★
Platform Engineering

The Agent Is Wearing Your Badge

An agent acting with your credentials can leave a record of your authority without a record of its involvement. Platform teams need to preserve who acted, under whose authority, and how to stop that access.

14 min read · 2.7k words
★
Platform Engineering

Omarchy: Linux Finally Reached My Desk

Omarchy installed on a drawer laptop in two minutes and everything worked. The reason is a platform lesson: choose the defaults, keep the escape hatches, and make the system legible to the agent.

11 min read · 2.0k words
★
Agentic SDLC

Your Agent Workflow Needs a Release Process

Kiro's frontier engineering principles describe how to work well with agents. Making that practice dependable across a team means treating the shared workflow as a software release, with a version, a scope, an owner, and tests for when it should stop.

10 min read · 2.0k words
★
Platform Engineering

The Developer Experience Ledger

An AI tool can save a developer an hour while the delivery journey consumes most of the saving. The developer experience ledger follows the work across that boundary, so platform teams can tell what they removed and what they merely moved.

10 min read · 1.9k words
★
Engineering Leadership

From Faster Code to Better Engineering

Sixteen months of building and writing taught me that AI makes implementation cheaper while raising the value of clear intent, trustworthy platforms, operational understanding, and human judgment.

18 min read · 3.4k words
★
Agentic SDLC

Nobody Pages the Agent

A gate proves a standard ran. It does not prove anyone can operate the result at 3 a.m. Operability has to become part of the spec, and the evidence has to survive the merge.

12 min read · 2.3k words
★
Platform Engineering

The Golden Path Needs an Intent Interface

The golden path made the right way easier to follow. It still asks developers to learn the road. With AI, intent can become the interface while the platform keeps the standards, the controls, and the gate.

7 min read · 1.3k words
★
Spec-Driven Development

The Spec Is the Product

Code used to be the durable asset. In an agentic SDLC, that changes. Code becomes the regeneratable output of a system that runs on something more important: a clear, versioned, reviewable specification. That shift changes what engineering organizations invest in, how they govern delivery, who they hire, and what they actually ship.

10 min read · 1.9k words
★
Platform Engineering

AI Populism is a Builder's Problem

Jasmine Sun argues AI politics has a new meta, and the warning shots have started. Reading her piece as an engineering leader, here is what the narrative failure looks like from inside a large team, why sociopolitical alignment is our job, and what each of us owes our own career in a market this fast.

6 min read · 1.0k words
AI Coding

Claude Code Is a Build System, Not a Chatbot

After thirteen months of daily Claude Code use, I stopped treating AI coding as a prompt discipline problem and started treating it like an engineering system: configurable, layered, observable, and built to learn.

18 min read · 3.6k words
GenAI

They're Using Claude to Ship Claude (And It Shows)

Anthropic has shipped more meaningful product features in the last few weeks than most teams ship in a quarter. A theory, and what it tells us about what AI-assisted development actually unlocks when a team uses their own product to build it.

6 min read · 1.1k words
GenAI

The Future of Interfaces

AI-powered interfaces are evolving beyond traditional graphical UIs toward intent-based interactions, where users describe desired outcomes rather than navigating through menus and clicks.

2 min read · 339 words