{"version": "1.0", "type": "rich", "title": "5th July 2023", "author_name": "kontextmaschine", "author_url": "https://kontextmaschine.com", "provider_name": "kontextmaschine", "provider_url": "https://kontextmaschine.com", "url": "https://kontextmaschine.com/post/721962411572264960/", "html": "

sreegs:

animentality:

I’ve worked at big software companies long enough to know how this would play out as a bug. Users report the issue. Engineers think oh thats a simple fix. However this is Google so it’s likely these tickets are triaged in a way that someone like a project manager has visibility into it before deciding to dedicate time into it.

the project manager asks “is this a bug, though?” not because of homophobia but because they want to know how many users experience this as being an incorrect suggestion vs a valid suggestion. so they call the data scientists in and run some queries, and lo and behold because there’s more straight couples in the world of course the data shows this is only affecting a very small amount of users. this is working fine for most users.

but the engineers and other stakeholders point out why this isnt as simple as what the data days and it’s more of a UX thing. call the project managers in for whoever’s in charge of like, grammar analysis and not just the system that flags it. an epic is created in jira. meetings are scheduled. don’t forget experts in other languages

five weeks later you’re running an A/B test on not correcting users when they write “his husband” to see if DAUs drop when your grammar suggestion engine considers that gay people can be married

", "thumbnail_url": "https://kontextmaschine.com/media/c285bb8d49531bfc41755dd19316669234bb5210_5887a5fdbc93.jpg", "thumbnail_width": 601, "thumbnail_height": 960}