Technology

59581 readers

4728 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

549

The Man Who Killed Google Search (www.wheresyoured.at)

submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]

135 comments fedilink hide all child comments

Edward Zitron has been reading all of google's internal emails that have been released as evidence in the DOJ's antitrust case against google.

This is the story of how Google Search died, and the people responsible for killing it.

The story begins on February 5th 2019, when Ben Gomes, Google’s head of search, had a problem. Jerry Dischler, then the VP and General Manager of Ads at Google, and Shiv Venkataraman, then the VP of Engineering, Search and Ads on Google properties, had called a “code yellow” for search revenue due to, and I quote, “steady weakness in the daily numbers” and a likeliness that it would end the quarter significantly behind.

HackerNews thread: https://news.ycombinator.com/item?id=40133976

MetaFilter thread: https://www.metafilter.com/203456/The-core-query-softness-continues-without-mitigation

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 32 points 7 months ago (2 children)

As an programmer, I want to think out loud about possible technical solutions.

I would have kept the understandable / hand-made algorithm as the core of search results. If you want to do fancy machine learning, do it on the periphery and we can include the machine output in our algorithm and weight its importance by hand. This would allow us to back out of the decision, because we could lower the weight of the machine learning output as needed.

It sounds like Google jumped strait to including the machine learning in the core algorithm though, and now with a decade of complexity in the core algorithm they are no longer able to go back without huge effort.

In general, it's important to consider "is this a decision we can easily back out of?".

[–] [email protected] 16 points 7 months ago (1 children)

Amazon (and I'm sure others) refers to this as a two way door. Good rollouts minimize impact and can be undone easily.

[–] [email protected] 4 points 7 months ago (1 children)

Exactly, and that's something my company is aggressively moving toward, even though our userbase is nothing like Google's. It's just good engineering to be able to rapidly undo an unfavorable rollout.

[–] [email protected] 2 points 7 months ago (1 children)

Google's operations are absolutely built around the idea of easy rollback. Their products, and the their entire product ecosystem, are not.

[–] [email protected] 2 points 7 months ago

Yeah, they seem to do "easy roll-foward." Any service is subject to replacement, given a sufficiently motivated project manager. So if there's a problem in deployment, they just replace the whole thing.

[–] [email protected] 7 points 7 months ago

Did you read the piece? This isn't a software issue, it got worse by design to push even more ads and stop suppressing the ad-ridden fake sites too.