4 ms·
I'm not sure how you reached this conclusion. The author writes, "Guido's talk describes many elements of what makes it scale...The second piece is an enforced
by nopal 17y ago
I'm not sure how you reached this conclusion.
The author writes, "Guido's talk describes many elements of what makes it scale...The second piece is an enforced policy of having every single patch go through a code review process before you check anything in...And beyond that you have people paying attention to best practices such as consistent style, good unit testing, so on and so forth. (All of which are reinforced in the code review process.)"
I think he makes it clear that the reason developing from HEAD has worked at Google is because they have lots of processes to ensure success.
- btilly 17y agoExactly. There is an entire package of tools and development process which, combined, makes things work out. The fact that you need an entire package, and the difficulty of adopting multiple simultaneous changes to change how you work is one of the primary reasons that I do not recommend that organizations all rush out and adopt Google's strategy. There really is an all or nothing thing here. As an illustration of the dragons that wait, what happens if someone adopts all of the tools and practices, but the product manager is still able to put real schedule pressure on developers. I guarantee that in the rush to finish features that anyone who holds up implementation with, "This code is crap and there is no way I'm approving it" will come under pressure to accept the crap code. And as soon as you cross that line, the entire strategy falls apart because, even though in theory you're following a good process, in practice you just lost a critical underpinning.