In the evolving world of software engineering, operational excellence is becoming the main focus. As coding becomes easier and more accessible, the real challenge lies in maintaining and running services over time. The author, Swizec Teller, argues that while many people can create quick demos, few want to deal with the ongoing demands of keeping a service operational. This shift indicates a rising demand for Site Reliability Engineers (SREs), who will play a crucial role in ensuring that software runs smoothly and reliably. Teller uses the example of Joe from accounting, who builds a no-code tool to automate a tedious task. Initially, this seems like a great solution, but as time passes, issues arise. Joe finds himself stuck with a system that he cannot easily hand off to others, struggles with constant updates, and feels overwhelmed by maintenance. This scenario illustrates the "computer disease," where tinkering with technology can lead to more problems than solutions. The author emphasizes that building a reliable service requires more than just writing code; it involves addressing numerous engineering challenges, like uptime, defect rates, and recovery from failures. Good software should be invisible to users, meaning it needs to work seamlessly in the background without constant attention. The article highlights that while the initial steps to create a functioning product may seem straightforward, the ongoing work to keep it running well is significantly more complex. In the end, the future of software engineering will prioritize those who can manage these long-term operational challenges effectively.