I think the title and parts of the article are misleading. Using volatile will never make a correct program incorrect. It cannot "break" a correct implementation.

It should not be overused, because as the article mentions it makes for slower and more confusing code, but it's not quite something to be afraid of either.

It is slower to use volatile, and bad form