A lot of times in this world, your software is going to need to be updated for a variety of different reasons. For one thing, the fact of the matter is that a lot of software is released before it is entirely done, or before a lot of its effects are fully known. After all, why would a manufacturer wait until the software is perfect (which will never really be able to happen) before they start to sell it? It is a whole lot better over the long term for them to just keep on patching it until they finally come out with an entirely new version… which will require patching itself.
Software updates are not generally the massive ordeals that they used to be. Ever since fast Internet took over the world, it is now a fairly simple process to simply allow your computer to update its software suites all on its own. And while it is not quite as romantic as sitting there swapping out disks like they did in the old days, it is a whole lot easier to just set it to update at a time when you are not going to be on, and let it work while you sleep.
Now there are going to be times when updating your software is not that great of an idea. One of those times is when you are working on a very sensitive project, and need to make sure that your software stays consistent throughout the process. While it is a rare occurrence, there have been times when a piece of software has been updated, and the process caused it to recognize files improperly and not be functional until it was fixed.