Google crackdown catches innocent devs in the crossfire

Re:Google crackdown catches innocent devs in the crossfire by glimcat on Friday August 03, 2012 @09:22AM (#4333858)

I had to can a project recently after spending over a month fruitlessly trying to get a response from Google's support resources.

On the up side, I made $70 and learned some interesting stuff.

But here's yet another way for Google to run false positives which send you into their black hole of non-support. So one of the things I'm still learning is "don't let Google be a mission-critical part of a project."

[ Parent | on HN ]

Re:Google crackdown catches innocent devs in the crossfire by DanBC on Friday August 03, 2012 @11:56AM (#4334534)

> "don't let Google be a mission-critical part of a project."

This can be expanded to "Don't let any single company be a mission critical part of a project".

[ Parent | on HN ]

Re:Google crackdown catches innocent devs in the crossfire by ansgri on Saturday August 04, 2012 @09:18AM (#4338382)

Better yet, "Don't let anything over what you have no control whatsoever be a mission critical part of a project". If that single company can be heavily influenced by you, risks are acceptable.

[ Parent | on HN ]