The author argues that the term "operations" in software development has unfairly gained a negative connotation. They contend that operations should not be seen as synonymous with toil or inefficiency. Instead, the primary goal of operations is to ensure that systems run smoothly and effectively. The article criticizes the shift from traditional operations to various new models like DevOps and SRE, which the author believes has caused a misunderstanding of what operations truly entails. The piece references a previous article where the author claims the DevOps movement aimed for a single feedback loop between developers and production but ultimately failed due to inadequate technology. Comments from LinkedIn users highlight a common sentiment that developers should take full responsibility for the systems they create. However, the author pushes back against this notion, emphasizing that operations is crucial for maintaining system integrity and that both development and operations have distinct, complementary roles. The author highlights the complexity of operations, asserting that the toughest technical challenges often lie within infrastructure engineering rather than product development. They argue that operations engineers must consider resource management and cost-effectiveness in ways that product engineers do not. The piece suggests that while developers focus on building features for business growth, operations teams are essential for providing the reliable infrastructure that supports those initiatives.