[matsemann]

Another classic is "c string".

[_peeley]

Every time I need to write up a research paper in TeX and insert a graph, I make the same mistake of searching "latex images" and getting some pretty exotic results

[tda]

I recall a colleague googling Prince Albert in front of his boss whilst discussing a potential project in Monaco. That was before either before safe search was a thing or he had it switched off.

[I_complete_me]

As a construction engineer, content with the word "erection" is very common but not very easy to get by the filters.

[skinkestek]

Another classic was (I haven't tested recently) that while Firefox would search if you entered a word that was not an address into the adress bar, while certain older browsers, at least Safari just added .com

:-/

[slig]

I remember that, specifically Python dot com. (was NSFW back in the day, enter at your own risk).

[nojs]

I remember studying fork/exec at uni and having some awkward queries involving “fork”, “kill” and “child”.

[BeFlatXIII]

I just got results for repairing cellos and violas. "G string" got the expected spicy content in addition to violin repair ads. Surprisingly, no string bass repairs (in spite of the bass also having a g-string)

[bobbyi]

When I first started using the python tool/ library named fabric, I knew that putting just "fabric" into google would not get me what I wanted, so I instead searched for "python fabric". The top results were trying to sell me handbags and boots.

(These days, the library does rank first for "python fabric").

[DylanSp]

And when you need to look up the Typescript playground, it's probably best not to abbreviate typescript as "TS".

[felipeccastro]

"mongoose relationships" is not always what you would expect, either.

[leephillips]

I learned something new today. And not about strings in C.