4 ms·

There are many cases where there is a desire not to have a company’s code base floating around on people’s laptops. For these folks remote development is a goo

There are many cases where there is a desire not to have a company’s code base floating around on people’s laptops. For these folks remote development is a good option. It mitigates the risk of losing intellectual property. My understanding is that much, if not all development at Google works like this. I don’t know their specific policy but a friend works on a similar project internally.

kyrra 8y ago
Google devs access the repo locally most of the time through a FUSE file mount. So the code is never written to local disk, but still accessible locally as far as you can tell. (The other ways of writing code aren't publicly mentioned yet in any talks or papers that I know of, so I'll leave that one alone) From the 2016 ACM paper. > Most developers access Piper through a system called Clients in the Cloud, or CitC, which consists of a cloud-based storage backend and a Linux-only FUSE file system. Developers see their workspaces as directories in the file system, including their changes overlaid on top of the full Piper repository https://m-cacm.acm.org/magazines/2016/7/204032-why-google-stores-billions-of-lines-of-code-in-a-single-repository/fulltext https://m-cacm.acm.org/magazines/2016/7/204032-why-google-st...