How do you determine what users want to see at internet scale? We ask Tito Director of Product Management at @Yahoo on this next episode of For the Sake of Search!
#SearchRelevance#Ecommerce#Search
https://t.co/Qkjhbhfb2w
The problem is sometimes bugs can linger a while before they're fixed. So a good heuristic we could use to solve this in a searchy way would be to boost issues that are viewed highly mixed with newer issues.
And that my friends is a search problem.
Case and point: user wants default sort to be newest issues when he lands on a project he's not interacted with before.
He shared most often when he visits new to him projects he has a bug and wants to see if it's been filed.
Okay, I am actually starting a serious company:
https://t.co/2rFivLCAXz
We're building the future of relevancy based search. We're pre-launch (despite launching this here). But we want to chat with small e-commmerce companies about their search problems.
Got bored… made an app this weekend to help me track my aquarium
https://t.co/Qt9Sqm9uTF
In case anyone else with a #reeftank wants a free place to track parameters over time 👀
Is X more responsive? Honestly, it’s so hard because so many people haven’t made the transition to <that platform> yet.
FOMO’s starting to kick in
It's always amazing to me how much work it takes to get "just search" working. This post/blog was a great reminder of that challenge.
Specifically, as it relates to building search indexes with the consistency mechanisms provided by Postgres.
1/12. I'm excited to share our latest technical blog post on ParadeDB.
After a brief hiatus focused on transforming ParadeDB into an enterprise-ready database, expect to hear a lot more from us.
Today's post: How ParadeDB built an LSM on top of Postgres block storage. 🧵
Super looking forward to getting to share about how @GitHub does ingestion! Hope to see you all there and let me know below, what do you want to know about ingestion?
The slides aren't done yet 😝
sneak peek: we'll have an @elastic developer event in mountain view in may — single track and just engineering. and I'll make sure to keep it *very* technical: besides developers from @langchain (@RLanceMartin) and @github (@dtaivpp) with more to come, we'll have @kimchy (Elasticsearch creator), @costinl (who most recently worked on JOINs for ES|QL), and dinesh (currently researching on agentic search) from elastic 1/2
@github friends I need your help! We want to make search even better for everyone using GitHub but we need to hear from you!
Tell us about your experience searching on GitHub below and let's make it better together 🫶