gonyea

The Hayward fault seems to have the most seismic activity lately. You'll feel them 2+ times a year in the East Bay--especially if you're in an older, multi-story building when it strikes.

Goal #1: Don't let the users "get screwed."

Goal #2: Don't have a solution that requires an army of people to manage.

If no one's willing to help fund your idea, you're out of luck. That seems... really understandable, given that every major government is literally investing millions trying to hack into Google's user data.

This all makes sense to me. If you're not providing enough value to users to cover the >$15k fee, you're just an attack vector for user data.

Consistency of the process aside, I'm really not sure what people would expect.

(I work at Google, yadda yadda, but have nothing to do with this.)

Google Maps is a travel powerhouse. Makes sense to have things in one place.

I’m traveling Europe right now and I live out of Google Maps.

This is an in-joke at Google.

I'm a Full-Stack developer at Google, which is fairly uncommon given the complexity of systems here.

The chief trait of a Full Stack developer, in my opinion, is often just growing into the needs of the team/moment. I've been weighted in different directions because that's where the product needed me; I'm currently the Front-End domain expert on my team.

Self-adulating thought leaders who throw shade at Full-Stack are themselves just really bad at using more than one language, let alone thinking about different parts of a large system.

(I'd also expect a Full-Stack developer to understand systems and resource provisioning/monitoring. Not just JS vs. Java.)

Uh, you realize that imap support has been in GMail for its entire history?

There are contractual obligations around changes to GSuite products (and their APIs).

On a related note: LED light bulbs often emit radio frequencies and all of the ones I’ve tried so far interfere with my garage door. Which was insanely hard to figure out.

(Garage door openers have spots for 2 light bulbs.)

Imagine you have ~billions of users and 99.9% of them use the default. Do you put your eng effort towards power-user flexibility for the tinfoil hat crowd or do you improve popular features?

In the case mentioned, searching "your locations" appears to be just all on or all off (I have no insider knowledge of Maps). That greatly reduces the surface area for heisenbugs in a high QPS system.

This is hilarious. Every single Google conspiracy is basically because some Google Engineer tried to DRY up functionality in an insanely complicated system.

China has a long history of imperialism. They even tried attacking Vietnam after its war with the US and failed.

In my experience, Developers who deviate from the norms are able to support themselves. Data Scientists are generally more dependent on support and infra from the rest of the org.

It's amazing that Apple seems to be holding on to their grudge against Nvidia... to their own detriment.

You haven't been able to buy a Mac/Macbook Pro with an Nvidia chip for many years now, and using one in an external enclosure is iffy. So data scientists are increasingly using Linux to do their work.