OneMoreGoogler

6 ms·

1.
by OneMoreGoogler 5y ago
Ha, busted.
2.
by OneMoreGoogler 5y ago
It was in the Android repo, which used Gerrit. I never dealt with readability, because Android did not require it. In fact that was part of their internal recruiting pitch: fed up with readability? Come work on Android! Heh.
3.
by OneMoreGoogler 5y ago
I worked at Google circa 2015, and found the code review process to be actively terrible. I was writing JS, while my sole teammate was a firmware engineer. He was not willing or able to meaningfully review my code, so I had to try to scroun
4.
by OneMoreGoogler 7y ago
During my time there, the internal Android repo required VP approval to access. Though I understand this was relaxed later.
5.
by OneMoreGoogler 7y ago
Over 16 years I've worked at only four companies, but one of them was Google, and it was honestly my least favorite. Creature comforts: I have an actual cubicle with >2x the space. Excellent meals are still provided, but now lines a
6.
by OneMoreGoogler 7y ago
You know Google's monorepo is successful because they have so many of them! google3, Android, Chrome browser, ChromeOS... Kidding aside, my point is Google recognizes obvious boundaries between e.g. their web stuff and android, and org
7.
by OneMoreGoogler 7y ago
I agree, it's between useful and harmless. But who considered someone taking a piss and thought "that time could be better utilized?"
8.
by OneMoreGoogler 7y ago
Example: my whole building was working in the android repo, but the ToT article would be about some tool for google3 (web) development.
9.
by OneMoreGoogler 7y ago
I saw these during my 18 months at Google. They were never relevant to my work. Working at Google you are bombarded with "nudges." The garbage cans have stop smoking signs. The plentiful candy is famously placed into jars to reduc
10.
by OneMoreGoogler 9y ago
Honestly it's the opposite. The way you get noticed and promoted at Google is by building something new, even if Google is already doing something else in that space. That's part of the reason there's so much duplication at G
11.
by OneMoreGoogler 10y ago
I got overchurned.
12.
by OneMoreGoogler 10y ago
Can you quantify that? Honest question - Android does not seem like a small project to me, but perhaps it really is dwarfed by Google's web services. What you wrote reminded me of a feeling I had: that these projects are these weird ex
13.
by OneMoreGoogler 10y ago
Checkouts are apparently instantaneous. Behind the scenes, there is a FUSE filesystem that faults in files by querying Google's cloud servers. So it does not require a significant amount of space (but does require fast access to Google
14.
by OneMoreGoogler 10y ago
During my 16 month tenure in Google, I worked on: 1. Android, using shell and Make 2. ChromeOS, using Portage 3. Chrome browser, using Ninja 4. google3 (aka "the monorepo") officially using blaze (but often there were nested build
15.
by OneMoreGoogler 11y ago
> It showed that the effective tax rate paid by those Americans jumped in 2013 to nearly 23 percent. As a data point, my family paid 28% average federal tax, on AGI of $355k. We are California residents. Taxes are regressive on the highe
16.
by OneMoreGoogler 11y ago
Speaking as a former member of more than one low-performing team at Google, none of the exercises would have helped our performance very much. What would have helped: 1. Being co-located. We would have been more effective sitting and worki
17.
by OneMoreGoogler 11y ago
> Any engineer can build any Google product from source on any machine A little too optimistic :) You can't build Android, Chrome, ChromeOS, iOS apps, etc. via blaze.
18.
by OneMoreGoogler 12y ago
No, not TBR. I was referring to the fact that you can +2 your own CL, which allows it to be merged. Officially this is an "emergency" feature, as you say, but a dirty secret is that it's used routinely. I encountered it in bo
19.
by OneMoreGoogler 12y ago
You can self-review. That's how people solve the problem.
20.
by OneMoreGoogler 12y ago
The smartphone requires awkwardly peering at a glass rectangle, yet it effortlessly reorganized social norms, because it's so damn useful and interesting. So why didn't Glass do the same thing? > I found that it was not very us
21.
by OneMoreGoogler 12y ago
Google HQ is officially a "dog friendly" campus, and dogs are welcome in the engineering offices, where some bark. Some owners respond by taking their dogs outside immediately, but others just shush their pet, which of course resu
22.
by OneMoreGoogler 12y ago
I am in a room full of people, none of whom are working on anything related to what I'm doing. The idea that my seating will help "foster collaboration" is ludicrous. It's all about maximizing the number of warm bodies p
23.
by OneMoreGoogler 12y ago
I am a SWE for Google and my area is super noisy. Construction, dogs barking (on our floor), phone calls, etc. My job requires me to work with a lot of PCBs, so I have to stay at my desk; I can't exactly curl up somewhere quiet. I hate
24.
by OneMoreGoogler 12y ago
During my one year at Google, the problem with the most complaints by far on memegen is Android L's "safety lock," requiring an extra swipe up before entering the unlock code. This is an edict from the design team, which engi