←back to thread

The man who killed Google Search?

(www.wheresyoured.at)
1884 points elorant | 2 comments | | HN request time: 0.001s | source
Show context
gregw134 ◴[] No.40136741[source]
Ex-Google search engineer here (2019-2023). I know a lot of the veteran engineers were upset when Ben Gomes got shunted off. Probably the bigger change, from what I've heard, was losing Amit Singhal who led Search until 2016. Amit fought against creeping complexity. There is a semi-famous internal document he wrote where he argued against the other search leads that Google should use less machine-learning, or at least contain it as much as possible, so that ranking stays debuggable and understandable by human search engineers. My impression is that since he left complexity exploded, with every team launching as many deep learning projects as they can (just like every other large tech company has).

The problem though, is the older systems had obvious problems, while the newer systems have hidden bugs and conceptual issues which often don't show up in the metrics, and which compound over time as more complexity is layered on. For example: I found an off by 1 error deep in a formula from an old launch that has been reordering top results for 15% of queries since 2015. I handed it off when I left but have no idea whether anyone actually fixed it or not.

I wrote up all of the search bugs I was aware of in an internal document called "second page navboost", so if anyone working on search at Google reads this and needs a launch go check it out.

replies(11): >>40136833 #>>40136879 #>>40137570 #>>40137898 #>>40137957 #>>40138051 #>>40140388 #>>40140614 #>>40141596 #>>40146159 #>>40166064 #
JohnFen ◴[] No.40136833[source]
> where he argued against the other search leads that Google should use less machine-learning

This better echoes my personal experience with the decline of Google search than TFA: it seems to be connected to the increasing use of ML in that the more of it Google put in, the worse the results I got were.

replies(3): >>40137620 #>>40137737 #>>40137885 #
jokoon ◴[] No.40137885[source]
that's not something ML people would like to hear
replies(2): >>40137911 #>>40144802 #
oblio ◴[] No.40137911[source]
Is ML the new SOAP? Looks like a silver bullet and 5 years later you're drowning in complexity for no discernible reason?
replies(5): >>40137975 #>>40137976 #>>40138686 #>>40139546 #>>40141708 #
1. __loam ◴[] No.40137975[source]
Don't forget about that expensive GPU infrastructure you invested in.
replies(1): >>40138296 #
2. jokoon ◴[] No.40138296[source]
and the power bill

and how difficult it is to program those GPU to do ML