The inner dev loop is the single developer workflow. A single developer should be able to set up and use an inner dev loop to code and test changes quickly.

Inner Dev Loop

The outer dev loop is everything else that happens leading up to release. This includes code merge, automated code review, test execution, deployment, <a href="https://www.getambassador.io/docs/argo/latest/concepts/canary/">controlled (canary) release </a>, and observation of results. The modern outer dev loop might include, for example, an automated CI/CD pipeline as part of a <a href="https://www.getambassador.io/docs/argo/latest/concepts/gitops/#what-is-gitops">GitOps workflow </a>and a <a href="https://www.getambassador.io/docs/argo/latest/concepts/cicd/">progressive delivery </a>strategy relying on automated canaries, i.e. to make the outer loop as fast, efficient and automated as possible.

Outer Dev Loop

A slow inner dev loop can negatively impact frontend and backend teams, delaying work on individual and team levels and slowing releases into production overall.For example:<ul><li>Frontend developers have to wait for previews of backend changes on a shared dev/staging environment and/or rely on mocks/stubs/virtual services when coding their application locally.</li><li>Backend developers have to wait for CI/CD to build and deploy their app to a target environment to verify that their code works correctly with cluster or cloud-based dependencies as well as to share their work to get feedback.</li></ul>

Slow Inner Loop

The developer experience and the inner dev loop How is the developer experience changing? The developer experience is the workflow a developer uses t…