Developer Experience on Alfero Chingono

The DORA Report Was Right: IDPs Improve Team Productivity by 10% — Here's How I've Seen It

Thu, 10 Apr 2025 09:00:00 +0000

When the DORA research started surfacing stronger evidence around internal developer platforms, the headline did not surprise me nearly as much as the reactions did.

Some people still hear “platform engineering” and imagine more process, more gates, and another internal team inventing obstacles. That risk is real. But it is only one version of the story.

The version I have seen in practice is much simpler: when you reduce cognitive load, standardize the boring parts well, and make the safe path the easy path, teams move faster.

That is why the widely shared DORA finding about internal developer platforms improving team performance felt directionally right to me. I have seen that pattern from multiple angles: CI/CD modernization that improved project velocity, reusable delivery templates that removed duplication, feature-flag and configuration patterns that reduced rollout risk, and platform standards that made decision-making less expensive for product teams.

I would not claim every platform effort automatically produces a neat percentage uplift. But I do believe the mechanism is real.

What platform engineering is actually buying you

At its best, an internal developer platform is not a control tower. It is a friction reducer.

It helps teams spend less time answering questions like:

How should we structure this pipeline?
Which security checks are required?
What is the approved deployment pattern?
How do we manage runtime configuration safely?
How do we release gradually without gambling in production?

If every team answers those questions from scratch, you get inconsistency, duplicated effort, and unnecessary risk. If the platform team answers them once, clearly, and with enough flexibility, you get leverage.

That leverage is where the productivity gain comes from.

Not from a portal. Not from a dashboard. Not from a maturity model.

From fewer repeated decisions.

Where I have seen the gains show up

One of the more durable lessons in my career is that developer productivity is usually downstream of environment design.

At VCA Software, the measurable win was CI/CD modernization. We saw delivery speed improve because the path from code to release became more repeatable and less person-dependent. That did not happen because engineers suddenly became more talented. It happened because the delivery system stopped making them re-solve the same operational problems over and over.

In more platform-oriented work, I have seen the same principle show up differently:

a reusable feature-flag framework that makes progressive delivery safer
standardized pipeline templates that reduce copy-paste infrastructure
better observability defaults so teams are not blind after deployment
configuration-management patterns that reduce drift and remove manual setup

That last point is one reason I still like the pattern I wrote about in Conditionally Deploying Resources in Azure App Configuration Using Deployment Scripts. It is not glamorous, but it is exactly the kind of operational sharp edge a good platform should smooth out.

The DORA nuance matters too

What I appreciate about the DORA research is that it does not treat platform engineering as universally positive in every implementation.

That matches my experience.

A platform helps when it gives teams self-service with sensible defaults.

A platform hurts when it becomes:

mandatory ceremony
an opaque ticket queue
a rigid abstraction over real team needs
a place where local context goes to die

This is where some platform efforts go sideways. They optimize for governance theater instead of developer flow. Then leaders conclude that platform engineering is slow, when the real problem is that the platform is not being run like a product.

What good platform teams do differently

The best platform work I have seen has a few traits in common.

1. It starts with repeated pain, not abstract ambition

Good platform teams do not begin with “let’s build an internal developer portal.” They begin with “teams keep tripping over the same deployment, security, configuration, or release problems.”

That difference matters because it keeps the work grounded in actual developer friction.

2. It productizes standards

A standard that lives in a slide deck does almost nothing.

A standard that shows up as a reusable template, a safe default, a documented flow, a working example, and a supportable paved road actually changes behavior.

3. It respects local autonomy

The best platforms do not remove all choice. They remove the expensive choices that most teams should not have to make repeatedly.

That is a very different posture from central control.

4. It measures adoption, not just existence

If nobody uses the platform voluntarily, that is feedback.

Platform teams need to care about usability the same way product teams do. A paved road that engineers avoid is not a paved road.

My working definition now

I increasingly think of platform engineering as the discipline of making good engineering behavior easier to repeat.

That includes technology, of course, but also language, templates, defaults, and trust.

Done well, it gives teams more autonomy because it lowers the cost of doing the right thing. Done badly, it creates another dependency.

That is why the DORA finding resonated with me. Not because I am attached to the term, but because I have seen the underlying dynamic up close. When teams have usable internal platforms, they make better decisions faster.

That is not magic. It is what happens when you turn institutional knowledge into operable systems.

If this topic interests you, the closest companion piece here is Why I Started Building My Own DevOps Platform, which comes at the same problem from the builder side rather than the organizational one.

References:

Why I Started Building My Own DevOps Platform (And What I Learned)

Sat, 15 Feb 2025 09:00:00 +0000

For a while, I had the same reaction to most AI-for-software-delivery demos: impressive in a narrow way, but not something I would trust with real work. One tool could write code. Another could summarize a diff. Another could review a pull request. But the hard part of software delivery is rarely one isolated step. It is the handoff between steps.

