Thread by @schrockn

1/ Last week @software_daily did a series of interviews on Facebook engineering that had interviews with myself, @dan_abramov , @floydophone , @jgoldfein, and @mvernal. This series will continue in spurts over the next few months.

2/ links:
- @floydophone: softwareengineeringdaily.com/2019/05/13/fac…
- @schrockn: softwareengineeringdaily.com/2019/05/14/fac…
- @jgoldfein: softwareengineeringdaily.com/2019/05/15/fac…
- @dan_abramov: softwareengineeringdaily.com/2019/05/16/fac…
- @mvernal: softwareengineeringdaily.com/2019/05/17/fac…

3/ This is @floydophone's brainchild. It's been an honor to work on this with him. Our general thesis is that while some of FBs open source technologies (e.g. React/GraphQL) have been very influential the engineering culture is less pervasive in tech sector.

4/ As ex-FBers have gone to other companies they have noticed that other folks make way different tradeoffs in terms of execution velocity, organizational cohesion, management practices, and other. We thought it would be valuable to flesh these out publicly.

5/ Note that we are talking about pure engineering execution and management, not the policies or the objectives of the business. To put it mildly, FB is controversial in the public sphere right now. And none of us speak for the company.

6/ Think of the series just like using React or something. Using React doesn't mean you support FB. Likewise, listening and learning from these podcasts doesn't mean you support FB. These practices and tradeoffs are orthogonal to policy.

7/ I'll be posting some of my own summaries commentary on these podcasts as these come out. I hope we can spur some discussion so we can get feedback and incorporate it into future interviews and written materials.

8/ Many many thanks to @the_prion of @software_daily for all the amazing work you've done. It's been a privilege to see your process work. It's really impressive. These turned out great.