Readit NewsNever stay at a job where the culture is toxic. Even if the money is better. Nothing eats at the soul like being held down by feckless, petty careerists and control freaks.
I used to think startups would be one of the few places that actually gave a shit about being lean and efficient - but turns out that's only true if they're bootstrapped.
It always amazes how blatantly authoritarian these "woke" types are. I would not be surprised if the sole reason she wanted the identities of every consultant was to engage in some sort of witch-hunting and bigoteering[0]
[0] https://www.urbandictionary.com/define.php?term=Bigoteering
Since this is Google's side of the story its in their interest to use words that would imply she's overbearing, or otherwise unaccommodating
(for all I know she could be all of those things, but this narration isn't sufficient evidence to prove that)
I derive a great deal of happiness from nice things. I suspect I’m not alone, and that people like me are the reason that the whole human environment isn’t just a pile of half-arsed crap designed to facilitate only certain types of approved experiences. We notice the qualities of the things around us every single moment of the day, and they can bring us great joy (or the opposite).
Materialism is clearly not in vogue (and I suspect there is a moral dimension to this), but for some people it will make them far happier than trying to chase experiences. I suspect there are many natural materialists out there struggling to conform to the new societal norm that only the ephemeral can lead to psychological salvation, and that all desire for material riches is a sin.
While there might be a vocal minority here (and elsewhere) that scoff at material wealth, its pretty clear that society at large still measures status by your possessions.
People still seek out more luxurious cars, more gadgets, new fashions year after year without fail; evidenced by the unstoppable growth in those industries.
Even if people might say that material riches are a 'sin', they certainly are not behaving as such.
...but with that said: I'm glad I only worked in countries where work is properly regulated and "on call" means "I'm getting fucking paid every cent for each hour I _must_ answer that goddamn phone". Which in practice means there's no PagerDuty.
The unpaid on-call culture is bullshit. The company can either pay me or go fuck itself.
The policy states that only the Operations team gets paid on-call, because I guess in the old days they would be the expected to deal with production.
Fast forward to today, and the Operations folks are a small team managing 2 datacentres, and all on-call rotations between SREs and developers are considered unofficial and therefore not eligible to be paid.
One of our Sr. Managers tried to take this up the chain, but then got reprimanded for putting developers on-call.
It isn't the norm, and it isn't competitive. It's just more "always on" culture in the workplace - and that's not healthy. A company should understand workers need real breaks - and being on call is not a real break.
_You_ might not be on call for your code, but _somebody_ will be. Often some poor SRE/ops person that has absolutely no idea what the app is doing/or why it's failing in production.
Not being on-call makes engineers complicit. I've seen it all, known memory leaks shipped into production, apps where half the endpoints couldn't even be compiled, code dumping the production redis at 1AM ... and every time the pain just felt on deaf ears.
If your code is what wakes you up in the middle of the night, you have: - Incentive to fix/mitigate as soon as possible. - No blame game to play. Either the error was made by you, or someone on your team. It doesn't have to go up 3 rungs on the ladder then back down again.
I don't think the author was suggesting that everyone should always be on call, just that you _must_ be responsible for your own code in production
Everything is predictable with enough guesses.