3 ms·

I've never even worked at Google, but if my team is working towards something and our announcement is pre-empted, yeah, I'm going to be upset. I would never wi

I've never even worked at Google, but if my team is working towards something and our announcement is pre-empted, yeah, I'm going to be upset. I would never wish anyone dead over it, but I would definitely be pissed at them. There's a lot of work that goes into those announcements. It's not just advertising the product that is the goal, it's presenting it their way. Similarly, when someone is telling a joke and someone else tells the punchline, they get upset about it. According to your logic, they shouldn't. The joke was told, and the audience heard it. But I've yet to meet anyone who wouldn't be upset about someone else telling the punchline to their joke. They were not brainwashed. You were incredibly insensitive to their feelings.

amelius 5y ago
As an engineer you should be focused on delivering objective value, not subjective value.
- UncleMeat 5y ago
  As an engineer my ultimate goal is to help people, not push metrics. The subjective value is the thing that matters.
greatgib 5y ago
If you are an engineer working on the software, the announcement really has little interest. You just want it to be wide and sure not being done in a way that put a bad light on your product. This kind of things happened in my case, and I was more happy to see the interest of the potential users than knowing who disclosed it as it would not be me anyway in all cases. It might not be true in a small company/team/product. But in a big tech corps, the guy that will do the official announcement is usually quite far and unrelated to the engineers that did the feature. Also, maybe a piece that was missing from my story is that the Googlers were not even in a team working or related to the disclosed thing. For example they were in the chrome team and it was an Android announcement or something like that. Another point is that, at Google, it looks like that each big product team is firewalled from the other team. For example, people not working on Android core will not know anything about it or it's development and be in separated buildings and co.
- mostdataisnice 5y ago
  This is just completely false - if you're working on a feature, you want a PR splash controlled by you, not a stream of silent leaks. PR begets other PR. You're being super presumptuous by saying engineers shouldn't care about the PR around the feature they worked on, even if someone else is running the PR
  - greatgib 5y ago
    If it was silent leaks, no one would have even cared about it!

amelius 5y ago

As an engineer you should be focused on delivering objective value, not subjective value.

UncleMeat 5y ago
As an engineer my ultimate goal is to help people, not push metrics. The subjective value is the thing that matters.

greatgib 5y ago

If you are an engineer working on the software, the announcement really has little interest. You just want it to be wide and sure not being done in a way that put a bad light on your product. This kind of things happened in my case, and I was more happy to see the interest of the potential users than knowing who disclosed it as it would not be me anyway in all cases. It might not be true in a small company/team/product. But in a big tech corps, the guy that will do the official announcement is usually quite far and unrelated to the engineers that did the feature. Also, maybe a piece that was missing from my story is that the Googlers were not even in a team working or related to the disclosed thing. For example they were in the chrome team and it was an Android announcement or something like that. Another point is that, at Google, it looks like that each big product team is firewalled from the other team. For example, people not working on Android core will not know anything about it or it's development and be in separated buildings and co.

mostdataisnice 5y ago
This is just completely false - if you're working on a feature, you want a PR splash controlled by you, not a stream of silent leaks. PR begets other PR. You're being super presumptuous by saying engineers shouldn't care about the PR around the feature they worked on, even if someone else is running the PR
- greatgib 5y ago
  If it was silent leaks, no one would have even cared about it!