• Counter point. I would wager people are more productive scrolling 5 minutes through a Facebook post then taking a 30 minute coffee break talking to various coworkers. I would hate this. Also if you’re a developer how would you research something? No stack overflow? No access to forums to solve particular problems? Not sure this is sustainable.

    • Losing access to language reference docs would be huge. What are they gonna do, save them all locally? Maintain copies of those sites on the company intranet, at the company’s expense? What happens when the next version of Python is released?

      This is a real cut the nose the spite the face move. Google would hemorrhage developers.

        • I mean let’s say they solve that part, sure. Let’s go back to Google’s original intent for this maneuver: they want to beef up “security.”

          Ars Technica’s sub-title line says “You can’t get hacked if you aren’t on the Internet.” That is utter nonsense. I’ll take “What is E-Mail?” for 500 Alex. Surely they wouldn’t block EMAIL right? How would they communicate with vendors, partners, governments, etc? Does Google think phishing emails, ransomware, etc don’t work if you don’t have internet access?

          • Actually, most email malware is staged now, so it wouldn’t work. PDFs with the malware embedded get flagged, so PDFs with a link to the malware replaced them. Even most ransomware is via an external link.

      • Why not? They already do for the vast majority of this stuff. It’s not that much and releases of these things are structured and indexed everywhere anyway.

      • Storing local copies of docs is a thing some companies do. I’ve worked at a couple of places that did that. And when the next version of $foo is released, and the devs get the go-ahead to use it, wget gets executed to make a new copy. Sucks, but that’s the threat model in some places.

        •  aksdb   ( @aksdb@feddit.de ) 
          link
          fedilink
          14
          edit-2
          11 months ago

          LLMs produce text. They don’t answer questions. If the probability of the keywords in the question are being used in correlation with the answer often enough, it might (re)produce the actual answer. But you can never be sure.

          LLMs are not a source for information.

  • Prepare for productivity to tumble lol switching tabs and keeping working is much more efficient than switching between your phone and your computer screen if you’re at a desk job. I guess I can understand why they want to do this but they better get a lot more lax with people being on phones, which I’m not gonna hold my breath on. Just more ways to shit on employees for other companies to emulate, love this capitalist innovation!

    •  Hirom   ( @Hirom@beehaw.org ) 
      link
      fedilink
      English
      1
      edit-2
      11 months ago

      I hope organisations invest in qubes os and other container/virtualization tools to make them more practical.

      Taking radical steps like cutting off internet would hurt productivity as much as it improve security.

  • Seems rather bizarre to me, though it could make sense for some non-technical roles. For developers, seems a bit impractical; much of language documentation is online and odd errors, common and esoteric, are frequently completely absent from docs. This seems likely to require devs to either use unauthorized devices or waste time digging through source (possibly for the programming language itself) to figure things out.

    However, the remark about root access makes me hope that there are not people logging into systems at Google as root. A sudoer, sure, but root is a big no-no.

    • Seems like they could have a machine with higher level access air gapped, and a less secure machine for browsing the internet but not internal tools. Would still suck for copy paste and things of the line, but would probably work in most cases.

      • I would think that this would be an approach that absolutely makes sense for corporate infra systems like domain servers, systems with access to network configs, etc.

        Maybe adding an additional security tier? Something like “sandbox dev” where new third-party libraries and technologies can be tested and a “production dev” which is more restricted. That might be the “right” way.

        The problem that I’d see is that productivity, development velocity, and release cadence would all take a nose-dive as software engineers have to continually repeat work, roughly doubling the real amount of work needed to release any piece of software. This would likely be seen as incompatible with modern business and customer expectations.