Whenever I have an issue with a Google Cloud service, whether it’s Firebase, Google Compute, or whatever else, I find myself on Stackoverflow looking at answers.

What at first I found strange and proactive, I’ve quickly realized is unhelpful and downright toxic. It would seem, at least on the outside, GCP has a policy that Stackoverflow questions regarding their service must be answered, so engineers will happily jump in and offer a piece of their mind.

In theory great. In practice, off of memory alone, here’s what I’ve seen happen instead:


  • Google engineers tell the user to get a reproducible case

What? That’s not what Stackoverflow is about.


  • Google engineers tell the user it’s a bug

I don’t care if it’s a bug, I’m looking for a solution


  • Google engineers spam the comment section asking if the user has found a solution yet

“Hey have you tried doing X?”

(2 days later) “Hey did X work for you?”

(3 days later) Posts solution suggesting X, even if you told them no repeatedly in the comments


And this one is the worst -

  • Google engineers say the service is not designed to support doing X, meanwhile two other SO users have found a solution to do X

I get why they might think they’re doing a service, but with very few exceptions, Google engineers are totally useless in the SO answers section. They seem to have no interest in actually helping you, and only an interest in looking like they’re trying to help you, and that’s a big difference. If you’re ever on Stackoverflow and notice someone has a highly upvoted, GCP related comment that isn’t actually useful, check their profile and see if they proudly boast to be a Google engineer.

And don’t feel bad giving them a downvote if it’s deserved.

  • @blank_sl8@lemmy.ml
    link
    fedilink
    52 years ago

    Google engineers tell the user to get a reproducible case

    That’s something you’re supposed to do for all stack overflow questions. Nobody, engineer or otherwise, can help you without being able to reproduce an issue.