Think 'Step Mother' to her husband's daughter. This would explain why she wasn't the one rushing to denver and rather made it so the father could make it.
It seems to me that, as Twitter goes the monetization route, these kind of changes only make more sense. They could have taken the option to charge developers for accessing their API's. But that would slow innovation.
So, it was only natural that they would look to create a larger piece of the pie for themselves while also trying to make it possible for developers to continue to be successful. Yes, that means that we, the developers, are now being forced to compete with them which seems like a non-starter. However, they are still providing an API for us to use which allows us to continue to compete.
In the end, dare I say it, they become Microsoftian in their API evolution; they use the API without releasing it to us and develop such a headstart that it is impossible for us to compete when the API is made public. If that happens, oh well. It was free and fun while it lasted.
The other possible point is that your employees shouldn't be allowed to report problems to companies that might actually hire them :)
Congrats to Aaron. I agree with hartor. Aaron worked to be the best sysadmin that he could be and when the opportunity presented itself to work at google, he was qualified to do so; both in motivation and skill.
