I am 100% convinced that "traditional" Google search moved to come kind of embeddings distance, LLM based algorithm at some point in the last 12 months.
I've noticed a distinct change in the results where now what I get back seems MUCH more related to "semantic similarity" with my search query I actually entered.
Great examples of this are when you search for a highly common topic, but specifically related to a highly niche sub-variant or focus area.
"Old" Google would have hooked into the edge-case as being a critical part of the query and zeroed in on that specificity (which you wanted), whereas now it will just go "these results were semantically similar to 95% of your search query, therefore they must be most relevant" - totally ignoring that the 5% it ignored was the critical differentiator.
Another way to trigger this behaviour really easily is to look for a contrarian view on something widely discussed by adding "not" or "doesn't" into the query. Google will just straight up ignore your input, returning a tonne of results that are 95% semantic matches for the words you used, but missing that ONE tiny point where you were searching for literally the opposite of what it returned.
Sharing this here, something one of my teams just shipped, a lot more coming in the next few months (Custom Merge Checks, Runtime Dynamic Pipelines, and more).
Shameless plug for something one of my teams shipped this morning. Pipelines is an extremely under-publicised part of the Bitbucket Cloud Product and ironically one of the most well-liked.
Hey - when you say you 'Never head about' in relation to Bitbucket Pipelines, do you mean you'd never heard that Pipelines was a product that was available as part of Bitbucket?
Asking as I took over as the PM for Bitbucket Pipelines around 6 months ago and have been working to make the case for us needing to do a lot more to make people aware of the capability as a lot think Bitbucket is just Git, not CI/CD as well.
First of all, sorry for the spelling mistake (head/heard.)
You are correct, I didn't know about Pipelines. However I don't use Bitbucket myself. I only use it when a customer uses it and this was the first customer of mine that uses Pipelines. I remember that I setup a pipeline for a new project and it was easy to do it.
In general I'm always surprised by the amount of different products that do the same thing and I never heard about. The diversity is good, my ignorance is bad. However there is a limit on the number of things one can use.
Thanks so much for taking the time to reply, little anecdotes like this do a lot to help me make the case for us needing a better brand.
Completely understand where you're coming from re: the number of different tools.
Obviously I'd love it if we were one of the one's people thought of when the topic of integrated Git + CI/CD came up, but that's on us to change the level of awareness.
Hey - PM from the Bitbucket Cloud Pipelines team here. We're actually kicking off internal beta testing of ARM runners for Bitbucket Pipelines as we speak.
If you're interested in being involved in that EAP please reach out to me at emunday@atlassian.com
https://bitbucket.org/blog/announcing-our-new-ci-cd-runtime-...
Come check out some of our cool new features while you're at it:
- https://bitbucket.org/blog/introducing-dynamic-pipelines-a-n...
- https://bitbucket.org/blog/custom-merge-checks-are-now-gener...