Google API's latest semantic version is behind the doc site (godoc.org/google.golang.org/api). Is this standard practice in Go?
I was coincidentally converting my Go project to use Go modules yesterday. I depended on a Google API which was originally retrieved via 'Go get', corresponded to docs and worked fine as this pulled from HEAD. `go mod` did not work out of the box, as it required the latest semantic version (v.0.2.0) of my this Google API import. This version, however, is behind documentation and broke my code.
I understand I can require a specific commit in the go.mod file, but the strings for specific commit seem cryptic. Where can I look up the version hash that matches the doc site?
I remember our psychology 101 professor offering .1 GPA “extra credit” for every psychology study you went to. There was no way to get a 4.0 in that class unless you attended every class, answered every exam question correctly, every quiz question, etc.
In my experience, Google does this to some extent.
I’ve had great coworkers who didn’t go thru the traditional route.
Personally, Google hired me when I quit my first job out of college, before the one year mark, and was unemployed for a few months. It wasn’t a great look on my resume. The vast majority of companies didn’t give me the light of day. These weren’t top-tier companies, and I doubt they could have offered me the engineering experience or career growth as Google. Those same companies look to employment at FANG as signals of competence. 3 years later, they’re spamming my LinkedIn. One of these companies ask candidates for their SAT score and high school GPA.
This feels true in Manhattan, too, where most people here are affluent compared to the rest of the nation. However, in NYC, being average amongst the people doesn’t feel like a bad thing. That’s what I like about NYC anyways.
The network of drivers would be rendered obsolete by SDC