F8 2015 - Big Code: Developer Infrastructure at Facebook's Scale

I think the best part of this article was the small link to the F8 2015 "Big Code" video [0] where they go into detail about switching from Git to Mercurial, building their own IDE around Atom, and detailing their continuous integration process. It's a long video but it's very watchable using the YouTube speed multiplier. :) [0] [VIDEO]

All correct, but I don't think Bryan O'Sullivan does much haskell these days. He's the manager of some sort of "Developer productivity" team. The Hack programming language came out of his team [1] (tho he wrote a blog post to contrast all the media coverage and say "my people did it, not me! [2]); he spoke about his activity at the last F8 [3]. But he does teach Haskell at Facebook after work :) [4] [1] [LINK] [2] [LINK] [3] [VIDEO] [4] [LINK] EDIT: spelling

Facebook does this to scale their tests, you can hear Katie Coons talking about it in CI at the end of [VIDEO] . There are also rules that say "if you changed this file, run all tests" for things like CI config and such. Also, the build tool Buck ( [LINK] ) enables this because it knows the graph and associates tests with the code they test...so you even get this test minimization locally as a developer (that is, outside CI) for free. I'm sure Bazel likely has a similar feature too.

It's an internal system, but it was discussed at F8 last year. Here's the video ( [VIDEO] ) and someone's notes on it ( [LINK] ).