I'm not a spokesperson for the company and really don't feel comfortable saying anything specific about this.
Generically: Identity is a very hard space. It's one of those things that sounds really simple but the deeper you go the more edge cases you find.
With an complex systems, changing fundamental designs of the system- while users and other systems are currently using that system- is like trying to upgrade the engines on a plane while in flight. Technically possible, with a lot of planning, but any wrong move or bad assumption and you're going to crash.
It's an interesting topic. From my observation industry is divided. For well-paying companies there is an influx of candidates - these companies can be very picky and calibrate hiring process to get the best of the best. Whatever it means in FANG+ big tech context.
On the other side, there are plenty of small, medium, mediocre, old-school places and these companies have to fight for talent if they don't pay a top dollar.
Incorrect. I know several people working on Google projects as temps (with Google-provided laptops and @google.com domains) and with the code and technologies they're working with there is no way they can work without Homebrew. Maybe it's different for full-time employees but I doubt it.
Not OP, but Googler here. We use an internal Linux distro for all our development. It's very similar to Ubuntu (so the default package manager is apt). People who have a Macbook use it as a thin client to ssh into their Linux desktops. So OS X package manager isn't really needed or used.
The biggest cause of downtime was deployment. Either deploying code with a bug that wasn't caught in testing, or changing a real-time configuration parameter that wasn't properly scoped.
As opposed to a scaling issue that showed up later, or a node failure or all the other things that could cause downtime.
Looks like a queue worker issue. From eng:
"We're moving about 5000 events per second now. Definitely shrinking now, and memory usage is dropping too."
The original post was about Google and generally I’d say FB is indeed faster to hire and also faster to pip/fire than Google. Compared to Amazon and Netflix, probably not.
I was a manager at FB for a couple of years. Basically, my first official act as a manager was firing someone. From there, it was pretty much, "find one person on your team per year to fire."
It was an extremely high performing team, and even the less talented engineers were still very good.