That was the itch that eventually pushed me to start building CueMarshal.

I did not start with the ambition to build “an AI company” or some abstract autonomous future. I started because I wanted a more coherent delivery system: one place where a task could move from idea to issue to branch to pull request to review without losing context every time responsibility changed hands.

The problem I actually wanted to solve

CI/CD was never the whole problem. In many teams, the pipeline is the most deterministic part of the process. The mess usually lives around it:

the design decision that only exists in a chat thread
the issue that says too little
the reviewer who has to reconstruct intent from commit history
the documentation that is always “we’ll do it after”
the growing pile of tools that all know a little, but none of them own the workflow

What I wanted was not another dashboard. I wanted a delivery surface that respected how engineering work already happens.

That led me to a simple conviction: Git should be the source of truth, not just the storage layer.

If work already becomes legible through issues, branches, pull requests, labels, and reviews, then the orchestration layer should live there too. Not beside it. Not behind it. Inside it.

Why I built it myself

There were three constraints that mattered to me from day one.

First, I wanted the system to be self-hosted. A lot of AI tooling assumes you are comfortable sending your code, your process, and your delivery metadata into someone else’s black box. Many teams are not. I wanted an approach that made data sovereignty a feature, not an apology.

Second, I wanted the system to be role-aware. Real software delivery is not “one super-agent with a clever prompt.” Design, implementation, review, testing, DevOps, and documentation are different jobs. Sometimes one person does multiple jobs, but the jobs are still different. That distinction matters.

Third, I wanted human control to remain the final gate. I am interested in automation, not surrender. If an AI system cannot work inside a reviewable pull-request workflow, I do not think it is mature enough for serious engineering work.

Those constraints eventually turned into the shape CueMarshal has now: a conductor service in TypeScript, specialized agents for architecture, development, review, testing, DevOps, docs, and linting, a Git-native workflow in Gitea, and a tool layer built around MCP so the same system can reason over structured interfaces instead of raw shell scripts and ad-hoc API calls.

The architecture came later. The principles came first.

Long before the implementation solidified, the design principles were already obvious to me.

1. Git is a better coordination layer than most agent UIs

An issue is a task. A branch is a workstream. A pull request is a proposal. A review is a decision record. A merge is a controlled state change.

That sounds almost too obvious to say out loud, but it changed how I thought about the whole problem. Once I stopped treating Git as the place where code merely ends up, and started treating it as the place where engineering decisions become inspectable, the rest of the architecture got much simpler.

2. Specialization beats a “do everything” agent

In CueMarshal, the system is intentionally split into named roles: Marshal for orchestration, Ava for architecture, Dave for implementation, Reese for review, Tess for testing, Devin for DevOps, Dot for docs, and Linton for linting.

That is not branding for its own sake. It is an operational choice.

The moment one agent tries to be planner, coder, reviewer, tester, and documentarian all at once, you lose clarity. You also lose accountability. Specialization makes prompts sharper, tool permissions narrower, and outputs easier to judge.

3. Tool contracts matter more than prompt cleverness

One of the biggest lessons from building CueMarshal is that the quality of an agentic system is heavily constrained by the quality of its interfaces.

If an agent is forced to improvise around loosely structured APIs, fragile shell commands, or browser automation for tasks that should be typed and validated, the system becomes harder to trust. This is one reason MCP clicked for me so quickly later on: it gave a clean shape to something I already knew was essential.

Good tool contracts do not just help the model. They help the human operator understand what the system is even allowed to do.

4. Stateless workers are a feature, not a bug

CueMarshal’s runners are intentionally stateless. They reconstruct context from the repository, the issue, the pull request, and the tool layer every time.

That may sound less magical than the “persistent AI teammate” narrative, but it is much easier to reason about. It scales better. It fails more cleanly. And it produces a better audit trail.

In practice, that has made me more skeptical of systems that depend on hidden memory to feel smart.

5. Human control is product design

The more I worked on this, the more convinced I became that “human in the loop” is not enough as a slogan. It has to be built into the workflow itself.

That is why I prefer issue-driven execution, reviewable pull requests, typed tools, explicit handoffs, and merge control. Those are not bureaucratic constraints. They are the difference between a system that can support real engineering and a system that is only good for demos.

What I learned from building in public

The most useful part of this project has not been proving that agents can write code. We already knew that. The useful part has been learning where coordination breaks, where trust gets earned, and what kinds of structure make AI assistance actually usable.

It also made one thing clearer for me: the next layer of software delivery is not “more CI/CD.” It is better orchestration around the work humans and machines are already doing together.

That is the reason I started building CueMarshal, and it is still the reason I keep working on it.

If you want the more technical follow-up, I wrote about what MCP actually changed for developers and the coordination lessons from building an eight-agent engineering orchestra.

References: