4 ms·

Completely agree, see it at companies like Google turning more and more into deep management chains. Some of the good remains (code & documentation transparency

• romwell 6y ago
  >Some of the good remains (code & documentation transparency) Not after the infamous need-to-know memo. Team docs visibility defaulted to "only to people I explicitly share with" for almost a year now. It's only a question of time until code branches follow suit.
  • ColFrancis 6y ago
    > Not after the infamous need-to-know memo. I couldn't find that memo, could you please link to a copy?
    • username90 6y ago
      It said that everything should only be shared on a need to know basis, basically ending the culture of all documents being open by default unless there is a need to hide it. When that change took into effect all documents I had were automatically set to hidden and I had to reshare them with everyone who needed to see them.
    • romwell 6y ago
      Here you go[1]. The audacity of that email was that it made accessing "need-to-know" documents internally (!!!) a fireable offense. In a kafkaesque move, "need-to-know" was not determined by labeling or access restrictions. Therefore, you can't know you are accessing a "need-to-know" document until you do. In short, this made using internal search engine fireable. It made clicking any link on the mail list fireable. That was a year and a half ago. [1]https://www.buzzfeednews.com/article/carolineodonovan/google-execs-internal-email-on-data-leak-policy-rattles https://www.buzzfeednews.com/article/carolineodonovan/google...