> "...removing features from your build isn't going to improve the features you keep." Taken literally, this statement is true, but either deliberately or acci

> "...removing features from your build isn't going to improve the features you keep." Taken literally, this statement is true, but either deliberately or accidentally, is hiding the reality that removing features can absolutely lead to improvements in remaining features. It reduces overall complexity with fewer points of failure due to less possible interactions. It frees up more time to devote to less features, so quality improves. Less features means improved focus. etc etc. > "This, and some other sentences, are gibberish. "DEVOPS" is not an operational model." https://en.wikipedia.org/wiki/Operating_model https://en.wikipedia.org/wiki/Operating_model Quoted from the wiki: "People, process and technology is one commonly used definition,[1] process, organization and technology is another, and [2] Process, Organization and people, Locations and buildings, Information systems, Suppliers and business partners, Management system yet another.[3]" DEVOPS falls clearly in the Process and Technology areas, as well as overlaps with People and Information Systems. Now one could argue exact relevance, but the OP's assertion that DEVOPS is an operational model is hardly gibberish, as in utterly lacking meaning or relevance.