HN user

litewulf

978 karma

hfwang@google.com or hsiufan@wejoinin.com

I think its pretty easy to figure out what I work on from those two ;)

Posts2
Comments461
View on HN

[I am a Cloud SQL-er, and worked on region expansion... among other things]

Cloud SQL has only been available in regions with at least three zones (since we believe that is the minimum to make sure we can maintain HA in the event of a single zone failure). asia-southeast1 currently only has two zones, when a third zone is launched, Cloud SQL will become available in that region.

[Cloud SQL person, SSL+connections is my jam]

When you say you couldn't get the root certs to work... what do you mean?

Cloud SQL automatically generates server certificates, and we offer UI+API for creating additional client certificates. The two should not share a root CA.

[I am a Googler and my team works on part of this]

You can connect to postgres from app engine standard... as long as its Java. See this doc https://cloud.google.com/appengine/docs/standard/java/cloud-...

And no, appengine standard is not a second class citizen. Hand-wave-ily, the connectivity path that flex uses works for postgres with minimal changes, but unfortunately some additional work is required to get appengine standard for other languages working for postgres. :(

How Google Hires 11 years ago

Was this for a software engineering role? I've never been asked this, and I'm pretty sure during interview training you are explicitly told not to ask those sorts of questions.

When I interviewed at Google 5 years ago they weren't using those brainteasers.

There are many posts online about the actual, CS-y questions that you can expect in a Google interview, I had just assumed that the mentions of brainteasers were merely urban legend.

If that is the case, then why do Asians underperformed compared to Whites? If affirmative action is meant to help underrepresented groups, shouldn't the overrepresented group be the one "taking the hit"?

Well, on iOS since the only real way to execute code is from their app store, its much harder to attack the client code. Android can not do so, so there needs to be defense in depth to protect against that.

On the bright side, its a bit easier on the device itself, as the package manager needs to copy the APK from the download location when installing, so by storing application resources outside of the APK, installs will be faster and less likely to fail.

Perhaps not all countries have equivalent suicide hotlines, and thus they would not get such a notice?

Its really interesting how I feel really good about this use of data, but feel much more uncomfortable with (for example) using location data to tell me where to go to get pizza.

I recall people panning the purchase of grandcentral because of the incredibly long delay between purchase and launch of Google Voice...

It is hard to tell what purpose a company is acquired for (talent, technology, marketshare...) and thus difficult to tell whether it was fruitful.

I do (but I'm not sure I can talk numbers.)

Honestly: I like that it means I don't have to muck around with configurations, the fact that downtime is out of my control is frustrating, but at the same time, if I were running things, there would be more downtime due to mistakes I/my fellow developers make. Datastore latency is something of a painpoint, but it was something we knew going in and designed a bit for, and it also helps quite a bit that we're very read heavy in the ways that appengine wants you to be.

My friends at wolfire ran the humble indie bundle (and lots of other stuff like their blog as well), and it does well. (documented at http://googleappengine.blogspot.com/2010/06/how-app-engine-s...)

Perhaps I don't want to learn two interfaces, so it is sometimes better to choose consistency over some sort of pure ideal.

Right, what I'm saying though is that people were willing to stick it out and fork instead of rewriting. I'm surprised a programmer would do that.