Re:Why you absolutely MUST write an API when you write your ...
by JoelSutherland on Tuesday November 23, 2010 @10:11AM
(#1933903)
Wow -- hey Nolan!
We have the same experience (at a much smaller scale!). We can pull down production sites into a VM to see what happens whenever we make an API improvement. It is a great way to catch subtler things too like performance changes.
We do the exact same thing at Flickr. Anytime the front-end needs an method to do something, we'll build it in (though it may not always make its way into our public API).
The nice thing is if we change the behavior of an API method inadvertently, we catch it instantly since the site itself reveals the bugs.