The article's focus is on avoid brittle code. By updating your dependencies often, you will shake out accidental coupling or assumptions in your code. It might

The article's focus is on avoid brittle code. By updating your dependencies often, you will shake out accidental coupling or assumptions in your code. It might be expensive in the short time, but it will make future upgrades easier. For example, if you are on library version 2.1 you will have a harder time jumping to version 4.3 to get some headline-making security update. You also avoid time spent debugging bugs that may have been fixed in a newer version of one of your dependencies. That said, updating every week might be unnecessarily frequent. :)