As Greg explains -
My own experience, [...], is that software development projects succeed when the key people on the team share a common vision, what Brooks calls “conceptual integrity.” This doesn’t arise from any particular methodology, and can happen in the absence of anything resembling a process.
Common vision (AKA the way we do things around here) is perhaps especially important, when your goal is to move fast and break things. And what better time to start than when on boarding a new engineer?
As Facebook's Joel Seligstein puts it -
I would describe it as a way for us to educate our engineers not only on how we code and how we do our systems, but also how to culturally think about how to attack challenges and how to meet people.
And as we briefly touched on before - a successful dev culture encompasses the entire process - all the way to deployment. For instance, in an older post, Greg talks about how to develop code which is impossible to maintain -
A key part of developing unmaintainable code (as per Greg), is to create a super elaborate build and deployment structure. As he puts it -
Programmers can argue about simplicity and elegance in code, and then turn around and build the most elaborate and baroque build and deployment systems.