Actually, we had 24 hours to change our code to adapt to the API change, and we were able to handle it quickly before it became a problem, we didn't end up with any duplicate tweets. The point of the article is that anybody who didn't see the announcement in time didn't really have a chance. It's a public API, there's a reasonable expectation here that a bit more notice would be given to such a change.