3 ms·

It is laughable to put something working this badly into your "service" at all. I realize this was probably 'forced' on some engineers at Google, but I'd still

It is laughable to put something working this badly into your "service" at all. I realize this was probably 'forced' on some engineers at Google, but I'd still be embarrassed to say I've had a hand in this. A bit like being a supporting character in the worst movie of the year. At what point do you threaten to quit over being forced to ship crap like automatic scanning of people's private files? I am unable to empathize here at all.

friedturkey 5y ago
Unfortunately, past experience at Google is still seen as a good sign in job applications. I think we're at a point where gap years should be a better sign than a stint at that company.
- snovv_crash 5y ago
  Google's engineering is still top-notch. Their product management is what lets the company down.
  - jamjamjamjamjam 5y ago
    No it is not
  - bathtub365 5y ago
    Would building a broken copyright enforcement system fall under engineering or product management?
  - ohgodplsno 5y ago
    Google's engineering is, on average, passable. Thousands of brand new grads that have studied to pass 5 rounds of interviews and have no experience are only going to put out barely passable software. Hell, the very reason that Go is so simple is because, by Google's own admission, their sw devs can't be trusted with anything more complex. What you see coming out of Google that may look cool (when it's not a new chat app they'll kill in two years) has thousands of drones behind.
tyingq 5y ago
Just a guess, but it has the feel of a flawed source database of what's been copyrighted. Something like a source where if one file in a collection is actually copyrighted, the entire folder/files/collection is assumed to also be copyrighted. And then, each file then goes in a database with a hash, etc. That would account for this issue, and the earlier one where files with just a one/two/three digit number in them triggered the copyright hammer.
userbinator 5y ago
"I have a job, it pays me well." That's probably what the majority of employees think. Even the SJW types there don't seem to care about these things.

friedturkey 5y ago

Unfortunately, past experience at Google is still seen as a good sign in job applications. I think we're at a point where gap years should be a better sign than a stint at that company.

snovv_crash 5y ago
Google's engineering is still top-notch. Their product management is what lets the company down.
- jamjamjamjamjam 5y ago
  No it is not
- bathtub365 5y ago
  Would building a broken copyright enforcement system fall under engineering or product management?
- ohgodplsno 5y ago
  Google's engineering is, on average, passable. Thousands of brand new grads that have studied to pass 5 rounds of interviews and have no experience are only going to put out barely passable software. Hell, the very reason that Go is so simple is because, by Google's own admission, their sw devs can't be trusted with anything more complex. What you see coming out of Google that may look cool (when it's not a new chat app they'll kill in two years) has thousands of drones behind.

tyingq 5y ago

Just a guess, but it has the feel of a flawed source database of what's been copyrighted. Something like a source where if one file in a collection is actually copyrighted, the entire folder/files/collection is assumed to also be copyrighted. And then, each file then goes in a database with a hash, etc. That would account for this issue, and the earlier one where files with just a one/two/three digit number in them triggered the copyright hammer.

userbinator 5y ago

"I have a job, it pays me well." That's probably what the majority of employees think. Even the SJW types there don't seem to care about these things.