Earlier quoted context omitted.
Reminds me of when GitHub stopped using "master" for the default branch because it was somehow offensive.
Main is better. Master/slave has uncomfortable connotations. This one isn't a big deal.
Google’s AI-powered ‘inclusive warnings’ feature is very broken
291–300 of 1001 posts
Re: Google’s AI-powered ‘inclusive warnings’ feature is very broken
#292I wonder if this is an example of not knowing your audience (or rather assuming one's self represents a wider audience than it does). The people vouching for this at Google are likely product marketing managers, public relations folks, social media managers, etc. All they do is write corporate garbage all day, and much like we have "nit"s in PR's for formatting, variable names, etc; they likely have similar reviews t…
I appreciate you adding to the conversation.
Re: Google’s AI-powered ‘inclusive warnings’ feature is very broken
#293I spent many years in the bluest corner of a very blue state. But still I can't imagine any objection to the word "landlord" outside of (1) a right wing attempt to satirize the left, (2) a Google product brainstorming meeting, or (3) a rare sincere outlier or concern troll. In any of those cases I don't think this is necessary. That said, if the word "landlord" organically fell out of favor and out of usage to be rep…
Google wouldn’t be my first choice, but it’s nice that someone is able to dedicate attention to this.
Re: Google’s AI-powered ‘inclusive warnings’ feature is very broken
#294Humans act so weird in large groups.
Re: Google’s AI-powered ‘inclusive warnings’ feature is very broken
#295Earlier quoted context omitted.
Reminds me of when GitHub stopped using "master" for the default branch because it was somehow offensive.
Main is better. Master/slave has uncomfortable connotations. This one isn't a big deal.
As far as "uncomfortable connotations", would you agree that that's a subjective claim?
I don't like that forced slavery is a thing, but I'm capable of handling context-specific word meanings, and of not getting emotional due to alternative meanings.
Re: Google’s AI-powered ‘inclusive warnings’ feature is very broken
#296In the article they use the example of "Motherboard" and "Landlord" and seem to suggest that these are areas where the Google AI is making mistakes or being overly strict. As a Google employee expressing my own opinion and observations of company culture, I can say that these are 100% not mistakes. Many Google employees are just so out of touch with the real world that they believe it is the duty of Google Docs to ch…
> Many Google employees are just so out of touch with the real world This isn't remotely limited to Google. My company does this too. I've heard of others making similar changes. Are these kinds of arbitrary changes to language usage silly and pointless? Maybe. But tough love here: languages change in arbitrary and pointless ways constantly. They always have. They always will. Your own common usages and idioms would…
Re: Google’s AI-powered ‘inclusive warnings’ feature is very broken
#297Earlier quoted context omitted.
I'm not worried about being Damore'd, as I have a lot more experience fighting progressives than he does.
What things did Damore do wrong that you would do differently (honest question)
Re: Google’s AI-powered ‘inclusive warnings’ feature is very broken
#298Who was asking for Woke Clippy? Is Google just bored and completely out of ideas? They seem increasingly disconnected with what their users actually want.
... and the willingness to take risks has historically served them pretty well.
Re: Google’s AI-powered ‘inclusive warnings’ feature is very broken
#299Earlier quoted context omitted.
Reminds me of when GitHub stopped using "master" for the default branch because it was somehow offensive.
My opinion: `main` is better. It's shorter, it's more descriptive, and costs nothing to remove something someone might find offensive. It's pretty much an all around win.
Re: Google’s AI-powered ‘inclusive warnings’ feature is very broken
#300I've been privy to people trying to ban words like "whitelabel" at my company. Thankfully, management & executives at my company never stood for that BS so I still get to use whitelist & blacklist in documentation, and don't worry about those non-issues get in the way of me actually doing work. Google might be too far gone, and working with those people would be so exhausting that it's actually stopped me from applyi…
My problem with all of this "progressiveness" in the workplace is that it just reeks of laziness. There are real problems in this world, yet it seems that the progressives are going after the minute details. From a SWE perspective, it would be like your app getting crushed by bugs and technical debt while you argue over how big the logo on the login page should be. The worst part of all of this, is the companies that…