[matt_o]

This idea was completely alien to me until I experienced it first hand. The F in FAANG puts emphasis on putting things like weekly/monthly status reports, incident investigation (even minor ones), and other useful information into 100-500 word posts. This has created a wealth of historical documentation about projects and problems that always helped me debug problems. What's more, it made discussing plans easier because participants had hours/days to think things through and shape them into paragraphs.

I've heard that Stripe and Amazon have writing coded into their cultures as well. I wish I knew more companies that did this because it's absolutely a different level of communication that helps ease so much friction (at a small price of reading/writing).