4 ms·
Most Googler SWEs have Mac laptops, not linux or windows laptops. But only a fraction of them use brew to install additional software. I'd love to interview t
by dekhn 6y ago
Most Googler SWEs have Mac laptops, not linux or windows laptops. But only a fraction of them use brew to install additional software.
I'd love to interview the creator of homebrew. There are so many dependency and reliabiltiy questions that it's clear brew doesn't handle well (same criticism of CPAN, and pip to some degree) in terms of performance or correctness that you could just talk for an hour about graph problems... who knows, something like... inverting a binary tree?
- chrisseaton 6y agoHow does Google develop software? Someone told me they did all their development in the cloud and you aren't allowed to check out software locally? Does that mean they just use their macs as thin terminals? But what's running in the cloud for development then? Linux X desktops, or do you edit in a browser, or do you develop entirely in a console over SSH? Nobody seems to talk about the developer experience at Google that I've seen, despite how much they talk about how they do operations and site reliability.
- dekhn 6y agoIt depends. Many googlers work on the centralized google3 source tree where the source lives in the cloud and your workstation is mostly a frontend for editing a FUSE view (citc): https://cacm.acm.org/magazines/2016/7/204032-why-google-stores-billions-of-lines-of-code-in-a-single-repository/fulltext https://cacm.acm.org/magazines/2016/7/204032-why-google-stor... among other documentation gives some details on the process. Typically that work will be done on a workstation at your desktop. But if you want to work remotely, and you can't access citc from your laptop. So, you'd ssh into your workstation, or use Chrome Remote Desktop (personally, I ssh from a ChromeOS laptop to a glinux workstation with tmux). Others use CRD for a full remote desktop. At that point the dev experience is mostly what like other people experience, except that the source and build and test environments are in the cloud, rather than on your local machine. That just describes one common case- devs and researchers writing stuff that runs on Google's internal resource management system, borg. There are many other teams, who have their own standards and approaches, which don't use the technology I described abvove. I'm sure there are plenty of devs at Google who actually build directly on their laptop, and commit code to open source repos without ever touching citc, or google3. For me at least, the dev experience at Google feels like every other dev job I've had: ssh to a LINUX machine, write code, compile it, run tests, send it for review, submit. A lot of people who are C++ server developers and python client developers could drop into the Google environment and quickly be productive. A lot of this is documented in external talks but it takes a ton of work to assemble all of it.
- CydeWeys 6y agoGooglers tend to use their Mac laptops as glorified remote desktop terminals, because they aren't allowed to so much as check out code to portable computers that can leave the office. It's a running joke that $2k top-of-the-line Apple laptops are being used as remote desktop terminals when much cheaper hardware would be perfectly sufficient.
- dekhn 6y agoI replaced my MacBook Pro with a Google Pixelbook since indeed my work is all remote and I don't really like MacBooks. I've previously tried high end Dell laptop (the most amazing laptop I've ever used, it had a high end nvidia GPU and you could train models on an airplane) and ended up with this device. I wish it was slightly larger with better specs and more ports, only because I spend a lot of time in video chat and there isn't enough CPU oomph to do video chat and Google docs on an external display.