Yes, of course, the individual employees know. But the decision making for these kinds of things is usually a full-time middle manager, who isn't deciding on behalf of Google as a whole, but on behalf of their organization within Google (could be 50 people, could be 2000). It's not just _not_ that manager's job to make the globally optimal decision for Google, it's actually likely often in direct conflict with their job, which is basically "set the priorities of your org such that they launch things that make your boss look good to his boss". Spending headcount on maintaining niche stuff is usually not that (and takes resources away from whatever is).
How can anyone here confirm that's true, though?
This reads to me like just another AI story where the user already is lost in the sycophant psychosis and actually believes they are getting relevant feedback out of it.
For all I know, the AI was just overly confirming as usual.
What's your git workflow for a change that depends on two other in flight changes? (More generally, of course, this can occur in an arbitrary part of one's change graph - which is usually not too deep, but at least in my experience, occasionally is.)
Having good tooling for this unlocked workflows I didn't know I was missing, and switching back to git when leaving Google felt like losing a limb.
That's simply not how employment works.
Society needs to change and we need to incentivize it.
Seems to be working!
I'm not fighting for a split/fork, just stating the fact that it's nothing compared to Erlang.
I didn't have any similar experience with any white international students.