alt Hacker NewsPeople who want to destroy you at work (which I imagine is rampant at Google) will sometimes prevent you from doing something, but they might also encourage you to do it in such a way that you fail spectacularly.
Some of my favorites from my career:
1. PM enticing me to "volunteer" to build a PoC over the weekend, to have it ready by Monday morning – come Monday, PoC is shipped live to all international customers. It was nowhere near prod ready, it was just to demo 1 thing.
Naturally, endless tickets open asking about missing functionality, and changes to the dashboard, "Nothing works!".
I'm in Slack talking to customer support like "Sorry I don't know why they launched it, it's not even close to being done". I've had nightmares about this kinda thing before, and then it happened lol. Anyway it was easy to paint the image that I'm just trash, biting off more than I can chew, can't let me near anything, and I got fired for it. They want back to maintenance mode.
It was a simple dashboard that looked great (for investors) and solved problems for customers, but there was no way the other guys on the team were going to let me launch that thing. Rather than stop it, they just "helped" get it out early. Project dead, they never built that.
2. And on the other end where I was stopped from launching something, I've had 2 devs go in league to say that code I was writing was a huge security risk (front-end React) and kept saying in meetings "Yeah I saw some things" without pointing out exactly what.
At some point one of them just irreversibly deletes all the branches related to it, live in standup, and puffs his chest "Yeah sorry guys we're not releasing this stuff, I'm worried about code quality" basically got him promoted to CTO.
So yeah I imagine politics and mind games happen all the time at Google, and it's probably very confusing what is or is not a good idea, what will work and will not work, because of the massive distraction of everyone backstabbing and preparing to backstab.
Replies
Yeah, it's way easier to argue that the product is a bad idea if they give you all the resources to build, release and grow it but there's just not enough customers showing up.
The alternative might be internal battles to kill it that take up time and energy and everybody can continue their argument forever.
> but they might also encourage you to do it in such a way that you fail spectacularly.
A skill one must develop is identifying no-win-scenario tasks that can be avoided. POCs are often such tasks.
A teammate and I got roped into some POC where everyone in the room seemed to silently agree the product was not fit for purpose. The meetings went in circles of seemingly trying to find anything they could do to use the product, rather than assessing it objectively on the use case the vendor pitched.
Behind the scenes it turned out the product was being pushed by someone seniors brother. So the thing was getting bought no matter what. What they were really looking for was the patsy to own finding any sort of use case for the stupid thing, integrating it and owning it.
Obviously a "the product cannot fail, it can only be failed" scenario. Run run run away.