{"id":220,"date":"2026-07-26T02:02:37","date_gmt":"2026-07-26T02:02:37","guid":{"rendered":"https:\/\/platformdev.org\/?p=220"},"modified":"2026-07-26T02:06:36","modified_gmt":"2026-07-26T02:06:36","slug":"you-build-it-you-run-it-famous-advice-but-does-it-actually-work","status":"publish","type":"post","link":"https:\/\/platformdev.org\/index.php\/2026\/07\/26\/you-build-it-you-run-it-famous-advice-but-does-it-actually-work\/","title":{"rendered":"“You Build It, You Run It” \u2014 Famous Advice, But Does It Actually Work?"},"content":{"rendered":"\n

In 2006, AWS CTO Dr. Werner Vogels famously coined the phrase: “You build it, you run it.”<\/strong><\/p>\n\n\n\n

The philosophy was simple: software development teams should own the entire lifecycle of their applications\u2014from design and build, to deployment, monitoring, and 24\/7 operational support. By tying developers directly to the operational outcome of their software, teams are naturally incentivized to write more reliable, well-tested, and maintainable code.<\/p>\n\n\n\n

I appreciate the spirit of the endeavor, but in practice, it doesn’t work for every organization.<\/p>\n\n\n\n

The effectiveness of this model hinges entirely on team composition. Running an application autonomously requires more than just product feature developers. A team needs a Site Reliability Engineer (SRE) who understands monitoring, auto-scaling, and chaos engineering. They need expertise in Infrastructure as Code (IaC), cloud provider services, and zero-downtime deployment strategies. Without these specialized skills embedded directly within the team, true autonomy becomes an impossible expectation.<\/p>\n\n\n\n

Why It Fails<\/h2>\n\n\n\n

When organizations attempt “you build it, you run it” and fail, it usually comes down to excessive cognitive load<\/strong>.<\/p>\n\n\n\n

Expecting software engineers to be experts in app logic, Kubernetes, Terraform pipelines, IAM policies, and on-call incident response burns people out. While tech giants like Amazon, Netflix, and Google have the budget and talent density to staff fully cross-functional teams for every microservice, most companies do not. Forcing developers to manage complex cloud infrastructure leads to misconfigurations, security oversights, and less time actually building business features.<\/p>\n\n\n\n

The Alternatives<\/h2>\n\n\n\n

If forcing every dev team to manage their own cloud infrastructure isn’t scalable, what works instead?<\/p>\n\n\n\n

Platform Engineering (Paved Roads):<\/strong> Instead of making every team reinvent the deployment pipeline, a dedicated Platform Engineering team builds Internal Developer Platforms (IDPs). They create self-service primitives and automated guardrails. Developers still “run” their apps, but they interact with clean abstractions rather than raw infrastructure code.<\/p>\n\n\n\n

Embedded SRE Rotations:<\/strong> Rather than trying to hire an SRE for every single feature team, organizations can embed senior SREs into application teams on a rotating basis. The embedded SRE works alongside developers to establish monitoring, automate toil, and build resilience before rotating to the next critical service.<\/p>\n","protected":false},"excerpt":{"rendered":"

In 2006, AWS CTO Dr. Werner Vogels famously coined the phrase: “You build it, you run it.” The philosophy was simple: software development teams should own the entire lifecycle of their applications\u2014from design and build, to deployment, monitoring, and 24\/7 operational support. By tying developers directly to the operational outcome of their software, teams are […]<\/p>\n","protected":false},"author":1,"featured_media":430,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-container-style":"default","site-container-layout":"default","site-sidebar-layout":"default","site-transparent-header":"default","disable-article-header":"default","disable-site-header":"default","disable-site-footer":"default","disable-content-area-spacing":"default","footnotes":""},"categories":[1],"tags":[],"class_list":["post-220","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"_links":{"self":[{"href":"https:\/\/platformdev.org\/index.php\/wp-json\/wp\/v2\/posts\/220","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/platformdev.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/platformdev.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/platformdev.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/platformdev.org\/index.php\/wp-json\/wp\/v2\/comments?post=220"}],"version-history":[{"count":2,"href":"https:\/\/platformdev.org\/index.php\/wp-json\/wp\/v2\/posts\/220\/revisions"}],"predecessor-version":[{"id":429,"href":"https:\/\/platformdev.org\/index.php\/wp-json\/wp\/v2\/posts\/220\/revisions\/429"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/platformdev.org\/index.php\/wp-json\/wp\/v2\/media\/430"}],"wp:attachment":[{"href":"https:\/\/platformdev.org\/index.php\/wp-json\/wp\/v2\/media?parent=220"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/platformdev.org\/index.php\/wp-json\/wp\/v2\/categories?post=220"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/platformdev.org\/index.php\/wp-json\/wp\/v2\/tags?post=220"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}