The concept of developer responsibility for full life cycle ownership is complex and depends on various factors such as organizational culture, size, and goals. While some organizations advocate for a "developer-as-owner" mindset, others believe that not every developer needs to be responsible for the full code-ship-run workflow. A middle ground exists where developers have enough understanding of the full life cycle to troubleshoot problems in their services, while SREs focus on infrastructure and core services to support the developer's primary goal: shipping software safely at speed. The idea is not an all-or-nothing question, but rather a spectrum where developers exist everywhere on it. Understanding the complexity of shipping and running code is crucial for delivering software safely at speed, and having some insight into infrastructure can be helpful in this regard.