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

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

  • Buttons@programming.devEnglish
    342·
    7 months ago

    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?”.

    • slumberlust@lemmy.worldEnglish
      16·
      7 months ago

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

      • sugar_in_your_tea@sh.itjust.worksEnglish
        4·
        7 months ago

        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.

        • bitwaba@lemmy.worldEnglish
          2·
          7 months ago

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

          • sugar_in_your_tea@sh.itjust.worksEnglish
            2·
            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.

    • yamanii@lemmy.worldEnglish
      7·
      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.