There's a huge difference between employees being able to see our source repository, and employees being able to see user data or secrets. Generally, Google val

There's a huge difference between employees being able to see our source repository, and employees being able to see user data or secrets. Generally, Google values its openness internally, and most employees can see the source code of most projects. In fact, that's how large scale refactorings and bug fixes work: I find a bug, I might have to fix the library in question, but also find all callers in the entire code base and fix them as well. In general, when I develop, I virtually have all of Google's code base 'checked out' and can edit any of millions of files in my snapshot of the world. I don't need to check out multiple silo'ed repositories or beg for access, diving into any code in the universe has almost zero transactional overhead, it's all mapped into one giant filesystem. (https://plus.google.com/+MattUebel/posts/4dQBDF5CmdX https://plus.google.com/+MattUebel/posts/4dQBDF5CmdX) On the other hand, production systems are heavily walled off from the corporate network. For all intents and purposes, the corp network your desktop is plugged into is "untrusted" Nice try though.