optimusclimb

Live in Salt Lake City now. Blowing red lights is like a sport here it seems.

Apparently chat around the water cooler was the real source of all of their innovation. It’s worth $600 an hour.

This is why I knew how to be a frontend engineer at one point in life but never pursued it past the early 2000s.

The brainpower wasted on web layout is immense.

Many in America get life sentences for drug offenses.

This happened recently - https://www.npr.org/2021/04/22/989822872/supreme-court-rejec...

This does not feel like enough.

The ads on that site made me give up on the article.

> Speaking from my perspective as a prolific FAANG interviewer

That's interesting, and somewhat rankling - as both times I interviewed at the G in FAANG, not a single interviewer gave a nickel about any of my experience, or projects I had worked on.

It's such a joke that the keys to a golden line on your resume and a giant salary are gated by the luck of which 7 people get picked to grill you that day, how busy they currently are, and what their pet question is.

> The building was purchased, "refurbished" and the rent was reset to a very high number.

And if someone was willing to pay that number, then that's what the place was worth.

If their opinion of you is dependent upon that, that fact just might be worth its weight in gold.

This would be too heavily influenced by confounding factors.

For instance:

* Are the teams that use certain languages comprised of more experienced people?

* How mature is the company and project? I.e., a faster moving startup cutting more corners, where time was decided to be of the essence (rightly or wrongly) will likely produce more on call incidents than a slower, more established company that can takes its time

Additionally, the vast majority of startups I've worked for, and am aware of, will not file the paperwork to let you 83b. AND, if you bring it up, they will probably tell you politely they're not going to bring up your request to the board and go through all that hassle just to hire you.

This service was a godsend when I lived there, due to how abysmal Muni was. Sorry to hear it didn't work out for them.

Not with those income levels that get everyone talking.

... if you want to live in the Bay.

Emergency situations. "Sir, we found your wallet...", etc., etc.

> Why is the latest generation constantly trying to solve injustice with more injustice?

Why is this a generational thing?

Charge me money, for content. Ala NYTimes, WaPo, Wall Street Journal, etc.

Also, I'd say it's a false dichotomy of "monetize" vs. "use every dark pattern and brings-browsers-to-their-knees script".

Countless times I've clicked on a link/article, only to go through this crap, and/or have it bring my browser on a most recent generation iDevice to a crawl, and given up/closed. I'm still happy to look at ads on free content (and yes, every now and then, click on one), provided I can actually see them.

Since pretty much every engineer under the sun knows this experience sucks, how can we attribute this to anything other than the rise of MBAs running the show?

If you're an existing AppEngine standard user/customer, it's pretty likely that that means you will not be able to take advantage of PostgreSQL, as the new runtime does NOT give you access to a ton of their existing services that you are probably already using (such as datastore.)

Then they should update their docs.

It is not possible to access Postgres based CloudSQL from Python on AppEngine standard. See here:

https://cloud.google.com/sql/docs/postgres/connect-app-engin...

Note that only node and Java are listed under non-Flex.

I got burned by this and had to start over with MySQL.

It's "free" in the same sense that the food is.

> Indeed so, if judging in a reference frame of gross oversimplifications and dismissing importance of details.

I'll admit, re: IRC - yes, that's a stretch and ignores details. It's more that Slack managed to kick Hipchat's butt so thoroughly that really surprised me.

Hipchat took standard IRC, and added some interface fluff, youtube links, and emojis. They achieved great market footprint.

Then Slack starts up later - makes literally the same exact product, and manages to surpass, and eventually subsume Hipchat.

Crazy.

Why should there even be a "compromise"?

My employer gives me free health care. Should that be restricted so I have to spend my own dollars and not get the benefit of a group plan?

Should employers not be allowed to give a transit subsidy because it hurts Lyft/Uber?

Maybe tech companies should not be allowed to offer stock based compensation because it's unfair to other city residents who work jobs without such things.

Man - California, specifically the Valley, is completely off its rocker when it comes to policy making.

I really hope Amazon's new HQ helps pave the way to start de-centralizing the tech industry from that one, overcrowded, and increasingly almost hostile spot.

> That feels like a pretty strong leap to make from your complaint about using the term "reload" when "load" is better.

I never made that leap - you're saying that. I'm saying that GCP docs are all severely lacking in "how to" guides.

API references are not so helpful without an explanation of how you're intended to use them. So, the problem isn't that the function name is "reload()" instead of "load()" - it's that nowhere does it tell you the pattern is to instantiate the object you're interested in (in this case, a Blob), and then you must make a call to retrieve the data from the server before the data you're interested in will show up.

Additionally, my commentary was made after now using many different GCP services - this was just something recently in mind.

Thanks for the response. See my response to bduerst in this same thread - it was that page.

Also to be clear - I don't think this particular example I gave is the end of the world/egregious - I just used it as representative of the fact that the general pattern I've seen of the docs following where details are explained, but the "obvious" bits of simple usage are not discussed.

Was reading that page. What it specifically says is:

> The size of the blob or None if the blob’s resource has not been loaded from the server.

That's pretty vague imho, because there is no high level overview or tutorial to tell you that you need to explicitly cause the load from the server. Point in fact, the function you need to use is "reload()", and the documentation of this func is "Reload properties from Cloud Storage." To me, the "re" part makes it a bit of a misnomer - as it implies there would have been some sort of initial load in the first place (there is not.)

Imagine if the interface for going to a web page in chrome was: 1. Type the URL in the location bar. 2. Hit "refresh."

Had to use the cloud storage python API yesterday to retrieve the sizes of many blobs I have stored there.

First time using said API. Creating the client was straight forward enough...oh look, there is a section of the API docs on Blobs, cool - create a blob...and there's a size property.

And it has no data. Scan through ALL of the docs on the page...ahh, there's a "reload()" method, and sure enough, calling it retrieves the data.

Though...why doesn't constructing the object fetch the properties? And if it doesn't, why don't you just write some sentences somewhere telling people the general flow they should expect for how to interact with the API?

From my experience with all other GCloud docs, the answer is - because Google couldn't care less if their customers can figure out how to use their products. You write some minimal API docs on functions, MAYBE give one example of doing one specific activity, and then it should be OBVIOUS how to do the rest.

Having used both - would never, ever choose to use GCP over AWS if given the choice - and the main reason, aside from any technical differences - is that one company seems to care about what the experience of using their product is, and the other just doesn't.

Ditto that was an insta-close for me as well.