There is a lot of content out there regarding high-quality source code to write maintainable and clean code. This is not what I am looking for.<p>Every now and then, I read answers from Ex-Google Engineers on questions like "How is it like to be out of Google? What do you miss in the industry?". Often they say "the quality of source code".<p>I am curious: What is that special to the source code inside Google? What makes them "high quality"?
Is it a well-commented code base? That people with less context get a grasp of what the piece of code is doing? Is it a strict following of company-wide coding guidelines? Is it the tooling around that supports the maintenance of the quality?<p>I am curious to hear answers from people who have experienced the code inside Google. And maybe have concrete examples?<p>Thanks all.
Go to <a href="https://github.com/google" rel="nofollow">https://github.com/google</a>, but sort by language:<p>- C: <a href="https://github.com/google?q=&type=&language=c" rel="nofollow">https://github.com/google?q=&type=&language=c</a><p>- C++: <a href="https://github.com/google?q=&type=&language=c%2B%2B" rel="nofollow">https://github.com/google?q=&type=&language=c%2B%2B</a><p>- Go: <a href="https://github.com/google?q=&type=&language=go" rel="nofollow">https://github.com/google?q=&type=&language=go</a><p>- Java: <a href="https://github.com/google?q=&type=&language=java" rel="nofollow">https://github.com/google?q=&type=&language=java</a><p>Google's style guides: <a href="https://google.github.io/styleguide/" rel="nofollow">https://google.github.io/styleguide/</a><p>Hand-picked: <a href="https://source.chromium.org/chromium" rel="nofollow">https://source.chromium.org/chromium</a>, <a href="https://android.googlesource.com/" rel="nofollow">https://android.googlesource.com/</a>, <a href="https://fuchsia.googlesource.com/" rel="nofollow">https://fuchsia.googlesource.com/</a><p>Filter by subject: <a href="https://opensource.google/projects/explore/featured" rel="nofollow">https://opensource.google/projects/explore/featured</a><p>Also you can do the same for <a href="https://github.com/microsoft" rel="nofollow">https://github.com/microsoft</a> and <a href="https://github.com/facebook" rel="nofollow">https://github.com/facebook</a>
See for yourself :)
<a href="https://github.com/golang/go" rel="nofollow">https://github.com/golang/go</a><p>This is a good example file:<p><a href="https://github.com/golang/go/blob/master/src/crypto/crypto.go" rel="nofollow">https://github.com/golang/go/blob/master/src/crypto/crypto.g...</a>
I think it says a lot more about how strict the readability standards are for submitting stuff to corp/production. Even code written by a moron by me looks decent after code review.
Find out for yourself by studying Cromium's, TensorFlow's or V8's source code. It's all available online. Most of the code for Android is too.