I totally see your point here. On the other hand, I left Philly in 2014 after getting laid off from a remote job. I could not get a job in town that utilized my skill set and paid me enough to maintain my family's costs.
From my perspective, there were only 2 games in town for people with specialized tech skills - Penn or Comcast. I'm sure that's not entirely true. But that's what it looked like to me.
The only place I could get hired (and maintain income) - Google. But Google doesn't do remote work, so here I am in the Bay Area. If Amazon comes to Philly, short term there will be costs if the city doesn't negotiate things properly. But long term, Amazon being here will mean other tech companies will come to poach labor. It's what happens in Seattle, Boston, the Bay Area in general.
Before IAM, the issue I had with service accounts is that I forgot to give the account Edit permissions. It seems the new way is like how @i_have_to_speak mentioned to use service account for an instance, which can only be done during creation of the instance, if you don't want to distribute keys. Then the newest way, that's still in beta, is to use IAM roles to further restrict the access scopes of that instance service account.
Yes, of course they're correct; however, invoking gcloud is comparatively much slower than just curl'ing against the metadata server (you know, no Python code to interpret in the latter case).
With regards to JSON, not sure what you mean, since getting e.g. instance zone from metadata server gives you a plain text string like "projects/<PROJECT_NUMBER>/zones/europe-west1-d". AFAIK, the only way to get JSON-like results is by making recursive requests, such as:
From my perspective, there were only 2 games in town for people with specialized tech skills - Penn or Comcast. I'm sure that's not entirely true. But that's what it looked like to me.
The only place I could get hired (and maintain income) - Google. But Google doesn't do remote work, so here I am in the Bay Area. If Amazon comes to Philly, short term there will be costs if the city doesn't negotiate things properly. But long term, Amazon being here will mean other tech companies will come to poach labor. It's what happens in Seattle, Boston, the Bay Area in general.