Inner Loop & Outer Loop
Where an engineer's time actually goes, and which loop a platform investment shortens.
5 to work through
-
beginner Multiple choice
Two teams own the same test suite. Team A can run the relevant tests locally in 40 seconds. Team B's only way to run them is a 9-minute pipeline. Team B's pull requests are about four times larger and when a test fails they take far longer to work out which change caused it. What is the mechanism connecting feedback time to those two outcomes and which change helps most?
3 min answer -
intermediate
Developers cannot run the system locally — one service needs twelve dependencies. The inner loop is now "push and wait eight minutes". How do you fix it?
2 min answer -
intermediate
Engineers report that the platform is fine but daily development is slow. Where should a platform team invest?
2 min answer -
intermediate Multiple choice
Sixty engineers each wait for a build roughly 15 times a day. The build takes 4 minutes. Roughly what does that cost a year, and what does the number rule in or out?
2 min answer -
intermediate
What distinguishes the inner loop from the outer loop, and where should a platform invest?
2 min answer
3 terms in this topic
Inner Loop
The edit-build-test cycle a developer repeats dozens of times an hour, entirely on their own machine or environment.
metricInner Loop Latency
The time from changing a line to observing its effect, repeated dozens of times a day and therefore the highest-leverage number in developer experience.
conceptInner-Loop Multiplier
The reason inner-loop friction dominates developer productivity - the loop runs dozens of times a day, so a small duration difference multiplies into…
Neighbouring topics
Platform Engineering
General material on internal platforms as products with users, adoption and lifecycles.
Internal Developer Platform
The assembled surface teams actually touch, and what belongs behind it.
Paved Road & Golden Path
A supported default route that is easier than the alternatives rather than mandatory.
Self-Service Provisioning
Teams getting infrastructure without a ticket, and the guardrails that make that safe.
Service Templates
Scaffolding new services with observability, CI and security already wired in.
Platform APIs
Treating the platform's own interfaces as contracts with consumers and compatibility rules.
Platform Tenancy
Isolating teams sharing a cluster, account or pipeline fleet, and where isolation must be hard.
Cluster Architecture
How many clusters, split by what, and the blast radius each split buys.
Service Mesh Operations
What a mesh genuinely solves, its failure modes, and the cost of running one.
Container Image Strategy
Base images, layer hygiene, rebuild cadence, and patching a fleet of images.
Developer Environments
Local, remote and ephemeral environments, and the fidelity each can honestly claim.
Abstraction Level Choice
How much to hide, and the leak that turns a helpful abstraction into a trap.
Platform SLOs
Committing to reliability for internal consumers who cannot choose another provider.
Platform Adoption
Migrating existing teams onto a platform without a mandate, and reading the adoption curve.
Platform Funding
Central cost, showback, chargeback, and justifying a team that ships no customer feature.
Platform API Deprecation
Removing something dozens of internal teams depend on, on a timeline that holds.
Guardrails vs Gates
Preventing a class of mistake automatically versus stopping to ask a human.
Platform Telemetry
Instrumenting the platform itself: usage, friction, and where teams leave the paved road.
Platform Team Topologies
Stream-aligned, enabling, complicated-subsystem and platform teams, and their interactions.