I doubt the person you're replying to works at google. His profile says he is a ruby developer and as far as I know we don't use that. Also, his attitude is not particularly common within google.
I didn't mean to imply that I think he works for Google.
>Also, his attitude is not particularly common within google.
So the majority of Google engineers disagree with the policies of the management? Do people internally push back against this stuff (trying to force account consolidation and making everything part of G+), or are people too afraid to speak out? If people aren't happy with it, how far does it have to go before morale drops and people start looking for other jobs?
Google is a big place and there's lots going on, both good and bad. There is lively internal debate and plenty of pushback, but there are also good reasons to stay even when you disagree about a particular issue. There are people who leave, but someone who's unhappy might just switch to a different team.
Brian said it better than I could. We can disagree with parts of organizational policy while still being happy with the whole. This is not unique to Google or even to employers. Any large organization will have things you don't like.
Also, I guess what I was really getting at is that I don't think the attitude is that cavalier in any case. People recognize that having to adopt a new API when we close a product sucks. But that is not the only consideration when deciding whether to continue. That's probably about as much as I can say while remaining vague enough to satisfy my conscience on the point of confidentiality.
