|
|
|
|
|
by takeitto
2959 days ago
|
|
It is just not a good idea to authenticate yourself as a Googler in these sorts of discussions. If there is doubt in the media about a tech from Google, Google's PR department is more than capable to handle that in due time. I think part of this guideline applies, and following it should avoid disclosure, embarrassment, or being forced to speak on the defensive of an entire company (not a job that most developers are automatically good at). > You probably know that our policy is to be extremely careful about disclosing confidential proprietary information. Consistent with that, you should also ensure your outside communications (including online and social media posts) do not disclose confidential proprietary information or represent (or otherwise give the impression) that you are speaking on behalf of Google unless you’re authorized to do so by the company. The same applies to communications with the press. Finally, check with your manager and Corporate Communications before accepting any public speaking engagement on behalf of the company. In general, before making any external communication or disclosure, you should consult our Employee Communications Policy and our Communications and Disclosure Policy. While a compiler may block you from writing faulty code, the media will just take your faults, and then present them as truths coming from upper management. |
|