> This article makes a lot of assumptions that only hold true in a very specific set of circumstances: Yes. The assumption that you are working on a web based

> This article makes a lot of assumptions that only hold true in a very specific set of circumstances: Yes. The assumption that you are working on a web based service is so core to this piece that it doesn't seem any more necessary to say "this doesn't work for desktop" than it would be to say "this doesn't work without internet". given that you are delivering software on the web, your customers are going to get changes to it and like it, because their other option is to run systems on the internet with known exploits. Customers who don't want changes host their own instance. And if your next release is a year away and you have no way to roll back the release, but you have no manual validation - then you aren't following this advice to begin with, and you have an appallingly broken process.