News for hackers. Stuff that matters.
Re:Google’s in-house desktop Linux by mistrial9 on Monday August 01, 2022 @11:46AM (#32307711)
I gave a demo in Mountain View of some excellent viz, on their big screen in some room. I wanted to make some tiny change to (plug something in) edit no not a new device, being polite, I suggested to move a device of theirs already on that network, closer to the overhead projector .. the alarm, consternation and definite NO that rippled through the three quickly-relaying employees there, was literally like an electric current. I was amazed that they couldn't change even the smallest thing, ever.

of course I was trying to get my brilliant colleague without a degree, noticed with that code; zero response, like stonewall. Later I read, that year Google got over 1million job applications.

weird place

Re:Google’s in-house desktop Linux by dsl on Monday August 01, 2022 @02:01PM (#32309816)
> I suggested to move a device of theirs already on that network, closer to the overhead projector

What you didn't know is that it wouldn't work.

There is also an expectation that you don't just randomly start changing things in shared conference rooms. If there is an issue, you open a GUTS ticket and someone comes and solves the problem. Chances are if you discovered a real issue, there are 90 other rooms with the same issue that also would be updated.

Re:Google’s in-house desktop Linux by dekhn on Monday August 01, 2022 @02:08PM (#32309933)
What were you trying to connect? Connecting to an ethernet port wouldn't work as they use ethernet authentication. Connecting to the projector's input ports instead of using Meet to present? Certainly something I wouldn't have protested if somebody external was giving a demo, back when I worked there.
Re:Google’s in-house desktop Linux by lupire on Monday August 01, 2022 @12:28PM (#32308508)
What kind of change?