anonygler

19 ms·

151.
by anonygler 7y ago
At Google, there are too many complex systems and too many team dependencies to break tasks down into granular chunks, or to shoot from the hip in a pair programming session. Google runs on design docs. You define the problem, dependencies,
152.
by anonygler 7y ago
This article sums up modern medicine, and tech, rather well. Let’s boil things down to common molecules, rather than viewing the world as holistic. Your body needs food. Not soylent with a “cancer beating booster pack.” Eating Kale, Spinach
153.
by anonygler 7y ago
Almost every sponsored project has internal discussions. Many sync from the internal source control to GitHub. Is it really realistic to make every chat with a colleague into a formal, public RFC?
154.
by anonygler 7y ago
This is overly snarky and should be closed for that alone. Google funded its development. OSS projects do this. React has Copyright Facebook, yet I don’t see snarky PRs about scrubbing their name. Maybe Google’s logo shouldn’t be colorful?
155.
by anonygler 7y ago
As an employee I can opt into having my Home recordings reviewed to improve quality. I’ve never heard about this being done for regular users.
156.
by anonygler 7y ago
This basically sums up Google’s internal activists. They’re culturally ignorant and always on the lookout for new forms of outrage. The white activists effectively shouted down Chinese employees on the topic of a Chinese Search engine.
157.
by anonygler 7y ago
The most impressive part about Google is how its emphasis on internal standards has allowed it to build some really impressive stuff. Eg, You can do a sql join on any dataset, in any datacenter. You can turn any query into a hosted visualiz
158.
by anonygler 7y ago
Except that dude boasted about leaking internal conversations. That’s a firin’.